If there are hundreds of these within 50km^2, then perhaps the best suggestion is to use a more reliable atlas and complain to the company that makes them.

I can't imagine many people go tens of km out of their way to survey a single road - so a journey will not usually be completely wasted.

But if you must tag them, perhaps just put a note=* tag explaining why not to bother surveying. If you are just using it to effectively send an internal note to other mappers - and there are too many to use the wiki effectively, this seems sufficient.

Here's a possibility, a bit of an alternative.

Set up a wiki page/pages for each major area - and have a section detailing known mapping errors in that area (e.g. phantom roads) on other maps - akin to one we already have - Copyright Easter Eggs, but more localised. Make locals in your area aware of the page - as a mapping aid - so if they are going out to survey area xyz, they can look at the page before hand to check for phantom roads. You can be much more descriptive there as well. You could also use the wiki pages as an aid to collaborating with other OSMers.

Further to the above comments, I had a look at a couple of the rails where you have already removed tracks=* info. The information was added by someone who runs a company (ITO) that makes maps for people in the transport industry, which are used by many public bodies, including councils and I'm sure the Department for Transport. If he thinks having that information is of use to him, then it's far from clear that the information is "trivial" or "redundant".

And to answer a point in the other thread - yes, some people do play tennis when they're away from home. They might be looking for it if they have a match against the home club. There are namefinder applications which not only search for sports centres by name, but also can find the nearest sports centre to a particular place.

OSM has so many uses that it's difficult to argue that extra tags are trivial or redundant.

Don't remove information just because "lint" warnings appear. To be honest, any key may be used - the lint renderers should probably be updated to add tracks=x as a commonly used tag, and in this case it clearly adds extra information

There must have been something available before "EGNOS" was officially live as I've been able to get the "D" icons on the satellite signal strength bars for many months.

And I've had location +/- 7ft displayed before the "switch-on".

UrbanRambler: Just for the avoidance of doubt, "Fake Liam123" is a parody, a la "Fake Steve Coast" / "Fake Ed Parsons" etc. of Liam123, who has been vandalising objects all over the south of England.

He recently moved/altered some objects you had previously edited - which is what is referred to above. These have all been fixed.

All of my OSM photos have been taken whilst I've had my GPS with me. There are several pieces of software out there that can automatically add lat/lon to exif based on a GPX file and using the time-stamps in the exif.

surely highway=byway, designation=public_byway would get most of the access permissions down.
Others have used date_on and date_off with dates for restrictions.
There's probably no easy way of tagging restrictions conditional on a gate being locked or not - perhaps put a note on the tags as well to explain?

In the first line, the "1 mile south of Ottery St Mary" should have been south-west

From the description in this link, you are in about the right rough area;
http://www.aaib.gov.uk/cms_resources.cfm?file=/9-1981%20G-ARBY.pdf

The description of the landing site says;
"The crash site was a large, essentially flat, grass field approx. 1 mile south of Ottery St Mary, bounded on its eastern edge by a disused railway and the River Otter, and on its west side by Fluxton Rd. The field was some 700 yards in length - North/South"
"The Viscount's port wing had struck a large tree on the line of the northern boundary of this field...before the first ground contact some 200yds south of this tree on a bearing of 190º...The propellor assembly (less 1 blade found beside a dead sheep) was found detached and adjacent to a tree located some 170yds beyond the initial fuselage contact mark. THe tree showed marked evidence of contact on its trunk, and the outboard section of the port wing and outboard aileron section were nearby...The 2nd tree impact caused G-ARBY to yaw to port as it slid across the remainder of the field, coming to rest on a heading of 074º adjacent to the eastern boundary fence of the field"

Might be enough to go on there??

OpenStreetMap is mentioned (and linked to) from the BBC website article about the game.

http://news.bbc.co.uk/1/hi/technology/8245700.stm

I would suggest not tracing from NPE. It's not vastly accurate, there are no road names, and much of it will have changed significantly; and it still needs to be visited by someone to get road names. A better idea would be organising a mapping party. Potentially get OSMers from all over the country to come to Bolton and map it.

Widening the net, there could be a mapping party series - with Bolton, Bury, Rochdale and Oldham being the focus for successive parties.

And whilst I'm here, I asked Cheshire East to clarify the correct direction of a route as it was very unclear. They have an online footpath problem reporting page on their website. I imagine many councils have something similar. I got an e-mail back within a couple of days saying someone had investigated and agreed with me. I went back that way not long ago and there were new signs put up - and they'd also fixed a stile nearby as well.

