The markup is just HTML so no need to go looking at any source ;-) It will be sanitised so some things may not work but basic markup should.

Please don't "tag for the renderer" by adding reference numbers to the name - tag the data (which is our primary asset) correctly and then wait for the renderers to catch up and get cleverer about rendering things. They are improving all the time you know!

Adding URLs to images as tag values is certainly not supported by any renderers as far a I know, and quite likely never will be as it's a path to abuse. I realise there is an issue in countries like the US where it is common to have lots of different shield styles and people expect to see them on the map but we need a better solution than taking URLs from the tag data.

You find find http://api.openstreetmap.org/api/0.6/way/$WAY/full a bit simpler ;-)

Agree with Richard. I live about a mile from the A10 and know full well that it is not trunk in UK government terms, but it is trunk in OSM terms so please leave it alone.

Importing POIs from wikipedia is generally considered to be a bad idea due to the way much of wikipedia's geodata has been sourced - some of it at least is believed to have been derived from sources like google maps. See this recent mailing list thread for a discussion of the issue:

http://www.nabble.com/Wikipedia-POI-import--to23392791.html#a23394016

Jenny didn't have prawns - she had the Whitebait (http://en.wikipedia.org/wiki/Whitebait).

IE6 should be working again now.

Changing the language of a diary entry after it was written was not working due to a bug which I have just fixed.

I think you'll find there's no such thing as an "allowed" or "not allowed" value for a tag - we're not proscriptive about such things.

You appear to have managed to create a duplicate of Sheffield Street somehow. I've removed the extra one now.

It also seems to like adding silly "test" roads in the middle of Nigeria:

osm.org/?lat=9.99961&lon=10.00212&zoom=17&layers=B000FTFTT
osm.org/browse/changeset/914200
osm.org/browse/changeset/914200

Lesson 3. Pay attention to the words "You need JOSM version 1529 or later" in the JOSM banner message about the 0.6 API update ;-)

I'll also add that what you must not do is to just upload your original data again with the extra tag added - if you do that you will leave two of everything in the database.

It's probably based on the planet dump, which means it will only update once a week at most.

No, the solution is not to split the way. Nor is it to provide a means of manual location. The solution is to fix whatever renderer is not choosing the right location.

Just to make things clear - that isn't my site, it's Matthew Somerville's, so if you have suggestions for improving it you should aim them at him.

It's a bug that was fixed within half an hour of somebody mailing me about it (which was about two hours before your post).

...except that surgeon also appears to be the only editor of that way as well!

I think surgeon may have been referring to osm.org/browse/way/24866162 which is under the way specified. Presumably in attempting to remove it the other way was accidentally added.

It's because mapnik does not support vector icons at the moment - please feel free to fix this limitation.