Hi,

Is there a reason you're moving place nodes to arbitrary locations like this?

OSM guidance is that nodes should be sited "in the perceived centre of the place, for example the town or village square to the central in terms of facilities and/or transport routes or next any appropriate central monument". (See osm.wiki/Places .)

This is particularly important for routing - e.g. if someone asks for a route from Canning Town to Ipswich, they will expect to start in the centre of the area, not on a road adjacent to a primary school.

It was correct before - the railway=station tag tells you it's a railway station, you don't need to repeat that in the name= tag.

Please do not add route=road relations in the UK except for E roads. I'm sure you're well-intentioned but they serve no purpose (as a road can only have one ref) and make the map significantly harder to edit for newbies.

Please revert these edits. If you would like to add more then please take the discussion to the talk-gb mailing list.

Hi Clifford - highway=unclassified is the standard OSM tag for a minor rural road of reasonable quality (assumed paved in a developed country), as well as those with more of a connecting role in urban areas. The introductory paras at highway=* explain it well.

The TIGER import assigned all geometries of class A41 to highway=residential. In many urban areas this was a good fit, but in rural ones it was (and continues to be) contrary to standard OSM practice.

Much of what the import tagged as highway=residential is more accurately highway=unclassified, highway=track, or in many cases entirely fictitious - there is no road at all. This means that it's difficult to use unreviewed highway=residential in rural areas with any degree of confidence: routing over it may equally send you up a beautiful paved road or into an impassable quagmire. See https://twitter.com/marcpfister/status/601782213688987649 for a typical result!

Assigning roads to the correct category that would have been used had they been mapped from scratch, rather than the arbitrary highway=residential mapped to the A41 class, therefore aligns with OSM in the rest of the world, results in more nuanced cartography, and lets data consumers make better decisions about which roads to choose.

doogal.co.uk is a direct interface to Google's geocoder data. See (for example) http://www.doogal.co.uk/ShowMap.php?postcode=OX7%203PH, open up the web inspector in your browser, and look at all the requests to maps.googleapis.com. This data can't be used in OSM.

Welcome back! :)

+1 - please don't do this. It breaks standard tagging practice in the UK, and makes the path more confusing for newcomers in most editors (as it'll be shown as a "Path" preset rather than the more descriptive "Cycleway").

highway=path is significantly *less* useful than highway=cycleway, as you can assume a good-quality surface with 90%+ certainty from the latter, whereas you can't with the former.

If you must retag in this fashion, then you need to add a surface tag. But given that the three-tag combination adds precisely no information over the single tag (I run a cycle map and router so have pretty extensive experience in this...!) I really don't know why you would want to.

Could you tell me *how* this improves the street network for routing, please?

We need more people mapping old Welsh chapels! Lovely buildings. :)

Hello Gerd,

Difficult one to call - if it's still a consecrated chapel/church then I certainly wouldn't call it "disused". But regular services may not be currently taking place. It needs an up-to-date local survey really.

Richard

TIGER review from aerial imagery. Essentially reviewing tagging on good-quality paved roads which go somewhere (i.e. through routes rather than just residential access), generally by bringing them into the standard highway=tertiary tag; plus occasional fixup of smaller roads that deserve to be residential or unclassified, but with tagging to indicate that the road has been reviewed (using tiger:reviewed itself for residential roads, or highway=unclassified which wasn't used in the original import and so implies a review).

way/14955798/history is pretty typical - a good-quality paved road which connects to tertiaries at either end and forms a through route. Although looking at it now I see the highway=tertiary tagging peters out at the southern end... must fix that. :)

I've changed the Milford Haven-Herbrandston-Marloes road back from secondary to tertiary, as in the UK we reserve highway=secondary for B roads (ref=B*).

That's great - thank you!

Hi,

Great to see the mapping of the Norwich cycle network.

"Orange Pedalway" etc. aren't really refs. Refs are short numeric/alphabetic references used on signs. "Orange Pedalway" is a name.

Many routers/renderers use 'shields' to show refs, and a ref with 15 characters is too big for any known shield - so the effect is probably that it'll not show up on most maps. (OpenCycleMap is a rare exception!)

As far as I can tell, the signage actually just shows the colours - e.g. http://www.norwich.gov.uk/TransportAndStreets/Transport/Cycling/PublishingImages/WayfinderSticker.png .

I'd suggest that it therefore would be better to revert to the simple "ref=Orange" which is a more accurate reflection of what's on the sign, and won't break so many clients.

cheers
Richard

Or if you do want to continue armchair mapping, may I gently suggest the rural US - where there's hordes of bad imported TIGER data that needs clearing up.

If you had tagged it highway=footway, even without the bicycle=yes tag, then routers and renderers would be able to parse it. Bike routers would say (for example) "On foot".

Tagging highway=something_you_just_made_up breaks connectivity for everyone - for pedestrians, for cyclists equally. Don't do that.

"Rubble and large broken slabs of reinforced concreate" is not a osm.wiki/Tag:name=, it's at best a description= tag. But even that's pretty pointless and you'd be better off using a surface tag.

You have completely broken routing for CycleStreets, cycle.travel, and other routers by inventing this bogus tag with no consultation: way/354359964

There is already a perfectly good way of tagging this - highway=footway, bicycle=yes.

what is this I don't even

Seriously, what does "made a Cycleway_guide highway type for a suspended stretch of footway prioity" even mean, and is there any likelihood that (whatever it is) any consumer of OSM data will ever, ever, ever use it?

It's very difficult to draw such long lines in P2 without crashing the browser. Looks more like a mistaken import from an external file to me.