OpenStreetMap Blogs Last Update:

Σε εφαρμογές που “πατάνε” στους Open Street Maps (σίγουρα στις Mapy. OSMand, Organic Maps, ίσως και αλλού), ως E65 εμφανίζεται ΛΑΘΟΣ ο παλιός δρόμος Λαμία-Δομοκός-Φάρσαλα-Λάρισα και όχι ΣΩΣΤΑ ο αυτοκινητόδρομος Θερμοπύλες-Καλαμπάκα (και ημιτελές Βορειότερα ως την συμβολή με την Εγνατία). Ιδίως για τους ξένους ταξιδιώτες είναι μέγα μπέρδεμα.

17 hours ago

05/02/2026-11/02/2026

♦

[1] The osm-mapper-globe by Martijn van Exel | map data © by OpenStreetMap Contributors.

Mapping

• User AndreaDp271 is seeking comments on their proposal of a tagging scheme for civil protection areas used in case of large scale emergencies. Please review the proposal and share your feedback to help refine the technical details and address any potential issues.
• Voting on the tagging scheme for advisory access restriction signage on destination signs proposal is open until Saturday 21 February.

Mapping campaigns

• Henry Wilkinson has mapped the Dundas West Station in Toronto, Canada, using the LiDAR sensor on an iPhone 17 Pro, in combination with the Niantic Scaniverse app, to capture 3D data. He then reconstructed the digital 3D scene with Meshroom and Blender before uploading the results to OpenStreetMap through JOSM (using the PicLayer plugin) to align imagery, and iD for streamlined indoor tagging. The completed work enabled detailed indoor mapping of the station, now viewable on OpenLevelUp.

Community

• darkonus wrote in their diary about elliptical toponyms (geographical names in which generic terms disappear over time) and explained why it is important for OpenStreetMap mappers to verify the full forms of names. The author examined various cases and focused on Ukrainian microtoponyms, emphasising that abbreviations in sources or in speech do not always indicate a change in the proper name.
• Bart Louwers and others have released the January 2026 edition of the MapLibre Newsletter.
• Matt Whilden has made an Ultra query to create a map that renders the nickname tag of places in OpenStreetMap.

OpenStreetMap Foundation

• Paul Norman reported that the OpenStreetMap Operations Team has recently made several improvements to the tile.openstreetmap.org raster map tile service.
• Minh Nguyễn reported that the OSM Wiki has just switched the CAPTCHA used in the account creation process from hCaptcha to Cloudflare Turnstile, aiming to improve protection against bots.

Local chapter news

• Oliver Rudzick announced ♦►♦ that FOSSGIS e.V. will once again host the FOSSGIS–OSM Community Meeting at the Linuxhotel in Essen. The event is scheduled for the extended first May weekend, from Thursday 30 April to Sunday 3 May. Additional details are available on the event’s Wiki page.
• OpenStreetMap United States 2026 board candidate nominations closed on 8 February 2026. There are five candidates and you can read their position statements on the Wiki.

Events

• The FOSS4G 2026 organising team announced that the Call for Proposals (closing 16 March) and Travel Grant Programme (closing 28 February) are now open for the global conference to be held in Hiroshima, Japan (30 August to 5 September 2026).
• Developers are invited to register for a free GeoSolutions instructional webinar on the Geonode 5.0 open-source software, a web-based application and platform for developing geospatial information systems and for deploying spatial data infrastructures. The webinar will be held on Tuesday 24 February at 4 pm GMT.
• Recordings of the State of the Map CZ/SK 2025 sessions are available ♦ on its Peertube channel. The details can be found ♦►♦ in the event’s schedule.
• The State of the Map US call for proposals closes on 16 February. OpenStreetMap US invites you to share your presentation ideas. Looking for inspiration? Check out the recorded talks from previous conferences. They also have Mapping USA recordings available.

OSM in action

• Christoph Langner, of Linux und ich, showcased ♦►♦ Chainlaine, a Brouter-powered bike navigation app on Android.

Software

• [1] Martijn van Exel has developed the osm-mapper-globe, a visualisation dashboard that enables users to watch OpenStreetMap edits in real time on an interactive globe. The code is available on Codeberg under an ISC licence.
• Stefan blogged about GraphHopper’s route optimisation API and ‘stop timing’, a new feature accounting for location overhead (the time spent at a stop on a delivery route).

Programming

• Martijn van Exel has developed cosmo, a command-line tool for filtering and converting OSM PBF data into GeoJSON or Parquet formats.

Releases

• The CoMaps team released version 2026.02.09 featuring OSM data from 7 February and automatic updates of the check_date tag when adding/editing POI. Furthermore, the search now supports Scandinavian letters (æøå), on Android you can now disable the speed limit display during car navigation, and on iOS in the EU you can now set CoMaps as your default map app.
• Sarah Hoffmann (aka lonvia) announced enthusiastically that Photon 1.0.0 was released with a lot of improvements in its search engine. She also thanked GraphHopper, Komoot, and Entur for their continued support of Photon development, which has made this release possible.

Did you know that …

• … the Academic Computer Club, at Umeå University, and the Oregon State University Open Source Lab contribute to OpenStreetMap by hosting tile render servers? If you also want to help OpenStreetMap run a tile server in your region, check this guide.
• … according to OpenStreetMap’s tile usage policy, it is recommended to include a ‘Report a map issue‘ link, so your app users can help improve the data?
• … Séverin Ménard (Les Libres Géographes) gave ♦ a keynote titled Le numérique, vecteur d’une appropriation collective des données environnementales? It was part of the Cycle Annuel 2025, helded by the Institut des hautes études d’aménagement des territoires. He showed the application of open and collaborative data and detailed the mapping carried out in Mayotte. The explanation of this mapping effort was published in the weeklyOSM issues 770 and 775.
• … the General Bikeshare Feed Specification (GBFS) has used the OpenStreetMap opening_hours format since version 3.0? GBFS is an open data standard designed to make it easier to discover and use shared mobility services.
• … the statistics of uMap instances are also published as a chart?

OSM in the media

• Historian Arseniy Chuhuy outlined how place names in Crimea changed during the imperial and Soviet periods and described efforts to restore historical, especially Crimean Tatar, toponyms. He also noted practical issues in the process, including duplicate names and settlements without clearly documented historical alternatives. The article is illustrated with a map by Ukrainian OpenStreetMap contributor and cartographic designer Fedir Gontsa.

Other “geo” things

• The Editora IVIDES is accepting ♦►♦ applications for the selection process to form the scientific committee for volumes 2 and 3 of the series Case studies in collaborative and participatory mapping (in Portuguese). Raquel Dezidério Souto, editor of the series, reported ♦►♦ in her OSM user diary that the first volume was released in August 2025 and has already been downloaded by over a thousand people.
• The Government of Portugal has published ♦►♦ a list of municipalities affected by Storm Kristin that are now under a state of public calamity. A humanitarian mapping effort is emerging, and you can learn more about this and other topics by following the Portuguese OpenStreetMap community group on Telegram and Discord.
• The UCL Warning Research Centre invites you to their free and hybrid launch of the UCL Warning Database, which will occur on 4 March, from 3 pm to 4 pm GMT, at Room 225, Central House, Bloomsbury.
• Miguel Alvarez has taken a look at the maps of Leonardo da Vinci. Further detail of Leonardo’s mapping career can be found in Christopher Tyler’s 2017 article.
• Will Dunham wrote in The Japan Times about radar data which shows a cavernous underground lava tube on Venus. Lava tubes are also found in certain volcanic locations on Earth and its moon and are believed to be present on Mars.
• Melinda Laituri, of Colorado State University, discussed women’s contributions to cartography. We previously reported ♦►♦ that Daniel Meßner had highlighted the American geologist and cartographer Marie Tharp and her contribution to the cartographic depiction of the Mid-Atlantic Ridge.

