
Hi Nick, Are you telling me that the man-made codes, 6400 and above, are not searchable in MapSource "Find Place-->Resource" tool? I mean, is this a mkgmap rule? I'm asking because I used to compile my maps with cgpsmapper and this search is allowed there. So, since I'm a mkgmap beginner, I do not know if this is a problem in mkgmap (bug) or conscious decision/rule. Thanks Alexandre 2015-03-17 19:03 GMT-03:00 nwillink <osm@pinns.co.uk>:
I'm not so sure mkgmap creates unusual search results, as the behaviour you describe applies in my experience to TOPO maps as well.
6402 like all 6400+ falls under 'man made' - the way they 'appear' differs depending on whether you are using Mapsource,Basecamp or say the Oregon - the more recent gps devices feature categories not even listed in Basecamp.
Often Mapsource gives more results than Basecamp - they are not limited to a particular region BUT its categories are more limited.
r
Nick
-- View this message in context: http://gis.19327.n5.nabble.com/Building-POI-are-not-searchable-resource-tp58... 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