OpenStreetMap Blogs Last Update:

1. 你驾车，Android Auto上使用OSM导航软件
2. 副驾不能晕车，放个笔记本在大腿上，在iD上连接两点，用编辑器把缺失的路现画上
3. 你在导航上规划路线，看哪里特别绕
4. 副驾对着卫星图画缺少的路
5. 你开车，副驾补全车道和路线信息

a day ago

19/02/2026-25/02/2026

♦

[1] VORTAC (VHF Omnidirectional Range / Tactical Air Navigation) (beacon:type=VORTAC) | Colling-architektur, via Wikimedia Commons CC BY-SA 3.0

Mapping

• Simgaymer has asked for comments on a tagging proposal to extend the existing building:flats=* tag, allowing mappers to record the number of flats with 0 bedrooms (studio), 1 bedroom, 2 bedrooms, and so on. For example building:flats:0_bedrooms=* to record the number of studio flats.
• The proposal flashing_lights=* is still open for voting. The proposal intends to indicate the precise design of flashing lights.
• Voting on the indication:*=*, a tag prefix to designate any feature with the help of existing tagging (useful for utility markers, like hydrants), refinement proposal has closed successfully at 100% approval rate (20 votes for, 0 votes against, and 0 abstentions).

Mapping campaigns

• [1] Matt Whilden has launched a MapRoulette project focused on improving the mapping of VORTAC (VHF Omnidirectional Range / Tactical Air Navigation) beacons (beacon:type=VORTAC), a type of radio station used in aviation to help pilots determine both their direction from a station and their distance to it. According to Matt many of these installations in OpenStreetMap have been incorrectly mapped as buildings, storage tanks, towers, or other structures, rather than being tagged as aviation navigation aids. The circular shelters and antenna arrays that characterise VORTAC sites are frequently misidentified when viewed from aerial imagery.

Community

• Following a recent outage affecting the Overpass API service used by many OpenStreetMap tools, Daniel Schep and Jacob Hall announced the launch of the MapRVA Overpass server (overpass.maprva.org/api/), a dedicated Overpass instance focused on the state of Virginia in the United States. Alongside the server, they also introduced a customised deployment of Ultra. The customised version is configured to use the MapRVA Overpass server and the MapRVA styling server as its default infrastructure, providing an alternative resource for users working with Virginia-focused data during broader service disruptions.
• Michal Migurski has written about the representation of boundaries in dispute using open data and mapping with OpenStreetMap.
• Derlamaer highlighted the current OSM proposal traffic_signals:detector=pedestrian_presence_sensor, suggesting a tag for indicating pedestrian presence detectors at traffic signals. This tag aims to improve the precision of signal controller datasets and support more detailed traffic engineering analyses.
• FeetAndInches has written a diary entry on how they process dashcam video and GNSS data into a sequence of images for Panoramax.
• Kevin Ratzel has written an Ultra query to visualise the 1.0 Pedestrian Working Group Schema, a tagging schema for pedestrian infrastructure mapping in OpenStreetMap.
• Anne-Karoline Distel has published a video explaining how to map bonfire sites associated with the Eleventh Night.
• Valentin Bachem has identified and explained ♦►♦ several potential safety risks in the current cycling path network of Heidelberg, calling on local authorities and the media to give greater attention to these issues and to pursue improvements aimed at reducing harm.
• SirfHaru wrote in their OSM user diary about some of the peculiarities of mapping addresses in India.

Events

• The call for participants at SotM 2026 is open. This year’s SotM will take place in Paris, France, 28 to 30 August. The Programme Committee is ready and waiting, eager to unwrap your submissions for talks, workshops, and panels. These sessions aren’t just part of the conference; they’re its beating heart, driving conversations and sparking ideas that resonate worldwide. Presenting your work, projects and ideas at SotM is also a great way to get in touch with the wider OSM community.

Maps

• Jochen Topf outlined several recent feature updates to OSM Spyglass, a debugging interface for OpenStreetMap that displays all tagged nodes, ways, and relations.

Open Data

• An update of the Portuguese coastline dataset, at a scale of 1:150,000, is now available ♦►♦, on the dados.gov portal, published by the Hydrographic Institute.
• The 2025 version of the Official Administrative Map of Portugal has been published ♦►♦ on the website of the Directorate-General for Territory. There is also a viewer for online data, which uses OSM as its base map.
• Pinhead map symbols is a repository of public domain SVG icons designed to be displayed at 15×15 pixels (minimum). You can find the project on GitHub.

Software

• ni5arga has made Sightline, an OSINT search engine for physical infrastructure, built on OpenStreetMap data. The tool uses the Overpass API and Nominatim, supports both free-text and structured queries, such as type:data_center operator:google, and relies on deterministic rule-based parsing instead of AI inference.
• nickrsan has built Browsm, a browser extension that allows users to edit OpenStreetMap points of interest directly while viewing a business or attraction’s official website.

Releases

• Organic Maps has released its February 2026 update. Users can now contribute by adding real-time public transport schedule data through sending GTFS feed sources and ensuring that a city’s OSM data includes all the necessary tags, which can be verified using the gtfs-osm-matcher.

Other “geo” things

• FOSSGIS e.V. has launched ♦ a mailing list aimed at the wider community. The list is intended as a place to ask questions about QGIS, discuss software or plugin choices, and exchange practical experiences with other users. Subscribers will also receive updates from the association, including event notices, job postings, and other announcements. Registration is available here ♦, and joining does not require association membership.
• The German tech outlet Golem.de reported ♦ that Google is further restricting the full functionality of Google Maps for users who are not signed in with a Google account. According to the report, the limitation has been confirmed to apply at least in the United States and Germany.
• The Atelier Parisien d’Urbanisme (Parisian Urbanism lab APUR) has published ♦►♦ the first Atlas de la Métropole du Grand Paris. As part of this publication, APUR has chosen to present an analysis of the departure patterns of Parisians and residents of the Île-de-France region to metropolitan seaside areas, based on data from CitiProfile ♦►♦, a French startup specialising in the production of decision-making tools based on the flow of people and vehicles.
• The Zürich-based Mapillary team hosted an event on 26 February to celebrate reaching 3 billion uploaded images. The meetup offered insights into the engineering behind hosting this volume of imagery, the future roadmap, and how mapping communities are using Mapillary.
• You can read the incredible history of Inō Tadataka, who was 55 years old when he set out to methodically survey the entire coastline of Japan in 1800, a task he would spend the last 17 years of his life working on.
• QGIS 4.0 Release candidate has been launched, with some important improvements and, according to the developers, this major release will represent the successful culmination of a long period of technical migration, transitioning the core of QGIS to Qt6. According to the Road Map, the release date for version 4.0 is 6 March 2026.

