OpenStreetMap logo OpenStreetMap

Changeset When Comment
177393986 about 3 hours ago

Hi OleKaysen, 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:
- 20 building(s)

Could you please confirm if these deletions were intentional or if they occurred by mistake?

Looking forward to your response.

#DeletionsCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=177393986

177368176 about 14 hours 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 12 potential crossings.

⚠️️ Problematic elements (top 3):
way/100086054 v16 | 6 crossings
way/696102006 v4 | 6 crossings

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=177368176

177360990 about 17 hours ago

Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain 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.

⚠️️ Problematic element (limit 1):
node/13446564315 v2

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Cake shop on Beach Road Kollam"

#MapWithoutSpam

177356069 about 17 hours ago

Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain 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.

⚠️️ Problematic element (limit 1):
node/10861784825 v4

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Beauty salon"

#MapWithoutSpam

177352320 about 17 hours ago

Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain 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.

⚠️️ Problematic element (limit 1):
node/13457717788 v3

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Fachhändler für alkoholfreie Getränke"
---
Zum Beispiel könnte eine neutralere und sachlichere Version deines Textes lauten: "Fachhändler für alkoholfreie Getränke"
---
(Auto-translation)

#MapWithoutSpam

177344285 about 17 hours ago

Hello, welcome and thank you for your contribution to OSM!

Your changeset was commented because your added description, note or slogan contain 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.

⚠️️ Problematic element (limit 1):
node/13462566128 v2

Could you please revise your text accordingly?

✅ For example, a more neutral and factual version of your text could be: "Math tutoring center for students"

#MapWithoutSpam

177356622 about 17 hours 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 15 potential crossings.

⚠️️ Problematic elements (top 3):
way/1308540270 v2 | 15 crossings

⚠️ Dragged Nodes (max 3):
node/12117867451 v2
node/12117867452 v2
node/12117867453 v2

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=177356622

177354389 about 17 hours 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 25 potential crossings.

⚠️️ Problematic elements (top 3):
way/315335167 v4 | 11 crossings
way/887595820 v5 | 8 crossings
way/1201356026 v1 | 6 crossings

⚠️ Dragged Nodes (max 3):
node/3214459999 v2
node/11135761752 v2
node/11138340154 v2

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=177354389

177348406 about 17 hours 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):
way/530833722 v4 | 10 crossings
way/742399852 v4 | 9 crossings

⚠️ Dragged Nodes (max 3):
node/6950354766 v5

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=177348406

177345402 about 17 hours 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 129 potential crossings.

⚠️️ Problematic elements (top 3):
way/1462620500 v6 | 25 crossings
way/1462629126 v3 | 24 crossings
way/1462851260 v2 | 24 crossings

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=177345402

177335210 about 17 hours 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 63 potential crossings.

⚠️️ Problematic elements (top 3):
way/1462322186 v13 | 21 crossings
way/1462572531 v7 | 19 crossings
way/1462847132 v2 | 12 crossings

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=177335210

177335013 1 day 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 38 potential crossings.

⚠️️ Problematic elements (top 3):
way/95891683 v12 | 9 crossings
way/1018364828 v2 | 9 crossings
way/1018796885 v10 | 11 crossings

⚠️ Dragged Nodes (max 3):
node/1111087198 v5
node/9392965456 v2

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=177335013

177333067 1 day 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 10 potential crossings.

⚠️️ Problematic elements (top 3):
way/1018756786 v3 | 3 crossings
way/306021662 v8 | 7 crossings

⚠️ Dragged Nodes (max 3):
node/1748929804 v2

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=177333067

177321474 1 day 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 48 potential crossings.

⚠️️ Problematic elements (top 3):
way/825935300 v4 | 9 crossings
way/894102318 v1 | 8 crossings
way/894102316 v1 | 8 crossings

⚠️ Dragged Nodes (max 3):
node/2189279140 v6
node/8310098130 v2

Would you mind revisiting those areas?

#CrossingCheck
---
https://resultmaps.neis-one.org/osm-change-viz?c=177321474