Hi! We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
But as we’re losing ad-revenue from this then why not make 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!
1. removed all the gpi files in the POI folder (Garmin ones had been renamed to oldgpi, but I have now moved them to my PC).
2. searched for any gpi files in internal storage - none found.
3. checked a number of gpx files with Notepad and searched for an "@" - none found.
4. loaded to garmin via POI loader.
5. Proximity Alerts / Audio - set to single tone
6. Proximity Alerts / Alerts - Custom POIs ticked
Down to Portsmouth tomorrow, so will see how it goes.
Joined: Mar 03, 2006 Posts: 7056 Location: Reading
Posted: Sat Feb 27, 2016 6:31 am Post subject:
If you only have a single camera .gpi and only one entry per camera like my first screenshot then that is correct.
One other thing that I've just remembered. When you run the converter, note the total number of cameras processed/written. Then compare this to the number POILoader says it has loaded.
POILoader also looks in subfolders and can load double cameras. I found this out ages ago when I had a CSV set in a sub folder to my Working Folder.
If you process the whole kit and caboodle then the total number of individual cameras is approaching 20,000. If POILoader reports a greater number...... _________________ Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
Joined: Mar 03, 2006 Posts: 7056 Location: Reading
Posted: Sat Feb 27, 2016 11:17 am Post subject:
That 19,000+ is based on the CameraManager3 files that I'm currently working on with Dales.
The Speed Zoned set could be configured differently.
I'll double check Monday when I'm at the PC that it isn't 15,995 and I'm going senile.
The Converter certainly sweeps up all files, that's been tested to destruction, so it's probably me. _________________ Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
On the trip to Portsmouth & back I ended up still getting 2 warnings if I was overspeed, the 2nd virtually straight after the 1st.
Today I removed the gpi file from the Garmin & had no speed cameras, so do not have any extra speed camera files on the device.
Looking at the files after using the "CSV to GPX Converter", I noticed there were a number of .prev files. No idea what these are, but when I looked at the contents in Notepad it looked like this:-
Joined: May 04, 2008 Posts: 752 Location: Knaresborough, North Yorkshire.
Posted: Sun Feb 28, 2016 10:52 pm Post subject:
Could you, by any chance, have ended up with a .gpi file on your device's SD card as well as in internal storage?
The .prev files are perfectly normal and cannot cause duplicate warnings (they are the previous csv files which the converter has now processed to gpx. They are renamed so that PoiLoader cannot read them).
If you have loaded the correct number of cameras, according to PoiLoader, then the fault cannot lie in the files on your PC. That is why I suspect there are old files still on the device or SD card.
I have not used an SD card, and could not find any other .gpi files on the Garmin. When I removed the gpi file with the speed cameras, nothing appeared on the device whilst I was driving.
I found something called current.gpx. Not sure what that is for?
Joined: May 04, 2008 Posts: 752 Location: Knaresborough, North Yorkshire.
Posted: Mon Feb 29, 2016 1:16 am Post subject:
Current.gpx is just a record of your Favourites and your stored routes and tracklogs of where you have been. It is just passive information, and it doesn't generate any warnings.
I'm stuck for what to say now, if your load and data and settings are correct.
Joined: Mar 03, 2006 Posts: 7056 Location: Reading
Posted: Mon Feb 29, 2016 6:24 am Post subject:
I can see exactly what that is........
Those cameras with the @ symbol are not the result of the setup you had in the picture you posted.
The @ symbol will indeed prompt the Garmin to keep on producing warnings if you are overspeed.
With the Overspeed column set to all zeros, as per your screendump, the symbol in the gpx files should be a # not a @. Just having the single @ is the result of having the approach column set to zeros and the Overspeed column having a value.
The program always saves your current options when it exits.
The .prev file is a facility that ties in with the top menu option to see camera changes. Once clicked the program will create a new csv file that can be loaded into Mappoint and will display where all the new cameras are.
I will probably remove that, if no one uses it, because I never use it and it does cause confusion. _________________ Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
Joined: Mar 03, 2006 Posts: 7056 Location: Reading
Posted: Tue Mar 01, 2016 5:40 am Post subject:
Only 1 warning, regardless of speed, is what it does for me, and what it should do.
I need to double check that gpx output because I wasn't aware that the xsd reference was on each line. May be correct, I'll check the schema requirements.
I worked on the Converter yesterday as I'm linking it to the CameraManager3 fileset. I've removed the .prev facility as it is causing confusion. The next release won't have the 'New Cameras' option. _________________ Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
Joined: Mar 03, 2006 Posts: 7056 Location: Reading
Posted: Tue Mar 01, 2016 11:38 am Post subject:
Oh
I didn't think anyone used the prev files. I haven't used them for a few years now. I've made some changes this morning to be more compatible with the CameraManager files and I removed the prev files option.
I used to get quite a few PM's about them wondering what they were for and could I provide an option not to create them. _________________ Satnav:
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Car Average MPG :
Posted: Today Post subject: Pocket GPS Advertising
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!
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
Or you could disable your ad-blocker for this site. We think you’ll find our adverts are not overbearing!
Hi! We see you’re using an ad-blocker. We’re fine with that and won’t stop you visiting the site.
But as we’re losing ad-revenue from this then why not make 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!