piebro/osm-data huggingface dataset:
Leo Slager (2018-12-13 15:30:32+00:00): Lijkt mij geen goed idee. In het forum wordt gesteld dat al deze verouderde codes kunnen worden verwijderd !
Ze worden vervangen door 1 landelijke code.
https://forum.openstreetmap.org/viewtopic.php?id=34039
IDeate (2018-12-14 14:07:49+00:00): Ah je bedoelt die ref:IFOPT. Ja die kan ik inderdaad ook pakken. Ik had geen idee dat er twee verschillende waren. Deze haltes heb ik nieuw toegevoegd en ik had gekeken hoe de dichtstbijzijnde al bestaande halte eruit zag.
Leo Slager (2018-12-14 14:32:16+00:00): Inderdaad, Sint E7 is kennelijk bezig om dat over heel nL uit te rollen.
Misschien kun je met hem contact opnemen ?
IDeate (2018-12-14 14:39:13+00:00): Als ik het zo zie is het model vrij eenvoudig. Het is gewoon NL:Q: en dan de standaard haltecode die ik al opgenomen had. Dat kan ik zo even veranderen.
mavl (2019-02-24 17:37:27+00:00): This changeset was redacted.
Frans S (2018-12-19 18:27:56+00:00): Hello, Thanks for mapping on this project.
I review tasks in order to validate tasks.
I have a remark.  When mapping buildings, for a rectangular building 4 nodes is enough. You put also nodes in the centre of the roof, No need to do that. Don't forget to square buildings with the S key in ID editor the next time.
Thanks and best regards
Ferdes (2018-12-19 22:25:26+00:00): Hello, it was a pleasure to map for this project. Thanks a lot for the advice. I will keep in mind for future mapping.

Best regards,
Ferdes
mavl (2019-02-24 17:37:12+00:00): This changeset was redacted.
freeExec (2018-12-14 05:45:26+00:00): Их следует обозначать так
https://wiki.openstreetmap.org/wiki/Tag:memorial%3Dplaque
Greg_Rose (2020-08-26 05:35:25+00:00): Just so you know, natural=yes does not create a swamp.
Leo Slager (2018-12-13 01:02:36+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privébericht.
Leo Slager (2018-12-13 01:04:17+00:00): De adresgegevens staan al op de adresnode die vanuit het Kadaster is geïmporteerd.
Adresgegevens worden dus niet nogeens op het gebouw getagd.
Ik herstel dat even.
viloan (2018-12-12 15:29:37+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
PerseP (2018-12-14 08:54:47+00:00): There are many spoken languages in Benidorm. instead of deleting the name you could tag it with its multilingual name
Leo Slager (2018-12-13 15:09:39+00:00): Lijkt mij geen goed idee. Dit parkeerterrein is getagd met access=private. Dat wil zeggen: Alleen toegankelijk voor medewerkers en bezoekers van het bedrijf.
Park and Ride is dus sowieso niet juist !
Dus dat wordt weer verwijderd.
Mod - BNV Mobility (2018-12-13 15:34:26+00:00): Excuses. Ik ben nog redelijk nieuw in het aanpassen in OSM. Ik had deze tag over het hoofd gezien.
Bedankt voor de feedback. Hier leer ik van.
Leo Slager (2018-12-13 22:45:46+00:00): We nemen je ook niets kwalijk. Velen in de community hebben het geleerd met vallen en opstaan. En veel opzoeken in de wiki. Het aangeven van openbare parkeerplaatsen is uiteraard een waardevolle bijdrage in de verbetering van de kaart. Veel plezier met verder mappen.
Frans S (2018-12-20 18:42:31+00:00): Dag Wim. Bedankt voor het mappen in dit project. Een opmerking. Kijk nog eens naar de wiki highways in Afrika, hoe wegen getagd moeten worden. Je tagt regelmatig wegen in een bewoonde omgeving als "tertiar" dwz  verbindingsweg tussen dorpen en steden. "residential' is hier meer op zijn plaats. Ik heb het veranderd. 
Bedankt.
mavl (2019-02-24 17:37:31+00:00): This changeset was redacted.
Radoslao (2018-12-12 16:24:27+00:00): Please delete hashtags
maraf24 (2018-12-13 08:37:32+00:00): Once the changeset is uploaded it cannot be changed.
maraf24 (2018-12-12 18:52:22+00:00): "W czwartek 13 grudnia 2018[...]."

To jutro.
eggie (2019-11-05 14:08:15+00:00): Nu ook een bijdrage in OSM Nederland.. daarom
Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privébericht.
MVG,
Eggie
Truchin (2018-12-13 11:05:45+00:00): Serait il possible de mettre un commentaire de changeset plus précis que Paris ? (qui n'a pas grand intérêt puisqu'on voit bien que la modification est sur Paris) .
Par exemple "passage piéton serait déjà beaucoup mieux"
osmviborg (2018-12-12 16:56:53+00:00): Please don't use DigitalGlobe when mapping in DK.
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/65415098
maus (snekin) (2018-12-13 09:25:06+00:00): i used mainly mapbox. on the reason of the fact that these imagery are the freshest, most accurate, with the least distortions and precisely offset(unlike, for example, from SDFE orthophoto). additionally used SDFE data. besides imagery of ESRI Clarity, if necessary, clarification of details, but no data was directly added for them.
Hjart (2018-12-13 11:14:09+00:00): When mapping in Denmark please always use our national SDFE imagery, which unlike Bing, DG, ESRI etc, is refreshed every spring and better quality than those too
Baloo Uriza (2018-12-14 00:48:40+00:00): Multiple values should be seperated by a ; and not a /
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/65415290
Claudius Henrichs (2018-12-16 19:59:46+00:00): Hm… i can't see where I added multiple values with a slash. I can see OSMcha complaining about it as well, but no pointer at which object it refers to. Any hint?
Baloo Uriza (2018-12-16 22:16:29+00:00): On the runways, ref=* has both runway numbers seperated by a /.
Claudius Henrichs (2018-12-18 21:07:18+00:00): Ah. Indeed. I totally overlooked these, because this is the established and documented standard for tagging the reference for runways. These are the first ten and hundred digits of the degree value of the runway heading. See https://wiki.openstreetmap.org/wiki/Tag:aeroway%3Drunway
Maybe we should teach OSMcha to not flag these...
Baloo Uriza (2018-12-18 21:35:59+00:00): I honestly could go either way on this, on one hand it is somewhat well established to use a / in this case.  On the other hand, aeroway refs are the only thing that does it this way.  Even ref:forward/backward=single_value would make more sense.
11daf (2018-12-28 06:59:50+00:00): Добрый день. Вы удалили много правильно обозначенных объектов, уничтожили границу населенного пункта и добавили адреса  на здания. Можно поинтересоваться источником адресных данных?
            ---
            #REVIEWED_BAD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/65415431
ftcat (2018-12-14 13:34:44+00:00): Be careful using satellite imagery to realign roads in Zambia as the imagery is not necessarily up to date and there have been a lot of road developments lately. If you zoom the images you will see some roads appear and disappear depending on zoom level as they are of different dates.
Anacostan (2018-12-15 00:57:57+00:00): Thanks for the information. I'll make sure to use the most updated imagery and check the zoom levels.
literan (2018-12-12 20:04:59+00:00): вы неправильно пишете адреса. Смотрите, как на зданиях сделано. Удалю, пробуйте еще
mavl (2019-02-24 17:37:35+00:00): This changeset was redacted.
Frans S (2018-12-16 13:46:00+00:00): Hello,  Thanks for mapping on this project.
I am reviewing tasks to validate them and have a few remarks.
1. please read the wiki  India highways to get a better understanding how and where to tag highways, (you tag highway=tertiary in  farming areas which just connect to small hamlets. Unclassified is more appropriate. 
2 Map only highways which connects villages etc to each other. 
Tag living_street is more used in urban areas. Here residential is better.
3 Try to connect highway to each other, for sure in residential areas.  GPS driven navigation systems cannot plan a route through gaps.
When a highway crosses a waterway, map a bridge or a ford on that place
Best regards
andrewwiseman (2018-12-12 22:52:20+00:00): Buenas dias, por favor no nombra calles con latitud y longitud, no están los nombres correctos. Si necesita ayuda, por favor envíame un mensaje.

Hello, please don't name roads for a Latitude and Longitude, that is not the road's name. Let me know if you have any questions.
maraf24 (2019-07-26 08:55:26+00:00): Błędne source.
mueschel (2018-12-13 10:13:09+00:00): Hi,
you added many objects with wrong address keys, like:
    Address=4130
    City=Saint Louis
    Postcode=63115
    State=MO
    Street=Saint Louis Avenue

Please use the existing scheme as described in the wiki: https://wiki.openstreetmap.org/wiki/Key:addr
dustinturp (2018-12-18 15:21:44+00:00): Hi. Thanks for helping. I need to learn how to use the JOSM editor more. How can I retract the edits that I made with errors?
freebeer (2018-12-18 16:06:05+00:00): do you mean to revert the entirety of this edit, so you can start anew, re-creating the objects but this time with the correct tagging values?  presumably you can just pull the same objects from the MS database with no real extra work.

i can do that for you, no problem

or do you mean using josm to convert the tagging errors into something correct?

i can't help there...
freebeer (2018-12-18 22:13:51+00:00): before any revert of this import is carried out, i'd ask you to take a look at the uploaded data and see if it meets the standards you expect.

https://www.openstreetmap.org/way/654530292
is one of the outlines i randomly picked to view, and it looks a bit at a funny angle compared with what i expect.

your data is not rendered because there is nothing to identify it save for the address info in the wrong format, but if you want to see everything, try
https://nrenner.github.io/achavi/?changeset=65416347
where you can zoom in for a rough preview of how your data will appear without further processing, which in some areas (without comparing against imagery) is, well, um ...

i will refrain from digging in with both hands into the can of worms already open in the mailing list and devouring them with relish.  or horseradish.  kremžská hořčice, aww, now i'm hungry again.  and i had hoped to give up eating until Lent.

in the upper right of the added buildings i see that four separate buildings were combined as one.  top row, three as one or two as one.  actually, all over i see that, so i'd give this import a 2 of 5, as there are some decent reasonably well-oriented outlines that match and could be clicked through, but i'd personally discard many or most of them as not meeting my personal standards of craft mapping.

just thought i'd bring this up before you get too far.  for reference, my background imagery is the Bing z20 found in metro areas like this and which appears to be quite well aligned with a similar LIDAR or whatever process used to distort the features, viewed with the `dim' checkbox in my potlatch 2 selected.

Personally, i'd let humans map most of the duds, but then in this area or in East St Louis i skipped a lot as without JOSM my outlines could not meet my standards.

five separate buildings with one postal address.  i wonder which goes where.

and it's a pity, for there are so many unmapped simple rectangular outlines that were a delight for me to trace even before the Mapbox imagery was released.  ah, the good old days when i actually contributed...
dustinturp (2018-12-19 14:50:42+00:00): I do not understand how JOSM works. I had my attributes set in QGIS and had them as polygons. Is there a simple way to translate features from a geojson to OSM file with keeping the geometry type as a polygon? I want to undo the entire commit.

It does not meet my standards. I assumed it kept the polygon geometry instead of converting to lines.  I chose a small neighborhood as my test. I want to focus on adding more data to economically deprived areas. I clearly should just stick with manually drawing.
freebeer (2018-12-19 18:48:33+00:00): if i may suggest, hold off on a revert.  the data is not hurting anyone and cannot be seen.  if anything, it's an ideal testbed for someone wanting to analyse the quality of the microsoft buildings, as the above comments from me might cause someone (anyone?) to have a look-see.

actually, i'm thinking of going through and manually deleting things in several passes to get an idea of the problems in the data, and at the end, after counting what remains, revert the lot.

specifically, first i'd delete multiple buildings counted as one, probably starting with five-as-one down to two-as-one.

then i'd nuke others that fail some degree of accuracy.  all in different changesets, to be able to count how many victims fell by the wayside, and what could be salvaged.

i am afraid i cannot help with JOSM questions, as i have never used it and most likely never will.  pity, for then i would know if one can apply a slight rotation transform to the buildings and salvage them, something i cannot do in potlatch.

the purpose of my testing would be to see if it is worth machine-adding this data and most importantly, *cleaning afterwards* for the most egregious of errors, or if that janitorial duty would be time best spent in manual tracing.  other reviews i have seen have spoken of the quality not being suitable for a blind import - particularly if city or country building data can be made available as in a few other parts of the us.

so, i hope i have your blessing to experiment here, and i thank you for giving me the opportunity to do something other than provide free customer support for the facebook/instagram map errors being dumped into the  osm support channels.

again, if someone doesn't chime in with JOSM tips, try asking somewhere else, and i apologise for not being useful there.

thanks
dustinturp (2018-12-19 21:12:21+00:00): In JOSM I could not see the overlapped features. In QGIS the data looked okay. I did not name my attribute fields correctly for the OSM format I think? I don't understand how the tags translate from attributes to the key-value pairs of the OSM format. I think I need to rename the fields to the correct ones and add a building= yes in there somehow. Not all are buildings. I definitely need to do more data cleaning and compare with my imagery. 

So your suggestion is to keep the data as is and pass through it one by one correcting addresses and converting them to areas? I can work on that if it is not going to get in the way. I started with the state set and brought the data to a small neighborhood level. Matching and joining attributes from city data was cumbersome but it mostly worked. I did not get the naming right for the field names.
freebeer (2018-12-19 21:34:17+00:00): no, my suggestion is *not* to try correctting this data.  it's too far gone and would be a waste of time.

pretend the data you uploaded no longer exists.  as soon as i get enough free memory, i'll go through things deleting them and collecting statistics.  i'll do the revert for you, slowly.

i'll let you know when it is safe to upload here again; if you get things working and want to upload in a different non-overlapping neighbourhood, go ahead.
freebeer (2018-12-19 23:52:33+00:00): by the way, i'm analysing your data and commenting on it as i purge it bit by bit.

it's probably easiest if you look at my most recent changesets, or else look at my changesets i've commented or those in the us.

links to help you find this drivel would be
https://www.openstreetmap.org/user/freebeer/history
(valid for the moment - stop reading as soon as i mention Pokémon)

https://resultmaps.neis-one.org/osm-discussion-comments?uid=429761
(does not include the changesets above where i have not commented yet, one so far)

i am finding more problems i did not expect, in particular the overlapping outlines for multiple buildings with differing addresses.  that looks like something important to be addressed, although the worse problem is where the Microsoft algorithm is interpreting and combining multiple separate building outlines into one large one.

i trust you are not surprised to learn i find several buildings demolished since the data was collected - i'll make a pass for those, although it will be limited by excluding anything that has collapsed in the past year or two since the mapbox aerials were flown.

i hope what i am doing here will help you to find problems in your data preparation, that should be addressed before further uploads.
freebeer (2018-12-20 02:47:24+00:00): if you would, take a look into
https://www.openstreetmap.org/way/654529301
it has only a postcode, no other address info, and as opposed to the angle of the rest of the buildings, this one seems completely aligned n-s-e-w, and indeed, the nodes of the middle horizontal line have in common
Location: 38.6638070, 
as seen in the ESRI imagery, here are two buildings that do not resemble this polygon, so i'm wondering if this was how the data was delivered by microsoft, or if somehow it was twisted to perfection.

curiouser and curiouser.
dustinturp (2018-12-21 14:36:24+00:00): There is a big gap with city data that is available. I need to adjust my join methods and do several passes. This is definitely a learning experience. Thanks. I also will be deleting the data myself. I do not want to be poked further for my mistake.
mavl (2018-12-24 23:49:39+00:00): This changeset has been reverted fully or in part by changesets 65744804, 65751034, 65750264, 65748673 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage - https://www.openstreetmap.org/user_blocks/2400].
muralito (2018-12-14 15:16:58+00:00): ¿Con las addr:city=La Plata que estan por afuera del limite admin level 8 de La Plata, que hacemos?
¿Se ha discutido cuales son esas direcciones en la realidad y si tenemos que modelar algo distinto en OSM?
alpertron (2018-12-14 16:43:05+00:00): Me parece que habría que poner Tolosa, City Bell, etc. No hice ningún cambio en addr:city.
De hecho los códigos postales están mal. En Tolosa todos los códigos postales arrancan con B1906 y no 1900.
muralito (2018-12-14 17:53:11+00:00): OK. Si los CP estan mal habria que corregirlos o borrarlos, lo dejo para que lo hagas vos o alguien que lo tenga bien claro.
muralito (2018-12-14 18:57:58+00:00): y con Gonnet, ¿"Gonnet" como name y el completo como alt_name u official_name?
alpertron (2018-12-14 19:33:37+00:00): Como hay que hacer muchos cambios, me parece que lo más conveniente sería plantear este tema en el grupo de Telegram de OSM Argentina.
muralito (2018-12-14 19:55:03+00:00): Si te parece cuando puedas plantealo.
No tengo acceso al Telegram. :-(
viloan (2018-12-12 17:51:41+00:00): Bem-vindo(a) ao OpenStreetMap e parabéns pela sua primeira edição! :-)

Temos um portal brasileiro sobre o OpenStreetMap, com várias informações úteis em https://wiki.openstreetmap.org/wiki/Brasil

Enquanto você está se acostumando com o OpenStreetMap, é recomendado que sempre pergunte aos usuários mais experientes antes de remover ou modificar objetos do mapa, especialmente aqueles que são aparentemente "estranhos" ou "fora do lugar".

Além disso, pedimos que não copie dados de mapas proprietários (como nomes de ruas do Google Maps, por exemplo) e que mapeie apenas o que existe na realidade.

Se você está mapeando por causa do Pokémon, dê uma olhada em https://blog.openstreetmap.org/2017/12/01/dicas-para-novos-mapeadores-pokemon-go/?lang=pt-pt

Se tiver qualquer tipo de dúvida você pode entrar em contato com a comunidade brasileira através de algum dos canais disponíveis em https://wiki.openstreetmap.org/wiki/Pt:Contact
O canal "Comunidade" do Telegram costuma ser o mais movimentado.

Abraço e boa diversão com suas edições!
b-holdet (2018-12-13 14:20:42+00:00): Are you sure about all these fences are here? Have you seen them actually or just from SDFE/LIDAR?
Normally we have hedge between our gardens in DK and fences are more rare than normal as drawn here.
maus (snekin) (2018-12-13 23:40:25+00:00): matching orthophoto and lidar.

i was not sure that this was a hedge, especially since in some thicker wall-like parts, pieces of narrow fences are sticking out. i had an assumption that these were lianas on a lattice basis. in any case, it is a kind of fence.

if you confirm that the thick sections are exactly hedges, the next time I'll edit here, i will re-tag.

thanks for the amendment.
Hjart (2018-12-14 00:39:17+00:00): In areas like these, hedges are way more common than fences and judging from SDFE orthophoto I'd say that the majority of "fences" here are indeed hedges.
maus (snekin) (2018-12-14 01:54:56+00:00): Thanks for the information and that dispelled my doubts on this matter. =) i`ll correct as soon as possible. well, i will know about it in the future.
mavl (2018-12-25 00:31:23+00:00): This changeset has been reverted fully or in part by changesets 65744804, 65751034, 65750264, 65748673 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: poor mapping, damage - https://www.openstreetmap.org/user_blocks/2400].
gurglypipe (2018-12-13 10:24:43+00:00): You’ve put bicycle=yes on the Caton Road interchange even though there are cycle paths explicitly mapped separately from the roadway. Why?

Where has all this data come from?
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/65417623
Pete Owens (2018-12-13 16:04:40+00:00): Fortunately, in the UK  there is no obligation to ride on the pavement just because it has been designated  for use by bicycles - in the same way motorists are still allowed to drive on the A6 even though there is a parallel motorway explicitly mapped for motors..
gurglypipe (2018-12-13 16:11:18+00:00): I realise that (I am a cyclist). It still seems redundant to add bicycle=yes to roads when the default legal status is for bikes to be allowed on roads. Similarly, the default legal status for motorways is for bikes to not be allowed, so tagging them with bicycle=no seems redundant.

Where has all this data come from?
Pete Owens (2018-12-13 16:34:34+00:00): Also checking the route of the cycle path navigating the A683 Eastwards (Morcambe-> Caton). After stopping for TWELVE separate signal crossings you are dumped on the slip road for the Motorway - so not a viable route in any case. I have added cycling=yes to that stretch of slip road so at least the route is available for west bound cyclists with plenty of time on their hands.

Unfortunately, while the "default" is for cyclists to be able to use the roads, there are a growing number of roads where cycling is being prohibited, so it is necessary to tag main roads to keep track of this.
John-O (2018-12-15 13:12:15+00:00): The tagging of roads with `bicycle=yes` seems unnecessary. Otherwise, every residential road in the country should have `bicycle=yes` explicitly set. 

A better solution would be to add `bicycle=no` where there road type allows cycling, but the particular instance does not. 

You still have not answered the question of where the data has come from? Speed limits aren't generally visible from `Bing aerial imagery`. Did you carry out a survey?
SomeoneElse (2018-12-12 20:31:02+00:00): Hello,
Is there any reason why you're using one changeset per fence here?
You can make more than one change in JOSM at once you know...
Best Regards,
Andy