Results 1 to 3 of 3

Thread: iGuidance 3.0 POI file format - partial decode

  1. #1
    Newbie
    Join Date
    Dec 2006
    Posts
    2

    iGuidance 3.0 POI file format - partial decode

    Instead of just bumping the old thread I decided to start a new thread; in part because much of the information in the old thread seems outdated or inaccurate. Old thread: Editing/reading iguidance POI bin files

    I have been decoding the POI file and I have determined:

    Little-Endian coding is used.

    At offset 0x24 there is a ULONG referring to the number of entries in the string table.

    At 0x78 the string table starts. Entries are separated by NUL. It ends at 0xAEF196.

    POI entries are 31 bytes long.
    There is no static separator between entries.
    The structure is as follows where B is the starting offset of a POI.

    B+0 = ULONG where the OFFSET IN THE FILE of the string in the file is determined by the 20 LSB (mask with 0x000FFFFF to get offset). I have no idea what the high 12 bits are for but they are used.
    B+4 unknown, likely signed LONG, -1 is common in sections
    B+8 unknown, but matches between POIs with same LAT/LONG (maybe just LAT?)
    B+12 unknown, but matches between POIs with same LAT/LONG (maybe just LONG?)
    B+16 FLOAT, LATITUDE
    B+20 FLOAT, LONGITUDE
    B+24 USHORT, flag bits of some kind, very sparse "bit-on" pattern
    B+26 unknown, likely LONG, I think it might be the same for all POIs in a section (most-significant byte never seems to be utilized)
    B+30 CHAR, values range from 1 to 34 or so, smells like flags

    One group of POI entries starts at 0x01516C05

    If this kind of hacking is something people enjoy or if you have information/know of something else started along these lines, lets me know. I could use help decoding the POI packing structure (the POI entries are separated into what appears to be geographical groups). I just hope there is no embedded BTREE or anything :-/

    As a bonus, if I can get this decoded, a POI editor for all!

  2. #2
    Calm
    Down
    Or
    Get
    A
    2
    Week
    Vacation
    -Love
    The
    Forum
    Policeman
    Wiredwrx's Avatar
    Join Date
    Jan 2003
    Posts
    3,605
    Quote Originally Posted by pstickne View Post
    Instead of just bumping the old thread I decided to start a new thread; in part because much of the information in the old thread seems outdated or inaccurate. Old thread: Editing/reading iguidance POI bin files

    I have been decoding the POI file and I have determined:

    Little-Endian coding is used.

    At offset 0x24 there is a ULONG referring to the number of entries in the string table.

    At 0x78 the string table starts. Entries are separated by NUL. It ends at 0xAEF196.

    POI entries are 31 bytes long.
    There is no static separator between entries.
    The structure is as follows where B is the starting offset of a POI.

    B+0 = ULONG where the OFFSET IN THE FILE of the string in the file is determined by the 20 LSB (mask with 0x000FFFFF to get offset). I have no idea what the high 12 bits are for but they are used.
    B+4 unknown, likely signed LONG, -1 is common in sections
    B+8 unknown, but matches between POIs with same LAT/LONG (maybe just LAT?)
    B+12 unknown, but matches between POIs with same LAT/LONG (maybe just LONG?)
    B+16 FLOAT, LATITUDE
    B+20 FLOAT, LONGITUDE
    B+24 USHORT, flag bits of some kind, very sparse "bit-on" pattern
    B+26 unknown, likely LONG, I think it might be the same for all POIs in a section (most-significant byte never seems to be utilized)
    B+30 CHAR, values range from 1 to 34 or so, smells like flags

    One group of POI entries starts at 0x01516C05

    If this kind of hacking is something people enjoy or if you have information/know of something else started along these lines, lets me know. I could use help decoding the POI packing structure (the POI entries are separated into what appears to be geographical groups). I just hope there is no embedded BTREE or anything :-/

    As a bonus, if I can get this decoded, a POI editor for all!
    Definitely head over Adding POI's in iGuidance??? and post your findings.

    Check out the last couple of pages, there has been renewed interest the last week or so.

    Michael
    ...I love the French language...especially to curse with...Nom de Dieu de putain de bordel de merde de saloperies de connards d'enculés de ta mère. You see, it's like wiping your *** with silk, I love it.

  3. #3
    FLAC W3bMa5t3r's Avatar
    Join Date
    Apr 2006
    Location
    Washington, DC
    Posts
    1,268
    Quote Originally Posted by Wiredwrx View Post
    Definitely head over Adding POI's in iGuidance??? and post your findings.

    Check out the last couple of pages, there has been renewed interest the last week or so.

    Michael
    This is the coder that thankfully took this challenge on.

    @ pstickne Glad to see you made it here bro. A POI editor for all is just what we were hoping for I've never done any hacking/decoding, but if there's anything I can do to help let me know (looking up POIs or whatever) lol. I usually have plenty of free time so it's something I can pick up... I can try my hand at the decoding...

Similar Threads

  1. Archive
    By Bitoholic in forum Mobile Media Center
    Replies: 2358
    Last Post: 09-21-2006, 06:59 PM
  2. Unknown map file format
    By tomelee in forum Map Monkey
    Replies: 11
    Last Post: 11-20-2005, 02:20 AM
  3. Poi DAT Format
    By garo in forum Map Monkey
    Replies: 7
    Last Post: 07-06-2005, 06:19 AM
  4. Replies: 3
    Last Post: 04-18-2005, 03:44 AM
  5. Replies: 6
    Last Post: 02-22-2005, 02:11 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •