Skip to main content
Geographic Information Systems

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • If you've got Esri, and it's working in Esri, why OGR2OGR? If you intention is to go open source why not select by location in QGIS and export selected records... Commented Dec 9, 2014 at 21:34
  • The Esri processing is taking way too long (weeks vs. ogr2ogr hours/days). I have 5 buffer sizes for 80,000+ grid points and I need to select only the exploded buffer features that can be selected by the grid point (buffer centroid). Commented Dec 10, 2014 at 2:34
  • Is it one polygon (buffer) for each size per point? It seems to me that the buffers are created by the points then have been erased by some other data. OGR2OGR is somewhat limited in this respect however it is quicker, would you consider using Near in Esri on the points to find the closest polygon then selecting by attributes (FID = Near_FID)? The other option is moving the shapefile to spatial lite or PostGis which do support spatial operators. Commented Dec 10, 2014 at 2:41
  • That's an interesting approach. I have some stuff processing so I'll try and do some tests on that approach. I'm down this rabbit hole sort of b/c I know it works. Can MakeFeatureLayer_management and SelectLayerByLocation_management be improved using in_memory? Commented Dec 10, 2014 at 16:52
  • This is a similar processing function - saying to use Spatial Join - gis.stackexchange.com/questions/12448/… Commented Dec 10, 2014 at 17:08