Tomtom Ov2 Creater
POI converter/creator. Discussion in 'TomTom POI Requests' started by battom. And it will create an ov2 for your TomTom. After using Skux's menu creator. Welcome to Create Your Own Content - where you get the power to customise your TomTom navigation device! You can add new content to your device using the content.
Hi, I want to create some custom OV2 files for my own use only. I often use my tomtom for geocaching. I can create simple OV2 files which just contain the location and name with a number of tools but it would be really nice if I could add more information. I know it can be done as I've seen some poi files with the full address etc in them.but how can I create them? I'm no stranger to visual basic and can rewrite my source into any csv/txt/xml format but I need either the format of the new ov2 files or method to create them from a known format. Can anyone help me? Hi, Thanks very much but I knew about being able to add a phone number but I'm sure you can add more.
Here's what I think. There's a different or extended version of makeov2 that not only takes the csv file but also some other data file. If you navigate to a poi with the extended info then the 'show info' button is lit (not greyed out) and the I see a pile of other info (such as fax,email,url etc) Google has given hints about this but no program however. Hints suggest the new CSV file is in the following format: Longitude, Latitude, 'POINamePhone number POI, alternative icon, POI id and also another file which a file which contains the 'Rich' information and is basically html with a POI id header for each section. Can anyone help??
You can create your own custom waypoint OV2 file from Geody ( target='blank ). Simply enter the place or the coordinates for the spot you want to add in its search bar, then in the page with the map of the spot click on 'Add to Cart' and do the same for all the spots you want to add to your custom file. When you're done click on 'Show Cart', now you can edit manually the name of the spots if you want (if you edit names remember to click the Update button), then choose 'Tom Tom OV2' format and click on Export to download your OV2 file.
Tomtom Ov2 File Opslaan
Hi all people on this forum. I am new in this forum and hope you people can give me some hope along the way. I am working in a multi utillity company in the netherlands and we have 180 tablet pc's and 2 navigator programs called navigon and tomtom. We store and maintain our poi databases (10.000+) in an access database and every month we make navigon poi's with our tool that i make in VB. Now some people want those poi's also in tomtom and now i have again a real big challenge on how to do that. Ov2 is a weird layout to my knowledge so if anyone know it and/or how to make it with a vb app i would be very very thankfull and name this site in my app, cross my heart! Many thanx Marc Holland (the netherlands).
Click to expand.It's not all that strange unless you're talking about the POI data that comes with the TomTom. Those are in a weird compressed format. The 'custom' file is not difficult to build yourself: Each entry in a simple custom OV2 file is as follows. 1 byte: type (always 2) 4 bytes: length of this record in bytes (including the T and L fields) 4 bytes: longitude coordinate of the POI 4 bytes: latitude coordinate of the POI 13 bytes: null−terminated ASCII string specifying the name of the POI Coordinates are stored as 4−byte integers representing a WGS84 longitude or latitude, multiplied by 100.000 and rounded to the nearest integer. As such, an X−coordinate should always be a value between −18.000.000 and +18.000.000, and a Y−coordinate should be a value between −9.000.000 and +9.000.000. It's not all that strange unless you're talking about the POI data that comes with the TomTom. Those are in a weird compressed format.
The 'custom' file is not difficult to build yourself: Each entry in a simple custom OV2 file is as follows. 1 byte: type (always 2) 4 bytes: length of this record in bytes (including the T and L fields) 4 bytes: longitude coordinate of the POI 4 bytes: latitude coordinate of the POI 13 bytes: null−terminated ASCII string specifying the name of the POI Coordinates are stored as 4−byte integers representing a WGS84 longitude or latitude, multiplied by 100.000 and rounded to the nearest integer.
As such, an X−coordinate should always be a value between −18.000.000 and +18.000.000, and a Y−coordinate should be a value between −9.000.000 and +9.000.000. Hi canderson, I've found a dos exe tool called makeov2.exe. With this tool you can convert txt files to ov2 and it works great!
It also creates a default bmp file The first tool, MAKEOV2, can be used to convert a simple text file containing the coordinates and names of locations into a ready-to-use OV2 file. The second tool, DUMPOV2, can dump the content of POI databases into text format (yes, text that can be used by the MAKEOV2 tool). The use of DUMPOV2.EXE is simple and straightforward: DUMPOV2 inputfilename outputfilename Where 'inputfilename' must be a valid TomTom Navigator POI file (with extension OV2) or a valid Route Planner or Citymaps OVERLAY file (with extension OVR). It is recommended to provide an outputfilename with extension ASC. If you do not specify any parameters, all OV2 and OVR files in the current directory will be converted (but existing ASC files will not be overwritten).
The use of MAKEOV2.EXE is as follows: MAKEOV2 inputfilename outputfilename The input file should be a text file (extension ASC is recommended) that should simply contain lines of text. Any line starting with a semi-colon will be ignored. Empty lines will also be ignored. All other lines are expected to represent points of interest. Such a line should specify a longitude, a latitude and a name, seperated by commas. It is recommended that the name is put between double quotes. A name should not contain double quotes.
Longitudes and latitudes may be specified either as degrees and fractions of degrees, or in degrees, minutes and seconds. Both colons and single-quote/double-quote notation may be used for minutes and seconds. So, all the following lines are all equivalent: 53.5, 4, 'Truckers Restaurant La Bamba', 4.00000000, 'Truckers Restaurant La Bamba' 53'30'00, 4'00'00, 'Truckers Restaurant La Bamba' 53'30, 4'0, 'Truckers Restaurant La Bamba' 53:30:0, 4, 'Truckers Restaurant La Bamba'.
It's not all that strange unless you're talking about the POI data that comes with the TomTom. Those are in a weird compressed format. The 'custom' file is not difficult to build yourself: Each entry in a simple custom OV2 file is as follows. 1 byte: type (always 2) 4 bytes: length of this record in bytes (including the T and L fields) 4 bytes: longitude coordinate of the POI 4 bytes: latitude coordinate of the POI 13 bytes: null−terminated ASCII string specifying the name of the POI Coordinates are stored as 4−byte integers representing a WGS84 longitude or latitude, multiplied by 100.000 and rounded to the nearest integer. As such, an X−coordinate should always be a value between −18.000.000 and +18.000.000, and a Y−coordinate should be a value between −9.000.000 and +9.000.000. Click to expand.I was unable to get this format to work.
As far as I can tell, it loaded correctly but when I tried to use it, there were no POIs on the GPS (I could see the category though). I tried both big and small endian for the integers.
I'm digging into the Favorites I downloaded from the GPS now which appears to have a somewhat similar format but different. Most notably, the null-terminated string seems to be variable length and looks like it can be longer than 13 bytes.
Also, there is a record at the beggining that begins with a 'd'. I think that may just be the home address though. I'll post more as I find out more. Code: #!/usr/bin/perl #Written by Richard Thomas, 4-23-2015, released to public domain #Donations to: bitcoin:1CUAEudNY6YctsipTrbFNRCMbwnbAxE87R # 1 byte: type (usually 2) # 4 bytes: length of this record in bytes # 4 bytes: longitude coordinate of the POI # 4 bytes: latitude coordinate of the POI # n bytes: null.terminated ASCII string specifying the name of the POI $lat=; $lon=-84.282958; $name='Point'; $len=14+length($name); $a=pack('C V V V a. x',2,$len,int($lon.100000),int($lat.100000),$name); print $a; There seems to be some issue with the POI bitmaps on my VIA. I can't get the transparency to work (should be magenta) and the GPS seems to cache images even if you overwrite them. Could be worse though.
Tomtom Ov2 Poi Files
Edit: It appears only name and phone# are possible maybe, separated by a though I will try some other characters.