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: Apr 04, 2006 Posts: 10118 Location: Bexhill, South Sussex, UK
Posted: Mon Feb 04, 2013 3:04 pm Post subject:
I have just done some tests agains a couple of test fixed cams on a dual carriageway. They are definitely not directional even with a route set (as I was certain they weren't) unless the have direction data in the normal iGO .txt file. So it appears that the other database is definitely directional as per Robert's findings. Now to find out how the other database/Alpine work together to extract this data from the last col in the .txt file
Joined: May 09, 2012 Posts: 46 Location: London, Wandsworth SW17
Posted: Mon Feb 04, 2013 4:18 pm Post subject:
Andy_P wrote:
Multiple confusion here... but lets start at the beginning. You seem to hjave gone wrong right from the top when you say this:
r4robert wrote:
The iGO database has a camera in Balham High Road/junction Marius Road. Coordinates taken from the PGPSW database (Yellow "we need you") give its location as 51.44011 -0.15568.
How did you get those coordinates? 'Cos there is no camera there on our submission map.
But there is one about 130metres south of that position, at 51.43918,-0.15618 which agrees with your next statement.
As a general note, whenever entering coordinates on the submission map, make suree you put a comma between the Lat and Long and NO space. (thus - 51.43918,-0.15618)
You get some weird results if you don't stick to that rule.
You are absolutely right. Sorry, I'm the one who is in error.
We ARE talking about the same camera!
Thanks for pointing this out
-Robert _________________ "Anyone who says he can see through women is missing a lot." - Groucho Marx
Joined: Mar 03, 2006 Posts: 7007 Location: Reading
Posted: Tue Feb 05, 2013 7:40 am Post subject:
Andy_P wrote:
Kremmen wrote:
If they are directional then we need some form of simple conversion.
Isn't that what we've been trying to do for the last week or so?
I didn't phrase that very well.
Rather than trying to be clever with a mathematical solution that seems to be eluding us, I was thinking about identifying a few cameras that point NSEW and see what Alpine reckon that converts to. Then simply replace one with the other.
it shows that you can save an 'alert point' including speed and direction. I wonder if, once created, it would be possible to interrogate the data and get a proper conversion? _________________ Satnav:
Garmin DS61 LMT-D (Indoor test rig)
Garmin 2599 LMT-D (Indoor test rig 2)
DashCam:
Viofo A119 V3
it shows that you can save an 'alert point' including speed and direction. I wonder if, once created, it would be possible to interrogate the data and get a proper conversion?
The problem I have experienced is that I cannot distinguish between Alert Points and regular camera data when I download the 'Device Info' on to an SD card.
There is no separate heading "Alert Points", just the familiar
X,Y,TYPE,SPEED,DIRTYPE,DIRECTION
1.55944,42.52194,1,60,0,9b298
etc,
etc.
Unfortunately, there is no provision for connecting the 928 up to a laptop, directly
Sorry, I'm stumped. _________________ "Anyone who says he can see through women is missing a lot." - Groucho Marx
Joined: Mar 03, 2006 Posts: 7007 Location: Reading
Posted: Wed Feb 06, 2013 7:50 am Post subject:
OK
I'm still looking but why they have to be so complicated beats me _________________ Satnav:
Garmin DS61 LMT-D (Indoor test rig)
Garmin 2599 LMT-D (Indoor test rig 2)
DashCam:
Viofo A119 V3
Last edited by Kremmen on Wed Feb 06, 2013 9:58 am; edited 1 time in total
Joined: Apr 04, 2006 Posts: 10118 Location: Bexhill, South Sussex, UK
Posted: Wed Feb 06, 2013 1:24 pm Post subject:
Kremmen wrote:
I just can't figure how 36394 gets converted to something like 135°
The SCDB bog std iGO database has no directional data in it, so I have a bit of doubt in my mind whether the hex values are directioal data. Unfortunately, Robert has not got back to us to indicate whether ie SCDB Alpine database is directional on a single carriagewayor not.
Joined: Mar 03, 2006 Posts: 7007 Location: Reading
Posted: Wed Feb 06, 2013 1:44 pm Post subject:
I thought he'd said it was directional ?
Plus, the screen input of an alert point allows directional so I'm guessing it is highly coded to protect the scdb.
I suppose one way to test it would be to put the same Hex value (130e3) at the end of each record in a small sample of different points and see if the Alpine sucks it in.
Yes the directions will be 'skew-whiff' but it will confirm whether it's pure coded direction or direction and some form of checksum added to the number you first thought of. _________________ Satnav:
Garmin DS61 LMT-D (Indoor test rig)
Garmin 2599 LMT-D (Indoor test rig 2)
DashCam:
Viofo A119 V3
Joined: Apr 04, 2006 Posts: 10118 Location: Bexhill, South Sussex, UK
Posted: Wed Feb 06, 2013 2:05 pm Post subject:
Kremmen wrote:
I thought he'd said it was directional ?
He did say that it appeared to be so on the A3 dual carriageway, but has not reported back on his findings on a single carriageway
Quote:
Plus, the screen input of an alert point allows directional so I'm guessing it is highly coded to protect the scdb.
Yes, iGO is directional, and it would appear that you can enter directional stuff in the UI, but it's the Alpine device that's 'decoding' the scdb database, so it's an Alpine thing, not an scdb thing. On your bog std iGO, you can edit a speedcam and the edit screen indicates whether the cam is one way, two way or omni direction. The latter being the case if there are two zeros in the last two cols of the data.
@ Robert. Can you edit an existing cam in the Alpine UI? If it's the same as Primo, then, in the edit screen, if the cam is one way, it's shown with a red 'radar' beam or perhaps an arrow, non directional cams have a red circle around them or perhaps a four way arrow.
Quote:
I suppose one way to test it would be to put the same Hex value (130e3) at the end of each record in a small sample of different points and see if the Alpine sucks it in.
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
