Saving Location Data Using Kernel Data

Question

I was wondering what approach is recommended for storing an array of CLLocation objects (forming a route or path) in a Core Data database? Is serialization a good approach, or would you recommend storing CLLocation objects in a separate model that is relevant to the route model?

The problem with serializing an array of locations is that you do not have easy access to specific places. On the other hand, storing each route / path location as a separate entry in the database seems to lead to a large database and may lead to poor performance.

I am interested to hear your suggestions.

Bart

Answer 1

The solution that best suits my needs is to store location data as double values, separately preserving latitude and longitude. As a result, the search is a little more complicated, but this approach seems to be better than any other approach that I have encountered so far.

I should note that there are reports that developers experience problems with this approach in terms of accuracy problems (significant numbers) when retrieving stored data. This thread is one such example.

Answer 2

For one of the applications I have a code, I store it in a string, as described in the Google Maps API.

http://code.google.com/apis/maps/documentation/directions/

Polyline Algorithm