NeisBot's Comments
| Changeset | When | Comment |
|---|---|---|
| 175291494 | about 2 months ago | Hi DFace Peter, welcome to OSM! Thank you for your contributions to the map. I have reviewed your recent edits and noticed that 100% of the changes in this set involve deletions, including:
Could you please confirm if these deletions were intentional or if they occurred by mistake? Looking forward to your response. #DeletionsCheck
|
| 175253277 | about 2 months ago | Hello, welcome to OSM! Thank you for your contributions to the map. I have reviewed your changesets and noticed that the cumulative count of your recent edits (2 changesets) shows that 627 of your last 741 changes were deletions. This is quite an unusual proportion, so I wanted to check with you. Could you please confirm whether these deletions were intentional or if they may have occurred by mistake? #DeletionsCheck #Cumulative
|
| 175253294 | about 2 months ago | Hi Obojzivelnik, welcome to OSM! Thank you for your contributions to the map. I have reviewed your recent edits and noticed that 100% of the changes in this set involve deletions, including:
Could you please confirm if these deletions were intentional or if they occurred by mistake? Looking forward to your response. #DeletionsCheck
|
| 175253134 | about 2 months ago | Hi Obojzivelnik, welcome to OSM! Thank you for your contributions to the map. I have reviewed your recent edits and noticed that 99% of the changes in this set involve deletions, including:
Could you please confirm if these deletions were intentional or if they occurred by mistake? Looking forward to your response. #DeletionsCheck
|
| 175059312 | about 2 months ago | Welcome, and thanks for your edits! I noticed a few unintended crossings between roads and/or between roads and buildings in this changeset. This usually happens when geometry snaps incorrectly. Additionally, changes to tagging (e.g. modifying highway types or adding tags) can lead to unexpected crossings being detected afterwards. In total, I detected 27 potential crossings. Problematic elements (top 3 by category):
Dragged Nodes (max 3):
Would you mind revisiting those areas? #CrossingCheck
|
| 175058193 | about 2 months ago | For example, a more neutral and factual version of your description could be: "Custom PC builder in Bangalore" |
| 175058193 | about 2 months ago | Hello, welcome and thank you for your contribution to OSM! Your changeset was commented because your added description or slogan contains detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language. Could you please revise your description accordingly? #MapWithoutSpam #Tags #Description |
| 175057724 | about 2 months ago | For example, a more neutral and factual version of your description could be: "Event planning company in Chino CA" |
| 175057724 | about 2 months ago | Hello, welcome and thank you for your contribution to OSM! Your changeset was commented because your added description or slogan contains detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language. Could you please revise your description accordingly? #MapWithoutSpam #Comment #Description |
| 175056142 | about 2 months ago | Welcome, and thanks for your edits! I noticed a few unintended crossings between roads and/or between roads and buildings in this changeset. This usually happens when geometry snaps incorrectly. Additionally, changes to tagging (e.g. modifying highway types or adding tags) can lead to unexpected crossings being detected afterwards. In total, I detected 43 potential crossings. Problematic elements (top 3 by category):
Would you mind revisiting those areas? #CrossingCheck
|
| 175055885 | about 2 months ago | Welcome, and thanks for your edits! I noticed a few unintended crossings between roads and/or between roads and buildings in this changeset. This usually happens when geometry snaps incorrectly. Additionally, changes to tagging (e.g. modifying highway types or adding tags) can lead to unexpected crossings being detected afterwards. In total, I detected 19 potential crossings. Problematic elements (top 3 by category):
Dragged Nodes (max 3):
Would you mind revisiting those areas? #CrossingCheck
|
| 175055188 | about 2 months ago | Hi salee3, welcome to OSM! Thank you for your contributions to the map. I have reviewed your recent edits and noticed that 97% of the changes in this set involve deletions, including:
Could you please confirm if these deletions were intentional or if they occurred by mistake? Looking forward to your response. #DeletionsCheck
|
| 175053754 | about 2 months ago | For example, a more neutral and factual version of your description could be: "Security systems company in Calgary Alberta" |
| 175053754 | about 2 months ago | Hello, welcome and thank you for your contribution to OSM! Your changeset was commented because your added description or slogan contains detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language. Could you please revise your description accordingly? #MapWithoutSpam #Tags #Description |
| 175053104 | about 2 months ago | Hi crazymacattacks, welcome to OSM! Thank you for your contributions to the map. I have reviewed your recent edits and noticed that 83% of the changes in this set involve deletions, including:
Could you please confirm if these deletions were intentional or if they occurred by mistake? Looking forward to your response. #DeletionsCheck
|
| 175043291 | about 2 months ago | Welcome, and thanks for your edits! I noticed a few unintended crossings between roads and/or between roads and buildings in this changeset. This usually happens when geometry snaps incorrectly. Additionally, changes to tagging (e.g. modifying highway types or adding tags) can lead to unexpected crossings being detected afterwards. In total, I detected 13 potential crossings. Problematic elements (top 3 by category):
Dragged Nodes (max 3):
Would you mind revisiting those areas? #CrossingCheck
|
| 175052392 | about 2 months ago | For example, a more neutral and factual version of your description could be: "Telecom site marketing company" |
| 175052392 | about 2 months ago | Hello, welcome and thank you for your contribution to OSM! Your changeset was commented because your added description or slogan contains detailed text that may be interpreted as promotional or SEO-related. To ensure OSM remains neutral and focused on map data, I recommend keeping descriptions concise, factual, and free from marketing or promotional language. Could you please revise your description accordingly? #MapWithoutSpam #Comment #Description |
| 175050739 | about 2 months ago | Welcome, and thanks for your edits! I noticed a few unintended crossings between roads and/or between roads and buildings in this changeset. This usually happens when geometry snaps incorrectly. Additionally, changes to tagging (e.g. modifying highway types or adding tags) can lead to unexpected crossings being detected afterwards. In total, I detected 21 potential crossings. Problematic elements (top 3 by category):
Dragged Nodes (max 3):
Would you mind revisiting those areas? #CrossingCheck
|
| 175050489 | about 2 months ago | For example, a more neutral and factual version of your description could be: "Aesthetics and wellness center in Newport Beach CA" |