Upcoming Events Country Where Venue What When ♦ 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 UN Maps Validation Friday Chat & Map ♦ 2026-02-27 ♦ Greater Noida Online Missing water Bodies of Delhi ♦ 2026-02-27 ♦ Essen Fahrrad-Messe Essen, Halle 5, Show-Truck Vortrag: Mitmachen bei OpenStreetMap, der Basis vieler Outdoor-Apps ♦ 2026-02-27 ♦ Potsdam Hafthorn Potsdamer Mappertreffen ♦ 2026-02-27 ♦ Ferrara Cimitero monumentale della Certosa di Ferrara Ferrara mapping party ♦ 2026-02-28 ♦ Messina Messina Mapping Day @ Messina ♦ 2026-02-28 ♦ Dijital Bilgi Derneği Genel Merkezi OpenStreetMap Community Meet-Up & Mapathon ♦ 2026-02-28 ♦ नई दिल्ली Jitsi Meet (online) OSM India – Monthly Online Mapathon ♦ 2026-03-01 ♦ Madurai Naveen Coffee Bar, Anna Nagar (tentative) OSM Mapping Party @ Madurai ♦ 2026-03-01 ♦ Milano Building 4A, Room Fassò – Politecnico di Milano PoliMappers Maptedì ♦ 2026-03-03 ♦ Salzburg Bewohnerservice Elisabeth-Vorstadt OSM-Treffpunkt ♦ 2026-03-03 ♦ Lille Salle Yser, MRES, 5 rue Jules de Vicq, Lille Rencontre OpenStreetMap à Lille ♦ 2026-03-03 Missing Maps London: (Online) Mapathon [eng] ♦ 2026-03-03 iD Community Chat ♦ 2026-03-04 OSM Indoor Meetup ♦ 2026-03-04 ♦ Brno Kvartální OSM pivo ♦ 2026-03-04 Harzer OSM-Stammtisch ♦ 2026-03-04 ♦ Stuttgart Stuttgart Stuttgarter OpenStreetMap-Treffen ♦ 2026-03-04 ♦ Online OpenHistoricalMap in North America ♦ 2026-03-04 OSM US Mappy Hour: OpenHistoricalMap in North America ♦ 2026-03-04 ♦ Flensburg Offener Kanal Flensburg 3. Open Data Day Flensburg ♦ 2026-03-05 ♦ Žilina Fakulta riadenia a informatiky UNIZA Missing Maps mapathon Žilina #21 ♦ 2026-03-05 ♦ Le Schmilblick, Montrouge Réunion des contributeurs de Montrouge et du Sud de Paris ♦ 2026-03-05 ♦ София Rectorate of Sofia University St. Kliment of Ohrid FOSS4G:BG Open GIS Conference 2026 ♦ 2026-03-06 – 2026-03-07 OSMF Engineering Working Group meeting ♦ 2026-03-06 ♦ Gent Wijgaard OpenStreetMap meetup in Gent – Pre-VLA-congres editie ♦ 2026-03-06 ♦ Hogeschool Odissee Hospitaalstraat 23 Sint-Niklaas Vereniging Leraars Aardrijkskunde (VLA) conference 2026 ♦ 2026-03-07 ♦ Perth Espresso Perk U Later Social Mapping Sunday: Moort-ak Waadiny / Wellington Square Perth ♦ 2026-03-07 ♦ Perth Espresso Perk U Later Social Mapping Sunday: Moort-ak Waadiny / Wellington Square Perth ♦ 2026-03-08 ♦ Delhi OSM Delhi Mapping Party No.27 (East Zone) ♦ 2026-03-08 ♦ København Cafe Bevar’s OSMmapperCPH ♦ 2026-03-08 ♦ London Social Sciences Centre – Western University Friends of MSF UWO Mapathon ♦ 2026-03-09 ♦ Brno Geografický ústav, PřF MUNI, Brno Březnový brněnský Missing Maps Mapathon na Geografickém ústavu ♦ 2026-03-09 Missing Maps : Mapathon en ligne – CartONG [fr] ♦ 2026-03-09 ♦ 臺北市 MozSpace Taipei OpenStreetMap x Wikidata Taipei #86 ♦ 2026-03-09 ♦ Hamburg Voraussichtlich: “Variable”, Karolinenstraße 23 Hamburger Mappertreffen ♦ 2026-03-10 ♦ Cork Logitech, Cork, Ireland Logitech Missing Maps – Office Mapathon ♦ 2026-03-11 ♦ Reston George Mason University, HUB VIP 3 The GAIN Mapathon ♦ 2026-03-11 ♦ Zürich Bitwäscherei Zürich 185. OSM-Stammtisch Zürich ♦ 2026-03-11 ♦ München WikiMUC Münchner OSM-Treffen ♦ 2026-03-12 ♦ Leuven Romaanse Poort Camera’s in kaart brengen ♦ 2026-03-14

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, Raquel IVIDES DATA, Strubbl, Andrew Davidson, barefootstache, derFred, izen57, mcliquid.
We welcome link suggestions for the next issue via this form and look forward to your contributions.

a day ago

Manchmal sind es die kleinen Details. Dank 360° Mapillary Bildern konnte ich an der Stelle die Gegend etwas “aufhübschen”. Auch wenn man natürlich nicht für den Renderer mappen soll. Aber ein paar Dinge sind doch nützlicherweise hinzugekommen.

♦

♦

Leider wollte imgur meine animierte webp-Datei nicht annehmen. :shrug:

3 days ago

In this next edition of our OpenStreetMap interview series we speak with DW Innovation about SPOT, their tool for searching geospatial patterns in OpenStreetMap. They share how the project began, the challenges behind building it, and what they have learned since its launch.

1. Who are you and what do you do? What got you into OpenStreetMap?

We are DW Research & Cooperation projects. We research and experiment with new technologies in national and international innovation projects to get a clear picture of how journalism can benefit from those technologies.

In our research domain ‘verification’ we acknowledged that a very time-consuming process is the location verification of digital media. OpenStreetMap is a very interesting source of geolocation data as it contains non-commercial data that is relevant for geolocating digital media.

2. What is SPOT? What prompted you to create it? Why do we need a tool like this?

Imagine that you have to verify the location of a picture on which you can see a fountain and a church and a tower block within 60 metres of each other in the City of London. Google Maps won’t be able to help you searching for multiple entities at once, but in OSM you can actually search for geospatial information patterns.

The tool that we previously used for that is Overpass Turbo, however, it was rather complex to use for a lot of journalists. We decided to make searching in OSM easier and build a tool that can translate natural language prompts to search queries for geospatial patterns. The user won’t need to understand OSM tags and descriptors and can just prompt the system in their natural language, for example: ‘find a fountain and a church and a tower block within 60 metres of each other in the City of London’. The result will look like this:

♦

3. What are the unique challenges involved in creating SPOT?

As we started in a world that was just being introduced to LLMs and training them for specific purposes it was quite complex to find the right open source model that would provide us with robust translation of natural language prompts to OSM search queries. We have developed a fine-grained automated benchmarking system that allows us to compare LLM models and measure the impact of fine-tuning.

Another challenge is the tagging system of OSM. We have developed our own descriptor-tag bundle index to try and make sure that we cover any way of searching for e.g. a public bin. We have also clustered visually similar entities, for example all kinds of train rails, due to our geolocation verification use case.

4. SPOT was launched at the end of 2024 launch announcement - what has the response been and what have you learned since then?

SPOT was received very well. The response from the journalistic and OSINT communities is very positive. We started with a Beta version that was not yet very stable. The early users saw the potential, looked through some bugs and provided us with very valuable feedback that allowed us to improve the application. Some, at first sight, minor issues led to insight that created structural changes in the system. Today, we have a well working, stable version that we can build on.

We are still learning that it is not easy to run well engaged open source projects. Building something, making it available for free and asking for input from like-minded is not necessarily the recipe for success. Also free products need to be marketed, also open source projects need to be well-managed and need Product Managers and Product Owners to thrive. We would be very happy to get more engagement from the OSM community, so if you can share the secret for that with us, we’d be much obliged!

5. Recently OpenStreetMap celebrated 20 years. Where do you think the project will be in another 20 years?

Phew, I was never so good at looking into the future. I guess we’ll see the urge and necessity to work on digital sovereignty in the near future. Implementation of that will take a bit. OSM can serve as a great example of how a society can build and own data and applications. OSM could possibly also use this momentum to make a leap and lead the way as a platform independent from state or big tech.

And of course, we would love OSM to be easily searchable for geospatial information patterns by everyone ;)

A big thank you to the team at DW Innovation for sharing their insights on SPOT and their work at the intersection of journalism, verification, and open geodata. We’re excited to see how SPOT and the wider OSM community continue to grow and collaborate in the years ahead.

Forward!

Ed and the OpenCage team

Please let us know if your community would like to be part of our interview series here on our blog. If you are or know of someone we should interview, please get in touch, we’re always looking to promote people doing interesting things with open geo data.

4 days ago

‘De Wasvrouwen’ is een beeld van Carla Rump in Groet, Noord-Holland. ♦
Link naar de locatie met tags op OSM.
Het beeld is een creatie van Carla Rump.

5 days ago

OK. Last year I wrote a short guide on mapping Indian addresses but I lost it in my tiny pursuit to delete myself. Today I suddenly came across the fact that the guide was actually used by mappers and, hence, as a result I am now writing this post to become a replacement for that old guide. Since this is a new one, I don’t want to just rehash the old stuff and instead this time I am going to take a simple problem and show how I would solve it from scratch.

A1, Tower 2, Sector 11, RK Puram, South West District, Delhi, India

A problem very similar to this one came up in OSM India’s XMPP channel today. So, how does one go about mapping this address?

As it’s usually the case we can ignore the district, state, and country part as they are all very well mapped in India. This leaves us with everything upto RK Puram.

If you are thinking that something as big as RK Puram should surely be already on the map then you are wrong; In my “career” I have actually seen larger areas without any nodes for them. So we will in fact check if it’s already on the map and, guess what, it actually is already mapped as a suburb, so that’s one less step for us! I should mention that in OSM there are three “neighbourhood” levels below the district: quarter, suburb, and neighbourhood in decreasing order of size. In most cases suburb and neighbourhood should be enough for you, but it is important to be aware of quarter for special situations.

Now let’s check for Sector 11. As of writing this, Sector 11 isn’t on the map. So I will put a neighbourhood node at the approximate centre of Sector 11. (Remember that neighbourhood is smaller than suburb.) We are making good progress.

Now let’s take care of Tower 2. It’s actually specifying a particular building, unlike the previous steps which were about specifying the area in which the building lies. In this case it should be “Tower 2” for housename and “Sector 11” for place. It’s important to specify the place because it could be the case that “Sector 45” node is actually closer to the building.

A small interjection: when mapping a building try to choose between housename and housenumber or place and street logically. If your address is “36, Shivaji Marg” then please please use 36 for housenumber and Shivaji Marg for street. If you do it incorrectly then there’s a 90% of divine punishment from OSM gods.

OK. The building is done. Now all you have to do is to add A1 to the unit tag as a separate node inside the building. Note that the A in this case does not refer to a block and so it should not be separated from the 1. Another important point is that even though A1 is referred to as housenumber in common language, in OSM it isn’t actually a housenumber since housenumber/housename are reserved for building. A1 is just a unit number which means that it is a part of the building. (In case you haven’t realized it yet, the given address was for an apartment.)

I forgot to mention but blocks are somewhat of a controversial topic. My method is usually to retain the blocks in housenumber if they are simple (such as the 1 in “1/265”) or move them into “place” if they are more complicated (like the Pocket E in “36, Pocket E”).

OK. Let’s see if you were reading carefully. Tell me how you would map

1/26/65EB, Gali Shanti, Near Phoole Wala Mandir, Chandni Chowk, Old Delhi

Were you able to do it? Here’s my answer:

Old Delhi is probably already mapped, Chandni Chowk would be a neighbourhood, I would ignore Phoole Wala Mandir, I would add Gali Shanti to the name of highway, then finally for the building I would add 1/26/65E as housenumber and Gali Shanti as street. Did you notice that I never actually told you that letters like E are allowed in housenumber? By that I wanted to show that this guide probably does not contain comments for each and every case, but it should work for the majority of cases. If you come across a difficult problem, then your best bet is always OSM Wiki. Just look it up!

This post was first released on my website with 💜 under CC BY-NC-SA 4.0.

7 days ago

A few months ago, I worked on a new project: the OSM Tagging Schema MCP — a Model Context Protocol (MCP) server built for AI assistants and LLM applications that interact with OpenStreetMap tagging data.

It serves as a bridge between AI systems and the official OpenStreetMap tagging schema, allowing agents to validate tags, query values, search presets, and suggest improvements using the structured knowledge from the @openstreetmap/id-tagging-schema library.

The current 3.x release is technically stable — all tools and endpoints work reliably without errors — but it should still be considered experimental. Active development on version 3 has ended; for now, I only maintain it through dependency updates.

The next major step will be version 4, a complete rewrite developed with AI-assisted coding, focusing on a cleaner architecture, long-term maintainability, and deeper MCP integration.

You can try the service live here: mcp.gander.tools/osm-tagging.

I invite you to experiment, test, and share feedback — your ideas and suggestions are always appreciated: gander-tools/osm-tagging-schema-mcp discussions

7 days ago

♦

Whether you’re passionate about maps, data, or shaping the future of  OpenStreetMap (OSM), the community is always looking for your inspiring ideas! Why not sharing them during State of the Map 2026?

The call for participation of SotM 2026, taking place in Paris, France, on August 28 – 30, 2026, is now open! The programme committee is ready and waiting, eager to unwrap your submissions for talks, workshops, and panels. These sessions aren’t just part of the conference; they’re its beating heart, driving conversations and sparking ideas that resonate worldwide. Presenting your work, projects and ideas at SotM is also a great way to get in touch with the wider OSM community.

Tracks

Sessions can be submitted for the following tracks:

• OSM Basics – Information dedicated to newcomers
• Community and Foundation – Bringing people together, working group experiences, strategies & vision
• Mapping – All about making the mapping easier and better
• Cartography – Your ideas on how to create good-looking presentations of the OSM dataset
• Software Development – Software for processing and editing data
• Data Analysis & Data Model – Reflections about the OSM data, its model and analysis of quality and completeness
• User Experiences – Stories of using OSM and its data as a user
• Education – How you use OSM in an educational context

If your submission doesn’t seem to fit into one of these tracks, don’t worry – as long as it is clearly related to OpenStreetMap, you’re perfectly fine if you simply choose the track that feels to fit best.

OSM Science (Academic Track) at SotM 2026

In addition to this general call for participation, there will again be a proper academic track with a separate CfP, which will be announced later. So, if you’re knee-deep in the captivating world of OpenStreetMap, stay tuned for the official call: The working group is eagerly awaiting the most riveting insights and groundbreaking results from your studies. Get your research hats on, gather your data, and prepare to submit the best of your studies.

Timeline and Deadlines

• 27 April 2026 23:59:59 UTC: Deadline talk, workshop and panel submissions
• End of May 2026: End of review phase, speakers will be informed, schedule published
• 28-30 August 2026: State of the Map in Paris, France

For more information on the above track categories, submission requirements and rating criteria, please visit the complete call for participation and the submission guidelines on the SotM website.

Stay tuned for more news about the State of the Map 2026! See you later this year in Paris, France, and online!

The State of the Map Working Group

Do you want to translate this and other blogposts in your language…? Please email communication@osmfoundation.org with subject: Helping with translations in [your language]

The State of the Map conference is the annual, international conference of OpenStreetMap, organised by the OpenStreetMap Foundation. The OpenStreetMap Foundation is a not-for-profit organisation, formed to support the OpenStreetMap Project. It is dedicated to encouraging the growth, development and distribution of free geospatial data for anyone to use and share. The OpenStreetMap Foundation owns and maintains the infrastructure of the OpenStreetMap project, is financially supported by membership fees and donations, and organises the annual, international State of the Map conference. Our volunteer Working Groups and small core staff work to support the OpenStreetMap project. Join the OpenStreetMap Foundation for just £15 a year or for free if you are an active OpenStreetMap contributor.

OpenStreetMap was founded in 2004 and is an international project to create a free map  of the world. To do so, we, thousands of volunteers, collect data about roads, railways, rivers, forests, buildings and a lot more worldwide. Our map data can be downloaded for free by everyone and used for any purpose – including commercial usage. It is possible to produce your own  maps which highlight certain features, to calculate routes etc. OpenStreetMap is increasingly used when one needs maps which can be very quickly, or easily, updated.

7 days ago

I successfully put Novato Baylands Point Blue Conservation Science as a pin on the map. However, I have not had success with editing the directions that maps provides to get you to the site. The directions still route you past the facility, rather than stopping right at the facility. They should tell you to go down Aberdeen Rd, and then the location is on your right. Thanks for any assistance with editing the route.

8 days ago

Code for Harimaの定例会で自分が表明したことで議事録に載せてますが、こちらに転記しておきます。

数ヶ月ほど前にあったCode for Harimaの定例会で、OSMを利用した万博マップに対して自分が「大阪万博には、赤字補てんのための公的資金投入やカジノありきの計画、パビリオン建設工事費未払問題などさまざまな政治的問題があり、それに加担するような活動は良くない」という発言したところ、参加していたOpenStreetMap Foundation Japanの某氏は「万博は政治的じゃない」と発言したことに驚いた出来事がありました。

OSMFJの人がそういう発言をするのであれば、自分は逆に 政治的なOpenStreetMap のプロジェクトをやろうと思いつきました。

自分が個人的にぼちぼちやるので、別になにかあるというわけではありませんが、とりあえず表明ということで書いておきます。ひとまず、次の2つを考えています。

1. 反人種差別のためのマッピング
2. 敵対的建築物(Hostile architecture)を記録するマッピング

1. 反人種差別のためのマッピング

OpenStreetMaps USで、社会的公平性のために人種差別に関する地物をマッピングして、wikidataとリンクさせて可視化するというプロジェクトがあります。

• United States/Racism - OpenStreetMap Wiki

アメリカでは、黒人奴隷や南軍、KKK関連の地物をマッピングしています。日本では、戦前、戦中に韓国や中国から強制労働で多数の人が連れて来られて、炭鉱や建設などに従事させられました。

その労働は過酷で、命を落とす人もいたので慰霊のための慰霊碑が建てられていたりします。たとえばこれとか。

• 神戸電鉄朝鮮人労働者の像 - Wikipedia

こういうものを記録していきます。群馬の森の朝鮮人慰霊碑が歴史修正主義者のクレームにより撤去されるという事態も起こっているので、記録は残さないとと思っています。

• 「群馬の森」朝鮮人追悼碑の撤去…平和を願う関係者の無念を映画化 - RKB毎日放送

2. 敵対的建築物(Hostile architecture)を記録するマッピング

敵対的建築物は直訳ですが、日本語では「意地悪ベンチ」「排除アート」と呼ばれているものです。

排除アートは、行政がホームレスや若者がたむろさせないために、ベンチを座りにくくしたり寝られないように手すりをつけることや、人が溜まりやすいスペースに意味不明なアートっぽい（アートではない）オブジェを置いて、そこに滞留できないようにすることです。

• 〈人を座らせないベンチ〉東京・新宿の“意地悪ベンチ”に批判続出！ 一方、下町では真逆の試み…ベンチだらけの商店街を取材 - 集英社オンライン - ニュースを本気で噛み砕け
• RedditのHostile Architectureサブレ
• 排除アート - Wikipedia

ふと気になってOSMのタグを調べたら、そのものズバリ「Hostile architecture」のタグがproposalに出てたので、この動きを推進するために、これらをマッピングします。

• Hostile architecture - OpenStreetMap Wiki
• Proposal:Hostile Architecture - OpenStreetMap Wiki

redditの写真を見れば排除アートがどんなものかわかりますが、広がっている問題については可視化しないとわからない人がいるので、どんどんつけて可視化したいと思ってます。

ということで、時間ができたときに自分はぼちぼちやっていきます。興味がある人がいれば連絡をください。

