Request to improve your database

 

Dear all,

I just receive message that my subscription with you guys was
gone. Still decide if still going with you again or not.

Here's of my experiences with your databases and wish that you can improve to help all of us.

- First of all, your database is not from SCDB, very small compared to them.
- Wish you guys to have nice interface at specific speed likely
SCDB
- Sometime your database shows weird fixed camera. For example last time in Boston, ran like crazy at 70 MPH on highway, suddenly there's announcement of speed limit is 25 MPH, confused little bit and just find out there's small road under the highway, maybe there's camera over there. It happens several times in many states.
- Most of the time we do have tickets because of trap of police on the highway. We drive on many well-known highways like I91 I87 I95, for example, you don't have good alert at all. Sometime, it's yes but it's not accuracy because it's nowhere that police can hide or exactly there's none of any sign of police cars around that areas. Actually I pay for 3 services: SCDB, Garmin Cyclop and yours, all of 3 services lack of police trap on highway.

Please help us by improve more your service, except there's another way to avoid these ugly expensive tickets from them

Thank you for listening and all of your understanding. Regards

Some notes re your criticism

Just a few notes in response--I'm sure the actual admins can note more:

a) You should note that POI Factory's database is almost entirely crowd-sourced, and--at least in my experience--has tended to be better in North America (SCDB is fairly Euro-centric, POI Factory largely covers the US and Canada and SCDB would actually be expected to have better coverage in Europe). POI Factory also tends (in my experience) to be quicker at noting sudden changes in RL deployment patterns than SCDB (among other things: RL and speed cameras being removed in TX due to court order, some increases in NYC near school zones, etc.)

b) POI Factory's files are largely optimized for Garmin systems as well as TomTom and compatibles (including at least one major smartphone GPS program, CoPilot). Not all the options for different speedcam warnings are available without multiple files (and again, SCDB largely makes these available for various GPS tools that DO have warnings for distinct speeds, such as iGO--popular in Europe, but with a very low user base in the US compared to Garmin/TomTom/Magellan and compatibles).

In other words: Most of the userbase just wants advanced warning, and doesn't require files and tweaks for each specific speed (especially since in the US, you have a lot of combined RL/speed cameras). You also have areas with variable speed limits due to schools that compromise the majority of speed camera areas in North America, which also makes it next to impossible to note a specific speed.

c) Those sudden shifts you're talking about, like with the Boston speed camera? Those are almost to a one in school zones (another reason there's not a nicey-nicey "pick your speed" like SCDB)--a lot, in fact, most speed cameras in the US and Canada are in school zones where the normal speed limit may be 45mph/80kmh but drops drastically to 25mph/40kmh or even 15mph/20kmh when school opens for the day and closes for the day. (In general, variable speed limits around schools are almost entirely a US and Canada phenomenon; it's expected that a speedcam database based in Europe isn't going to catch this.)

d) Speed trap databases aren't done because--outside of a few jurisdictions that are notorious speed traps (like a certain town in Ohio that actually ended up being de-incorporated, among other things) speed traps are such a moving target in the US and Canada that no database can be expected to keep up with them even if it were updated daily. In my own area (a city and surrounding suburbs where the developed area is close to a million people) you will actually see police change enforcement points multiple times a day, and the frequency of enforcement also changes. Again, there are very few places that can RELIABLY be said to be speed traps most of the time (mostly in very small towns and along state borders where there is a large speed shift)--at least for I-95 (a major north-south highway in the US) there is an existing POI set for the known "regular" speed traps here.

And yes, police here in the US and Canada frequently change the location of "stakeout points" for speed traps multiple times a day by design; they don't want the equivalent of "shunpiking" (aka where speeders deliberately slow down or bypass the particular speed trap). About the only places that have permanent speed traps are, again, along borders of states with a SIGNIFICANT drop in speed (like the WV-MD border where the interstate speed limit formerly dropped from 70 to 55 with little warning) or in very rural small towns along an interstate or state highway (where there really isn't an alternate route) that gain practically all their income from speeding tickets.

Honestly, in the US and Canada your best bet for detecting speed traps involves a mix of contacting the local AAA (which usually keeps tracks of the worst "permanent" speed trap areas), keeping a radar detector (if you are in a state or province where it's legal--I'd argue if you're in Canada the radar detector won't help you as so many provinces ban them) with lidar and multiband detection, using an app like Waze in populated areas (Waze is usually pretty good at noting where police speed traps tend to be, even if it is crowdsourced it has a large enough userbase it's kept up to date), and using a CB radio tuned to channel 19 on rural highways (yes, the truckers will know where the speed traps are and will warn each other, and you may as well take advantage of the intel).

Some examples of why I note "quality over quantity"

SCDB may have more quantity, but the quality is lacking in that they have some older RL and speed cameras that are not actually in use, and are also lacking some new ones that do show up in the POI Factory DB.

A good example is at https://www.scdb.info/en/countrycameralist/USA/34 where SCDB is still listing Dallas, TX RL and speed cameras; RL and speed cameras were actually ruled unconstitutional in Texas well over three months ago and the law was changed in Texas three months ago to ban RL and speed cameras in the state (http://www.poi-factory.com/node/49845). The existing cameras are in place up to end of contract but any citations from them are unenforceable legally.

I also saw some listings where it was noted the cameras were removed but still kept in the SCDB database, and I half suspect they're doing a fair amount of this "fluffing". (Again, keep in mind SCDB is a database subscription service based in Europe, paid in euro, based in Hamburg, Germany that probably doesn't have the resources to keep the non-European databases up as much as the Euro DBs--seriously, they don't even take into account variable speed limits at school crossings with speed cameras installed, which is pretty much purely a US/Canada phenomenon.)

How reliable would any

How reliable would any static database be that has mobile speed traps, that change when ever the police cars move to another location.

If you absoulutely need that than rely on Waze so you don't get speeding tickets. Or just accept that if you speed you might get a ticket. Maybe obey the speed limit?

--
I never get lost, but I do explore new territory every now and then.