-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with artificial links generated #147
Comments
Looks to me like an issue with coordinate systems, there's a note on that in the wiki. Did you convert the schedule to a projected coordinate system? |
Hi, Federico |
Goodmorning, Federico |
Yes the workflow looks like this:
both Gtfs2TransitSchedule and Osm2Multimodalnetwork should convert their input data to a projected coordinate system. I can't tell whether 1k link is ok for your area but it does seem high. It's generally better to just look at the generated network/schedule (in via) and see if the links make sense or if some parts are missing (e.g. railway). I'd focus on that visual analysis first instead of the plausibility check. |
Hello,
I'm using pt2matsim. I'll try to explain myself as clear as possible.
I downloaded first the .osm map, and using the MATSim plugin in JOSM I generated the network.xml. After that, I downloaded the GTFS files, executed first the GTFS2Transit to generate both the transit and the vehicles, then I generated the config file with CreateDefaultPtMapperConfig, modified it accordingly in order to generate the final network.
When I finally run the checkmappedscheduleplausability, I saw that the mapper generated around 10k artificial links, even though in the plausability output it could find out the corrected transit route (schedule_TransitRoutes).
I'll attach the zip of the plausability and the config file, maybe I messed up in the generation of the config file.
Kind regards,
Federico Bigi
allPlausibilityWarnings.xlsx
config.txt
The text was updated successfully, but these errors were encountered: