piebro/osm-data huggingface dataset:
TiffanyArpi (2025-10-16 14:49:55+00:00): Apologies. New user here. I updated the Playground to follow OSM tag/key rules. "ADA_acs" was not compatible with these rules. Should I include source tag as well for "sensory_friendly" and "wheelchair" (source:sensory_friendly=NYC Parks Open Data).
user_5359 (2025-10-16 16:15:30+00:00): I admit that I find it difficult to translate the meaning of ‘sensory-friendly’ into the necessary conditions for the playground, but your suggestions are a much better choice of keywords. Thank you for your understanding. 

By the way, are you familiar with the wiki (https://wiki.osm.org, including https://wiki.osm.org/wiki/Tag:leisure%3Dplayground) and/or the forum (https://community.osm.org), where you can also find and detail suggestions and ideas for mapping possibilities?
zorun (2025-10-29 22:03:38+00:00): Bonjour,

Merci pour votre contribution, mais l'adresse est maintenant incohérente avec la position du point.

Il faut que vous supprimiez ce point et en recréez un nouveau au nouvel emplacement. Ou éventuellement déplacer le point si c'est pas trop loin.
eggie (2025-10-16 13:39:22+00:00): Welkom bij OSM,

Alleen een naam zal niets doen in OSM.
Wellicht even hier kijken?
https://wiki.openstreetmap.org/wiki/Tag:amenity%3Devents_venue

MVG
eggie
SomeoneElse (2025-11-16 20:12:31+00:00): Hello,
What made you think that https://www.openstreetmap.org/way/304255640/history was an unclassified road?
rarad74 (2025-10-16 18:58:25+00:00): Salut inca odata. Te rog NU mai modifica CE ESTE CORECT si unde nu stii! Nu ai de ce sa adaugi turn lanes:forward pe un segment  in care directia liniei este invers sensului de mers si unde deja exista turnlanes:backward. Corect este cum era deja pe harta cu turnlanes:backward. La directiile pentru turn lanes se tine cont de directia reala a liniei strazii. Daca dai zoom mai aproape o sa vezi ca apar niste sageti mici de sens pe segmentele oricaror linii de pe openstreetmap. Daca directia la turnlanes este aceeasi cu directia sagetilor de sens atunci se pune forward. Daca directia este invers fata de sagetile de sens se pune backward. Daca tot nu ai inteles, putem discuta pe mail sau citeste documentatia wiki. ai aici link: https://wiki.openstreetmap.org/wiki/Forward_%26_backward,_left_%26_right
Radu Silveanu (2025-10-27 18:13:00+00:00): Buna seara, multumesc pentru mesaj si pentru link.  Este greseala mea.  Imi cer iertare.  Imi cer iertare si pentru raspunsul intarziat.
Baloo Uriza (2025-10-29 21:04:29+00:00): No, this isn't a building.  Accuracy matters.
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/173367931
Mateusz Konieczny (2025-10-22 17:42:41+00:00): reverted edits that added suspect names, it is from a suspect account, as https://www.openstreetmap.org/changeset/166617410 and https://www.openstreetmap.org/changeset/164649036 remain not answered

https://www.openstreetmap.org/changeset/173640162
ilias_ (2025-12-13 00:06:07+00:00): Hi nona mostafa,

This is actually not a road in construction but an extra railway in construction. See https://scontent.fmad22-1.fna.fbcdn.net/v/t39.30808-6/599588699_1336077858318723_3484377484770537088_n.jpg?_nc_cat=107&ccb=1-7&_nc_sid=833d8c&_nc_ohc=yNNhk6JD8mcQ7kNvwFIrHZ_&_nc_oc=AdkmFjf2NdwmD07wt3rrFxv5Oc4bPHzdFt_YRb1mkX_vTZyfkH2YW-Cm7p7LF5CPlQc&_nc_zt=23&_nc_ht=scontent.fmad22-1.fna&_nc_gid=QsROFeCS7h2zepquFWrkhA&oh=00_AfkLIEMA2AVf1T4wNrWhS4OSRkcCu3780oTcIDRQrkW-Hg&oe=6942947E
nona mostafa (2025-12-16 08:03:35+00:00): Hi Ilias,
Thanks for letting me know. Feel free to fix that based on your local knowledge, because my source is relatively old.
Thanks again.
nona mostafa
andrew-m8387 (2025-10-29 20:58:56+00:00): Boy, put my road back
JessAk71 (2026-03-20 17:56:07+00:00): Hello, it looks like you may have accidentally added a building tag to this area, the entire area is not a building so it should not have a building tag, instead it should have the poi type tag to represent the business such as a specific amenity. I have removed the building tag for you here but please be careful in future edits when using the building tag so that only specific structures have a building tag not an entire business area.
NorthCrab_upload (2025-10-16 16:32:02+00:00): Zauważyłem, że Twoja zmiana zawiera adresy wymagające dodatkowej uwagi. Przygotowałem listę obiektów oraz dodatkowe informacje:

Nazwa ulicy nie istnieje w okolicy. Jeśli adres ma nazwę ulicy, upewnij się, że jest ona poprawna. Jeśli nie, usuń addr:street, a nazwę miejscowości przekaż w addr:place.
https://www.openstreetmap.org/way/675528241

Dokumentacja adresów (po polsku):
https://wiki.openstreetmap.org/wiki/Pl:Key:addr:*

W razie problemów lub pytań, proszę pisać. Chętnie pomogę.
Pozdrawiam! 🦀
SpinOff (2025-10-17 23:56:01+00:00): Nazwa "Bunkier dla mieszkańców Okolicy" nadana ruinom bunkra? To brzmi jak opis, ale co lokalni mieszkańcy mają wspólnego z tym bunkrem?
Mateusz Konieczny (2025-10-22 17:42:13+00:00): reverted edits that added suspect names, it is from a suspect account, as https://www.openstreetmap.org/changeset/166617410 and https://www.openstreetmap.org/changeset/164649036 remain not answered

https://www.openstreetmap.org/changeset/173640136
ilias_ (2025-10-16 16:17:57+00:00): Reverted for vandalism

https://www.openstreetmap.org/changeset/173374543
Kovoschiz (2025-10-17 07:13:38+00:00): Speed limit isn't the same as train speed. The latter is affected by headway, and timetabling. You should only use real speed limits, signposted or codified rules.
Wetitpig0 (2025-10-17 07:46:15+00:00): I am aware of this. These data are based on trackside signposts. GPS data is mainly for verification.
FMC-Henri (2025-11-07 15:16:17+00:00): Hallo,

wieso wurde https://www.openstreetmap.org/way/1414065082 zur highway=service? Das scheint mir nicht korrekt zu sein. Könntest du dir das nochmal anschauen?

Danke und Grüße
Henri
fmc_Mlvln (2025-11-10 11:23:59+00:00): Ich nehme an das war ein Copy-Paste-Fehler. Ich habe es korrigiert.
LG fmc_3/Mlvln
Enock4seth (2025-11-30 15:54:17+00:00): Hi and welcome to OpenStreetMap, this changeset did not make OpenStreetMap better. Please if you are not sure of what you are doing do not upload your changes to OpenStreetMap. Here is what OpenStreetMap is about https://welcome.openstreetmap.org/
NeisBot (2025-10-16 17:06:23+00:00): Hi atlas2004, welcome and thanks for your contribution!

To make collaboration easier and help others understand your edits, it’s best to add a short description of the changes you made. Clear comments help the community follow your work and provide better feedback. You can find tips on writing good comments here[1].

Based on your map edits in this changeset, I’ve drafted a suggestion for what a comment could look like: "Updated height to 10"
---
[1] https://osm.org/wiki/Good_changeset_comments
user_5359 (2025-10-22 08:58:35+00:00): Hello! What is the mean of the tags
currency:ALPH=yes
currency:ATOM=yes
currency:DASH=yes
currency:EPIC=yes
currency:ETH=yes
currency:FIRO=yes
currency:KAS=yes
currency:LTC=yes
currency:NAM=yes
currency:XMR=yes
currency:ZANO=yes
?
Please notice we use the standard ISO 4217 for the short cuts.
NeisBot (2025-10-16 14:56:44+00:00): Привет Maloj85, добро пожаловать и спасибо за ваш вклад!

Чтобы сделать сотрудничество проще и помочь другим понять ваши правки, лучше добавить краткое описание сделанных изменений. Ясные комментарии помогают сообществу следить за вашей работой и предоставлять более лучшие отзывы. Вы можете найти советы по написанию хороших комментариев здесь[1].

На основе ваших правок карты в этом наборе изменений, я составил предложение о том, как мог бы выглядеть комментарий: "Добавлена тропа"
(Auto-translation)
---
Hi Maloj85, welcome and thanks for your contribution!

To make collaboration easier and help others understand your edits, it’s best to add a short description of the changes you made. Clear comments help the community follow your work and provide better feedback. You can find tips on writing good comments here[1].

Based on your map edits in this changeset, I’ve drafted a suggestion for what a comment could look like: "Added path"
---
[1] https://osm.org/wiki/Good_changeset_comments
magnode (2025-10-17 07:07:03+00:00): Underground yard tracks are poorly supported, and the result is messy.

https://www.openstreetmap.org/changeset/173395480
Noen (2025-10-20 18:51:48+00:00): Hei, 
underjordiske anlegg er godt støttet i Openstreetmap. OSM er ikke først og fremst bare ett kart, det er også dataene og verktøyene rundt, og det er mer enn en måte å vise frem kartdataene på.
Siden du har redigert jernbane tidligere, kjenner kanskje til et godt eksempel, Openrailwaymap.
Hvis du syns fjellstallen ikke vises på noen god måte i standardkartet, går det an å komme med forslag til hva man kunne gjort annerledes på Github.
https://github.com/gravitystorm/openstreetmap-carto/issues
Hvis du ønsker gjenoppretter jeg gjerne bidraget ditt.
AndyB_66 (2025-11-10 15:04:17+00:00): https://wiki.openstreetmap.org/wiki/Pl:Dobre_komentarze_zestawu_zmian
CRCulver (2025-10-19 23:49:45+00:00): If you replace a single stop node at an intersection with separate nodes marked direction=forward/backward, then please make sure you copy over the stop=all tag. Your edit at 33.83208, -117.5648 deleted the information that that every stop sign represents an all-way stop.
MacOSMapper (2025-10-20 00:36:14+00:00): Hello @CRCulver, thanks for the feedback.

Can you provide a link to where I can get additional info about this, or where I can find an example as you've described?

To me it made sense to remove the tags on the node where the ways intersect since that's not where the the stop signs are actually located. It's not clear to me if you are suggesting to put the stop=all tags on the node of the intersecting ways, or on the stop sign nodes. Either way, I'd appreciate some additional detail.

I understand that deleting data is not the default approach. But leaving any tags on the intersecting node seemed incorrect to me after I split the stop signs into their own separate nodes to add detail.

Thanks!
CRCulver (2025-10-20 00:49:34+00:00): The stop=all tag should be added to the new individual highway=stop nodes you created, and deleted from the node of the intersecting ways.
MacOSMapper (2025-10-20 01:14:46+00:00): Thanks for the quick reply @CRCulver.

It makes sense to me to remove the tags from the node of the intersecting ways. We're good there.

It's still not clear to me why having stop=all on the individual stop sign nodes would be expected since they are already tagged with direction=forward/backward.

My perspective (which could be wrong) is that it would be incorrect to tag them with stop=all based on the direction tags.

If you could provide a link to information that explains the approach you suggested I would appreciate it.

I'm wondering if there is an implied "it's better to keep the stop sign at the node where the ways intersect" in your feedback??? My goal with this change was to add more detail to the map as I've been mapping sidewalks and crossings. My understanding was that it was preferred to have the stop sign as a node where vehicles/cycles would need to stop since they don't actually stop in the middle of the intersection but before the crossings.

Thanks again!
CRCulver (2025-10-20 01:24:19+00:00): Your approach of adding individual stop-sign nodes at the stop positions for greater precision is perfectly sound, no complaints there. But even if the new nodes are tagged for direction=forward/backward, that tells nothing of whether the trajector along one of the ways is reaching an all-way stop or a stop that affects only the minor ways, hence the stop=all tag remains a useful piece of information to describe the intersection. You can see that this is commonly done by doing an Overpass API query.

You can do an Overpass
MacOSMapper (2025-10-20 20:26:04+00:00): It looks like part of of your reply got cut off but I was able to dig into Overpass a bit. Thanks.

I've made some changes, please see this changeset:
https://www.openstreetmap.org/changeset/173554932

As I was searching for examples I noticed that in that same area there are some stop signs that you have edited that don't have the `stop=minor` tag. I'm assuming those should be tagged similar to the four way stops where you suggested `stop=all`. My changeset includes a couple/few stop signs where I added `stop=minor` with that assumption.
kamilbogacki (2025-10-16 15:10:51+00:00): https://www.portalspozywczy.pl/handel/wiadomosci/dino-w-warszawie-to-nie-tylko-wilanow-na-pradze-polnoc-trwaja-juz-prace,281736.html
Pich14 (2025-10-17 00:08:35+00:00): La cancha que agregaste en el SUPE ya no existe, por eso la eliminé y puse una zona en construcción que es lo que hay actualmente ahí ya que se están construyendo casas. Las imágenes de Esri fueron actualizadas por última vez en 2023, por lo que ya son viejas. Te invito a que veas esa zona en Google Maps y vas a ver que es así. Se supone que hay que mapear lo actual y no lo que ya no está.
Diego Krein (2025-10-17 10:39:50+00:00): Muchas gracias por la corrección. Está perfecto. Es así, hay que mapear lo actual.
Andrea Musuruane (2025-10-17 06:56:41+00:00): Ciao. Faccio fatica a capire il motivo del cambio dei nomi delle strade. Ad esempio da "Via Sabotino" a "Via Monte Sabotino". La strada si chiama nel primo modo. Non e' che "Via Po" a Torino si chiama "Via Fiume Po" (!!). Ciao, Andrea
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/173371674
NeisBot (2025-10-16 16:26:34+00:00): Hi clare7, welcome and thanks for your contribution!

To make collaboration easier and help others understand your edits, it’s best to add a short description of the changes you made. Clear comments help the community follow your work and provide better feedback. You can find tips on writing good comments here[1].

Based on your map edits in this changeset, I’ve drafted a suggestion for what a comment could look like: "Added Chinese cuisine, website, and opening hours details"
---
[1] https://osm.org/wiki/Good_changeset_comments
NeisBot (2025-10-16 15:36:40+00:00): 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
NeisReview (2025-10-18 11:00:34+00:00): 👍 Thank you for updating the element https://osm.org/changeset/173372745
user_5359 (2025-10-17 07:57:44+00:00): Welcome to OSM! Please be careful! You moved the node https://www.osm.org/node/9810207421 more than 100 meters over streets and buildings. 
I moved the node back to the original position.
watmildon (2025-12-12 23:01:13+00:00): Hello!

What's the story with the one_way tag on this waterway? It's somewhat curious and I would love to know more.

https://www.openstreetmap.org/way/956194416/history#map=16/43.06842/-86.21916
Trail_Caretaker (2025-12-12 23:18:17+00:00): No story.  I don't understand what you mean by story?
watmildon (2025-12-12 23:31:46+00:00): Oh, it was marked by you as oneway= and I was curious to learn more. It's an unusual tag on a waterway. If it's a mistake then I'll tidy it up, if it has a real purpose I would love to hear about it. 

I found it because the whole waterway was pointed upstream causing a loop in the waterflow graph. I have reversed that part but figured I'd ask about the other.
Trail_Caretaker (2025-12-12 23:51:49+00:00): Streams and rivers by default are tagged directional to the direction that you draw them.  If they have flow they should have a direction.  If you check out any river or stream line drawn on OSM you wilI find a direction of flow.  I am still not sure of your question.
Trail_Caretaker (2025-12-13 14:38:41+00:00): I went to the item you were mentioning and see what you mean now.  I removed the oneway tag.  If I remember correctly, that small portion of the Grand River had no direction of flow indicated or the incorrect direction of flow on the map.
watmildon (2025-12-13 19:47:26+00:00): Ah gotcha. It looks in a decent state now. Thanks for looking into it!

I originally found it looking at the QA layer on WaterWayMap for "loops" in waterway directions. The US is mostly tidied up but it's always interested to see where the smaller defects are https://waterwaymap.org/loops/#map=2/0/0
Trail_Caretaker (2025-12-13 21:51:49+00:00): Thanks for catching that.  I enjoy paddling and like the waterways to be accurate, for myself and the paddling community.  There are a lot of water trails in Michigan that need map help.  I have been reading and watching seminars on how to map them properly but have only reached the tip of the iceberg.  A lot of it is above my head.
watmildon (2025-12-13 22:14:07+00:00): Oh my goodness yes. There's an infinite well of things to learn and map and a million little pitfalls.

Connectivity for paddling around and routing folks is still relatively knew so I expect there's a lot of great work to be done. :-D
eggie (2025-10-16 17:41:37+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privebericht.
Feedback  Het vpad is niet verbonden met de HC de Jonghweg.
Alleen aan het fietspad. Bij een pad moet je denken aan een (smal ) paadje.
Zal het wellicht een highway=track zijn? Dus geschikt voor 4 wiel voertuigen? 
Accesstags zijn lastig. Deze spreken elkaar allemaal tegen.
Iets kan zijn bv algemeen access=private(routeert niet)  of permissive (routeert wel)

Eggie
Namens de OSM Community
eggie (2025-10-16 17:54:45+00:00): Ik heb het aangepast naar een track ipv path en algemeen access=private toegevoegd. 
toegangsweg ook doorvebonden met hoofdrijbaan. 
Het gebouw heb ik hersteld. Op grond van luchtfoto's svp geen gebouwen aanpassen. 
Je edits https://overpass-api.de/achavi/?changeset=173373955
MVG
eggie
Wanneer hier een bord staat Alleen toegang voor bewoners zou het destination zijn.
Al die andere accesstags zijn niet nodig.

Mocht het 'moeten'kunnen routeren voor hulpdiensten dan emergency=yes toevoegen op het hek en de track.
Dan zal het hek wel geopend moeten kunnen worden door bv de brandweer.

MVG
eggie
tastrax (2025-10-17 09:08:14+00:00): Hi folks FYI - Phone numbers in Australia should be added to OSM according to the following format with the country and regional code +61 x xxxx xxxx, +61 xxx xxx xxx for mobiles or use the phone:AU key if a 1300 or 1800 number.
For freecall numbers that work whilst overseas (ie 13 13 13) use +61 XX XX XX as per the wiki guidelines https://wiki.openstreetmap.org/wiki/Australian_Tagging_Guidelines/Australian_features#Phone_Numbers .  I have just updated a recent addition that you made to OSM – Cheers
Hwerhwette (2025-10-17 09:58:11+00:00): Thanks for letting me know tastrax. I'll have to go back and fix the formatting for some previous telephone numbers I added - but I'll be sure to format them according to the guidelines from now on (same goes for the state abbreviations). Cheers.
Hwerhwette (2025-10-17 15:19:00+00:00): Nevermind, I see that you've fixed them all. Thank you!
bartgron (2025-10-19 21:23:51+00:00): NIE DODAJEMY TAKICH OPISÓW!!!
NeatNit (2025-10-16 20:51:17+00:00): שלום, ותודה על שאתה תורם למפה!

רוב החלקים של השביל כבר קיימים במפה, ויותר מפורטים ומדוייקים ממה שהוספת. למה החלטת להוסיף את השביל?

מכיוון שזה נראה כמו טעות אני מחקתי את מה שהוספת: https://www.openstreetmap.org/changeset/173384263

אם זו לא הייתה טעות, בבקשה תפרט מה ניסית לעשות
AndyB_66 (2025-10-17 15:37:31+00:00): Po raz kolejny proszę - stosuj się do zasad, obowiązujących w społeczności OSM: https://wiki.openstreetmap.org/wiki/Pl:Dobre_komentarze_zestawu_zmian
Mateusz Konieczny (2025-12-19 09:16:01+00:00): Hello! https://www.openstreetmap.org/way/33189267/history has sidewalk:right = both that was added in this edit
so left or right or both?
Max-Kritic (2025-12-19 10:36:59+00:00): Je irai voir pour corriger l'erreur. Merci
Superadlen (2025-10-20 12:34:45+00:00): merci
AndyB_66 (2025-10-17 15:36:51+00:00): Po raz kolejny proszę - stosuj się do zasad, obowiązujących w społeczności OSM: https://wiki.openstreetmap.org/wiki/Pl:Dobre_komentarze_zestawu_zmian
Matt McCutchen (2025-10-16 17:05:52+00:00): The entry restrictions at East Jefferson Street are mapped separately.  In a survey, I saw no evidence of an access restriction along the segment of Rollins Avenue.
SomeoneElse2 (2025-10-31 21:59:37+00:00): You introduced a couple of typos here "yesx" - I've fixed them to "yes".
VLD318 (2025-11-03 17:11:12+00:00): Hi SomeoneElse2. Thank you for catching this typo and making the change.
bartgron (2025-10-19 21:22:37+00:00): Nie dodajemy nazw "nieformalne przejście kolejowe"
user_5359 (2025-10-17 07:53:31+00:00): Hello! It is not allowed to copy data from Google maps!
Flap Slimy Outward (2025-10-17 17:00:25+00:00): I also used the website provided. Basically, this node with barely any tags attached to it was moved to its proper location, so I added an address. I used Google Maps for those two, but I used the website (which is uh, interesting to say the least) for everything else.
marc__marc (2026-01-26 23:09:50+00:00): Bonjour,
Merci pour cet ajout.
pour info Arecaceae n'est pas une espèce d'arbre mais une famille.
cela se renseigne avec
taxon=Arecaceae
éventuelement aussi leaf_type=broadleaved
Bonne continuation dans la cartographie
streckenkundler (2025-10-16 19:30:40+00:00): Hei,

Uhi... Das ist ganz in meiner Sichtweise! Vielen Dank... 

Hast du Lust noch mehr solcher Dinger zu bereinigen?  Anbei eine adaptierte Abfrage aus meinem Fundus, adaptiert für Sachsen: https://overpass-turbo.eu/s/2dOm

Die Abfrage zeigt alle Reationen mit type=multipolygon, dann Elemente mit role=outer >=2. Elemente mit der Rolle inner können sein, müssen aber nicht.
Bahnsteigrelationen und Solarfelder habe ich da auskommentiert.

Dickes Danke! 

Das erinnert mich, Brandenburg mal wieder durchzusehen...

Sven
kalupner (2025-10-17 06:03:17+00:00): Hallo Sven,
wenn ich Zeit und Lust habe werde ich mir weitere MP's vornehmen. Danke für deinen Link.
VG Karl
SpinOff (2025-10-17 23:53:47+00:00): Wydaje mi się mało prawdopodobne by okresowy strumyk tej wielkości miał nazwę. Jakie jest żródło tych danych?
Mateusz Konieczny (2025-10-22 17:41:41+00:00): reverted names from suspect account, as https://www.openstreetmap.org/changeset/166617410 and https://www.openstreetmap.org/changeset/164649036 remain not answered

https://www.openstreetmap.org/changeset/173640119
FroschForscher (2025-10-18 09:44:44+00:00): Hallo cosphi,
für die Erfassung einer 30er Zone fehlt noch zone:maxspeed=DE:30. Vgl. älteren Teil der Storchenstraße.

FroschForscher

PS: https://wiki.openstreetmap.org/wiki/DE:Good_changeset_comments
cosphi (2025-10-18 18:39:48+00:00): Ist doch da oder hast du das eingetragen?
FroschForscher (2025-10-18 20:34:55+00:00): Am "neuen" Teil der Storchenstraße und am Brachvogelweg ist nur `maxspeed=30` gesetzt, ohne `zone:maxspeed=DE:30`. Es sind also zwei Eigenschaften nötig damit es eine 30er *Zone* ist.
(Ich gehe davon aus das die 30er Zone fortgeführt wird.)
cosphi (2025-10-19 07:25:16+00:00): zone:maxspeed eingetragen. Das kannte ich tatsächlich noch nicht. Vielen Dank für den Hinweis.
Schönes Wochenende
cosphi (2025-10-19 07:27:17+00:00): Ih weiß wie das passiert ist - Ich habe das mit der App "Go Map!!" gemacht. Die App hat angezeigt dass die max. Geschwindigkeit fehlt. Die App ist sowas wie StreetComplete für Android.
OnlyAppleCanDo (2025-11-05 13:02:28+00:00): 按照 道路等级 和 珠海市城市快速路系统提升规划 这条路应该是 trunk。

按照珠海市城市快速路系统，这条路是珠海市的二级快速路。

无论是技术标准还是政府文件都不应该是primary，这条路而且还是全立交道路......
LokNeko (2025-11-05 15:49:51+00:00): 根据珠海市声环境功能区区划，此路属主干路。
再者，没必要完全按照文件规划来，这样太死板了，正如双向四车道限速60的兴业快线，给个快速路，实在是辣眼睛。应该灵活设置，南湾路军区以南区域是双向6车道，给个Primary比较合适，军区以北有双向8车道的立交桥，可以给trunk，不一定一条路只能有一个道路等级，灵活来。
anpk (2025-10-16 18:23:24+00:00): Фото будущего съезда: https://vk.com/wall-177763215_1978
eggie (2025-10-16 18:51:14+00:00): Dag E.. In dat geval kun je beter de bedrijfsinfo verwijderen en shop=vacant taggen.
Mvg
eggie