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.

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

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

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

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

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

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.

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.

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

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.

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.

Eu odeio relações de ônibus

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.

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: https://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.

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. 

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.

29/01/2026-04/02/2026

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.

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:

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:

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:

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:

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.

Те, як серйозно в OpenStreetMap ставляться до обговорень, — справді сильна сторона проєкту. Протягом років таких обговорень спільнота сформувала дуже цілісну систему теґування назв. Ці настанови прості для тих, хто тільки починає, але при цьому дозволяють точно класифікувати та наносити на мапу реальні назви. Саме назва, мабуть, є найважливішим елементом даних для більшості користувачів — адже саме її вони хочуть бачити на екрані й на папері, чути та навіть торкатися.

Але цей допис не про те, який теґ обрати для назви, а про те, у якому вигляді цю назву заповнювати. Я хотів би розповісти про явище еліпсису або, якщо перефразувати, — усічення назв, і про те, на що ми, картографи, повинні звертати увагу під час збору та нанесення на мапу топонімів.

Що таке еліпсовані топоніми?

Еліпсовані топоніми — це власні географічні назви, які історично під час усного чи письмового вжитку були усічені або скорочені. Наприклад, ті, у яких спочатку було родове поняття, що позначало тип обʼєкта, але з часом воно частково або повністю зникло. Нижче у таблиці наведено кілька прикладів таких «усічених» скандинавських топонімів:

У 1980 році радянський лінгвіст та перекладач Адольф Туркін написав статтю «Еліпсовані назви в топонімії Комі» про це явище з багатьма прикладами подібної еволюції назв, коли закінчення, що позначало тип обʼєкта, з часом було відкинуте. Кілька таких назв можна побачити у таблиці нижче:

Усе це, здебільшого, назви, які змінилися давно, але є і сучасніший приклад. В одній із дискусій у гілці місцевої спільноти OpenStreetMap Болгарія я трохи відійшов від теми і поставив запитання про те, чому в усіх назвах вулиць опускається родове поняття. Виявилося, що відкидати слово «улица» цілком природно у болгарській мові, і це було відображено у місцевій практиці нанесення назв на мапу:

Приклади вище добре ілюструють цей аспект еволюції топонімів по всьому світу, а останній ще й те, що спільнота OpenStreetMap не залишається осторонь цього процесу. Звичайно, я не ризикуватиму давати поради щодо підходів до нанесення назв в інших країнах, але думаю, що маю чим поділитися з учасниками проєкту з України.

Еліпсовані топоніми в Україні

Отже, на що я пропоную звертати увагу? Очевидно, що мова не застигла в часі та є живим організмом, тому й назви змінюватимуться разом із нею. Треба спокійно ставитися до того, що чим назва старіша, тим більше вона зазнала змін; і варто фіксувати її не такою, якою вона була колись, а в її сучасному вигляді.

Але не варто й поспішати з висновками про те, що назва є усіченою. Відсутність родового слова не означає, що назва справді була скорочена історично. Часто це просто зручне розмовне скорочення або перенесення із таблиці чи списку, де сама родова назва була зазначена в окремій комірці чи заголовку. Усічена назва може бути скопійована з іншої мапи, автори якої прийняли таке творче рішення. Зрештою, самому учаснику може здатися, що тип обʼєкта «і так зрозумілий», і варто зробити назву коротшою.

Наше завдання — не закріплювати випадкові спрощення, а перевіряти, чи ця коротка форма справді живе як самостійна назва: чи так пишуть на табличках, у документах, в офіційних джерелах, чи так говорять люди поза конкретним контекстом. Якщо ні, значить, родове поняття є частиною назви, і його не можна губити.

Ось приклади назв із книги Сергія Олеговича Павленка «Мікротопоніми Чернігово-Сіверщини» 2013 року, читаючи яку, можна помилково вирішити, що ці мікротопоніми не мають родових слів або втратили їх. Та насправді це не так. Автор зазначає родовий термін на початку, а через тире — перелік назв уже без такого терміну, мабуть, із метою економії місця. Багато з цих назв мають обовʼязково наноситися на мапу у повному вигляді:

Щоб зрозуміти, коли родове слово в назві є обовʼязковим, а коли воно справді може зникнути без втрати змісту, треба подивитися на саму будову назв. Топоніми мають різну структуру, і саме вона часто підказує, чи є родове поняття невіддільною частиною власної назви, чи лише уточненням. Тому далі спробуємо розкласти назви за типами словосполучень.

Структура українських назв

Означення

