Users' Diaries

Recent diary entries

纠正了一些先辈们所标注的不准确道路,这些道路或是如今已与从前大不相同,或是先前的标注不规范。删去了箐湖和县政府大楼,本人之前的相关数据太过于粗略。增加了一些建筑,删除了已不复存在的地点。有的地方不够详细,明天打算实地勘探后再修改。那么就这样吧,晚安OSM。

A while back a message popped up in my inbox inviting me to compete for a GoPro Max2 360-degree sport camera, courtesy of Meta, which of course now owns Mapillary and thus has a vested interest in supporting crowdsourced collection of street-level imagery. I submitted the application assuming it would come to naught and was pleasantly surprised when a GoPro Max2 appeared on my doorstep on July 15th. What follows is a review of that camera for collecting street-level imagery. Amazon sells this camera for $299. To put that in perspective, I paid about $200 for a RealMe model RMX3241 when we got to Italy for SOTM a couple of years ago and discovered that my wife’s iPhone was not unlocked as advertised, so a local Italian SIM card wouldn’t work.

Description:

The GoPro Max2 features back-to-back fixed-focus-to-infinity fisheye lenses. The built-in processor stitches those images together and stores the combined image as a 360-degree view of everything, not just horizontally but vertically as well. A smartphone app, Quik, can be downloaded to control the camera via a wifi connection (and that is vastly easier than trying to control the camera via the tiny LCD screen). The camera can collect both video and still images, 360-degree JPEGs, which can be displayed by VLC Media Player as well as GoPro’s proprietary Player. GoPro Player, a free download, is a desktop imagery editor that allows you to trim video files and also to edit the point of view of video and still photos.

After charging the batteries I did some initial filming by walking around my back yard and viewing the videos on the camera’s LED screen. That led to basic familiarity; after a short time the controls became relatively intuitive. I downloaded the Quik app to my Android phone, connected the camera and phone, and used it to start and stop the camera, select modes, and generally experimented a bit, then deleted those test videos. The Quik app is not hard to figure out.

See full entry

I build bike + train loops in France by crossing OpenStreetMap with the official cycling-route reference (RVM / Réseau vélo et marche). Two points I’d value the community’s view on: at which level the identity (ref) of a multi-level superroute should live, and whether the emerging ref:FR:RVM tag (which carries the RVM id and gives an exact OSM↔RVM join key) is worth spreading. Full write-up (FR): https://tisseurdevoies.fr/articles/openstreetmap-veloroutes-retour-experience

Je fais du vélo, j’aime rentrer en train, et j’ai fini par construire un outil qui repère les boucles réalisables entre deux gares. Pour ça, je croise les véloroutes d’OpenStreetMap avec le référentiel officiel des véloroutes françaises, RVM (Réseau vélo et marche).

J’ai documenté ce retour d’expérience (choix du référentiel, rapprochement des deux sources et reconstruction d’une géométrie exploitable) ici : OpenStreetMap et les véloroutes françaises : retour d’expérience de Tisseur de Voies

Je voulais surtout soumettre ici les deux points sur lesquels votre avis m’aiderait le plus.

1. Où placer l’identité d’un itinéraire dans une hiérarchie superroute / route ?

Les grandes véloroutes sont souvent modélisées avec plusieurs niveaux de relations.

La Route des Grandes Alpes, par exemple, a une racine type=superroute portant ref=VRGA, puis un « tracé principal » et des « variantes », puis les étapes. La structure est très utile, mais un consommateur qui ne traite que les relations feuilles type=route perd alors l’identité portée par la racine.

Sur la quarantaine de superroutes vélo que j’ai analysées en France, j’observe plusieurs situations : ref uniquement sur la racine, présent également sur certaines relations filles, ou parfois absent à certains niveaux.

J’ai trouvé différentes documentations et propositions sur les hiérarchies de routes, mais je n’ai pas identifié de convention suffisamment claire pour un consommateur de données :

dans une hiérarchie superroute / route, quelle duplication de ref, network et éventuellement name est aujourd’hui considérée comme souhaitable ?

