Home PageFacebookRSS News Feed
PocketGPS
Web
Read the current newsletter! Weekly
Newsletter
SatNav,GPS,Navigation
Pocket GPS World - SatNavs | GPS | Speed Cameras: Forums

Pocket GPS World :: View topic - Garmin CSV to GPX Converter
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in for private messagesLog in for private messages   Log inLog in 

Garmin CSV to GPX Converter
Goto page Previous  1, 2, 3 ... 17, 18, 19 ... 70, 71, 72  Next
 
Post new topic   Reply to topic    Pocket GPS World Forum Index -> Garmin Portable Navigation Devices
View previous topic :: View next topic  
Author Message
Kremmen
Pocket GPS Verifier
Pocket GPS Verifier


Joined: Mar 03, 2006
Posts: 6665
Location: West London & Reading

PostPosted: Fri Oct 16, 2015 7:04 am    Post subject: Reply with quote

Opinions wanted.

The way the Garmin works is that it uses the @xx (xx=30,40,50,etc) text in the description field to produce the continual warnings or not to produce any warning if it deems you don't need one.

Currently, by using the alternative test field(s) this replaces the current text with whatever you choose at the time of processing. Because of this it has to ignore the Overspeed column or you would get 2 back to back approach warnings for every camera, and, it stops the RedSpeed conversion because by the time it assesses the text it's already been changed away from 'Gatso'.

Would it be acceptable to move the alternative text feature to a standalone process that is run manually after the normal process has completed or leave it as is with the limitations?
_________________
Satnav:
Garmin DS61 LMT-D (In the car)
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Back to top
View user's profile Send private message
Allan_whoops
Frequent Visitor


Joined: Feb 18, 2006
Posts: 369

PostPosted: Fri Oct 16, 2015 7:31 am    Post subject: Reply with quote

If I understand it correctly, moving it to a manual process allows the overspeed function to be back to a single warning. If so, then I would welcome that.
Back to top
View user's profile Send private message
Kremmen
Pocket GPS Verifier
Pocket GPS Verifier


Joined: Mar 03, 2006
Posts: 6665
Location: West London & Reading

PostPosted: Fri Oct 16, 2015 8:50 am    Post subject: Reply with quote

Sort of.....

The approach and overspeed function relies on me writing 2 almost identical lines in the gpx files.

At the moment that is one line that contains Gatso10#50 and the other contains [email protected]

The # line forces the approach warning to always occur.
The @ line will continually produce a warning from the time distance you set if you are on or over the camera limit.

To keep the 2 separate functions I would need to retain the @50, or whatever speed in the overspeed line.

So if you opted for Fixed Camera to replace Gatso then the line would have to include Fixed [email protected] That will be subject to the Garmin allowing a space. May have to be FixedCamera subject to testing.

Because the Merc needs it all to be alpha characters I need to introduce some options.

Hope that lot makes sense Smile
_________________
Satnav:
Garmin DS61 LMT-D (In the car)
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Back to top
View user's profile Send private message
Nemesis1
Regular Visitor


Joined: Aug 24, 2005
Posts: 169

PostPosted: Fri Oct 16, 2015 7:59 pm    Post subject: Reply with quote

Makes sense to me mate.
And could work even better for us in Mercs. I found after much testing (as you know as you contributed and helped me greatly) I found that the best results alert wise are proximity only. Any kind of speed sensitive alert in the Mercedes is very hit and miss. I used to spend hours manually editing the files at each release, carefully removing all numbers and speed info and inputting a proximity only parameter.

I then made a decision to use your program, and the enhancements you have made have made my life so much easier. If another enhancement stand alone or not, make it possible to further replicate the heavily edited files I had a relative success rate with, that would be awesome.

I currently work with no on screen icons, these are suppressed by Mercedes, and an approximate 80-85% hit rate for alerts. Even given your programs various settings to force an alert, these have no affect for me. Absolutely not the fault of your software Kremnen, Garmin have repeatedly confirmed that Mercedes specifically requested the suppression of many of the Garmin functions.

:-)
Back to top
View user's profile Send private message Visit poster's website
Kremmen
Pocket GPS Verifier
Pocket GPS Verifier


Joined: Mar 03, 2006
Posts: 6665
Location: West London & Reading

PostPosted: Sat Oct 17, 2015 4:42 am    Post subject: Reply with quote

Ta

The routine to replace the text is a bit cumbersome and restricted by doing it during processing.

What I'll do is take the processing bit back to what it was and then work on the text change screen to have a few more options to really customise what is output. That will allow the recent RedSpeed to be allowed.

All it will do is open each gpx file and make the requested changes. There will still need to be some restrictions like if you remove the @50 then duplicate approach and overspeed lines in that file will have to be removed.

I'll get started next week.
_________________
Satnav:
Garmin DS61 LMT-D (In the car)
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Back to top
View user's profile Send private message
Kremmen
Pocket GPS Verifier
Pocket GPS Verifier


Joined: Mar 03, 2006
Posts: 6665
Location: West London & Reading

PostPosted: Mon Oct 19, 2015 10:00 am    Post subject: Reply with quote

Have I missed anything?



The yellow fields are where you enter your option and the blue fields are the result. The result is changed dynamically.
I've included 2 examples where I've changed the test.

Final job, if I haven't missed anything is the write the processing routine.
_________________
Satnav:
Garmin DS61 LMT-D (In the car)
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3


Last edited by Kremmen on Mon Jul 03, 2017 7:40 am; edited 1 time in total
Back to top
View user's profile Send private message
M8TJT
The Other Tired Old Man
The Other Tired Old Man


Joined: Apr 04, 2006
Posts: 10118
Location: Bexhill, South Sussex, UK

PostPosted: Mon Oct 19, 2015 11:57 am    Post subject: Reply with quote

Hi kremmen. I find the overspeed information a bit difficult to get my head around as to what exactly does or doesn't happen if you change the text. It's probably because I don't realise the significance of the # and @ symbol. A bit more explanation would help I feel.
Back to top
View user's profile Send private message
Kremmen
Pocket GPS Verifier
Pocket GPS Verifier


Joined: Mar 03, 2006
Posts: 6665
Location: West London & Reading

PostPosted: Mon Oct 19, 2015 2:16 pm    Post subject: Reply with quote

The OverSpeed function needs to have a @50 (or whatever speed) symbol in the text field of the GPX file.

If that is removed then that line will be treated by Garmin as a mandatory warning so the overspeed functionality will be lost and both limits (Approach and OverSpeed) will both produce a warning.

So changing the text to say 'Fixed Camera - Fifty Mph' in both existing lines would produce 2 warnings, always.

For them both to work as intended you would need one of the lines to be 'Fixed [email protected]'

Can be done if all that is required to be changed is 'Gatso', 'Specs', etc.

If it's any consolation, I know what I mean Smile
_________________
Satnav:
Garmin DS61 LMT-D (In the car)
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Back to top
View user's profile Send private message
M8TJT
The Other Tired Old Man
The Other Tired Old Man


Joined: Apr 04, 2006
Posts: 10118
Location: Bexhill, South Sussex, UK

PostPosted: Mon Oct 19, 2015 6:33 pm    Post subject: Reply with quote

I'm pleased about that.
Back to top
View user's profile Send private message
Kremmen
Pocket GPS Verifier
Pocket GPS Verifier


Joined: Mar 03, 2006
Posts: 6665
Location: West London & Reading

PostPosted: Mon Oct 19, 2015 6:47 pm    Post subject: Reply with quote

It all circulates around the reports we used to get about cameras we know that are in the database but not being reported by the Garmin.

Garmin uses to @30 @40 @50 etc to check against the GPS speed to make this decision.
Having a line without the @xx forces its hand.

By allowing a text change this will more than likely remove the @xx so a second possibly unwanted warning will be produced.

By definition I should only be delivering an overspeed warning when you are.
_________________
Satnav:
Garmin DS61 LMT-D (In the car)
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Back to top
View user's profile Send private message
Nemesis1
Regular Visitor


Joined: Aug 24, 2005
Posts: 169

PostPosted: Tue Oct 20, 2015 9:28 pm    Post subject: Reply with quote

Could the overspeed be made to work against a number in the file name?
If there are no number against an individual entry in a file, but the file itself is called xxx_20 Garmin sets every entry in that file to 20 I believe?

Just a thought mate, I know nothing of how it would all work but that just popped in my head. I remember experimenting with all this while trying to get mine working even a little bit. Numbers in file names don't seem to mess it up like numbers in the description field does in the Mercedes system.

:-)
Back to top
View user's profile Send private message Visit poster's website
Kremmen
Pocket GPS Verifier
Pocket GPS Verifier


Joined: Mar 03, 2006
Posts: 6665
Location: West London & Reading

PostPosted: Wed Oct 21, 2015 4:49 am    Post subject: Reply with quote

Ta for the feedback.

That is exactly what I've had to do in the latest, in testing, version with the Redlight file as there is no speed in the filename. The new version uses this where previous versions ignored it. Unlike the other files though Garmin uses the keyword 'Redlight' to make its decisions so the character within the fiie is the # throughout.

The problem is that Garmin gets its instructions from the data in the .gpx file as there is no overriding 'number' in the filename. In your case where you can't have internal numbers you're scuppered because Garmin needs it.

If you have say a 15 second approach and a 5 second overspeed, both just containing alpha characters and no say @50 then you will always get a warning at 15 and 5 seconds from the camera. With an overspeed containing the @ symbol, if you have slowed down (on a Garmin PND) then you will not normally get the overspeed warning which is ideal.

On the latest version I have changed the wording of the top screen warning, plus I am not ignoring the overspeed setting. What it does now is just say that if you do set an overspeed time with an alpha character warning prompt then you will get 2 warnings. You will have to let me know how it goes when you get it.

The new version, not published yet, does give you more options. I'm sure once released you will see how it goes.
Because the warning banner text is now a separate process it's easier to enhance.
_________________
Satnav:
Garmin DS61 LMT-D (In the car)
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Back to top
View user's profile Send private message
M8TJT
The Other Tired Old Man
The Other Tired Old Man


Joined: Apr 04, 2006
Posts: 10118
Location: Bexhill, South Sussex, UK

PostPosted: Mon Nov 16, 2015 8:49 pm    Post subject: Reply with quote

Your link on page 1 is broken Kremmen. Since you re-organised I guess.
(I was loooking for a link to D/L sox.exe. and I know it's in your converter)
Back to top
View user's profile Send private message
Kremmen
Pocket GPS Verifier
Pocket GPS Verifier


Joined: Mar 03, 2006
Posts: 6665
Location: West London & Reading

PostPosted: Tue Nov 17, 2015 5:28 am    Post subject: Reply with quote

Ta

I'll sort that this morning.

(Just checking you were on the ball)
_________________
Satnav:
Garmin DS61 LMT-D (In the car)
Garmin 2599 LMT-D (Indoor test rig)
DashCam:
Viofo A119 V3
Back to top
View user's profile Send private message
tankerman10
Lifetime Member


Joined: Feb 28, 2006
Posts: 23

PostPosted: Fri Dec 04, 2015 7:17 pm    Post subject: Reply with quote

Thanks for all your hard work, Kremmen.

I've just been playing with the converter and getting it set up. It's mostly working OK but there are no warnings for the variable speed cameras on the M42, although the gatso_var.gpx/bmp/wav files appear in the file list. The warnings, icons etc appear if I use Ash10 Camera Manager.

Any idea what I might be doing wrong?
Back to top
View user's profile Send private message







Posted: Today    Post subject: Pocket GPS Advertising

Back to top
Display posts from previous:   
Post new topic   Reply to topic    Pocket GPS World Forum Index -> Garmin Portable Navigation Devices All times are GMT + 1 Hour
Goto page Previous  1, 2, 3 ... 17, 18, 19 ... 70, 71, 72  Next
Page 18 of 72

 
Jump to:  
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

Powered by phpBB 2.0.11 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003 http://www.nukecops.com

Make a Donation



CamerAlert Database

Click here for the PocketGPSWorld.com Speed Camera Database

Download Speed Camera Database
20.064 (22 Jun 22)



WORLDWIDE SPEED CAMERA SPOTTERS WANTED!

Click here to submit camera positions to the PocketGPSWorld.com Speed Camera Database


12mth Subscriber memberships awarded every week for verified new camera reports!

Submit Speed Camera Locations Now


CamerAlert Apps



iOS QR Code






Android QR Code







Terms & Privacy


GPS Shopping