theCrag/website — Issue #470: Show inherited location on route and possible area pages
Author: brendanheywood
Created: 2012-02-28 08:14:21+00:00
State: open
Labels: Enhancement, Idea for discussion, Maps

A 'boulder' area might be located to within a couple meters, or a 'cliff' area within 10's of meters but when you go to a route page it says it is unlocated. As a general rule we probably don't even want to encourage locating individual routes as you can just locate the area and in most cases that is enough accuracy to get you to the cliff and then the topos would take over as the primary form of nav.

So, I think in web view we should pass through the most located ancestor node. Even if this is a grandparent or further up. We can infer from this location the accuracy, so we can give a lat long and then say, accurate to 100m using some simple algorithm (even just bbox max size).

I'm thinking we could even extend this to the API but we need to be careful, if someone gets a crag they can infer this themselves, but if they only request a route then we could give them the inherited nodes location.