[talk-au] Melbourne Airport (mapped as both node and way)

Andrew Harvey andrew.harvey4 at gmail.com
Thu Oct 1 05:43:41 UTC 2015


@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 same as an area they fall in. We shouldn't need to do that process. If
Garmin GPS's only support points, the conversion software should convert
these areas to points.

@Warin I support this, and would like to do this for the victorian airports
too.

On 1 October 2015 at 14:11, Warin <61sundowner at gmail.com> 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 done.
>
>
>
>
> On 1/10/2015 12:04 PM, Alex Sims wrote:
>
>> 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 a pedestrian, rather than driving.
>>
>> I’ve added a lot of car parks at places I visit at well. I need to add a
>> lot more addresses too.
>>
>> There are however some mkgmap peculiarities and the maps that most people
>> package up tend not to have their mkgmap configuration published and this
>> may produces strange results in an Australian context. Some recipes tend to
>> make a point for each area on the Garmin, so you definitely don’t want a
>> node and an area for a single POI as you can end up with three entries. The
>> mapping from OSM to Garmin for POI category seems also a bit variable and
>> often not what is expected. The other weirdness is due to OSM having
>> unlimited precision and Garmin having a max resolution of a few metres, so
>> I might have removed a few extraneous nodes here and there :), but I try
>> real hard not to “map for the renderer”
>>
>> Alex
>>
>>
>> On 1 Oct 2015, at 5:26 am, John Henderson <snowgum at gmx.com> wrote:
>>>
>>> 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
>>>> http://www.openstreetmap.org/way/305804278
>>>>
>>> Garmin GPS units have always been a favourite with OSM mappers, as well
>>> as the general public who don't want to pay exorbitant prices for map
>>> updates.
>>>
>>> I regularly update and use an OSM base map on my Garmin car GPS.  It's
>>> great for finding routing errors in the underlying OSM data.
>>>
>> _______________________________________________
>> Talk-au mailing list
>> Talk-au at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-au
>>
>
>
> _______________________________________________
> Talk-au mailing list
> Talk-au at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-au
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-au/attachments/20151001/e8e83cce/attachment.html>


More information about the Talk-au mailing list