piebro/osm-data huggingface dataset:
viloan (2019-04-18 00:59:34+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!
aharvey (2019-04-22 00:14:25+00:00): Can we not just use natural=cape for all points/headlands? If not can you distinguish what the difference between a point and a cape in OSM would be?
aharvey (2019-04-22 00:17:49+00:00): I want to delete place=locality, natural=cape is rendered by the default style and already used as the tag for many "Points". natural=point has no wiki page. So I think we should use natural=cape, as it's the accepted tag currently. In the future with the appropriate tagging proposal for natural=point it can be changed back.
Warin61 (2019-04-22 06:33:42+00:00): A 'cap' is into the sea (or water) and point can be overland .. 
I'd retain place=locality for rendering and natural=point for truth. 

Checking place=cap to see if it is a 'point' later on would be a pain, finding location and point is easy.
Warin61 (2019-04-22 06:45:56+00:00): errg cape not cap! Cap is in there too under natural .. no idea what that is.
aharvey (2019-04-22 06:54:31+00:00): Yeah sorry I should have clarified, I'm only talking about the ones over sea here like https://www.openstreetmap.org/node/4084216641
Warin61 (2019-04-22 07:02:13+00:00): Oh, yep go right ahead... :)
mvexel (2019-05-06 15:14:08+00:00): Hi njtbusfan, 
Thanks for helping work on the UTA transit relations. If you add new routes, please add them to https://wiki.openstreetmap.org/wiki/Utah/Transit#Utah_Transit_Authority_.28UTA.29 as well, and have a look at existing routes. 

I see you changed the name tag on many UTA bus routes to something that is more descriptive but doesn't match the official routes names from UTA. Can I ask after your rationale please? Are you local to the area? I would appreciate it if you would discuss sweeping changes like this before implementing them.

Thanks,
mvexel
mvexel (2019-05-06 16:13:13+00:00): I looked again at the transit route wiki and it states the recommended value as "<type of transport><reference number>: <from> → <to>	" which you also didn't follow. I am going to propose to discuss this on-list because I see you have been editing bus routes across the nation and others may be interested in weighing in.
mvexel (2019-05-06 16:44:52+00:00): I posted to talk-us, please see https://lists.openstreetmap.org/pipermail/talk-us/2019-May/019507.html
Mateusz Konieczny (2019-05-06 19:49:26+00:00): name tag is for names, only, not for descriptions

