On 22/08/17 12:23, Colin Smale wrote:
> If you ask people where they live, they will probably talk about the
> county level and the settlement/town/city, but the informal boundaries
> of these settlements will likely not follow the administrative
> boundaries. In fact, it may not be possible to
Of course. But accuracy (perhaps correctness is a better word here) is
relative to some frame of reference. What is right under some
circumstances can be wrong under other circumstances. If you are a
postman, you have a different view of toponymy than a local government
official, a visitor or a
Alternatively in JOSM:
File > Download from Overpass API
Then put ref:Chiltern_Society = * in the text box next to "Build
query", then click "Build Query".
Next select download area, and then click "Download"
David
-- Original Message --
From: "Bob Hawkins"
Accurate *as possible*
On 22/08/2017 13:59, Colin Smale wrote:
That depends on your definition of "accurate", doesn't it?
On 2017-08-22 14:15, Dave F wrote:
But a query to the OSM database isn't interested in what 'locals'
misinterpret, it's interested in what OSM returns.
The ignorance
That depends on your definition of "accurate", doesn't it?
On 2017-08-22 14:15, Dave F wrote:
> But a query to the OSM database isn't interested in what 'locals'
> misinterpret, it's interested in what OSM returns.
>
> The ignorance of the person on the street is just one reason why OSM needs
But a query to the OSM database isn't interested in what 'locals'
misinterpret, it's interested in what OSM returns.
The ignorance of the person on the street is just one reason why OSM
needs to exist & be as accurate as possible.
DaveF
On 22/08/2017 12:50, Andy Townsend wrote:
On
OSM is geospatially aware. I'm unsure why there's a reluctance to use it.
is_in tags are far more "incomplete and imperfect" than boundaries.
Boundaries are maintained far more than the antiquated is_in:*.
*Every* entity will require a full set of is_in tags to be workable.
If an entity is in
On 2017-08-22 13:50, Andy Townsend wrote:
> On 22/08/2017 12:23, Colin Smale wrote:
> What would a "local" answer?
>
> Good luck getting a consistent answer to that :)
>
> http://ma3t.co.uk/euanmills/euanmills/tifd.html
Wow, I rest my case...
Although he seems to have asked people who were
On 22/08/2017 12:23, Colin Smale wrote:
What would a "local" answer?
Good luck getting a consistent answer to that :)
http://ma3t.co.uk/euanmills/euanmills/tifd.html
Best Regards,
Andy
(and apologies in advance for anyone upset by small-font profanity in
the link)
The main one I came across was is_in:continent=Europe. I asked why there
wasn't one. The conclusion was no one could agree where the boundary
actually was. Saying that, I'm unsure if specifying
is_in:continent=Europe is that beneficial.
Also many local authority political ward boundaries
Let's have some use cases out on the table... if my location is
{lat,lon}, where am I? What answer am I expecting? Postal address? Town
or other settlement? The local council? What would a "local" answer?
In the UK, the hierarchy of admin boundaries is incomplete and imperfect
- there are
Hi,
new to OSM edit. I live in an estate TW10 7NY. Currently 192 homes and
it is at risk of redevelopment in to make 425 homes. There is also a
community project to document historical features so I want to thank
you for this guidance. It will be helpful to edit entries.
Regards,
Andres
On Mon,
Hello,
I am an M.Sc. researcher with the University of Nottingham and am currently
conducting a research study regarding the potential for 3D building data
collection by OSM users and the crowd.
I am particularly interested in people’s motivations for collecting 3D building
information and
On 12/08/17 13:12, Dave F wrote:
> I also think the 'is_in:country_code' along with all 'is-_in' tags are
> redundant if there's a boundary tag..
In the past I thought that the is_in element was something of a problem,
but it does have a place when one remembers that OSM is all about the
data.
14 matches
Mail list logo