8 days ago

12/02/2026-18/02/2026

♦

[1] | DER SPIEGEL has built its own open-source mapping stack based on MapLibre and Protomaps | © MapLibre – Protomaps – map data © OpenStreetMap Contributors.

Mapping

• Comments are requested on the proposal bicycle_parking=absent. This tag aims to document that no bicycle parking is available around a feature, for example a shop or station, making such gaps in infrastructure discoverable in data analyses. Related discussion is also taking place on the forum.

Community

• Clifford Snow introduced the ‘Safe Routes to School’ initiative, which supports families who want their children to walk or cycle to school in a safe way. The project focuses on identifying the most suitable routes and collaborating with local authorities to make those routes safer. The team is currently looking for additional volunteers to improve the data. Those who would like to contribute can join the #safe-routes-to-school channel on the OSM US Slack.
• OpenCage has published an interview with Nicolas Collignon, CEO of Kale AI, a company developing urban delivery routing solutions powered by OpenStreetMap.
• Anne-Karoline Distel showed how to add information about what is or was quarried at a quarry in OpenStreetMap, noting that such data can be valuable for historical research, whether in industrial, social, or even church history.
• Marcelm005 has proposed a project to map the Lincolnshire ER Routes, emergency routes that enable people to quickly evacuate from flood-prone areas.
• rtnf is trying to learn how OSM tile servers work.
• The OpenStreetMap US community is currently deliberating on the most effective method for querying OpenStreetMap objects based on their geometric shapes.

OpenStreetMap Foundation

• The next OSM Foundation Board meeting will take place on Thursday 26 February 2026 at 13:00 UTC.The meeting will be accessible through the video room.The topics to be covered are:
  • Chairperson’s report
  • Secretary’s report
  • Treasurer’s report
  • 2026 board face-to-face meeting update
  • French cadastre changes and release of code updates for ‘OSM components’ on GitHub
  • Creation of an OSMF Coinbase account for BTC donations
  • Potential statement/policy for OSMF’s participation with other parties in proposals for EU-funded projects, and related topics:
    • Draft blog post: OSMF approach to EU-funded project collaborations
    • Potential OSMF participation in Horizon Europe CSA (GeosTeX)
    • European Institute of Technology (EIT) communications
    • 2026 Sovereign Tech Agency call for tenders
  • Request for comments for GERS as an OGC Community Standard
  • Guest comments or questions.
• The Marche Region (Italy) reported ♦►♦ about its recent entry among the supporters of OpenStreetMap as a ‘Silver Member’. This is the first time that an Italian public body has officially recognised the usefulness of OpenStreetMap and decided to actively contribute to its financial support.

Local chapter news

• OpenHistoricalMap has kicked off their first donation drive to help fund technical development and operations.

OSM research

• A Danish survey conducted in January 2026 found ♦ that in Denmark, OpenStreetMap contained approximately 20,878 km more paths, footways, and tracks than the official Danish road network dataset, GeoDanmark Vejmidter. The survey was carried out by the Danish organisation GeoDanmark.
• A new study published in Nature Communications uses OpenStreetMap land use and AOI data to help classify 110 million buildings across 109 Chinese cities, demonstrating how open, community-mapped data supports national-scale urban inequality analysis and evidence-based planning.

Maps

• kafked has presented his side project rename.world on Hacker News. rename.world is a MapLibre-based map where users can click any place and propose new names. Around 40,000 renames have already been submitted; the non-commercial project runs on SvelteKit, with self-hosted vector tiles, and is explicitly not intended for navigation.
• The Welikia project shows the native ecology of New York City (i.e. what it was before settlement), using OSM as base map. The project is maintained by the Urban Conservation team at the New York Botanical Garden.

OSM in action

• [1] At the News-Infographics-Analytics-Maps 2026 conference ♦ in Berlin, data visualisation journalist Ferdinand Holsten presented how the German news magazine DER SPIEGEL has built its own open-source mapping stack based on MapLibre and Protomaps. This allows DER SPIEGEL to host tiles for interactive maps independently of commercial services such as Mapbox. The presentation, which is now available ♦ as a video on media.ccc.de, outlines the workflow from data preparation to tile generation and the integration into an interactive storytelling. Ferdinand Holsten has kindly provided us with an automatic translation of the presentation into English.
• Jake Coppinger (UrbanSpectra) has published a map tracking community and government projects across a river catchment, utilising OpenStreetMap data (Sydney, Australia).
• rbb24, part of public service broadcasting in Germany, naturally uses ♦►♦ OpenStreetMap, with correct attribution, in its reporting of locations.

Open Data

• HeiGIT reported that it has published new open and ready-to-use global risk assessment datasets, with the objective to simplify risk analysis by removing major technical barriers to data preparation. These datasets are designed for easy use with the risk assessment QGIS plugin and enable humanitarian stakeholders to conduct multi-hazard, evidence-based risk assessments to support anticipatory action.
• Xiong et al. have published a dataset, which contains a topologically connected representation of the European high-voltage grid (220 kV to 750 kV) compiled from OpenStreetMap data extracted with overpass turbo.

Software

• sylvester_aswin has introduced their project Map Frame, which allows users to generate minimalist map posters based on OpenStreetMap data. Any location worldwide can be selected and downloaded as a 4K PNG (3600×4800); the first poster is free, additional downloads cost one US dollar.
• Carlos Froh introduced ♦ OnRouteMap, a web tool that helps find petrol stations, supermarkets, snack bars, drinking fountains, and similar places along your uploaded GPX track.
• The solo developer thattechiedude, from Hudson Valley, has presented ROLLIN, a map platform rating locations from 0–100 based on six features such as wheelchair access, accessible toilets, and lifts. The project uses OpenStreetMap data, cross-references Google Places, and adds community verification, and offers a free API tier for developers.
• Terence Eden, the developer of OpenBenches, has recently implemented a login with OpenStreetMap function in OpenBenches.
• Ulf Rompe has developed ‘What Did You Do‘, a simple tool that shows the number of OpenStreetMap edits made by each software application within a certain period of time.

Programming

• Thomas de Wolff has introduced his Go library geo/osm on Reddit, offering fast parsing of OSM PBF files through handwritten protobuf decoding, optimised readVarint and readSint routines, and custom zlib decompression. The library can skip specific object types, generate file statistics, and extract geometries by region filter, making it suitable for building custom renderers.
• In response to recent Overpass API service instability, Matt Whilden has developed microcosm, a GitHub Actions script that retrieves a narrow slice of OSM data and updates it nightly.
• Andy Townsend discussed the difficulties encountered in setting up your own Overpass API server.

Did you know that …

• … you can zoom one-handed in Organic Maps?
• … you can easily submit a brand to the Name Suggestion Index project by using NSI Submit a Brand?
• … there is a Mastodon instance run by and for OpenStreetMap contributors that is funded by the OSMF?

Other “geo” things

• Emmanuel Mathot and Jonas Sølvsteen wrote on the Development Seed blog about the release of the ‘EOPF Sentinel Zarr Explorer’, a framework for spatial analysis based on Sentinel images. The cloud-based geospatial project is funded by the European Space Agency through the Copernicus Space Component programme, and was developed by a consortium led by Development Seed and EOX, with community outreach led by thriveGEO.

Upcoming Events Country Where Venue What When ♦ 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 ♦ Toulouse Artilect – 10, Rue Tripière – Toulouse Rencontre OSM Toulouse ♦ 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 ♦ Mumbai High Point restaurant, Lokhandwala Market, Andheri OSM Mumbai Mapping Party No.7 (Western Line – South) ♦ 2026-02-22 Missing Maps : Mapathon en ligne – CartONG [fr] ♦ 2026-02-23 ♦ Saint-Étienne Zoomacom Rencontre Saint-Étienne et sud Loire ♦ 2026-02-23 ♦ Olomouc Přírodovědecká fakulta Univerzity Palackého Únorový olomoucký mapathon ♦ 2026-02-24 ♦ Online Mappy Hour OSM España ♦ 2026-02-24 ♦ Derby The Brunswick, Railway Terrace, Derby East Midlands pub meet-up ♦ 2026-02-24 ♦ Berlin Online OSM-Verkehrswende #72 ♦ 2026-02-24 ♦ City of Edinburgh Guildford Arms, Edinburgh OSM Edinburgh pub meetup ♦ 2026-02-24 ♦ Praha Fakulta Elektrotechnická ČVUT v Praze Missing Maps Mapathon na ČVUT v Praze ♦ 2026-02-25 ♦ 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 ♦ Essen Fahrrad-Messe Essen, Halle 5, Show-Truck Vortrag: Mitmachen bei OpenStreetMap, der Basis vieler Outdoor-Apps ♦ 2026-02-26 ♦ Milano Building 3A Ground Floor – Politecnico di Milano PoliMappers Maptedì ♦ 2026-02-26 ♦ Zürich Meta Zurich Office Mapillary: Celebrating 3 Billion Images ♦ 2026-02-26 ♦ Online Asamblea General Ordinaria – Asociación OpenStreetMap España ♦ 2026-02-26 ♦ Santa Clara Santa Clara University Friends of MSF Mapathon ♦ 2026-02-26 UN Maps Validation Friday Chat & Map ♦ 2026-02-27 ♦ Essen Fahrrad-Messe Essen, Halle 5, Show-Truck Vortrag: Mitmachen bei OpenStreetMap, der Basis vieler Outdoor-Apps ♦ 2026-02-27 ♦ Potsdam Hafthorn Potsdamer Mappertreffen ♦ 2026-02-27 ♦ 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 ♦ Milano Building 4A, Room Fassò – Politecnico di Milano PoliMappers Maptedì ♦ 2026-03-03 ♦ Salzburg Bewohnerservice Elisabeth-Vorstadt OSM-Treffpunkt ♦ 2026-03-03 ♦ Lille Salle Yser, MRES, 5 rue Jules de Vicq, Lille Rencontre OpenStreetMap à Lille ♦ 2026-03-03 Missing Maps London: (Online) Mapathon [eng] ♦ 2026-03-03 iD Community Chat ♦ 2026-03-04 OSM Indoor Meetup ♦ 2026-03-04 ♦ Brno Kvartální OSM pivo ♦ 2026-03-04 ♦ Stuttgart Stuttgart Stuttgarter OpenStreetMap-Treffen ♦ 2026-03-04 OSM US Mappy Hour: OpenHistoricalMap in North America ♦ 2026-03-04 ♦ Online OpenHistoricalMap in North America ♦ 2026-03-04 ♦ Flensburg Offener Kanal Flensburg 3. Open Data Day Flensburg ♦ 2026-03-05 OSMF Engineering Working Group meeting ♦ 2026-03-06 ♦ Gent Wijgaard OpenStreetMap meetup in Gent – Pre-VLA-congres editie ♦ 2026-03-06 ♦ Hogeschool Odissee Hospitaalstraat 23 Sint-Niklaas Vereniging Leraars Aardrijkskunde (VLA) conference 2026 ♦ 2026-03-07 ♦ Perth Espresso Perk U Later Social Mapping Sunday: Moort-ak Waadiny / Wellington Square Perth ♦ 2026-03-07 ♦ Perth Espresso Perk U Later Social Mapping Sunday: Moort-ak Waadiny / Wellington Square Perth ♦ 2026-03-08 ♦ Delhi OSM Delhi Mapping Party No.27 (East Zone) ♦ 2026-03-08 ♦ København Cafe Bevar’s OSMmapperCPH ♦ 2026-03-08 ♦ London Social Sciences Centre – Western University Friends of MSF UWO Mapathon ♦ 2026-03-09 Missing Maps : Mapathon en ligne – CartONG [fr] ♦ 2026-03-09 ♦ Brno Geografický ústav, PřF MUNI, Brno Březnový brněnský Missing Maps Mapathon na Geografickém ústavu ♦ 2026-03-09 ♦ 臺北市 MozSpace Taipei OpenStreetMap x Wikidata Taipei #86 ♦ 2026-03-09

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, PierZen, Raquel IVIDES DATA, Strubbl, Andrew Davidson, barefootstache, derFred, mcliquid.
We welcome link suggestions for the next issue via this form and look forward to your contributions.

9 days ago

Taking a break for 1 week because of ramadhan and installing gentoo as my main system.

10 days ago

Until recently, I used generative AI (GenAI) for programming almost exclusively through the browser in the form of ChatGPT, Gemini, or via my own Ollama backend. My typical use cases ranged from “I need a function or a script that does …” to “There’s a bug in the following lines, how could I fix it?” A direct integration of GenAI into my development environments was not really on my radar. However, through my recent activities around OpenClaw, I kept running into coding assistants more often and I started wondering whether those assistants could be combined with (my) local large language models (LLM).

The Candidates
VS Code as an editor is nothing new, and neither the Copilot extension. I had simply never tried it before. Claude Code is Anthropic’s CLI-based development environment and so far (for me) it has a strong focus on Git workflows, project understanding, and structured refactoring. On the other hand, OpenAI offers Codex as a CLI variant for AI-assisted coding.

Installation and First Tests
VS Code worked as a regular editor right away. Claude Code and Codex could both be installed on my macOS system with just a few terminal commands. Setting up a local Ollama server in those tools was a bit more challenging. With Claude Code, in the simplest case, three environment variables with the connection parameters were enough. Codex was somewhat trickier. The profile configuration and model naming did not quite match up at first. Due to a current bug in VS Code, I initially couldn’t connect my own Ollama server there. My attempts with a proxy failed. So things escalated a bit: I switched to VS Code Insiders, checked out the Copilot extension locally from GitHub, built it myself, and integrated the extension directly. Looking back, this took by far the most time, especially compared to the other tools. However, classic YouTube examples such as Flappy Birds or Tetris could be tested surprisingly quickly. For me, it was once again a mix of “whoa,” “aha,” and a bit of “oh dear.”

♦
Overall Claude Code works transparently and shows which files are being modified, including a GitHub-like diff view showing additions and deletions. Codex feels functional, but compared directly, the overall look and feel seemed slightly less polished to me than Claude Code. On the positive side, I really liked its suggestions about what meaningful next steps could be implemented. VS Code with the Copilot extension, despite the fiddly installation, delivered the best integration and usability for me, especially in combination with my own Ollama server.

Which Model Performed Best? Context Is King.
I prefer to use Ollama as my backend. Given my hardware setup, I am also able to test larger models locally. My first choice was qwen3-coder-next, a model recommended on the Ollama website. At first, the assistants behaved somewhat strangely with more complex requirements. After several tests, it became clear that my (default) chosen context window was too small. Normally, I work with a context window of around 4,096 or 8,192 tokens. However, when programming with Ollama, I achieved significantly better results with 64,000 or even 128,000 and more tokens of context. This obviously has consequences: higher VRAM usage, more load on the GPU or unified memory, and longer response times. Interestingly, VS Code with the Copilot extension felt more robust in this regard. I had to do less manual parameter tuning.

First Flappy Birds, Then WebGIS
I conducted my tests using German prompts. Why German? In my experience, if it works well in German, it will definitely work in English. After starting the classic way with “Create Flappy Birds as a browser game.”, I moved on to a more realistic use case from geoinformatics: a simple WebGIS. My prompts, unchanged, were:

1. “Please create a webpage with a map centered on Mainz.”
   (German: “Bitte erstelle ein Webseite mit einer Karte, die auf Mainz zentriert ist.”)
2. “Please add additional layers, for example using GeoJSON.”
   (German: “Bitte baue weitere Layer z.B. mit geojson ein”)
3. “Could you move the GeoJSON into a separate file that is then loaded?”
   (“German: Könntest du die Geosjon in eine separate Datei auslagern die dann geladen wird?”)
4. “Using Python, create a server for the GeoJSON files.”
   (German: “Erstelle mir mittels python einen server für die geojson files”)
5. “Do you know what an OGC Feature API is?”
   (German: “Weisst du was eine OGC FeatureAPI ist?”)
6. “Yes, please implement it as an additional API.”
   (German: “Ja, bitte als weitere API umsetzen.”)
7. “Could you also add another baselayer in the form of a WMS?”
   (German: “Könntest du noch ein weiteres Baselayer in form eines WMS hinzufügen?”)

What used to feel like an entire semester of teaching to build a Leaflet map with a server, layers, and OGC interfaces was now possible in a basic version with just a handful of prompts. That is somehow impressive and at the same time thought-provoking.

♦

What Does This Mean for Me?
I am seriously considering trying this kind of setup with students in the next semester. But one central question remains in the back of my mind: how much foundational knowledge is necessary to use such powerful tools in a meaningful, reflective, and sustainable way? If you do not understand HTTP, APIs, projections, or data formats, if you cannot debug, if you cannot read code, then you become heavily dependent on these tools instead of being able to use them in a controlled way.
For me, one thing is clear: “vibe coding” has arrived. And it is not going away. The question is no longer whether I use it. The question is how wisely I integrate it into my teaching.

a day ago

 

♦It's been a bit of a gap since my last ride because I've been busy decorating. In the process of clearing the room I discovered a leaflet of cycle routes around Wooler. That sent a pretty clear signal of where I should head for my next ride. So today I headed for Wooler.

The point of a folding bike was that I could stick it in the boot of the car, or take it on public transport to places that weren't hilly. So I'm getting used to easy flat rides. Wooler isn't like that. Some of the routes suggested in this leaflet are described as "strenuous". But I picked one that was described as "moderate". I expected something a bit more demanding than what I'm used to. What I didn't anticipate were the hailstorms.

I was mostly riding on quiet country lanes. There were more dog-walkers than traffic. Most of them said "hello" or "good afternoon". Which was nice. One said "What a lovely afternoon". She wasn't being ironic. I wonder what weather they've been experiencing recently around Wooler.

In summary: Several nice bridges, including Weetwood (thought to have been built in the 16th century, with alterations in 1775) and Fowberry (pictured). More gradients than I'm used to. Interesting weather. In the end I cut it short and only covered 10 miles of a longer route. Still, it was a good ride.

2 days ago

谁有中国地区电网数据

3 days ago

♦

Como corrigir o nome de uma rua na aplicação CNEFE

Corrigir um nome de rua usando a aplicação CNEFE – Logradouro é um processo simples e direto, integrando os dados oficiais do Instituto Brasileiro de Geografia e Estatística com o mapa colaborativo do OpenStreetMap.

Veja o passo a passo:

1️⃣ Escolha a área no mapa Acesse a aplicação e navegue pelo mapa até a cidade ou bairro desejado. Você pode usar o zoom e arrastar o mapa para localizar a região onde deseja verificar os nomes das ruas.

2️⃣ Use o filtro “Rua” No painel de filtros, selecione a opção Rua. Isso fará com que a aplicação mostre apenas os logradouros classificados como ruas, facilitando a identificação de divergências entre o CNEFE e o OSM.

3️⃣ Escolha o editor A aplicação permite abrir a edição diretamente em um editor do OSM. Você pode escolher, por exemplo:

Editor iD (no navegador) JOSM (editor avançado para desktop)

Selecione o editor com o qual você já trabalha.

4️⃣ Selecione a rua a ser corrigida No mapa, clique sobre a rua que apresenta nome incorreto ou divergente. Compare o nome exibido no OSM com o nome oficial disponível na base do CNEFE.

5️⃣ Faça a correção No editor escolhido:

Selecione o trecho da rua No campo name, apague o nome incorreto Cole o nome oficial correto conforme indicado no CNEFE Verifique se não há abreviações indevidas ou erros de grafia

Exemplo: Se no OSM estiver “R. C. J. Silva” e no CNEFE constar “Rua Coronel João Silva”, atualize para o nome completo correto (seguindo as boas práticas da comunidade).

6️⃣ Envie a atualização Após revisar a edição: Salve as alterações

Escreva um comentário claro no conjunto de alterações (ex: “Correção de nome de rua conforme CNEFE 2022”)

Envie para o OpenStreetMap Pronto. O nome será atualizado no mapa colaborativo.

✅ Boas práticas Sempre confira se a rua selecionada corresponde exatamente ao logradouro do CNEFE.

