piebro/osm-data huggingface dataset:
EllieNyaa (2022-12-06 13:39:39+00:00): Can you please revert this? I disagree with a lot of these classification changes; this over-classifies many local arterials and needs more discussion. The guidelines there aren't really up-to-date and we're working on drafting better classification guidelines at https://wiki.openstreetmap.org/wiki/Michigan/highway_classification; I would encourage you to help with that as the project there has stalled a bit.
wusatosi (2022-12-10 00:10:24+00:00): Hi, EllieNyaa, sorry I have no idea this draft is still going on, I saw as there's no further updates regarding it since September that it is dead.

Can you link me to potential discussions within Michigan mappers regarding this project?

NFC is used by governments, local, regional and state to design their road network and its road geometry. It provides the clearest insight into how a road is intended to be used. It might not reflect the current road geometry & capacity & flow, but it is the most stable source we can reference without doing expansive surveys and having excessive and debates. Basing our classification on NFC is the best approach here IMO and it is what suggested on the current guideline https://wiki.openstreetmap.org/wiki/Michigan#Highway , however I understand our current translation guideline may not be optimal.

Please don't take this personally, I see you as the sole only contributor to the new updated classification guide, and its guideline vague and full of "idea"s, I understand this is a draft, I share your concern but I don't think classifying trunk lines and main roads case by case is a good idea. 

If there is an ongoing discussion among mappers I'd love to have a peak, but if its an on going draft that's going to keep coming in and stalling away for the next few months or years, I am frankly not interested to be stuck in a duality and get nothing done.

The road classification in and around Ann Arbor/ the Southeast Michigan is so random that I thought I should come in and help, I cannot work with your draft right now considering its state, it's a worse choice than what we have right now. 

Yes, over-classification could be a problem, but inconsistent classification is worse. 

Thank you for improving the classification guideline and communicating it to me, but I will not revert my changes just because there is an early draft of the classification guideline. 

However if there is an workable guideline draft, I would love to attempt to implement it in Ann Arbor and to discuss what I think.
EllieNyaa (2022-12-11 14:39:43+00:00): Most of the discussion has taken place on Slack, so few have felt the need to edit that guideline page itself. The particular thread where that discussion was started is here: https://app.slack.com/client/T029HV94T/CCAEPLP33/thread/CCAEPLP33-1662863532.635799

The NFC is really not the correct source of classification to use here. It can be a useful tool but your interpretation is very much overclassifying these roads compared to how classification in OpenStreetMap is intended to be used. Please stop making these edits until you get a consensus to do so.
ivanatora (2022-12-06 07:27:22+00:00): Hello,

Please, commit your work into more localized changesets for ease of managing.

Thanks,
Ivan
mrpulley (2024-02-08 10:10:52+00:00): Just letting you know that the maxspeed is still signposted 80 (not 100) on this road
mrpulley (2024-02-08 10:09:23+00:00): Just letting you know that the maxspeed is still signposted 80 (not 100) on both these roads
pitscheplatsch (2022-12-06 19:14:12+00:00): Hi.

Could you use the comment field of your created changeset for describing your map edits? See https://wiki.openstreetmap.org/wiki/Good_changeset_comments

Thanks.

---
Detected by #SuspiciousOpenStreetMap
https://resultmaps.neis-one.org/osm-suspicious
SiarheiFedartsou (2022-12-06 20:20:42+00:00): Hi, okay probably something is misconfigured in https://maproulette.org/browse/challenges/36475, so it doesn’t add all details. I am the owner of this challenge, so I will try to check what is wrong.
archpdx (2022-12-08 20:54:24+00:00): Hi and welcome to OpenStreetMap! Thanks for adding these addresses. Please note however that we don't use the name field for describing features in OSM (see https://wiki.openstreetmap.org/wiki/Names#Names_are_not_for_descriptions). The information you added in the address field should suffice. 

Also, it looks like you've added that address for 2008 to both the building and as a separate point. I would either remove the point or remove the address data from the building.
mrpulley (2024-06-14 12:27:29+00:00): Ron Banks Road is maxspeed 80 (not 100). Corrected at https://www.openstreetmap.org/changeset/152452243
LockOnGuy (2022-12-06 02:44:04+00:00): Thank you! keep up the good work dear friend. Thank you so much. Best regards to you Sir!
            ---
            #REVIEWED_GOOD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/129759941
mrpulley (2024-01-30 11:22:43+00:00): Just wondering what the "NSW Speed data" source is? I've recently been through here, and The Lakes Way is still maxspeed 80 (not 100). I didn't check Old Soldier's Road on my recent trip, but on Google Street View, it's maxspeed is still 90 (not 100).
Harsimranjit Kaur (2024-01-30 22:47:50+00:00): Hi Mrpulley,
'NSW Speed Data' is the data I get from 'https://opendata.transport.nsw.gov.au/dataset/speed-zones' and 'https://opendata.transport.nsw.gov.au/dataset/road-segment-data-from-datansw'. According to this data, when coming from Pacific Hwy, The Lakes Way is an 80 km/h zone only up until Koorak Place, and the rest of the road is marked as a 100 km/h zone. However, if you have been through the road and are positive that the whole road is an 80 km/h zone, please feel free to update the changes. Thanks
aharvey (2024-02-08 23:06:14+00:00): Hi Harsimranjit,

A few things, if you're only relying on this dataset, then I don't think you should be replacing existing speed limits data in OSM, as how would you know this dataset is correct and OSM is not?

What you could do is use this data to as a hint to check other sources like aerial imagery and street level imagery and then perhaps use this to add a changeset comment to the original contributor.

Third, looking through you're account it appears you're importing this dataset and if so then you must follow the guidelines at https://wiki.openstreetmap.org/wiki/Import/Guidelines
mrpulley (2024-02-14 09:08:33+00:00): Just letting you know that I will be going through your changesets, and doing reversions to many of them (mainly the 'NSW Speed data' ones), because of the above issues. For some changesets, the source isn't clear, so I'll probably ask some questions on those changesets when I come to them. This has been discussed on the talk-au mailing list.
mrpulley (2024-06-14 10:52:12+00:00): You may have noticed that I ended up not reverting any of your changesets at the time. I've checked some of them in-person on my recent holiday. Regarding this changeset, The Lakes Way is definitely maxspeed 80 (as mentioned above). Old Soldiers Road does not have a speed zone sign on survey at either the eastern or the the western end (apart from the 60 zone entering Diamond Beach)
Diógenes de Sinope (2022-12-12 05:28:43+00:00): L'inspection de cette série de changements m'a fait rire : 

Fajita ou Fahita ?

https://www.mapillary.com/app/?pKey=716569475848667&focus=photo&lat=-8.836568240002&lng=13.228439810002&z=17
NorthCrab (2022-12-06 03:35:47+00:00): Hi, it would be a good idea to add some more details to the point - at least the name. It would help massively in future verifications of that place.
aTarom (2022-12-06 09:05:30+00:00): Hola dr_grijando,
se han quedado tags "cmt" sin ningún valor en
https://www.openstreetmap.org/node/10241267740/history
https://www.openstreetmap.org/node/10241267738/history
https://www.openstreetmap.org/node/10241267744/history
Otro tema, en este último, por ejemplo, la elevación del IGN indica 952m en el máximo zoom del visor y con la herramienta de información de coordenadas 951.32m y lo tageado 955m

¿Puedes indicar la fuente de datos que usas?

Saludos y gracias por editar
NunoCapeloCaldeira (2023-01-01 20:05:34+00:00): vandal, fictional data
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.org/changesets/129760633
woodpeck_repair (2023-01-01 20:14:25+00:00): This changeset has been reverted fully or in part by changeset 130762437 where the changeset comment is: reverting edits by touchgrassstudio which were not in line with reality
ybungalobill (2022-12-06 04:59:24+00:00): Hi t2editme,
As fellow editors pointed out to me earlier, OSM uses the 'can it be jumped across' test to distinguish streams versus rivers. I'm re-classifying some of these streams back as rivers, since they fail that test in the majority of their span.
literan (2022-12-06 17:25:36+00:00): Береговая улица следует писать целиком

вернул
Firefishy (2022-12-06 16:29:40+00:00): Thank you for the help mapping Durban.  Please note the name field is only for the name of the building, and in this case this building is not named "added a building to the imagery" ;-) I have fixed all instances. Happy mapping.
maraf24 (2022-12-06 20:54:16+00:00): Piszesz "nazwy rond", a wprowadziłeś nazwy trawnika. Czy one mają nazwy? Nie sądzę.
arichnad (2023-02-15 02:25:28+00:00): Hello whubsch,

I see warnings with this changeset in iD:  thousands of warnings.

I think you maybe duplicated some nodes?  Thanks in advance,

arichnad
whammo (2023-02-15 11:23:19+00:00): Thanks arichnad, no idea how that happened, but they're all deleted now:
https://www.openstreetmap.org/changeset/132576884
arichnad (2023-02-15 16:01:14+00:00): Perfect, thank you.
Hikaruchu (2022-12-13 05:26:40+00:00): I'm not so sure about the copyright status of the Fairfax City OpenGIS data's copyright?

