POST
|
Michael, I've used the SQLite DB directly without issue in several apps that I've worked on but there are limitations. There is no way to run spatial joins directly in SQLite or deserialize geometry BLOBS after you read them. If you're trying to do non-spatial joins/aggregation it should work just fine and you can create views just like you would in any other SQLite DB. Like Mark said, summary stats are also an option. FYI, With Objective-C, I used FMDB and with Swift I started using SQLite.swift.
... View more
07-10-2018
10:26 AM
|
3
|
0
|
600
|
POST
|
Garima, My apologies - I am using the add method you referenced. And my baseman is in web mercator. I'm not seeing a way to send that geodatabase privately via geonet (maybe Im just missing it). Is there an email address or other means to upload it?
... View more
07-09-2018
02:21 PM
|
0
|
1
|
943
|
POST
|
I'm working with an offline geodatabase with version 100.3 of the iOS SDK. I have an AGSFeatureTable and used create() to get a new feature. I set the geometry on the new feature and then attempt to save. let table = self.esriGeodatabase?.geodatabaseFeatureTable(withName: tableName)
let feature = table?.createFeature()
feature.geometry = geometry
table.save(feature, completion) I get the following error and stack trace (image attached): Error Domain=com.esri.arcgis.runtime.error Code=2 "Invalid argument" UserInfo={NSLocalizedFailureReason=!input_SR || !output_SR, NSLocalizedDescription=Invalid argument, Additional Message=!input_SR || !output_SR} Note: Same as the error here: Error updating Feature: Invalid Argument: !input_SR || !output_SR I've verified the following: The AGSFeatureTable spatial reference is set to 102100 The spatial reference of the new feature's geometry is 102100 The geometry is not nil and was created with an AGSSketchEditor The error message and stack trace lead me to believe that a reprojection is occurring but I can't understand why, since the table SR matches the geometry SR. Regardless, I can't see why this would fail since the spatial reference is set on both the feature table and the new feature. Any help on this would be much appreciated.
... View more
07-08-2018
03:52 PM
|
0
|
4
|
1172
|
POST
|
Michael Moor Did you get this resolved? I'm running into the same error with no clear cause. Thanks!
... View more
07-08-2018
03:41 PM
|
0
|
1
|
712
|
POST
|
Divesh Goyal Ryan Olson Any update on this? Any chance this will be in the next release of the SDK? Thanks!
... View more
02-21-2017
06:22 AM
|
0
|
0
|
698
|
POST
|
I haven't run into this exact issue but have a number of other issues with sync over the last several years. One recurring problem that I had was that my app would freeze up while preprocessing the delta geodatabase. It would happen even when I had a small number of records. I've also found that the larger the geodatabase, the more time these operations seem to take (both pre and post processing of the sync). I would recommend running the app in the instruments time profiler and see if/where the app is getting hung up. I would not be surprised if you just have a really lengthy preprocessing step that just never finishes.
... View more
02-06-2017
05:36 AM
|
0
|
1
|
567
|
POST
|
I hadn't seen that but I have been force-quitting to test this. I'm willing to bet that a force quit is handled different when connected to the debugger. I will test this more today and see what I find.
... View more
10-20-2016
05:56 AM
|
0
|
0
|
357
|
POST
|
I've been using [AGSGDBSyncTask generateGeodatabaseWithResumeID:status:completion:] to restart downloads that did not finish. I'm putting this in place to handle scenarios where the app is killed, a user loses connectivity, etc. I've found that when I'm attached to the debugger, I can call this method and the download will resume from where it left off. However, if I launch the app without being attached and resume the generate task with that method, the download will restart completely. Is there a way I can force the SDK/iOS to resume the download from where it left off? Has anyone experienced this or have an idea as to why this would only work when attached to the debugger? Thanks!
... View more
10-18-2016
06:23 AM
|
0
|
2
|
776
|
POST
|
They are infrequent but if it happens once in production then we have a problem. I've considered the approach you described, and it's certainly an option, but it would require bookkeeping for all create/update/delete operations which I would like to avoid. More importantly, if one of these manual rollbacks fails then we're still in a situation where we have corrupt data.
... View more
10-11-2016
07:12 PM
|
0
|
0
|
698
|
POST
|
I have multiple records that together make up one transaction. If I insert three records but the fourth fails, then I have situation where I have an incomplete data or orphaned record. Saving the records and maintaining relationships is not the issue. The real problem is that I want either all of my records in the database or none at all.
... View more
10-11-2016
05:59 PM
|
0
|
2
|
698
|
POST
|
I found a bug report regarding this issue and I'm not clear whether this is supposed to be resolved or not. I was told that this was fixed in 10.4 but that doesn't seem to be the case and the ticket doesn't reflect that. Has anyone seen this or know of a workaround? BUG-000087670: Unable to download a file from ArcGIS output directo.. Thanks!
... View more
10-06-2016
07:52 AM
|
0
|
0
|
1005
|
POST
|
Our users go through a series of editing views to update attribution on tables as well as create and update geometries for feature classes. When they're finished with the process, we need to save all of those updates as a transaction otherwise we risk corrupting our database. We don't use esri relationship classes but we do have relationships in our database that we must maintain. In our largest workflow, we have 5 tables and one feature class that all need to be saved at the same time, as one transaction.
... View more
10-06-2016
04:18 AM
|
0
|
4
|
698
|
POST
|
I'm not seeing this functionality in the Quartz SDK. Am I just missing it? Will it in the final release? If not, is there a recommendation or best practice from Esri for performing a series of edits as a transaction?
... View more
09-25-2016
07:52 AM
|
0
|
8
|
1638
|
POST
|
When I attempt to sync and have a large number of deltas from the server, the UI thread is blocked and becomes unresponsive. For a delta geodatabase that is ~20 MB, the block lasts well over a minute and for ~37 MB (the largest I've tested), it lasts closer to 5 minutes. Even when I have a small number of deltas, the UI freezes for a few seconds. We're currently using version 10.2.5 of the SDK and have tested with ArcGIS Server 10.3.1 and 10.4. I've verified in instruments and it appears that this entire process (of applying deltas) runs on the main thread. I've attempted to kick off the sync task on a background thread using both GCD and NSOperations, but in both scenarios, my status/completion blocks do not get executed. Looking at the stack trace, I get the sense that even if that did work, the SDK is explicitly kicking back to the main thread to apply deltas. This lockup seems to have gotten worse in recent months and I'm not sure if that is the result of the increased amount of data in my system or some other external factor. I tried removing indices on a few of the tables that had the largest number of edits (one had 45,000 edits that needed to be applied) and that made no difference. I know there were similar threading issues with 10.2.4 but they were supposed to be fixed. Has anyone run into this with this latest version (10.2.5) and had success with any performance optimizations? I've found a number of ways to speed up SQLite execution but I'm cognizant of the fact that changing those settings could interfere with the SDK. Any insight would be appreciated.
... View more
08-30-2016
07:24 AM
|
0
|
1
|
1299
|
Title | Kudos | Posted |
---|---|---|
3 | 07-10-2018 10:26 AM | |
2 | 06-24-2016 12:54 PM | |
1 | 06-06-2016 07:50 PM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:23 AM
|