Welcome guest, is this your first visit? Click the "Create Account" button now to join.
Results 1 to 3 of 3
  1. 12th March 2022, 10:28 AM #1
    1franka
    1franka is offline
    Senior Member
    Join Date
    Aug 2014
    Location
    United Kingdom
    Posts
    143
    Rep Power
    39

    KML icon HERE map integrity

    I have been checking the integrity of my stored maps from years 2021_Q2, 2020_Q4, 2020_Q2 & 2019_Q4

    All of the above files[except WESTERN_EUROPE maps] return "checksum mismatch" errors.
    All of the WESTERN_EUROPE maps return "all files seem okay"

    However, if i check the maps for 2018_Q1/Q3/Q4 ALL maps return "all files seem okay".

    WHY????



    edit:- the maps were checked using "iGOViewer 4.1.3.48"
    Last edited by 1franka; 12th March 2022 at 10:33 AM. Reason: more information
    Reply With Quote Reply With Quote

    2.    Advertissements


  2. 12th March 2022, 10:35 AM #2
    Boki
    Boki is online now
    iGO Enthusiast HERE map integrity
     Boki's Avatar
    Join Date
    Jun 2014
    Location
    Niš
    Age
    53
    Posts
    6,981
    Rep Power
    4734

    Default

    Because the tool you use to do that is obsolete.

    New releases have slightly modified content. It's not just Here, this also applies to TT.
    iGO reads it without problems, but iGO_View reports errors.

    This has already been mentioned several times ...
    Before asking a question, know it's already discussed here and at 99.9% is not unique. Use search.
    NO ONE IS A SEER, READ (click on): [Only registered and activated users can see links. ] <- Click!
    [Only registered and activated users can see links. ] <- Click!

    Spoiler: obs
    Many questions become very arduous, a lot of time chewed deja vu...Since we have lost all the year of work and effort, many people have no will to answer the same questions again. Me neither. Use a search, please.
    Reply With Quote Reply With Quote
  3. 12th March 2022, 02:49 PM #3
    lunapark
    lunapark is offline
    Master
    Join Date
    Nov 2017
    Location
    europa
    Posts
    123
    Rep Power
    244

    Default

    mentioned several times... but never explained in detail

    In fact, the checksum is a simple md5 added to the original encrypted file, and therefore we can add as many md5s as we want at the end and make believe that the file is valid.

    igoview by assuming that on some extensions the md5 is still existing and sometimes mistakenly considers that the last 16 bytes read are an erroneous MD5,

    except for a good estimate it is necessary to analyze the beginning of the file to extract the supposed position of the end of the file.

    This value less than or equal to the size of the file, is sometimes followed by a zip archive which once eliminated allows access to the MD5 signature if the resulting value corresponds to the size of the file - 16 bytes.

    By ignoring these 16 bytes, it then becomes possible to calculate the real md5 to compare it to the existing one or possibly add it as a verification signature.

    So if igoview displays: a green flag means that the md5 corresponds to the file as long as it has not been modified upstream, a red flag will not necessarily mean that the file is corrupt.

    we have already observed aberrations of itineraries by off-road lines because the data of the file was incorrect while its structure was good.
    Reply With Quote Reply With Quote
 

 
« Previous Thread | Next Thread »

Tags for this Thread

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
  •  

Forum Rules

Powered by vBulletin
Copyright © 2025 vBulletin Solutions, Inc. All rights reserved.
Copyright © 2008-2017 GPS Power . All rights reserved
All times are GMT +1. The time now is 09:40 AM.