namdre
commented
1 month ago The discrepancy comes from the fact that the component search is done in the node/edge graph whereas "select reachable" is done in the lane/connection graph.
Furthermore pedestrian simulation has two modes:
- [detailed mode[(https://sumo.dlr.de/docs/Simulation/Pedestrians.html#building_a_network_for_pedestrian_simulation) (this requires additional options to build "crossings" and "walkingares" and will cause additional connections to be created) - since you didn't activate these options, the sidewalks have no connections
- simple mode: pedestrians ignore connections in the network and only care about the topology of the node/edge graph
If you don't need the pedestrian network at all, you can get rid of it by setting netconvert option --remove-edges.by-vclass pedestrian. Otherwise, set option --crossings.guess to build detailed connectivity.
The same goes for rail edges: If you want to get rid of them, add the relevant classes to option --remove-edges.by-vclass .
If you only need cars you can just set --keep-edges.by-vclass passenger instead.
Importing OSM data for the a part of Berlin results in a network that contains many edges that are connected by junctions but are still not reachable. When using the provided script to import the OSM data, many edges are unusable as no traffic can flow between them and any other edge. Right clicking an exemplary edge using sumo gui and selecting "select reachable > pedestrian/passenger" shows no connected edges.
I do understand that converting the imported data is complex but I do not know how to handle that many edges which are not connected. Using the option "--keep-edges.components 1" does not solve the problem as it apparently viewes the edges as connected.
SUMO-version: 1.20
operating system: Mac OS 14 or Rocky Linux 8.9
Steps to reproduce:
Script: setup_wedding_net.txt
Thanks for a fix or an existing solution to this!