OpenStreetMap
UMBRAOSM Training April 2022.
Dia: 27 de Abril de 2022.
Hora: 17:30hs (UTC3).
Link do Treinamento: https://meet.google.com/aib-ieae-oai
UMBRAOSM - União dos Mapeadores Brasileiros do Openstreetmap www.umbraosm.com.br
Boa Noite!!
Convido(a) a participar do nosso grupo de mapeadores OpenStreetMap da UMBRAOSM ( União dos Mapeadores Brasileiros do Openstreetmap) no aplicativo Telegram, o link da nossa sala e esse; https://t.me/grupoumbraosm
Baixe o Aplicativo do Telegram na Loja de Aplicativo Play Store e Instale o APP, em seguida entre em nossa sala atraves do link´s https://t.me/grupoumbraosm
aguardo você em nossa sala.
Acompanhe os Projetos da UMBRAOSM no OpenstreetMap na Wiki; osm.wiki/Umbraosm
Nosso Site; www.umbraosm.com.br
No Site voce encontra link para ser usado no Openstreetmap, como sites com informações do IBGE, Site que e usado como ferramenta para o OSM, Aplicativos GPS usando o OSM, Data de Eventos e etc.
A UMBRAOSM - União dos Mapeadores Brasileiros do Openstreetmap Tem Disponivel Para Mapeamento diversas tarefas no site da HOT que podem ajudar no Mapeamento do Openstreetmap em todo o Brasil.
Terefas para Mapear na HOT.
BRASIL - PRAIA ILHA DE ITAMARACÁ (PE) - EDIFÍCIOS https://tasks.hotosm.org/projects/12290
BRASIL -FERVEDOURO - (MG) - EDIFÍCIOS, ESTRADAS, PONTOS DE INTERESSE E ÁREA VERDE. https://tasks.hotosm.org/projects/12343
BRASIL -MIRADOURO - (MG) - EDIFÍCIOS, ESTRADAS, PONTOS DE INTERESSE E ÁREA VERDE. https://tasks.hotosm.org/projects/12344
BRASIL - VITORIA DE SANTO ANTÃO (PE) - MAPEAMENTO DE EDIFÍCIOS, ÁREAS VERDES E RIOS. https://tasks.hotosm.org/projects/12089
BRASIL - PALMARES(PE) EDIFÍCIOS, AREA VERDE E PONTOS DE INTERESSE. https://tasks.hotosm.org/projects/12266
Um forte abraço.,
Raphael de Assis
Recife-PE;
Membro do Coletivo UmbraOSM.
Coletivo UMBRAOSM - União dos Mapeadores Brasileiros do OpenstreetMap www.umbraosm.com.br
A seguito di una gradevole conversazione via email con un altro utente OSM, salvo qui tre utili URL personalizzati da usare come strato di sfondo in fase di modifica delle mappe sul sito OpenStreetMap con l’editor integrato iD. Clicca sull’icona “Impostazioni dello sfondo” nel menu verticale a destra, scorri la lista degli sfondi disponibili e scegli l’ultima voce “Personalizzato”, clicca sui tre puntini sulla destra, copia ed incolla uno degli URL personalizzati che trovi qua sotto ed infine clicca sul pulsante “OK” per salvare le modifiche ed iniziare ad utilizzare la nuova mappa.
1) True Ortofoto EagleFVG 2020
2) Vector CTRN (Carta Tecnica Regionale Numerica) 1:5000
3) Hillshade
After a pleasant email chat with another OSM user, I’m saving here three useful custom URLs to use as a background layer when editing maps on OpenStreetMap website with integrated iD editor. Just click on the “Background Settings” icon in the right vertical menu, scroll down the list of available backgrounds and choose the last item labeled “Custom”, click on the three dots on the right, copy and paste one of the custom URLs you can find below and finally click on the “OK” button to save changes and start using the newly added map layer.
1) True Ortofoto EagleFVG 2020
2) Vector CTRN (Carta Tecnica Regionale Numerica) 1:5000
3) Hillshade
During validation on HOT’s Tasking Manager giving feedback to mappers is crucial to enable improvement and encourage them to continue mapping. Beginners make the most errors, catching them as early as possible to provide constructive feedback can limit the quantity of errors and steer them in the right direction. This can lead to an overall increase in data quality.
I’ve outlined some of the most frequent feedback that I give to mappers while validating projects that involve mapping buildings as well as explaining the importance of intervening. Please feel free to use these comments in your own validation efforts on HOT’s Tasking Manager.
Today, we had an online meeting HOT Consultation on Measuring Our Collective Progress Towards Enabling Change. It was impactful on how to measure our collective program. Letting the government, private sector and humanitarian communities to see the need why they should help the actors(contributors of the open data source).
Alamat rumah Kg.jelki latarek, Kuala krai,18000 Kelantan
自宅近所のPOIや建物を隙間時間を使ってだいぶ追加しました。 ただここからどうしようかなとも思い始めています。建物の高さとか道路の幅とか測って入れるべき？あんまり使われないのも面白くないので、入れる意味があるのか分からず。
I’ve added many POIs and building near where I live. But I don’t know what to do next. Should I measure the height of buildings and the width of roads to have my neighborhood’s data more concise and completed? I wonder how much it makes sense if I do that.
Mapatona de Edifícios, Área Verde e Ponto de Interesse em Boa Viagem - CE - Brasil.
Mapathon in the City of Boa Viagem(CE) Brazil. Mapathon of Buildings, Green Area and Point of Interest in Boa Viagem - CE - Brazil.
Link de Inscrição:
https://docs.google.com/forms/d/e/1FAIpQLSeiJNulOSqVGr30TNnB0VSmbKY0DuFS_aAMhMj1R7NO4VtkxA/viewform
Como MAPEAR:
Instruções para o Mapeamento na Cidade de Nanuque/MG. Edificios: Muitos edifícios são muito próximos mas na verdade não se tocam. Tente mapeá-los o mais próximo possível, sem permitir que eles se conectem entre si ou com as ruas.
Caminho para pedestre: Selecione a tag “footway” - caminhos acessíveis apenas a pé.
Área Verde “Mata Nativa ou Relfa”: Selecione a tag “natural=wood” - Para Mata Nativa ou natural=wood para Relfa.
Ponto de Interesse:
Mapatona de Edifícios, Área Verde e Ponto de Interesse em Boa Viagem - CE - Brasil.
Mapathon in the City of Boa Viagem(CE) Brazil. Mapathon of Buildings, Green Area and Point of Interest in Boa Viagem - CE - Brazil.
Link de Inscrição:
https://docs.google.com/forms/d/e/1FAIpQLSeiJNulOSqVGr30TNnB0VSmbKY0DuFS_aAMhMj1R7NO4VtkxA/viewform
Como MAPEAR:
Instruções para o Mapeamento na Cidade de Nanuque/MG. Edificios: Muitos edifícios são muito próximos mas na verdade não se tocam. Tente mapeá-los o mais próximo possível, sem permitir que eles se conectem entre si ou com as ruas.
Caminho para pedestre: Selecione a tag “footway” - caminhos acessíveis apenas a pé.
Área Verde “Mata Nativa ou Relfa”: Selecione a tag “natural=wood” - Para Mata Nativa ou natural=wood para Relfa.
Ponto de Interesse:
I loaded the Plum Creek Timberlands, LP - commercial Forest relation, but I am struggling with tagging, something the Mapnik renderer will accept and recognize. From my reading of the wiki the boundary=Forest seems to have been the compromise to mapping recognizable Forest ownerships that might not fit in boundary=protected_area, leisure=nature_reserve. I gather the idea with the boundary=forest tag allows one to continue mapping natural=water, =wood, =wetland or land use=forest within the boundary. If I could find a conservation easement documented I would change to boundary=Protected_area, the more common tag. But the Mapnik renderer doesn’t recognize the boundary=Forest tag (osm.wiki/AreasTab) making it tempting to add or change to land use=forest and just excluding natural=*, water areas etc.
Anywho I added all the other tags I could come up with. This commercial Forest data came from the MDNR but for at least the large ownerships doesn’t seem all that up to date, it included some MDNR parcels probably recently acquired. Maybe the larger ownerships are too complex and small changes are hard for the MDNR to stay on top of since they rely on a legal description in the commercial Forest application process. The MDNR comm. Forest data includes owner, so in QGIS I pulled out the corporate owners and dissolved by owner for their holdings, figuring those might get imported first since they are biggest and most likely to remain in the program longer. Since they are adjacent, I got back into fixing up the Escanaba River State Forest and Copper Country State Forest units- I created one for Baraga, Crystal Falls for Copper Country and the Gwinn unit for Escanaba. I did some fixing while ways were in the Escanaba main relation, but got a glitch and it dumped them all out of that, so I went ahead and created a relation for Gwinn rather than reload them all back in to Escanaba. Wheh!
I’ve recently completed 365 days mapping and went past my 400,000th map change and thought I would reflect a little on it.
I never actually started out to do a year of mapping. I had signed up to OSM way back in 2016 but never made an edit. I don’t recall why, but the project probably seemed impenetrable to me back then. Fast forward to the middle of Covid I started to think about how I could volunteer my time and so I started editing on OSM.
It was only when I noticed I had gone over half a year that I thought a year of mapping was achievable and set it as a goal to myself. Some days were just one edit, some large edits.
Being honest, I would not recommend people to do a year of mapping as it became somewhat forced towards the end. Especially when I had missed a couple of days when I first started mapping so had to keep going for a few extra months to fill them in! I also went through phases where it looked to myself like substantial progress had been made and then periods where there I realised how much was still to be done in my area.
My initial OSM journey started with doing general StreetComplete and OSM editing/tinkering and then I settled on a main objective to map as much residential buildings in the large blank areas Aberdeen, Scotland. Why? To be honest, I don’t really know. Possibly because if they had not been done in over 11 years then they would never get done as people may not see them as a priority or fun to do. I also felt getting the main foundations of an addressable city would have many use cases. Along with the building outlines, I wanted to put down as much addressing as possible leaving just a street side survey to add the house number which can easily be done by anyone using StreetComplete or OSM.
Ich bin nach einiger Zeit wieder dazu gekommen, mich mit der Erfassung der Bahnstrecke weiter zu befassen. Da ich es jedoch bisher nicht hinbekommen habe, meinen Fieldpapers-Plan zu importieren, habe ich mich einem anderen Teilbereich zugewandt, den mir Dakon in einem Kommentar unter meinem letzten Blogeintrag vorschlug:
![Kommentar von Dakon am 18. April 2022 um 09:27 Uhr: "Es wäre schön, wenn du bei der Gelegenheit auch ein paar weitere Daten für das existierende Gleis erfassen könntest. Insbesondere die Position der Hektometertafeln [Anm. d. Verf.: Positionsschilder an einer Bahnstrecke, im Netz der DB üblicherweise alle 200m] wäre von Interesse.](https://i.imgur.com/BBpPNsG.png)
Da ich diese Daten für meine eigene Eintragungen als Referenz ebenfalls gut gebrauchen konnte, begann ich heute damit, die Positionen der Hektmetertafeln stückweise zu erfassen. Mein Vorgehen hier war relativ einfach:
Foto kenangan saya dirumah, Kg.jelkis latarek, kuala krai 18000, Kelantan, Malaysia
After some discussion we at Open Mapping Hub Asia-Pacific have decided not to limit both you and ourselves with weekly fixed time slots, and to support you on your OSM-related issues in an in-need basis.
So, whenever you need support on an OSM-related issue, feel free to contact me by sending a message, an e-mail or by filling out the appointment form and I will get back to you quickly. We can discuss the topic in writing, or set up a short call depending on our calendar availabilities and tackle the challenge together. I’d be very happy to support you in your learning process, and for most of the times the topics discussed are acting as refreshers for me, too.
Here are what was discussed during the past week:
You can directly write the name of the region as available in its name=* tag in OpenStreetMap in your queries since overpass syntax supports geocoding.
Suppose that you are interested in the parks of Istanbul. Writing leisure=park in Istanbul to the wizard will generate you this query:
[out:json][timeout:25]; {{geocodeArea:Istanbul}}->.searchArea; ( node["leisure"="park"](area.searchArea); way["leisure"="park"](area.searchArea); relation["leisure"="park"](area.searchArea); ); out body; >; out skel qt;You’ll see the use of geocoder to define the search area in the line:
{{geocodeArea:Istanbul}}->.searchArea;
One reason for it might be that your area of interest might be having the same name with other places in the World. It might be that the query brings data for a different place with the same name, or an empty dataset.
Another reason might be that the place name would consist of multiple words like New Orleans. In that case, while using the wizard, you must write the place name in apostrophes like:
leisure=park in ‘New Orleans’
ดอนพะงาด
Here is my attempt at mapping additional commercial forest lands in Michigan that are open to public access for hunting, trapping and fishing- starting with a relation for a blob of Plum Creek Timberlands, L.P., operating subisidary of Weyerhaueser: osm.org/relation/14051942
I am uncertain about the best course of tagging - these do not fit the boundary=protected_area, or leisure=nature_reserve tags for public lands. Maybe boundary=forest (osm.wiki/Tag:boundary%3Dforest). Currently tagged with landuse=forestry per- osm.wiki/Tag:landuse%3Dforestry
It appears with the approved new tagging scheme of boundary=forest, areas within would be mapped landuse=forest (plantations, managed forest), and natural=wood (unmanaged wood), natural=water, natural=wetland, eg.)
Anyone care to weigh in?
.png)
