piebro/osm-data huggingface dataset:
AntMadeira (2020-03-01 17:30:37+00:00): Olá, ftrebien.
Obrigado pelas tuas observações a esta alteração na Praça Garibaldi.
Respondendo ponto a ponto.
1) Não costumo sobrepor polígonos com vias, mas neste caso, considerei o parque até à borda do calçadão, pois a via de pedestre começa dentro do parque e tem uma largura que abrange parte dele. Confesso que foi uma decisão hesitante e sem grande certeza.
2) As ligações foram feitas em volta do parque, menos no vértice sul, pois aí não existe faixa de pedestre, apenas para ciclista. A faixa de pedestre foi colocada mais a norte.
3) Na minha experiência de mapeador do OSM, o problema das calçadas é um problema sobre o qual ainda não me debrucei muito, pois sei que não há consenso e há coisa mais importantes para mapear. Concordo quando você diz que mapear calçadas sobrecarrega o mapa de dados e de grafismo, por isso mesmo eu evito mapear. O mesmo em relação ao roteamento de percursos pedestres. Se não houver calçada desenhada como fazer um roteamento numa faixa de segurança? Vai ligar a faixa aonde? A minha ignorância nesta área ainda é grande.
No entanto, nas praças, costumo desenhar as calçadas, por serem um elemento que compõe todo o conjunto. Esta praça tem uma calçada de 3 metros de largura a norte. Como não mapeá-la, se as calçadas interiores estão mapeadas? Difícil...
Além disso, existe diferença entre highway=footway (calçada e outros caminhos para pedestres que não ruas para pedestres) e a mesma etiqueta com footway=sidewalk, que corresponde ao "passeio" em Portugal, que serve apenas para ladear as ruas. Ambas estão bem descritas no iD. Por isso eu aqui distingo uma calçada de praça (que define uma calçada da praça, tal como as outras interiores que são mapeadas) e o "passeio" ou calçada de rua, que, e aqui concordo contigo, deve ser mapeada com sidewalk=* nas vias.
Por fim, eu uso o JOSM em determinadas situações, mas prefiro o iD por diversas situações. Em primeiro, para ajudar a desenvolvê-lo. Se não o usarmos, não podemos ajudar ao seu desenvolvimento. E isso é importante, pois quem chega ao OSM pela primeira vez vai usar o iD e não o JOSM. Se a ferramenta não for boa, perdemos um mapeador. E a ferramenta é muito boa, tem evoluído tremendamente nos últimos tempos. Além disso, sou tradutor e contribuo para a correta tradução do iD em português de Portugal, para ajudar a padronizar os termos e a ajudar os mapeadores mais casuais a usar corretamente as etiquetas.
Se quiseres, podemos continuar esta conversa lá no Telegram do RS.
Abraço.
ftrebien (2020-03-01 18:32:47+00:00): "Ambas estão bem descritas no iD." O ponto comum do OSM é o conteúdo do wiki. Já vi os desenvolvedores do iD optando por divergir de práticas bem estabelecidas à revelia e com isso causando confusão. Ainda hoje o iD permite ao mapeador leigo fazer coisas não muito certas achando que está fazendo certo, notavelmente em certas situações permite combinar vias com etiquetas diferentes sem avisar o mapeador que são diferentes. Os desenvolvedores sabem (eu mesmo reportei anos atrás) e nunca trataram do problema, apesar do tratamento ser simples. Vejo esse editor com esperança de que continue melhorando, já que realmente ajuda o projeto como você dise, mas com um pouco de ceticismo também.
ftrebien (2020-03-01 18:40:00+00:00): Em relação à ausência de faixa de pedestre, no caso especificamente no encontro da footway que margeia a escola Cantinho Amigo com a José do Patrocínio, não é necessário haver faixa de pedestre, que é o caso de crossing=marked .
AntMadeira (2020-03-01 20:39:14+00:00): "notavelmente em certas situações permite combinar vias com etiquetas diferentes sem avisar o mapeador que são diferentes."
O iD (já) não permite combinar vias com etiquetas diferentes.


