Databases
StackOverflow2013
Postsdbo
POHow to store MKOverlay object to file for retrieving later
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to store MKOverlay object to file for retrieving later
    primarykey
    data
    text
    <p>I am writing an iOS application to record your travel path and then storing it so that it can be retrieved later. Most of the code for drawing the path is based on the sample code <a href="http://developer.apple.com/library/ios/#samplecode/Breadcrumb/Introduction/Intro.html" rel="nofollow">Breadcrumb</a>. </p> <p>Now I am adding features to save the drawn overlay. What is best way to do it? I can use <code>CoreData</code> but I am not looking to do much to the drawn overlay rather than retrieving it later again. I have currently tried a simple <code>NSArray</code>. I convert the CrumbPath object into <code>NSData</code> and store it in the array. Later I retrieve it and convert it back to CrumbPath. However, I seem to be doing something wrong.</p> <pre><code>@interface CrumbPath : NSObject &lt;MKOverlay&gt; { MKMapPoint *points; NSUInteger pointCount; NSUInteger pointSpace; MKMapRect boundingMapRect; pthread_rwlock_t rwLock; } - (id)initWithCenterCoordinate:(CLLocationCoordinate2D)coord; - (MKMapRect)addCoordinate:(CLLocationCoordinate2D)coord; @property (readonly) MKMapPoint *points; @property (readonly) NSUInteger pointCount; @end </code></pre> <p>I save a CrumbPath object "crumbs" like this:</p> <pre><code>NSData *pointData = [NSData dataWithBytes:crumbs.points length:crumbs.pointCount * sizeof(MKMapPoint)]; [patternArray addObject:pointData]; [timeArray addObject:date]; NSArray *paths = NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES); NSString *documentsDirectory = [paths objectAtIndex:0]; // Create the full file path by appending the desired file name NSString *patternFile = [documentsDirectory stringByAppendingPathComponent:@"patterns.dat"]; NSString *timeFile = [documentsDirectory stringByAppendingPathComponent:@"times.dat"]; //Save the array [patternArray writeToFile:patternFile atomically:YES]; [timeArray writeToFile:timeFile atomically:YES]; </code></pre> <p>And retrieve it later like this to show in a table:</p> <pre><code>NSData *pointData = [appDelegate.patternArray objectAtIndex:indexPath.row]; MKMapPoint *points = malloc(pointData.length); (void)memcpy([pointData bytes], points, sizeof(pointData)); </code></pre> <p>And construct the path again:</p> <pre><code>crumbs = [[CrumbPath alloc] initWithCenterCoordinate:MKCoordinateForMapPoint(points[0])]; for (int i = 1; i &lt;= pointCount; i++) { [crumbs addCoordinate:MKCoordinateForMapPoint(points[i])]; } [map addOverlay:crumbs]; </code></pre> <p>However, I get an error: <code>'NSInvalidArgumentException', reason: '-[NSConcreteData isEqualToString:]: unrecognized selector sent to instance</code></p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRob
    1. USSap
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to store MKOverlay object to file for retrieving later
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow to store MKOverlay object to file for retrieving later
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    3. VO
      singulars
      1. POHow to store MKOverlay object to file for retrieving later
      1. USPowerHorse
      1. VTFavorite
    1. COUnrelated to your exception, you're showing us your calls to `malloc`, but not the corresponding `free` calls. I assume you have that somewhere, but make sure you clean up after yourself. Or you can avoid calls to `malloc` and `memcpy` (like my code sample below) and you don't have to worry about it.
      singulars
      1. POHow to store MKOverlay object to file for retrieving later
      1. USRob
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload