sumo icon indicating copy to clipboard operation
sumo copied to clipboard

Public transport routes contain edges with no connection after gtfs import

Open slaemmer opened this issue 1 year ago • 0 comments

I create a network file for berlin using osm data - afterwards I use the gtfs import script to convert the publicly available gtfs data into a suitable format for the public transport. I do understand that the conversion from osm data into a sumo network file does not work flawlessly and the network often needs to be adapted afterwards.

However, I do not understand why the public transport routes are chosen in such way, that they contain malformed routes. According to the documentation the routes should be computed as fastest paths and therefore result in valid routes.

Also, weirdly, some of the errors were solved by just opening the network in netedit, switching to the connection mode, removing and setting them again, and then saving the network.

Appended is the network setup script and some of the errors that were thrown after iteratively running and solving them. If anything else is needed feel free to ask. Thanks!

issue_folder.zip

SUMO-version: 1.20

operating system: macOS 15.0

Note: I've just seen that --repair does seem to be an option that only impacts the conversion when using ptlines. I did set it initially though. Does it have an effect on the conversion when --osm-routes are not set? It should not, right?

slaemmer avatar Aug 27 '24 09:08 slaemmer