Yesterday morning, our OSM community in Metro Manila, conducted an AlayData event for the quarter. We gathered to celebrate Open Data Day, focusing on open geopsatial data from OpenStreetMap, and give ourselves opportunities to socialize and get to know other contributors, sharing stories and experiences, and a chance for hands-on learning with new tools.

Among the things that our community learned from a “getting to know you” survey we did last quarter, is the high interest in other aspects of the OSM movement: like field mapping, photo-mapping, and getting familiar with other tools available from the OSM ecoysystem, and to more casual opportunities to contribute other than arm-chair mapping.

The volunteer group was sub-divided into three teams of their choice:

• Galúgad - folks also on foot, using FieldPapers, for a no-tech mapping approach. In Filipino, “Galúgad” means travelling to explore, or search for something.
• Tahák - folks on foot, using StreetComplete_EE (SCEE). “Tahák” in Filipino means to pass through a new or unusual path.
• Padyák - folks on HPVs (in our case, just bikes), to collect ground-level photos, to support or augment map editing. “Padyák” in Filipino means to stomp, and by extension, to pedal or push with your foot.

Initial results

Here’s the latest heatmap of recent edits made in the area:

… See full entry

I have created a web-based tool to easily and intuitively obtain the access token needed to make most requests to the OpenStreetMap api.

It is hosted courtesy of Interactive Maps.

The tool walks you through the process of obtaining such a token. It is useful for those writing server-side software that communicates with the api.

I created this tool because there is no other simpler way to authorise server applications. Current ways require running code locally.

It is available here: https://tools.interactivemaps.xyz/token

In case you might have not yet noticed, my current project on OSM is to cover the entire remainder of Vancouver Island with woodland data. I started with my home area of the Comox Valley and am radiating out from there in all directions, eventually finishing up with the area around Cape Scott. Every patch of forest I find in aerial imagery, no matter how expansive, even if the trees are small, will be added.

---

✔ YouthMappers UFRJ receives the Women’s Participation Award!

✔ YouthMappers UFRJ recebe o Women’s Participation Award!

✔ Our participation in the Open Data Day YouthMappers at UFBA 2024

✔ Nossa participação no Open Data Day 2024 do YouthMappers at UFBA

✔ Web map do mapeamento colaborativo para redução de riscos e desastes (RRD)

✔ Web map of colaborative mapping for the Disaster Risk Reduction (DRR)

✔ Mapear POI no OpenStreetMap e exibir dinamicamente com uMap

✔ Mapping POI in OpenStreetMap and displaying dynamically with uMap

✔ Resultados do GIS DAY 2023!

✔ V Olimpíada Brasileira de Cartografia incluiu o OpenStreetMap como parte de sua etapa prática

✔ V Brazilian Cartographic Olympiad included OpenStreetMap as part of its practical stage

✔ Geocodificação com OpenStreetMap

✔ Mapeamento humanitário e OpenStreetMap

✔ Nossa participação no State of the Map Brasil 2023

✔ Atualização dos dados populacionais dos municípios brasileiros no OpenStreetMap

✽✽ Women’s participation is recognized

---

Leia em Português

The international project YouthMappers awarded the YouthMappers UFRJ Chapter (Rio de Janeiro, Brazil) for promoting women’s participation in its activities and organization, corresponding to more than 50% of its membership.

The YouthMappers UFRJ Chapter is an initiative of open collaborative mapping, that results of a partnership between the Virtual Institute for Sustainable Development - IVIDES.org and the Laboratory of Cartography - GeoCart-UFRJ, chaired by Dr. Raquel Dezidério Souto.

On this International Women’s Day, we dedicate this award to all girls and women, hoping that they can achieve their goals!

… See full entry

---

Our participation in the Open Data Day YouthMappers at UFBA 2024

Nossa participação no Open Data Day 2024 do YouthMappers at UFBA

Web map do mapeamento colaborativo para redução de riscos e desastes (RRD)

Web map of colaborative mapping for the Disaster Risk Reduction (DRR)

Mapear POI no OpenStreetMap e exibir dinamicamente com uMap

Mapping POI in OpenStreetMap and displaying dynamically with uMap

Resultados do GIS DAY 2023!

V Olimpíada Brasileira de Cartografia incluiu o OpenStreetMap como parte de sua etapa prática

