*NOW FIXED* Heading Errors in the MIO Camera Database

Andy_P · Posted: Fri Jun 22, 2007 10:29 pm Post subject:

Thanks for the full description Trevor.

I realised that with a bit of hard work it wouldn't be difficult to correct entries where the error was slight, but was curious about all the others which either have no info at all (i.e. set to '0') or are totally wrong (as in your '180' on an E-W road example).

Now I know those are going in a separate 'un-decided' file, it all makes sense.

M8TJT · Posted: Fri Jun 22, 2007 10:42 pm Post subject:

Ain't I lucky not having anything better to do?
Trevor

Andy. I'll talk to MaFt about the awkward ones. Perhaps it would be better just to take the direction data out so they become 'omni'. Also, I only intend to do the ones that already have direction data allocated. 11,000 cams is just toooooooooo much to tackle.

(Good this edit button, isn't it?)
T

Andy_P · Posted: Fri Jun 22, 2007 11:02 pm Post subject:

Just as a daft thought... How does the Mio cope with a heading that REALLY IS 0 degrees? Would you have to call it something like '1' degree to stop it being registered as an omni?

M8TJT · Posted: Fri Jun 22, 2007 11:15 pm Post subject:

Not sure. I'll check it out and report back. I suspect that it will be OK.
Just to be on the safe side, I put in eithe 001 or 359, which of course for all intents and puposes is pretty close to North, and well within the MIO's acceptance angle.

The last two columns of PGPSW database contain 'direction' and 'ways'. If these are empty, the MIO registers this as an omni not an az of zero as you imply. So to register an omni or 'not known' cam, the last two columns are left blank.
Trevor

MaFt · Posted: Fri Jun 22, 2007 11:24 pm Post subject:

Sallyann · Lifetime Member Joined: Jun 23, 2006 Posts: 768

M8TJT · Posted: Sat Jun 23, 2007 10:17 am Post subject:

Although there are no headings of zero in the PGPSW database .asc, There are a couple of 360 degs.

Sal, do you know off the top of your head what happens in the MIO with 'ways' field? Ok on 1 and 2, but what happens if it's set to zero or, say, 4 with a direction in the az column?
Trevor

Andy_P · Posted: Sat Jun 23, 2007 1:39 pm Post subject:

Do you know.... I've just realised I've been having an extended "senior moment" and all this time have been thinking about the "0" used for "unknown speed" in the camera ID names, rather than for "omni" in the directional info.

Apologies for wasting all your time (although I learnt a lot), I shall now go and sit in the corner in shame Embarassed

Sallyann · Lifetime Member Joined: Jun 23, 2006 Posts: 768

Anything other than 1 or 2 will produce an omni camera, regardless of any quoted bearing.

Sal

M8TJT · Posted: Sat Jun 23, 2007 3:11 pm Post subject:

Sal
Thanks.
So I could leave the wrong az in and set the 'ways' to 0 and this would work as an omni.
As an example of the cams that I am having probs with, have a look at the one at 52.4156N, 1.6754E. The database gives an az if 170Deg
Or the onone at 0.79613W 51.29382N with an az of 180??? More likely 90 or 270 but I suppose it could be to trap people speedding up to the junction down (180 ish) Trunk Road.
Although I suspect that the best bet with these sort is to make them omni???

Trevor

Sallyann · Lifetime Member Joined: Jun 23, 2006 Posts: 768

How are you getting on Trevor?
I'm looking forward to the results of all your work!

Sal

M8TJT · Posted: Wed Jun 27, 2007 6:07 pm Post subject:

Sally.
Did you get my email?
Iv'e done just over 1400 cams. All those South of 51N and all those East of Zero E. Have not done any for a few days now as I have been working on sorting the ones that I have done from my full list, to make an update .asc file.
I have a couple of problems. Sad

First: Your MTC builder does not seem to merge an update.asc file larger than 32K?? (Or is it me doing something wrong?) but if I rename my 58k exported .csv file of all PGPSW cams (with my changes) to .asc file, Builder works OK and my changed cams now point the right way.
Second, and looking forward, I am having problems comparing a 'new' PGPSW .asc file with my master list to find any cams that they may have updated and wondered whether it would be a big job to change Builder to do a comparison between two files, and export the differences/additions.
I'm PMing you in a couple of mins.
Trevor

Sallyann · Lifetime Member Joined: Jun 23, 2006 Posts: 768

Trevor,
No email from you, but got your PM.
It's quite possible that there is a limit on the update file size as I didn't expect it to support the sort of thing you are using it for, however you seem to have got round it OK.
I think what you are suggesting would need a new Reader program rather than a Builder, but I'm piled high with work at the moment.
Are you familar with Excel? It should be a possible to import both .ASC files into a spreadsheet and use Excel functions to compare them. Just a thought.

Sal

M8TJT · Posted: Wed Jun 27, 2007 8:46 pm Post subject:

Sal
That's exactly what I am attempting at the moment, but doing it in VBA takes forever. Still it does do it, sort of.
Trevor

M8TJT · Posted: Fri Jun 29, 2007 7:27 pm Post subject:

@Salllyann
Well actually 'for ever' is actually about 5 1/2 mins, and my coding cannot be 100% because it missed some changes. Back to the drawing board on that one then. 3 out of 10, see me, must buck up and try the comparison algorythm on a smaller database so that it don't take 5 mins to run.

Trev

	PocketGPS
	Web