Велика частина власних назв на мапі України — словосполучення з узгодженим означенням. Зазвичай це прикметник або числівник, який узгоджується з родовим поняттям у роді, числі чи відмінку.

Ці та інші назви я пропоную записувати у прямому синтаксичному порядку, саме так, як це роблять в українському правописі. Узгоджене означення має бути на початку, а вже після нього — означуваний іменник з маленької літери:

1-ша Садова вулиця, Соборна площа, Турійське озеро, Таранева бухта, Дарницький район, Згурівська селищна громада, Крабова бухта, Чорнобильський куток, Дегтярна затока, Боричів узвіз.

Родове поняття у таких назвах не можна опускати, адже назва буде неповною, навіть у випадку, якщо тип обʼєкта описаний теґом верхнього рівня.

Не менша частка назв є словосполученнями з неузгодженим означенням. Цим компонентом виступає іменник у родовому відмінку, що не змінюється одночасно зі зміною відмінка родового поняття. У таких назвах родове поняття потрібно записувати на початку:

острів Файнберга, перевал Легіонів, вулиця Каменярів, парк Захисників України, бульвар Верховної Ради.

Отже, якщо назва виглядає неповною або схожою на означення, варто перевірити джерела й уживати повну форму назви разом із родовим словом. Його не слід опускати, навіть якщо тип об’єкта вже вказаний у теґах.

Прикладка

Ще один різновид означення — прикладка. Тут родове поняття також має бути на початку. Після нього йде іменник у називному відмінку, що конкретніше уточнює це родове поняття. Якщо у двох попередніх типах назв родове поняття було невідʼємною частиною, то у цьому випадку його за потреби можна опускати. Деякі з перерахованих нижче назв традиційно вживають без родового слова, а в деяких воно є надлишковим, бо в нанесеного обʼєкта вже зазначений теґ що описує його тип:

місто Львів, селище Лосинівка, село Трипілля, річка Десна, гора Говерла, станція Жмеринка, автозаправка ОККО, ресторан МакДональдз.

Натомість у назвах вулиць, провулків та інших подібних обʼєктів родові слова слід зберігати завжди. Для різних типів вулиць немає окремих теґів, крім того, ці обʼєкти використовуються в адресації, тому їхня повна назва має особливе значення:

вулиця Яремківці, площа Ринок, майдан Ринок, вулиця Полівка, провулок Полівка, провулок Хуторок, провулок Романчуків Хутір.

Чому це важливо для кожного з нас?

На перший погляд, дискусії про «урочища» чи «кутки» можуть здатися надмірним академізмом, проте для OpenStreetMap диявол ховається саме в таких дрібницях. Багата мікротопонімія України — усі ці кутки, ставки, поля та острівці — є живою історією. Зберігаючи повні назви, ми захищаємо нашу ідентичність та мовний колорит регіону, не даючи мапі стати «стерильною» чи одноманітною. OSM залишається чи не єдиним живим проєктом, де ми можемо зафіксувати назви найдрібніших обʼєктів саме так, як їх вживали поколіннями.

https://en.wikipedia.org/wiki/Akkadian_Empire https://en.wikipedia.org/wiki/Ebla#/media/File:Ancient_Near_East_2400BC.svg https://en.wikipedia.org/wiki/Bell_Beaker_culture https://en.wikipedia.org/wiki/Ebla https://www.historicnewburgh.org/_files/ugd/e582e3_718ec184562a4a38b356d24b99a57131.pdf https://www.usi.edu/media/cprjxhjf/campus-maps-floor-plans_01-21-2022.pdf

Trijn Rembrands (Alkmaar, ca. 1557 – aldaar, 10 juni 1638[1]) was een vrouw uit Alkmaar die bekendheid verwierf door haar vermeende rol tijdens het beleg van Alkmaar in 1573. Ze wordt in historische bronnen en literatuur afgeschilderd als een heldin die dapper meevocht tegen de Spanjaarden. Zij wordt soms de Kenau van Alkmaar genoemd; een duidelijke verwijzing naar Kenau Simonsdochter Hasselaer.) Wikipedia

Op 10 oktober 2025 is in het Victorypark in Alkmaar een standbeeld onthuld ter ere van Trijn. Het locatie met alle tags.

Today, I continued my journey as an OpenStreetMap contributor by actively participating in humanitarian mapping through the HOT Tasking Manager. During this session, I focused on mapping basic features such as buildings and road segments using satellite imagery.

This experience helped me better understand the importance of accurate data in supporting humanitarian efforts, including disaster response and community planning. I paid close attention to data quality, proper tagging, and alignment with OpenStreetMap mapping guidelines.