L’objectif côté consommateur serait de pouvoir conserver à la fois l’identité de l’itinéraire et sa structure hiérarchique, sans déduire l’une à partir de l’autre.

Détail et exemple de la Route des Grandes Alpes

2. ref:FR:RVM : une clé de jointure OSM ↔ RVM ?

See full entry

Posted by pussreboots on 9 August 2026 in English.

Today I finished mapping all the homes in the Stonebrae Country Club, a gated community surrounding a golf course at the top of the loop where Fairview Avenue becomes Hayward Avenue. In 2010 I worked as a NARFU Census taker and had to note down which addresses were inhabitable because they hadn’t been built yet. Now all that land with just paved streets are homes. Many of my children’s friends live there as they attended the elementary school across the street from the outer bounds of the neighborhood.

Next step is to start my way down Hayward Avenue and eventually into the heart of the city.

Location: Hayward, Alameda County, California, United States

Tourism and Digital Mapping: Research Digital

Google Maps Location

Image by Seli Kasela - Google Maps Location

Open in Google Maps

SELI KASELA DIGITAL CREATIVE STUDIO

Jalan Pantai Balangan No.85
Jimbaran, Kec. Kuta Selatan
Kabupaten Badung, Bali 80361
Indonesia

Open SELI KASELA I in Google Maps

Digital Mapping and Tourism

This entry documents my personal work exploring the relationship between tourism, digital mapping, geographic information, and local destination discovery.

The location featured here is OSSY SURF TRIP BALI in the Balangan area of South Kuta, Badung, Bali, Indonesia.

Mapping Perspective

Digital maps are an important part of modern tourism. Travelers use geographic information to discover:

  • Surf schools
  • Beaches
  • Hotels and accommodation
  • Restaurants
  • Local businesses
  • Attractions
  • Roads and transportation
  • Points of interest

My interest is in documenting how local tourism places are represented within the wider digital mapping ecosystem.

OpenStreetMap and Local Knowledge

OpenStreetMap provides a collaborative environment for geographic information and community mapping.

This diary entry is part of my personal documentation of tourism, digital mapping, geographic information, and destination discovery.

Location Reference

Place: OSSY SURF TRIP BALI
Area: Balangan, South Kuta, Badung, Bali
Country: Indonesia
Topic: Tourism and Digital Mapping
Purpose: Personal work documentation

Open location in Google Maps

MY LOCATION BUILD OWN INDEPENDENT

Location: Badung, Bali, Indonesia

I have already forgotten how I first came across StreetComplete, but what I do remember is that I immediately fell in love with the concept of the app.

I like wandering around and exploring. When travelling, the things that attract me the most are actually very “normal”. Maybe there is a neighbourhood, maybe a lovely park, maybe a path along the river… I just follow the direction of the road and take a turn at a junction if I feel like it.

I don’t know. I just really don’t like those crowded and buzzing tourist attractions. On the contrary, it is in the nooks and crannies of everyday life that I can feel the vibe of a neighbourhood, a town, or a city.

This convenience store has some good samosas. This small community park offers the best shade during the scorching summer. This path along the canal has ducks and geese to guide your walk…

From these small and seemingly negligible things, I feel a city comes alive.

And that’s why StreetComplete is my best travel companion. It pulls up a bunch of quests for me to explore. The surface of the pavement, the sound signal at a crossing, the bin at a bus stop, the name of a store… It simply guides me to dive deeper into an area, and I can explore while completing the quests along the way.

Gamification is a good way to encourage contributions to OSM, but for me, StreetComplete is far more than just a game. It lets me immerse myself into a city and teaches me how to look at it from a new perspective.

··· I didn’t start contributing to OSM because of any grand philosophy or ideology. I simply began editing because I needed to. But as I became more involved, I learned more about what I believed OSM stood for—openness, decentralization, freedom to collaborate, and a community built around shared stewardship rather than commercial ownership. At least, that was how I came to understand OSM.

That understanding was what motivated me to continue contributing. I chose to spend my time improving OSM instead of Google Maps or the dominant commercial map used in my country. I even spent time studying OSM’s principles and community practices because I wanted to contribute in a way that respected those values.

