Hi Mark,
Mark Burton wrote:
What I can see on my etrex is that the custom icon will disappear at
the level you expect (given the resolution value it has) but some of the
built in poi icons disappear sooner.
Which type ?
One thing we have to keep in mind is that also the gps settings (max. zoom
Version 1166 was commited by steve on 2009-09-04 10:06:15 +0100 (Fri, 04 Sep
2009)
BRANCH: multipolygon
Re-encapsulate some fields in Tags and Element.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Folks:
Inside official Garmin IMG files there are typically several tiles named
Ihex number.GMP. Does anyone know how the hex number is derived
please? I guess that it is a bit-interleave of the latitude and
longitude of some reference-point in the tile, but it could be a
byte-interleave, or a
Hi Felix,
Well one thing that this patch makes, is much much bigger filesize
(around 30% increase).
To be expected.
Furthermore it really crashes Mapsource. Not even possible to move out
anymore.
Hmm, not so expected.
After panning around a bit and choosing a well working zoomscale,
This v2 patch makes squarer subdivisions than v1 - otherwise works
the same.
diff --git a/src/uk/me/parabola/imgfmt/app/trergn/RGNFile.java b/src/uk/me/parabola/imgfmt/app/trergn/RGNFile.java
index f0300e8..5c0dc77 100644
--- a/src/uk/me/parabola/imgfmt/app/trergn/RGNFile.java
+++
Hi Gert,
What I can see on my etrex is that the custom icon will disappear at
the level you expect (given the resolution value it has) but some of the
built in poi icons disappear sooner.
Which type ?
Umm, can't remember exactly what I tried but I think it was 0x1b16
(lighted navaid,
Mark Burton wrote:
This v2 patch makes squarer subdivisions than v1 - otherwise works
the same.
Well, on v1 patch, the problem at this place appeared even without
having the problematic polygons in the polygons file.
With v2 it's back to normal and only happens with the problematic
Felix,
Well, on v1 patch, the problem at this place appeared even without
having the problematic polygons in the polygons file.
That's interesting.
With v2 it's back to normal and only happens with the problematic
polygons or without deleting a fair bit of my lines in the lines
Felix,
Please enable info logging by using the attached logging.properties file
and add this to the java options (note - it's a java option not a
mkgmap option)
-Dlog.config=logging.properties
rerun with v2 of the patch and email me the mkgmap.log file(s). They
should contain some diagnostic
Hi
On 04/09/09 10:16, Steve Hosgood wrote:
Ihex number.GMP. Does anyone know how thehex number is derived
please? I guess that it is a bit-interleave of the latitude and
longitude of some reference-point in the tile, but it could be a
byte-interleave, or a nybble-interleave, or the
Felix,
Okay, here are the output files. Once including the problematic
landuse=* line, once without.
Thanks. Unfortunately, they have too much other crap in them and not
enough of what I want to see. Did you use the logging.properties file I
sent to you?
Mark
Does the IMG file contain markup on junctions to control whether or not
a turn left/right announcement will occur when you reach it?
I've got a case locally where a tertiary road meets a primary road at a
shallow approach-angle of about 30 degrees. The Garmin does not announce
the junction,
Steve Ratcliffe wrote:
Hi
On 04/09/09 10:16, Steve Hosgood wrote:
Ihex number.GMP. Does anyone know how thehex number is derived
please? I guess that it is a bit-interleave of the latitude and
longitude of some reference-point in the tile, but it could be a
byte-interleave, or a
Ahh, you're adding POIs to areas, aren't you. Have you tried building
with that option turned off?
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Version 1167 was commited by markb on 2009-09-04 23:16:23 +0100 (Fri, 04 Sep
2009)
Fix isInfoEnabled() so that it tests the correct log level.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Version 1168 was commited by markb on 2009-09-04 23:16:26 +0100 (Fri, 04 Sep
2009)
Fixed the fixed* error reporting.
Now unwraps Errors thrown within worker thread.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Version 1169 was commited by markb on 2009-09-04 23:16:29 +0100 (Fri, 04 Sep
2009)
Make exception messages more realistic.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Version 1170 was commited by markb on 2009-09-04 23:16:33 +0100 (Fri, 04 Sep
2009)
Add --make-poi-index option to enable POI index generation.
The POI index, which used to be generated by default, doesn't actually
appear to be useful at this time. So now it's only generated if you
give this
Felix,
Wild guess here: I wondered if the POI index was overflowing and
trashing some other stuff because in the bad map example you sent, it
contained just over 32K entries. So commit 1170 disables POI index
generation. It wasn't useful anyway, so that's no loss. Please see if
that makes any
I've got a case locally where a tertiary road meets a primary road at a
shallow approach-angle of about 30 degrees. The Garmin does not announce
the junction, not warn of its approach when you're on the tertiary.
Coming from the other direction on the primary though, you get an in
Apologies if this is a stupid question. What is the benefit of
creating poi index? for search?
On Sat, Sep 5, 2009 at 6:16 AM, svn commits...@mkgmap.org.uk wrote:
Version 1170 was commited by markb on 2009-09-04 23:16:33 +0100 (Fri, 04 Sep
2009)
Add --make-poi-index option to enable POI
21 matches
Mail list logo