There are usually waymark arrows, which gives you a direction to travel, and stiles/gates along the route. If there aren't any of these, and the route is lightly travelled such that there is no eroded trail at all, then ask the council to erect more signs/waymarks. They should do this if it's impossible to follow otherwise.

If there are waymarks, then follow them - again it can be inferred that if the council put the waymarks pointing in a specific direction, then that direction is correct.

If following the route is very difficult, then just do the best you can. If you are slightly out from the official route, then it's not the end of the world, particularly if the route you are following is the way everyone else goes (even if not the 'official' route).

To give yourself the best chance of finding the correct route;

When about to enter a new field, check for a waymark arrow on the stile or gate etc. Stop and look in the direction the waymark arrow is pointing. In the distance, you might be able to spot a post with a waymark arrow, or a 'fingerpost' sign-post or another stile or gate which is your exit point from the new field.

If so, then it's a reasonable assumption - in the absence of any other evidence - that the correct route might be a straight line between where you are and this waymark/post/stile/gate etc. in the distance.

When you reach this feature - have a look at the opposite side of it for a waymark arrow pointing back towards where you've just come from. Check the route you've walked matches the direction on the arrow.

Check the lie of the land; sometimes footpaths follow old trackways which might be slightly raised - or indeed lowered - above/below the level of the surrounding land. Follow this route rather than a straight line in this instance.

Many footpaths follow field boundaries - if your waymark arrow points you almost straight away towards a hedge or fence, then follow the hedge/fence until you reach a field exit, or another sign telling you not to.

Again, if you're slightly out, then it's not normally a problem. There are countless roads just traced from NPE which could be a hundred metres out or more.

> The only way to determine this is by reference to the DM.

Not really. As someone said above. If the council puts up a sign saying "public footpath" then we can infer that it is a legal right of way on foot.

It's completely analogous to how we collect road names. We don't copy road names from an official list or official map. We do so from the road signs that the council puts up, which is meant to reflect this list.

It's of course possible that a sign might be wrong (particularly in the spelling of road signs etc.) - but we should just map what is actually on the signs - whether something says "public footpath" or Acacia Avenue etc.

Quichina: If you can't tell which direction the path goes, follow the most logical route at the time. This will typically be a straight line across a field, or following field boundaries. If necessary, back-track to the last waymark arrow and check the direction. Follow a straight line from there in the direction the waymark arrow is pointing. Did it lead you to a stile, gate, or a post with another waymark arrow etc (even if broken). If so, you can be happy enough to mark that on OSM. If it didn't and you've reached the edge of a field, then you might need to track along the field boundary until you do find one. When you eventually find it, it's useful to back-track from this point to where you where you originally were (and knew you were still on the footpath).

If all fails, approach from the other direction, and see if you can end up on the original route.

If there are tall crops obscuring vision and possible routes through, then you might need to come back at a different time of year when there aren't. Growing crops on the line of a public right of way is not allowed and you could ask the council to sort this out.

If you, who after all is out actually looking to find the correct route, can't follow the correct route, then chances are not many others will be able to using the signs alone. Get onto the council and ask them to add additional waymarks or signs. The council have a duty to waymark routes where the situation is not clear.

If you do measurements at the same time on two consecutive days, the alignment of the satellites might not be much different - since the satellites orbit twice per siderial day (twice every roughly 23h 56m)

davidearl: Are you sure. I can't see anything on the Mapnik layer. I *can* see something on the Osmarender layer however.

These also work in the example you link to, Ash Kyd - both on the area and way.

The tag "name" is standard for naming objects.

If you have a name which is unofficial - e.g. perhaps some of those mentioned in traffic reports on the radio - something like "loc_name" might work for a name known to locals but unofficial

Whilst it's obviously frustrating - can I suggest you change the nodes to make right angles on a local copy of the data - rather than in the database?

Actually editing the data to achieve a desired result is not generally the done thing - it's not much different from tagging for the renderer.

What happens when you use the Mkgmap software to convert it into the right format is I think some roads get merged in the pre-processing. There must be some tolerance on the angle to decide if one road carries on from another (there are many thousands of split roads where you would not want an instruction).

There has been a lot of talk about using relations to create some sort of a priority path - (but I don't think this has really taken off yet) - to clear up confusion where two ways have the same name but you must turn off to travel between them.