Hello experts, there are many POIs like barrier, traffic lights, trees an so on. Is it possible to show them in the map, but without a hit in the poi-search? Best regards Arndt
Am Freitag, 5. Juni 2015, 08:46:36 schrieb Arndt: Hi Arndt you can use these types 0x2900-?, they are visible in 'all POIs', but not in other categories We, Franco and i, made a lot of tests to make sure how POIs types are sorted by the garmin devices. Bernd
Hello experts,
there are many POIs like barrier, traffic lights, trees an so on. Is it possible to show them in the map, but without a hit in the poi-search?
Best regards
Arndt
-- amarok2 now playing:
Sorry, clicked to fast The customs types, 0x011500-0x01161f, are not shown on my Oregon, searchable only over a complete search. Bernd Am Freitag, 5. Juni 2015, 09:36:02 schrieb Bernd Weigelt:
Am Freitag, 5. Juni 2015, 08:46:36 schrieb Arndt: Hi Arndt
you can use these types 0x2900-?, they are visible in 'all POIs', but not in other categories
We, Franco and i, made a lot of tests to make sure how POIs types are sorted by the garmin devices.
Bernd
Hello experts,
there are many POIs like barrier, traffic lights, trees an so on. Is it possible to show them in the map, but without a hit in the poi-search?
Best regards
Arndt
-- amarok2 now playing:
I've been able to find out which POIs on my Oregon 450 and 600 are searchable and which are not using the following method: 1) Create a 'fictitious' mp file with POIs ranging from say 2a00 to 7F00 and an another one from 11500 to 14400 2) Use the type number as labels 3) Have the coordinates fairly close together so it can be scanned easily in Basecamp etc as well. 4) use mkgmap to parse the files and dump on device. You will notice the search differences between your device and say Basecamp You will also discover new search categories, ie Book Store. You also discover which types as yet not used by Garmin -- View this message in context: http://gis.19327.n5.nabble.com/POIs-without-POI-search-tp5847187p5847264.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Nick, I think we should add such a file to the mkgmap dist. Would you mind to post a link to yours? Gerd
Date: Fri, 5 Jun 2015 09:19:07 -0700 From: osm@pinns.co.uk To: mkgmap-dev@lists.mkgmap.org.uk Subject: Re: [mkgmap-dev] POIs without POI-search
I've been able to find out which POIs on my Oregon 450 and 600 are searchable and which are not using the following method:
1) Create a 'fictitious' mp file with POIs ranging from say 2a00 to 7F00 and an another one from 11500 to 14400 2) Use the type number as labels
3) Have the coordinates fairly close together so it can be scanned easily in Basecamp etc as well.
4) use mkgmap to parse the files and dump on device.
You will notice the search differences between your device and say Basecamp You will also discover new search categories, ie Book Store. You also discover which types as yet not used by Garmin
-- View this message in context: http://gis.19327.n5.nabble.com/POIs-without-POI-search-tp5847187p5847264.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi, I think best would be to add the compiled map for device and BaseCamp. Compile-process should stay the same. Would be very appreciated! Henning
Hi Henning, I just learned (again) that mkgmap has a feature to create a map, at a first glance the result looks similar to that of the map generated by Nick: java -jar mkgmap test-map:all-elements creates it. With r3612 I see some warnings SCHWERWIEGEND (ShapeMergeFilter): test-map:all-elements: shape is not closed with identical points 0 I'll fix this soon. Gerd osm-8 wrote
Hi,
I think best would be to add the compiled map for device and BaseCamp. Compile-process should stay the same. Would be very appreciated!
Henning
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/POIs-without-POI-search-tp5847187p5847430.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
Hi Gerd, so test-map:all-elements did the same as POI-tester? Do you know the range of the generated POIs? Or is the range based on style? Henning
Hi Henning, I am just looking at the code. Up to now it generates POI from 0x00 to 0x7f with subtypes from 00 to 30, and also some lines and shapes. I think it should be easy to add some options to generate extended type POI as well. See also the comments in the source code: http://www.mkgmap.org.uk/websvn/filedetails.php?repname=mkgmap&path=%2Ftrunk... <http://www.mkgmap.org.uk/websvn/filedetails.php?repname=mkgmap&path=%2Ftrunk%2Fsrc%2Fuk%2Fme%2Fparabola%2Fmkgmap%2Freader%2Ftest%2FAllElements.java&rev=3613&peg=3613> Gerd osm-8 wrote
Hi Gerd, so test-map:all-elements did the same as POI-tester? Do you know the range of the generated POIs? Or is the range based on style?
Henning
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/POIs-without-POI-search-tp5847187p5847436.htm... Sent from the Mkgmap Development mailing list archive at Nabble.com.
participants (6)
-
Arndt -
Bernd Weigelt -
Gerd Petermann -
GerdP
-
Henning Scholland -
nwillink