We collect data about speed zones, but we do not publish them as there is no real use for it. You are the second person ever mentioned it in our forums. The main purpose of the database (at the moment) is to alert you about camera location.
I'm really only the second person? Wow - I see the speed listing as an integral part of the speed camera database. I know there are often 35 signs around the speed cameras showing the speed so we should know exactly what the speed is, but in the same light we should surely know where the speed camera is because of the signs (my point being publishing the speed limit, in my opinion, is as important as publishing the location because if we're bad enough to miss the speed camera surely we're bad enough to miss the speed limit). There have been a few times where as you're going past the camera you start to doubt whether you've got the speed right - did I miss a sign? have I already forgotten it? If the GPS is beeping at you then you'll know you're going too fast.
Some cameras are variable - Newcastle freeway, school zones etc - but I think just list the lower speed (the aim is to get people to slow down afterall).
Is there perhaps scope to publish the speeds as a separate file and those that would like to include the speeds can tack the "@xx" on the end of the listing?
Thanks Mark. Interesting discussion - I am really surprised people haven't been asking for it.
It is a good idea to have separate file with speed zone limits. Will be available soon... We still believe that having a lot of information on your screen can have adverse effect on your driving practice. You may know that looking to the screen is not legal in some states in USA. Driver should listen voice commands and audio information ONLY - that is what we strongly recommend. I wounded if there is any report about accident(s) involving GPS user who was reading info from the screen before crash...?
Garmin introduced speed camera zones as an advertising trick, but we found no real use of it.
Anyhow, we will follow the market needs and we will publish collected data if there is any considerable public demand.
Thanks for the reply - your points make sense. I guess I am thinking of the speed alerts as an audible thing, but then again a speed flashing on the screen is not too different to checking out your speedo. I agree you shouldn't look though.
Hopefully we'll see the speeds come up soon. Meanwhile I'll start listing some schools in my area and submit via the form.
Hi Mark - just an observation now that I have been using my C320 for a few more weeks now. I have to disagree that it's more distracting to NOT list the speed zones associated with cameras. Let me elaborate:
As it stands now the Garmin automatic install of POIs has speed cameras set at 0km/h which means your Nav unit beeps it's head off while going past the camera. This can be frustrating and annoying, but also overrides any audible directions given by the unit so navigating a turn requires you to look at the screen while it is beeping incessantly.
You can set the speed camera to a proximity alert but this makes the driver look at the map to ascertain the location of the camera.
If the speed was listed on the POI then your unit would only beep if you were over the speed limit and therefore providing you're a responsible driver you would never have any alerts for speed cameras - BUT if you were distracted or didn't realise your speed was creeping up it would beep at you, alert you and slow you down.
It seems to me that by listing the speed alerts you actually reduce the need to have ANY attention on your unit unless you are over the speed limit (school zone cameras aside as they would have to be set at 40 at all times and would just beep outside school hours).
I know you're intending to list the speeds separately (and I can't wait) but I thought you might find my observations interesting and might aid you in future planning for these files.