New answers tagged intersection
0
If a license higher than "Basic" is available a great option is the Planarize Lines tool on the Topology toolbar:
http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//001t0000008t000000.htm
2
Try using Split (Analysis) to subset your data.
To illustrate, I added a new text field to the split features (i.e. 1-16 based on OID) and used that as the basis for the split. There are 16 resulting shapefiles on the image to the right.
Also, try the Split Layer by Attributes script tool if you have licensing issues. I believe you may need to ...
0
Have you tried "Union" in Analysis tools?
0
If you're interested in the simple hexagon cartogram approach, Hexer is available. I use it for generating density and boundary maps of large LiDAR point sets (millions). It can read OGR point data sources in addition to ASPRS LAS data if you set the CMake config -DWITH_GDAL=ON when configuring.
0
There is the big difference between SDO_GEOM.RELATE and SDO_RELATE.
The first argument of SDO_RELATE specifies a geometry column in a table. So, at least one geometry object must be located in a table. It is the limitation. On the other hand SDO_RELATE can use the spatial index, so it works fast.
SDO_GEOM.RELATE doesn’t care about the geometry location.
...
0
As far as I know JTS does nothing with the SRID value (see this email). You will need to use GeoTools to reproject your features to a common projection and then call intersection on them. The result will then be in the common projection and you can then project back to one or both of the input projections.
1
There has been a recent trend towards questions asking for an explanation of the differences between tools. If you're using ESRI products the ArcGIS Online Help should be your first stop.
You can find full explanations of each tool:
Intersect
Clip
In this case you will find that the Intersect tool will create output features which possess the attributes ...
3
The main difference will be in the attributes of the results. When using Clip only the input feature’s attributes will be in the output (none from the clip feature), where if you used Intersect the attributes form all features used will be in the output.
0
Don't know if this is still an open question, but an idea that occurred to me was that if you had the points/centroids from which your circle polygons were generated, you might be able to more quickly assess their euclidean distance from the coast, select those below a threshold, and then relate these points to the polygon feature class and use that for a ...
2
You could try only doing the Within() test against points that are within the polygon features envelopes, i.e.
def PointsInPolygons(pointsLayer, polysLayer):
nbInside = 0
polyFeat=polysLayer.GetNextFeature()
while polyFeat:
polyGeo = polyFeat.GetGeometryRef()
pointsLayer.SetSpatialFilter(polyGeo) #<----Only test points within ...
0
You could add a field to your polygons and fill with some random but traceable value. Then do a Spatial join with the points, and all the points residing within a specific polygon will get the corresponding value.
Not sure if this will be any faster, but at least it's an alternative approach.
0
What you need is a Point-In-Polygon test, which is a standard algorithm and has been covered extensively in other sources.
See here
or here
or even this post here on GIS-SE
0
Actually, I was looking for something like this. At the end we've found solution:
double y = (Log(1/Tan(lat1/2+PI/4) * Tan(lat2/2+PI/4))+long1 *
1/Tan(alpha)-long2 * 1/Tan(beta)) / (1 /Tan(alpha) -1/ Tan(beta));
double x = (-Math.PI + 4 * Math.Atan(Math.Tan(lat1 / 2 + Math.PI / 4)
/ Math.Exp((long1 - y) * 1 / Math.Tan(alpha))) + 4 * Math.PI) / ...
Top 50 recent answers are included