Upcoming Events Country Where Venue What When ♦ Delhi Dosa Coffee, Model Town ILUGD Meetup × OSM Delhi Mapping Party No.26 (North Zone) ♦ 2026-02-15 ♦ Lancaster Lancaster University Welcome center 1 Lancaster FoMSF Mapathon ♦ 2026-02-16 ♦ EPN d’Arlon, rue de Diekirch 37, Arlon EPN d’Arlon – OpenStreetMap – Contribution ♦ 2026-02-17 ♦ Milano Building 3A Ground Floor – Politecnico di Milano PoliMappers Maptedì ♦ 2026-02-17 Missing Maps London: (Online) Mid-Month Mapathon [eng] ♦ 2026-02-17 ♦ Online Mappy Hour OSM España ♦ 2026-02-17 ♦ Lyon Tubà Réunion du groupe local de Lyon ♦ 2026-02-17 ♦ Bonn Dotty’s 197. OSM-Stammtisch Bonn ♦ 2026-02-17 ♦ San Jose Online South Bay Map Night ♦ 2026-02-17 ♦ Online Lüneburger Mappertreffen (online) ♦ 2026-02-17 ♦ MJC de Vienne Réunion des contributeurs de Vienne (38) ♦ 2026-02-18 ♦ Karlsruhe Chiang Mai Stammtisch Karlsruhe ♦ 2026-02-18 ♦ Bratislava Prírodovedecká fakulta UK Bratislava Missing Maps mapathon Bratislava #12 ♦ 2026-02-19 OSMF Engineering Working Group meeting ♦ 2026-02-20 ♦ Karlsruhe Geofabrik, Amalienstraße 44, 76133 Karlsruhe Karlsruhe Hack Weekend February 2026 ♦ 2026-02-21 – 2026-02-22 ♦ Belfast School of Geosciences, Queen’s University Belfast Belfast Mapathon ♦ 2026-02-21 ♦ TAK Kadıköy Tasarım Atölyesi OpenStreetMap Outdoor Editing ♦ 2026-02-21 ♦ Kalyani Nagar TomTom Pune Office, India OSM Mapping Party at TomTom Pune, India ♦ 2026-02-21 ♦ Atelier Vélo Utile Rencontre OSM Saint-Brieuc ♦ 2026-02-21 ♦ Toulouse Artilect – 10, Rue Tripière – Toulouse Rencontre OSM Toulouse ♦ 2026-02-21 ♦ Mumbai Third Wave Coffee Roasters, Lokhandwala Market OSM Mumbai Mapping Party No.7 (Western Line – South) ♦ 2026-02-22 Missing Maps : Mapathon en ligne – CartONG [fr] ♦ 2026-02-23 ♦ Olomouc Přírodovědecká fakulta Univerzity Palackého Únorový olomoucký mapathon ♦ 2026-02-24 ♦ City of Edinburgh Guildford Arms, Edinburgh OSM Edinburgh pub meetup ♦ 2026-02-24 ♦ Derby The Brunswick, Railway Terrace, Derby East Midlands pub meet-up ♦ 2026-02-24 ♦ Hannover Kuriosum OSM-Stammtisch Hannover ♦ 2026-02-25 ♦ Luxembourg neimënster, Luxembourg & online MSF Luxembourg hybrid Mapathon ♦ 2026-02-25 ♦ Düsseldorf Online bei meet.jit.si/OSM-DUS-2026 Düsseldorfer OpenStreetMap-Treffen (online) ♦ 2026-02-25 ♦ Seattle Seattle, WA, US OpenThePaths 2026: Connecting People and Places Through Sustainable Access ♦ 2026-02-26 – 2026-02-27 ♦ Santa Clara Santa Clara University Friends of MSF Mapathon ♦ 2026-02-26 ♦ Online Asamblea General Ordinaria – Asociación OpenStreetMap España ♦ 2026-02-26 ♦ Ferrara Cimitero monumentale della Certosa di Ferrara Ferrara mapping party ♦ 2026-02-28 ♦ Messina Messina Mapping Day @ Messina ♦ 2026-02-28 ♦ नई दिल्ली Jitsi Meet (online) OSM India – Monthly Online Mapathon ♦ 2026-03-01 ♦ Chennai Corporation Mapping Party @ Chennai ♦ 2026-03-01

Note:
If you like to see your event here, please put it into the OSM calendar. Only data which is there, will appear in weeklyOSM.

This weeklyOSM was produced by IVIDES.org, MatthiasMatthias, Raquel Dezidério Souto, Strubbl, Andrew Davidson, barefootstache, darkonus, derFred, giopera, jcr83.
We welcome link suggestions for the next issue via this form and look forward to your contributions.

a day ago

OSMのマッピングをはじめて、今日で継続年数1年たった。

アカウント自体は5年前に作っていたが、
当時は県道沿いに建物は張り付いてた分しかなくて（うるおぼえ）、
かつて住んでたところくらいはと、3町分の建物を描いたところで、飽きてしまい辞めた。

そして去年の今日、たまたまマップを見てみたら、建物やPOIがかなり充実してたのを見て再燃し、今に至る。

今のところ、熱は冷めてない。
個人的に継続中の調査テーマもあるし、描きたいものもたくさんある。
続けていくつもりなら、いずれはデータを活用する側にも回りたい。
そのためにもマッピングを進めていこうと思う。

オレはようやくのぼりはじめたばかりだからな
このはてしなく遠いマッピング坂をよ……

2 days ago

 

♦ 

Today I covered a slice through the Northumberland Coalfield. Starting in Newbiggin-on-sea, riding through Ashington to Pegswood then returning through Bothal and Woodhorn to Newbiggin. 

NCN 155 runs from Newbiggin-on-sea to Morpeth. The whole route is less than 8 miles long, but I only followed it for about 5 miles, as far as Pegswood. That section is pretty flat. The only real challenge is following twists and turns through Ashington. On the route back, for variety, I deviated from NCN 155 to visit Bothal then Woodhorn.

Newbiggin-on-sea has history as a fishing port and colliery town but today it mainly has the character of a small seaside resort Today was a sunny Saturday. It followed what feels like endless days of rain. Despite the cold, lots of people were out. Newbiggin-on-sea claims to have the longest promenade in Northumberland and it was buzzing with activity.

A short section of NCN 155 took me to Ashington. Until the 1840s Ashington was a tiny hamlet. But it lies above several layers of coal seams. In the second half of the 19th century the Duke of Portland built housing to attract people to come and work at his multiple local collieries. Ashington expanded rapidly to become the "world's largest pit village". The coal industry declined rapidly in the 1970's and 80's but the long parallel rows of colliery housing remain. The loss of employment hit the town hard, and parts still show the scars. But former industrial land has been reclaimed, private housing has expanded. Ashington station reopened to passenger services at the end of 2024. It feels as though a different town is emerging.

Next, on to Pegswood. This is a small pit village, with a similar history of growth, decline and recent regeneration. Perhaps the most striking feature is this sculpture, officially called 'Fire', but also known as "Robin of Pegswood", it depicts a bronze figure on a steel girder firing a miner's shovel as though it was a bow and arrow. The landowner, Welbeck Estates, has associations with Nottingham. Hence the link to Robin Hood.

♦
My next destination was Bothal, a small estate village that lies deep in the valley of the river Wansbeck. The village history has always been closely tied to the families who owned the estate. The castle (pictured top) contains the administrative offices for the Welbeck Estate, which owns virtually all properties in the village.

It's a steep climb out of Bothal, but there's no shame in pushing. On to Woodhorn, where the colliery closed in 1981. The site is now home to Northumberland Archives and the Woodhorn Museum which depicts the work and lives of local mining families, and art created by the Ashington Group of painters. The pithead gear is currently covered in scaffolding as repair works start thanks to a grant from Historic England of almost £1million. I would have liked to take a closer look but I wasn't prepared to pay the entrace fees. So I pressed on to Newbiggin-on-Sea, where I pootled around the back streets, doing a bit of exploring before calling it a day.

The weather was cold, but not too cold. There's still a lot of water on the fields and some on the roads, including one quite exciting splash though a deep flood. However, today's blue sky was a very welcome change. Total distance covered was just over 15 miles.

2 days ago

About 99% of supplements have garbage in them like seed oils, starch, citric acid or other fillers because most people are too ignorant to read the ingredients labels, let alone realize that ultra-processed pseudo-food is harmful for them in the first place.

I wonder if there is some tag for a nutrition supplements store to state that they offer clean supplements with just one ingredient, just like vegetarian tags, except focused on health rather than ethics.

Maybe diet:raw=* could somewhat apply?

5 days ago

We are happy to announce the release of Photon 1.0.0. With its first major release Photon fully switches to OpenSearch, sees a lot of improvements in performance and gets some new features on the query side.

This release marks a major milestone in the journey to make Photon a more efficient and flexible geocoder. Over the last year the code has seen a lot of modernization. We are moving away from being a simple search front end to Nominatim, towards becoming a fully featured geocoder where OpenStreetMap data can be one of many sources.

Here are the most important highlights for this 1.0 release:

Streamlined database structure

Photon’s internal database structure has been streamlined. Any metrics that are not relevant for the geocoding problem have been dropped. We’ve also dropped all language-specific indexes. Using those has slowed down queries for very little gain in accuracy.

Altogether the database is now about half the size than a 0.7 database. A planet needs about 95GB of disk space as of early 2026.

Revamped CLI

Over the years Photon has collected quite a few command-line options to tweak the import and the operation of the server. To bring a bit of order into this mess, the command-line is now organised in git-style subcommands for import, update and serving. You can ask for help for each of the commands with the ‘-h’ parameter and will get a more compact response with parameters neatly organised in groups. Have a look at the new usage documentation to learn more about the available commands.

The changes to the CLI are backwards-compatible. When no command is given then Photon will fall back to the old-style command-line parameters. This will give everybody some time to adapt their scripts to the new layout. But don’t wait too long. The old-style parsing will be removed with the next major version.

New query features

The /structured endpoint, which was optional in previous releases, is now available by default and can be used together with the database dumps from the export server. Be aware though that structured search is still somewhat new and little tested. You are welcome to provide feedback on the Github discussion page.

Version 1.0 newly introduces categories. These are custom tags that can be added to the import data and can then be used for filtering queries. This is much more powerful than the current layer and osm-tag filters. In fact, categories will replace the osm-tag filters eventually. There are currently special categories included except for a category that represents the OSM main tag. So this is mainly something you can use right now when customizing your data to create a specialised search engine.

Finally, there is a new dedupe parameter which switches off the internal result deduplication. This can for example be useful when a street is cut into many sections in OSM and you would like to get all sections instead of just one representative.

JSON import and export

Version 0.7 already introduced an experimental feature for exporting to and importing from JSON dumps. With version 1.0 we have finalized the format and published the official specification. JSON dumps of the OSM planet and selected abstracts are available on the export server. Use them to filter and adapt the data before importing into Photon, to create databases with custom settings (like additional languages) or add your own custom data. We are looking forward to hear what you are doing with this new feature.

Server metrics

If you are running Photon in a production environment that is monitored by prometheus, then the server is now able to export internal metrics like number of queries and query duration or memory usage. The endpoint isn’t enabled by the default, you need to switch it on when starting the server.

 

With this major release, Photon will switch to a more conventional use of the semantic versioning schema. From now on, patch releases will only bring bug fixes and dependency updates. Minor releases may contain new features or change existing ones trying to maintain backwards compatibility. Major releases are reserved for breaking changes in functionality and for changes that require a database reimport. We have a few ideas for more major changes to come, so don’t expect another 12 years to pass before Photon 2.0.

Many thanks to Graphhopper, Komoot and Entur for their continued support of Photon development, which has made this release possible.

6 days ago

