<<Thats where I first spotted them ;> old things that have past on today based maps has been an issue in the past esechialy when some old non exsitant things are added to paper maps like roman roads to ordance servey I think it just takes an achalogists confimation to mark them maybe it changed since then. OSM solved the issue by spawning OHM. which when done allows both datasets to be be loaded together when needed. OSM's detail level is outstriping large parts of OHM at the moment but the dual use gets around the slower growth at this early stage.>>

Hi there is a quiry from a user about wether you may have misspelt the name of a staircase as 'Stairecase 8' and we wondered if it was an intential spelling or a mistake?
The note is at:- osm.org/note/493340

this sign was a very large direction sign. Somehow this needs to be a relation and not a phiscial way according to:-
osm.wiki/Relation:destination_sign
which is confusing to do to a real object rather than a virtual sat-nav indicator.
there seems a lot of confusion possible till you realise that there are two functions of defining and indicating traffic signs in OSM
Function 1: Alert the navigation system that a traffic rule is in action in a place or part of the road.
Function 2: To indicate the location of street furniture used to make a physical sign displaying infomation to road users.

In simply mapped areas using a single way for everything then tags fit to way sections for function 1, and a point, with point specific tagging, carries function 2.
Its been debated wether the point goes on and into the way (as all is 1-dimensional) or by the side like a more 2-dimensional form. The obvious over sign has hight seperating layering style tags to avoid confusion.

