SCDB POI database

[Andy Davies]

So, I just paid my subscription and downloaded some camera locations to my 2720 and when I look at the categories I see the letters 'O' 'S' 'NW' 'SO' etc next to the category icon. Can anyone enlighten me as to what they mean?

Andy

 

[PanEuropean]

I suspect they are the abbreviations used in the German (not Garmin!) language for North, South, East and West. For example, East is 'Ost' in German.

Michael

 

[Andy Davies]

I suspect they are the abbreviations used in the German (not Garmin!) language for North, South, East and West. For example, East is 'Ost' in German.

Michael

French I can do, my lack of German is exposed. Thanks Michael.

Andy

 

[ianran]

French I can do, my lack of German is exposed. Thanks Michael.

Andy

Isnt Ouest french for west?

 

[Andy Davies]

Isnt Ouest french for west?

But its seeing it in context that gives the clue.

Andy

 

[Andy Davies]

So here's another point to note. When you have the data base loaded for UK and say France, it screws up the speeds multiplying the km by 8/5. I need to do some editing.

Does anyone know the column order for csv files and just how to get the gpsr to recognise the speed limit and warn if you're exceeding it.

Weather's great in France just now [Beaune]!

Andy

 

[PanEuropean]

So here's another point to note. When you have the data base loaded for UK and say France, it screws up the speeds multiplying the km by 8/5.

Hi Andy:

Yeah, that's a known issue. The problem is this: You have to specify at the time you upload the custom POI database whether the speeds and units of measurement are metric or imperial. Sadly, you can't have both.

The only ways to work around this are as follows:

1) You reload the custom POI's whenever you cross the English Channel, and when you are doing the reload, you specify the measurement units of the place you are going to (UK or Continent). This is what I do, but it means you need to have a laptop computer with you.

2) You need to talk with the folks who are constructing your database, and ensure that they use the same measurement units (metric or imperial) for the whole darn custom POI database. It's fine to have speed cameras loaded in with the trigger points specified in km/h, and have the GPSR set to display MPH - in such a case, the GPSR will do the conversion from km/h to MPH, and warn you at the appropriate speed. If you had such a database, then you would specify that it was constructed with metric units when you upload it using POI Loader.

The root cause of the problem is that the folks who create the custom POI databases mix units of measurement in the database - they list UK speed cameras with MPH trigger points, and Continental speed cameras with km/h trigger points. This forces you to follow procedure 1), above.

Michael

 

[Andy Davies]

Hi Andy:

Yeah, that's a known issue. The problem is this: You have to specify at the time you upload the custom POI database whether the speeds and units of measurement are metric or imperial. Sadly, you can't have both.

The only ways to work around this are as follows:

1) You reload the custom POI's whenever you cross the English Channel, and when you are doing the reload, you specify the measurement units of the place you are going to (UK or Continent). This is what I do, but it means you need to have a laptop computer with you.

2) You need to talk with the folks who are constructing your database, and ensure that they use the same measurement units (metric or imperial) for the whole darn custom POI database. It's fine to have speed cameras loaded in with the trigger points specified in km/h, and have the GPSR set to display MPH - in such a case, the GPSR will do the conversion from km/h to MPH, and warn you at the appropriate speed. If you had such a database, then you would specify that it was constructed with metric units when you upload it using POI Loader.

The root cause of the problem is that the folks who create the custom POI databases mix units of measurement in the database - they list UK speed cameras with MPH trigger points, and Continental speed cameras with km/h trigger points. This forces you to follow procedure 1), above.

Michael

Fortunately, I did have a computer with me (although to take work away with me whilst on holiday is not the ideal!). To keep the data base workable in both units, I renamed the Km speed camera groups as 'speed_(km*5/8)'. On the way back to Zeebrugge from Burgundy the camera warnings were triggered correctly (although perhaps with some rounding errors to the extent of 109kmh instead of 110 - but I can live with that).

So FYI that's a work around if you cannot take a laptop with you!

Michael, another question. As I was pretty loaded coming back with the car and family, I was behaving and staying below the limits. However, I would like to check the warning for excess speed. When simulating a route, how do you get the GPSR to exceed the limits? I am assuming that the speed warnings are flagged as you illustrated in your 2820 report.

From (for once) a very sunny Argyll.

Andy

 

[PanEuropean]

Hi Andy:

I don't think you can vary the speed that the GPSR simulates driving a route at. To the best of my knowledge, the GPSR looks at the cartographic database and chooses the speed to use for simulation from one of these two sources: 1) The road speed attribute for that road, if it is present, or; 2) The speed attribute for that class of road, if no actual speed limit is present.

Michael

 

[ianran]

But its seeing it in context that gives the clue.

Andy

My context was the Mary Poppins float in disneyland France!!!!!!