On 01/10/2015 05:11, Warin wrote:
-1
Here am I taking nodes and making them areas - thus removing the node.
I think mkgmap needs some improvement to get relevant areas into POI
... if that is a problem.
I'd put money on a mkgmap 'expert' tell us that it is not a mkgmap
problem as it can be
On 1/10/2015 4:50 PM, Ian Sergeant wrote:
I guess I was talking about navigating there by aircraft.
A 'point' calculated for an aerodrome area would be good enough until
you had to select a runway .. where you would want the end points of the
runway .. not the node of the aerodrome (most of
On 01/10/15 20:44, Andy Townsend wrote:
I'm no mkgmap expert and even I manage to do it, using the
"--add-pois-to-areas" flag. :)
Wow, mkgmap has come a long way since the early days. Time for me to
have another look and revise my flags :)
One of the things it needs to do to be really
On 1 October 2015 at 21:17, Warin <61sundow...@gmail.com> wrote:
> On 1/10/2015 4:50 PM, Ian Sergeant wrote:
>
> I guess I was talking about navigating there by aircraft.
>
> A 'point' calculated for an aerodrome area would be good enough until you
> had to select a runway .. where you would want
I guess I was talking about navigating there by aircraft. For passengers,
sure you'd want a passenger terminal location, and an entrance to the same.
Ultimately, regardless of what form of transport you use, you are going to
be navigating to a point. The question is there an automated algorithm
Certainly when navigating to an airport, you need a 'point' to navigate
to. An calculation of a valid airport point from a airport boundary that
may often include industrial parks, etc, is problematic - verging on
intractable. Having this point 500m off significantly breaks stuff.
It's a
When travelling to an airport, you normally travel to a terminal which are
separately mapped, ideally with an entrance=main. Where would you put this
point at say Sydney where international and domestic are on opposite sides?
I think it's not the same as admin_center for admin boundaries.
On
You might as well clean it up as somebody is eventually going to find it here:
http://keepright.ipax.at/report_map.php?schema=50=56568170
and do it anyway.
On Wednesday, 30 September 2015, 19:31, Andrew Harvey
wrote:
Currently Melbourne Airport appears in
On 30/09/15 19:31, Andrew Harvey wrote:
Currently Melbourne Airport appears in the database twice, once as a
node once as a way. Is there any reason why I should not move the
tags from the node to the way and delete the node?
http://www.openstreetmap.org/node/235151361
Currently Melbourne Airport appears in the database twice, once as a node
once as a way. Is there any reason why I should not move the tags from the
node to the way and delete the node?
http://www.openstreetmap.org/node/235151361
http://www.openstreetmap.org/way/305804278
When I added the area there weren't a lot of airports locally tagged as
anything other than nodes.
I was probably being a little cautious at the time, i'd think it would be
safe to merge them now.
On Wed, Sep 30, 2015 at 7:31 PM, Andrew Harvey
wrote:
> Currently
Hi,
Another “me too” as I have almost exclusively used OSM mapping in my Garmin GPS
for a few years now. It’s highlighted all sorts of things, missing turn
restrictions, wrong speed limits (not visible but affects routing), street
names etc. Even works overseas, although I’ve mainly used it as
-1
Here am I taking nodes and making them areas - thus removing the node.
I think mkgmap needs some improvement to get relevant areas into POI ... if
that is a problem.
I'd put money on a mkgmap 'expert' tell us that it is not a mkgmap problem as
it can be done.
On 1/10/2015 12:04 PM,
@John I sympathies with your concern, but we can't hold up progress in the
OSM database for the sake of a particular GPS vendor or piece of software
not supporting the OSM data model. Right now with a point and area data
consumers would need to try to automatically remove points where they are
the
14 matches
Mail list logo