Now in more complex and more detailed mapping used for small area rendering like doorway approches etc meny line features gain full areas and it is logical to make point features of flat objects into lines carring the same tagging to give the same meaning especialy when signs become 10 meters tall and twice the width of the sidewalk like on the southen bypass. there are also box bolard signs used along this road when the flat ones where crashed into that was a cheap replacement. they may apper as tiny squares after being areaised the four faces can carry different signs when needed too (though I don't think the replacement one here dose and carries a non-sign on one side a black rimed white circle).

The function1 role for the traffic_sign UK:610 is given by forceing a split of the routing line at the correct spot to obay it, in an areaised highway. Remeber that the road now has lots of width as well as length and the routing line needs to follow the middle of the carrage way and not run over the sidewalk lamps and poles just drwan in the middle of the road, and this is the natural way to guide cars and busses past the features too (when some one measures the lane width changes and gives it in lane features it will make more sence too that lorries can take a staighter course but the routing line needs to fllow the middle for the logic of so meny other tags that get dumped on it. so that's why I drew them as I did. reading the wiki still dosn't seem to put this into question (especialy if you take the licence to convert points to ways when converting ways to areas when this make most sence when scaled to the phisical feature (ie the same size as real life)

The problem with this direction sign (in osm.org/changeset/36931147) is that direction signs don't commonly carry a common referance standard-drawing number in the pointed too offical traffic_sign manual because the signs a composed on a custom to site basis following some layout rules on stuff like spaceings and line widths and angles etc. So the function 2 tagging so far seems absent as only the function 1 seems covered so this sign needs to be here to be added to a form of more virtual sign defined here:-
osm.wiki/Relation:destination_sign
possibly as a new role type of physical sign board or something...

The sign contains sub signs too as well a very long winded textual execption list that will probably need a lot of special use of clausual tags (more common to parking) on top of this there is question make about the intergation this with lane tagging and/or diffend marking as although these are ghost lanes only the tagging for laneing carries a lot of this infomation on lane use and possible extions of the inclusion of detination tagging to complement this signs intentions, this is fitting more of the function 1 role. Finally the question of how to intergrate possible lane features that may be drawn in future into any relation for
osm.wiki/Relation:destination_sign
Is another question that will probably be answered as a yes included.

As I had run out of time for this doing the other 100 features needing offset correction I drew a simple sign board so it could at least be used for function 2 pedestrian navigation uses on the sidewalk (like "oh yes I'm here; because overthere's that huge sign shown on my map"). Also others might feel like finishing the puzzel for me as it wasn't finished.

the absolute compas system makes more sence when you see that the point has no direction feature to relate forward or backward to and the roads around are split into to one way section in opposeing directions.

It might make sence when the sign sits on the line of or just by a highway marked only by one way. since this has just been areaised that no longer works in a prctical sence anymore so relateing to the map orintation is simpler to work with. this is a escialy true on the middle of roundabouts faceing the outside direction!

osm.wiki/Key:traffic%20sign?uselang=en-GB
page in relation to last comment

from the traffic sign wiki:-
You can use the direction=* tag to describe the facing orientation of the sign by using an angle or cardinal direction.

I got an email today a bout a traffic sign.
I can't find what you are pointing to to its isn't comming up in my system where is the sign you are talking about That changeset had so meny changes on arournd a 100 objects I can't remember which may have missed something from by mistake?

oh yes I must have done without a recheck from a dogey memory I thought it was a highway feature...

ok that how I've left it witht the barrier tag too.

yes I did just recheck and spell it the original way with central

oh ok how about:-

highway=central_reservation
barrier=traffic_island

?

I'm minded to reverse this change as the wiki suggests that your new tag is a painted line in the middle of the road the line is a indication of a traffic island that turns this into a dual carrageway and the line is the central resevation (like the bit in the middle of an Autobahn!) This site was only finished its latest remodel last year so not a lot of sources are up to date.
I sourced the tag from a stretch of the A4074:-
osm.org/way/107118868
where I'd done some earlier work. The spelling of not useing central instead of Centre seemed a bit odd but it seems to be something people have been ok with for the last 5 years so I jst tryed to be consitant.
I was thinking about adding a area for it but I was haveing a lot of tree overhang a loss of the redesign plan ment I couldn't be acurate so I chose the way it was done 5 years ago for the time being but I'll add the island when it is well fillmed for bing maybe if no one else goes and measures it first...

hello Richard,
can you tell me whether the deleted parking asles are the ones missing at the moment that lie on the over platform structure?
if they were could you revet them back or did I need to reservey and add start to them all again?
currently there's the ramp that goes up and down, some stair structures and the platform but I thought I'd put in some more of the footways and level1 routes marked and signed on the platform?

Hi Andrew Chadwick, Can you check that you aren't missing some prefixes to some of the times and other features you added in this changeset. St. Aldates operates 24hrs a day all year round, As does the Highstreet and most directly connecting roads.
Some one left a fixme about this but it isn't clear what the things relate to be able to fix them. Using a sub feature relation to colect tags about a perticular asspect of the road or a prefixing more commonly used to avoid this type of confusion could help?

Yes I's studied the lfts and most if not all can go to the basement and the fire escapes have been sperated for both people going up and people going down so they don't miss the ground floor exit to safty when the place is filed twith smoke and people can't tell where they are well.
I'm looking to do soom indoor work on the site over some time (to fit it in)
Thanks againg for your help.

thank you for your help

I thought it did when I looked at the other day I'll do a recheck. I think they needed to change the lift to give in to leagal and moral presure, plus they get more custom too.

Hi Martin, I was looking at the changes you made to the M&S store in Oxford and I was wondering how you came to the conclusion that the store was not totally wheelchair accessable? I've just been in and I found customer lifts to all levels wide routes though the goods disabled toilets level access to the reastaunt staff amenable to serveing at lowerd counters wheelchair accessable banking facilities and the only bit not checked throughly was the fitting rooms.
I was wondering if you could let me know so I check if the sticking point has since changed and then I can alter this tag you left about to accessable?
Meny Thanks,
Govanus

the discription was wrong for this edit. the description should be:- serveyd details at Oxford Brookes Uni

thanks for this I was planning or doing some of these soon.
I think I was confused by the mistakes of others who insisted on converting all my highway:area and landuse=highway tags into highway=* & area=yes tags so they all came out like plazas. I tried to add area:highway tags too to at least let not be confused with the routing lines in some systems but I was never happy with them - though they did come out nice on standard at openstreetmap.org (but that wasn't the point). This rendering also confused me as I didn't relise I was seeing plaza code and just thought the render was wrongly mapping only area=yes road features(as a stanard for doing a road and not the plaza's only).

I guess I've got a lot of fixing to do. Thank you for sorting out this part.