piebro/osm-data huggingface dataset:
tesp (2018-11-01 13:42:08+00:00): Oops. I thought I checked every building before submitting this. I apologize. It is fixed now.
viloan (2018-10-31 18:58: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!
MyrikLD (2018-11-02 16:55:34+00:00): Точка 6027205968 есть на официальном сайте Ганны.
https://www.ganna.by/torgovaya-set/firmennye-magaziny-ganna/#map

Точка 6027206324 тоже есть, но местоположение еще уточним
LLlypuk82 (2018-11-02 17:09:03+00:00): 6027205968 — в реальности это https://www.openstreetmap.org/node/1144549895

6027206324 — то, что отмечено — не существует

на сайте может быть всё, что угодно, в том числе вот эта ерунда: https://www.openstreetmap.org/node/6027204765
удаляю в очередной раз и очень прошу больше не создавать (то, чего нет, не было и нет в реальности)
nevw (2018-11-01 08:39:00+00:00): Hi
I removed the apartment node placed on the footway as these buildings are already mapped and tagged correctly.
GerdP (2018-11-01 16:16:44+00:00): Hi and welcome to OSM!
Please be very careful when mapping coastlines. The direction of the way is very important, land must be on the left, sea on the right. I am correcting some of these islands now. See also
https://wiki.openstreetmap.org/wiki/Tag:natural=coastline
Happy mapping!
viloan (2018-10-31 20:19:39+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!
Nutchanon Wetchasit (2018-11-04 05:36:35+00:00): Hello there, welcome to OpenStreetMap. It's always nice to see new surveying contributors.

Regarding your edits, please note that what you are doing is *not* a proper way to add multiple-language place name to a POI in OpenStreetMap [1]. Read more at:

- <https://wiki.openstreetmap.org/wiki/Multilingual_names#Thailand>
- <https://wiki.openstreetmap.org/wiki/Key:name>

In the iD editor you are using, the main `Name` field is for the local language (Thai), or the language that is written biggest on the sign of that place.

To add a different language, click `[+]` button at the right of Name field, the "Multilingual name" box will appear, which you can select a new language ("English") and type in the new English name.

For maximum compatibility to all OpenStreetMap-related software, you should also repeat what you just filled the main `Name` field in another "Multilingual name" box too, with appropriate language selection (e.g. "ไทย").

When done correctly, you should see something like this in your editor:

| Name
| ตลาดอุดมสุข
| 
| - Multilingual name
|    English
|    Udom Sok Market
| 
| - Multilingual name
|    ไทย
|    ตลาดอุดมสุข

Please fix your edits.

P.S. If you are worrying about not seeing English name on the map, there is an alternate rendering of OpenStreetMap that displays both Thai and English name at once, here:

<http://thaimap.osm-tools.org/>

[1] The act of intentionally adding wrong data to make enhance a specific view of the map is called "Mapping for the Renderer" <https://wiki.openstreetmap.org/wiki/Tagging_for_the_renderer>. It is looked down upon; since it wrecks havoc in other applications that use OpenStreetMap data.

In this specific case, the edit is breaking satellite navigators' ability to display POI in user's configured language.
Nutchanon Wetchasit (2018-11-04 05:40:43+00:00): The multilingual tagging issue aside, is "อุดมสุข" really officially written there as "Udom Sok" in English?

Because to me, it seems that the correct one should be either "Udom Sook" (with double 'o') or "Udom Suk"; otherwise, the name would pronounce "อุดมศก" which carries a different meaning.
Nutchanon Wetchasit (2018-11-04 05:52:16+00:00): On another note, you should also mark the "ตลาดอุดมสุข" building as a market too, so that people could find it when they search for a specific type of place.

In your editor, select the building, expand the "All tags" section at the bottom of the sidebar, and click `[+]` button at the bottom of the tags table.

Once the new row appears, fill "amenity" in the first cell, then "marketplace" in the second cell.

After doing this and saving the edit, wait few minutes, and refresh the map; you would see a magenta-colored vendor booth icon above the building name- which indicates that the POI is a market.
eggie (2018-10-31 23:34:41+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privébericht.
eggie (2018-10-31 23:36:59+00:00): Wonderlijk.. plots een andere naam?
eggie (2018-10-31 23:37:48+00:00): Dit was je edit.. https://overpass-api.de/achavi/?changeset=64059420
eggie (2018-11-01 07:58:16+00:00): Wellicht beter dan
name=Bloedkei of Bloedsteen
name:en=Bloodstone
Nu is de Nederlandse naam verdwenen.
MVG,
Eggie
eggie (2018-11-01 09:31:05+00:00): Ik pas wat aan
natural  = stone  op een node  was al de juiste tag. Alleenstaande grote steen of rotsblok  .. ook de naam.. name=Bloedsteen alt_name=Bloedkei
Hier hoort ook geen adres op.
Vitru (2018-11-05 19:17:01+00:00): Hi NKA,

you should not have reverted me: Now Fredrik Lindseth has deleted all your bad features: https://www.openstreetmap.org/changeset/61372458

I feel disrespected by you not answering me at https://www.openstreetmap.org/changeset/60256692

Kind regards
freebeer (2018-11-07 14:42:28+00:00): this changeset has added tagging not in Tuebingen, but to the junction of two roads in Bruck an der Leitha, austria, which is obviously wrong.
freebeer (2018-12-10 08:36:04+00:00): This changeset has been reverted fully or in part by changeset 65335823 where the changeset comment is: undo buggy addition of unrelated tagging nodes worldwide intended for polygons in Tuebingen germany via a defective gateway
5m4u9 (2018-11-05 21:09:20+00:00): hola, gracias por seguir mejorando el mapa. cambié de categoria a los salones de eventos para que se muestren bien...
nevw (2018-11-01 08:43:40+00:00): Hi 
I added natural=water to your edit.
https://learnosm.org/en/
SpencerJaquish (2018-11-01 20:30:53+00:00): Test
thermo_nuclear (2018-11-07 22:59:18+00:00): Это ещё что такое? То, что на въезде стоит кирпич, не отменяет того факта, что это улица.
SanchouZ (2018-11-21 10:49:01+00:00): С одной стороны кирпич а с другой ввобще всем закрыт проезд
GerdP (2018-11-02 16:06:32+00:00): Hi!
You used natural=coastline here but the Markermeer is a natural=water.
https://www.openstreetmap.org/relation/49368
See https://wiki.openstreetmap.org/wiki/Tag:natural=coastline
SpencerJaquish (2018-11-01 20:24:01+00:00): Test
FinB2000 (2019-03-22 10:04:53+00:00): Thank you for adding houses in Newport. Looking forward to seeing more of them on the map :)
robertkupis (2019-03-29 10:24:58+00:00): I'm glad you enjoy it ;) . Thanks for your kind words.
SpencerJaquish (2018-11-01 22:06:05+00:00): Test
freebeer (2018-11-29 15:10:09+00:00): Mojn zmoore, moin moin Spencer, e ciao Team Lyft...

i have taken a closer look at this missing section of the cycle route (found earlier today in a different changeset comment), as it has undergone complex editing in the past month and was not so easy to analyse at sleep-deprived discovery, as were the bus routes (broken much more recently).

i believe this is the problem edit, made in iD editor.

if you look below at the listing of the two ways, the original 2234... revision 6 of cali ave was split in two, leaving a very short original segment southwest, intersecting the separate bike path.  that still remains today as part of the cycle route:

Part of

    Relation Dumbarton - East - West Connector (1109585)

the longer segment looks to have then been split repeatedly into short segments such as the next changeset visualised at
https://nrenner.github.io/achavi/?changeset=64060805
and so on.

it is my guess that we are seeing a bug in iD that i have not yet read about (i spent last night trying to read and learn about what issues iD has in editing routes like this, and could only understand there is an ordering issue which i do not believe is at all applicable here).

it appears that iD splits a way that is a member of such a relationship and at least sometimes, loses one (maybe more, not yet spotted by me?) of the way relations - i am guessing from the newly-created segment as here, that being in this case the longest one.

well, i have no conclusions, i just wanted to present the results of my research and hope someone from osm with far more knowledge of routes like this, or of iD internals, will jump in here, even if i am not sure how likely this changeset comment is to attract any attention.

And i don't know where the best way to find these mapper experts is, perhaps the general questions forum...  we will see.  :-)

yours &c.
ggando_lyft (2018-11-30 16:46:36+00:00): Hi freebeer, 

I'm Gizelle and work on Lyft's OSM editing team. 
Thank you so much for telling us your research on these broken relations. We used achavi, that you linked in your comment to locate the broken cycle route and using iD Editor to correct it. 
We have been researching relations and our team will be undergoing training to avoid future issues. The achavi visualization tool that you provided was helpful in finding issues, and we hope to use this and JSOM to validate our changes moving forward.
If there are any experience mappers with similar issues, we appreciate feedback and the opportunity to learn from you! 
Thank you again, freebeer, and I hope you get some well-deserved sleep. 

Best, 
Gizelle :D
Ryzen (2018-11-02 21:26:01+00:00): "Traced BDOrthoIGN" is the source, but for this there is an separate input field. May you please use the changeset comments to state what you've mapped?
eggie (2018-11-01 07:51:26+00:00): Dag Steltenpower... Je straat Dieze is goed gelukt. Hij zit alleen vastgeplakt aan de landuse=residential van Raalte. Dat is de reden dat je editgebied zo groot is geworden. Plakken kun je voorkomen door als je tekent de linker Alt-toets in te houden. 
Ik zal de weg losmaken van de landuse.
MVG,
Eggie
Bickendan (2018-11-12 21:07:50+00:00): Why was this changed? It is signed as 'Salmon River Hwy' at the junction with OR 219.
Adam Schneider (2018-11-13 06:07:55+00:00): I interpret that sign to mean "this way TO the Salmon River Highway." No one typically refers to it by that name until west of McMinnville.  (And "Salmon River Highway No. 39" is an ODOT designation that is unknown to the general public, and putting it on the map would just be confusing; see https://highway.odot.state.or.us/cf/highwayreports/road_parms.cfm)
Bickendan (2018-11-14 08:30:27+00:00): While I completely disagree with your interpretation of that sign (the US 20 junction from I-5 has 'Santiam Highway' on the sign), I actually do agree with the rest of your assesement. Perhaps the Salmon River Highway no. 39 designation be added as an alt tag instead of the format I used to begin with? I do believe it should be added but not as as the primary tag (Newberg-Dundee Bypass is sufficient for this until the final phases of the construction project are done).
Adam Schneider (2018-11-20 06:55:59+00:00): I did add "Salmon River Highway" as an alt_name tag on the bypass.  But let's leave "No. 39" out of it, since it's really only for internal ODOT use.
Mobilités Montpellier Méditerranée Métropole (2018-11-15 12:40:52+00:00): Bonjour,


Vous avez caractérisé des bretelles de voie express différemment 'trunk_link' et 'secondary_link' sur un échangeur de la RD66. Y-a-t-il une raison à cela ?
Bonne journée,

Emmanuel
_URUS (2018-11-16 20:46:49+00:00): Bonjour,

Les bretelles sont caractérisées ainsi car ce sont des voies d’accès. Ce sont des 
voies qui parte d'une route pour aller à une autre. (donc route quelconque vers voie rapide ou route quelconque vers route départementale). 

Je met highway : trunk_link car caractérisation de la route est plus précise, ce n'est plus une simple route mais c'est une voie d'insertion.  

S'il y a le moindre soucis je peut effacer les modifications apportées.
Leo Slager (2019-02-19 10:48:24+00:00): Volgens een opmerking op de kaart moet de hele zaak worden opgeschoven in ZO richting, zodat de N62 weer op het oorspronkelijke trace komt te liggen.
Wil je daar zelf mee aan de slag ?
A67-A67 (2019-02-19 11:35:39+00:00): Ik had destijds vooral de wegen die op construction stonden, open gezet en de busroutes daarop aangepast. 

Op dit moment staat de weg nog niet in de BGT. Ik zou daarop wachten om dubbel werk te besparen. Als het in de BGT staat, dan kan de weg exact uitgelijnd worden.
eggie (2018-11-01 08:40:55+00:00): Welkom bij OpenStreetMap. Ik heb een uitgebreid welkomstbericht met wat handige tips en links gestuurd als privébericht.
Warin61 (2018-11-11 05:38:34+00:00): Hi,
You and magrej are adding the same roads ... ! over the top of one another. 
See change set https://www.openstreetmap.org/changeset/64062247

I leave the two of you to work out what to do here. 

Secondly .. I don't think you can correctly determine the surface:grade from satellite imagery.
aleksaJov (2018-11-11 17:18:53+00:00): Hello,

I just fixed the duplicate way issue. Thank You for the information about this problem. Also, we did not have any conflict when dataset was in uploading process to server.

I removed surface:grade tag from that ways. My approach was simple logical, where is new asphalt road and good imagery surface:grade must be 3.

Regards,
Aleksandar
Warin61 (2018-11-11 05:38:13+00:00): Hi,
You and magrej are adding the same roads ... ! over the top of one another. 
See changeset https://www.openstreetmap.org/changeset/64062242


I leave the two of you to work out what to do here.
Alecs01 (2018-11-02 13:17:30+00:00): Ciao, ho cambiato il tagging in route=historic visto che è una linea non più in funzione https://wiki.openstreetmap.org/wiki/Relation:route#Others
seichter (2018-11-01 08:56:11+00:00): PLZ Zahlendreher (korr.)
fx99 (2018-11-01 10:06:57+00:00): danke!
viloan (2018-10-31 23:31:17+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!
viloan (2018-10-31 23:34:33+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!
Omnific (2018-11-01 18:27:26+00:00): Hey, good work. One thing: we use the fully unabbreviated names in OSM, so I'll expand it to Listening Avenue Northeast.
da5idr (2018-11-02 03:26:41+00:00): Got it Omnific, thanks, i'll not use any abbreviations in the future.

Da5idr
seichter (2018-11-01 09:01:38+00:00): PLZ 88353 (korr.)
YukonTramp (2018-11-05 21:25:50+00:00): Danke
seichter (2018-11-06 17:39:32+00:00): Keine Ursache.
Passiert mir manchmal auch. So angenehm es ist, wenn man gleichbleibende Angaben nicht immer wieder eingeben muss: Einmal nicht aufgepasst - danach immer falsch.
Trevor_1 (2018-11-01 01:03:47+00:00): *village
AgusQui (2018-12-29 22:38:09+00:00): Hola Ignacio, elimine las 2 lagunas que creaste en este cambio, por las imagenes satelitales parecen no existir, si es un error por favor hazmelo saber.
viloan (2018-11-01 02:25:50+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!
nevw (2018-11-01 08:56:41+00:00): Hi
be careful to get permission to use copyrighted site info
https://wanderstories.space/cape-pallarenda/
I don't think we have permission to use info from QTopo either which is part of QSpatial I believe. 
Old thread here:
https://lists.openstreetmap.org/pipermail/legal-talk/2016-October/thread.html#8553

The Data Catalogue has up to date info:
https://wiki.openstreetmap.org/wiki/Australian_Data_Catalogue
nevw (2018-11-01 08:58:30+00:00): Hi
be careful to get permission to use copyrighted site info
https://wanderstories.space/cape-pallarenda/
I don't think we have permission to use info from QTopo either which is part of QSpatial I believe. 
Old thread here:
https://lists.openstreetmap.org/pipermail/legal-talk/2016-October/thread.html#8553

The Data Catalogue has up to date info:
https://wiki.openstreetmap.org/wiki/Australian_Data_Catalogue
nevw (2018-11-01 09:04:27+00:00): Ooops, accidentally sent twice.
It is fine to hike all those trails, etc and add from your local knowledge and others efforts to survey them such as from gps devices or use the satellite imagery to assist.
Just don't copy from Google maps and other sources we don't have explicit permission to use.
Luen Warneke (2018-11-01 22:52:14+00:00): Thanks for your comment. I will heed your warnings about QSpatial (QTopo & Queensland Globe). 

I am the owner and author of https://wanderstories.space/. Those articles, maps & GPX files were created by me over time. 

I have also contributed a tremendous amount of local knowledge to theCrag.com, Google Maps and other platforms, mostly open source.
nevw (2018-11-02 00:43:03+00:00): Hi Luen
Thanks for putting that very useful data in to the osm.
Cheers
Nev
Supaplex (2019-02-06 16:54:15+00:00): 恭喜您完成第一次的地圖編輯！ 歡迎加入開放街圖，群眾共同參與，繪製生活週遭大家關心事物的共編地圖。以下是相關的參考資料，歡迎隨時指教與提問。

編輯須知
台灣的標示依循準則可參考 http://wiki.openstreetmap.org/wiki/Taiwan
常見的圖徵標示方式可參考 http://wiki.openstreetmap.org/wiki/Zh-hant:Map_Features
給Pokemon Go玩家的建議：https://wiki.openstreetmap.org/wiki/Tips_for_new_(Pokemon_Go)_mappers

台灣社群網站
台灣 OpenStreetMap 網站 http://www.openstreetmap.tw
臉書粉絲頁OpenStreetMap台灣 https://www.facebook.com/opestreetmaptaiwan/
台灣社群Facebook社團 https://www.facebook.com/groups/OpenStreetMap.TW/
郵件論壇 https://lists.openstreetmap.org/listinfo/talk-tw
Telegram OpenStreetMap Taiwan https://t.me/joinchat/Aqu2IgnTuIidMfREdNmomQ
Telegram OpenStreetMap Asia  https://t.me/OpenStreetMapAsia
Slack https://osm-tw.signup.team/

Happy Mapping!
Supaplex (2019-02-06 16:53:58+00:00): 恭喜您完成第一次的地圖編輯！ 歡迎加入開放街圖，群眾共同參與，繪製生活週遭大家關心事物的共編地圖。以下是相關的參考資料，歡迎隨時指教與提問。

編輯須知
台灣的標示依循準則可參考 http://wiki.openstreetmap.org/wiki/Taiwan
常見的圖徵標示方式可參考 http://wiki.openstreetmap.org/wiki/Zh-hant:Map_Features
給Pokemon Go玩家的建議：https://wiki.openstreetmap.org/wiki/Tips_for_new_(Pokemon_Go)_mappers

台灣社群網站
台灣 OpenStreetMap 網站 http://www.openstreetmap.tw
臉書粉絲頁OpenStreetMap台灣 https://www.facebook.com/opestreetmaptaiwan/
台灣社群Facebook社團 https://www.facebook.com/groups/OpenStreetMap.TW/
郵件論壇 https://lists.openstreetmap.org/listinfo/talk-tw
Telegram OpenStreetMap Taiwan https://t.me/joinchat/Aqu2IgnTuIidMfREdNmomQ
Telegram OpenStreetMap Asia  https://t.me/OpenStreetMapAsia
Slack https://osm-tw.signup.team/

Happy Mapping!
Supaplex (2019-02-06 16:53:25+00:00): 恭喜您完成第一次的地圖編輯！ 歡迎加入開放街圖，群眾共同參與，繪製生活週遭大家關心事物的共編地圖。以下是相關的參考資料，歡迎隨時指教與提問。

編輯須知
台灣的標示依循準則可參考 http://wiki.openstreetmap.org/wiki/Taiwan
常見的圖徵標示方式可參考 http://wiki.openstreetmap.org/wiki/Zh-hant:Map_Features
給Pokemon Go玩家的建議：https://wiki.openstreetmap.org/wiki/Tips_for_new_(Pokemon_Go)_mappers

台灣社群網站
台灣 OpenStreetMap 網站 http://www.openstreetmap.tw
臉書粉絲頁OpenStreetMap台灣 https://www.facebook.com/opestreetmaptaiwan/
台灣社群Facebook社團 https://www.facebook.com/groups/OpenStreetMap.TW/
郵件論壇 https://lists.openstreetmap.org/listinfo/talk-tw
Telegram OpenStreetMap Taiwan https://t.me/joinchat/Aqu2IgnTuIidMfREdNmomQ
Telegram OpenStreetMap Asia  https://t.me/OpenStreetMapAsia
Slack https://osm-tw.signup.team/

Happy Mapping!