piebro/osm-data huggingface dataset:
ScottWalkerAU (2022-01-24 07:23:31+00:00): Hi & welcome, you can use the "square corners" action in iD to make houses have right-angle corners
Mister Levy (2022-01-24 07:34:22+00:00): Thx for the tip. Didn't know there was such a feature. 
I'll google how to do that.
mavl (2022-01-25 13:58:02+00:00): Здравствуйте. В России в OpenStreetMap действует соглашение об именовании улиц.  
  
https://wiki.openstreetmap.org/wiki/RU:%D0%A0%D0%BE%D1%81%D1%81%D0%B8%D1%8F/%D0%A1%D0%BE%D0%B3%D0%BB%D0%B0%D1%88%D0%B5%D0%BD%D0%B8%D0%B5_%D0%BE%D0%B1_%D0%B8%D0%BC%D0%B5%D0%BD%D0%BE%D0%B2%D0%B0%D0%BD%D0%B8%D0%B8_%D0%B4%D0%BE%D1%80%D0%BE%D0%B3  
  
Слово "улица" пишут полностью без сокращений.
Carnildo (2022-01-24 23:04:55+00:00): There's no need to put three names into the "name" field -- one is sufficient.  That's the whole reason there are "name:lang" tags.
NFZANMNIM (2022-01-24 23:25:12+00:00): it's a common practice on OSM to use multiple languages on the "name" tag for jurisdictions that have more than 1 official/principal language. Same thing is done in parts of Europe (such as the city of Brussels) and Africa that are bilingual/multilingual , or also in Canada specifically for reservations.
Carnildo (2022-01-25 02:26:00+00:00): In case you haven't noticed, the United States isn't part of Europe, Africa, or Canada.
NFZANMNIM (2022-01-25 03:15:19+00:00): ummm i think you misunderstood my point. My point was about how the tag "name" is used on OSM elsewhere.

and yes you're correct about the US in general. Nevertheless, Native American Tribal governments in the US are considered to be sovereign entities, with their own official and protected indigenous language(s) alongside English.
Dimitar155 (2022-05-09 19:22:24+00:00): Здравей, може ли да погледнеш адреса на https://www.openstreetmap.org/way/974913297?
Lee Carré (2022-01-24 23:44:52+00:00): Err, why?
Lee Carré (2022-01-25 00:26:50+00:00): Seems like a purely mechanical edit, too.
user_5359 (2022-01-25 05:20:54+00:00): The values for the opening_hours key "24/7" and "24/7 open" are synonymous. Since all points were recognisably from the same entrant, I carried out this normalisation in a change record.
Lee Carré (2022-01-25 08:10:05+00:00): But, to what end? What was gained?

24/7 open is more explicit (since there are instances of 24/7 closed).
user_5359 (2022-01-25 08:19:03+00:00): Thank you for pointing this out. I think it is a mistake to have a symbol for, for example, a hotel appear on the map when it says closed in the opening hours. There are life cycles for this, such as the prefix disused:
Lee Carré (2022-01-26 02:32:45+00:00): This is changing the topic, without answering previous questions. I take it, then, that nothing was gained, and there was no point in this changeset, which makes it spam and thus warrants reversion.

Re tagging a closed hotel

“it is a mistake to have a symbol for, for example, a hotel appear on the map”

Firstly, please see http://wiki.osm.org/wiki/Tagging_for_the_renderer
If you don't like a particular rendering, then use a different one, or submit a change to whichever renderer you think is wrong.

Tagging is data problem, not a rendering one. A hotel marked as closed conveys valid (& correct, depending on circumstances) semantics. Not everyone seeking a hotel will want one which is open right now. Marking it as disused, when it's merely closed, is incorrect.

Notice, in your perusal of my past changes, that most are source=survey, or occasionally local knowledge when I learn about it from a well-recognised source.

I agree re prefixes (where applicable), however others (both local & not) don't and become upset when tagging isn't as they think it should be, even if their changes make the tagging no longer reflect reality.

However, depending on which hotels you mean, marking them as closed but not disused is correct; e.g. being closed for the winter (and not necessarily specifying an opening date), but remaining a hotel.
Some even go so far as to make a duplicate element, or delete the element marked as disused (compare deleting shop=vacant). See http://wiki.osm.org/wiki/Keep_the_history
Not as it should be, but gotta work around human psychology.

Keep in mind, too, that different countries have different tagging conventions. Quite a few things are different, here, or rules which make sense elsewhere don't make sense here.