OPORTUNIDADE PARA PARTICIPAR DE PUBLICAÇÃO CIENTÍFICA ABERTA

Portuguese only

A Editora IVIDES está com inscrições abertas para processo seletivo que visa à composição do comitê científico dos volumes 2 e 3 da série Estudos de caso em mapeamentos colaborativo e participativo. O primeiro volume da série, lançado em 2025, já conta com mais de mil downloads! Os documentos informativos desta seleção estão disponíveis:

 

🡇 Chamada pública para o comitê científico - Critérios 🡇 Convite para o comitê científico

 

✻ O prazo para envio das candidaturas é: 20 de fevereiro de 2026, 17h (UTC-3, hora de Brasília)

 

✍ Formulário de inscrição

 

✻ Os resultados serão comunicados até 23 de fevereiro de 2026, 23h59 (UTC-3, hora de Brasília), via e-mail informado pelo candidato;

 

✻ Chamada para residentes em países lusófonos;

 

✻ Parte dos capítulos inclui OpenStreetMap, aproveite para contribuir e enriqueça o seu currículo como parecerista.

 

♦

Créditos da imagem de fundo (livro): @jcomp Freepik

♦

6 days ago

Banjar

• SD Negeri - ALL DONE
• SD Swasta - ALL DONE

Pataruman

• Pataruman
  • Negeri 1-5 - ALL DONE
  • Swasta
• Binangun
  • Negeri 1-2 - ALL DONE
  • Swasta

Purwaharja

• SD Negeri - ALL DONE
• SD Swasta - Empty

Langensari 7 days ago

Hello! I’m Quincy Morgan. Thank you for considering my candidacy for the board of directors of OpenStreetMap US.

If we haven’t met before, or if you just want to chat about OSM, I encourage you to reach out via OSM, Slack, email, or social media. You can check out my website for detailed information about me, my work, and more ways to contact me.

About

I have been an avid member of the OpenStreetMap community since 2018 in both volunteer and professional capacities. I am the only person to have been employed by both OpenStreetMap US and the OpenStreetMap Foundation. Recently I have organized my activities under Wayside Mapping.

Mapping

As a volunteer mapper, I’ve contributed more than 13,000 changesets over the span of 1,400 mapping days, including more than 3,000 changesets in the past year. My mapping interests are varied but include trails, waterways, peninsulas, scenic routes, monitoring stations, and undermapped places.

Development

As a paid and volunteer open source developer, I have made major contributions to OpenStreetMap tools such as iD, Field Papers, OpenTrailMap, and the openstreetmap.us website. Most recently, I have built and launched themap.is and OSM 411 on my own time.

Life

I’m currently based in New York City but have previously lived in Pennsylvania, California, and Idaho. I’ve spent time in all 48 contiguous United States and all 10 provinces of Canada. When I’m not at my desk, you can find me hiking, biking, paddling, train hopping, or road tripping to the next spot on the map.

Positions

I believe the core roles of a nonprofit board member are threefold:

1. Represent membership

A board member is a democratic representative of the members of the organization. If elected, it would be my job to actively listen to the community and be responsive to their interests.

As a white cis male, I am concerned that people like me are overrepresented in many OSM spaces to the detriment of others and to the OpenStreetMap project as a whole. OSM should be a welcoming environment where everyone has a seat at the table. If elected, I would use my position on the board to support initiatives that promote demographic and geographic diversity within OSM US events and spaces, and to ensure some voices aren’t privileged over others.

2. Support professional staff

OpenStreetMap US has an amazing executive director and professional staff who continue to excel in their large slate of responsibilities. These include running conferences and working groups, supporting mappers and tools, and helping the public use and understand OSM.

I am the only board candidate to have previously been a paid employee of OpenStreetMap US, giving me extensive firsthand knowledge of the organization.

If elected, I would be a stalwart advocate and supporter of the org’s professional staff, making sure they have the space and resources to carry out the mission of OpenStreetMap US.

3. Perform outreach

A core but often underappreciated role of a nonprofit board member is to interface with people outside the organization. Educators, researchers, organizers, nonprofits, governments, and companies are just some of the stakeholders who use or should be using OSM data, and who should be giving back.

I’ve attended over a dozen geospatial conferences since 2019. Most recently, I attended State of the Map Europe at my own expense as a representative of the US mapping community, hoping to improve understanding with European mappers.

But the bigger task for a board member is to represent OSM US in non-OSM spaces in an effort to build partnerships and solicit funding. If elected, ensuring the financial solvency of OSM US would be a top priority for me.

Election

To vote, make sure you are a member of OpenStreetMap US before February 22, 2026. You will receive your ballot via email. Please vote by March 1. Thank you again for considering my candidacy.

7 days ago

About me

I started mapping in 2021 as I tried to ride every street in Brooklyn, NY on wandrer.earth. I kept finding private streets and other issues on OSM and began fixing them.

At the moment I split my time between the Seattle area and Tucson, Arizona. My professional work is in non-profit accounting. I have worked with a number of organizations covering a full range of financial responsibilities. Handling everything from hands on bookkeeping to grant management to financial strategy.

My mapping

My most cohesive, complete project is detailed mapping of Train Mountain Railroad, the worlds longest miniature railroad. If you’re curious I gave a talk at State of the Map US in 2024 about it.

Most of my mapping is more miscellaneous in nature. I’m a big StreetComplete user, and I’ll always pull over on a bike ride to map a public bookcase! I also enjoy contributing detail to pedestrian and bicycle networks.

Board service and goals

Through the last two years serving as the Board Treasurer I have help usher OpenStreetMap US through a number of shifts in financial situation. Guiding the staff through financial challenges and changes in financial structure.

Through the next two years I want to continue this work, and assist the staff in streamlining bookkeeping and reporting. In addition, as a best practice I would like to see the organization through a financial audit or review. Ultimately leaving the organization on an even stronger financial foundation than it is today.

8 days ago

 

♦Starting and ending in Embleton, on today's ride I covered 18 miles. If I'd followed this route a century ago I would have ridden past four stations.

1. The first would have been Christon Bank Station. This lies just outside Embleton but for some reason was named after a nearby farm rather than the village. It opened in 1847 and closed in 1965. In addition to a limited volume of passenger traffic the station also carried whinstone from the nearby Embleton Quarry. The two were linked by a narrow gauge tramway. More details <here>.
2. The second would have been Fallodon which opened in 1847 and closed in 1934. Only a mile or so from Christon Bank, this was another complete station with two platforms, name boards and a station house. But it was never intended for the general public. They used Christon Bank Station. Fallodon was solely for the use of the Grey family, their guests and their servants. The Grey family also had a private station at Little Mill: four miles south, close to the other family seat at Howick Hall. At the time, the proprietor of Fallodon Hall was Sir George Grey, who was Home Secretary. The passage of the Newcastle & Berwick Railway Bill through Parliament was eased by providing him with a private station and the right to stop any public train. More details <here>.
3. The third was Chathill Station (pictured above). This opened in 1847. At the time there four passenger trains called every weekday in both directions. Now there are only two services each way on a weekday and none on Sunday. The station building is now a private house. It is listed, Grade-2, but the station is unstaffed and has no ticket facilities or other amenities.
4. From 1898 Chathill Station was the south-western terminus of the North Sunderland Railway. This was built to serve the harbour at Seahouses. The line was rarely profitable and a proposed extension to Bamburgh was never constructed. It was taken over by the LNER in 1939, and closed in 1951. Seahouses station was then demolished. The site where it stood is now the village car park and (importantly on a cold day) also houses the public toilets. For a view of how the North Sunderland line looked about 100 years ago (with its one loco and three coaches) see the Pathe film <here> and more information <here>.

We've had a lot of rain recently. Fields are flooded and ditches over-flowing. But the weather today was an improvement. Some mist, and a noticeable headwind on the return journey. No proper rain, patches of blue sky and even a little sunshine were very welcome. 

8 days ago

29/01/2026-04/02/2026

♦

[1] OSM Kids! | © MapLibre – OpenFreeMap – OpenMapTiles – map data © OpenStreetMap Contributors.

Mapping

• Two proposals are waiting for your vote:
  • The flashing_lights=* proposal as of Thursday 5 February 2026. The proposal suggests a new design for flashing lights beyond just crossings.
  • The markers indication proposal until Tuesday 17 February 2026. This proposal is intended to introduce minimal necessary tagging to solve the indication of utility markers on their respective map markers.

Mapping campaigns

• The Italian OSM community’s January campaign ♦ ended and it has resulted in the addition ♦ of 30,000 Wikidata links across the country. Following a community vote ♦ February’s project will focus on mapping street lamps and lit=* tags.
• Developed in response to the OpenStreetMap Italia community’s street lamp mapping initiative ♦, Matt Whilden launched an interactive dashboard that visualises street lamp mapping progress, featuring daily data updates, a leaderboard, baseline and newly mapped lamps, and a time-slider for tracking changes over time.
• DNL852 has created a machine learning algorithm to identify all the pedestrian zebra crossings in Slovakia and Czechia. The newest local orthophoto imagery was used and the process can be also used for other easily recognisable objects (e.g. to identify bus stops painted on the street or colourful recycling containers or others). The results of the ML algorithm were transferred to a MapRoulette challenge.

Community

• FOSSGIS congratulated ♦ OSGeo on its 20th anniversary and expressed hopes for continued wider adoption of open-source software in the geospatial domain, along with healthy growth of a globally active community.
• reDoubleYou described the status of his mapping activities around the town of Sa Pobla on the Spanish island of Mallorca in a blog post.
• Andy Townsend has noticed a growing trend in the UK of pubs near railway stations installing electronic departure boards, and subsequently developed a Postpass query to locate OpenStreetMap objects tagged with amenity=pub in combination with departures_board=*.

OpenStreetMap Foundation

