Change drop_shapes default to True#2070
Open
felixguendling wants to merge 1 commit intopublic-transport:mainfrom
Open
Change drop_shapes default to True#2070felixguendling wants to merge 1 commit intopublic-transport:mainfrom
felixguendling wants to merge 1 commit intopublic-transport:mainfrom
Conversation
most shapes contained in datasets have very low quality or are also routed on OSM like we do it (no improvement) therefore the default should be not to use them and if we find a dataset with better quality shapes than those we automatically compute via map matching on OSM data, it should be easy to keep the original shapes
Collaborator
|
I don't think this makes sense, then we can also use the MOTIS option to reroute everything. However I fully agree that the shapes from the Austrian Railway dataset don't provide any advantage, we can absolutely drop them. I could not easily find the problem with the FlixTrain shapes, what did you notice there? |
Contributor
Author
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Most shapes contained in datasets have very low quality or are also routed on OSM like we do (= no improvement).
Therefore the default should be not to use them, and if we find a dataset with better quality shapes than those we automatically compute via map matching on OSM data, it should be easy to keep the original shapes.
Just looking at Germany, we get low quality shapes for FlixTrain, from Austrian datasets that have partial shapes (only routed in Austria), in Berlin there are buses flying through buildings, etc.
I agree that there might be cases where a dataset has better shapes than what MOTIS would compute. However, the default is that I browse through the debug view to find bugs in our map matching and almost every shape that looks bad turns out to have
TIMETABLEas source. So we would definitely benefit from dropping them by default in order to improve average shape quality.Edit: another option would be to drop a lot of shapes (manually going through a lot of datasets and setting the flag) and monitor this for all new datasets. Since nobody is willing to do this, the better option is to drop the shapes by default and for the rare cases where we know that the dataset has better shapes, we can put an effort to disable
drop_shapes.