Recent Posts9801
Living Room / Re: GPS Unit Recommendations?
« Last post by Renegade on May 21, 2010, 06:31 AM »Cell phone triangulation is what it is, so you can't expect it to be nearly as accurate. You'll notice that while you are standing in one spot, your location can easily shift by 30~50 meters *as you are standing still*. As long as you know that it's a *ROUGH* estimate and treat it as such, you're fine. Real GPS on the other hand is highly accurate. For a pedestrian, a phone is good enough.
This is a real problem. GPS as a driving navigation device needs to live up to the kinds of standards set in the automotive industry. While you can't expect 100%, expecting more than 50% of trips to be trouble-free isn't unreasonable.
The main problem I see is that for unfamiliar places, this is where you need the GPS to be accurate and need it to to be responsive. You just can't stop in the middle of traffic because your GPS unit is slow and you've already missed 2 turns because of it. You'd quickly find out what road rage is like on the receiving end. Steering you wrong is simply a hazard. Especially in heavy traffic where you need to be paying attention to the road, and not constantly glancing at the GPS while you wait for it to update because you're now hopelessly lost.
Common sense can't help you in some of those driving situations (I take it that you mean you need to use common sense to know that the unit will make mistakes for things like out of date maps, etc.). The only thing you can do is to make sure that you prioritize your driving and get ready to suck up the GPS unit's mistakes. I'm just tired of sucking it up for half all the trips I need it for.
You cannot trust a GPS unit (phone or stand-alone) 100%. You must also use common sense. For example, if the road configuration changes, it will be different from the map on the GPS unit, until the map is updated.-bgd77 (May 21, 2010, 05:59 AM)
This is a real problem. GPS as a driving navigation device needs to live up to the kinds of standards set in the automotive industry. While you can't expect 100%, expecting more than 50% of trips to be trouble-free isn't unreasonable.
The main problem I see is that for unfamiliar places, this is where you need the GPS to be accurate and need it to to be responsive. You just can't stop in the middle of traffic because your GPS unit is slow and you've already missed 2 turns because of it. You'd quickly find out what road rage is like on the receiving end. Steering you wrong is simply a hazard. Especially in heavy traffic where you need to be paying attention to the road, and not constantly glancing at the GPS while you wait for it to update because you're now hopelessly lost.
Common sense can't help you in some of those driving situations (I take it that you mean you need to use common sense to know that the unit will make mistakes for things like out of date maps, etc.). The only thing you can do is to make sure that you prioritize your driving and get ready to suck up the GPS unit's mistakes. I'm just tired of sucking it up for half all the trips I need it for.
) The most interesting thing is the new EGG compression format as it has smart compression for different file types, e.g. JPEG vs. PNG vs. BMP all benefit from different compression types. It also does solid compression now, which is very nice. 
Yeah, I guess I should have put the .NET 4 requirements down there. (It could be done in .NET 3, but I kind of wanted to play around a bit and just have a look at .NET 4.)