Hi Gerd Yes, this code seems to be redundant; changing the limits didn't effect the behavior on my eTrex, so I guess they were chosen to attempt to match the in-build behaviour of the device. Ticker On Wed, 2017-06-07 at 20:23 +0000, Gerd Petermann wrote:
Hi Ticker,
this code is used for the make-poi-index option. I believe that this index is completely obsolete, but maybe the Etrex uses it. Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Mittwoch, 7. Juni 2017 11:51:27 An: mkgmap-dev@lists.mkgmap.org.uk Betreff: Re: [mkgmap-dev] Creating a point with a full address that can be found
Hi Gerd
I think you are saying that the IMG format doesn't support an address unless it is associated with a road/way. So I should give up this idea.
On a related subject to this and your recent work on MDR indexes, a while ago I found (on Garmin eTrex) that points with type 0x29 are findable with Find>"All POI". This POI shows as a small square icon without a label but hover does show the label. The other types "All POI" show are 0x2a-0x30 (ie food&drink, lodgings, attractions, entertainments, community, other..) and 0x12. It doesn't find Geographic Points.
This seems to be related to imgfmt/app/lbl/PlacesFile.java: public static final int MIN_INDEXED_POI_TYPE = 0x29; public static final int MAX_INDEXED_POI_TYPE = 0x30; ... void createPOIIndex(String name, int index, Subdivision group, int type) { assert index < 0x100 : "Too many POIS in division"; int t = type >> 8; if (t < MIN_INDEXED_POI_TYPE || t > MAX_INDEXED_POI_TYPE) return; ...
Do you know of a reason for this range? Is including 0x29 a mistake? Should it be configurable? Maybe all POI should be allowed?
I don't really need answers to these questions, more a matter of interest. I'm going to try changing the range to 0x0e .. 0x72
Ticker
On Wed, 2017-06-07 at 08:44 +0000, Gerd Petermann wrote:
Hi Ticker,
yes, the img format stores address info in a format that is similar to an addr:interpolation=* way along a road.
Gerd ________________________________________ Von: mkgmap-dev <mkgmap-dev-bounces@lists.mkgmap.org.uk> im Auftrag von Ticker Berkin <rwb-mkgmap@jagit.co.uk> Gesendet: Dienstag, 6. Juni 2017 17:59:19 An: mkgmap development Betreff: [mkgmap-dev] Creating a point with a full address that can be found
Hi
I have point items (actually postcodes) that I want to be able to find with the Find>Address function. These are not normally on a street, but I have a street name as a point tags that I want to use and standard mkgmap:admin_level processing provides the city, region and country.
Having them as standard POI doesn't look good (I'd rather they didn't show on the map) and they swamp other POI making find>"All POI" not very useful.
Having them as Cities has similar problems.
Trying to decipher how mkgmap processes address information, it seems to be totally tied up to ways (MapRoad/RoadDef).
Does anyone know if this might be possible?
Thanks Ticker
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev