logo separator

[mkgmap-dev] Track rendering on device

From Gerd Petermann gpetermann_muenchen at hotmail.com on Tue Nov 25 08:52:25 GMT 2014

Hi Patrik,

I also see this from time to time, but I think it happens only when I touch 
the display so that the device switches into a different mode. I don't know
how Garmin calls it, I call it move mode. In this mode the device shows a small
arrow in the bottom left corner, and it is no longer changing the map center
to my position.  Could this be your case?


From: KeenOnKites at gmx.net
To: mkgmap-dev at lists.mkgmap.org.uk
Date: Tue, 25 Nov 2014 09:43:43 +0100
Subject: Re: [mkgmap-dev] Track rendering on device

I have from time to time an issue on my 450t that might belongs into the same category.... 'unfortunately' also with mkgmap created maps (fzk) as I normally don't use the official garmin ones:

If I look at the garmin after a while in action (moving) it happens from time to time that the displayed recorded track (my actual movment) diplays wrong. It does not display my real movement but just has a straight line from somewhere off the map to the actual position.... as soon as the display get's updated (because it's turning due to my movment) or I zoom in/out it's displayed correctly again...

Actually I've noticed this only on the 450t not on any other garmins I use with the same maps (eTrex 30, Monterra).... if I remember correctly.


Not sure if it's the same, a similare or a complete other issue....






Gesendet: Dienstag, 25. November 2014 um 09:17 Uhr

Von: "Gerd Petermann" <gpetermann_muenchen at hotmail.com>

An: "mkgmap-dev at lists.mkgmap.org.uk" <mkgmap-dev at lists.mkgmap.org.uk>

Betreff: [mkgmap-dev] Track rendering on device

Hi all,

I wonder if this is a problem that is specific for maps generated with

mkgmap :

When I chose a track as target for routing the track is displayed as a

magenta line. When I follow this track on my bicycle the device sometimes

fails to render the map, as a result large areas are flooded with magenta .

The device is an Oregon 450t.

The problem disappears when I move a few meters or chose a different zoom

level. I'm never able to reproduce the problem at home, so I guess

it is related to the movement, maybe combined with low batteries.

I did not yet try if the latest changes regarding MapSplitter improved


Did anybody else see this effect in original Garmin maps?

Any idea what the reason is?

_______________________________________________ mkgmap-dev mailing list mkgmap-dev at lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev



mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20141125/c583d408/attachment.html>

More information about the mkgmap-dev mailing list