Furthermore some of this information is inaccurate to on the ground real world conditions.
whammo (2022-12-13 12:53:42+00:00): I will look into it, I had presumed the data was public domain but it's possible I was wrong.
antonr (2023-01-02 10:34:55+00:00): Hejsa,

Det ser ud til at du har ført nogle skovveje (fx https://www.openstreetmap.org/way/1118981819) henover det nye hegn (https://www.openstreetmap.org/way/1118981825). Er det meningen? Da jeg var på stedet blokerede det nye hegn for vejene, derfor klippede jeg vejene over.

Mvh
Niels Elgaard Larsen (2023-01-03 18:09:28+00:00): Godt, jeg har fjernet vejene.
Men der må jo være en låge eller anden indgang et sted.
antonr (2023-01-03 19:16:36+00:00): Hegnet er opført i forbindelse med udvidelse af dyreparken, så det giver fin mening for mig at der (endnu) ikke er adgang gennem det...
antonr (2023-01-08 19:54:18+00:00): Det så for mig ud til at du ikke har fået fjernet vejene, så har forsøgt mig med en delvis revert her: https://www.openstreetmap.org/changeset/131028629
balski (2022-12-06 01:38:03+00:00): This is a private building on private property. You had no right to be there, nor to add it to a public map.
eerib (2022-12-06 01:43:55+00:00): Hello balski,

Please refer to my comment on your initial changeset/deletion of this private building.

https://www.openstreetmap.org/changeset/129757190

Thank you - eerib
nevw (2022-12-06 22:30:42+00:00): Hi
Species or taxon is the correct tag for trees instead of giving each a name.
https://wiki.openstreetmap.org/wiki/Tag:natural=tree

Please don't use name in this manner.
https://wiki.openstreetmap.org/wiki/Names
MxxCon (2022-12-07 02:41:01+00:00): What do you think if we name firehouses based on "FacilityName" field from https://data.cityofnewyork.us/Public-Safety/FDNY-Firehouse-Listing/hc8x-tcnd
So that it's consistent across datasets?
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/129761902
MxxCon (2022-12-07 02:47:31+00:00): Hello.
I see that on some ferry routes you added relevant info directly on the way and on some you created relations. It's best if it's consistently done with relations following PTv2 schema.
Additionally, some of the info is duplicated on the way and on the relation. Doing that goes against https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/129761932
julcnx (2026-06-16 03:52:57+00:00): Hi, I migrated the surface=latérite ways in this changeset to surface=laterite: latérite is the French spelling of the same surface, and surface=laterite was approved as the canonical tag on 2026-06-15. More info: https://wiki.openstreetmap.org/wiki/Tag:surface=laterite
Muhmaker (2022-12-09 08:13:48+00:00): Hi. Ich bin im letzten Sommer auch schon mal über die Routen für den Walking-Bus gestolpert. Bei einer sehr flüchtigen Suche im Umfeld der Schule konnte ich nichts finden, dass ich als Wegmarkierung interpretieren würde. Hast du vielleicht schonmal dazu etwas gesehen? Auf der Homepage der Schule steht auch eine Bemerkung, dass das Projekt seit 2019 verwaist ist. Das waren wohl eher virtuelle Routen für den internen Gebrauch nach meinem Eindruck. Ich sehe dass kritisch, dass die wie touristische Wanderrouten in OSM behandelt werden. Ich würde die eher komplett löschen wenn nicht doch noch Wegmarkierungen irgendwo auftauchen sollten.
DeFra85 (2022-12-10 23:14:36+00:00): Nee, ich hatte mich mit denen noch gar nicht auseinander gesetzt. Habe nur gesehen das sie als Route=hiking eingetragen waren und der/diejenige es wohl mit den Relationen in einer Überrelation  nicht so wirklich geschafft hatte.
Das hatte ich behoben und gehofft, dass mit der Umstellung auf Route=foot sie aus den Wanderwegen verschwindet. Pustekuchen xD

Habe mir heute auch mal die Homepage angeguckt und nur die wohl neuen Routen von den ElternTaxi Standorten gefunden. Auf dem Weg zu meinern Eltern heute habe ich die Augen in Graeben-, Garten-, Rosen- und Kisker-Str. offen gehalten: das Logo (https://www.lindenschule-halle.de/wp-content/uploads/Lasst-uns-laufen_Logo_rechteckig.jpg) habe ich NUR an den Halteplätzen für die ElternTaxi gefunden, sonst absolut gaaar nix an Markierung.

Ich denke auch die können weg, ist ja schließlich nichts vor Ort .
Muhmaker (2022-12-16 19:24:53+00:00): Ich habe die alten Walkingbus-Routen und das Netzwerk jetzt gelöscht. Die neuen Wege würde ich nicht erfassen. Sind ja vermutlich nur wenige 100 Meter. Die Eltern-Haltezonen könnte man prinzipiell eintragen. Aber soweit ich mich erinnere gibt es dazu auch noch kein überzeugendes Konzept. Und ich werde auch keins erfinden ;)
Fizzie-DWG (2025-04-10 02:43:23+00:00): DWG revert - undiscussed Organised import from unknown source

https://www.openstreetmap.org/changeset/164748511
willkmis (2024-06-24 08:24:19+00:00): Old changeset I know, but I've just come across this. Are you sure this portion isn't supposed to be HI 2000? I think I saw signs with 2000, and it looks like 200 goes down Kaumana Dr into downtown Hilo. See also wikipedia: https://en.wikipedia.org/wiki/Hawaii_Route_200#Related_route
opendcc (2022-12-06 06:51:28+00:00): Hello and welcome to openstreetmap. May I kindly ask to use meaningful changeset comments (what is changed/added) and to locally restrict your changesets (not covering the half world). Thank you.
map per (2023-01-04 17:03:22+00:00): REVERTED in https://www.openstreetmap.org/changeset/130875196 and https://www.openstreetmap.org/changeset/130875207
elkueb (2022-12-23 09:43:22+00:00): Hallo, du hast hier und in anderen Changesets einige Straßennamen angepasst nach dem Schema "Dr. => Doktor" oder "St. => Sankt". Die Schreibweise entspricht aber soweit ich sehe weder dem was in der basemap steht, noch dem was vor Ort beschildert ist. 
Gibt es einen Grund/Quelle für diese Anpassungen?
hlfan (2022-12-23 13:41:45+00:00): Nach dem OSM-Wiki sollen Straßennamen nicht abgekürzt eingetragen werden, da die Entscheidung über Abkürzung der Namen eigentlich die Software innehat, die leichter abkürzen als Abkürzungen ausschreiben kann.
elkueb (2022-12-23 17:07:23+00:00): Interessant. Ja, nach "If a signpost abbreviates the name to save space, but the name can reasonably be spelled out in full, the name=* should also be spelled out in full." aus https://wiki.openstreetmap.org/wiki/Key:name kann man das so sehen.

Mein Eindruck war aber, dass der Konsens in Österreich da auf "was vor Ort beschildert ist" geht: Weder "St. Pölten" noch der "Dr.-Karl-Renner-Ring" sind ja ausgeschrieben...
hlfan (2022-12-24 13:46:23+00:00): Wenn man bei der Suche nach "Straße Pölten" zur Landeshauptstadt gelangen will, ist das natürlich sinnvoll, sonst bin ich mir da nicht ganz so sicher.

Aber wenigstens ist das computergestützte Abkürzen der Straßennamen zum Rückgängigmachen meiner Änderungen einfacher anzustellen.
elkueb (2023-01-09 11:40:32+00:00): Hab diesbezüglich mal ein Thema im Forum aufgemacht, damit da hoffentlich Einigkeit zwischen allen Mappern entsteht :)
Siehe: https://community.openstreetmap.org/t/strassennamen-in-osterreich/7701
nevw (2022-12-06 22:23:42+00:00): Esri satellite shows these new streets.
hoserab (2022-12-06 05:42:33+00:00): Oh hello again, Michael.

