TomTom One 3rd Edition Custom POI error

VintageRifle · Occasional Visitor Joined: Dec 16, 2007 Posts: 4

Hello,

I have been working on a custom POI database for use on my TomTom One 3rd Edition. TomTom version 7.163

Everything started out just fine and was correct until I added a few more POIs to the data file. I now have a category with with red square, a "." before the name, and no POI found when selected.

Name looks like this after the red square: .Shooting Ranges

I also have the complete category, with custom icon, and all POIs included.

What have I messed up and how can I fix it?

Thank you for your help.

PaulB2005 · Posted: Sun Dec 16, 2007 5:39 pm Post subject:

What is the name of the POI file?

Oldboy

VintageRifle · Occasional Visitor Joined: Dec 16, 2007 Posts: 4

The .ov2 file name is Shooting_Ranges.ov2
The .bmp file is Shooting_Ranges.bmp

I cannot find any other files that start with a dot.

Contents of the USA_and_Canada Folder:

cline.dat
faces.dat
Fire_stations.ov2
Fire_stations.bmp
USA_and_Canada.pna
Shooting_Ranges.ov2
DeletedPoi.local
poi.dat
School.bmp
School.ov2
tables.dat
traffic.inc
USA_and_Canada-5.meta
Toledo_Zoo.bmp
tmccodes.dat
traffic.dat
MapSettings.cfg
MapUserPatch.dat
cname.dat
mapinfo.dat
Playing field.ov2
Shooting_Ranges.bmp
Playing field.bmp
USA_and_Canada-5.meta.dct
cnode.dat
Toledo_Zoo.ov2

PaulB2005 · Posted: Sun Dec 16, 2007 7:48 pm Post subject:

I suggest single click on each file, hit F2 and retype the name of each file to make sure there are no extra "." any where.

Won't hurt or take 10 seconds to try.....

VintageRifle · Occasional Visitor Joined: Dec 16, 2007 Posts: 4

When I remove the Shooting_Ranges.ov2 file and the Shooting_Ranges.bmp file, the red dot fantom file also goes away. Seems there is an error in the written file that ghosts a second empty .ov2 file.

Oldboy · Posted: Sun Dec 16, 2007 11:48 pm Post subject:

In Windows Explorer, Tools, Folder Options, View, make sure that Hide Extensions for known File Types is UN-Ticked.

Also select Show hidden Files.

To Windows a "." has special significance in the Folder hierarchy. Whether it has in Linux I don't know.
_________________
Richard

TT 910 V7.903: Europe Map v1045
TT Via 135 App 12.075: Europe Map v1120

VintageRifle · Occasional Visitor Joined: Dec 16, 2007 Posts: 4

Did not find any odd file names. I ran the .ov2 file through another editor and saved it. Took care of the problem. Not sure what was up with the error to begin with.

dmunsil · Occasional Visitor Joined: Jan 10, 2008 Posts: 4

I'm seeing this same issue, or rather someone else is seeing this issue on their One XL with OV2/BMP files that work fine on my Go 510.

When he installs the OV2 files, he gets bogus categories listed with a period in front of their names, and a red square for the icon. And when he selects the categories, it says something like "No POIs found!"

On my 510, everything works tickety-boo. I'm currently working through testing the following hypotheses:

- One of the POI uses a character than the One XL doesn't like
- One of the POI has a name that's too long
- The file name itself has a character the One XL doesn't like
- The BMP files aren't in a format the One XL likes

Anyone else have an idea?

If you want to try the files yourselves (they're POI for the Walt Disney World area), they're on this page:

http://www.mousesavers.com/gps.html

Or here's the direct link to the zip file of OV2/BMPs:

http://www.mousesavers.com/MouseSavers_TomTom.zip

Again, these exact files work fine on a Go 510.

Don Munsil

strik · Occasional Visitor Joined: Jan 11, 2008 Posts: 1

Ha ha... Hey dmunsil, to quote from a Disney line, its a small small world.
I'm 99.9999% sure I'm the fellow who's having the problem you've been trying to help. I've been Googling around for a solution and came across this thread. Still no luck.

A couple notes:

I've tried multiple POI files from various sources and I always get the problem. I get a "." then a space then the name. When I select it, I get "No POI found!"

I've tried hitting the reset button

I've tried doing a hard reset

When I look at the files, on my computer, they look ok. They don't have the "." or anything.

Would love to get a suggestion, or maybe I have to exchange this one at BestBuy?

Andy_P · Posted: Fri Jan 11, 2008 2:45 am Post subject:

This sounds like it might be connected to TomTom stupidly changing the format of their own POI files (to "type 100").
Try opening your problem ov2 files in POI Edit and then resaving. No promises, but it might help.

dmunsil · Occasional Visitor Joined: Jan 10, 2008 Posts: 4

I tried that - the original files had been generated with MakeOV2 (v. 1.1), as it seemed like the safest bet. I tried regenerating the files from scratch using POIEdit, and the same problem occurred.

Since then he's tried downloading some other OV2 files from tomtomforums.com, and had the same issue. It's possible there's something wrong with his unit, but I'm continuing to explore other possibilities. If someone else with a One XL gets it working, then that would suggest that it's just his unit, but for now I only have two data points - mine and his.

Thanks much for the suggestion!

Don

GerryC · Posted: Fri Jan 11, 2008 4:06 pm Post subject:

Andy_P · Posted: Fri Jan 11, 2008 4:32 pm Post subject:

dmunsil · Occasional Visitor Joined: Jan 10, 2008 Posts: 4

Kind of off-topic, but actually, you can create a file that begins with "." in Windows, at least since Win95. Explorer (the main Windows shell) will stop you from doing it, but using a command window or another program there's no problem.

Just open a command window and type something like "notepad .foobar". It'll ask you if you want to create a file ".foobar". Hit "Yes", select save, then quit. Back at the command window, type "dir" and there's the file. It's hidden from explorer windows, even if you have "show hidden files" turned on, which is interesting.

As to this problem, FWIW my current thinking is that it's caused because Strik is using a Mac, and it's saving both the main file and a hidden "resource" file that begins with "._". Macintosh files have a data fork and a resource fork, and on non-Mac formatted disk drives and SD cards it has to store two files to get both forks.

If that's true, then either he needs to use a low-level file manager to copy the files over, or he needs to delete the extraneous "._" files after copying the files over, or figure out a way to get the Mac to suppress the extra files for files of type OV2, because it doesn't do this behavior for every file type, it appears. If it "knows" the file type doesn't need a resource fork, it doesn't bother creating one. How that happens, I don't know.

I remember dealing with this problem years ago on a mixed network of Macs and PCs, but that was like 1991, and I haven't seriously used a Mac since around '94.

Don

	PocketGPS
	Web