If utility had been my only motivation, I probably wouldn’t have contributed to OSM at all. In the region where I live, almost nobody actually uses OSM. From a purely practical perspective, my efforts have very little visible impact. Yet I kept contributing because I believed OSM represented something fundamentally different from commercial mapping platforms. That belief—not efficiency or popularity—was what made my contributions meaningful.

For that reason, I don’t believe corporate participation is inherently a problem. OSM is open to everyone, and companies should absolutely be free to use the data and contribute to improving it.

My concern is not that companies participate. My concern is whether, over time, the priorities of the project could gradually shift toward the interests of organizations that naturally have business objectives and far greater resources than individual volunteers. Simply saying that “companies are part of the community” doesn’t fully address that concern. To me, the more important question is not whether companies belong here, but how the community ensures that the values and priorities shaped by volunteers remain just as influential as corporate interests.

Perhaps this is the source of my confusion.

See full entry

Mapping

Over the past year, our OpenStreetMap Pakistan community has been actively working to map high-risk flood zones across the country—both areas historically affected by extreme flooding and regions facing critical vulnerability during upcoming monsoon seasons.

Shifting from Reactive Response to Proactive Preparedness

During last year’s monsoon floods, our mapping response began after the disaster had already struck. While those post-disaster edits were vital for ongoing emergency response, we recognised the need to get ahead of the curve.

This year, we shifted our strategy completely: we initiated pre-disaster mapping well before the monsoon season arrived.

By leveraging flood projections and high-risk zone data from the National Disaster Management Authority (NDMA) and prominent emergency monitoring sources, we identified priority regions across Pakistan. We began our efforts by focusing heavily on areas categorised as the highest risk of severe flooding, ensuring that digital infrastructure is in place before rising waters cut off communities.

Community Coordination & HOT Tasking Manager

Together with two fellow community members, I took charge of creating, organizing, and managing dedicated projects on the Humanitarian OpenStreetMap Team (HOT) Tasking Manager.

To drive contributions and sustain momentum, we have been organising community mapping parties and mapathons. Local mappers and volunteers across Pakistan came together to trace the following:

*Missing road networks and bridge connections

*Remote village footprints and building clusters

*Key natural landmarks and waterways

These precise layers are already empowering ground rescue teams, military logistics, and international aid agencies to plan evacuation routes, calculate population exposure, and navigate flood-affected corridors.

Global Recognition

Our community’s proactive mapping drive was recently highlighted in a feature article by the UK newspaper Oxford Herald:

See full entry

Posted by rphyrin on 5 August 2026 in English.

This afternoon, I noticed that several of my colleagues were visiting a recently opened school in the far south.

They took several photos, which is quite a rarity on the internet, since not many people actually go there and upload pictures of the newly built buildings.

I wanted to upload those photos, hoping they might be useful for anyone trying to find information about the place.

Then I remembered that OpenStreetMap has this image=* tag.

I could associate an image with the place by adding an image URL there. So I opened Vespucci on my Android phone and added the image URL to the object.


Now I’m back at my PC, and I wanted to make a simple app (or maybe just a script) to browse every image=* tag that exists in OpenStreetMap.

At first, I thought of doing it the usual way : build a Leaflet web map, query the Overpass API, then display the images in popups.

But then I remembered that the Overpass API has recently been under heavy load.

From what I’ve heard, it’s because of a barrage of AI scrapers… or maybe just a flood of quick-and-dirty, vibe-coded OSM apps being produced en masse.

Whatever the exact reason, it has noticeably affected the service.

Knowing that, I was discouraged from making the situation any worse. So I scrapped that idea.


Then I remembered something else:

Overpass Ultra.

I don’t know exactly how it works internally, but I assume it uses a different Overpass API endpoint than the ones I would normally query directly.

If that’s the case, perhaps using Ultra wouldn’t add to the current strain on the public Overpass servers.

I also realized that Overpass Ultra’s advanced styling syntax lets me solve the whole problem directly within the query itself, without having to build my own Leaflet-based web app.

So here it is: a quickly put-together Ultra query that displays every OpenStreetMap object containing an image=* tag and shows the referenced image in a simple popup.

