Tag Info

New answers tagged

-1

The build is broken. Cross compiling from Linux with the same versions just fixed the issue.


1

It is entirely valid, but it may not produce the results you expect in any Cartesian coordinate space. So it isn't a problem with degrees or WGS84, but rather the mapping from the ellipsoid to a plane. If the polygon is very large, the mapping of the curved surface on the ellipsoid to the plane can produce some artifacts where a point looks like it would be ...


0

Near is not your friend in this case: It alters the point features by adding NEAR_FID and NEAR_DIST to their table and optionally other fields. You are right, a point can only be 'near' one polygon. What you really want is Generate Near Table with a search_radius of 0 (or at least something very small) - a point on a line mathematically is very difficult ...


0

Intersect points and polygons (ArcGIS) - output type - point. For points exactly on the shared boundary of 2 polygons this will result in 2 points


1

For ArcGIS I would suggest using a python script for this. The general code flow would go something like: Make feature layer of point layer Create count field for polygon layer Define update cursor on polygon layer Loop through each feature and use select layer by location method Use get count method to get the number of selected point features Write ...


0

All but one of the point in polygon libraries / routines that I've found fail on a polygon that includes the date line. The all seem to use ray casting or other algorithms that wrap the wrong way or just simply don't work. I believe that the routine in OGR works properly but it's somewhat complex to implement. ...



Top 50 recent answers are included