new poi catergory

[andy-c1]

I was bored teh other day so made a new poi group on my tomtom ,but when i tried to view them after converting there is just an empty file ,yet if i show them up on tomtom they are there ,it's never happened to me before and it always worked ..... any ideas please
_________________
TomTom 5001

[Oldboy]

[andy-c1]

did it on my tomtom via add poi find it on the map and added poi's then wanted to open it with dump ov2 but there was nothing inside the page under notebook ,when there should have been everything i added from the tt
_________________
TomTom 5001

[andy-c1]

yep it was
_________________
TomTom 5001

[Andy_P]

I guess your last post was meant to go in the other topic about a Schools POI?

Back to your problem...
I can't remember what DumpPOI does, but you probably don't need it...
If you make the POIs on the TomTom itself, then they are automatically made into a standard ov2 file, which can be exported just by copying the file from your TomTom's map folder.
That ov2 file is already compatible with several brands of satnav, and most of the others use "csv".
You can use POI Edit to view your files and convert to csv (or several other formats too).

[Oldboy]

[Andy_P]

Is there a write up anywhere of all the ov2 "types" and the differences between them. I thought I read that TT now used "type 100", not heard of type 064H (or is that 100 in hex?!)

[Oldboy]

[Oldboy]

[pcaouolte]

So far I have seen OV2 files with the following record types in them:

0= Deleted record
1= Skipper record (defines areas containing POIs)
2= Location and text description
3= Location, Text description, Unique ID, Extra data (unknown)
4= Encoded location with no description
5= Encoded location with short numeric description
6= Encoded location with long numeric description
7= Encoded location and text description
8= Encoded location and description compressed using lookup table
9= Encoded location and description compressed using binary tree
10= Encoded location and description compressed using character translation table
12= Encoded location and description compressed using 5 bit encoding
15= Same as type 2
20= Same as type 4
21= Same as type 5
22= Same as type 6
23= Same as type 7
24= Same as type 8
25= Same as type 9
26= Same as type 10
28= Same as type 12
100= Header record with unknown content

and yes 100 decimal = 064H

[andy-c1]

I thought i should check another group i have started adding to, wimpy and all the poi's I've added there are there ,i tried manually changing my other poi and my poi's ended up way off course .......
_________________
TomTom 5001

[andy-c1]

ok i finally got them converted ..... all i need is for some kind soul to make a picture with the words "COOK" anyone .. from cook.co.uk
I've tried to make 1 but it's awful
_________________
TomTom 5001

[Andy_P]

As TT have now taken to blaming the the PGPSW speed cam files when v7 software repeatedly looses all the 'warn when near' settings, are there any plans for PGPSW to re-jig them into TT's preferred new format?

Have TT even given developers any clues about the new format? (I doubt it!)

Is anyone beavering away to make a utility to convert between the different types?

[pcaouolte]

I have yet to find anyone who has decoded the type 100 (064H) record.

If I delete the record from the POI file I can detect no difference on the tomtom.

On the tomtom, if you create a new POI category with no entries the file contains a type 100 record. If you then create another POI category it gets a type 100 record containing different data. The data does not seem to relate to the category name or the icon used for the category.

I am currently at a loss as to the purpose of this record.

[Oldboy]

We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
Have you considered making a donation towards website running costs?.
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!