V Brazilian Cartographic Olympiad included OpenStreetMap as part of its practical stage

Geocodificação com OpenStreetMap

Mapeamento humanitário e OpenStreetMap

Nossa participação no State of the Map Brasil 2023

Atualização dos dados populacionais dos municípios brasileiros no OpenStreetMap

An event to strengthen alliances between mappers from Brazil and Africa

---

Read in Portuguese

Between March 2nd and 5th, 2024, the event OPEN DATA DAY - Communities mapping communities: Brazil-Africa connection was held in Salvador (Bahia, Brazil), with the participation of Brazilians and Africans, who presented special keynotes and case studies on collaborative mapping, on the themes of sustainable development, gender equity, adequate housing, humanitarian mapping, disaster risk reduction and urban planning.

The YouthMappers at UFBA, producer of the event, also held mapathons, or mapping marathons, in the format of hybrid workshops, where participants mapped collaboratively on-line, using the editor iD for OpenStreetMap.

The YouthMappers UFRJ participated of the event, with the special keynote Collaborative mapping for disaster risk reduction - Case study: Municipality of Maricá (Rio de Janeiro, Brazil), given by its president, Dr. Raquel Dezidério Souto (IVIDES.org).

WATCH the RECORED VIDEO (in Portuguese and English), clicking here.

READ The PDF PRESENTATION FILE (in Portuguese and English), available here.

KNOW about this case study of collaborative mapping here.

… See full entry

Introduction

I am writing this tutorial because adding wireless connectivity to the cheapest hobbyist RTK module (Ardusimple simpleRTK2B) is very useful but not trivial for those inexperienced with electronics, and Ardusimple closed down their forums for… some reason. Hopefully this is something anyone can follow to make RTK more accessible to the general hobbyist mapper.

This entry is building on from my previous diary entry “Affordable, High Quality 360 Street Level Imagery using GoPro Fusion and Ardusimple”, I have now been using the rig for a couple years and it is holding up very nicely.

A quick summary is that I used the simpleRTK2B with my phone and GoPro Fusion 360 to make a very cheap and ultra portable street level imagery rig, for Mapillary or Kartaview. It can be used handheld or mounted to a car or bicycle.

The last survey I went on, whilst mostly fine, did bring up some issues regarding the reliability of the USB OTG data connection. This has always been a weak point of the rig in other ways because;

• the USB connection would drain my phone’s battery and make it difficult to charge the phone simultaneously whilst surveying, unless using wireless charger
• the phone always needed to be in close proximity to the simpleRTK2B
• too easy to accidentally disconnect
• The OTG adapter is wobbly in the type-c port

As my Android app of choice “SW Maps” permits a bluetooth connection for the NTRIP corrections, it was the obvious way to go.

Bluetooth module choice

Ardusimple sells the Bluetooth XBEE module for the simpleRTK2B for €34 which is quite expensive. I know you’re reading this Ardusimple! Third party Bluetooth XBEE modules are somewhat cheaper (around $20 AUD), however I had a generic bluetooth UART module laying around so I decided to just solder it in. Similar ones are quite cheap to buy new, for example the arduino HC-06 module goes for around $10 AUD.

Connecting it up

… See full entry

Added sidewalks south of Center Avenue between Hazelwood and Hiland, north of ORB/PA-65. Connected sidewalk to previous additions from Ben Avon.

I plan to extend coverage north of Center Avenue within Emsworth, and south of ORB/PA-65.

Added some parking lots here and there where most obvious, and cleaned up the area around Camp Horne Road & ORB intersection. This area could likely use some more work.

Realigned buildings here and there based on updated aerial photography. Might make another pass because there are quite a few that seem to be several meters out of alignment. I’ll have to check the original data these were derived from, but at least so far it seems that the PEMA imagery is the most accurate and precise available. I’ve cross-checked several notable points against the Allegheny County GIS viewer to confirm alignment to the best of my ability for now.

(All images via WikimediaCommons)