"Em relação à ausência de faixa de pedestre, no caso especificamente no encontro da footway que margeia a escola Cantinho Amigo com a José do Patrocínio, não é necessário haver faixa de pedestre, que é o caso de crossing=marked."
Não percebi este comentário, podes explicar melhor?
ftrebien (2020-03-01 21:47:06+00:00): "O iD (já) não permite combinar vias com etiquetas diferentes." Permite. Veja aqui: https://www.openstreetmap.org/?mlat=-29.99638&mlon=-51.12409#map=19/-29.99638/-51.12409

Por exemplo, se você selecionar a parte norte (http://openstreetmap.org/way/393911414) e a parte sul (http://openstreetmap.org/way/288081207) da Alameda 3 de Outubro, onde uma tem oneway=yes e a outra não tem oneway=*, o iD permite combinar as duas, transformando todo o trecho numa via oneway=yes, sem dar aviso algum. Nesse caso, o roteamento fica incorreto. Ele só impediria a combinação se um lado tiver oneway=yes e o outro tiver oneway=no. O mesmo vale para qualquer outra etiqueta. O JOSM sempre avisa.
ftrebien (2020-03-01 21:47:43+00:00): "que é o caso de crossing=marked" Desculpe a confusão, eu quis dizer "que é o caso de crossing=unmarked" (era pra ser o valor unmarked, não marked).
user_5359 (2020-02-15 04:09:54+00:00): Please understand and follow: In OSM we used the two-letter country abbreviation in capital letters for the value of addr:country. The value is CA instead of Canada.
ftrebien (2020-03-01 18:39:35+00:00): Discordo fortemente da separação desta ciclovia. Estava mapeada corretamente como ciclofaixa antes, correspondente ao padrão M2b descrito neste artigo: https://wiki.openstreetmap.org/wiki/Bicycle#Cycle_lanes_in_oneway_motor_car_roads
ftrebien (2020-03-01 18:51:02+00:00): E por que você removeu a etiqueta horse=no? É proibido em todo o município desde 2016 segundo as leis municipais 10531 e 12117, foi bastante noticiado na época. Seria melhor não misturar os dois assuntos no mesmo changeset.
AntMadeira (2020-03-01 20:34:38+00:00): Como conversado no Telegram, pode reverter este changeset.
user_5359 (2020-02-15 04:24:31+00:00): Welcome to OSM! Please read https://wiki.openstreetmap.org/wiki/Key:payment for a better description of payments. What is the meaning of payment:SNAP/EBT ?
Edmund-Adewu (2020-02-15 19:24:11+00:00): EBT (Electronic Benefit Transfer) is an electronic system where state welfare departments issue benefits to qualifying US residents via a payment card. SNAP (Supplemental Nutrition Assistance Program) is a United States food assistance program where qualifying residents, usually citizens with little to no income, receive funds towards food via the EBT card.
boubascript (2020-02-16 00:20:06+00:00): The keys payment:snap and payment:ebt exist separately. ( See https://wiki.openstreetmap.org/wiki/Key:payment#Government_assistance_programs).
The key you have isn't being recognized because you put them both into one as SNAP/EBT.
Pavlenkog (2020-02-15 14:27:42+00:00): Die Stromleitung wurde demontiert
luschi (2020-02-15 19:43:35+00:00): Danke für den Hienweis.     
Das nächste mal bitte klar im Changeset reinschreiben...     
Wenn jemand in seinem ersten Changeset, eine Stromleitung entfernt und das dann auch noch irgendwo auf dem Land ohne weitere klare Angaben kommt das einem schnell komisch vor.

Werde sie wieder entfernen     

lg
Pavlenkog (2020-02-16 07:31:45+00:00): Ja, es stimmt. Nächstes Mal schreibe ich ausführlichen Kommentar. Danke!

SG
aharvey (2020-02-16 07:06:12+00:00): Just a tip, when adding wikipedia links you need to also specify the language code of the page. I've done this for this feature see https://osmlab.github.io/osm-deep-history/#/way/4631838. If you add it with the iD editor it should do that automatically if you select from the dropdown, it should also add the wikidata id.
user_5359 (2020-02-15 04:16:25+00:00): Please understand and follow: In OSM we used the two-letter country abbreviation in capital letters for the value of addr:country. The value is CA instead of Canada.
pangoSE (2020-02-16 15:30:39+00:00): Hi, could you please split edits like this in multiple changesets?
RicoElectrico (2020-02-18 17:49:24+00:00): @pangoSE 
It's not possible to split them, maps.me decides for the user when to upload edits. I notified the maps.me team about the issue, but as evidenced by this edit - they don't care.
pangoSE (2020-02-19 05:25:06+00:00): Oh, thank you for the information.  Maybe you should switch to OsmAnd, which is also free software. I have the version from f-droid and adding POIs work very well. 😃
RicoElectrico (2020-02-19 10:00:00+00:00): I'm not the author of the edits ;)

Also, while I personally use OsmAnd, it's very clunky to use, even more so than maps.me. Not great for newbie users.
frosm (2020-02-15 09:41:53+00:00): Bonjour,
j'ai corrigé le parking qui était responsable des 54 alertes :) il y avait un point totalement éloigné.
pour le café, vous avez squaté le point addr représentant l'adresse du batiment.
la bonne façon de faire est de créer un nouveau noeud dans le batiment
Bonne continuation
Vinber (2020-02-21 09:08:12+00:00): Bonjour et bienvenue dans OpenStreetMap,

nouvelle-nouveau, un petit mot ici pour faciliter votre arrivée : https://wiki.openstreetmap.org/wiki/FR:WikiProject_France/bienvenue

Cas particulier / Vous êtes en seconde, en cours de SNT, alors s'il vous plait, veuillez faire suivre à votre enseignant-e le lien suivant https://dane.ac-lyon.fr/spip/spip.php?article628

Et n'hésitez pas à répondre, poser des questions, ...
mariotomo (2020-05-25 17:04:28+00:00): Hi Ika-Chan, very interesting data you contributed here!
ika-chan! (2020-05-25 17:26:47+00:00): I think it is only a fraction of all the woodland around the area. It takes a long time just to map a small area of woodland when it is so patchy.
mariotomo (2020-05-25 21:07:50+00:00): may I invite you to have a look in Northern Veraguas?  it should be quite quick, it's almost just a single patch of natural wood.  the openings are slash-and-burn areas, or settlements.
Glassman (2020-02-20 23:06:41+00:00): I drove by the new location of Sandmaiden business. It is not at this location. I email the owner, she replied that the business is run out of her home and does not want it on any map. 

I have removed the business but left the building and address.
marcoSt (2020-02-15 14:47:35+00:00): Hello, MacLondon,
What is your intention, to split this Flixbus-Line? Can you explain that, please? I think that is not a good idea, because it is a whole line, which use the Eurotunnel train.

Best regards

Marco
MacLondon (2020-02-16 04:52:32+00:00): Hi Marco,
Unfortunately it isn't valid for a route=bus to run along a railway=rail.

Although the buses themselves do go onto the train, passengers then generally get off the bus and this section of the public_transport journey is a route=train.

PTv2 bus routes that run along train tracks are displayed as invalid on OSM Inspector (http://tools.geofabrik.de/osmi/?view=pubtrans_routes&lon=1.34715&lat=51.04895&zoom=10&overlays=ptv2_routes_invalid). This also makes it difficult to identify any additional errors that might occur along this long route.

Regards,
Mac
marcoSt (2020-02-16 11:35:48+00:00): Hi Mac,
I know what you mean. This error exists also for ferries ect. 

I have tried to solve this problem, too, with less success. I have tagged a bus=yes on this tunnel-line. The error was gone, but the whole community was not amused about this. So I must have deleted this tag. Since than I have ignored this error. 

Perhaps an IT-Specialist has a solution for this problem. Not really satisfied is the whole thing.

Best regards

Marco
MacLondon (2020-02-17 21:48:51+00:00): Hi Marco,

I agree it would be nice to be able to have a continuous route. I'd previously hoped that tagging the Eurotunnel train route relation with 'service=car_shuttle + cargo:bus=yes' might solve the problem but it didn't. I also tried adding the Eurotunnel route relation (instead of the railway tracks segments) to the bus route without any success.

With regard to an IT solution to the use of nested relations, I wonder if https://hiking.waymarkedtrails.org/help/rendering/hierarchies *might* be a pointer to finding a solution (site is run by https://wiki.openstreetmap.org/wiki/User:Lonvia).

In the background, she has somehow managed to combine nested relations for individual walking/cycle routes to display them on a map as a single route, e.g. London's Capital Ring walking route (https://hiking.waymarkedtrails.org/#route?id=10952) is made up of 15 subrelations. Another example from the cycle routes is https://cycling.waymarkedtrails.org/#route?id=1207220&map=5!56.2246!14.5649.

I should mention, I did replicate the changes from this changeset in the other coach routes using the Eurotunnel train in advance of seeing your initial comment here.

On last night's OSM Inspector update, all these routes did show as valid, but I'm waiting to test out a couple of further things I've done like reverting an individual route to the preferable 'route=bus' to check if it remains valid when OSM Inspector updates again tonight.

On a different route I'm testing out whether the 'virtual ramp' to the train track can be included in a bus route.

Regards,
Mac
marcoSt (2020-02-18 19:34:05+00:00): Hello Mac,

There are really interesting examples that you have given. That could be the key to solve this problem. I am cautiously optimistic that it could work. Just take a look.

Regards,
Marco
ToniE (2020-02-18 20:58:05+00:00): Hi Mac,

Marco pointed me to this discussion here, may I join?

Nested Relations as described on waymarkedtrails could be a solution, but this hierarchy is not covered by the PTv2 specification. Busses using ferries, shuttle transport and so might be seen as a gap in the specification though.

Another - not new approach to PTvX - is similar to the solution of Sarah (Lonvia). This introduces "segments", i.e. a bunch of roads (in a sequence) which are grouped by a segment relation. Segment relations can be members of route relations. 
In dense areas, a segment would be a collection of 'ways' between two junctions (assuming busses join or leave the common route at those junctions).
But that's another story.

I have no solution yet to group 

1.) London - Folkestone (bus relation)

2.) Folkestone - Calais (train relation)

3.) Calais - city-on-the continent (bus relation)