• The SotM Organising Committee explained how the SotM 2026 Travel Grant Programme supports accessibility and diversity for the global SotM, to be held in Paris, France, offering multiple grant sizes from free tickets to up to £1,300 to help with travel and accommodation costs. The programme’s call for applications is open until 1 March 12:00 UTC and includes smaller remote-attendance grants to subsidise mobile data for those with limited connectivity. The selection process uses a points system to rank applications and aims to enhance participation from a diverse range of contributors, especially first-time attendees.
• The Wikimedia Foundation’s Product and Technology team has notified the OpenStreetMap Foundation system administrators that access to Wikimedia APIs for the OSM wiki may be restricted due to inefficient use of Wikimedia Commons images. To avoid a potential block, the team has requested that image requests be limited to standard thumbnail sizes. As a result, minor adjustments to thumbnail dimensions may appear across the wiki in the coming days, and any resulting layout issues are being monitored.

Local chapter news

• The Overture Maps Foundation has become a supporter of OpenStreetMap US, as an Organisational Member at the Strategic level. Overture’s membership will be used to support OSM US tooling, namely MapRoulette, which is a tool that makes it easier for mappers to contribute to OpenStreetMap.

Events

• The team behind State of the Map Europe 2025 have sent out their final newsletter, with links to reports, photos, and session recordings from the conference.

Education

• soundsbeard has published a video on makertube.net with the title ‘openstreetmap (osm). ways to contribute’, which deals with ways to contribute to OpenStreetMap, from JOSM to StreetComplete and other tools.

Maps

• [1] Daniel Schep announced OSM Kids! at Mapping USA 2026, an OpenStreetMap-based interactive Web map that emphasises the visibility of child-themed points of interest, such as playgrounds, theme parks, and toy shops.
• Minh Nguyễn has released a proof of concept of OpenHistoricalMap Americana, which applies OpenStreetMap Americana’s cartographic design to OpenHistoricalMap’s historical road coverage.
• hmaharoof has developed OpenMediaMap, an open and free crowdsourced initiative aimed at digitising and geo-locating historical photographs while preserving their accompanying information. The platform accepts submissions of photographs taken before 1 January 1930.
• OpenStreetMap Americana can now simulate a globe, as an alternative to a Web Mercator projection.
• For their detailed mapping and documentation of the historical Jewish cemetery in Gruenstadt (State of Rheinland-Pfalz, Germany) (we reported earlier), Mannheimer Mapathons and its partners in Gruenstadt were named ♦►♦ as award-winners in the state competition Ehrenamt4.0 (Volunteer4.0). The award was given by the State President, Alexander Schweizer, at the Chancellery in the castle in Mainz (state capital) on 17 January 2026.

OSM in action

• Victor M, of Pplware, has reported ♦►♦ about several new features of Mapbox’s in-car navigation system. The system has been deployed in select vehicle models, including the 2026 Toyota RAV4.
• In response to Storm Kristin that severely impacted Portugal, SOS Leiria has launched ♦ an emergency platform ♦, powered by OpenStreetMap data, enabling users to request or offer assistance at specific locations. The service requires no account registration and includes offline functionality, allowing it to operate even when internet connectivity is disrupted during emergency situations.

Software

• Andres Gomez Casanova reported on an ‘OSM Mesh Notes Gateway’ ♦ project published on Github by the Asociación de Cartografía Colaborativa de Colombia. It is a system designed to support mapping activities during disasters and other connectivity outages.
• Eugene highlighted several key features of OsmAnd Web Explore, demonstrating the tool by exploring notable locations across Patagonia in South America.
• OsmAnd presented their ski profile: detailed piste, lift and route maps for alpine adventures, including 3D terrain and avalanche warning colours. Ideal for skiers and ski tourers, based on OSM-Datenosmand.net.
• openstreetmap-website welcomed the new year with new progress on the transition to MapLibre, as well as a number of small improvements.
• Aron Sommer has released OpenMapEditor, an open-source, local-first web editor for personal geographic data. It supports drawing paths, areas, and markers, importing and exporting GeoJSON, GPX, KML, and KMZ files, routing, elevation profiles, custom WMS layers, a POI finder using OpenStreetMap’s Overpass API, and Strava integration. All processing happens in the browser. The source code is available under the AGPL-3.0 licence.
• Organic Maps launched the gtfs-osm-matcher, a tool to build mappings between stops in various GTFS feeds and OpenStreetMap, enabling GTFS data to be displayed on the map.
• rphyrin has developed offosm v26.2.3, an OSM map that you can access while you’re offline.
• TrickyFoxy published a recap highlighting all feature additions made to the better-osm-org userscript throughout 2025.

Programming

• sphaerophoria, in his streams, has built his own map engine based on OpenStreetMap data in a somewhat chaotic style. He processes OSM in real time, prepares geometry for the GPU, and renders the map using WebGL.
• Paul Norman explained how to use the OSMF vector tiles to create custom vector tiles, with a focus on rendering trees and forests.

Releases

• CoMaps is now available on the Linux desktop.
• Organic Maps has released its January 26 update, fixing out-of-memory crashes when planning cross-country routes and adding GeoJSON export support for bookmarks and tracks.

Did you know that …

• … you can retrieve statistics about instances of the uMap on GitLab?

Other “geo” things

• In 2008, the city of North Oaks asked Google to remove its Street View imagery, arguing that it violated the city’s trespassing ordinance. In 2026, Chris later exploited a series of legal loopholes to map the city despite the long-standing restrictions.
• Citizen science is being used by cryosphere scientists to study and monitor the Arctic permafrost in a project titled UndercoverEisAgenten, which takes us on a drone journey over the ever-changing permafrost landscapes.
• David Oesch released a proof of concept for the automated detection of topographic features from aerial imagery using AI. This project utilises open-source models to identify objects such as buildings or roads and provides this information for mapping applications. A guide explains the local installation of the tools for individual experiments with geospatial data. Developers and mappers can now experiment with automated terrain mapping using open-source resources.
• netzbegrünung has published a map illustrating which microblogging network leads in the number of posts using hashtags of the German state capitals, based on data collected between 1 September 2025 and 31 January 2026 across X, the Fediverse, and Bluesky.

Upcoming Events Country Where Venue What When ♦ Montpellier La Base Mapathon OSM à La Base : cartographier Haïti pour la prévention des risques ​ ♦ 2026-02-05 ♦ Dresden Bottoms Up, Dresden Stammtisch Dresden ♦ 2026-02-05 ♦ Montrouge Réunion des contributeurs de Montrouge et du Sud de Paris ♦ 2026-02-05 ♦ Freiburg im Breisgau CCCFR OSM-Treffen Freiburg/Brsg. ♦ 2026-02-05 ♦ Amersfoort De War Amersfoort Workshop OpenStreetMap ♦ 2026-02-05 OSMF Engineering Working Group meeting ♦ 2026-02-06 ♦ Braunschweig Stratum 0 Braunschweiger Mappertreffen im Stratum 0 Hackerspace ♦ 2026-02-07 ♦ København Cafe Bevar’s OSMmapperCPH ♦ 2026-02-08 Missing Maps : Mapathon en ligne – CartONG [fr] ♦ 2026-02-09 ♦ Grenoble La Turbine Atelier de février 2026 du groupe local de Grenoble ♦ 2026-02-09 ♦ 臺北市 MozSpace Taipei OpenStreetMap x Wikidata Taipei #85 ♦ 2026-02-09 ♦ EPN d’Arlon, rue de Diekirch 37, Arlon EPN d’Arlon – OpenStreetMap – Utilisation ♦ 2026-02-10 ♦ Milano Building 3A Ground Floor – Politecnico di Milano PoliMappers Maptedì ♦ 2026-02-10 ♦ Hamburg Voraussichtlich: “Variable”, Karolinenstraße 23 Hamburger Mappertreffen ♦ 2026-02-10 ♦ New York Online MSF USA Virtual February Mapathon ♦ 2026-02-11 ♦ Zürich Bitwäscherei Zürich 184. OSM-Stammtisch Zürich ♦ 2026-02-11 ♦ München Echardinger Einkehr Münchner OSM-Treffen ♦ 2026-02-11 ♦ Wien Schlupfwinkel (Kleine Neugasse 10, 1040 Wien) 77. Wiener OSM-Stammtisch ♦ 2026-02-11 Online Mapathon von ÄRZTE OHNE GRENZEN ♦ 2026-02-11 ♦ Seattle 1215 E Columbia St, Seattle, WA 98122, US Olympia, Connected ♦ 2026-02-12 UN Mappers: Validation Training ♦ 2026-02-13 ♦ Delhi ILUGD Meetup × OSM Delhi Mapping Party No.26 (North Zone) ♦ 2026-02-15 ♦ EPN d’Arlon, rue de Diekirch 37, Arlon EPN d’Arlon – OpenStreetMap – Contribution ♦ 2026-02-17 Missing Maps London: (Online) Mid-Month Mapathon [eng] ♦ 2026-02-17 ♦ Lyon Tubà Réunion du groupe local de Lyon ♦ 2026-02-17 ♦ Bonn Dotty’s 197. OSM-Stammtisch Bonn ♦ 2026-02-17 ♦ Online Lüneburger Mappertreffen (online) ♦ 2026-02-17 ♦ MJC de Vienne Réunion des contributeurs de Vienne (38) ♦ 2026-02-18 ♦ Karlsruhe Chiang Mai Stammtisch Karlsruhe ♦ 2026-02-18 ♦ Karlsruhe Geofabrik, Amalienstraße 44, 76133 Karlsruhe Karlsruhe Hack Weekend February 2026 ♦ 2026-02-21 – 2026-02-22 ♦ Belfast School of Geosciences, Queen’s University Belfast Belfast Mapathon ♦ 2026-02-21 ♦ TAK Kadıköy Tasarım Atölyesi OpenStreetMap Outdoor Editing ♦ 2026-02-21 ♦ Atelier Vélo Utile Rencontre OSM Saint-Brieuc ♦ 2026-02-21 ♦ Kalyani Nagar TomTom Pune Office, India OSM Mapping Party at TomTom Pune, India ♦ 2026-02-21 ♦ Mumbai OSM Mumbai Mapping Party No.7 (Western Line – South) ♦ 2026-02-22 Missing Maps : Mapathon en ligne – CartONG [fr] ♦ 2026-02-23

