Finding Intersections with Python: Difference between revisions
Brian Wilson (talk | contribs) mNo edit summary |
Brian Wilson (talk | contribs) |
||
Line 33: | Line 33: | ||
=== GDAL === | === GDAL === | ||
Here is a page where I talk about [[Building GDAL | Here is a page where I talk about [[Building GDAL on Linux]]. | ||
=== Shapely === | === Shapely === | ||
Here is the home of [http://pypi.python.org/pypi/Shapely Shapely] |
Revision as of 16:03, 6 February 2013
Where roads meet
We need to be able to build a table of all the places roads meet.
- Not just geometric intersections. Road intersections.
- And we don't want to find the places that roads CROSS (over- or under-crossings).
Both of these points are salient because they mean dealing with dirty input data.
- Roads should always meet at a vertex
- Roads that meet should always have a common vertex, not just be "close".
- Roads that do not meet (crossings) should NOT meet these conditions.
To this end, I want a tool that:
- Generates a point layer of intersections
- Generates a point layer of error cases
The tools
I have a version of this program already written in C# using ArcObjects, and it's a BIG MESS. Worst of all, every time I do a build in a new release of ArcGIS, it breaks!
I want something easy to maintain, easy to update, easy to run, and reasonably fast.
To accomplish this I am reading Python Geospatial Development by Erik Westra. Packt Pubs
At this point, I'd prefer NOT to use PostGIS because I might end up giving the tool away to ArcGIS users. I think this means I will be using Shapely.
I want to be able to use File Geodatabases, so I will be using a custom built GDAL with Python bindings.
GDAL
Here is a page where I talk about Building GDAL on Linux.
Shapely
Here is the home of Shapely