The problem is the Garmin-Data-Format.
Garmin use only 24 Bit for longitude/latitude. This is for the highest
zoom. If you reduce the zoom, then use garmin internaly only 23, 22, ...
Bit.
The biggest number with 24 Bit is 16.777.215. Use this for 360°. From this
it follows that 360°/16.777.215
Frank Stinner wrote
> The problem is the Garmin-Data-Format.
>
> Garmin use only 24 Bit for longitude/latitude. This is for the highest
> zoom. If you reduce the zoom, then use garmin internaly only 23, 22, ...
> Bit.
> The biggest number with 24 Bit is 16.777.215. Use this for 360°. From this
Am 24.12.2012 09:26, schrieb Frank Stinner:
> I think, there is no way.
The way would be to improve the reduce-point-density
options.
Chris
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://lists.mkgmap.org.uk/mailman/listinfo/mkgma
Am 24.12.2012 10:53, schrieb Chris66:
> The way would be to improve the reduce-point-density
> options.
Of course this would not help for buildings mapped with 4 points
but could improve roundabouts and streets mapped with a high
density.
Chris
___
m
GerdP wrote
> I assume this problem will "disappear" when cheap hardware is able to
> handle
> more details, means, Garmin will sell new hardware with new software and
> new map
> formats or everything will be done just in time using online data.
>
> Gerd
Offtopic: The competitors are already th
Hi,
I think we have solved this problem at least partly during the last weeks.
If you still find deformed polygons or roundabouts that cannot be explained
by the rounding problems, please let me know how to reproduce the problem.
Reg. roundabouts there is one additional source of problems in the