Through this contribution, I strengthened my familiarity with the OSM editing tools and improved my confidence as a mapper. I also gained valuable insight into how collaborative mapping enables volunteers from around the world to support vulnerable communities with reliable geospatial data.

I look forward to continuing my contributions, improving my skills, and participating in more humanitarian mapping projects in the future.

Jede*r hier hat (ständig wechselnd) andere Prioritäten und alle halten ihren Schwerpunkt immer für den Wichtigsten ;)

So schlimm ist es natürlich nicht. Ich mache mich mal auf im Landkreis Waldeck-Frankenberg einen Ort nach dem Anderen (nach Gemeinde) abzuarbeiten um die uralten Geometrien aus den Anfangsjahren mal ein wenig abzuarbeiten.

Jovita Fuentes Javellana, age 82, of Acworth, GA, passed away on Thursday, February 7, 2019. She was born on June 24, 1936 in Iloilo, Barotac Nuevo in the Philippines to Angelina Agudo and Nicolas Fuentes. We call her by her name, Betty. Our lola (Grandma) Betty.

Jovita was a dedicated and loving wife, mother and grandmother. She had a talent for sewing, crocheting and gardening. In addition to being a wonderful mother, Jovita was also a great cook.

In the past, we used to visit her on weekends, and I always looked forward to those days when she radiated so much energy and positivity. One memorable moment stands out: I wrote her a heartfelt letter on a yellow pad to express my sincere gratitude for all she had done for us in the family, especially during Christmas. It was a small gesture, but it captured the depth of my appreciation for her presence in my life.

Lola, I miss you more than words can express. I wish more than anything to spend time with you again, alongside Papa, creating new memories together. You are always in my thoughts and forever in my heart.

Your grandson,
Jon

Source: https://www.dignitymemorial.com/obituaries/kennesaw-ga/jovita-javellana-8154176

Bilang paggunita sa aking yumaong lola ngayong buwan ng Pebrero: sa ika-7 anibersaryo ng kanyang pagpanaw; napagpasyahan kong i-pin sa OpenStreetMap ang libingan ng aking lola na si Jovita J. Isa siya sa mga pinakamahalagang tao sa aking buhay, kasunod ng aking mga magulang, at patuloy na nabubuhay ang kanyang alaala sa aking puso.

Si Jovita Fuentes Javellana ay pumanaw noong ika-7 ng Pebrero, 2019 sa Acworth, Geogia sa Estados Unidos sa edad na 82. Ipinanganak siya noong ika-24 ng Hunyo, 1936 sa Iloilo, Barotac Nuevo sa Pilipinas. Mga magulang niya ay sina Angelina Agudo and Nicolas Fuentes.

Si Jovita ay isang mapagmahal na asawa, ina, at lola. Siya ay may natatanging talento sa pananahi, crocheting, at paghahalaman. Bilang isang masigasig na ina, palagi kong hinahanap ang mga masasarap at masustansyang pagkaing hindi malilimutan. Tulad ng Pasta Valenciana, at mga pagkaing tatak Ilonggo.

Si Jovita Javellana ay nag-iwan ng mga minamahal na alaala sa kanyang mga anak na lalaki:

Ronillo Javellana,
Jovel at asawa niyang si Rayda Javellana;

mga anak na babae:

Mary Ann Cox,
Divina Suzette Nalzaro,
Minnie Leonor Priete;

manugang na lalaki:
Larry Nalzaro;

manugang na babae:
Marita Javellana;

mga kapatid na lalaki:
Dr. Rene Fuentes at Gng. Ron Javellana, G. at Gng. Elpedio Javellana, G. at Gng. Pepito Javellana;

mga kapatid sa ama o ina:
Elma, Jean, Maritess;

mga apo:
David Lance Javellana, Marion Kate Javellana, Ron Adam Javellana, Jonathan Javellana, Ryan Nalzaro, Nash Nalzaro, Leif Nalzaro, Reid Nalzaro, Stephany Cox, John Cox, Daisy Cox, Winnie May Priete, Edwin John Priete, JC Priete, JJ Priete; at mga pinsan: Portia at asawa niyang si Rey, G. at Gng. Jaime Javellana, G. Robert Javellana.

OSM Node: osm.org/node/13528653302

im sooo new plssss what can i benefit from this, i needddd this to help me for the future and stuff idk

