Question reg. points with extended type
Hi, when mkgmap builds an index (the mdr file), it reads the points from the img file. Up to now, points with extended types are ignored by this routine. I wonder if this is a GARMIN restriction or a limit in mkgmap ? Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Question-reg-points-with-extended-type-tp5755... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi, On Sun, Mar 31, GerdP wrote:
Hi,
when mkgmap builds an index (the mdr file), it reads the points from the img file. Up to now, points with extended types are ignored by this routine. I wonder if this is a GARMIN restriction or a limit in mkgmap ?
Which index is that exactly? On my GPSmap 62s, all POIs are listed in the nearest POI search, even the one with extended types. On my GPSmap 60CSx POIs with exteded type are not findable. But: The 60CSx needs 2 sec. to list all POIs in the near, the 62s needs 6 sec. Looks like the 62s does not use the index but generates it somehow itself new. Thorsten -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Hi Thorsten, good that you asked. I just found out that the overview2 branch did no longer create the index in the same way. This is corrected with r2558. The so called global index is created when you use the --index option. I don't know for sure what the device does with it. I assume that a map with many point with extended types needs longer to list the POIs, because they are not indexed. Don't know if that can be changed. Gerd Thorsten Kukuk wrote
Hi,
On Sun, Mar 31, GerdP wrote:
Hi,
when mkgmap builds an index (the mdr file), it reads the points from the img file. Up to now, points with extended types are ignored by this routine. I wonder if this is a GARMIN restriction or a limit in mkgmap ?
Which index is that exactly?
On my GPSmap 62s, all POIs are listed in the nearest POI search, even the one with extended types. On my GPSmap 60CSx POIs with exteded type are not findable.
But: The 60CSx needs 2 sec. to list all POIs in the near, the 62s needs 6 sec. Looks like the 62s does not use the index but generates it somehow itself new.
Thorsten
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Question-reg-points-with-extended-type-tp5755... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Gerd, On Sat, Apr 06, GerdP wrote:
good that you asked. I just found out that the overview2 branch did no longer create the index in the same way. This is corrected with r2558.
The so called global index is created when you use the --index option. I don't know for sure what the device does with it. I assume that a map with many point with extended types needs longer to list the POIs, because they are not indexed. Don't know if that can be changed.
Looks more like a firmware issue. I removed all extended types, 60CSx still needs only 2 secs, 62s still needs 6 seconds. Thorsten
Thorsten Kukuk wrote
Hi,
On Sun, Mar 31, GerdP wrote:
Hi,
when mkgmap builds an index (the mdr file), it reads the points from the img file. Up to now, points with extended types are ignored by this routine. I wonder if this is a GARMIN restriction or a limit in mkgmap ?
Which index is that exactly?
On my GPSmap 62s, all POIs are listed in the nearest POI search, even the one with extended types. On my GPSmap 60CSx POIs with exteded type are not findable.
But: The 60CSx needs 2 sec. to list all POIs in the near, the 62s needs 6 sec. Looks like the 62s does not use the index but generates it somehow itself new.
Thorsten
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Question-reg-points-with-extended-type-tp5755... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
Hi Thorsten, okay, let's wait for a feedback from Steve. I have almost no knowlegde about the index structures. Gerd
Date: Wed, 10 Apr 2013 23:23:32 +0200 From: kukuk@suse.de To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] Question reg. points with extended type
Hi Gerd,
On Sat, Apr 06, GerdP wrote:
good that you asked. I just found out that the overview2 branch did no longer create the index in the same way. This is corrected with r2558.
The so called global index is created when you use the --index option. I don't know for sure what the device does with it. I assume that a map with many point with extended types needs longer to list the POIs, because they are not indexed. Don't know if that can be changed.
Looks more like a firmware issue. I removed all extended types, 60CSx still needs only 2 secs, 62s still needs 6 seconds.
Thorsten
Thorsten Kukuk wrote
Hi,
On Sun, Mar 31, GerdP wrote:
Hi,
when mkgmap builds an index (the mdr file), it reads the points from the img file. Up to now, points with extended types are ignored by this routine. I wonder if this is a GARMIN restriction or a limit in mkgmap ?
Which index is that exactly?
On my GPSmap 62s, all POIs are listed in the nearest POI search, even the one with extended types. On my GPSmap 60CSx POIs with exteded type are not findable.
But: The 60CSx needs 2 sec. to list all POIs in the near, the 62s needs 6 sec. Looks like the 62s does not use the index but generates it somehow itself new.
Thorsten
-- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Question-reg-points-with-extended-type-tp5755... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev -- Thorsten Kukuk, Project Manager/Release Manager SLES SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
participants (4)
-
Gerd Petermann -
GerdP
-
Minko -
Thorsten Kukuk