So, I went on a little outing with a friend to look at some historic/ folkloristic sites that I hadn’t been to before. One of them was an old monastic site where there is still a working church with a holy well (https://wiki.openstreetmap.org/wiki/Tag:place_of_worship=holy_well) and high cross (https://wiki.openstreetmap.org/wiki/Tag:historic=high_cross) nearby. When we went to the holy well/ high cross site, I was delighted to see that the site also had a rag tree which hadn’t been recorded on the government’s Historic Environment Viewer. Now, there could be several reasons for that which I won’t go into, but it reminded me that rag trees were something I had wanted to map, but of course, there was no tagging scheme.

I had mapped some previously using just https://wiki.openstreetmap.org/wiki/Tag:natural=tree with various other tags, but I thought I needed a tagging scheme that was applicable to other countries and cultures as well.

… See full entry

Today marks a milestone in the development of OpenStreetMap NextGen. After months of rigorous development, I conducted the 1^st OpenStreetMap NextGen performance benchmark, a crucial step towards realizing the vision of a more robust, efficient, and user-friendly OpenStreetMap.

The focus of today’s benchmark was on evaluating static and unauthenticated requests. Since this core functionality is unlikely to change significantly during future development, it’s the perfect time to test it.

Future benchmarks will focus on timing authenticated requests as well as API 0.6.

What was measured

The benchmark analyzed request processing speed, excluding network and client latency. Both osm-ruby and osm-ng support the X-Runtime response header, which tracks how long it takes to process a request and generate a response.

Here’s a general breakdown of a typical static request processing:

… See full entry

2720 m

3520 m

3050 m

Peak Forest

See pt1 of this series here.

See pt2 of this series here.

A Long Overdue Release

The goal with the Field Mapping Tasking Manager (FMTM) was to adopt an agile development style, making a new release around once per month.

3 months have passed since the last blog post and there was no FMTM release in between!

What gives??

Well, the team has been working extremely hard simplifying usage of FMTM and making it much more usable.

It’s been hard to find a good point to stabilise a release due to so many great and rapidly developed updates!

From this release onwards we plan to follow through with a new version increment every month. Look out for version 2024.4.0 next month.

Public Beta Now Live

• The main goal we have been working towards is releasing a public beta this month.
• The public beta for FMTM is now live on https://fmtm.hotosm.org
• The idea to to have the public test out it’s functionalities & definitely break a thing or two!
• With your valuable feedback we want to make FMTM the best it can possibly be 🙏

… See full entry

Started working on extending sidewalk mapping coverage into Emsworth Borough. I’m working much the same way as I did for Ben Avon, mapping sidewalks using a combination of aerial imagery, street-level photographs (Bing, PEMA, Esri, as well as my own), and in-person survey.

I was somewhat surprised to see that a footpath I have used numerous times going back many years was unmapped, so I added it (marked on the associated map).

I am trying how best to approach the area of Memorial Field (adjacent to Ohio River Boulevard / PA-65). The area currently marked shows as a football field, but the actual usage of the field is also a baseball diamond seasonally. In addition the area is shaped and sized differently than currently shown. Also, there are footpaths around it that are somewhat challenging to see on aerial imagery, so I suspect I will have to do some in-person GPS tracking to get better data. I am debating whether or not to map the pedestrian tunnel that passes beneath ORB/PA-65, as in the past I have been admonished that it is illegal to use. But it’s not physically blocked, nor are there posted signs indicating the access status. I just don’t want someone to wander through it and get into trouble, so maybe I’ll map it and tag it private or something to discourage public use until I can confirm.

I will probably bounce around between sidewalks and other features as I come across them.

Morocco and the western sahara is one entity there is nothing called Sahrawi Arab Democratic Republic or western sahara as a state

https://community.openstreetmap.org/t/proposal-to-add-the-emoji-as-a-reaction/107167/1

this thread which is even has 2 DWG participants started off as a joke but has turned into coordinated harassment and trolling, they even praise “skillful trolling” I am going to let people read this for themselves. This is the backbone of OSM everybody.

I’ve begun to add sidewalks in Swissvale Borough.

This is my current methodology (just putting this somewhere so I can reference it later, and adapt to new information/methodology when necessary):

1. add longest section of sidewalk possible (using clearest aerial imagery available, when in doubt, crosscheck with others; using PEMA, Esri, Bing for the most part), tag surface and smoothness where appropriate.
2. add pedestrian crossing across intersecting ways, tag surface and markings.
3. add crossing for intersecting ways (when prompted), tag surface and markings.
4. tag all corners appropriately (curb height, wheelchair access).
5. verify the above using street-level imagery and in-person surveys when possible.
6. change tag for adjacent streets to sidewalk=separate to indicate that the sidewalk is mapped separately.