Detecting Bad CoreLocation Data
When a new point comes in, it is invalid and can be discarded if it matches any of the following criteria: In regards to the last bullet, the
CoreLocation can (and will) give you poor location data. Over the course of developingRunMonster, I have become painfully aware of this fact. It turns out, though, that you can detect and discard the most egregiously bad location data using a few simple tests.
CoreLocation framework seems to cache and report points from the last time the GPS unit was used. For instance, if you last ran the GPS in Montana and then open your app in Georgia, the first point could be the last cached point from Montana. If you are running a distance-tracking application, then your app would merrily add thousands of miles to your total distance.
When a new point comes in, it is invalid and can be discarded if it matches any of the following criteria:
In regards to the last bullet, the
Saket - The Link Master
- Saket: YAY YAY YAY
- Saket: that's you!
- Saket: (subtraction.com is Khoi Vinh's personal blog)
- Troy: Awesome!!!
- Troy: Thanks for all the great links!
- Troy: I'm getting in the habit of sending all your links to our fyi email list
Flipboard goes beyond the RSS feed and actually grabs from the oriignal content source, in a way that i think is quite illegal, or questionably illegal, but i think it’s interesting because it’s forcing the news organizations to rethink whether it’s enough to give you just a headline and a few sentences in their feed.