@jidanni Here’s a nickel go and buy yourself a real editor.

;-)

I’m not sure you could design a more English tag if you tried.

It’s use is probably the result of a lack of other tags for an open area set aside for recreation. The common tag could stretch to cover these as the land is sorta held in common, but the tag doesn’t get rendered any more so no one is going to use it. As a side effect large swaths of land in Australia now get tagged as a park but you wouldn’t be able to tell by looking that it was anything other than bush.

Ouch.

There are at least two schools of thought on splitting a roundabout for routes.

I’m in the don’t split camp because I see the junction=roundabout as a single entity. Others want to split them because they think that it is more accurate.

As there is no consensus on which one to use I tend not to attempt to “fix” roundabouts as I don’t see it as a worthwhile use of my time.

The GPS receiver would also have to have been switched off for 20 years as the receivers store the last values it used so that they know when the counter has looped around.

Last time this happened it was pretty much a damp squib. Bugs do occasionally turn up GPS firmware but they are fairly rare.

Internally GPS works on the GPS time scale, which is the number of seconds since the epoch. All of the navigation calculations are done using the GPS time scale. The GPS time scale repeats every 19.6 years because the week number occupies only 10 bits, which means that the GPS receiver can only convert GPS time to UTC with a 19.6 year ambiguity.

This is why it is most likely that during the rollover a GPS will continue to give you correct navigation information as it doesn’t care what the current time is in UTC. It is also why the advisory from Homeland Security is addressed to “owners and operators and other users who obtain Coordinated Universal Time (UTC) from Global Positioning System (GPS) devices” and other, navigation concerned, organisations such as the FAA have not released any advisories.

To work out which particular UTC time and date it is now requires an external source of data. To do this your smart phone can just ask the network if it is currently 1980, 1998, or 2019 (or remember what the date was the last time it asked or what date it was when it was built).

Meh, the GPS rollover doesn’t affect the ability to provide accurate location data or time of day information. The real problem is that the day/month/year could be wildly wrong. However, as smart phones set their time from data received over the network this really isn’t going to be a problem.

We can’t really blame the Americans for “train station” as the correct term in US English would be railroad station. However, un/fortunately it is just one of those things where the language is changing.

I don’t know who set up the MapRoulette challenge but this has been discussed on the talk-au mail list:

https://lists.openstreetmap.org/pipermail/talk-au/2017-September/011451.html https://lists.openstreetmap.org/pipermail/talk-au/2017-September/011465.html

For reference 1 lakh = 100,000.

(Sorry I have to Google “lakh” every time I see it to work that out)

Turns out that it’s not that simple. I’ve tried this on a Windows 7 machine and it doesn’t work even if you have the dead keys activated. It will work if re-assign the shortcut to something else.

The instructions are not very clear. The imagery layer switch is mapped to the dead tilde key. This means if you are using an English keyboard layout then you don’t have this key. You need to change your keyboard layout to one that has the dead keys enabled ie:https://en.wikipedia.org/wiki/QWERTY#US-International.

Rather annoyingly you can’t use the keyboard shortcut set up to map things to the (live) tilde key (probably because they’re not available on a German keyboard layout?).

There is another version of this that covers 2006-Jan 2018 here.

This was extensively discussed on the tagging mail list:

https://www.mail-archive.com/[email protected]/msg35194.html

and the view was strongly against duplicating tags on the member ways of relations.

Sure @Sam Wilson, why not get into a never ending edit war with a WikiData fan boy? Sounds like a great use of my time ;-)

I’m with @SomeoneElse on this. Just because a user has decided to link a OpenStreetMap wiki page to a Wikipedia page, via WikiData, does not mean that they are the same thing. There are plenty of cases where the Wikipedia definition deviates from the OpenStreetMap concept.

source_ref and source:ref mean two different things.

source_ref is the reference for the source of data or as taginfo puts it “used to link external source of information:”. If you look at the tag values over 90% of them are from two imports and point to the url describing the source.

source:ref on the other hand tells you where the value of the ref tag came from. So:

name=Something source:name=survey source:name:date=2014-05 ref=256 source:ref=Some dataset source:geometry=bing highway=trunk source:highway=Some other dataset . .

I use The Mail Archive to search the OSM mail lists:

https://www.mail-archive.com/[email protected]/msg00000.html

In fact, something as obscure as centre_turn_lane you can search all their mail lists:

https://www.mail-archive.com/search?l=all&q=centre_turn_lane

Just ran the JOSM validator on the level 6 boundaries and this way is in two counties. Will need some local knowledge to fix.

I had thought that once a “roundabout” was big enough to have a name (or has places you might want to find a route to) it stopped being a junction. So you could say:

1. Continue Petersburger
2. Right into Bernsarinplatz
3. Right into Petersburger

You may also want find a route to somewhere on Bernsarinplatz.

1. Continue Petersburger
2. Right into Bernsarinplatz
3. Your destination is on the right.