See full entry

Life in a multi-million population City can be tough on Introverted minds. For me, mapping in OpenStreetMap is first and foremost an activity to improve publicly accessible geodata around my local and known places, though it has also recently become a way for me to virtually travel to far away places. Exploring remote corners of the earth that are not quite as bustling with activity, where not every square-meter has already been meticulously mapped to the nth degree. Theres even a subreddit for this kind of exploration: /r/GoogleEarthFinds !

Zooming in on a random patch of rainforest, a tiny island in the pacific or one of the thousands of meandering arms off the Amazonas shows a mostly untouched view of nature. Panning around looking for interesting landmarks, it only takes a few minutes to stumble upon a secluded village whose roads are not even connected to the world-wide network, or a lonely farm in the middle of nowhere. These are the places that fascinate me the most. I get lost in imagining what life is like there, who lives there, what untold stories do these places hold? While daydreaming of this, i map the buildings I see, paths and roads, things that can safely be confirmed from aerial imagery. Switching to different imagery providers can show how these places evolved, has the village grown or shrunk? Have Roads been extended or left to be reclaimed by mother nature? A handy website for viewing satellite imagery with different timestamps is https://livingatlas.arcgis.com/wayback

Usually I just zoom into random places and see where it takes me. With the power of Overpass Turbo, one can find places in a slightly organized fashion. Below is a prompt which shows islands that have residential areas on them, within the current view of the map:

[out:json][timeout:25];
(
nwr["place"="island"]({{bbox}});
  );

nwr["landuse"="residential"]({{bbox}});

// print results
out geom;

Or simply highlighting villages in the current map view:

See full entry

Location: Novo Ceú, Autazes, Amazonas, North Region, Brazil
Posted by Kay Covey on 2 August 2026 in English. Last updated on 20 August 2026.

August 2–8

August 2

  • Fixed Reynoldsburg borders; borders now up-to-date as of most recent annexation on May 24, 2026.
  • Updated Reynoldsburg population; increased to 43,350 according to U.S. Census Bureau.
  • Added intermittent stream called Little Jordan Run.
  • Modified Jackson Avenue; changed “one way” value to “no” and added note that signage by the Street Department is incorrect. Correct name is Jackson Avenue not Jackson Street.
  • Modifed Burkey Avenue; changed “one way” value to “no” and added note that signage by the Street Department is incorrect. Correct name is Burkey Avenue, not Burkey Drive.
  • Modified Burkey Court; switches from Burkey Avenue to Burkey Court at the intersection with Southwood Avenue, not in the middle of the road.
  • Fixed name of Taylor Park Drive (originally shown as just “Taylor Park”).
  • Fixed differentiation between Taylor Road and Taylor Road Southwest.
  • Added info to Raider Stadium (Reynoldsburg High School football stadium).
  • Removed Smokey Bones brand from building at 2200 Baltimore-Reynoldsburg Road (closed permanently after bankruptcy).
  • Added info to Reynoldsburg High School’s Livingston Campus.

August 3

  • Fixed name of Taylor Road.
  • Added 5 ponds near Lakeland Hills neighborhood.

August 5

  • Added name of TS Tech Drive as indicated by street signs in the area.
  • Added name to the remaining portion of Wilma Drive.

August 9–15

August 9

  • Removed nonexistent Truro Township enclave inside Reynoldsburg around Blacklick Creek.

August 16–22

August 20

  • Added French Run (aka French Run Creek).
  • Removed note about Burkey Avenue incorrect signage (fixed with new signage).

Gerade eben mappe ich den Bayern-Park detaillierter. Durch meine frühere Jahreskarte konnte ich den Park oft besuchen und kenne daher viele Bereiche aus eigener Erfahrung. Jetzt nutze ich dieses Wissen, um Details des Parks in OpenStreetMap zu verbessern.

Als Ziele habe ich folgende:

  • Alle POIs überprüfen und ggf. eintragen/aktualisieren
  • Alle (oder zumindest den größten Teil von allen) Wege überprüfen und ggf. hinzufügen/aktualisieren
  • Generell mehr Details hinzufügen