Hi All,
I recently started using the map editor hopefully doing some uncontroversial edits, thought I’d better drop in and say Hi!
I do have a small question though. I was looking at a village in which I used to live and there seems to be a discrepancy between the road name as reported by the OS online (and Waze) and the signage on the ground as well as the local naming of the road.
For the moment I have added an alternative name to the road segment… have I done the right thing there? The road is Batsford in St Mary Bourne, Hants.
The first segment from the B3048 is known locally as School Lane and the street sign at the B3048 end says “School Lane leading to Batsford”. The OS online has the whole road as Batsford (I haven’t had a chance to check the paper version). Google maps has it as School Lane. The first 2 houses in the road have an address of School Lane, the second 2 and those in the branch to the left going in all have Batsford as their address.
Thanks in advance for any advice!
Richard
Hi Richard, and welcome to the forums. :mrgreen:
You’re right in that OS has the whole road as Batsford and the Waze information is almost certainly taken from there, since the OS data is public domain and we have a script that allows us to copy OS data straight into Waze. However, physical signage should always take priority - after all, If Waze says “turn left onto Batsford” and the sign in front of the driver contradicts that, it does not present a good experience.
The alternate name will be used for address search, but it will not be announced or even visible in the app.
From what you describe, the best thing would be to split the first segment of Batsford into 2 segments, just after the first 2 houses. Then name the first new segment “School Lane” and the second new segment “Batsford”. No need for alternate names. Also, because it will very obviously be a deliberate edit, there is little likelihood another editor will come along and change School Lane back to Batsford based on the OS data.
Thanks for the reply… I’ve now made the edit as suggested.
The splitting of the road looks good - but you’ve managed to introduce some forbidden turns somehow! If you press SHIFT-Z, that toggles between “show all turn arrows for a single, selected segment” and “show all red arrows (forbidden turns)”.
Since all turns are allowed here, the simplest way to rectify it is to click on the junction node where the segments meet, and in the left-hand pane click on “disallow all turns”, then “allow all turns”.
Why disallow all first? For various complex technical reasons, Waze can sometime enable “forbidden” turns, like turns the wrong way onto a one-way segment. Although these don’t affect routing nowadays, experienced editors will still do both actions to make sure those invalid turns are cleared.
Also, we do not normally enable u-turns. Given the size of most British roads, doing a proper u-turn at an intersection is rarely practical for all vehicles. That’s why they teach us “reversing around a corner” in the driving test. 
The biggest problem is that, if a user has left the Waze route for some reason and Waze wants to turn them around, it will direct a user to turn up School Lane/Batsford simply to take the u-turn at the bottom.
Oops sorry! I’ve made another edit to allow all the turns at all of the nodes on that road and turned off the u-turn.
Thanks again for your advice. It shows how easy it is to miss something!
Looks perfect now. :mrgreen: