Make segment size configurable

[ArdtK]

Currently edges are segmented in pieces of 100m. OsmNetworkWrapper._download_clean_graph_from_osm

Workflow (OSM)

• Simplified base_graph (MultiDiGraph) is downloaded from OSM and complex base_network (GeoDataFrame) is created
  • Networks: _get_new_network_and_graph
  • OsmNetworkWrapper: _download_clean_graph_from_osm/_get_clean_graph_from_osm based on polygon

Conclusion: for OSM no segmentation is done. The edges of the originally downloaded (complex) graph are used

Workflow (Vector)

• The vector file is read into vector data (GeoDataFrame)
  • VectorNetworkWrapper: _read_vector_to_project_region_and_crs
• The vector data is converted into a graph (Graph/DiGraph)
  • VectorNetworkWrapper: _get_direct_graph_from_vector
• From graph the edges and nodes are extracted (both GeoDataFrame)
• From these edges and nodes a complex_graph is created (why these additional 2 steps?)
• This complex_graph is directed, deduplicated and simplified
• From this graph (again) the edges are derived

Conclusion: for Vector no segmentation is done.

Workflow (Shape/Trails)

• TODO
• Segmentation (segmentation_length) based on degree (0.001 ~ 111 m in Europe) based on network config cleanup.segmentation_length. This is not very precise worldwide due to projection.

Tasks

• [ ] Find out where the segment size is determined
• [ ] Add as config

[ArdtK]

Conclusion The network downloaded from OSM/Vector is converted to 2 GeoDataFrames, containing the nodes and edges. These are not segmented.

[ArdtK]

@mjevanmarle will create new issue for segmentation of graph before calculating the damages.