OpenStreetMap logo OpenStreetMap

Users' Diaries

Recent diary entries

该标签用于提供通往住宅区或住宅区内的道路。虽然这些道路通常允许直通交通,但它们通常不用作直通路线。住宅道路上的大多数交通将用于进出住宅物业。主要通过交通或非住宅交通的道路应酌情使用不同的高速公路标签(例如,)进行标记(参见高速公路)。通往个别住宅的道路通常会被标记为(并且可能)。highway=residentialunclassifiedtertiaryhighway=serviceservice=driveway

对于城镇中的标记,考虑以下因素可能会很有用:

residential– 通常用于定居点内当地交通的街道或道路。主要用于进入住宅物业,但可能包括进入一些非住宅物业(例如街角商店或便利店)。可能会有较低的速度限制或采取交通平静措施。 unclassified– 互连道路网络中优先级最低的道路。当交通不仅用于住宅通道时使用,即使住宅物业也可以通过这条道路进入。 tertiary– 使用取决于当地的地图惯例,但通常用于交通量低至中等的连接或连接道路。可能仍在住宅区,并且可能有住宅物业毗邻,但通常会连接多条住宅道路、当地活动中心或其他郊区。

Location: 世业镇, 镇江市, 江苏省, 中国

J’espère avoir donné envie à des gens de se lancer dans OSM (via les liens dans des notes anonyme) moi tant pis je supprime mon compte OSM dans une semaine. J’ai découvert OSM grâce à la vidéo dont j’ai mis le lien dans des notes anonyme peut être que des gens s’inscriveront et resteront, moi à peine j’arrive mes contributions disparaissent sans savoir pourquoi. Bye

Posted by zman809xx on 5 August 2025 in English.

Opener

Woah, I didn’t realize how quickly this would be something I’d like. I know my account has been around since 2022, but I seriously started mapping in mid-2025. ~10k Edits pretty quickly, and turns out I enjoy editing the map. Maybe I’m looking for a job around this kind of work… Who knows.

ALPR’s

Automated License Plate Readers… Man these things are poping up everywhere. I stumbled on Deflock.me recently. I don’t agree with their “Why” but, I don’t agree these things are good for society… I get that we don’t have a “right to privacy” in public spaces, but man…. this seems one flew over the coo koo’s nest. Is pervasive surveillance at this scale really that surprising? My county alone has 95 ALPR’s (mostly by flock) running 24/7/365 rain snow or shine…. That’s 1 camera per 22 sq.mi. or 1 camera per 7700 people.

Its not right…

95 Cameras over 2130 square miles, and estimated 730,000 people.
Posted by Monchinho on 3 August 2025 in Galician (Galego).

Cústame escribir isto pero teño a necesidade de facelo. Vou parar un tempo (non sei se definitivo) porque estou sufrindo unha certa obsesión con OSM, absorbéndome moitísimo tempo e esforzo e creo que comezo a ter algúns problemas psicolóxicos ou de conduta. Ata soño polas noites co mapa. Tamén me decatei que cando alguén cambia as miñas edicións dun xeito errado sufro unha leve ansiedade e ata aquí cheguei. Non quero enfermar.

Un saúdo á comunidade galega e berciana e moita forza.

Location: Las Águilas, Latina, Madrid, Comunidade de Madrid, España
Posted by yrichard on 3 August 2025 in English.

I like technology and adapting it for the sake of technology . I am not addicted to yet we can not escape it. I only carry my phone when necessary , a computer works so much better , a mix of the old and the new ,technology moves very quickly . I’d prefer a GPS to a 5G modem ,API are not as readily available now

Location: New Norfolk, Derwent Valley, Tasmania, 7140, Australia

延吉 222401

图们 222402

敦化 222403

珲春 222404

  • 市域无县道

龙井 222405

和龙 222406

汪清 222424

安图 222426

Posted by IsStatenIsland on 2 August 2025 in English. Last updated on 3 August 2025.

https://archive.org/details/AMTK-NEC-employee-timetable-20250505-si

