unenTT's Comments
| Changeset | When | Comment |
|---|---|---|
| 186912334 | Hi, the associated Maproulette challenge is paused as of August 4, and is not accessible until the QA is completed. |
|
| 186589943 | Hi James, I understand the issue, but the solution you have implemented is against the OSM community guidelines unfortunately. The name of the road should be reverted to its previous state, without any numbering, as the numbers should be incorporated into the buildings with appropriate address tags. When I check the info on the Credit Union building, I'm seeing that the address is tagged properly as 5000 E George Richey Road. So I'd assume that the issue is not with OSM data, but with the software you are mentioning. I'd also want to share the following article, as tagging for the renderer/router is not encouraged within the OSM community: osm.wiki/Tagging_for_the_renderer Please feel free to reach out and let me know how I can be of help in resolving the issue. All the best. |
|
| 186512594 | Hi Tomas. Thanks for reverting the changeset and sticking with data accuracy. Please accept our apologies in this case as it seems like there were duplicate tasks for the same location, one for a sharp angle and another for very short segments. We’ll investigate this and try to avoid similar situations. Thank you for your understanding on this matter. |
|
| 184515411 | Hi 9_tab, thank you for your understanding on my late response as I was out of office and was not able to check my messages until Monday. For OSM editing, we don't have an alternative spec document to the OSM Wiki. osm.wiki/Organised_Editing/Activities/TomTom#Editing_Requirements states that our editing team refers to OSM Wiki for following community standards. The work process regarding this incident is also documented in osm.wiki/Organised_Editing/Activities/TomTom#TomTom_Map_Feedback So here Sebasawk referred to the service=driveway article in their edit and interpreted things that way. Again, local practices and interpretations might differ from region to region, and right now we are also aware what you consider to be a driveway and a service way. We will do our best to take note and align accordingly. Please let me know if we'd need to further clarify anything by directly reaching out to me. I'd also happy to connect you with our community manager for Switzerland for deeper discussions, if necessary. |
|
| 183586688 | Hi Marvk, thank you for your feedback and clear explanations on what went wrong. We also experienced some issues on our changeset notifications which seem to be working well now. We are looking at the issues to carry out the necessary fixes, also addressing the matter internally to make sure our organised editing team contributes to high-quality, accurate data to OpenStreetMap. |
|
| 184431396 | Hi hsc666, thank you for your feedback and clear explanations on what went wrong. We are looking at the issues to carry out the necessary fixes, also addressing the matter internally to make sure our organised editing team contributes to high-quality, accurate data to OpenStreetMap going forward. |
|
| 184432735 | Hi hsc666, thank you for your feedback and clear explanations on what went wrong. We also experienced some issues on our changeset notifications which seem to be working well now. We are looking at the issues to carry out the necessary fixes, also addressing the matter internally to make sure our organised editing team contributes to high-quality, accurate data to OpenStreetMap. |
|
| 184431950 | Hi hsc666, thank you for your feedback and clear explanations on what went wrong. We are looking at the issues to carry out the necessary fixes, also addressing the matter internally to make sure our organised editing team contributes to high-quality, accurate data to OpenStreetMap going forward. |
|
| 184431627 | Hi Christopher, thank you for your feedback and clear explanations on what went wrong. We are looking at the issues to carry out the necessary fixes, also addressing the matter internally to make sure our organised editing team contributes to high-quality, accurate data to OpenStreetMap going forward. |
|
| 184322703 | Hi rab, thank you for your feedback and clear explanations on what went wrong. We are looking at the issues to carry out the necessary fixes, also addressing the matter internally to make sure our organised editing team contributes to high-quality, accurate data to OpenStreetMap going forward. |
|
| 184515411 | Hi there. I’m Can, a project manager from TomTom’s OSM program. Regarding the distinction between a service road and a driveway, our editing team might treat a driveway as a road leading to a single feature only, as the last segment that is branching out from service roads. Members of our editing team perform edits globally and mainly stick to Wiki definitions. But we are also aware that mapping practices and interpretations might differ between different communities and regions. And if those different interpretations are also documented on OSM Wiki or another relevant space such as the community forum, we try to respectfully follow the local practices as well. In this case, your interpretation of driveways is duly noted as well as your concerns. Please reach out to me and let me know if further alignment would be necessary. |
|
| 183585778 | Hi Marvk, thank you for your feedback and clear explanations on what went wrong. We are looking at the issues to carry out the necessary fixes, also addressing the matter internally to make sure our organised editing team contributes to high-quality, accurate data to OpenStreetMap going forward. |
|
| 182979881 | Hi Marvk, thank you for your feedback and clear explanations on what went wrong. We are looking at the issues to carry out the necessary fixes, also addressing the matter internally to make sure our organised editing team contributes to high-quality, accurate data to OpenStreetMap going forward. |
|
| 182977310 | Hi Marvk, thank you for your feedback and clear explanations on what went wrong. We are looking at the issues to carry out the necessary fixes, also addressing the matter internally to make sure our organised editing team contributes to high-quality, accurate data to OpenStreetMap going forward. |
|
| 182976387 | Hi Marvk, thank you for your feedback and clear explanations on what went wrong. We are looking at the issues to carry out the necessary fixes, also addressing the matter internally to make sure our organised editing team contributes to high-quality, accurate data to OpenStreetMap going forward. |
|
| 182975261 | Hi Marvk, thank you for your feedback and clear explanations on what went wrong. We are looking at the issues to carry out the necessary fixes, also addressing the matter internally to make sure our organised editing team contributes to high-quality, accurate data to OpenStreetMap going forward. |
|
| 182974452 | Hi Marvk, thank you for your feedback and clear explanations on what went wrong. We are looking at the issues to carry out the necessary fixes, also addressing the matter internally to make sure our organised editing team contributes to high-quality, accurate data to OpenStreetMap going forward. |
|
| 182966738 | Hi Marvk, thank you for your feedback and clear explanations on what went wrong. We are looking at the issues to carry out the necessary fixes, also addressing the matter internally to make sure our organised editing team contributes to high-quality, accurate data to OpenStreetMap going forward. |
|
| 180391138 | I missed checking Panoramax sequences at that time. Thank you for making the corrections and your feedback. |
|
| 180850794 | Thanks for this context, I understand. We'll perform the edit but also check for similar patterns to see how they are generally reflected in the database. |