The tourism market is in flux (and has been for quite a while). Sometimes the fate of a hotel is uncertain, thus minimal changes (which are easy to undo) are wise.

Just because I happen to be a somewhat frequent contributor, among a small handful of locals, doesn't justify treating my changes as merely my personal opinion. Some of them come from discussions with other local mappers, which could be argued as a consensus.

There's also the point that surveying takes a long time (compared to armchair, for a similar count of changes); thus, making sweeping revisions discourages the effort of surveying (which is what's needed, here). No, I'm not the only surveyor to think this.

It would've been prudent to discuss your intended change with the local community first, or better to seek understanding of local conventions, before performing an island-wide search-and-replace.
user_5359 (2022-01-26 06:22:38+00:00): I think it is an overreaction to conclude that a badly chosen example is spam. 
If a key describes the open hours of an object and there is a defined value for always open (24/7) then values like "24/7 open" are identical.
Regarding your example hotel, there is a difference between use (tourism=hotel) and appearance (building=hotel). 
And I can only hope that it is clear that an ice cream parlour (if it only sells ice cream) is not open in the winter months due to lack of turnover. It would be a mistake to write opening_hours= closed because the person entering cannot currently eat ice cream. But I don't delete nodes, I just change the values. In this way, the data can be read in the history as described.
What can I do to focus on the change record and the added value of "24/7 open" and "24/7" that you have seen?
Lee Carré (2022-01-30 04:44:42+00:00): “… defined value for always open (24/7) then values like "24/7 open" are identical.”

So as I suspected; nothing was gained, and this changeset is pointless.

As you likely know; opening_hours has its own syntax, which must be parsed (rather than mere string-matching). In which case, a correctly implemented parser will yield the same answer anyway. Except that one is more explicit, which you've undone / removed here, which achieving nothing.

Avoiding ambiguity is why I liberally add note:*=* & fixme(*)=* to elements, along with source:*=* .

I'm being considerate of other (& future) mappers.

“… an ice cream parlour (if it only sells ice cream) is not open in the winter months …”

This is a straw-man of my point.

But, yet, hence (for example): http://www.osm.org/node/9117291510

“… It would be a mistake to write opening_hours= closed because the person entering cannot currently eat ice cream. …”

Ideally, but what if you surveyed it during winter, when clearly closed, but there was not enough info to specify the full & correct opening_hours ?