Note:
If you like to see your event here, please put it into the OSM calendar. Only data which is there, will appear in weeklyOSM.

This weeklyOSM was produced by MarcoR, MatthiasMatthias, Minh Nguyen, PierZen, Raquel Dezidério Souto, Strubbl, Andrew Davidson, barefootstache, derFred.
We welcome link suggestions for the next issue via this form and look forward to your contributions.

9 days ago

Die FOSSGIS-Konferenz 2026 findet vom 25.-28. März 2026 in Göttingen und Online statt. Es sind nur noch wenige Wochen bis zur Konferenz. Die Vorfreude wächst stetig und die Vorbereitungen laufen auf Hochtouren!

Die Konferenz wird vom gemeinnützigen FOSSGIS e.V, der OpenStreetMap Community in Kooperation mit dem Geographischen Institut der Georg-August-Universität Göttingen organisiert und findet auf dem Campus der Uni Göttingen statt.

Auch in diesem Jahr zeichnet sich ein großes Interesse an der Konferenz ab. Die Anmeldungen steigen von Woche zu Woche. Zum Glück bietet das Zentrale Hörsaalgebäude der Uni Göttingen ausreichend Platz, so dass es die bisher größte FOSSGIS-Konferenz werden könnte.

♦

Der Zeitplan

Das Konferenzprogramm findet von Mittwoch bis Freitag im Zentralen Hörsaalgebäude (ZHG) der Uni Göttingen statt. Am Samstag finden OSM-Samstag und Community Sprint an der Fakultät für Geowissenschaften und Geographie am Nordcampus statt.

Die Konferenz startet in diesem Jahr schon am Dienstag, den 24.03.2026 ab 10 Uhr mit längeren Workshops (180 Minuten). Wählen Sie unter 7 Workshops aus siehe Programm: fossgis-konferenz.de/2026/programm/ und reisen Sie schon ganz entspannt am Dienstag an.

FOSSGIS 2026 Programm

Das FOSSGIS Team freut sich auch in diesem Jahr auf ein spannendes Programm mit zahlreichen Vorträgen, ExpertInnenfragestunden, Demosessions, BoFs und Anwendertreffen und sowie 28 Workshops.

www.fossgis-konferenz.de/2026/programm/

Die Workshops sprechen sowohl Einsteiger:innen als auch Fortgeschrittene an, es sind noch Plätze frei. Buchen Sie gerne noch einen Workshop und nutzen Sie die Chance in kurzer Zeit Wissen zu einem Thema aufzubauen.

FOSSGIS vernetzt - Anwendertreffen und Community Sprint

Rund um die und während der Konferenz gibt es zahlreiche Möglichkeiten sich zu vernetzen. Die Pausenversorgung kombiniert mit Firmen-Ausstellung und Poster-Ausstellung finden im Foyer des ZHG statt sowie auch die Abendveranstaltung am ersten Konferenztag. Für die fachliche Vernetzung bieten sich Gelegenheiten bei den Anwendertreffen, Expert:innenfragestunden und weiteren Community Sessions, eine Onlineteilnahme ist möglich. www.fossgis-konferenz.de/2026/socialevents/

FOSSGIS Konferenz 2026 Sponsoren

Herzlichen Dank an die Sponsoren der Konferenz. die durch Ihre Unterstützung maßgeblich zur Finanzierung der Veranstaltung beitragen. Werden auch Sie FOSSGIS-Sponsor. Wir freuen uns über weitere Unterstützung. Informationen finden Sie unter fossgis-konferenz.de/2026/#Sponsoring

♦

FOSSGIS - ein Teamevent

Die FOSSGIS lebt vom ehrenamtlichen Engagement, zahlreiche Helfer*innen bringen sich ein und übernehmen unterschiedlichste Aufgaben vor und während der Konferenz. Herzlichen Dank dafür!

Es werden noch Helfende gesucht, insbesondere für Sessionleitung, Unterstützung im Hörsaal für die Vortragenden sowie beim Catering, siehe www.fossgis-konferenz.de/2026/helfen/.

OSM-Samstag und Community Sprint

Am Samstag, den 28.03.2026 werden OSM-Samstag und Community Sprint in den Räumen des Geographischen Instituts in der Goldschmidtstr. 3-5, 37073 Göttingen stattfinden. Die Gelegenheit ins Gespräch zu kommen oder beim Community Sprint sich einzubringen oder Know-How aufzubauen. Jede:r ist herzlich willkommen teilzunehmen. pretalx.com/fossgis2026/talk/VVYN7A/

Reichhaltiges Rahmenprogramm

In diesem Jahr freuen wir uns über ein vielseitiges Rahmenprogramm mit spannenden Exkursionen und Treffen in interessanten Lokationen Göttingens. FOSSGIS steht auch für Netzwerken. Dies ist schon am Dienstagabend möglich. Die Geochicas laden zu einem Treffen ein. Außerdem findet der Inoffizielle Start mit einem gemeinsamen Abendessen (Selbstzahler) statt und heißt alle schon angereisten Konferenzteilnehmenden willkommen.

Alle Informationen finden sich unter www.fossgis-konferenz.de/2026/socialevents/

Informiert rund um die Konferenz

Informationen rund um die FOSSGIS finden sich unter dem Hashtag #FOSSGIS2026. Den Haschtag #FOSSGIS2026 nutzen wir für Informtionen in den Social Media, nutzen sie es auch, um die Social Media Aktivitäten zu verbinden.

Archiv FOSSGIS-Konferenzen

Im FOSSGIS-Archiv finden Sie spannende Beiträge der letzten Konferenzen fossgis-konferenz.de/liste.html.

Das FOSSGIS Team 2026 wünscht eine gute Anreise und freut sich auf eine spannende Konferenz in Göttingen

a day ago

多言語表記のタグ付けを考える

2026-02-01に’さくらインターネット Blooming Camp’で行われた「マッパーズサミット2026」での発表内容です

パート１: OSMの基礎知識編

発表内容のうち、OSM wikiに記載されている項目の解説を「OSMの基礎知識編」します

「基礎知識」と思ってバカにしないでください。日本の編集のほとんどすべて（９９％以上）がOSM wikiに記載事項に違反しています
また、’talk-ja’などでの意見も OSM wikiに記載事項を理解されていないと思われるものが多いです

♦

実例を使って交差点のタグ付けを考えて見ましょう。

ちなみに、この例は私の自宅近くにある交差点で一般的なものです、特殊な例ではありません。

• 交差点なので junction=yes とします。

♦

案内板に表示されている「虚空蔵橋際」をタグ付けします

• 「虚空蔵橋際」をそのまま name = 虚空蔵橋際 とします。

♦

アルファベット表記になっている部分をタグ付けします

この部分は @国土交通省では「国際化に対応する・・・」とされています

• 国際化表記部分なので int_name = Kokuzobashi とします

♦

この部分は @国土交通省では「ローマ字表記」とされていますが、「英語」と「ローマ字」が混じった表記とされています

• 「英語/ローマ字」の判断が必要です → 「bashi」となっているので「ローマ字表記」と考えられます name:ja-Latn = Kokuzobashi とします

♦

案内標識のローマ字表記は「長音」が省略されています。 OSMwiki では’省略してはいけない’ことになっているので「省略された長音」を補完します

• name:ja-Latn = Kokuzō-bashi とします
  • 「省略しない」@wiki/JA:名称#略称
  • 「name:ja-Latnのローマ字表記にはūやōなどのマクロン付きの文字を使用する」@wiki/JA:Japan_tagging#地名の入力規則

♦

[OSM wiki]には「現地語名称は言語明示サブキーと重複させてください」とあります

• 日本では現地語名称は「日本語」なので name:ja = 虚空蔵橋際 を追加します
  • 「現地語名称は言語明示サブキーと重複させてください 」@wiki/JA:多国語の名称#言語明示タグによる複数回の名前付け

♦

案内標識のローマ字表記は”省略”されています。 OSMwiki では’省略してはいけない’ことになっているので「省略された部分」を補完します

この例では「際」が省略されています

• name:ja-Latn = Kokuzō-bashi-giwa とします
  • 「略称は使用しないでください」@wiki/JA:名称#略称

♦

osmwiki/JA:名称に「特定の言語での名前（name:en=…）の使用を検討してください」とありますので、int_name に対応する name:en の使用を検討します

• 「特定の言語での名前（name:en=…）の使用を検討してください」@osmwiki/JA:名称

♦

name:ja-Latn と同様に、name:enについても省略された「長音」と「省略部分」を補完します

• name:en = Kokuzoh bridge side とします
  • 「特定の言語での名前（name:en=…）の使用を検討してください」@wiki/JA:名称#名称キー int_name
  • 「略称は使用しないでください」@wiki/JA:名称#略称

♦

name:en,name:ja,name:ja-Latn は一致させる必要があります。つまり int_nameからname:enを作るのではなく、nameからname:enを作ります

• 「name=虚空蔵橋際」の「虚空蔵橋」は「ごくぞうばし」と読むので name:en = Gokuzoh bridge side とします

♦

ここで「ローマ字表記」部分が変更された場合を考えてみます

• 案内標識のローマ字表記部分が「Gokuzou Bridge」に変更された場合は、int_name = Gokuzou Bridge に変更します。
• name:en,name:ja-Latnを変更する必要はありません
  • 平成26年に発令された「改正標識令」により、2026年現在で約60％の「ローマ字表記」部分が変更されました。残りの40％程度が今後変更される可能性があります。
  • 令和７年に「内閣告示」が改定されましたので、またローマ字表記が変更されることが予想されます