See https://wiki.openstreetmap.org/wiki/Names for more detailed info
stevea (2019-05-08 23:01:18+00:00): I add my voice to Mateusz that we use name=* as we document it our wiki.  And to and to Martijn's that if there is a wiki that keeps track of (or does its best to do so, as there is in this case) something like the status of a transit network, a state's railroads, a collection/tables of motorways/highways at a political level, etc., that before sweeping changes are made, these wiki should be consulted, followed and updated when required.  Thank you.
FransWillem (2019-04-19 17:47:38+00:00): Hello Emily,  Thanks for mapping on this desolate task. A remark. When you map highways, please restrict mapping to paths which are of influence to human activities. 
Please read the Wiki East african highways how to measure and tag highways.  Footpath don't belong to that. Path is sufficient. 
Try to avoid to map your highway in a way that it becomes a loop. This a faulty mapping.
Best regards and keep mapping
FransWillem (2019-04-19 17:55:34+00:00): Hi, Back again.  When you map a building, be sure it is a building. Mostly you can recognize a building on his form, round huts here are common, and the fact there is a shadow to see, very often you will see paths leading to them and the surface is  different ( lighter of color, sand color etc.)
Best regards
AINMcl (2019-04-18 06:42:45+00:00): Avenida Puerto Chacabuco no es el nombre correcto, el correcto es "Cruce Ruta 7 (Alto Baguales) - Puerto Aysén - Puerto Chacabuco"
jptolosa (2019-04-18 11:24:53+00:00): Y cuál es tu fuente?
viloan (2019-04-18 02:36:51+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!
GhostEye (2019-04-19 01:45:22+00:00): Hello viloan. Thank you for the helpful feedback! I look forward to corresponding with you in future and will defer to your expertise.
viloan (2019-04-18 02:45:32+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!
pitscheplatsch (2019-04-18 18:54:51+00:00): #failed #test ?

Bzw. sieht das nach Blödsinn aus.
aharvey (2019-05-10 07:26:16+00:00): +1

I just migrated to the existing tags from the node to your new way, to ensure we only have one object for the school.
Warin61 (2019-05-10 21:53:48+00:00): I should have got that myself... missed it sorry.
viloan (2019-04-18 03:34:36+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!
mavl (2019-07-21 15:47:14+00:00): This changeset was redacted. Reason: copyrighted data were used.
laurent-38 (2019-05-23 18:17:24+00:00): Hi, 
Thank you for your contribution. However, it would have been nice to move the buildings according to the aerial imagery too, in order to prevent erroneous intersection between ways and buildings…

And you need to create a point at the crossing between service ways and footways. (see https://www.keepright.at/report_map.php?schema=7&error=126606792)

Cheers
Laurent-38
yaswap (2019-05-24 06:58:49+00:00): Hi,

Thanks for looking into the edit. The editor might have turned off the building feature. That is why it got missed. Thanks again for reviewing it. We are updating the edits as per your suggestion. 

Please let us know if we need to add anything else so that it can improve the edit.

Regards,
yaswap.
laurent-38 (2019-05-25 16:03:50+00:00): Thank you for the quick fix, it's fine.
mavl (2019-07-21 15:47:17+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:47:21+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:47:24+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:47:27+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:47:30+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:47:33+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:47:36+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:47:39+00:00): This changeset was redacted. Reason: copyrighted data were used.
MikeN (2019-04-22 15:36:43+00:00): Hi, please be careful when dragging an entire way to re-verify all nodes along its length.   In this case, someone else wrongly connected power lines to roads, and as a result this road was distorted - https://www.openstreetmap.org/node/109712420#map=19/34.55825/-82.46793  .
mavl (2019-07-21 15:47:42+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:47:45+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:47:49+00:00): This changeset was redacted. Reason: copyrighted data were used.
abrensch (2019-04-21 08:51:48+00:00): Hallo Lokalfürst,

meine Netz-Recherche hat keinen Hinweis geliefert auf diese Sperrung der beiden Übergänge zur B49 Richtung Giessen.

Kannst Du mir helfen?

Danke und Gruss, Arndt
abrensch (2019-04-28 08:25:03+00:00): Nochmal Hallo,

Kannst Du bitte mal irgendwie Deinen Kenntnisstand beschreiben zur Talbrücke Dorlar. Den jetzt eingetragenen Zustand finde ich nirgends im Netz dokumentiert. Und das alles 2019 fertig werden soll, nicht 2022.

Danke und Gruss, Arndt
abrensch (2019-05-11 08:21:33+00:00): ich habe die sperren für die auffahrt auf B49 Richtung Giessen entfernt
Lokalfuerst (2019-10-30 12:19:36+00:00): Hallo Arndt,
das betreffende Strassensegment war sehr lange Zeit wegen Bauarbeiten gesperrt. Es Ist inzwischen wieder für den Verkehr freigegeben. Habe die Aktualisierung heute eingetragen.
Gruss
Lokalfuerst
PeanutButterRemedy (2019-04-27 05:25:35+00:00): This node has all of the traits of a poor SEO addition meant to game the system. One of those traits is creating a throwaway account that is never monitored for feedback. If this is not the case, please comment and we can help restore your addition.
PeanutButterRemedy (2019-04-27 05:25:13+00:00): This node has all of the traits of a poor SEO addition meant to game the system. One of those traits is creating a throwaway account that is never monitored for feedback. If this is not the case, please comment and we can help restore your addition.
FulanoHerminio (2019-04-22 17:22:04+00:00): Possible duplicate fire hydrants due Map4review false positives: nodes 6413254985, 6413254986 (discussion & details in Portuguese at https://lists.openstreetmap.org/pipermail/talk-pt/2019-April/001697.html)
viloan (2019-04-18 05:15:07+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!
Supaplex (2019-04-18 06:33:03+00:00): 也太厲害了找得到
            ---
            #REVIEWED_GOOD #OSMCHA
            Published using OSMCha: https://osmcha.mapbox.com/changesets/69330545
mavl (2019-07-21 15:47:51+00:00): This changeset was redacted. Reason: copyrighted data were used.
maraf24 (2019-04-18 11:30:35+00:00): "Publicznej Szkoły Podstawowejim. Maratończyków Polskichw Miłoszycach"
mavl (2019-07-21 15:47:55+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:47:58+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:48:01+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:48:04+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:48:08+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:48:11+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:48:14+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:48:17+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:48:20+00:00): This changeset was redacted. Reason: copyrighted data were used.
mavl (2019-07-21 15:48:23+00:00): This changeset was redacted. Reason: copyrighted data were used.
viloan (2019-04-18 06:00:21+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!
abakus_uploader (2019-04-18 22:30:36+00:00): (Wiadomość automatyczna)
Cześć!
Otrzymujesz ten komentarz, ponieważ dodałeś lub zmodyfikowałeś adres, który jest niepełny lub błędny.
Adres powinien zawierać minimum trzy znaczniki: addr:city=[nazwa_miejscowosci] + addr:street=[nazwa_ulicy] + addr:housenumber=[numer_porządkowy].
Wyjątkiem są miejscowości bez nazwanych ulic - wtedy stosujemy znaczniki: addr:place=[nazwa_miejscowosci] + addr:housenumber=[numer_porządkowy].
Bez poprawnego oznaczenia adresów, nie będą one brane pod uwagę przez wyszukiwarki, dlatego warto je dostosować do ww. schematu (w zależności od sytuacji).
Więcej informacji na forum: https://forum.openstreetmap.org/viewtopic.php?id=5632 - a pytania najlepiej zadawać tu: https://forum.openstreetmap.org/viewtopic.php?pid=681873
Pozdrawiamy!
eggie (2019-04-18 06:37:38+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privébericht.

.... Je zou de source=3dshapes nog kunnen aanpassen aan bv PDOK aerial imagery.
MVG,
Eggie
PeanutButterRemedy (2019-04-27 05:24:31+00:00): This node has all of the traits of a poor SEO addition meant to game the system. One of those traits is creating a throwaway account that is never monitored for feedback. If this is not the case, please comment and we can help restore your addition.
eggie (2019-04-18 06:44:19+00:00): Dag Rendier. BAG adresnode 7a zwerft nog rond hier zonder gebouw.
Wellicht even goed positioneren?
MVG,
Eggie
opendcc (2019-04-18 09:38:40+00:00): Hallo,

das ist ausgeschildert als Fußweg, Radfahrer frei. 

Servus Wolfgang
dvdhoven (2019-04-18 08:35:00+00:00): Kun je aub andere routes intact laten of herstellen? Ik heb nu al zo'n 7 routes hersteld na doorknipfouten door jou, allemaal changesets met dezelfde omschrijving.

Alvast bedankt,
Dick van den Hoven, die nog steeds niet snapt dat als je aan route werkt, je andere routes kapot maakt en niet hersteld.
Peter Elderson (2019-04-18 08:46:05+00:00): Dit snap ik niet, ik open bij knippen iedere keer alle relaties die daar lopen en gebruik het pijltjes-knopje bij elke relatie om de wijziging in de relaties door te voeren! Ik doe kennelijk nog steeds iets verkeerd.
dvdhoven (2019-04-18 14:10:44+00:00): Hallo Peter,

Ook als je het pijltjesknopje gebruikt hebt, kan de relatie nog buiten volgorde liggen. Je moet altijd daarna het routelijntje of routelijntjes in het venster controleren of die geen breuken vertonen. Is dat wel het geval, dan moet je even met het weggedeelte wat net ontstaan is, schuiven, of naar boven of naar beneden. Gewoon even proberen.
En verder nooit op 2 plekken tegelijk doorknippen. Bijv als je een brug maakt, dan is het verleidelijk om op beide brugknopen tegelijk door te knippen. De kans is dan groot dat er een blokje van 3 wegen precies omgekeerd wordt.
Succes

Vriendelijke groeten,
Dick van den Hoven
Peter Elderson (2019-04-19 06:15:02+00:00): Ik heb nog even goed gekeken naar mijn werkwijze. Voor enkele knippen moet het gewoon goed gaan, ik kijk normaal ook in alle getroffen relaties of "mijn" wegstukje goed geknipt is. Aangezien dat altijd het geval is kijk ik bij grote series (soms wel 15) niet alles afzonderlijk meer na. Bij de dubbele knippen heb ik dat juist niet zorgvuldig gedaan, haastwerk, ben ik bang. Die doe ik dan maar niet meer. Verder, in een hoop routes die ik zo tegenkom zitten al andere fouten. Het is niet te doen om alle fouten helemaal na te kijken en te repareren, dan zou ik nooit door de nieuwe/gewijzigde LAW of SP komen. Dan staat dus wel mijn naam in die route als wijziger, maar de fout is niet altijd aan mij toe te schrijven.
dvdhoven (2019-04-19 06:26:26+00:00): Hallo Peter,

In alle gevallen, die ik de laatste dagen onder handen heb gehad bij jouw changesets, betrof het rcn en rwn routes. En het rcn is in Nederland geheel foutvrij op één incomplete route na. Het rwn helaas niet, maar alle routes, die ik heb gerapareerd waren voor jouw changeset foutvrij.
Dus het argument van oude fouten gaat hier niet op.

Vriendelijke groeten,
Dick van den Hoven
Peter Elderson (2019-04-19 06:45:35+00:00): Shazbutt, zelfs dat ene smoesje kom ik niet mee weg!
alphensebezorger (2019-04-19 07:37:46+00:00): Ik heb eens wat zitten proberen met JOSM om uit te vinden wanneer je bij het knippen van een weg routes wel en niet kapot maakt. Mijn conclusie is er sorteerfouten kunnen ontstaan, wanneer de geknipte weg niet helemaal in het gedownloade gebied ligt. Je moet dan eerst een klein gebiedje downloaden rond de eindpunten van de weg. Alleen downloaden rond het punt waar je gaat knippen is dus niet afdoende. Vooral bij lange wegen loop je dus het risico dat het misgaat, als je kleine download-area gebruik.
dvdhoven (2019-04-19 07:54:17+00:00): Dat kan een reden zijn.
Een andere heeft met de richting van de route te maken. Dat kun je goed bij busroutes zien. Als er daar een knipfout is, zijn de routes de ene kant uit heel en de routes de andere kant uit stuk. 
Leo heeft in het verleden dit ook al eens bestudeerd.

Maar het feit blijft dat je - naar mijn idee - hier prima mee kan leven.
Als ik een weg doorknip, check ik alle routes en ik schuif - indien nodig - even met het wegstukje in de route en klaar is Klara. Het is gewoon een gewoonte aanleren. In het uiterste geval kost mij dat zo'n 5 minuten. Veel meer niet.
Het relatievenster is echt goed hierin, je ziet de routelijn en je ziet direct een verstoring.

Vriendelijke groeten,
Dick van den Hoven
Peter Elderson (2019-04-19 14:43:29+00:00): Dat van die lange wegen kan bij mij best gebeuren, ik doe meestal downloaden rond een gpx en dat garandeert niet dat alle te gebruiken wegen geheel binnen de bandbreedte liggen. Toch nog beter opletten en nakontroleren dus. En ik dacht nog wel dat ik op dit punt wel zo'n beetje volleerd was... Het wordt wel behoorlijk moeilijk om nieuwe routemappers te vinden. Als je dit soort dingen vertelt lopen ze meestal hard weg. Oudere mensen kunnen trouwens dat richting- en aansluitlijntje in relatievensters vaak nauwelijks zien, fysiek.
TZorn (2019-04-18 10:02:45+00:00): Hallo Julia,

verwende besser das disused:-Präfix (https://wiki.openstreetmap.org/wiki/DE:Key:disused:). Also ändere lieber das shop=jewelry in disused:shop=jewelry statt disused=yes hinzuzufügen.
stadt-lev-schaefer (2019-04-18 12:36:07+00:00): Hallo Tobias,

danke für die Hilfe. Könntest du mir sagen, ob es jetzt richtig ist?

Liebe Grüße

Julia
TZorn (2019-04-18 12:48:35+00:00): Noch nicht ganz. :-) Was vor dem Gleichheitszeichen steht, gehört in den key/Schlüssel, das dahinter in den value/Wert. 

Ich hab's mal korrigiert.
felipeeugenio (2019-04-18 15:37:04+00:00): Estimado. Muchas gracias por sus aportes.
Vemos que agregó mucha información muy útil sobre el hospital a la estructura del edificio.
La información está perfectamente ingresada, pero es propiedad del hospital, no de la estructura. Ahora pasé todo al recinto del hospital. Le agradecemos mucho.
saludos
user_5359 (2019-04-18 18:30:26+00:00): Welcome to OSM! I must deleted you node, because you aren’t a church and the node isn’t well placed. Don’t use the geocoder from Google (Google don’t allow this), look on the aerial image and mark the right building!
eggie (2019-04-18 07:12:59+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privébericht.
felipeeugenio (2019-04-18 12:42:26+00:00): Estimado. Muchas gracias por sus aportes.
Hemos visto como tiene muchas ganas de aportar, pero es necesario que conteste los mensajes o se una a la comunidad para conversar y enterarse de las convenciones que usamos en @OSMcl
Para este caso, el tag name= debe usarse para el nombre de la calle, la cual nosotros agregamos en base a los datos del INE y una visita que miembros hicieron a Puerto Aysen para levantar la numeración. Le quisiéramos preguntar como esta usted obteniendo los nombres que agrega.
Por otro lado, si el puente tiene un nombre característico por el cual es conocido, debe usarse el tag ref=
Saludos cordiales y quedamos atentos