My personal enemy that I take so serious, is someone who edits an area on a map as “under construction” and then it SITS for longer than 6 months in that stage. In some cases people have been living in that neighborhood for 3 years…and it’s been marked as “under construction.” Here I am today fixing areas that are fully developed now, fully established- and the average of the construction edits were made 2 years ago. Here’s hoping doordash, my personal use favorite Strava, or even pokemon go run an update for those poor folks.

This is purely a diary rant about residential areas and their roads not being updated. I almost wish there was a way to make “under construction” just be something for an existing thing being updated/fixed, not something being built. We’re mapping what’s there to be mapped. I’d rather new developments or roads have like a “coming soon” tag of some sorts that wouldn’t block in app access.

We can use strava as an example, i’ll set a route and it’ll make me avoid an entire neighborhood because “Deleted User” 3 years ago marked these 7 streets near the lake trail as “under construction.” Took me a sad amount of time, admittedly, to realize what was happening. Another example is Niantic not having in game spawns (pikmin, pokemon, ingress) if an area is marked “under construction” because the game labels the area as dangerous, so why would they give server room to RNG spawn their in game items there? Reality though is Ash can and SHOULD be able to catch his Pikachu there because he’s been living there for 3 years- Niantic just doesn’t think it’s safe.

So, here’s my little rant about the amount if neighborhoods i fixed today that i have personally been to, biked through, walked my dog through, that have been “under construction” the last 28 months.

I finally got back to mapping, after about 6 months of being inactive. I’m really happy!

Green Open Data Day 2025

Ive just roled out some updates for waymarkedtrails, the website for browsing route relations. The most notable improvement is that waymarkedtrails is finally able to understand member roles in route relations.

OSM History Viewer and OSM Route Manager are two ancient tools that help visualising and analysing changesets and route relations.

Latest Update from Henderson.

Traili Map - Bike route planner that prioritizes official bike trails

I want better local information so here I am learning and updating Open Street Maps! (4 MAR 2025)

Introduction

This diary entry describes my current insights how best to map and tag pedestrian and bicycle crossings. The many words may make it seem complicated, but the actual tagging is designed for easy and direct tagging what you see on the road, with as little redundancy and required expertise as possible. As follows:

A simple unmarked, uncontrolled crossings is only an intersection nodes without any tags.

A simple zebra can be tagged with highway=crossing + crossing=zebra (or, equivalent highway=crossing + crossing:markings=zebra)

A simple crossing with other markings can be tagged with highway=crossing + crossing:markings=dots/dashes/lines/surface

If traffic lights control the crossing, add crossing:signals=yes

If there are special kerbs, add kerb=lowered/flush/…

If there is tactile paving, add tactile_paving=yes

If there is a crossing island, ad crossing:island=yes

If the crossing path goes uninterrupted over the road it crosses, so the road is interrupted rather than the crossing path, ad crossing:continous=yes

Scope:

• Footway crossing any higher order way, including cycleway and busway, excluding rail.
• Cycleway crossing any higher order way, including busway, excluding rail.
• Mentioned, but excluded: designated horse crossings.
• Mentioned, but excluded for now: how to map a crossing as a way.
• Mentioned, but excluded for now: detailed mapping of the operation of traffic signals.

Basic principles:

• Consider only nodes where a footway, path or cycleway intersects a higher order way, or would intersect if it is actually drawn as a way of its own.
• The intersection of two ways is already a crossing node, even without any tags. It gives the location and the fact that the ways cross, and type and access/designation tags from the crossing way apply to the crossing node.
• only add the highway=crossing tag and additional tags if there are actually attributes to tag, which do not follow (inherit) from the crossing way itself.
• Only tag positive attributes, not missing attributes, unless: a. the applicable default values in your country differ from world-wide defaults; b. the no indicates something generally unexoected, such as crossing=no on a loactoion that cannot be crossed.
• All existing crossing=* schemas are flawed and form a chaotic mix, leaving data users and other mappers to guess what was meant. I use only the additional tags to describe each additional attribute. A crossing= value may still be computed from the separately tagged attributes, for any of the previously used mixed schemes.
• For incremental mapping (start simple and add details later) crossing=zebra is acceptable as a stub for a zebra crossing. All the other crossing types have unclear meanings, because of historical differences in tagging schemes. Note that in some countries even crossing=zebra has been used systematically for non-zebra crossings!

Explanations of the basic principles

Ad 1. If a path, footway or cycleway is not actually drawn in OSM, you can still put a node on the way representing the place where the actual crossing is. In this case, it’s required to tag it highway=crossing., and prefaraby a tag to indicate how people see that it’s a crossing (crossing:markings=zebra/dots/dashes/lines/surface and/or crossing:signals=yes)

Ad 2. The intersection node of a footway with a higher order way is a pedestrian crossing with access foot=designated. If the footway is tagged with bicycle=yes and/or horse=no, the crossing is also foot=designated + bicycle=yes and/or horse=no. Explicit tagging of the node with the same information is redundant, unnecessary, because the information is already there.

Ad 3. Information which warrants explicit tagging of the crossing node is: markings, signal control, tactile_paving, special kerbs, presence of a (safe) crossing island, access or designation not present on the crossing way (or in absence of the crossing way).

Ad 4. Many crossings are tagged as e.g. highway=crossing + crossing=unmarked/uncontrolled + crossing:markings=no + crossing:signals=no + crossing:island=no + tactile_paving=no. The only information there (apart from being an intersection) is that someone some time did not see those attributes. While taht is useful workflow information for a mapathon, OSM generally stores what you can see, not what you can not see, and it’s up to data users to determine what to do if they want information which is not there. We should be clear in what we tag and how, so data users can apply logical defaults. Only if e.g. a national default is clearly differen from the OSM-wide default, it is sometimes wise to tag no, such as foot=yes on Dutch cycleways., because the recommended worldwide default for cycleways is foot=no. Tagging crossing=no on a location where seemingly a crossing is possible: an example is a point where separately mapped cycleways are linked from both sides to the centre line representing the road. This would suggest a crossing, but that is an artefact of using short link sections to make routing possible.

Ad 5. These special tags I often use:

• crossing:markings=zebra/dots/dashes/lines/surface /* road markings showing where to cross
• crossing:signals=yes /* the traffic over the crossing node is normally controlled by traffic lights
• crossing:island=yes /* the crossing has a traffic island, but the road has not been split around it.
• kerb=yes/lowered/flush/… /* The kerb type, important for the impaired pedestrian
• tactile_paving=yes /* presence of tactile paving to guide the visually impaired pedestrian over the crossing.
• crossing:continous=yes /* The crossing path goes uninterrupted over the crossed way; the crossed way is visually interrupted rather than the crossing path.

Tag what’s there, not what you would expect

Only tag positive values, where the expected default is no. However, for footways a kerb is to be expected, so kerb=yes on a foot crossing is redundant and kerb=no is special, to be tagged if it is seen.

bicycle=yes/designated?

In Nederland, bicycle=yes and bicycle=designated have been used a lot. I regard this as unnecessary for a bicycle crossing, because the crossing cycleway already contains that information. Only if a bicycle crossing has been mapped without a crossing way, an explicit bicycle=designated would be warranted; this is because crossings without the crossing way are usually pedestrian crossings.

Crossing node or crossing way?

I think it is acceptable to map both the node(s) and the way as crossing, but preferably tag the details on either the node OR the way, not on both at the same crossing. The exact geometry of a crossing can be mapped using the crossing way, adding way type and access as needed, possiby split into sections such as cycleway=crossing, footway=traffic_island and kerb nodes at the exact spot. My preference is to tag markings and traffic signals on crossing nodes, and to add a crossing node on every intersection node.

Example. Suppose we have a footway crossing a secondary road that has two separate ways for the directions, a traffic island in between, and separately mapped cycleways on both sides; and zebra markings from side to side; and traffic lights for pedestrians to cross the main road, but not the cycleways. There is tactile paving all along, and kerbs are lowered.

I would draw a highway=footway from side to side, crossing a cycleway, two halves of the secondary road, and again a cycleway. I would 1. tag the footway as highway=footway + footway=crossing. 2. tag the four intersection nodes as highway=crossing with crossing:markings=zebra + tactile paving=yes + kerb=lowered. 3. additionally tag the two footway/tertiary intersection nodes with crossing:signals=yes

Now this is intermediate level of detail mapping. Other mappers might just put crossing=zebra on the intersection nodes: low level of detail. High level of detail would be to add nodes for the exact postion of traffic lights and kerbs, splitting the footway into sections for approach, crossing and traffic_island, and e.g. tagging request buttons, sounds and vibrations.

Horse crossings

I don’t know any designated horse crossings in Nederland, although I am sure there are some. Since it would be a bridleway crossing a higher order road, I think the basics are the same as for cycleways and footways. There might be special markings, then we could simply add a value for crossing:markings. Where horses are allowed on footways, paths and cycleways, not even horse-yes would be needed. If they are -by exception- not allowed, add horse=no to the crossing footway/cycleway/path. I know that in several places high placed request buttons are present for horse riders. This is probably best tagged as a detail on the crossing nodes or on the highway=traffic_signals nodes. I don’t know an existing or proposed tag for this.

Blacksburg Square Dance Odd Fellows Lodge #20, 199 Wilson Avenue, Blacksburg, VA Homestead Farm, 5500 Homestead Rd, Riner, VA 24149

The latest updates from the town of Hernderson Nebraska. I believe i have around 90% of the buildings mapped. Once done, will move on to the sidewalks, parking lots, and other navigation details visible from the sky.

Mapping Journey

Nachdem ich OSM bisher nur passiv genutzt habe und mich inzwischen mehr ins Fediverse & Open-source einarbeite, möchte ich auch hier etwas beitragen. Erstmal geht es los mit kleinen Ergänzungen, Korrekturen und Infos zu Orten in meiner Nachbarschaft.

VG, c20

12 Fishpond Ter., Barnegat, NJ 08005

Started picking out small towns which have no detail, and started to add some details. This is Henderson, Nebraska. Currently trying to get all the buildings outlined.

I made another small analysis about the reviews made with MapComplete and Mangrove. You can read all about it here:

Added missing house names and numbers. Many similar and/or confusing addresses in Old Conna area.

Some of the readers may have experienced the sinking feeling when they just attempted to upload dozen if not 100s of changes and a network glitch resulted in the editor app failing the upload.

The Year 2021 was my most productive year in OpenStreetMap mapping. It was all downhill from there due to a variety of factors, highlighted by an abrupt career change that I never anticipated (COVID-19 pandemic did a lot of damage to everyone), and d…

View, edit, and create GPX files online with advanced route planning capabilities and file processing tools, beautiful maps and detailed data visualizations.

Saint-Maximin-la-Sainte-Baume

I used to enjoy making edits on OSM, but now it is so cluttered with every little detail in some areas that you can’t even zoom in to see anything but symbols. I don’t know how to cancel my username. Sorry folks, but I am outta here!

How to delete?

.

Electronics store

QQ7M+JP9, King Faisal Dt., Riyadh 13215

0561640894

.

OSGEO Hokkaido team and SotM Japan team hosted the FOSS4G Hokkaido and State of the Map Japan 2024 in 15th February in Sapporo, Hokkaido.

Hi

I am a absolute beginner in use the open street map tool.

I want to import publicly available data, postcode, address etc into an open street map. How do I do that?

This is cross-linked from my blog, posted on 11 July 2023

Discover the Milagrow Advantage: Innovation, Efficiency, and Cutting-Edge Technology for Home & Office
In today’s fast-paced world, where time is precious and convenience is key, having the right technology in your home or office can make all the dif…

Some days ago, I searched online for a bus route that was supposed to be newly introduced to go from Kilkenny to New Ross. I didnt find it, but I found another one which pleased me even more which goes from Kilkenny to Fiddown ().

To follow along with this tutorial, please setup and configure a Oracle Cloud instance for mapillary tools. Please refer to this guide for instructions on how to accomplish this.

Install & Configure Oracle Cloud Infrastructure to upload Mapillary images from ARM processors

So I recently started working on adding the features of a local high school into a relations group, but after looking at the docs, I’m not sure I’ve properly understood when or how relations should be used. Could somebody help clarify this?

Well, I’ve just discovered that anybody can edit like it’s wikipedia. So instead of doing homework, I’ve spent several hours fixing little things in my hometown. This is fun.

npm install leaflet react-leaflet @types/leaflet import ‘leaflet/dist/leaflet.css’; import { MapContainer, TileLayer, GeoJSON } from ‘react-leaflet’;

<MapContainer center={[39.8283, -98.5795]} zoom={4} style={{ height: ‘400px’, width: ‘100%’ }} >

<GeoJSON data={stateGeoJSON} style={stateStyle} onEachFeature={onEachFeature} /> </MapContainer>

I used this query in overpass turbo:

[out:xml][timeout:25];
// fetch area “Kildare” to search in
{{geocodeArea:County Kildare}}->.searchArea;
// gather results
(way["highway"="tertiary"]["maxspeed"="80"](area.searchArea);
way["highway"="unclassified"]["maxspeed"="80"](area.searchArea);)->.roads;

// print results
(.roads;>;); out meta;

and loaded it directly into Josm, then replaced 80 with 60, and added maxspeed:type=IE:rural as suggested on the talk-ie list, which I hope will make the difference between “rural” local roads, and those at the edge of urban areas, obvious.

I couldn’t find any exceptions listed by Kildare County Council, so I’m reasonably confident I shouldn’t have scooped up any inappropriately, but do shout if I’m wrong.

stuff

My End Goal: Have all the ferries in the world listed in the best possible way on Openstreetmaps!