teambtcmap/btcmap-general
8
0
Fork 0
Code Issues 8 Pull Requests Actions Packages Projects Releases Wiki Activity

REvised changeset guidance.

Nathan Day 2025-05-19 15:58:47 +00:00
parent 63a650ee58
commit 937c57e6df
1 changed files with 16 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
Tagging-Merchants.md

@ -30,11 +30,11 @@ A video tutorial can be found [here](https://rumble.com/v1ldybp-how-to-create-an
Add new or update existing locations directly as you see fit or help with the backlog of submissions from the Noob Form at one of the links below:
- [New locations ready for Shadowy Supertaggers](https://github.com/teambtcmap/btcmap-data/issues?q=is%3Aissue+is%3Aopen+sort%3Acreated-asc+label%3Alocation-submission+-label%3Aassigned+no%3Aassignee) 🆕
- [New locations ready for Shadowy Supertaggers](https://gitea.btcmap.org/teambtcmap/btcmap-data/issues?q=&type=all&state=open&labels=901) 🆕
- [Verified locations ready for Shadowy Supertaggers](https://github.com/teambtcmap/btcmap-data/issues?q=is%3Aopen+is%3Aissue+label%3A%22verify-submission%22+-label%3Aassigned+no%3Aassignee) 📍
- [Verified locations ready for Shadowy Supertaggers](https://gitea.btcmap.org/teambtcmap/btcmap-data/issues?q=&type=all&state=open&labels=903) 📍
If you're a serious tagger, please consider joining the Shadowy Supertagger Team on GitHub so you can manage issues. We have a Supertagger [Discord](https://discord.gg/f88bzkDA4u) channel to get you onboarded.
If you're a serious tagger, please consider joining the Shadowy Supertagger Team on GitHub so you can manage issues. We have a Supertagger [Discord](https://discord.gg/f88bzkDA4u) channel to get you on-boarded.
Please use the following guidance when editing locations:
@ -42,15 +42,15 @@ Please use the following guidance when editing locations:
Our main goal is to provide the public with an accurate data-set and locals know best. Please try to prioritize locations with close physical proximity to you. Make sure that you're relying on the most accurate data, such as:
- On-site survey.
- Direct phone/email ([e.g.](verifying-locations.html))/social media survey.
- On-site survey
- Direct phone/email/socials
- Various online sources (be careful about [copyright](tagging-instructions.html#copyright)), not all online data is free to use! The official website of the merchant is usually the best online source.
Relying on a form submission without any additional checks is discouraged. An extra step of due diligence should be taken to ensure we are adding accurate data to OpenStreetMap and being good stewards of the database.
Relying on a form submission without any additional checks is strongly discouraged. The information submitted should be verified to ensure we are adding accurate data to OpenStreetMap.
### Double-check Coordinates
If taking on issues submitted from the Add Location form, you can and should make adjustments to the exact pin location IF you notice it is incorrect. The person submitting the location will not be a mapping expert and that it ok - this is where the extra validation by the Supertagger can help improve the data accuracy. Any submissions with completely invalid locations (like in the middle of the ocean) can be closed as not-planned with the reason provided in a comment.
If taking on issues submitted from the Add Location form, you can and should make adjustments to the exact pin location IF you notice it is incorrect. The person submitting the location will not be a mapping expert and that is ok - this is where the extra validation by the Supertagger can help improve the data accuracy. Any submissions with completely invalid locations (like in the middle of the ocean) can be closed as not-planned with the reason provided in a comment.
### Source of Data
@ -117,11 +117,18 @@ It is easy to look up all the available tags and their use-cases in the OSM [Wik
### Changeset Comments
Every edit on OpenStreetMap has the option to add a changeset comment. This is an important way for other OSM contributors to get a quick idea of what the edit contained. You can include a short description of your changes in this field.
Every edit on OpenStreetMap has the option to add a changeset comment. This is an important way for other OSM contributors to get a quick idea of what the edit contained. You should include a short description of your changes in this field.
Please include:
- The `#btcmap` hashtag in your changeset comments so that the activity is associated with our [Organised Editing](https://wiki.openstreetmap.org/wiki/Organised_Editing/Activities/BTCMap) initiative.
- Under `source` the Issue ID in the form `issue:1234` as a minimum. Refrain from using "Local Knowledge" as a proxy and be specific where possible e.g. "Confirmed via email with business owner".
You should also include the Issue URL as
Additionally, another OSM contributor may ask a question for clarification about one of your edits. You should receive an e-mail notification when this happens. Please make an effort to respond to any non-frivolous and respectful questions.
Please include the `#btcmap` hashtag in your changeset comments so that the activity is associated with our initiative.
## Completing Issues