Depuis que je suis en retraite dans le cantal, je me suis pas mal intéressé aux aspects agricoles. A partir des orthophotos 2025 j’essaie de cartographier l’emprise des cours de fermes dans le département en travaillant aussi sur l’amélioration et le maintien des landuse. il y a environ 4000 cours de fermes dans le Cantal. Un peu plus de 1100 sont tracées. C’est facile pour les bâtiments récents et on observe une belle modernisation des bâtiments d’élevage en 10 ans avec une grosse majorité d’installations photovoltaïques en toiture. petite extraction sur Umap https://umap.openstreetmap.fr/fr/map/fermes-dans-le-cantal_1326159#10/45.146663/2.712250

In classic adventure stories, traveling through remote regions meant you had to rely on maps, luck, and intuition. Patagonia — famously portrayed in "In Search of the Castaways" — was once a place of uncertainty and long, unpredictable routes. Today, exploring Patagonia can look very different with OsmAnd Web Explore. Modern tools make it easy to discover key places, explore what’s nearby, and plan routes across one of the world’s most spectacular regions.

Photo by Rafael Pazini on Unsplash

Let’s Start with a Search​

February is a great time to explore Patagonia — it’s summer in the Southern Hemisphere, with long daylight hours and easier access to remote areas. A quick online search for “Patagonia must-sees” almost always brings up one name: Los Glaciares National Park in Argentina — a UNESCO World Heritage site since 1981.

So why not make it the starting point of our journey?

Open OsmAnd Web and tap the Search icon on the map. You can search not only by place name, but also by exact coordinates — a handy option when you know the location but not the name. For this example, enter the coordinates -50.000000, -73.000000. The map instantly centers on this point and places a pin in the heart of Patagonia, near Lago Argentino and the glaciers that give the park its name.

Selecting the location opens the context panel, where you can review the position, copy the coordinates, and use quick actions to keep planning.

Explore Nearby and Start Navigation​

With the map centered on the Los Glaciares area, tap Explore. OsmAnd instantly highlights interesting places around you, turning the surrounding landscape into a collection of discoverable spots — viewpoints, lakes, glaciers, mountain ranges, and protected areas.

Each place comes with useful information: a name, category, short description, and often photos. To narrow things down, you can use filters to show only what matters to you — for example, Nature & Outdoors. This makes it easy to move from a broad view of the region to a focused list of places worth adding to your journey. By the way, if you prefer exploring on the go, OsmAnd also offers a similar Explore feature in the mobile app (Android only) — see the step-by-step guide here.

Among the many results, one destination stands out almost immediately: Torres del Paine National Park — this time across the border, in Chile. It’s one of Patagonia’s most iconic national parks, and a natural next step for our route.

Selecting Torres del Paine opens the POI context menu, where you can save the park to your Favorites, share a direct link to it, or jump straight into route planning and navigation.

Choose Navigation, and the selected park becomes your destination point. For the starting point, set Los Glaciares National Park. If you want to shape the journey more precisely, you can add intermediate points along the way — useful when you want the route to pass through specific locations, border crossings, or scenic stops.

Next, select the routing profile that fits your plans. OsmAnd recalculates the route instantly, drawing a clear path between these two landmark destinations and showing distance, estimated travel time, and elevation profile.

What once would have required multiple maps and guesswork now becomes a clear, flexible plan — ready to adapt as your adventure unfolds.

One Route, Multiple Ways to Travel​

Patagonia isn’t just about long roads and mountain passes. In Chilean Patagonia, travel often includes water as well — fjords, channels, and scenic ferry routes that cut through dramatic landscapes. One of the most famous examples is the Navimag ferry, which connects Puerto Montt and Puerto Natales, offering a multi-day journey through Chile’s southern fjords.

When a journey includes different types of terrain and transport, planning everything as a single route can be a challenge. This is where OsmAnd Web Plan Route really shines. In the route planner, you can build one continuous track and change the routing profile for individual segments. Drive between towns, switch to a boat profile for ferry crossings, then return to a pedestrian or driving profile for the next part of the journey — all within the same route.

Using the Change profile option, you decide whether a new profile applies only to the next segments or recalculates the entire route. This makes it easy to adapt your plan as the landscape changes, without starting over.

So, while classic adventures have already been written and have earned their place in history, your own Patagonia story is still ahead of you. With OsmAnd Web Explore and Plan Route, you can turn curiosity into a clear plan: find the places that inspire you, see what’s nearby, and build a route that matches the terrain and the way you travel.

We appreciate your interest in us and thank you for taking the time to read this article. Join us on social media to keep up to date with the latest news and share your experiences. Your opinion is important to us.

Follow OsmAnd on Facebook, TikTok, X (Twitter), Reddit, and Instagram!

Join us at our groups of Telegram (OsmAnd News channel), (EN), (IT), (FR), (DE), (UA), (ES), (BR-PT), (PL), (AR), (TR).