Hi Alex:
You are correct in your last comment, above.
There are two different issues involved in units of measurement for speed camera databases. One issue is what unit of measurement was used by the person who complied the database. The other issue is what unit of measurement you tell the loading application (POI loader) you want to use.
I purchase my speed camera databases from a German site. These folks have quite good coverage for both the UK and the Continent. In their database, they list speeds for the cameras on the continent in km/h, and speeds for the UK cameras in MPH. In other words a camera that triggers at 30 MPH (same velocity as 50 km/h) is listed as being a '50' if it is on the Continent, and a '30' if it is in the UK.
All well and good, but the GPSR can't cope with this - all the data imported in a given load has to be defined by the same unit of measure. This means that when I am on the ferry (or train in the Channel Tunnel) on the way to the Continent, I get to pull out my laptop and re-load the very same database I had previously loaded for UK use all over again - but this time specifying that the trigger speeds are in km/h, because I am going to the Continent.
If you are not sure about all this, create your own fake radar camera database by setting up two geographic points one block apart in the neighborhood that you live in. Set one to trigger at 30, and one to trigger at 50. Then, upload this huge database (both points) with POI loader set to MPH, and see how things behave. Later on, upload it with POI loader set to km/h and see how it behaves.
Actually, on second thought, it might be better for the sake of your driver licence and your wallet to try uploading the test database in km/h first, and then upload it in MPH second, unless you happen to live on a street with a 50 MPH speed limit...
Michael