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!
I tend to agree that the directional data is not understood by this system. I'll removing column 3 entirely from all files in future, that will make things simpler
One issue I've discovered with my method, alerts always displays the camera as being 0.2 miles away when they are clearly not. This is presumably due to specifying all speeds as 20 MPH in the file name (eg "*_20"). eg 0.2Miles == 35sec at 20MPH. I've tried to solve this by installing the complete database but failed miserably to get icons to display with that.
You should be able to increase the distance by using the manual method of compiling the files in POILoader and ticking distance rather than speed for the _20 alert files.
Whats the software version before the 16/49 bit. I suspect its v8.1 which will display icons without shifting the alert positions.
Just as a matter of interest which merc do you have. My garmin is actually in my wifes car, a 2017 GLA but it wont let me update to v8.1 - crazy!
Yes I read your very informative info. from last year but I didn't notice that it solved the particular problem I was having which is with v6.0 map and v6.1 software that the alert banner read in chinese and no icons were displaying on the map.
Using the Poi shift method the icons now display and deleting the specific font files gets rid of the Chinese. The trouble is, each new version seems to change the goal posts.
Joined: Mar 03, 2006 Posts: 6664 Location: West London & Reading
Posted: Tue May 09, 2017 3:44 pm Post subject:
The 2 things that stuck out were
1) The text changes posted
2) The proximity of the alerts
Both catered for in the Converter.
What Nemesis found was that the warning banner text had to be upper case alpha characters only or the system threw a wobbly.
In my text converter routine you can change it to "GAT" or "MOB" if that's all you want. _________________ Satnav:
Garmin DS61 LMT-D (In the car)
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Joined: Apr 04, 2006 Posts: 10118 Location: Bexhill, South Sussex, UK
Posted: Tue May 09, 2017 4:21 pm Post subject:
Then I might suggest that you possibly have a chat with Kremmen to see if you can work out how to possibly adapt his programme to accommodate your particular flavour of Merc system, as he has adapted it successfully for another Merc user. And it makes converting the PGPSW files a breze for bog std. Garmins, and if you also use the direction converter before tyhe CSV converter, you get announcements saying in which direction the camera traps (If your system will allow for user audible alerts.
The business about the Merc system taking camera descriptions in ALL CAPS with the other stuff that screws it up has already been solved.
No point in re-inventing the wheel when all but the tyre tread has already been invented.
At which, I rest my case and will not clutter up your thread any more.
Joined: Mar 03, 2006 Posts: 6664 Location: West London & Reading
Posted: Tue May 09, 2017 4:37 pm Post subject:
POIloader does one simple task, it converts CSV or GPX files into a .GPI file that is standard across Garmins.
What I like to see is one sample CSV line that has been manually tweaked that has been posted as partially working. _________________ Satnav:
Garmin DS61 LMT-D (In the car)
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Joined: May 16, 2005 Posts: 86 Location: United Kingdom
Posted: Wed May 10, 2017 11:25 am Post subject:
I'm with Kremmen here. If someone could post a .csv line that is known to work that would be very useful. I've tried a couple of methods using the macros and manual conversions but as yet can't get anything to work. That's not say they won't and is more likely age related (me!) So some examples would help.
I'm on the V8 software too.
As I mentioned before I use a MAC with Open Office Calc for spreadsheets so I think the Macro's and F&R criteria are slightly different from Excel.
However, thanks to all those that are trying to get this to work!
If someone could post a .csv line that is known to work that would be very useful.
Terry
This is what has been working for me using the consolidated files and 44x44 consolidated icon files.
Icons appear as soon as any camera location enters the screen, with standard driving zoom levels, not just locations on the route.
Bong sound at around 35 seconds and again at 10 seconds before the camera.
This is one line from my GAT.csv file, the GAT_20.csv file is exactly the same just a different file name.
-2.94512 52.93073 "GAT"
The above being 3 cells of the csv spreadsheet.
I start by deleting the first line of the csv file to remove the semicolon etc, ensure it's deleted and not just a empty line.
Then delete all of column 3
Enter "GAT" in the first cell of column 3 and copy down.
Save as GAT.csv and again as GAT_20.csv all to the same folder.
Repeat for:
MOB.csv and MOB_20.csv
PMOB.csv and PMOB_20csv
RED.csv and RED_20.csv
SPEC.csv and SPEC_20.csv
Past the 44x44 bmp icon files to this folder and rename GAT.bmp, MOB.bmp etc.
Run the Garmin POILoader in "Express" mode.
Copy the the SD cards POI folder.
Note:
I'm not saying all this is essential, it's what's been working for me, it does however seem to be easier to produce a set of files which don't work than a set which do work.
Some of the things which I think will break the files:
Don't have anything in the forth scv column.
Remove the semicolon at the start of the first line.
Do use the same (GAT) name in all three files and in the third column surrounded WITH QUOTES. Same with MOB etc.
I believe all text needs to be upper case.
Extra text in column 3 has caused problems, suspect it may be a files size issue.
@xx speeds in the third column appear to break things.
Try first, without the _20csv files just process the ???.csv and ???.bmp files to check the icons show. I have had occasions were I've made a error in the _20.csv files and that's stopped the icons from showing.
Joined: Apr 04, 2006 Posts: 10118 Location: Bexhill, South Sussex, UK
Posted: Wed May 10, 2017 11:16 pm Post subject:
If you include a ???.WAV file (same filename as the ???.csv files) in the mix, does the device play the file? You will need sox.exe in the same folder as POILoader.
What is the purpose of the two .csv files as in SPEC.csv and SPEC_20.csv?
Joined: Mar 03, 2006 Posts: 6664 Location: West London & Reading
Posted: Thu May 11, 2017 5:52 am Post subject:
That is exactly the same format that is possible with the CSV Converter, if you use the text change facility before using POILoader.
However:
-2.94512 52.93073 "GAT" ?
I would expect to see
-2.94512, 52.93073, "GAT"
On the older Merc/Garmin system all that had to happen was the warning banner text changed to upper case, which is what is happening here. Ie GAT
So, is the Merc Garmin system unable to read in a .GPI file, still to Topografix schema standards created from a GPX file ?
If so then you will have to live with having the warnings 36 seconds before the camera which when I tried it was far too soon. Bespoke systems seem to aim for half that.
Once processed into GPX here is the result (with the text change applied):
I've also had to remove some HTML tags as the forum doesn't allow them.
lon="-1.94351" lat="53.07334" GAT#50
So could it be the #50 that it doesn't like ?
If someone has the time to remove that bit and report back I can sort that. _________________ Satnav:
Garmin DS61 LMT-D (In the car)
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
What is the purpose of the two .csv files as in SPEC.csv and SPEC_20.csv?
The ???.csv together with the ???.bmp files populate the screen with camera icons, regardless of whether they are on your route.
The ???_20.csv file produces the ping warning when you approach a camera location and doing 20MPH or more. As I understand it, the _20 on the end of the file name gives a global speed settings to all locations within the file -- any @speed text within the file over rides this.
@Kremmem,
I suspect it may be the @50 it doesn't like. Whenever I've tried using a speed setting within a PGPSW database file it's given problems. Having said that, I have previously used a fixed camera only database file with some success. That file was much smaller so it may be a file size thing -- who knows.
If you want me to test things with your converter, I'm happy to do so but please give clear instruction as I'm not familiar with your software.
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!
Forum FAQ
Search
Usergroups
Profile
Log in for private messages
Log in