Though, that's simpler, when it's seasonal but merely closed at the moment. Either omit the tag, tag that it's closed right now (today's date), and/or set note:opening_hours with an explanation (preferably along with a fixme:opening_hours=[something like; #SurveyMe during summer]

This actually contradicts your point about hotels; when they're merely closed for the winter, no need to mark them as disused.

In some cases, they were undergoing construction / renovation, with an unknown (to me) completion date (for reopening). Yet, it's still a hotel.

As for building=hotel, that's different & depends. Especially considering building:use=* .

“What can I do to focus on the change record and the added value of "24/7 open" and "24/7" that you have seen?”

I don't understand this question. Rephrase?
Lee Carré (2022-01-30 04:55:48+00:00): There's a whole bunch of much weirder values for opening_hours: http://taginfo.osm.org/keys/opening_hours#values
Some of which seem to be invalid syntax.

Might I suggest fixing those, instead?

Or, better, survey your local area.
Lee Carré (2022-02-26 11:13:13+00:00): Reverted: http://www.osm.org/changeset/116778932
danieldegroot2 (2022-01-24 09:07:40+00:00): Hey ygeffens,

Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privebericht.

Feedback; Even goed kijken wat er staat op het onderbord;
https://wiki.openstreetmap.org/wiki/NL:Jaagpad

Staat er iets niet bij op bovenstaande pagina, kijk dan hier;
https://wiki.openstreetmap.org/wiki/NL:Key:access#Vervoer_over_land

MVG,

Daniel

Namens de OSM Community
Lee Carré (2022-01-24 23:48:17+00:00): Seems like an automated / mechanical edit, without a cited discussion, to me.
CAM-Gerlach_Repair (2026-06-09 10:39:08+00:00): Cleaned up SEO spam and applied correct tagging for World of Smoke & Vape POI in changeset 183868273

https://osm.org/changeset/183868273
danieldegroot2 (2022-01-24 09:12:41+00:00): Feedback; Standaard staat alles op =yes. Als dit het geval is hoef je dit niet aan te geven.
Jrachi (2022-01-24 21:59:44+00:00): Ciao.
Fa piacere vedere chi si dedica alla correzione degli errori!
Però fai attenzione a modificare delle relazioni!
Hai interrotto la relazione del percorso a catasto ECNAF140000.
Ho già sistemato.
Ivo, Jrachi
sbelemey (2022-01-26 05:54:55+00:00): Hi, Jrachi!
thanks for your feedback. Sorry i made a mistake, but i can't fix it, because the changes were made after me. https://pewu.github.io/osm-history/#/way/817898060
could you fix the error in the cadastral path ECNAF140000?
best regards, sbelemey
SomeoneElse_Revert (2022-03-01 18:43:00+00:00): This changeset has been reverted fully or in part by changesets 117961003, 117970393, 117965218, 117980733 where the changeset comment is: Following a complaint about invalid edits, and a lack of decent reply (see https://resultmaps.neis-one.org/osm-discussion-comments?uid=414659 , https://www.openstreetmap.org/user/Max_Kritic/blocks ) reverting changesets where _only_ osmose was used.
danieldegroot2 (2022-01-24 09:37:10+00:00): Feedback; Benaming garage lijkt me te kloppen op basis van luchtfoto.
Het kunstwerk laat ik over aan je lokale kennis, ik kan er niet direct iets over terug te vinden (alleen als referentie).
ygeffens (2022-01-24 09:47:41+00:00): Het kunstwerk is echt weg :-) Is ook te zien op google streetview.

Nu had ik die 2 gebouwen als garage ingeschreven. Is dat eigenlijk 'nuttig' zulke wijzigingen? Mij lijkt van niet, maar ik kno het niet laten :-)
danieldegroot2 (2022-01-24 16:11:51+00:00): Ah, nou dat zou ik als referentie kunnen gebruiken, maar echt gebruiken mogen we privé-data zoals Google niet. Bovendien lees ik het liever zwart-op-wit, zeg in een nieuwsbericht (feiten mogen we al sneller gebruiken), en niet dat die even naar de apk is bewijze van.

Altijd handig om te weten wat wat is. We hebben in OSM veel 'nuttige' data. Als je een tijdje hebt gemapt zal je zien dat je binnen de kortste tijd putdeksels in kaart begint te brengen e.d. ;)
喵耳引力波 (2022-01-24 08:36:47+00:00): 抱歉！可能我在#116528391  之后编辑时间拖的比较长

在 #116529302 这个changeset中和您出现了冲突

我另开JOSM在
https://www.openstreetmap.org/changeset/116529920
中上传了我的编辑

因此还请您检查一下您的编辑是否正确保留，我今天24点前不会再动方圆一百公里以内的区域，所以您可以放心检查和编辑！

给您添麻烦了！十分抱歉！
tux67 (2022-01-24 11:58:25+00:00): Hi,
die einzige Quelle, welche du bei diesem  angibst, sind die von ID automatisch hinzugefügten Luftbildquellen.
Im Sinne der OSM Community und einer nachvollziehbaren Änderung ist das aber nicht ausreichend und ich möchte dich bitten deine Quellen beim Upload anzugeben.
https://wiki.openstreetmap.org/wiki/DE:Good_changeset_comments
iD hat dafür extra ein Source Feld, das beim Upload gefüllt werden kann.
Danke & Gruß tux67
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/116529893
Fulnir (2022-01-24 12:46:12+00:00): Da ich lokale Kenntnisse habe, habe ich das optionale Quellenfeld ignoriert.
tux67 (2022-01-24 12:51:37+00:00): Eine interessante Begründung - gerade wenn lokale Kenntnisse die Quelle sind solltest du es reinschreiben um Nachfragen zu vermeiden. 
Gerade bei access=private gehen nach diversen, nicht begründeten Weglöschungen und Zutrittsbeschränkungen von Anliegern schon mal die Alarmglocken an.
Gruß
tux67
Fnkok (2022-01-24 08:55:46+00:00): 问题已解决，可以继续编辑了，感谢提醒：）
Patr1k_P (2022-01-25 15:24:26+00:00): "name" sa tam nepise, len ak by existoval nejaky skutocny nazov...ze je to studnicka je vyjadrene znackou natural=spring
Patr1k_P (2022-01-25 15:27:32+00:00): a myslim ze ani wetland tam nepatri, to sa tyka druhu mokradi...
Dodko (2022-02-03 11:43:25+00:00): Email je s preklepom.
Pan Perníček (2022-02-03 11:50:56+00:00): Dobrý den,
děkuji za upozornění, chybu jsem upravila.
aceman444 (2026-07-14 14:23:22+00:00): Je toto teraz bludisko attraction=maze ? A je to zaroven aj labyrint maze=labyrinth ?
*Martin* (2026-07-15 06:01:46+00:00): Nie je to idealne otagovane. Skus to prosim otagovat podla https://www.freemap.sk/#show=gallery-viewer/28958
aceman444 (2026-07-15 07:16:08+00:00): Uf, tak to je zvlastna vec.
KVI0n (2022-01-24 08:59:10+00:00): correct: #mbx_netherlands_roads
Richard (2022-01-24 09:29:27+00:00): Buggeration, forgot to close the changeset before starting something new. Sorry about that.
danieldegroot2 (2022-01-24 10:30:47+00:00): Hey KVI0n,

