maning/osmphgps

include addr data as POI

Closed this issue · 3 comments

maning commented

create a minimal searchable POI for address data.
@ralleon, what hex would you reccomend?

ralleon commented

let's sacrifice any unused hexcode of geographic land feature. you can try
the following. Just assign an invisible or a low profile "dot" on TYP
660b gap
660c isthmus
660e lava
660f pillar

they are currently not searchable in mapsource v6.13.7
but i expect them to be searchable in the latest version of mapsource,
basecamp, and when loaded in garmin receivers

I cannot experiment or compile on mkgmap right now, as I'm currently
experiencing unexplained (clueless)
Error in style: Error.... Stack size is 2

On Mon, Jul 4, 2011 at 6:13 PM, maning <
reply@reply.github.com>wrote:

create a minimal searchable POI for address data.
@ralleon, what hex would you reccomend?

Reply to this email directly or view it on GitHub:
#32

maning commented

Too much clutter, should be removed in the public map.

ralleon commented

must advise the user that the details is optimized at "high", not higher or
highest

On Sat, Jul 16, 2011 at 10:44 PM, maning <
reply@reply.github.com>wrote:

Too much clutter, should be removed in the public map.

Reply to this email directly or view it on GitHub:
#32 (comment)