By "fixing" road names it seems you mean that you're simply "unabbreviating" the quadrant suffixes on all named roads in Calgary.

You do know that by convention all street signage and municipal addresses in Calgary always use the two-letter abbreviations, right? The Alberta Land Titles system, the City of Calgary Addressing Bylaw and parcel address database, Canada Post postal codes database... they all use the two-letter abbreviations. You know that even in a colloquial context between Calgarians the quadrant is always written with the two-letter abbreviation, right? 

Just making sure you're aware. As a local, it sure would seem silly to write out "Southwest", "Southeast", "Northwest" and "Northeast" in one's address...
tastrax (2022-12-06 06:35:53+00:00): Its the norm in OSM to spell out full street names including prefix/suffix. I will see if I can find the wiki entry where this is spelt out. There are lots of things that are different in OSM and it takes a while to get the hang of all the subtleties.
hoserab (2022-12-06 19:57:56+00:00): Oh I know precisely what you're talking about tastrax, and absolutely "know the hang of it". You're thinking of https://wiki.openstreetmap.org/wiki/Names#Abbreviation_(don't_do_it).

That said, lots of people don't follow that as gospel because it has issues, particularly in North America. See https://wiki.openstreetmap.org/wiki/Talk:Names#Abbreviation_(don't_do_it)_._Abbreviations_on_street_signs! and http://vidthekid.info/misc/osm-abbr.html.