and backwards in one route(_master) AND at the same time specify that 1.)-2.)-3.) build an itinerary with a single fare/ticket and so on.

Best regards,
Toni
MacLondon (2020-02-20 02:43:57+00:00): Thanks Toni. I found an example of one of these 'segment' routes at https://www.openstreetmap.org/relation/2125451 just to see a specific example of the tagging used. The tagging seems to be in use mostly in Germany for the members of a few route=road parent relations (https://taginfo.openstreetmap.org/keys/segment#map).

The equivalent for the Folkestone - Calais segment would be to make a collection of the railway tracks, but I'd expect that any route via this segment (along a collection of railway tracks) would still need to be a route=train.

For now, I have applied "segment=yes" to all the nested route relations. Marco, hopefully that tag could in some way be made use of by you.

A couple of potential issues I though of with the use of nested relations:

(i) Would all bus stops be better placed at the top of the parent relation, i.e. before the nested route segments?

(ii) Maybe there might be a need for separate train relations for each bus route It might transpire that the train segment will need to have the same ref/network tag as the parent relation.

An alternative simpler (dream!) solution would be if any route tagged with e.g. "shuttle=bicycle;vehicle" or "cargo=bicycle;vehicle" would be 'valid' in PTv2 for use by bicycles + vehicles, so all ways could be used in a single route relation.