Evite alterar nomes se houver sinalização local divergente — nesses casos, vale validar em campo. Mantenha o padrão adotado pela comunidade do OpenStreetMap no Brasil.

Assim, cada correção contribui para um mapa mais preciso, padronizado e útil para todos.

Correção de Nomes de Ruas no Openstreetmap. Aplicação CNEFE/CENSO2022.

cnefe.mapaslivre.com.br/logradouro/#map=5/-8.75479/-48.66943

4 days ago

多言語表記のタグ付けを考える(パート2: 編集合戦編)

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

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

この記事は「基礎知識編」の続編です

必ず「基礎知識編」を見てから「編集合戦編」へ進んでください

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

パート2: 編集合戦編

ここからは、OSM編集で実際に起きた「編集合戦」について説明します。

パート１を見ていない方は、パート１: OSMの基礎知識編 を先に見ください

♦

事件は「渋谷スクランブル交差点」で起きました
- ウェイ: 渋谷駅前交差点 (1335178864) “バージョン #6” 2025-07-30

この交差点は英語圏では “Shibuya scramble crossing”として世界的に認知されており、インバウンド観光客の目的地ともなっています
- 渋谷スクランブル交差点

訪日客が”Shibuya scramble crossing”を目的地にした場合、数多ある渋谷周辺の’交差点’の中からどうやって”Shibuya scramble crossing” だと確信することができるでしょうか？
交差点にある「案内標識」の「国際表記名=Sybuya Sta.」がOSMに入力されていれば,日本語を解さない人でも「Sybuya Sta.」と表記された場所が「Shibuya scramble crossing」だと確信することができます

• ここでは、OSMwikiの「一般的な名称以外は、派生名に入れてください」に従い、国際表記部分を int_name=Sybuya Sta. と入力します
  • 「一般的な名称以外は、派生名に入れてください」@osmwiki:名称キー

♦

引き続き「ウェイ: 渋谷駅前交差点 (1335178864) “バージョン #6“」のマッピングを見てみます

「name = 渋谷駅前交差点」となっています

• 実際の表記は「渋谷駅前」なので、現物のとおり name=渋谷駅前 とし、交差点を削除します
  • 「存在しないものには名称をタグ付けしないでください」@osmwiki:多国語の名称
  • 「名前に説明を組み合わせて名称を作らないでください」@wiki/JA:名称#名称で説明しない
• OSMwikiに「現地語名称は言語明示サブキーと重複させてください 」とありますが、
  name=渋谷駅前としたことにより、name:ja と一致しなくなりましたが、下記の理由により、name:jaは変更せずにこのままとしました
  • すでにwikidataタグが付けられており、name:XXがロック状態になっているため
  • name:XXのソースが不明。ひょっとすると現地のどこかに表記があるかもしれないため

♦

int_nameをマッピングしたところ、２～３日後に int_name が消されました。
- 「ウェイ: 渋谷駅前交差点 (1335178864) “バージョン #7“」

• int_name= を消すことは OSMwikiの記述に違反することになります
  • 「他の名前はすべて、派生名に入れてください」@osmwiki:名称#名称キー

また、name:enが name:en=Shibuya Sta.に変更されてしまいました

• name:en=Shibuya Sta. に変更することは、OSMwikiに違反することになります
  • 「現地語名称は言語明示サブキーと重複させてください 」@wiki/JA:多国語の名称#言語明示タグによる複数回の名前付け
  • 「略称は使用しないでください」@wiki/JA:名称#略称
  • 「省略しない」@wiki/JA:名称#略称
  • 「一般的な名称以外は、派生名に入れてください」@osmwiki:名称キー

ちなみに、すでにwikidataタグが付けられており、name:enはロック状態になっていいます。

wikidataタグがあるにもかかわらず’name:en’を改変しても意味はありませんし、OSMデータベースに不要なごみデータを蓄積されるだけです。（データベースの保守は無料ではありません）

無意味な編集合戦はやめましょう。

6 days ago

本系列编辑主要修复了部分住宅楼的过大幅度偏移，以及一些误标记的绿化。问题区域主要在星塘街以东，为方便起见，以东西向道路作阶段性的分割。

记录

2026/2/24已完成修复兆佳巷以北

2026/2/25已完成修复中新大道东以北

2026/2/26已完成修复港田路以北

7 days ago

Before

♦

After

♦

7 days ago

finding myself to osm was something I couldn’t understand at the time. Now with an open eye, in my field of water engineering introduced to geographical information system. I love it here my journey begins now mapping take me overseas. 😊

7 days ago

I’m new to editing OpenStreetMap, so this is my first change! I noticed that most neighbourhood areas in Lethbridge, my local city, don’t have a name shown in OSM. However, they’re all neatly shown on an official 2024 map from the government of Lethbridge, so I used it as a source. I did notice that some areas are already named in other ways, but I couldn’t find the item that holds the name. This induced visual clutter by doubling some names (those of the industrial parks, Copperwood, and seemingly Paradise Canyon), but I still added the names to the neighbourhood areas for consistency anyways. If anyone around knows how to get rid of this without removing the naming consistency, it would be great if this slight issue could be resolved. I haven’t actually tested the map yet, since I just uploaded the edit, but if what I’m describing is actually a problem, please help? Anyway, I intend on updating and adding a lot of things to Lethbridge (like adding addresses and new buildings) in the near-ish future, so it’d be fun to get to know the local OSM community.

8 days ago

• tools.geofabrik.de/

• hdyc.neis-one.org/

• osmose.openstreetmap.fr/

• OSM Lane Visualizer

9 days ago

包含建筑物、森林。之前陆陆续续修复了一些，不过都是游击式地修复，没有系统地记录过。现在有时间捡起这件事了，先在这里留个坑吧。

……不要给房子加layer标签来逃避冲突检查器的检查。

26/2/21

10 days ago

I have a large set of photographs I made while running. They are geotagged, as I took them with my phone camera. The compass direction is completely unreliable, but lat/lon is more trustworthy. I thought it would be an interesting experiment to extract greenery like grass and trees from these photographs. It can be a useful addition for creating routes that are more pleasant to walk, since the eye-level point of view is not available in OSM. As this is based on my personal photographs, it has the additional benefit of recommending routes that I tend to use. The first challenge I encountered is that out of a few thousand photographs, only a handful were taken during the daytime. After deduplicating and dropping all photos that contain no greenery, this becomes a relatively small set of waypoints. I decided not to extrapolate additional points along OSM ways to keep the dataset small and avoid adding misleading info. The greenery detection works well enough with the SegFormer model, although it is somewhat slow locally. My plan is to select waypoints from this dataset before calling OSRM. This way I get routes that are more enjoyable to walk and run, but are generally longer than the default shortest route. You can find my dataset on Kaggle.

10 days ago