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!
Joined: Aug 31, 2005 Posts: 15218 Location: Bradford, West Yorkshire
Posted: Mon Dec 16, 2019 4:49 pm Post subject:
Leo_A wrote:
MaFt wrote:
Kremmen wrote:
For those now using Speedtrap Alert on a Samsung .... replace Samsung TTS with Google TTS. Text To Speech.
It produces a proper, not robotized, voice and is louder.
@MaFt, would it be feasible to produce a bespoke iGo based database with an additional column for start, middle and end Specs ?
If you give me the specifications that the app needs then yes - I can. I can even call it 'Speedtrap' instead of iGO too to avoid confusion
Hi, I'm a developer. It would be great.
Specification for first test is simple:
SPEC start and middle - type 100010 (instead of default 4)
SPEC end - type 100011 (instead of default 4)
That's all.
For first test it is enough just to generate the text file. I'll test it and if everything is ok, then to include it to download page.
OK, so to clarify, for this camera:
SPECS:202920 (END) the app would need
-0.49636,51.49468,100011,50,1,269 (replacing the type '4' to '100011'?)
Is there a way to include the camera name/ID for reference in there? (the SPECS 100011)
I assume you're using the same headers as iGO: X,Y,Type,Speed,DirType,Direction
What are the IDs for the other camera types - do you use the iGO values:
REDSPEED = 2
REDLIGHT = 3
SPECS / average = 4
MOBILE = 5
Gatso / truvelo (fixed camera) = 1
OK, so to clarify, for this camera:
SPECS:202920 (END) the app would need
-0.49636,51.49468,100011,50,1,269 (replacing the type '4' to '100011'?)
Yes, exactly
What are the IDs for the other camera types - do you use the iGO values:
REDSPEED = 2
REDLIGHT = 3
SPECS / average = 4
MOBILE = 5
Gatso / truvelo (fixed camera) = 1
Yes.
[i]Is there a way to include the camera name/ID for reference in there? (the SPECS 100011)[i]
Yes, there are two variants: GUID taken into figure brackets and text. If identifier presents, it goes first. Examples:
123456,4.066639,46.05067,2,0,2,65 // text representing integer number
AAB00123,4.066639,46.05067,2,0,2,65 // text representing some text
"//" - comment is possible.
Limitations for text identifiers: no quotations "" or '', no commas. Ideally, only alphanumeric characters.
In its current version the app can perform some meaningful actions only with GUID identifiers. Under meaningful actions I mean : liking (confirming) and disliking when passing a camera, reporting cameras and dangers in real time, receiving real time cameras, sending feedback and comments for a point selected on the map. This is possible because GUID guarantees global uniqueness across the world and I can collect and store all these data in one database without a risk of duplicated identifiers.
Support of text identifiers currently means only that app parser accepts an extra first member in the line. Text identifier is stored internally together with Lon, Lat, Speed, etc, and can be sent over the internet somewhere, but further actions with such data are under responsibility of the receiving webserver with the risks mentioned above.
Joined: Jun 25, 2005 Posts: 802 Location: Sandy, Bedfordshire
Posted: Mon Dec 16, 2019 10:45 pm Post subject:
I have had a good test with STA in Belgium and France. The banner is loud and provocative, I certainly noticed it I don't have a problem with the voice, it sounds like the one I have already. What was handy this weekend was the speedo. On arrival in France, I noticed the car only has speed in mph, so it was good to have a big digital kmh display. They don't seem to have specs over there, so I can't comment (and I don't understand all the ongoing conversation )
I am thinking more data is going to be used now though as I only use CA in list mode. _________________ Garmin Drivesmart 51 LMT-D Europe
......They don't seem to have specs over there....
Be careful, marksfish, they do, loads of them in fact. There's an example at 43.4952,4.96578 SPECS:184312, near Marseille. _________________ Garmin Nuvi 2599
Android with CamerAlert, OsmAnd+, Waze & TT Europe.
TomTom GO 730, GO 930, GO 940 & Rider2.
SatMap Active 10 & 20.
Joined: Jun 25, 2005 Posts: 802 Location: Sandy, Bedfordshire
Posted: Tue Dec 17, 2019 4:07 pm Post subject:
I was only skirting Dunkirk, Ypres and Bruges, so none there that affected me this weekend. Now, if it had the ability to show a banner when our militant gaelic lorry driving friends were keeping the motorway to 20kmh, I would buy it now _________________ Garmin Drivesmart 51 LMT-D Europe
Joined: Mar 03, 2006 Posts: 7099 Location: Reading
Posted: Tue Dec 17, 2019 4:12 pm Post subject:
What is a good idea is the way STA produces a warning and then produces a series of double beeps* to remind you you are still approaching a camera, finishing with a triple beep when you pass it.
*Beeps can be turned off.
I'm not so sure that this replaces a bespoke overspeed warning though ? _________________ DashCam:
Viofo A119 V3
Car Average MPG :
Joined: Apr 04, 2006 Posts: 10118 Location: Bexhill, South Sussex, UK
Posted: Tue Dec 17, 2019 4:56 pm Post subject:
But it's not an overspeed warning anyway. The beeps are a 'you are approaching a camera reminder' There is a separate overspeed warning if you care to set it.
OK, there is now a 'Speedtrap Alert' format that can be downloaded. This uses the start/mid/end for Specs.
BUT
it does not make use of the EXITSPECS catageory nor does it have the text description of the cameras.
Leo_A wrote:
Limitations for text identifiers: no quotations "" or '', no commas. Ideally, only alphanumeric characters.
Our camera names include colons would they be ok? e.g. GATSO:12345, SPECS:543 etc
Thank you a lot. Almost perfect, except several SPECS point which are not marked in the database as 'start'/'mid'/'end', although they are chained in continuous av.check zone, and therefore they go to the file as type 4. For example, SPECS:81859@50
Joined: Jun 25, 2005 Posts: 802 Location: Sandy, Bedfordshire
Posted: Tue Dec 17, 2019 7:24 pm Post subject:
I have downloaded the STA files for tomorrow as I venture up the M1 roadworks, to see what happens. How are the databases updated? I downloaded the new STA files to my phone and hit the update databases, but nothing happened. I had to manually remove the old files and manually add the new ones, is that right? If so, what is the update databases link for? _________________ Garmin Drivesmart 51 LMT-D Europe
Joined: Mar 03, 2006 Posts: 7099 Location: Reading
Posted: Tue Dec 17, 2019 7:34 pm Post subject:
That update menu option may be for the other databases Leo supports.
Robert has suggested a link and that option would be perfect.
As it stands it's a manual download then use the + option to search and add the new .txt file, then set the slider to off on the old one or remove it. _________________ 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!