In particular in Calgary, like I said, nobody would write a road name out in a "full, unabbreviated" form. Justification for doing so on the wiki is "Using short forms is a decision of software; i.e., the underlying data should have the full street name. This will allow a renderer, a router or a location finder to introduce abbreviations as necessary." However, it also says "Apart from following the above rules, *you should always enter the full name as it appears on the street name signs*". You won't find a single street sign in Calgary that spells the quadrant suffix out in full. In fact you sometimes will find them without the quadrant, because it's as much or more about wayfinding and spatial orientation within the city of Calgary as it is "the road's name".

The idea that we spell the quadrants out in full because "some software may not be able to deduce what it means" is a bad idea. The argument boils down to a routing engine with spoken directions may say something like "One Avenue 'Swuh'" because it can't figure out that "SW" = "Southwest" when spoken aloud. That said, when spoken aloud, we NEVER use the cardinal numbers, we always use the ORDINALS. "1 Avenue" spoken aloud is "First Avenue", categorically NOT "One Avenue". Conversely it's written with the cardinal "1", not the ordinal "First". One would never say for instance "I'm at the corner of Fourteen Street Southwest and Seventeen Avenue Southwest", one would say "Fourteenth Street and Seventeenth Avenue Southwest"; notice that the quadrant does not bear repeating, as it is the intersection of 14th St and 17th Ave, located in the southwest quadrant of the city. 

So... one could just leave well enough alone, safe in the knowledge that the rest of the roads in the entire city of Calgary are already tagged "correctly" with the abbreviated quadrants, or one could take it upon themselves to "fix" road names piecemeal where there is no "fixing" to be done and some local mapper will likely come along later and undo this anyway.
Viajero Perdido (2022-12-06 20:41:56+00:00): Edmonton is same. My property tax bill shows the street address as "... NW".  NW *is* the official name.

It took me a while to de-expand the whole city, thanks to that charming import.
hoserab (2022-12-06 20:47:12+00:00): You're making it sound like local mappers actually know what the heck they're doing and talking about, fellow traveller.

Jeez, I don't know, those local yokels...?  :P
Viajero Perdido (2022-12-06 20:53:12+00:00): :)

And there has been peace in Edmonton ever since.
hoserab (2022-12-06 21:06:28+00:00): Ah, but little did you know you Edmontonians are a simpleminded folk who don't know how to name stuff. Ol' Mikey60634 will set you straight, he knows all the official rules.
Friendly_Ghost (2022-12-08 02:18:23+00:00): I would love to see the documentation that hoserab uses to dictate guidelines to others.
Minh Nguyen (2022-12-08 02:48:58+00:00): Hi, I see that Vid the Kid’s old essay about abbreviation was mentioned above. For context, Vid wrote it in 2009 when they and I were among a handful of mappers in the Midwest. Back then, there was serious debate among the U.S. community on the merits of expanding the abbreviations that TIGER used throughout the country. By 2012, those in favor of expansion won out and we expanded all of TIGER’s abbreviations by bot.

Vid used to be very active in the vicinity of Columbus, Ohio. Some of the surrounding counties’ road names indicate the quadrant (e.g., Mink St. SW), and indeed the names can feel pedantic at times. But as you can see from the current map of Fayette and Licking counties in Ohio, we did end up expanding the abbreviations and haven’t looked back.

With the benefit of hindsight, I would say with confidence that the essay no longer reflects consensus and that its conclusion about official names was simply incorrect. However, I very much appreciated Vid’s approach to gaming out the pros and cons of each approach. I hope folks here can coolly arrive at a workable solution.
Friendly_Ghost (2022-12-08 10:14:53+00:00): Thank you for your insights, Minh. I agree that it would be nice if people would come to a conclusion that is not based on outdated documentation.

Slightly off-topic but maybe still interesting: the Dutch community recently discussed addr:street tags with abbreviated names. The preference at https://community.openstreetmap.org/t/addr-street-en-afkortingen-name-of-official-name-volgen-poll/5928/ seems to be leaning towards addr:street tags that match the official names of streets.