♦

@osmwiki:多国語の名称には、「存在しないものには名称をタグ付けしないでください。」「その他すべての言語に対して name: タグをつけるべきではありません!」とあります

• 有名な「渋谷交差点」を見てみましょう。name:en以外の16カ国語が設定されています。
  • 「[その他すべての言語に対して name: タグをつけるべきではありません](osm.wiki/JA:%E5%A4%9A%E5%9B%BD%E8%AA%9E%E3%81%AE%E5%90%8D%E7%A7%B0)」というOSM wiki の規定に違反した状態になっています

♦

osmwikiに「存在しないものには名称をタグ付けしないでください」とあるにも関わらず、@osmwiki:名称には「特定の言語での名前（name:en=…）の使用を検討してください」と矛盾した記述があります

name:enが特別扱いされる理由は,フォールバックした言語で現地語の名称を表示する場合に、目的の言語が存在しないときは’英語の名称’を表示するためです

つまり、name:enはレンダリングのためのタグ付けということになります

• 「存在しないものには名称をタグ付けしないでください」@osmwiki:多国語の名称
• 「特定の言語での名前（name:en=…）の使用を検討してください」@osmwiki:名称には
• 「[フォールバックした言語で現地語の名称を表示する場合に英語の名称を表示」@JA:多国語の名称#理由

♦

『name:enはレンダリングのためのタグ付け』というのはOSMの原則に反することになります

そのため、「特定の言語での名前（name:en=…）の使用を検討してください」というOSMwikiの基準に矛盾する記載が OSM wiki に多く見られます。

• 「”名前に複数の言語タグが付けられている場合”に注意してください。名前が1つの言語のみでタグ付けされ、今後もその状態が続くと予想される場合、この方法のメリットは大幅に小さくなり、めったに行われません。また、この方法は議論の余地があります。特に単一言語地域では顕著です。@wiki/JA:多国語の名称
• 「存在しないものには名称をタグ付けしないでください」 @wiki/JA:多国語の名称#言語明示タグによる複数回の名前付け
• 「翻訳は回避すべき」@wiki/JA:多国語の名称#課題
• 「通常の綴り規則から逸脱していても、標識にある通りに入力します」@[wiki/JA:名称#良いやり方](](osm.wiki/JA:%E5%90%8D%E7%A7%B0#%E8%89%AF%E3%81%84%E3%82%84%E3%82%8A%E6%96%B9)
• 「標識のような地物の名前を示すものがあるときに限って、名前をタグ付けすべきです」@wiki/JA:名称#名称で説明しない

♦

ここまでのタグ付けをまとめてみましょう

name と int_name は、標識に記載された内容をそのまま設定している

しかし、name:ja以外の name:en,name:ja-Latnは、マッパーの思考・嗜好が反映されたものとなっています

♦

立場をかえて、日本人である私達は、USAの「ゴールデンゲートブリッジ」のことを「金門橋」と呼んでいます

このことをOSMに入力することはできるのでしょうか？

• ‘リレーション: Golden Gate Bridge‘に、name:ja = 金門橋 をタグ付けすることは、OSM wikiに明確に否定されています
  • 「存在しないものには名称をタグ付けしないでください」 @wiki/JA:多国語の名称#言語明示タグによる複数回の名前付け
  • 「翻訳は回避すべき」@wiki/JA:多国語の名称#課題
  • 「通常の綴り規則から逸脱していても、標識にある通りに入力します」@wiki/JA:名称#良いやり方
  • 「標識のような地物の名前を示すものがあるときに限って、名前をタグ付けすべきです」@wiki/JA:名称#名称で説明しない

♦

では、「金門橋」のような現地に表示が情報はどうすればよいのでしょう？

それは、wikidataと連携させて間接的にOSMに反映させることができます

• wikidataの「ゴールデンゲートブリッジ」に、「金門橋」を入力します
• OSMの’リレーション: Golden Gate Bridge‘に、wikidata=Q44440 として、Wikidataとリンクさせます

wikidataとのリンクで ‘name:XX’ が無効化

wikidataとリンクすると、iDエディタでは ‘name:XX’ がグレーアウトして ‘name:XX’が編集できなくなることに注目してください。

wikidata と OSM では扱うデータが住み分けられています。

• wikidata :
  公開された文献(Webデータを含む)に記載された情報
• openstreetmap :
  現地の事実情報(位置情報を持つものに限る)

つまり、nameやint_nameは現地の事実情報なので
- –> OpenStreetMapに入力(OSM wikiでも推奨しています)

いっぽう、name:XX は、現地に表記されていない情報なので
- –> Wikidata は、公開情報に記載があれば入力できる - –> OpenStreetMapに入力できない(OSM wikiでも現地に表記のないデータは入力しないことになっています)

POIが wikidata とリンクした時点で、OSMのデータとしては不適切なname:XX は、用無しとなります
以後、name:XXを編集することは意味がありませんし、name:XXはゴミデータになります

♦

もし、’wikidata’は 『’wikipedia’のようなもの』と認識しているのでしたら、それは間違いです。
‘wikidata’は、’wikipedia’よりも『’OpenStreetMap’のようなもの』と認識したほうが正しいです。

‘wikipedia’と’OpenStreetMap’は、互いに補完しあうことでデータの一貫性を担保することができるようになっています。
また、そのための仕組みや強力なツールも整備されています

• wiki/JA:Wikidataには 「wikidataとのリンク」の重要性が説明されています
  • 1 なぜウィキデータにリンクするのか？
    • 1.1 ウィキデータはウィキペディアではない
  • 2 OSMからウィキデータへのリンク
    • 2.1 タグの修飾子として
    • 2.2 ツール
      • 2.2.1 OSM要素にウィキデータをリンクする
      • 2.2.2 検証ツール
      • 2.2.3 品質保証
    • 2.3 ウィキデータのユーザースクリプト
  • 3 ウィキデータからOSMへのリンク
    • 3.1 ウィキデータにおけるOpenStreetMap関連のプロパティ
    • 3.2 OSMタグとキー

♦

ライセンス上の理由により、OSMのデータをwikidataへコピーすることは禁止されています

• そもそもOSMには、現地に存在する事実情報しかないはずなので、文献データを扱うwikidataへコピーする情報などないはず・・・

♦

ライセンス上の理由により、’wikidata’のデータをOSMへコピーすることは禁止されています

• そもそもwikidataには、文献情報しかないはずなので 現地の事実情報を扱う OSMへコピーする情報などないはず・・・

♦

2 days ago

大阪市の中心付近に、信号停止線に「一時停止」タグがつけられた箇所がたくさんあります。

「一時停止」標識が存在しない場所なので、誤ったタグ付けなのですが、交点に信号機があるだけの状態よりも優れたマッピングです。

しかし、このままでは、初心者マッパーに「誤りだから・・」という理由で単純に削除されてしまう恐れがあります。

♦

改善編集

「osmwiki JA:Tag:highway=traffic_signals」で推奨されている「highway=traffic_signals」に書き換えましょう！

• 信号停止線にある「highway=stop」タグを「highway=traffic_signals」に書き換えます。
• 交差点の交点にあった「highway=traffic_signals」を「junction=yes」に書き換える

♦

2 days ago

Purpose

Safe Routes to School is a program designed to help parents encourage their children to walk and bike to school safely, while promoting healthy engagement. In some locations, walking or biking to school is a child’s only means of getting to school. My goal is to help parents find the best routes to school and to assist them in working with local governments to improve safety. But we need more volunteers to help improve the data.

What We’re Building

• Pedestrian and bike maps
• Child-safe routing opetions
• Walking and biking isochrone (walkshed) tools
• Clear tutorials on how to map for pedestrians and cyclists
• Tools SRTS groups can use in their local communities

Pedestrian and bike maps

Bike maps already exist. Not only does OSM offer two different map layers for cyclists, but there are several apps available. Pedestrian maps are a different story. While there are some pedestrian maps, such as the University of Washington’s Taskar Center for Accessible Technology’s AccessMap.app, they are limited. What is needed is a tool that parents can use to find a good walking route to school, as well as a tool that can help improve pedestrian mapping, much like OpenStreetMap US’s OpenTrailMap.us. The rendering should show pedestrian ways, crossings, accessibility features like tactile pads and kerb ramps.

Routing Engines

OSM has some great routing engines. The user interface will likely need to be improved so that features can be added to avoid. For example, railways may be dangerous for children to cross. By allowing the addition of features to be avoid, it’s possible to provide a safe route.

Walking and biking Isochrones (Walksheds)

Good open-source isochrone maps are available. One of my favorites is Valhalla. Below is an example of an isochrone map of a local elementary school created using Valhalla in QGIS. It shows 5, 10, and 15 minute walk areas. However, there are two major problems with the isochrone. First, it uses streets with no sidewalks. It also crosses the Division Street Bridge, which the school district doesn’t feel is safe for children to cross. If we add an isochrones feature to our pedestrian and bike map, it needs to be able to restrict the isochrones to only safe walking and biking routes.

♦

Mapping for pedestrians and cyclists

Four main features need to be mapped: schools, pedestrian ways, cycleways, and traffic calming features. A how-to page, along with video tutorials are needed to help new mappers get started.

Schools’ buildings, parking, bus drop off areas, main entrance, and bike racks need to be mapped. Emphasis needs to be placed on adding accessibility features for kids with disabilities. See wiki.openstreetmap.org/wiki/Disabilities

The OSM US Pedestrian Working Group has developed a schema for mapping pedestrian ways. Footways, curb ramps, tactile pads, crossings, surface, width, and other features needed to be mapped. I should note that the schema focuses on mapping sidewalks as separate ways, which is not universally accepted. My experience is that mapping sidewalks as a separate way produces better routing.

Bike mapping is well established in OSM. For SRTS, intersection details, like traffic signal mapping is important for the safety of the children.

Traffic calming features, such as speed bumps, traffic islands, choker points, etc, are used to slow vehicle speeds, making walking and biking safer. Additionally, highway classifications and speed limits on roads are needed to help pick safer streets for children to walk or bike to school.

Volunteers Wanted

The project needs your help in bring together the tools needed for parents to find safe routes to school. Below is an incomplete list of what is needed. If you are interested in helping, leave a message below, or join our #safe-routes-to-school channel on the OSM US Slack.

• Tutorial to map sidewalks
• tutorial to map bike routes
• Turorial to map traffic calming features
• Create a background layer to assist mappers add and update pedestrian features
• Making sure that routers (Valhalla, OSRM, GraphHopper) can handle exceptions (next phase)
• Create an isochrone layer for use with the pedestrian layer (later phase)

Final thought

Not only is mapping for SRTS important in helping parents get their kids to school safely, but it also helps document areas that need safety improvements. While local governments typically have a detailed inventory of cycleways, sidewalks, curbs, and roads, they may not have put it together in one source like we do in OSM.

Links:

Safe Routes: National Center for Safe Routes to School www.saferoutesinfo.org/

Federal Highway Administration’s Guidance for the Safe Routes to School Program website: www.fhwa.dot.gov/environment/safe_routes_to_school/guidance/#toc123542171

Safe Routes Partnership website: saferoutespartnership.org/

Washington State Department of Transportation website: wsdot.wa.gov/business-wsdot/support-local-programs/funding-programs/safe-routes-school-program

Seattle PDF: www.seattle.gov/documents/Departments/SDOT/SRTS/SeattleSafeRoutestoSchoolEngineeringToolkit.pdf

Washington Safe Routes to School Network website: www.washingtonsaferoutes.org/

4 days ago

县道、乡道、村道的编号规则是什么？ 答：1.县道命名及编号规则：

（1）命名规则：以起终点行政节点名称第一个汉字加“线”组成，如起于高淳县东坝镇终于高淳县固城镇，则命名“东固线”；如起终点为非行政节点，则以起终点具代表性的名称第一个汉字加“线”组成。

（2）编号规则：本轮县道网编号以现有编号体系为基础，现有县道编号基本保持不变，新增县道编号按照方向和类型，在现有县道编号后依次排列，即“老路老编号、新路新编号”。具体编号原则如下：

①编号由字母和数字共10位构成，如“X105320125”，其中，“X”反映县道的性质；“105”反映线路的类型、方向和顺序；“320125”为线路所在县（市、区）的行政代码（以国家统计局发布的2013年江苏省行政区划代码为准）。

②例：“105”：第一位“1”表示线路方向和类型，“05”表示为顺序码。

“1”开头表示由县城（市、区）向外辐射的树状县道网，顺序码从正北方向顺时针依次增大；

“2”开头表示南北纵向县道编号，顺序码从东向西依次增大；

“3”开头表示东西横向县道编号，顺序码从北向南依次增大；

其中，“101~150”、“201~250”、“301~350”编号，适用于保留、局部延伸或调整的现有县道线路，原有县道线路编号不做调整；“151~199”、“251~299”、“351~399”编号，适用于本轮新增县道和上轮县道规划后陆续增编的临时县道编号线路（即X+字母+两位数字+行政区划代码的线路）。

2.乡道命名及编号规则：

（1）命名规则：以起终点行政节点名称第一个汉字加“线”组成，如起于溧水区晶桥镇止于溧水区晶桥镇新山里村，则命名“晶新线”；如起终点为非行政节点，则以起终点具代表性的名称第一个汉字加“线”组成。以上两种命名规则，必须保证在同一县域范围内名字不重复。

（2）编号规则：路线编码由行政等级代码+三位编号+县级行政区划代码共十位组成，具体表示方法如下所示：

“Y”：代表乡道的行政等级代码；“101”：代表乡道的排列顺序编码，采用“老路老编码，新路新编码”原则，老线路以及延伸段采用原有编码，新线路编码从“AA0”开始至“ZZ9”；“320111”：代表该县（市、区）的行政代码。

县（市、区）交通运输局根据各乡镇的实际情况拆分乡道编码，确保县（市、区）域范围内乡道编码的唯一性。

3.村道公路命名及编号规则：

（1）命名规则：以起终点行政节点名称第一个汉字加“路”组成，如：起于溧阳市上兴镇建盟村，终于溧阳市上兴镇红旗村，则命名“建红路”；如起终点为非行政节点，则以起终点具代表性的名称第一个汉字加“路”组成。以上两种命名规则，必须保证在同一县（市、区）域范围内名字不重复。

（2）编号规则：路线编码由行政等级代码+三位编号+县级行政区划代码共十位组成，具体表示方法如下所示：

“C”：代表村道的行政等级代码；“101”：代表村道的排列顺序，采用“老路老编码，新路新编码”原则，老线路以及延伸段采用原有编码，新线路编码从“AA0”开始至“ZZ9”；“320125”：代表该县（市、区）的行政区划代码。

县（市、区）交通运输局根据各乡镇的实际情况拆分村道编码，确保县（市、区）域范围内村道编码的唯一性。

5 days ago

Вітаю, спадарства!

Неўзабаве скончыў перакладаць openstreetmap на клясычную (тарашкевіцу).

Спроба сыстэматызаваць тое што было, пасьлядоўна ды ґрунтоўна прайшоўся водле працы якую пачалі ўжо даўно. Пэўныя тэрміны, магчыма, будуць незразумелымі ці нязвыклымі, мэтай была ўжываць нашыя спрадвечныя адменьнікі, унікаючы калькаваньня.

Цяпер патрэбная вычытка, прыбраць хібу, якую я мог дапусьціць.

Пераклад ужо бачны на сайце, каб пабачыць трэба выбраць мову, яна ніжэй, пад “беларуская”. Перакладзены толькі сайт, не id-рэдактар, там нашмат болей працы, і іншы пляц для перакладу, не такі зручны як translatewiki.

6 days ago

For a while, I was interested in understanding what makes one pedestrian OSM way better than another. I wanted to know if there is some generic way to identify good walking routes from OSM data. I looked at Garmin and Strava heatmaps at first. Then I checked Strava segments and their proximity to points of interest such as rivers, ponds, and parks. Then I thought to look at my running pace along OSM ways to separate good and not-so-good walking routes. My idea was simple — a good walking route means a smooth running pace. There are fewer stops, less waiting at intersections, etc. Of course, my pace depends on many factors, such as how far I have to run to get to a certain place. So it cannot be a simple cutoff, but rather the distribution of paces along a given segment. This turned out to be a reasonably good approximation of how good or bad I perceive each route to be. I created this Kaggle dataset as an illustration. This relies on my personal GPX data, so it does not scale, but it captures the kind of local knowledge that I find hard to share in any other way.

7 days ago

I mainly edit OSM based on GPX files from my runs. I use JOSM. I created a simple script to extract a buffered area around my GPX files to make sure I don’t accidentally edit parts of OSM I don’t intend to. See this Github Gist for the source.

7 days ago

Eu odeio relações de ônibus

8 days ago

En mi entrada anterior “Procesamiento en tiempo real de notas de OSM con Bash” expliqué cómo mantener una base de datos local sincronizada con las notas de OpenStreetMap en menos de 10 segundos, usando herramientas comunes de Linux y PostgreSQL. Ese trabajo permitió tener un repositorio actualizado y confiable de notas, comentarios y cambios de estado.

Hoy quiero mostrar el siguiente paso: cómo esa base de datos se convierte en un servicio WMS que permite visualizar las notas directamente en aplicaciones como JOSM, Vespucci o QGIS. De esta manera, pasamos del procesamiento en segundo plano a la representación gráfica en el mapa, abriendo nuevas posibilidades para mapeadores e investigadores.

Las Capas del Servicio

El servicio ofrece cuatro capas principales:

• Notas abiertas (rojo): todas las notas activas, con intensidad de color según antigüedad.
• Notas cerradas (verde): reflejan el trabajo ya realizado, con intensidad según el tiempo desde el cierre.
• Países y zonas marítimas: fronteras, aguas territoriales y ZEE, para dar contexto geográfico y político.
• Zonas en disputa y no reclamadas: áreas donde la asignación de país es ambigua, clave para entender por qué algunas notas no encajan en un análisis nacional.

Casos de Uso

• Priorización de trabajo: un mapeador abre JOSM, carga la capa de notas abiertas y ve un cúmulo de puntos rojos en su ciudad. Decide enfocarse allí.
• Verificación de progreso: un grupo comunitario carga la capa de notas cerradas y observa un mar de puntos verdes, evidencia del esfuerzo colectivo.
• Contexto geopolítico: cerca de una frontera, las notas aparecen en una zona marcada como disputada. El mapeador entiende la ambigüedad en la asignación.
• Análisis espacial: un investigador usa QGIS para estudiar patrones: más notas en áreas urbanas, menos en rurales. El servicio facilita estadísticas y visualizaciones.

Cómo Usarlo

En JOSM:
1. Ir a Imagery → Add WMS Layer…
2. Ingresar la URL: geoserver.osm.lat/geoserver/osm_notes/wms
3. Seleccionar las capas deseadas.

En Vespucci:
1. Abrir configuración de capas.
2. Agregar capa WMS con la misma URL.
3. Activar las capas de notas abiertas, cerradas, países o disputas.

Conclusión

El proyecto avanza en dos etapas complementarias: primero, la ingesta en tiempo real de notas con Bash y PostgreSQL; ahora, la visualización mediante un servicio WMS que las pone directamente sobre el mapa. Juntos, estos componentes permiten a la comunidad OSM analizar, priorizar y coordinar esfuerzos con mayor claridad.

Invito a todos a probar el servicio en JOSM o Vespucci, y a seguir aportando ideas para mejorar esta herramienta que conecta la potencia del procesamiento en tiempo real con la riqueza de la visualización geográfica.

8 days ago

Kilka słów o postępie w nauce, 8 lutego 2026 roku

1. Dodawanie zakresów mieszkań tagiem addr:flats jest tylko informacyjne. Nie pomaga to niestety w nawigacji i możliwości wpisywania adresów z numerem mieszkań do prowadzenia przez nawigację. Stanowi jednak dobry wstęp by w przyszłości “rzeźbić” samemu każde mieszkanie lub by ktoś inny się tego podjął.
2. To dziwne, że nie było automatu Pocztex zaznaczonego na osiedlu Zygmunta starego. InPost, DPD czy one box są dobrze oznaczone w całym mieście, jednak tutaj niezweryfikowane podejrzenia iż to się zaczytuje automatycznie.
3. Podejrzewam, że OSM jest traktowane po macoszemu przez wszystkich. Szczególnie tych, którzy korzystają z tego nieświadomie. Ma to swoje zalety - udało mi się jako pierwszemu dodać dwa urządzenia będące recyklomatami na mapie OSM dla Poznania.

Podsumowując, całkiem przyjemnie jest edytować wiedząc, że nikt mnie nie ubiegnie. Szkoda jednak, że tak wiele jest jeszcze przez to do zrobienia.

9 days ago

The seriousness with which the OpenStreetMap community approaches discussions is a true strength of the project. Over years of debate, the community has formed a highly cohesive tagging system for names. These guidelines are simple for beginners, yet they allow for the precise classification and mapping of real-world names. A name is perhaps the most vital piece of data for most users—it is what they want to see on screens and paper, hear via voice navigation, and even touch.

However, this post isn’t about which tag to choose, but rather the format in which the name should be entered. I want to discuss the phenomenon of ellipsis—or, to put it simply, the shortening of names—and what we as mappers should watch out for when collecting and adding toponyms to the map.

What are elliptical toponyms?

Elliptical toponyms are geographical proper names that have been historically truncated or shortened in oral or written use. These are often names that originally included a generic term (a word indicating the type of object), which over time partially or completely disappeared. The table below shows several examples of such “shortened” Scandinavian and Baltic toponyms:

Historical Full Form Truncated Form Explanation Sed-ezeris Sedzeris The hydronym “Lake Seda” lost the generic term ezeris (lake). Spanggroben Spanget A neighborhood near a stream; the second element -groben (ditch/trench) was dropped. Stampedam Stampen A farmstead near a pond; the second element -dam (pond) was dropped, leaving only the specific element. Sankt Peters Kirche Sankt Peter St. Peter’s Church; the second element Kirche (church) was dropped.

In 1980, the Soviet linguist and translator Adolf Turkin wrote an article titled “Elliptical Names in Komi Toponymy” about this phenomenon, providing many examples of name evolution where the suffix indicating the object type was eventually discarded. You can see a few of these in the table below:

Historical Full Form Truncated Form Translation & Generic Term Kӧdzvidz Kӧdz “Pebble Meadow”; meadow (-vidz) Shudayu Shuda “Happy River”; river (-yu) Ozyu Oz “Strawberry River”; river (-yu) Tarkamayag Tarkama “Pine forest full of grouse leks”; forest (-yag) Ruchguamu Ruchgua “Field riddled with fox holes”; field (-mu)

While these are mostly names that changed long ago, there are more modern examples. In a discussion within the OpenStreetMap Bulgaria community, I asked a question about why the generic term is omitted in all street names. It turns out that dropping the word “ulitsa” (street) is entirely natural in the Bulgarian language, and this was reflected in their local mapping practices:

Full Name (Transliterated) Entered in name tag Context/Notes ulitsa “Zapadna” Zapadna “Zapadna” means “Western.” A common directional street name. ulitsa “Vladaiska” Vladaiska Named after the Vladaiska River, which flows through the heart of Sofia. ulitsa “Uiliam Gladston” Uiliam Gladston Named after William Gladstone, the British statesman

The examples above illustrate this aspect of toponymic evolution worldwide, and the latter shows that the OpenStreetMap community is an active participant in this process. While I won’t presume to advise on mapping approaches in other countries, I believe I have insights to share with project contributors in Ukraine.

Elliptical toponyms in Ukraine

What should we be paying attention to? Language is a living organism, not frozen in time, so names will naturally change. We should accept that the older a name is, the more likely it is to have undergone changes; we should record it as it exists today, not as it once was.

However, we shouldn’t rush to conclude that a name is truly “elliptical.” The absence of a generic word doesn’t always mean the name was historically shortened. Often, it’s just a convenient spoken shorthand or a result of copying from a table or list where the generic term was kept in a separate column or header. A truncated name might be copied from another map where the authors made a “creative” design choice. Ultimately, a mapper might feel the object type is “obvious anyway” and decide to make the name shorter.

Our task is not to codify accidental simplifications, but to verify if the short form actually lives as an independent name: is it written this way on signs, in documents, or official sources? Do people use it this way outside of a specific context? If not, the generic term is part of the name and must not be lost.

Here are examples from Serhiy Pavlenko’s 2013 book, Microtoponyms of Chernihiv-Sivershchyna. Reading it, one might mistakenly think these microtoponyms lack generic terms. In reality, the author lists the generic term followed by a dash and then a comma-separated list of names, omitting the term from each individual entry to save space. Many of these must be mapped in their full form:

Name from the List Full Name Context/Notes Marusenkiv Marusenkiv stavok Marusenko’s pond; named after a family or located near the estate of a man named Marusenko. Khvynenkove Khvynenkove boloto Khvynenko’s marsh; named after the Khvynenko family or a person with that surname. Horile Horile ozero Burnt Lake; “Horile” literally means “burnt” or “scorched.” Nimetskyi Nimetskyi kutok German neighborhood; “kutok” (literally “corner”) refers to a specific section or historical area of a settlement. Kondrativ Kondrativ kutok Kondrat’s neighborhood; named after the estate or family of a man named Kondrat. Baidyne Baidyne urochyshche Baida tract; named after a man with the surname Baida. Ostatna Ostatna dolyna The Last/Remaining Valley; “Ostatna” is a dialectal word for “last.” Note: “dolyna” here refers to a small valley or dell. Semeshkova Semeshkova krynytsia Semeshko’s well; named after a man named Semeshko. Vysoke Vysoke urochyshche High tract; “Vysoke” literally means “high,” likely referring to its elevation. Kovalivske Kovalivske urochyshche Koval tract; named after a man with the surname Koval (which means “Blacksmith”).

To understand when a generic word is mandatory and when it can disappear without losing meaning, we need to look at the structure of the names themselves. Toponyms have different grammatical structures that often signal whether the generic term is an inseparable part of the proper name or merely a clarification.

Grammatical structure of Ukrainian toponyms Agreed attributes (adjectives)

A large portion of proper names on the map of Ukraine are phrases with an agreed attribute. Usually, this is an adjective or numeral that agrees with the generic noun in gender, number, and case.

I suggest recording these in direct syntactic order, as prescribed by Ukrainian grammar. The agreed attribute should come first, followed by the generic noun in lowercase:

1-sha Sadova vulytsia, Soborna ploshcha, Turiiske ozero, Taraneva bukhta, Darnytskyi raion, Zghurivska selyshchna hromada, Krabova bukhta, Chornobylskyi kutok, Dehtiarna zatoka, Borychiv uzviz.

The generic term in such names cannot be omitted; the name would feel incomplete, even if the object type is already defined by top-level tags.

Non-agreed attributes (genitives)

Another large share of names consists of phrases with a non-agreed attribute. This component is a noun in the genitive case that does not change when the generic noun’s case changes. In these names, the generic term should be written first:

ostriv Fainberha (Feinberg Island), pereval Legioniv (Legions Pass), vulytsia Kameniariv (Stonemasons Street), park Zakhysnykiv Ukrainy (Defenders of Ukraine Park), bulvar Verkhovnoi Rady (Verkhovna Rada Boulevard).

If a name looks incomplete or functions like a modifier, check your sources and use the full form including the generic word. Do not drop it, even if the object type is already specified in the tags.

Apposition

Another type of attribute is apposition. Here, the generic term also comes first, followed by a noun in the nominative case that specifically identifies the object. While the previous two types require the generic term as an inseparable part, in this case, it can often be omitted if necessary. Some of the names below are traditionally used without the generic word, or the word is redundant because the mapped object already has a tag describing its type:

misto Lviv (City of Lviv), selyshche Losynivka (Settlement of Losynivka), selo Trypillia (Village of Trypillia), richka Desna (Desna River), hora Hoverla (Mount Hoverla), stantsiia Zhmerynka (Zhmerynka Station), avtozapravka OKKO (OKKO gas station), kafe Teplo (Teplo Cafe), restoran McDonald’s.

However, for names of streets, lanes, and similar objects, generic words should always be preserved. There are no separate tags for different types of streets, and since these objects are used in addressing, their full name carries specific importance:

vulytsia Yaremkivtsi, ploshcha Rynok, maidan Rynok, vulytsia Polivka, provulok Polivka, provulok Khutorok, provulok Romanchukiv Khutir.

Why does this matter to us?

At first glance, debates over “tracts” (urochyshche) or “corners” (kutok) might seem like excessive academicism. However, for OpenStreetMap, the devil is in these details. Ukraine’s rich microtoponymy—all these local corners, ponds, fields, and islets—is living history. By preserving full names, we protect our regional and linguistic identity. OSM remains perhaps the only living project where we can record the names of the smallest features exactly as they have been used for generations.

9 days ago