Conversation
With this change just selector is not enough at all. iD, maybe other data consumers, really should get request along 'For incline=up/down show which end is up' lines maybe such hint should be part of iD tagging schema? Which other fields would benefit from such hint?
|
after this is merged: create mentioned iD issue, maybe schema builder issue, maybe GoMap!! issue, maybe for other data consumers take look at #2049 (comment) an open next radio PR |
|
🍱 Your pull request preview is ready Please use this preview to check your changes. Ideally use the test documentation template and document your test results by commenting on the PR. This will speed up the review process for everyone. FYI, once this PR is merged, you can use the iD Editor Preview to test your changes in interaction with all other changes. |
|
note: steps start suffering from field taking more space steps
ladder https://pr-2141--ideditor-presets-preview.netlify.app/id/dist/#locale=en&map=22.55/52.16956/21.06761&disable_features=boundaries&background=MAPNIK&id=w1420792996 |



With this change just selector is not enough at all.
iD, maybe other data consumers, really should get request along 'For incline=up/down show which end is up' lines
maybe such hint should be part of iD tagging schema? Which other fields would benefit from such hint?
Description, Motivation & Context
see #2049
Related issues
part of #2049
Links and data
Relevant OSM Wiki links:
Relevant tag usage stats:
Checklist and Test-Documentation Template
Read on to get your PR merged faster…
Follow these steps to test your PR yourself and make it a lot easier and faster for maintainers to check and approve it.
This is how it works:
After you submit your PR, the system will create a preview and comment on your PR:
Once the preview is ready, use it to test your changes.
Now copy the snippet below into a new comment and fill out the blanks.
Now your PR is ready to be reviewed.