Create unsearchable preset for associatedStreet#997
Create unsearchable preset for associatedStreet#997tyrasd merged 1 commit intoopenstreetmap:mainfrom
Conversation
c611d30 to
35f423c
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
🍱 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. |
|
After we merge this, we need to ping #1538 because AFAIK this will need to be updated to add the new relation. |
|
tested https://pr-997--ideditor-presets-preview.netlify.app/id/dist/#locale=en&map=19.07/49.35525/19.60342&disable_features=boundaries&background=MAPNIK&id=r2172790 and it seems to work
without that PR:
PS I want to register my deep, deep dislike toward associatedStreet schema and expecting mappers to do manually what computers can do on their own and complicating tagging schema without good reason. I eradicated those in my area, with community agreement. |
|
Thanks for testing it @matkoniecz. Technically it looks good. I just noticed, that the reason for this PR was resolved 3 weeks ago with an exception in iD openstreetmap/iD#9639 (comment) So I would like to wait for other input on this before merging. Because as a data consumer I agree, that this tagging is problematic. |
|
Note that preset is unsearchable so it should not result in people being encouraged to use that terrible idea. And for example French community is using it anyway. |
|
@tordans How long we should wait? What you would propose as enough? Week? |


closes: openstreetmap/iD#9639