|
|
|
|
|
|
by jldugger
3222 days ago
|
|
|
> I would expect part of that budget includes the replacement of several legacy databases and software applications to support the high frequency, low latency querying of license plates several times per second, per vehicle. Well, if we're just checking to see if a car is registered stolen, that's hopefully a very small database. A simple hash table should be sufficient for a yes/no decision. But God only knows what goes on inside the DMV, and getting that data out into a rapidly queryable state could be tricky. |
|
|
Google reckons there's only 4.5 million registered vehicles in Victoria (.au) - with 6 character [A-Z0-9] = 36bit/5byte plates that's only gonna need ~22 meg to store them all and you've got a few bits for "flags" - even if 10% of them are listed as stolen at any time, you'd only need a couple of meg for the "stolen car list" - even without handwaving away the overhead for the data structure, this seems a reasonable solution. If you want the make/model/colour info you could then just query the remote db when you get a hit for a plate with the "stolen" flag set (or perhaps the "vehicle of interest" flag).
Of course nobody's gonna build it that way, because then you lose the data set of plate locations you can own without needing to ask for consent. This will, of course, store GPS location and timestamp of every plate is acquires, and if they're being particularly audacious, the actual imagery captured as well. That's how you make this a $80mil project... :-/
(Of course private industry already has this - tow trucks carry alpr rigs and sell the data to repo agencies in the US, I'm told...)