Skip to content
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

keep track of osm way id #2

Open
nlehuby opened this issue Feb 13, 2019 · 3 comments
Open

keep track of osm way id #2

nlehuby opened this issue Feb 13, 2019 · 3 comments

Comments

@nlehuby
Copy link

nlehuby commented Feb 13, 2019

To debug easily, it would be great to get the way id from OSM. Maybe in the shape_id of the GTFS or at least in the geojson path.json when you only compute one trip.

I will make possible to fix OSM more easily if the shape is not consistent and it could even be used to map the shapes of the transport routes in OSM (as they are OSM relations with the list of the ways in the right order)

@patrickbr
Copy link
Member

I agree. However, pfaedle simplifies the input OSM graph and any 1:1 mapping between edges and OSM ways is lost. I will think about skipping these simplifications and storing the OSM way ids somewhere if a flag is set.

@nlehuby
Copy link
Author

nlehuby commented Feb 13, 2019

it would be cool 👍

@hbruch
Copy link

hbruch commented Feb 13, 2019

Would really be cool. This could be used to maintain OSM's route relations, also. Perhaps pfaedle could report the OSM IDs of matched stop_positions, as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants