piebro/osm-data huggingface dataset:
emvee (2019-12-03 07:13:36+00:00): It is always better to have information for the ground, but on the other hand it is also good to have information that is not inconsistent in saying "yes you can cycle" (cycleway=track/lane)  and at the same time saying "bicycle=no".

Like said in the the commit message, the incoming ways do not have bicycle=no and therefore I made this change.

If you think the change is not improving things, please feel free to revert it, but also have a thought on how the data can be made consistent.

Thanks,

Martin.
aharvey (2019-12-03 09:31:07+00:00): cycleway=lane doesn't say you can cycle here, it's simply saying there is a cycle lane infrastructure here, which is the case, but then it's overridden by a sign which says no bicycles allowed, ie. bicycle=no. It can happen as the cycle lane was built but then closed for an extended period due to construction works happening further down the motorway.
emvee (2019-12-03 09:43:23+00:00): Yes, I see your point.

I still would prefer to see somewhere a hint that the closure is due to construction, the combination of these tags is not normal and often indicating there is a bug in the data.
aharvey (2019-12-02 22:59:09+00:00): See https://www.mapillary.com/map/im/wc31bMCC_qNGKHBDVlrb4g this is from April 2019 but unless you have more recent on the ground information, I don't see any reason to change this back to being open to bikes.
aharvey (2019-12-03 01:37:21+00:00): I've reverted this until someone does a ground survey to re-confirm as based on all available information this is still closed to bicycles while the construction works are underway.
emvee (2019-12-03 07:28:10+00:00): Good you better know the situation on the ground so the revert makes sense.

Is there any way to make the reverted data more consistent, I guess the cycle lane is close for construction so how about "cycleway=construction"
emvee (2019-12-03 07:31:20+00:00): As a side note, when it is open again, better add "bicycle=yes" as the proposed default access restrictions for Australia indicate motorway is by default bicycle=no, see https://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Access-Restrictions#Australia
aharvey (2019-12-03 09:35:16+00:00): It's further up the road where the cycleway has been taken up by construction works, but they close this segment since it's the last exit. So this segment really does have a cycle lane on the ground that you're not allowed to cycle in.

I agree, it's best to always map motorways with an explicit bicycle=yes/no. I always try to add this in when I can.
mavl (2019-12-06 19:24:41+00:00): This changeset has been reverted fully or in part by changesets 78068790, 78065244, 78067045, 78062691 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: an incompatible source].
gobeirne (2019-12-02 23:27:41+00:00): Hi there - thanks for your edits, and I can see why you did them. However, the imagery is out of date, and my edits from 11 months ago still represent the current state of the school (I was there this morning!), so it would be good if you could revert these changes (or I'm happy to). Here’s a source: https://www.dropbox.com/s/mmnmomz5wg69qx1/IMG_3974_Original.jpg?dl=0
Best wishes, Greg
Warin61 (2019-12-03 00:45:45+00:00): Done.

The Maxar premium looks to have it 'up to date' (well better than LINZ/Esri). I should have checked there ...
viloan (2019-12-02 21:30:45+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 você está mapeando por causa do jogo do Harry Potter, as dicas e explicações na página anterior também são úteis para você.

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!
literan (2019-12-03 18:06:57+00:00): Вы зачем церковь удалили? https://osmcha.mapbox.com/changesets/77843106
aharvey (2019-12-03 00:49:19+00:00): This looks good, thanks. The bicycle=no for the onramp way is valid per https://www.mapillary.com/map/im/i8PoC8URdMfrriKCUVSciw
skfd (2019-12-03 09:02:53+00:00): Привет! Поменял беседки в детском саду с carport на shelter, думаю так немного правильнее будет
maraf24 (2019-12-04 00:21:11+00:00): Proszę o niezmienianie istniejących rodzajów przejść dla pieszych na to ustawienie w iD. Jest ono niestandardowe i niewspierane przez większość sfotu.
user_5359 (2019-12-03 04:58:42+00:00): Hello! For a better description of your object please see page https://wiki.osm.org/wiki/Waste_Processing .
gscholz (2019-12-10 05:43:29+00:00): Hi greenmapper,
your recent changesets have left behind several errors in the osm database regarding not connected ways:

http://tools.geofabrik.de/osmi/?view=routing&lon=-58.50925&lat=-3.07930&zoom=12&overlays=duplicated_edges,duplicated_edges,duplicated_edges_areas,snap_points,unconnected_open_ends_1,unconnected_open_ends_4,unconnected_open_ends_5,unconnected_open_ends_6

Can you please fix this?

Guido
trigpoint (2019-12-08 15:37:44+00:00): Hi, these edits seem rather odd. Most of what is here is pasture rather than meadow. These areas are also huge, cover roads and the boundaries have no relation to on the ground features. Why so square, could you explain please?

Cheers Phil
ffos-las (2019-12-13 14:05:08+00:00): I agree that pasture would be more appropriate than meadow, however when researching how to tag grazing fields, it seems to me that OSM doesn’t distinguish between the different uses. I’m happy to change the landuse so that it reflects the actual use better, but in the absence of landuse=pasture, landuse=meadow still seems to be closer to the truth than natural=grassland.

The outer boundaries of my edits are simply that; I use Ordnance Survey grid squares to organise my mapping because it would be difficult to keep track of which areas I’ve covered without having some sort of temporary boundary for work in progress. I don’t trace off their maps, in case you’re worried about that. As for the size of the landuse=meadow areas, they reflect the use of the land in the area. Obviously, there is no grass on the roads, but it feels silly to map the outline of each individual field when a road goes between them.
SK53 (2019-12-15 16:26:04+00:00): It might be worth looking at the recent discussion on talk-gb about farmland (https://lists.openstreetmap.org/pipermail/talk-gb/2019-December/023889.html), where there are a few of us who have moved to the view that mapping individual fields is probably the best approach for detailed mapping. Also NRW has a very detailed dataset called Phase 1 Habitats  (http://lle.gov.wales/catalogue/item/TerrestrialPhase1HabitatSurvey/?lang=en) which codified all land in Wales by categories, which in the main, relate fairly cleanly to OSM tags (see https://wiki.openstreetmap.org/wiki/Plant_Community/UK_Phase_1_Habitat_Classification). I haven't looked at the licence for a while so not absolutely sure it can be used in OSM (it used to be verboten).
viloan (2019-12-02 22:31:44+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 você está mapeando por causa do jogo do Harry Potter, as dicas e explicações na página anterior também são úteis para você.

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!
fx99 (2019-12-28 09:10:59+00:00): Die you miss some tags here?
https://www.openstreetmap.org/way/553722812
gendy54 (2019-12-07 21:49:33+00:00): Bonjour,

Dans ces cas là, c'est le terrain qui fait foi. Ca ne dispense pas éventuellement de confronter les sources de données.
            ---
            #REVIEWED_GOOD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/77844771
Andrea Musuruane (2019-12-07 09:07:05+00:00): Ciao Michele, highway=living_street ha un significato ben preciso: https://wiki.openstreetmap.org/wiki/IT:Tag:highway%3Dliving_street. In massima parte questo tag non si usa in Italia. Tu stai cercando di indicare delle strade di accesso alle proprietà: https://wiki.openstreetmap.org/wiki/Tag:service%3Ddriveway
gormur (2019-12-03 00:50:25+00:00): Also proposed new road to ENGK airport. Should have been two changesets :/
gendy54 (2019-12-07 21:37:35+00:00): Bonjour,

Les tags city et postcode sont superflus en France
En revanche, vous pouvez ajouter addr:housename la valeur mise dans le tag name
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/77844980
trigpoint (2019-12-08 15:41:12+00:00): HI, please could you explain what DEM means and these names appear to be made up, I would expect Welsh here, what is the source please.

Cheers Phil
ffos-las (2019-12-13 14:06:09+00:00): DEM stands for Digital Elevation Model. OpenTopomap uses free Shuttle Radar Topography Mission (SRTM) data to plot contour lines, and that’s where I got the summit locations from.

The names of the summits “Old/New Warren Hill” already were on the map, I just moved the summit markers to match the DEM so they are actually on the top of the hills. While most natural features in Ceredigion have Welsh names, it’s not that unusual to have occasional English names, so I’m happy to go along with whoever put those names on the map.
☆Finvenkulo (2019-12-02 23:14:38+00:00): malfarita redakto:
https://www.openstreetmap.org/changeset/77825579
ClarkstonCorrect (2019-12-03 00:11:08+00:00): what is this
☆Finvenkulo (2019-12-03 00:35:44+00:00): @ClarkstonCorrect
Bonvolu priskribu vian problemon.
ClarkstonCorrect (2019-12-03 00:57:14+00:00): why is this the entire planet
☆Finvenkulo (2019-12-03 01:09:55+00:00): Ĉar mia redakto formas kvadraton de Arkta Oceano (https://www.openstreetmap.org/node/305639710) al Oceanio (https://www.openstreetmap.org/node/249399679).
SomeoneElse_Revert (2019-12-09 21:54:32+00:00): This changeset has been reverted fully or in part by changeset 78172369 where the changeset comment is: Reverting some undiscussed international name changes to the status quo ante while discussion is ongoing.  See https://www.openstreetmap.org/user_blocks/3326 and https://lists.openstreetmap.org/pipermail/talk/2019-December/thread.html#83609 .
sleemp (2020-11-11 13:35:11+00:00): Вы можете подтвердить наличие данного офиса в реальном мире по данному адресу?
А также не стоит использовать карту как площадку для спама - это насчет поля description в описании вашего "офиса".
gscholz (2019-12-10 05:43:37+00:00): Hi greenmapper,
your recent changesets have left behind several errors in the osm database regarding not connected ways:

http://tools.geofabrik.de/osmi/?view=routing&lon=-58.50925&lat=-3.07930&zoom=12&overlays=duplicated_edges,duplicated_edges,duplicated_edges_areas,snap_points,unconnected_open_ends_1,unconnected_open_ends_4,unconnected_open_ends_5,unconnected_open_ends_6

Can you please fix this?

Guido
sheldonelectric (2024-11-17 21:52:09+00:00): If the highway is one-way, the sign's direction is implicit. Tagging the direction is only useful when we can drive both ways.
user_1566574 (2024-11-17 21:58:11+00:00): True, but in this case where the street is slightly weird, adding as much infos as we can is a great benefit.
And more generally, it adds a level of details. I'm not sure I will change my habits on this, but I get your point, it makes more sense adding it when it's both ways you're right . :)
sheldonelectric (2024-11-17 22:09:26+00:00): Define "weird". On a 1-way street, a sign can only be applied to that direction.
So I delete these tags when I notice them (even if I was focusing on something else such as maxspeed), as they are duplicate info.
user_1566574 (2024-11-17 22:18:35+00:00): Well, as you can see, only a portion of this narrow street is oneway.
There's no indication at the beginning (C12 sign) and the street is so narrow that we could think it is for pedestrians only.
That's why I consider that every informations adds a layer of detail, making it easier to understand what's on the ground.

Whatever, do whatever you want, but unsure to check the presets (in this case, it is one I added to JOSM, don't remember the name) to "fix" the problem at the source.
user_1566574 (2024-11-17 22:19:58+00:00): In another hand, the "duplicate info" doesn't seems to be a valid argument anymore... https://www.openstreetmap.org/changeset/138835692

I sometimes understand less and less the logic and what should I do.
sheldonelectric (2024-11-17 22:34:43+00:00): If you want to add that the street is narrow, the correct tag is maxwidth=* but I usually only use this tag where there is an explicit sign.
For pedestrian, it's highway=pedestrian.

When you see highway=secondary, you know it's not a pedestrian street.
user_1566574 (2024-11-17 22:39:19+00:00): No, the correct tag is narrow... https://wiki.openstreetmap.org/wiki/Key:narrow

You don't need to teach me things I already know, but thanks anyway…
sheldonelectric (2024-11-17 22:47:41+00:00): Ah i didn't get you talked about the narrow sign. I thought you were talking about that one https://wiki.openstreetmap.org/wiki/Key:maxwidth

All signs have implicit direction, if placed on a highway with explicit direction.

Idk what to say about the case of names on the sidewalk. I'm surprised, never had seen this before. Wiki says "There is no consensus on whether this is necessary" https://wiki.openstreetmap.org/wiki/Sidewalks#Sidewalk_as_separate_way
PT-53 (2020-05-24 09:12:00+00:00): Hallo whb,
ist die Straße Bierhelderhofweg immer noch gesperrt?
Gem. Baustellen-Info von Heidelberg
https://www.heidelberg24.de/heidelberg/heidelberg-baustellen-sperrungen-heidelberg-21-bis-27-oktober-2019-12962669.html
sollten die Bauarbeiten nur bis Frühjahr 2020 andauern.
Fragende Grüße
whb (2020-05-24 21:27:09+00:00): Hallo PT-53,
die Straße ist inzwischen freigegeben.
Danke für die Nachfrage.
Die Bauarbeiten wurden überraschend 5 Wochen früher abgeschlossen:
https://www.die-stadtredaktion.de/2020/04/information/baustellen/bierhelderhofweg-neubau-der-stuetzwand-und-strassensanierungsarbeiten-fruehzeitig-abgeschlossen/
Diogo Correia (2019-12-02 23:30:39+00:00): Boa noite, obrigado pelo feedback Nuno, tive o cuidado de rever os limites da area de parque do jardim municipal....os pontos, estão agora creio que mais exactos...nao verifiquei nenhum que estivesse "colado" ao das ruas circundantes...aproveitei para também nestas poder melhor orienta-las. os unicos pontos que vi juntos, foram o dos percursos pedestres ligados aos das ruas (neste nao fiz alteração na edição anterior), caso nao esteja ainda correcto por favor dê "roll-back" obrigado
☆Finvenkulo (2019-12-03 00:33:11+00:00): Mi pardonpetas, kial vi malfaris mian redakton?!
iandees (2019-12-03 00:46:27+00:00): Removing names of important features is harmful. Please see previous blocks and revert comments.

Translated:
Forigi nomojn de gravaj ecoj malutilas. Bonvolu vidi antaŭajn blokojn kaj reverti komentojn.
☆Finvenkulo (2019-12-03 01:01:36+00:00): En kiu lingvo estu nomoj de kontinentoj kaj oceanoj? Kial ne en la Pola lingvo ekzemple?
Mi proponis nomi ilin en neŭtra Esperanto, sed la uzanto https://www.openstreetmap.org/user/woodpeck_repair malfaris mian redakton; do mi proponas tute forigi la etikedon "name", kaj forlasi nur name:pl, name:eo, ktp.
iandees (2019-12-03 01:11:13+00:00): Why is Esperanto more neutral than English? No matter, this change should be discussed with the community at large. Changing important features without discussion is why your changes are reverted.

Translated:
Kial Esperanto estas pli neŭtrala ol la angla? Ne gravas, ĉi tiu ŝanĝo estu diskutata kun la komunumo ĝenerale. Ŝanĝi gravajn funkciojn sen diskuto tial kaŭzas viajn ŝanĝojn.
☆Finvenkulo (2019-12-03 01:22:36+00:00): Angla lingvo apartenas al iu nacio (Angloj), Esperanto estas konstruita, do tiel ĝi estas neŭtra. Por eviti ĉiun diskriminacion, estus pli bone TUTE FORIGI LA ETIKEDON "NAME".

Pardonu, ĉu iu ajn diskutis pri nomi ilin en la Angla? La kreinto eĉ ne skribis komenton (https://www.openstreetmap.org/changeset/445363).
☆Finvenkulo (2019-12-03 01:28:29+00:00): Vi uzas JOSM en la Angla (en), via programo legas la etikedon name:en kaj vi vidas nomojn en via lingvo: "Europe, Arctic Ocean, Karkinit Bay...". Nigra Maro/Black Sea havas nomon en 69 lingvoj, estas neniu kialo por privilegii iun.
Martin Constantino–Bodin (2019-12-04 12:41:45+00:00): Ĉiel, la specife nomataj etikedoj “name:eo”, “name:en”, ktp. estas korektaj, ĉu ne? Do iu ajn kiu agordis sian mapon por legi specifan lingvon normale legos la nomojn.

La problemo temas pri la baznomo de loko kiuj ne estas asociitaj al specifa lingvo, kiel oceanoj. En kiu lingvo ĝi devintus esti? En mia opinio, estas sufiĉe frustriga ke oni eĉ devas doni tian baznomon por tiaj lokoj ☹ Ĉu eblas lasi la baznomon “name” malplenan kaj nur plenigi la specifajn “name:eo”, “name:en”, ktp.?
Martin Constantino–Bodin (2019-12-04 12:49:07+00:00): (Fakte, estis la propono de Verdizulo: forigi la baznomon “name”, sciante ke ĉiuj lingvoj jam enhavas sian lokalan version “name:eo”, “name:en”, ktp.)
SomeoneElse (2019-12-04 13:28:44+00:00): @Martin Constantino–Bodin - OpenStreetMap is a community.  The key point that @iandees was making above was that changes like this need to be discussed with the community first.  It's possible (but I think unlikely) that after discussion people will think that having a name for Antarctica really does best represent the languages most spoken there, but the important point is that you can't just dive in and change things to your favourite artificial language without discussion.  If you want to reach the OSM community globally, the best place to start is probably https://lists.openstreetmap.org/listinfo/talk .
SomeoneElse (2019-12-04 13:29:17+00:00): @Martin Constantino – Bodin - OpenStreetMap est une communauté. L’argument essentiel que les @iandees ont soulevé plus haut est qu’il faut d’abord discuter des changements de ce type avec la communauté. Il est possible (mais je pense que cela soit peu probable) qu'après la discussion, les gens pensent que le nom de l'Antarctique représente vraiment le mieux les langues les plus parlées dans ce pays, mais le point important est que vous ne pouvez pas vous contenter de changer les choses et de les modifier. langue sans discussion. Si vous souhaitez atteindre la communauté OSM à l'échelle mondiale, le meilleur endroit pour commencer est probablement https://lists.openstreetmap.org/listinfo/talk.
Martin Constantino–Bodin (2019-12-04 14:26:24+00:00): @SomeoneElse I get that. Thanks. (And thanks for the link.) I wasn’t claiming that one should actively change the database without consulting the community. I was just questioning the relevancy of the “name” tag in the case where there is no relevant language associated to the place. Probably not in the right place. Sorry about that.

Also, don’t say that Esperanto is artificial without thinking about it. It indeed started as a constructed language, but its recent (that is, in the last hundred years) evolutions have been entirely driven by its community and its practice (much more than most non-constructed languages, actually): this is not what the word “artificial” is conveying. Using such negatively connoted words is not a good starting point for a safe discussion.
skquinn (2019-12-04 20:25:18+00:00): As much as I like the idea behind having a neutral world language, I found Esperanto quite difficult to learn when I tried. The practical reality, as unfortunate as it may be for non-native English speakers, is that English is as close to a true world language as we are going to get.
Martin Constantino–Bodin (2019-12-05 09:54:06+00:00): @skquinn: You have to understand several things first here.

First, personnal experience is worth exactly nothing when there are studies claiming the contrary. Most studies you can found on Google Scholar mostly study the propedeutical nature of the language, but you can still find some about the learning time. Learning languages is hard in general. You seem to live in an English-speaking area. So yeah, of course English is easier to speak for yourself. This does not mean anything about the language: everybody is biased and that’s why we need some actual statistics to claim anything about language difficulty, not personnal experience.

Second, the suggestion of this changeset here was not to use Esperanto for the main “name” tag. It was to remove the “name” tag for places whose language is not obvious (oceans, Antartica, etc.). The point is that these places are already associated with a ton of localised tags “name:en”, “name:eo”, etc. and thus any renderrer can use them instead. This has nothing to do with actually chosing a neutral language. Note that the documentation does not says that English should be used as neutral ground at all in this situation: https://wiki.openstreetmap.org/wiki/Key:name It is something that has not been stated by the community yet, and should be debated first. Stating that “English is the obvious choice” or anything by that is against the rules for the very same reason that this changeset was reverted.

Anyway, this is absolutely not the right place to debate for it. I’ve send yesterday a message to the talk mailing list on the link given by SomeElse above, and it still awaits moderation. We have to be patient here. But please, do not misunderstand the whole point of the changeset (whose author I am not, but the way) or place personnal biases above scientific studies.
user_5359 (2019-12-03 04:54:23+00:00): Welcome to OSM! Please be careful when editing the map data. You moved the node https://www.osm.org/node/6311931879/history over 100 meters, so there were problems with the corresponding way.I move the node back to the original position.
alester (2019-12-03 05:01:12+00:00): Please stop doing this. Such a massive change needs to be widely discussed with the global OSM community. The community will not allow you to be the only one to decide on this major topic, so there's no point trying to impose your personal opinion. You're just wasting everyone's time.

Translation:
Bonvolu ĉesi fari tion. Tia amasa ŝanĝo devas esti vaste diskutata kun la tutmonda OSM-komunumo. La komunumo ne permesos al vi esti la sola decidi pri ĉi tiu ĉefa temo, do neniel penas trudi vian personan opinion. Vi nur malŝparas ĉiun tempon.
woodpeck (2019-12-03 14:06:56+00:00): https://www.openstreetmap.org/user_blocks/3309
skquinn (2019-12-09 19:37:29+00:00): Stop doing this before you wind up getting permanently banned from editing OpenStreetMap (which has happened to others who have done similar things).