Just fyi, your changeset comment is inaccurate. You've only created new nodes in this changeset, not connected multiple ways, so your changeset comment could be i.e. "extended road".

Also, please use "PDOK aerial imagery Beeldmateriaal.nl 25cm latest" when working in the Netherlands.

Regards,

Daniel
KVI0n (2022-01-24 11:16:26+00:00): Hi Daniel! 
Thanks for the feedback, I'll take your advice into account. 
Regards, Liliya.
Pierre Van Tichelen (2024-04-05 02:57:46+00:00): Hello,
This lift doesn’t exist. Why did you add this ?
danieldegroot2 (2022-01-24 09:57:41+00:00): Hey kaartenliefhebber,

Dit mag gewoon voor zover ik weet. Poorten worden meestal als knoop gemapt op het hek en het type is dan af te leiden van het hek, dus de meeste mensen nemen de moeite niet.
(Er zijn overigens tags om het type poort te beschrijven;
https://wiki.openstreetmap.org/wiki/Tag:barrier%3Dgate#Gate_details )

Groet,

Daniel
danieldegroot2 (2022-01-24 09:58:57+00:00): PS: Je kan er ook gewoon voor kiezen "material" te gebruiken, dit is voor alle objecten te gebruiken.
kaartenliefhebber (2022-01-29 13:15:59+00:00): hoi Daniel,

ik twijfelde ook wel bij het weghalen, want het kan ook weinig kwaad, was meer vanwege zo'n osmose check, maar die zijn wel vaker onterecht, of discutabel. 

zal ik er dan een gate_type van maken ipv een fence_type?

groeten
Karel
danieldegroot2 (2022-01-29 13:54:23+00:00): Dat is goed.
Jakka (2022-01-25 08:02:21+00:00): Ici un zoo, pas de nom, site ? Heure ouvertures ?
bxl-forever (2022-01-25 11:39:28+00:00): I fixed it.

User wrote "réserve naturelle" in her changeset; it looks like she clicked on the wrong preset in iD.  Correct tagging is leisure=nature_reserve.

That should be fine now.
danieldegroot2 (2022-01-24 10:12:42+00:00): De tag "surveillance" is om aan te geven waar de camera staat;
https://wiki.openstreetmap.org/wiki/Key:surveillance
Gebruik waar dat kan een van de waarden op bovenstaande pagina.

Pas je dit ook even aan voor de camera's die je hebt toegevoegd?
Voor andere tags kan je de veelgebruikte waarden ook terugvinden op de wiki.

Groet,

Daniel
Dodko (2022-01-24 11:12:00+00:00): Tri chotáre je zaniknutý historický geografický názov.
https://zbgis.skgeodesy.sk/mkzbgis/sk/zakladna-mapa/detail/zbgis/98/3073?pos=48.290209,17.159001,18
victorio sk (2022-01-24 11:36:41+00:00): Prečo ho ale opätovne nepoužiť, keďže ten vrchol iný názov aj tak nemá? Je s tým nejaký názvoslovný problém? Je tam aj vrcholová kóta s geodetickou tyčou vo výbornom stave, o ktorý sa predpokladám už asi nik nezaujíma, keďže ten bod figuruje ako zaniknutý, čo je na škodu.
victorio sk (2022-01-24 11:41:11+00:00): https://zbgis.skgeodesy.sk/mkzbgis/sk/rgb/detail/rgb-sts/6/184084?bm=zbgis&z=8&c=19.530000,48.800000&pos=48.290211,17.158984,16
cxc (2022-01-26 11:39:25+00:00): Buongiorno, credo che la dicitura riportata nel Building:private_mountain_refuge (way 700636023) non sia corretta. Vedi la wiki.
saluti
Bagoo (2022-01-26 16:53:44+00:00): mountain_huts or muntain shelter..in ogni caso privato e gestito privatamente da "Associazione Veterani della Montagna
cxc (2022-01-29 14:19:48+00:00): Ciao, le definizioni delle chiavi sono definite nella wiki... https://wiki.openstreetmap.org/wiki/Buildings
è opportuno seguire le indicazioni comuni. Esistono altre chiavi per inserire altre definizioni. Ho notato che hai anche dato definizioni alla chiave access... access per come l'ho interpretata sta a definire se l'accesso sia limitato (e anche qui ci sono diverse definizioni) ma il grado di pericolo ha altre chiavi. Puoi chiedere sui vari canali in caso di dubbio. 
https://www.openstreetmap.org/help
buona serata
danieldegroot2 (2022-01-24 10:47:43+00:00): Feedback;
Niet gaan slepen met de kaart, de informatie op https://www.openstreetmap.org/node/2683139882 staat nu op https://www.openstreetmap.org/node/2683176028 wat onderdeel van het gebouw is.

https://www.openstreetmap.org/node/1998558467
Als je de adres-tags uit de BAG
addr:*=
source=BAG
source:date=
laat staan kan je de POI-tags zoals
phone=
website=
gewoon verwijderen.
(POI; Point of Interest zoals bar etc.)

Ik neem aan dat de sluiting definitief is en niet tijdelijk.
eggie (2022-01-24 11:25:11+00:00): Hoi... adresnode 11 heb ik teruggeplaatst...  De rest van de cafeinfo op het BAGadres na heb ik verwijderd.
Schade krijg je als je selecteert met de linkermuis en dan gaat schuiven. 
Dan schuift niet alleen de kaart maar soms ook een node met alles wat daar aan vast zit. 

Gr eggie


Dit waren je edits https://overpass-api.de/achavi/?changeset=116534462
timmito (2022-02-07 15:16:26+00:00): Hallo Hermann001, ich bin immer dankbar für deine Arbeit mit georeferenzierten Fotos, in diesem Fall hast du jedoch die Grenzen des Naturschutgebietes verändert, die zuvor ein Nutzer mit Genehmigung zur Übernahme von amtlichen Daten bearbeitet hat. https://www.openstreetmap.org/way/244608415/history Sind das jetzt also die Grenzen des Naturschutzgebietes oder des Waldes?
Hermann001 (2022-02-09 10:41:02+00:00): Hallo Timmito, ich habe den Übergang des Rothschildparks zum Wald verfolgt. An einigen Stellen habe ich dazu den Zaun fotographiert, der die Grundstücksgrenze des Rothschildparks ist. Und dort hin habe ich die Grenze des Burghains verschoben. Die Bäume des Waldes gehen tiefer in den Park hinein, gehören dann aber zum Rothschildpark. Deswegen würde ich die Grenzlinie nicht am Wald darstellen, sondern  an den tatsächlichen Zäunen. Was würden Sie meinen?
eggie (2022-01-24 11:32:37+00:00): Dag paver.. 
Je tapijtplein zit geplakt aan alle wegen. Beter is het om zoiets los te laten en gewoon hier de straten in te tekenen. 
Een straatnaam doe je met name=  
Wat jij gebruikt addr:street is voor woonadressen.
De placenode zal ik verwijderen. Die is voor andere doeleinden.

Je pad loopt dwars door een gebouw. Zie foutmelding warnings:crossing_ways:building-highway
Tip Goed inzoomen. 
MVG
eggie
eggie (2022-01-24 11:52:46+00:00): Elk begin is moeilijk.
Het plein heb ik aangepast.. De placenode en adres verwijderd. Die garage op een node gezet incl ingang. 
gr eggie
eggie (2022-01-24 12:45:36+00:00): surface=bestraat is geen geldige tag..
Ik heb dat aangepast naar paving_stones. Probeer steeds in de wiki op te zoeken hoe te taggen.
Ook is een gedeelte van de Koningsloper geen wandelpad, maar iets anders. Ik heb het conform de andere wegen omgetagd naar woonerf. 
Incline heb ik verwijderd. 
MVG
eggie
Temat-Droga (2022-01-26 07:42:56+00:00): Tak jest, nie wiem czemu ktoś to wycofał akurat wtedy gdy wprowadzono wykaz xD
eggie (2022-01-24 11:34:27+00:00): incline =   is iets voor bergpaden en steile hellingen/ trappen...  Dat beter niet toevoegen hier.

Je pad loopt door een gebouw.
warnings:crossing_ways:building-highway

eggie
user_5359 (2022-01-24 14:44:56+00:00): Willkommen bei OSM! Die Umbenennung des Hauses "Pflege-/Heimdirektion" zu "Pflege- und Heimdirektion" ist keine Begründung das Gebäude komplett zu löschen und neu zu zeichnen. Wurde es denn neu gebaut (z.B. ohne den Innenhof)?
ANCELCHONG (2022-01-24 10:50:24+00:00): #ASEC # Youngmappers
Becky Candy (2022-01-24 11:41:40+00:00): Already fixed
            ---
            
            Published using OSMCha: https://osmcha.org/changesets/116535540
SekeRob (2022-02-01 11:02:26+00:00): 8 days later Osmose again reports a gap in the FL7 route Rome-Minturno. Don't have/know the tools to pinpoint where, the manual scanning is a crime to do in ID, to include if a section was tagged twice. Cumbersome to say the least.
clay_c (2022-02-10 15:42:25+00:00): Hi,

I've reverted this changeset because the Texas Highway Designation Files list this as a Farm-to-Market Spur, not a State Highway Spur [1]. Signs for both of these networks look identical, which I'm sure is confusing.

[1] https://www.dot.state.tx.us/tpp/hwy/fm/fm0149.htm
clay_c (2022-02-10 15:42:35+00:00): https://www.openstreetmap.org/changeset/117251329
A_Prokopova_lyft (2022-02-10 16:48:06+00:00): Hi,clay_c
I’m Anastasia, and I’m a mapper on the OSM team at Lyft. I’m sincerely sorry for this mistake, thank you for bringing it to my attention. 
While making edits with the relation I was guided by the sign visible on the Mapillary (https://www.mapillary.com/app/?pKey=886835558843297&focus=photo&lat=30.202864798575&lng=-95.680142180987&z=17&x=0.6906023690502407&y=0.5271993214124768&zoom=0 ), and different route markers misled me.
Thank you for the clarification and the changes you made. I appreciate your feedback and will take into account the information in order to avoid similar errors in the future.
Best regards,
Anastasia
clay_c (2022-02-20 18:32:09+00:00): Hi Anastasia,

After discussion with other local mappers, it became clear that roads like these should be tagged according to the visible signage, regardless of the legal designation. I made a changeset here [1] to retag network=US:TX:FM:Spur to network=US:TX:Spur statewide, while adding a note about their legal designations. Sorry for the confusion.

[1] https://www.openstreetmap.org/changeset/117547164
A_Prokopova_lyft (2022-02-21 10:49:56+00:00): Hi,clay_c
I really appreciate your input on this case and I'm glad that the question was successfully resolved. We will take into account this information for further edits in this region. 
Thank you for the clarification and for the edits you made.
bxl-forever (2022-01-25 11:13:19+00:00): Thanks.
I made small changes to your edit because there was some confusion with the building structure and you added some information twice.  It should be fine now.
BCNorwich (2022-01-24 13:10:57+00:00): Hi, Welcome to OpenStreetMap.

The tag addr:city=??? should contain the postal city name, as per Royal Mail, not the village name.

Regards Bernard.
Sandal man (2022-03-02 21:07:51+00:00): Gracias por tus ajustes en OSM pero por favor no dibujes un camino encima de otro o los planificadores de rutas se confundirán.
te corregí los errores
Saludos Jan
mijano (2022-03-03 22:03:23+00:00): Hola, gracias por las correcciones. ¿Podrías ponerme un ejemplo de lo que me indicas? Es que no estoy seguro de entenderte bien, y es por no repetir los mismo fallos
Sandal man (2022-03-03 22:40:17+00:00): Hola, Básicamente, cuando dibujas un nuevo camino, no tienes que dibujar sobre un camino existente.
Lo mejor es dibujar la nueva parte, conectarla a la carretera existente y más adelante dibujar una nueva parte nuevamente.
O corta el existente en unas pocas piezas y cambia el nombre de las piezas.
Espero que entiendas esto después de la traducción con Google :-)
https://www.openstreetmap.org/way/682012307
https://www.openstreetmap.org/way/1036662078
Habías conectado estas dos piezas sobre la carretera existente.
mijano (2022-03-04 18:57:28+00:00): De acuerdo, entendido. Muchas gracias