Lifetime RDF Contributor
Lifetime Premium Member
- Nov 27, 2015
- Reaction score
- Cleveland, OH
I am therefore wondering, if perhaps Uniden and I could together provide an easier way of collectively update and revise the gps data for these detectors? This would make this reporting system much more open and in many ways better than escorts system since the updates are reviewed in more detail.Your service to the community is indeed appreciated. However, the better, easier implementation of this effort would be using GIS. I don't operate in the free Google Maps / QGIS World so I wouldn't know how to do it without some research put into it. But in the ESRI ArcGIS world, I would create a simple ArcGIS Survey123 field form, with mandatory drop down menus covering the details you present in your first form. These would get posted to the map within 30 seconds or so. On the back-end you can download the database on a weekly, bi-weekly or monthly basis as your time allows, merge it with the existing Uniden database and post it for us to download. With your mad skillzzz, you surely would find a way to filter out duplicates and in doing so remove Uniden's entries that have dated or wrong information such as speed limits. This way we would have our own community-developed "Waze-like" database of end-user reported cameras.
Incorrect Speed Warning in both directions at the following location. There isn't a speed camera anywhere in the area. I'm running R3 with firmware v1.50 and getting the same false report with db190402.bin and the latest db190704.bin
Confirmed, nothing there in either direction.There is also one other camera alert in the database close to this position at 32.4313202,-96.231163 (set as 15 mph monodirectional alert). Before I complete the build, please could you confirm whether this one also needs to be removed.
Sorry, that was probably not a fair request / comment. This information is also probably not something that needs to be known generally. I also now consider that perhaps some of this memory allocation could also be used for other purposes such as user marks and gps lock-outs, so it might not be so clear cut an answer anyway. It would however be useful to know the memory capability of the detector, as I don't really want to overload it. Especially if the upload tool was not contemplated to handle such large files. Trial and error probably the way forward.However, @UnidenSupport might already know the answer. Could you please confirm my prediction before I subject a DFR7 to potential destruction?