rivus icon indicating copy to clipboard operation
rivus copied to clipboard

Feature Request: OSMnx integration for possible better data aqcuisition

Open lnksz opened this issue 8 years ago • 0 comments

Package OSMnx should be investigated, as it proposes a very convenient gdf_from_place function.
(Although it fetches only one polygon, the source could serve as a good example for similar functionality.

Alternatively, as the NetworkX integration has been already started by #22, the whole shapefile phase could be skipped, with its ox.graph_from_place('Manhattan, New York, USA', network_type='drive') function. And the spatial data (at least vertex and edge, without demand and source data) could be calculated from that source.

There are even some possibilities to simplify the resulting graph, which could be an alternative to the current skeletron based approach.

Furthermore, this package already solved the automated UTM code calculation so at least, that would be of great use for us. :

    >>> osmnx as ox
    >>> city = ox.gdf_from_place('Berkeley, CA')
    >>> city_xy = os.project_gdf(city)
    >>> G = ox.graph_from_place('Manhattan, New York, USA', network_type='drive'

Summary:

  • [ ] Check out gdf_from_place(), let it inspire us.

  • [ ] Consider an OSM -> NetworkX -> GeoDataFrame workflow instead of / besides OSM -> Mapzen -> Shapefiles -> GeoDataFrame

  • [ ] Investigate graph simplification steps instead of skeletron's topology based approach.

  • [ ] Adopt the automatic WGS84 to UTMXX projection method. That mean senseful data in the GeoDataFrames. (.length attribute would be calculated correctly plus we could leverage Shapely's full functionality)

lnksz avatar Sep 10 '17 15:09 lnksz