Ov2proc

From OpenTom

Jump to: navigation, search
ov2proc
A filter for .ov2 files (points of interests, used by tomtom).
Properties
Developer: Markus Hoffmann
Version: 1.00  (06.01.2010)
Architecture: arm-linux, linux-intel, intel/WINDOWS
Language: C
Comment:
Dependencies
Requires: {{{requires}}}
See also: Software

Input files can be ca????.ov2, PA????.ov2, poi.dat and any user defined .ov2 file, as well as ASCII(*), geomap-file-format(*), XML (from Openstreetmap) (*). Output can be ASCII representation, again ov2 file or universal geomap-file-format.


Usage on TomTom Device:

  1. unzip ov2proc-1.xx-bin.zip and install the content on the TomTom Directory including empty folders (ov2/).
  2. Put your ov2 files into the ov2/ folder.
    1. Maybe modify bin/ov2proc-wrapper and set the parameters you want
  3. Run the TomTom device and press ov2proc icon.
  4. The output of ov2proc can be found in that folder.


Features

  • show the contents of ov2 files (ASCII)
  • extract point of interests from a specific region out of the input data
  • recalculate the interval areas
  • merge several ov2 files together
  • convert ov2 files into other formats
  • Search for POI category and name
  • output the nearest POI by given koordinates and category. (*)

Download

Installation

TomTom: put the content of the ...bin.zip file on the TomTom filesystem (including the folders).
PC/linux: Install the debian package: (double-click on it), or do a dpkg -i ov2proc_xxx.deb.
PC/WINDOWS: extract ov2proc.exe from the ov2proc-win-x.xx-x.zip. Then open a command windows (cmd) and run it from there by typing ov2proc <options> filename.ov2. Or, if you do not like to use the command window, read the readme.txt and follow the instructions given there.

Commandline options

ov2proc [OPTIONS] filename.ov2 [filename2 ...]

-h --help                  --- Usage
--intoa                    --- output content of input files in ASCII format to stdout
--category <number>        --- specify a category number (you can specify multiple category numbers each for one input file  
                               defined in the same order)
--clip lon1,lat1,lon2,lat2    --- clip the input data to window defined by lon1,lat1,lon2,lat2
--pattern <pattern>           --- specify a search pattern (including wildcards like *,?,[1..3])
--scat <category>             --- output only POIs of this category
--nearest <lon>,<lat>         --- output POIs sorted by distance to the given koordinate (*)
--radius <lon>,<lat>,<meters> --- clip output to circle around given point with radius (in meters) (*)
-o <filename>                 --- put output to file  (*)
--otyp <typ>                  --- specify the output file format: can be asc,ov2,geo (*)
-v                            --- be more verbose                                      
-q                            --- be more quiet

(*) not implemented yet.

sample output

# ov2/germany_Night_Life_and_Business.ov2 converted by ov2proc
# NUM=18385/2047 BOUNDS=[587167:1498768][4731222:5501520]
AREA 18385 [587166:1498769][4731221:5501521] {
  AREA 7111 [587166:1042883][4731221:5116371] {
    AREA 460 [673597:814788][4754302:4923789] {
      AREA 6 [730661:739959][4804270:4827193] {
        POI #12 cat=0xffff x=730662 y=4804271 name="Bank:Cr$$dit Agricole"
        POI #13 cat=0xffff x=735853 y=4807790 name="Bank:Cr$$dit Mutuel"
        POI #14 cat=0xffff x=735587 y=4807870 name="ATM:Soci$$t$$ G$$n$$rale"
        POI #17 cat=0xffff x=739958 y=4827192 name="Bank:Caisse d'Epargne"
        POI #15 cat=0xffff x=732189 y=4819426 name="Bank:Cr$$dit Agricole"
        POI #16 cat=0xffff x=731869 y=4819519 name="Bank:Cr$$dit Mutuel"
      }
      AREA 247 [753736:814519][4754302:4837475] {
        AREA 65 [753736:783606][4754807:4795818] {
          AREA 20 [755626:767769][4755271:4773244] {
            AREA 4 [761179:761599][4759209:4761555] {
              POI #0 cat=0xffff x=761180 y=4759214 name="Bank:Sparda-Bank"
              POI #40 cat=0xffff x=761186 y=4759249 name="Bank:Volksbank"
              POI #39 cat=0xffff x=761598 y=4759210 name="Bank:Sparkasse"
              POI #44 cat=0xffff x=761381 y=4761554 name="Bank:Sparkasse"
            }
    ... 

(data from openstreetmap source: [1] )

What it can not do

  • create poi.dat files
  • create/encode compressed ov2 data
  • decode undocumented ov2 chuncks.
  • convert ASCII input back into ov2 (use a2ov2.bas instead)

Limitations of use

Important: POIs from Tomtom Navigator are copyrighted and you MUST NOT use the information extracted from these files to exploit-modify-diffuse natives POIs or do anything that Tomtom licence prohibit. However, it seems that licence permit to replace native POI.DAT with your own file, based on private or free data. The situation for CAxxxx.ov2 files is less clear. Although some of the other record types are supported, you should use this program only to show the content of .ov2 files with free data content or such which you have created yourself. This progam must not be sold. Read the

Original Warning from TomTom:

 (1) No information stored in OV2 format, or extracted from files in OV2 format
   (using whatever means, tools or techniques, based upon either published or
   selfdiscovered knowledge about the OV2 format), nor any knowledge about the
   OV2 format itself, may be 
   * sold in any form, unless with written permission from the owner of the 
     original (raw) information,
   * used from within any application other than a TomTom product,
     commercial or otherwise, without explicit written permission
     from a director of either Palmtop BV or TomTom Inc, unless
     (a) that application has the sole purpose of providing
         additional functionality to TomTom Navigator or TomTom
         Citymaps, and
     (b) that application only functions on devices on which TomTom
         Navigator or TomTom Citymaps is installed, and
     (c) that application is accompanied by a warning similar to this warning.
 (2) Furthermore,
 * we will not provide support about the format, or any related tools or 
   documentation,
 * we do not guarantee correctness or completeness of the either
   the format, the tools or the documentation,
 * we hold the right to change or extend the format without notice,
 * we do not guarantee that details of future, changed or extended
 * formats will be made available,
 * we do not guarantee that future, changed or extended formats will
   be compatible with the current format,
 * we do not promise that we will allow the same things for future,
   changed or extended formats.
(3) Finally, please note that the POI data that is distributed as part of 
    TomTom products is
    (a) not in OV2 format, 
    (b) expressly not allowed to be accessed in any way whatsoever, and 
    (c) protected by international copyright laws.

Known bugs

  • add something here



Thanks to Laurent Licour for discovering the poi.dat file format. See his page: http://www.licour.com/gps/poi_format/poi_file_format.html


See also: ov2show.bas, a2ov2.bas

Personal tools