Hi, I have noticed unusual behaviour of some POIs. I cannot understand why some types are shown even at low detail level where others are not. An example: point|tourism|picnic_site|0x4a|0x00|20 point|tourism|information|0x4c|0x00|20 point|amenity|toilets|0x4e|0x00|20 are visible in MapSource even as all other POIs with resolution at 20 or slightly less are no more there. Does MapSource treat these three types specially? That is resolution 20 for these types means something else as for other types? I have double-checked (grep -r) for "picnic_site" in my garmin related directories, and the only definition of this feature sets the resolution to 20. Any ideas? Paul -- Don't take life too seriously; you will never get out of it alive. -- Elbert Hubbard
Hi! Paul Ortyl schrieb:
I have noticed unusual behaviour of some POIs. I cannot understand why some types are shown even at low detail level where others are not. An example: point|tourism|picnic_site|0x4a|0x00|20 point|tourism|information|0x4c|0x00|20 point|amenity|toilets|0x4e|0x00|20 are visible in MapSource even as all other POIs with resolution at 20 or slightly less are no more there.
Does MapSource treat these three types specially? That is resolution 20 for these types means something else as for other types? I have double-checked (grep -r) for "picnic_site" in my garmin related directories, and the only definition of this feature sets the resolution to 20.
When creating custom styles, I have observed that in the Garmin maps some POI types are treated differently. Of several pois with different types and identical resolution, some show earlier and some show later. Objects with id 0x1e show up earlier than objects with id 0x17 even though both have resolution 21. I have seen this behavious on the device, but I guess it may be the same principle in MapSource. bye Nop
Nop schrieb:
When creating custom styles, I have observed that in the Garmin maps some POI types are treated differently. Of several pois with different types and identical resolution, some show earlier and some show later.
I have seen this behavious on the device, but I guess it may be the same principle in MapSource.
I can confirm this problems. Not all POI numbers are working (correctly or at all) when you are using typ-files. Mapsource and the devices are behaving a little bit differently, but both show strange effects. Sadly this is also true for some of the numbers which are used for the POI searches. So at the moment I choose a better map display instead of the POI search and stay with the numbers I know to work correctly: 0x40??, 0x41??, 0x50??, 0x51??, 0x60??, 0x61?? Gruss Torsten
participants (3)
-
Nop -
Paul Ortyl -
Torsten Leistikow