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!
Posted: Sat Mar 25, 2017 4:02 pm Post subject: mivue 638 658 - Data to feed converter utility
I've a Mivue 658 gps camera with camera alerts, but the database they supply only has fixed ones. So these (otherwise great) units are chocolate tea-pots as far as speed cameras are concerned. The format for the unit looks like a bespoke ".bin" format but they created a converter utility for the Russian market !!
Is it possible to get the following information from the speed camera database ? I can then try the Russian converter and report back whether it works.
I found the format described on another forum as follows :
Y - Y coordinate in WGS84. Snapped to the closed by road. ( -89.9°~+89.9°)
X - X coordinate in WGS84. Snapped to the closed by road. (-180°~+180°)
BEARING ANGLE - Driving direction of the targeted car. 0 for north, 90 for east, 180 for south, 270 for west. (0°~359°)
SPEED RESTRICTION - Speed restriction in km/h (0~180)
CAMERA TYPE
1 – a static one
2 – an implemented in traffic lights one
3 – check out of passage through red light (my lovely violation – it allows to spare more time as an exceeding of speed limit)
4 – a cam that measures speed on the whole segment of the road
5 – a mobile cam (cops ambush)
DIR TYPE
0 – all directions (360°)
1 – one direction that’s defined through “ANGLE” parameter
2 – direction that’s defined through “ANGLE” parameter and the opposite one
Version - Speed camera data version displayed on device, number only. E.g. 3 or 28
Joined: Apr 04, 2006 Posts: 10118 Location: Bexhill, South Sussex, UK
Posted: Sat Mar 25, 2017 7:20 pm Post subject:
That data is pretty much identical to the iGO format so try the IGO~UK-Single file with all cameras. That's a .CSV (or possibly .TXT, but just rename it to what your unit takes.)
Joined: Apr 04, 2006 Posts: 10118 Location: Bexhill, South Sussex, UK
Posted: Sat Mar 25, 2017 9:22 pm Post subject:
Just make a few up using the submission map to get the lat/lon. Do it in notepad and save it as a *.txt file (The download file is a .txt file, not a CSV as I said earlier)
Here's an extract from the first few entries in the iGO file. Not in your area, but enough to give you the idea.
I don't think that you will need to convert the speed int KPH, as iGO uses your regional settings and displays the number as MPH in UK, and converts it to KPH elsewhere. But I could be wrong about this on yours. But that's what happens on my iGO installations.
I'll answer my own question - yes it does work perfectly.
Curry's had the 618 on offer for £74 so took the plunge.
It does all I need at a reasonable price.
I made up some local locations as a test and created the bin file and it loaded ok and driving around the made up locations brought up the warning.
There is one adjustment that has to be made - it seems it assumes the speeds in the data are KPH so it converts them to MPH for the warnings and display so the speeds in the spreadsheet have to be converted to KPH
I'll see how the MIO database works out but I suspect I'll be subscribing to the PGPG database.
Joined: Apr 04, 2006 Posts: 10118 Location: Bexhill, South Sussex, UK
Posted: Sat Apr 08, 2017 2:37 pm Post subject:
dapjukebox wrote:
I made up some local locations as a test and created the bin file and it loaded ok and driving around the made up locations brought up the warning.
Good bit of research dapjukebox. It would be good if you could put an example or several of the data needed to run your device. If so, then it might just be possible to persuade MaFt to publish the PGPSW database in that format (unless it already does).
I made up some local locations as a test and created the bin file and it loaded ok and driving around the made up locations brought up the warning.
Good bit of research dapjukebox. It would be good if you could put an example or several of the data needed to run your device. If so, then it might just be possible to persuade MaFt to publish the PGPSW database in that format (unless it already does).
This is still a work in progress.
I have noticed that the camera type that it reports doesn't match the types listed above. All of my test locations where mobile (type 5) but they are reported as specs.
The manual seems to indicate that it can report 6 types of camera so my next test when I get the chance is to create another set of test locations with each camera being a different type.
I guess the official database uses 6 for bus lane cameras or the like although I believe it only contains fixed cameras.
The converter can produce files for the following dash cams:
388, 538, 568, 618, 636, 658, 678, 668, 688.
It may support newer ones that were released after the converter was produced.
There is a template excel spreadsheet supplied with it that is fairly self explanatory except there are some changes that are required to use camera type 6. The speed column needs to be in KPH.
If anyone wants any help using this I am more than happy to assist.
Joined: Apr 04, 2006 Posts: 10118 Location: Bexhill, South Sussex, UK
Posted: Mon Apr 10, 2017 2:00 pm Post subject:
Like I said, if you post a sample of data for a few cams, with an explanation of each field, I'm certain that MaFt can/will? create the correctly formatted file from out data.
@MaFt?????
Last edited by M8TJT on Mon Apr 10, 2017 2:04 pm; edited 1 time in total
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!