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

re-order stop-output attributes by importance. The stopping place id shouldn't be last #14542

Closed
namdre opened this issue Mar 19, 2024 · 3 comments

Comments

@namdre
Copy link
Contributor

namdre commented Mar 19, 2024

advantage: the (most often) relevant info can bee seen without horizontal scrolling or line wrapping)

disadvantage: potentially breaks every user script that uses parse_fast on stop-output
this only seems to affect ptlines2flows on our side (used attributes still in correct order)

@namdre namdre changed the title rorder stop-output attributes by importance. The stopping place id shouldn't be last re-order stop-output attributes by importance. The stopping place id shouldn't be last Mar 19, 2024
@namdre
Copy link
Contributor Author

namdre commented Mar 26, 2024

xml attribute order is generally not to be relied on... (Mirko)

@namdre
Copy link
Contributor Author

namdre commented Mar 26, 2024

@behrisch your comments?

@behrisch
Copy link
Contributor

Go ahead. I would not agree in general because apparently parse_fast relies on the order but stop-output does not seem so important to me. (I would not agree if we reorder fcd-output attributes for instance).

@namdre namdre closed this as completed in e93afd7 Apr 11, 2024
namdre added a commit that referenced this issue Apr 11, 2024
behrisch added a commit that referenced this issue Apr 11, 2024
namdre added a commit that referenced this issue Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants