The list absolutely is used by P2.

There are two things that might be relevant:

• P2 uses the .json file from http://osmlab.github.io/editor-imagery-index/imagery.json . It may be the case that this hasn’t been updated to take in new additions, I don’t know. You would need to raise an issue with editor-imagery-index if that’s the case.
• P2 does not and will not support WMS (or any other format devised in the 16th century ;) ).

What issue is that?

The reason for defaulting to the multipolygon relation is that standard practice is now that, in the case of a multipolygon, tags should be on the relation. So if you’re tagging a building with a hole, the relation should be tagged building=yes (as well as type=multipolygon), and the constituent ways should be untagged. No other type of relation is automatically selected. See osm.wiki/Relation:multipolygon, https://github.com/osmlab/fixing-polygons-in-osm/issues/15 etc.

Shift-drag needs finessing to stop accidental zooms, rather than disabling entirely, and I’ll do that when I have a spare minute. There’ll be an option to customise the maximum data level in a future version.

@metatech Now fixed in the code, will be fixed on osm.org next time it’s deployed.

+1 to Vincent; very common in the UK too.

Heh - someone can write a JOSM plugin to do that but it’ll have to be someone who uses JOSM, understands the JOSM codebase and has more than a passing knowledge of Java, none of which is me!

Thanks. Probably the tag selector getting in the way even though it’s closed - I’ve had that problem before. I’ll take a look.

@metatech: hm. That’ll be related to dialogue boxes appearing on the screen - one of the changes in 2.5 is that the normal keypresses are blocked when (for example) the save dialogue is on the screen. It should restore them when the dialogue is closed, but it sounds like it isn’t doing so. If you could come up with steps to reproduce this consistently that’d be a huge help.

@ghost_07: good idea! @sulagaloh: hopefully a keyboard shortcut to select the way would fix your issue; I’ll look into that.

I would expect this most central spot to be often in front of the townhall (maybe sometimes the cathedral) or the main market square (in traditional towns) or likely both.

In Britain, it’s often a central junction where the historic through-roads meet. So in Oxford it’s Carfax, in Gloucester it’s The Cross, here in little Charlbury it’s Bull Corner, and so on.

Side effect of another change. It’ll be back in the next version.

Rory: amen to that. As a data consumer, I recognise that more harm can be done to the utility of the map by one self-regarding “super mapper” than by a thousand newbies adding ponds.

Same school of thought as the dozens of narrowboats called “Meander”…

Excellent. I had noticed a bunch of newly marked railway crossings while fixing up TIGER classifications!

The latter is https://github.com/openstreetmap/openstreetmap-website/issues :)

*copywriters

Groups on osm.org! :)

A halfway functional pull request exists (https://github.com/openstreetmap/openstreetmap-website/pull/297) but it was never finished and needs restarting from scratch, really. But the intention was absolutely to cater for situations like this.

There is some irony in pinning permanent notes on trees to complain about other notes on trees which are removed, while the permanent notes stay there forever…

IRC: go to http://irc.openstreetmap.org/; type a nickname (e.g. ‘alexkemp’) in the first box; select #osm (general channel), #osm-dev (development), #osm-gb (Great Britain) in the dropdown; click ‘Login’; type away and ask your question!

cycle.travel’s routing does this to some extent: it has different surface assumptions in urban vs rural areas. In particular, in the US, it assumes that highway=residential, tiger:reviewed=no is paved in urban areas, but not in rural areas. But yes, getting more roads explicitly tagged would be a big win.

This has been discussed a few times before. OSM maps “what’s on the ground”, so it’s not wrong to map these paths; however, if access is forbidden, then the consensus is to tag them as:

• https://wiki.openstreetmap.org/wiki/Tag:highway=path
• https://wiki.openstreetmap.org/wiki/Tag:access=no
• https://wiki.openstreetmap.org/wiki/Tag:informal=yes

You can read up on the background at osm.wiki/Proposed_features/Social_path and the various linked pages.

Great to see Merkaartor being revived.