-
Notifications
You must be signed in to change notification settings - Fork 884
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
Suggestion : store NSI data in the OSM wikibase #4657
Comments
Is there anything actionable for us to do? |
I guess the idea is to expand the wikidata script to also add the nsi entries (and all the tags) into the OSMwikibase ? |
First, "discussed" if it could be a good point for NSI project and OSM 😃 But, we could write code for the website to add and edit "brand"… |
Sorry @pyrog but I still don't really understand what this issue is about. |
I'm all for storing critical OSM metadata in the data items, but we should discuss all the logistics of that process -- how items are added, if we should have an extra UI for it, how downstream projects consume such information, issue resolution, etc. |
Nice 😃
👍 Where, here ?
Currently JOSM do that to fetch formatter URL (P8). |
We already use a node.js script to sync up all the NSI items to Wikidata so we'd probably just use that same script (or one just like it) to push our data to OSM's wikibase too. |
stale |
The OSM wikibase (aka Data Items) is (or will be) the repository of OSM keys, tags, concepts…
One don't need to write an issue or a PR, just create a new data item and add properties 😃
@nyurik
The text was updated successfully, but these errors were encountered: