Speeding To Become Impossible In UK?
dmearns writes: "Picked this up from comp.risks. It seems the UK government is planning on requiring computer controlled speed limiters on cars within 5 years. The system uses GPS to figure out if the vehicle is in a speed limited zone. The original story is here.
I suppose it is inevitable that officials would think of something like this, but I never thought people would accept it!"
What about places where you can't get a good fix on GPS satillites? I know with my eMap, if theres enough tree or building blockage I can't get any satillites. In downtown minneapolis I have no reception at all.. will the cars just stop totally?
I suppose once the system is in place there won't be any more patrollers on the road looking for speeders. So if you crack it you can speed and no one will looking for you. So for once I suppose I'll be on time :-)
- How big is your land, sonny?
- Lissen, dude, I can jump in my car in the morning, drive it until the sun sets, and I'll still be on my land.
- I used to have a car like that, too...
--
Do you realize how inaccurate radar guns are? How is the cop on the side of the road supposed to know that you in your subcompact 4 lanes over was the one doing 11mph over the speed limit and not that 18 wheeler going the other way? If speed kills, why are accident and death rates still dropping after the repeal of the 55mph national speed limit? (When the NHTSA estimated that it would cause 10s of thousands of more deaths) Speed tickets are simply about revenue enhancement - unfortunately, it's not the $75 speeding ticket that nails you, it's the $1000 in insurance premiums you'll pay as you work off your "violation." Frequently the only viewpoint on speeding ever covered by the media is the government line provided by the NHTSA. For the other side of things take a look at the NMA.
Of course not. They're going to feed it to the government in real time. If you think that's unrealistic, look at the Digital Telephony Act and Carnivore. That could enable some interesting opportunities for an alert law-enforcement type (and I'm just scratching the surface):
- A crime is committed at a certain address. Let's interview the ten cell phone users who were nearest at the time. We'll ask, "What were you doing on 15th street last night?" and see if they can come up with an alibi that matches their GPS trail.
- Analysis of the GPS trails will yield some phone users who live in the suburbs but travel into the ghetto periodically. Obviously they're getting drugs. Let's pull them over as they're leaving the ghetto - they'll either be high or carrying drugs. Even a 10% success rate makes it very worthwhile.
- When criminals are caught, their GPS trails can be used as a reference. So if it turns out that serial killers go to the library on Fridays, drive out of town on weekends, and go to Chinese restaurants on Sundays, other phone users who share these traits could be pre-emptively monitored, arrested, or searched. At least they'd be prime suspects if another serial killer starts operating.
Please note that I haven't even touched on abuse of the capabilities by a malicious cop. I've just listed some legal, sensible steps which law enforcement would take with this technology. I also haven't brushed on the commercial possibilites."Speed limiters?" Here in the States, we call them "governors" (that is, they govern how fast your vehicle can go, how fast alcohol can be poured from the bottle, etc.) The introduction of these devices into England would inevitably lead to Britons getting into each other's vehicles and greeting each other with inane phrases such as "How's your guv'nah, guv'nah?" "Ah, give us a kiss, guv'nah, and let's burn some petrol up to the guv'nah, and then Jack's a doughnut, we'll be there!"
:-(
This would make the British even less intelligible than they already are.
We're going down, in a spiral to the ground
What happens if my wife or whomever is about to give birth? Then what do I do? Relax and enjoy the scenery, I guess.
--------
--------
It's OK to be social, just don't tell anyone about it.
Hi!
My firm is developing a web-based vehicle locator system which uses GPS receivers mounted in a vehicle, coupled with a GIS database. I can tell you that while this sounds technically feasible, it won't work.
A system like this requires two parts: a GPS-based locator; and a GIS (Geographic Information System). The GPS locator is relatively easy--there are commercial GPS chipsets that (depending on technology) can identify your position to +/- 3 meters. The latitute/longitude values can be mapped against a database of road segments--and that's where the problem begins.
With what speed limit data?
Even computer professionals tend to leap to unbelievable conclusions about the ability of computers. This is an excellent case: GIS data is stored in a massive database (the MapQuest.com database ships on 37 CD-ROMs). Look at any digital map--it is made up of bazillions of very short line segments. Each and every one of those segments has to be categorized by the type of road, the street numbers of buildings on the road, the lat/lon where the segment starts, the lat/lon where it ends, and lots more. But there is some surprising information that is not included in that data: weight restrictions, load restrictions (such as haz mats), and speed limits. Adding that information would be a big job--and an expensive job.
Expensive? We're talking about the government here....
Okay--so there has never been a government initiative yet that was dropped for being too expensive. That's not the only problem. Getting 37 CD-ROMs worth of data into storage on your vehicle may be a worthy challenge, but let's assume that the bright lights in government can handle that one too. (Stop snickering.) The big problem here is that geographic information changes--all the time. That new shopping center you drive past on your way to work? You may have noticed the new traffic signal--but did you notice that the shopping center driveway has a street name? Did you notice that the speed limit on the boulevard past the shopping center changed? Did you notice the housing development behind the shopping center, with a dozen new streets?
Anybody working with street-level GIS data gets a quarterly database update. (Which means we're all re-loading 37 CDs every quarter.) Streets get dug up and moved; streets get extended; streets get eliminated; streets get widened; bridges get closed. A quarter's update might include changes to millions of street segments--it is by no means trivial. And typically there is a 3 to 6 month lag between the time a street is changed or added and the time it appears in the database. In order for this system to work, every single car would have to be updated to the current speed limits--and they'd all have to be updated more or less simultaneously. Consider the spring construction schedule on your favorite interstate highway--what happens when construction starts? They'll drop the speed limit to 25 mph, and make all the computers slow all the vehicles down. What happens on the day the project ends--and only 96% of the cars have had their computers updated to show the speed limit on that road segment to be 75 mph again? Answer: 4% of your drivers die. Updating all that data to every single car--simultaneously poses a massive challenge.
And that's not all. With a GPS chipset that supports WAAG (fixed-position, ground-based GPS transmitters) we can determine your position to +/- 3 meters--but the road data frequently isn't that accurate. In the U.S., for instance, all but one commercial GIS data provider uses street data based on the U.S. Commerce Department TIGR data files. Different providers will tweak the data--fixing problems, even comparing the TIGR data to satellite photography (the difference in price between different vendors is generally due to the detail quality of their maps). But even with the best maps you can buy, vehicles sometimes still seem to appear well off the actual road. Not all the time, not most of the time, but often enough that this system won't work. Consider what happens when the onboard computer on a vehicle on I-78 in New Jersey (speed limit 65) decides that it is really on the adjacent service road (speed limit 25, just 15 meters south) and slows down....
As it happens, this level of imprecision drives me nuts. The client is continually having to remind me that GPS and GIS are about displaying information, and letting a human brain do the pattern analysis to determine what it sees. For example: suppose we have a position report that shows a vehicle at 40.638 North/74.8974 West. Is the vehicle on I-78 (speed limit 65 mph), County Route 513 (speed limit 40 mph), or Old Highway 22 (speed limit 25)? The answer is--could be any of the three. (The lat/lon--and it's real data--is an overpass.) You and I can easily answer that question based on our knowledge of other data points, and perhaps knowledge of the specific vehicle we're tracking. (We can see four other data points showing the vehicle westbound on I-78, and we know the vehicle is being driven by a Pennsylvania resident, and we know that the data points were mapped during the westbound rush hour: we can easily deduce that the vehicle is probably on I-78. But all we can do is deduce that--and all we can deduce is that the vehicle is probably on I-78. The driver may well be on the off-ramp, heading for a nearby McDonald's. We have to accept that level of imprecision, because that level of fuzziness is the best we can do.
There is an enthusiasm for technology today that sometimes can let people get carried away. This is one of those times. The developers will get a grant from the government to pursue the idea. And maybe they'll do pilot studies and tests and generate a lot of good PR. And hopefully they won't kill anybody before they realize the limits of this technology, and give it up.