Lates V7 map came with new poi database stored in db3(SQLlite) format when latest version of navi firmware (D-unit) just uses this database. That means, ppl with such a combination were unable to create custom POI database. Problem wasn't database itself, but coordinates (lat/lon) stored in one big "magic" number called z-value, what was hard to decode. Now everything changed as (with some help from few dudes) we have found, how to decode this speciality.
Finaly, you can try alone this calculator I've made:
Great article explain all about this can be found here.
So let expect new version of PI handling this database soon...
Friday, February 4, 2011
Subscribe to:
Post Comments (Atom)
8 comments:
Yeeeeees !
I can't wait !
You're the best
OMG, yes....
I can't wait the new version.
Hey, that sounds promising! Thanks for your good work :-)
Is there a trick to decoding the Z-Value (perhaps a bit shuffle, hash, or salt of some form)?
For value '9002980736026581713' (7 Eleven Broadbeach) the geo coordinates should be approx -28.035528, 153.43289, but I'm getting: -3.0031456E27, 7.040995E26 using the bit interleave/deinterleave method.
BTW - interleaving the bits for this location give me z-value: 8073641874292273677 (which can be successfully de-interleaved).
Does it have something to do with the bit representation of the floating point numbers being used? I'm using Java to convert raw integer bits to an IEEE float.
Hi there this tool doesnt seem to be working, is it broken?
Thaanks for sharing
Could you share algorithm of encoding/decoding? Or more any info
Post a Comment