Regards,
Mac
ToniE (2020-02-20 10:55:04+00:00): Hello Mac,

> (i) Would all bus stops be better placed at the top of the parent relation, i.e. before the nested route segments?

yes, stops are specific for routes, express busses for instance may skip 2 or 3 stops.

> (ii) Maybe there might be a need for separate train relations for each bus route It might transpire that the train segment will need to have the same ref/network tag as the parent relation.

Hmm, not sure about this. In a PM to Marco I sugested that PTv2 does not explicitely exclude member ways "railway=track" or ferries from route=bus relations.
Could we make use of this "inaccuracy" and keep one single route-relation per direction which "simply" includes highways as well as railways - thus being "lazy" mappers?
On the other side: How do OSRM, Graphopper, OsmAnd, ... handle ferries and shuttle transport when they calculate a route for a car? Can we "learn" from that?

Just my 2 cents.

Best regards,
Toni
user_5359 (2020-03-15 05:54:24+00:00): Welcome to OSM! Is there any reason why you use the key Mapper (there is also the key mapper) 
Regardless of the case, the person who entered the data is also in every version of the data set. 
Is there a project description that requires this?
angys (2020-07-19 21:49:11+00:00): Why you delete this?
https://www.openstreetmap.org/way/754641284/history
Matt13311 (2020-02-15 05:59:09+00:00): sorry had a typo. Meant to type "now destroyed" instead of "not destroyed"
majkaz (2020-02-18 13:54:07+00:00): Ahoj, ta myčka je takhle blbě označená. StreetComplete patrně nebude správný nástroj, jakým to dělat. Navíc to jméno je tam blbě, "Ruční myčka OMV" určuje co to je zač, ne jak se to jmenuje. Fakt není problém tu myčku zadat jako takovou, a jméno tomu vůbec nedávat. Totéž u toho parkovacího domu u finančáku. access=yes je zbytečné značení, normálně to funguje obráceně - dává se jen omezení přístupu (tj. soukromé/pro zákazníky).
mavl (2020-02-17 16:09:19+00:00): This changeset has been reverted fully or in part by changeset 81124906 where the changeset comment is: The changesets are reverted [DWG has the request to revert the changesets. Reason: nonexistent objects - https://www.openstreetmap.org/user_blocks/3502].
Mir76 (2020-02-21 17:09:17+00:00): Почему вы заменили на отношении 1628595 тег natural=wood на natural=scree???
RomanKlykov (2020-07-05 17:24:14+00:00): Извините, видимо случайно. Не видел то что вы писали. Как можно получать уведомления о таких вопросах не подскажете? Можно личным сообщением.
Mir76 (2020-07-06 04:03:54+00:00): Вроде отдельных настроек нет. Мне просто приходят письма на почту, с которой я здесь зарегистрирован с темой вида "[OpenStreetMap] RomanKlykov прокомментировал пакет правок, который вас интересует".
RomanKlykov (2020-07-07 07:05:13+00:00): Точно, приходило. Пропустил. Много треков добавляю, глаз замылился от сообщений что трек успешно добавлен )
azakh-world (2020-03-19 10:58:25+00:00): Hi.
A relation with tags type=boundary + admin_level=2 corresponds to a country. You've created many such relations, e.g. https://www.osm.org/relation/10713816/history, so there appeared many new countries, particularly multiple countries with name "Paraguay". I'll remove unwanted relations and tags. Please read osm wiki about multipolygons and boundaries and look how other country boundaries are mapped before further playing with countries.

Best regards,
Alexey
user_5359 (2020-02-15 13:13:12+00:00): Welcome to OSM! I have delete your SEO SPAM (mostly no standard keys, no verifiable data or not positive verifiable address data). If this is an error, you can report it here, then we will be happy to help restore the data. For the most information in the description we have own keys. Please have look on the website http://wiki.openstreetmap.org.
ralley (2020-02-15 08:25:46+00:00): Welcome to OSM and thanks for your edits.  Most houses in NZ consist of mainly 90 degree corners.  In ID if you right click the building outline you can automatically square it so all corners are 90 degrees.  Short cut key is Q.
            ---
            
            Published using OSMCha: https://osmcha.mapbox.com/changesets/81035136
FreedSky (2020-02-17 08:12:37+00:00): 有用的这个node。
https://www.openstreetmap.org/relation/10694395#map=8/30.325/108.270
iWowik (2020-02-23 21:24:24+00:00): Приветствую вас в проекте, я заметил, что вы рисуете домики и к тому же не пишете в названии улиц слово улица, что требуется в обязательно порядке.

Скажите пожалуйста, где вы берете адреса для домиков?
Обычно их сложно найти, чтобы понять где на карте какой адрес, нужна карта.
К тому же у различных карт и планов есть правообладатели и без их явного разрешения данные в OSM вносить нельзя.
Целью проекта является сбор данных, свободных от претензий других лиц, поэтому данные, вносимые без разрешения их владельца могут в какой-то момент быть удалены из проекта.
Администрация МО "сельсовет Алходжакентский" (2020-03-01 16:15:30+00:00): Здравствуйте. Это все с официальных данных Администрации "сельсовет Алходжакентский". Карта и адреса домиков,  все данные переданы главой села для обновления вашей системы.
SomeoneElse_Revert (2020-03-02 13:20:27+00:00): This changeset has been reverted fully or in part by changesets 81679210, 81682323 where the changeset comment is: Reverting more political edits between Armenia and Azerbaijan .  See https://www.openstreetmap.org/user_blocks/3528 for more information
ftcat (2020-02-16 16:48:35+00:00): Hi, Just a note to bear in mind when editing here, this is a large floodplain/wetland most "streams" are just open water channels in the reedbeds and would normally flow towards the Zambezi, so if you are mapping to the east of the Zambezi they would flow west or, as in this case, to the west of the Zambezi they would flow east. Nothing flows north, if it is not flowing east or west it will be flowing south but as I say most are just channels of open water not actual streams. and the open water may be temporary depending on how wet the season has been or at what time of the year the imagery is from.
ftcat (2020-02-16 16:54:49+00:00): Having a closer look at your edit and then zooming out the channel is maintained by people in dugout canoes so they can get out to the low lying island out in the floodplain where there is a small settlement, probably a fishing village with some small gardens around it. The channel then extends toward a larger channel and then the main stream of the Zambezi. The local people here will travel great distances by dugout
bsin (2020-02-18 11:02:46+00:00): Thanks for having a look at this and being a great validator. I completely agree with this thinking and after this edit I dont think I added another "stream" in a flood plain area as it could change per year. Look at Esri imagery taken when it wasnt in flood alot of the "stream" dries up. I live in this greater area and would also not have called this a stream as there is no flow, hence the wrong direction put on map. Sorry. I think it would be wise to avoid to many tracks on flood plains and also water bodies. Unless compared to dry season. Thanks again for the assistance
SomeoneElse_Revert (2020-03-02 13:20:17+00:00): This changeset has been reverted fully or in part by changesets 81679210, 81682323 where the changeset comment is: Reverting more political edits between Armenia and Azerbaijan .  See https://www.openstreetmap.org/user_blocks/3528 for more information
SomeoneElse_Revert (2020-03-02 13:20:16+00:00): This changeset has been reverted fully or in part by changesets 81679210, 81682323 where the changeset comment is: Reverting more political edits between Armenia and Azerbaijan .  See https://www.openstreetmap.org/user_blocks/3528 for more information
SomeoneElse_Revert (2020-03-02 13:20:01+00:00): This changeset has been reverted fully or in part by changesets 81679210, 81682323 where the changeset comment is: Reverting more political edits between Armenia and Azerbaijan .  See https://www.openstreetmap.org/user_blocks/3528 for more information
SomeoneElse_Revert (2020-03-02 13:20:07+00:00): This changeset has been reverted fully or in part by changesets 81679210, 81682323 where the changeset comment is: Reverting more political edits between Armenia and Azerbaijan .  See https://www.openstreetmap.org/user_blocks/3528 for more information
SomeoneElse_Revert (2020-03-02 13:20:24+00:00): This changeset has been reverted fully or in part by changesets 81679210, 81682323 where the changeset comment is: Reverting more political edits between Armenia and Azerbaijan .  See https://www.openstreetmap.org/user_blocks/3528 for more information