This is the most up to date Northeast Corridor Employee Timetable (ETT) I’ve requested, published May 5, 2025. It contains Amtrak’s maximum authorized speeds on the Northeast Corridor. The Acela 2’s planned speeds (mostly focusing on changing 150 to 160 mph) have not yet been integrated into the rules by Amtrak, despite the observed or assumed compatibility with 160 mph service by track class, catenary structure or demonstration in recent test runs. The current runs remain just that: test runs.

There are currently 4 sections of 150 mph (for Type A trains and on the “main” or “inner” two tracks) on the Northeast Corridor:

  • New Jersey: Midway & CP Clark

  • Rhode Island #1: MP 154.3 & MP 171.7, except Cv MP 159.7 & MP 160.5 and Cv MP 170.5 & MP 170.9

  • Rhode Island #2: MP 174.5 & MP 180.5, except Cv MP 180.1 & MP 180.2 and Cv MP 180.2 & MP 180.5

  • Massachusetts: MP 194.5 & MP 205

New Jersey, County & Midway is really close at 145 mph (except 3 curves) and I’m not sure what’s going to happen with that.

One of two things needs to happen before OSM can be updated with the new speeds:

  • A new ETT is issued with blanket authorization of new speeds (perhaps without even authorizing any actual train type)

  • A revenue run is observed at the new speeds

I’ve set up this tag regime to give editors a signal that the maximum speed data is extremely recent and not just based on casual observation:

  • planned:maxspeed=”160 mph”

  • source:maxspeed=”Amtrak ETT 2025-05-05”

I’ve additionally set planned:maxspeed=”160 mph” on the “between CP Clark & Ham” section as that is actually planned and possibly under construction.

There may be changes in speeds on certain curves which is why I would prefer to wait for a new ETT anyway so all changes can be done at once.

See full entry

Posted by notmyproblem1 on 2 August 2025 in English.

Welcome to my diary, “Where did I macro-mapped” This will be available in English and not Italian cuz: 1. I need to speak better english 2. I will (not now but not far away) wanna macro-mapping in the USA (i heard that they have absolute good imagery!) 3. Wanna move from Italy and go to Wisconsin, USA. — Where did I micro-mapped? I micro-mapped Tre Ponti Est (service plaza/rest area/or whatever you call it) look it in 3d, look it in 2d changeset I also micro-mapped the nearby service plaza/rest area, Tre Ponti OVEST, look it in 3d, look it in 2d, changeset 1, changeset 2 — (If you are looking from when I published. UTC+2 02/08/2025 23:30 or Wisconsin Time 02/08/2025 16:30, The Tre Ponti Ovest is not available cuz of cooldown aka [waiting server](https://en.wiktionary.org/wiki/waiting#:~:text=waiting%20(countable,%2C%20service.)

Location: Faibano di Marigliano, Marigliano, Naples, Campania, 80034, Italy
Posted by rphyrin on 2 August 2025 in English.

“You’ve been involved with OpenStreetMap for at least 15 years,” the interviewers begin, marking the start of the session.

I gasp a little. Wow—15 years? Imagine all the… fights and drama?

So I get a little curious and start tracing this person’s digital footprints across the whole OSM universe. See if I can learn a thing or two.


“Upgraded road 11390 to secondary to make it stand out from all the other roads.. Because it has bus routes and stands out for transit traffic.”

“This reasoning sounds quite arbitrary to me. Also what degree of transit traffic is necessary so that the road has to ‘stand out’? General convention followed elsewhere outside of cities – and as currently documented – is to use this tag of this type and that tag for that type. The way this road stands out is now inconsistent to how other roads of these types stands out. I think it should be restored.”

“Hmm. That is a fun rule that’s easy to implement and validate. But what are you expecting to achieve with it, other than theoretical correctness – which in cartography is useless, as you might have experienced? I made it secondary, because of its heightened importance to transit traffic. So that routing engines prefer it when routing to there and not fall back on local roads. And even visual inspection would send people on it. So what would be the intention on changing it back?”

“The main benefit of mapping it to certain official classification is that this way we have a clear criteria. This official classification after all also generally indicates which roads are actually more important. If we tied tagging values to official traffic density data then probably it’d be considerably more difficult and likely the result wouldn’t be as intuitive for end users. I find that this way it’s rather difficult to decide on which highway value each road should get.”

The conversation abruptly stopped right there.

See full entry

Disclaimer: This is just the start of a diary article, details about mapping objectives, progress and obstacles/questions will follow

Description of the area

The Ndomba Sector (Collectivé de Ndomba) is the easternmost sector of the Kabeya-Kamuanga Territory. While the eastern and southern borders of the sector are as well the borders of the territory (which have already been mapped for years), the western border of the sector is the River Lubi.

Roads and paths

This sector is still very remote, despite of the fact that the big City of Mbuji-Mayi and the highway Route National 1 (RN1) are close by in the south-east and south. The main reason for the remoteness is that a number of meandering rivers hinder or limit the asccess from almost all directions. The main access road from the south and from Mbuji-Mayi has been the one which leaves RN1 at 6° 06 28.3 N / 23° 26 03`` E just west of the village of Tschibombo - only 20 kilometers west of Mbuji-Mayi. This road follows the border of the watersheds of the river Mulenda (east) and of the rivers Lubi and Kagangayi (west). This way the crossing of rivers and streams is avoided for most of the distance.

Location: Ndomba, Kabeya-Kamuanga, Kasaï-Oriental, Democratic Republic of the Congo

GSoC 2025 Midterm Update: Temporary Road Closures Database and API

Project Overview

I’m excited to share the midterm progress on my Google Summer of Code 2025 project: Temporary Road Closures Database and API for OpenStreetMap. This project aims to create a centralized platform where users can submit and retrieve real-time information about temporary road closures, enabling OSM-based navigation apps to provide better routing around construction, accidents, and other events.

  • Mentor: Simon Poole and Ian Wagner
  • Organization: OpenStreetMap
  • Project Duration: 12 weeks (175 hours)

🎉 Midterm Evaluation Status: PASSED

I’m thrilled to announce that I’ve successfully passed the midterm evaluation! The project is progressing well and is currently on schedule with several components ahead of the original timeline.

Progress Summary

Completed Components (Weeks 1-8)

1. Geospatial Database & Core Infrastructure

  • PostgreSQL + PostGIS setup with Docker containerization
  • SQLAlchemy models for Users and Closures with spatial geometry support
  • Database initialization scripts and sample data loading
  • PostGIS spatial indexing for efficient geospatial queries

2. RESTful API Service (FastAPI)

  • Complete CRUD operations for road closures
  • Spatial query endpoints supporting bounding box and coordinate-based filtering
  • Authentication & Authorization with JWT tokens and OAuth2
  • Input validation and error handling
  • Swagger UI documentation with integrated authentication

3. OpenLR Integration

  • OpenLR encoding/decoding service integrated into the API
  • Location referencing endpoints for map-agnostic road segment encoding
  • Validation endpoints for OpenLR data integrity
  • Closure service enhancement with automatic OpenLR generation

4. DevOps & Infrastructure

  • Docker containerization for easy deployment
  • Environment configuration management
  • AGPL-3.0 licensing for open-source compliance
  • Comprehensive documentation and setup instructions

See full entry

京杭运河镇江段是重要的航运水道,桥梁多为大型公路桥或铁路桥,跨越宽阔的水面。主要桥梁自西向东(大致方向)包括:

高资河桥/高资桥: 位于丹徒区高资街道附近。

润扬大桥(公路桥): 虽然不是直接横跨运河主航道,但其南汊桥(悬索桥)跨越长江,其引桥和接线工程会跨越或邻近运河相关水道(如运粮河等),是区域重要通道。

镇江西高速桥: 沪蓉高速(G42)跨越运河的桥梁。

镇江西互通连接线桥: 连接镇江市区与高速公路的桥梁。

戴家门桥/润兴路大桥: 位于润州区,是市区西部跨越运河的重要通道(S243省道)。

檀山路桥: 连接镇江主城区与丹徒新区的主干道檀山路跨越运河的桥梁。

九华山路桥: 九华山路跨越运河的桥梁。

官塘桥: 位于官塘桥路,是市区南部跨越运河的重要通道。

沪宁城际铁路桥/京沪高铁桥: 高速铁路专用桥梁。

沪宁铁路桥: 京沪铁路(老线)跨越运河的桥梁。

丁卯桥路桥: 丁卯桥路(金港大道市区段)跨越运河的桥梁,是连接镇江主城区与丁卯、大港的重要通道。

谏壁公路桥/越河街桥: 位于谏壁镇,连接越河街,靠近谏壁船闸。

谏壁闸桥: 位于著名的谏壁船闸枢纽处,通常指船闸交通桥或附近跨越节制闸的桥梁,是连接运河两岸的关键节点。非常重要。

雩山桥: 位于丹阳市访仙镇附近(雩山脚下)。

陵口大桥: 位于丹阳市陵口镇,是跨越运河的公路桥。

二、 镇江市区古运河上的主要桥梁 古运河从平政桥(京口闸)进入市区,向东南流经市区,在谏壁汇入大运河主航道。这段河道较窄,桥梁密集且更具历史人文气息。主要桥梁自北向南(入江口到东南方向)包括:

平政桥: 位于古运河入江口(京口闸遗址附近),历史悠久,是古运河的起点标志之一。

新西门桥: 连接新西门内外。

中山桥: 市中心重要桥梁,连接大西路和中山路。

解放桥: 位于解放路上,靠近伯先公园。

虎踞桥: 历史悠久的古桥(现为复建),位于南门大街北端。

南水桥: 位于正东路西端。

珍珠桥: 跨越珍珠路。

塔山桥: 位于塔山路。

丁卯桥: 古桥名,现为区域地名(丁卯片区),该处古运河上有现代桥梁(如丁卯桥路桥跨越的是主运河,非此段古运河)。

谷阳桥: 位于谷阳路上。

丹徒闸桥: 位于古运河汇入谏壁大运河主航道之前的节制闸(丹徒闸)上。

需要注意的关键点 区分主运河与古运河: 京杭大运河镇江段(主航道)宽阔,是国家级航道,桥梁高大、跨度大、数量相对少些(主要是干线公路、铁路桥)。市区古运河是历史河道,穿城而过,河道窄,桥梁密集,多为城市道路桥,更具生活气息和历史感。

数量众多: 以上列出的是主要的、知名的桥梁。实际数量更多,尤其在城市支路和古运河段还会有不少小桥。

名称变化与具体位置: 部分桥梁可能有俗称或历史名称,具体位置描述可能随城市发展略有变化。高速公路桥、铁路桥通常没有特别的名字,常以线路名称指代。

谏壁枢纽: 谏壁船闸和谏壁闸桥是京杭大运河上的关键节点,非常重要。

动态变化: 随着城市建设和交通发展,新的桥梁可能会建设,旧的桥梁可能会改造或更名。

Location: 四牌楼街道, 京口区, 镇江市, 江苏省, 212000, 中国

Co-Creation Workshop for Road Network Mapping in Karnali, Nepal

Date: 28 March 2024
Title: Planning & Co-Creation Workshop on Mapping Road Network of Karnali
Venue: Care Nepal, Sanepa
Organizer: Open Mapping Hub Asia Pacific
Led By: Rabi Shrestha, Sr. Field Mapping Expert & Prajwal Sharma, Jr. Field Mapping Expert

Project released for remote mapping

The rugged terrain of Nepal’s Karnali Province tells a story of resilience, isolation, and untapped potential. As the only province where road access remains severely limited—particularly in districts like Jumla—the need for a comprehensive and accurate road network is more urgent than ever. With this in mind, a collaborative Planning and Co-Creation Workshop was conducted to collectively address the challenges, gaps, and opportunities for mapping the road network of Karnali through open-source tools and community engagement.

Setting the Stage: Opening Remarks and Partner Introductions

See full entry

Location: Dhobighat, Lalitpur-04, Lalitpur, Lalitpur Metropolitan City, Lalitpur, Bagamati Province, 40000, Nepal