POST
|
Yes, it is possible with v100.0. You can use `AGSExportTileCacheTask` to download tiles and view them in offline mode. Check out this sample that demonstrates this.
... View more
01-19-2017
02:00 PM
|
0
|
0
|
187
|
POST
|
What is the format of your GIS data? This section talks about how you can display various types, including base maps, items from your ArcGIS Org or Portal, feature services, mobile map packages etc using ArcGIS Runtime SDK for iOS v100.0. Check out our samples too
... View more
01-19-2017
01:56 PM
|
2
|
0
|
268
|
POST
|
You can create a tpk file with ArcMap or Pro. Check out these links. Once created you can side load it to the device for use in your iOS app. Alternatively, you can also use the SDK's `AGSExportTileCacheTask` to generate tile package.
... View more
01-19-2017
09:47 AM
|
0
|
0
|
203
|
POST
|
Regular png does not have spatial reference, and therefore adding it as an operational layer in a map does not render the layer. It can be added as a base map layer. There is an exception though. If the png file is created from ArcGIS desktop and comes with an .aux.xml metadata file, the spatial reference and extent information can be stored in an xml, in which case, the info can be read. For the more common case when it's just a png file, there is no spatial reference.
... View more
01-13-2017
09:43 AM
|
0
|
3
|
831
|
POST
|
Would it be correct to assume that this applies to queries from a local geodatabase as well? Queries in a local geodatabase are always local. The query therefore returns all the fields that are in the geodatabase (loaded feature) What will be returned by AGSQueryFeatureFieldsIDsOnly? Unloaded features that have ObjectID and GlobalID fields will be returned This all or nothing approach to returning fields has the potential to create some significant unnecessary memory usage or slowdown when querying large volumes of data It's not really all or nothing. If you want the features on the map, it must have the required fields for rendering and editing. That's the minimum set of fields returned using AGSQueryFeatureFieldsMinimum. In this case, features are loaded as needed. If the features won't be on the map, then you can just request for IDsOnly if the number of features is going to be more. or simply LoadAll. You could use ServiceFeatureTable's ManualCache mode to specify custom outfields. Let us know if your requirement still necessitates outFields
... View more
01-04-2017
05:00 PM
|
0
|
1
|
613
|
POST
|
James, Yes, it is. You can check AGSFeatureQueryResult's transferLimitExceeded. We have plans to add support for paging queries in an upcoming release Suganya
... View more
11-28-2016
11:24 AM
|
0
|
0
|
613
|
POST
|
hello, Yes, AGSQueryParameters no longer has outFields. You can use one of the AGSQueryFeatureFields enum values or use the service feature table in ManualCache mode which allows specifying outFields. The concept of loading features into tables in 100.0.0 is different from 10.x where all the fields were brought by default and features were in memory, so you could use outFields to easily get a subset of fields. 100.0.0 featureRequestMode OnInteractionCache: In 100.0.0, the default featureRequestMode of AGSServiceFeatureTable (OnInteractionCache) brings down just the minimum set of fields required for rendering of features on map in addition to any editor tracking fields. This enables rendering and working with large number of features with just necessary fields to start with, without the overload of fetching everything. A feature could then be loaded to get all fields as needed, for instance when beginning to edit. When querying a table in this mode, you can request for - IDs only - Minimum fields required for rendering (which is what happens when the layer is added to a map) - Load all features which means all fields are queried The query in this mode could be local or an online query depending on whether the features are already in the table and the AGSQueryFeatureFields enum chosen. 100.0.0 featureRequestMode ManualCache: If you set featureRequestMode on the table to ManualCache, it means the features would be populated from the server once, and would be used locally there forth, likely in a disconnected environment. You can specify outFields then while populating using the method populateFromServiceWithParameters:clearCache:outFields:completion: Note that querying is always local in Manual Cache mode.
... View more
11-28-2016
10:01 AM
|
1
|
5
|
613
|
POST
|
Please send a sample project that would reproduce the issue so we can take a look.
... View more
05-16-2016
11:32 AM
|
0
|
0
|
386
|
POST
|
I was using Edit Features (Connected) sample. Note that this is Quartz-beta branch and requires Quartz-Beta2 version of the SDK. for field in popup.popupDefinition.popupFields { field.visible = false } You may try the same with Offline Editing sample 10.2.5 using popupInfo.fieldInfos, but the behavior would be slightly different.
... View more
05-16-2016
11:22 AM
|
1
|
0
|
257
|
POST
|
You can reduce number of steps in Quartz as attributes and attachments are presented in the same vc. So by following a similar approach Divesh suggests, you may have the following steps 1. Click Edit 2. Popup VC opens in editing mode with just attachments (assuming visibility of fields in popupDefinition.fields is set to false). 3. Hit Done to close popup. In my app some layers require attribute editing, but for some layers, inspectors just want to take picture attachments (because attribute editing for these layers is handled with different custom view controller). It seems like you already have a different workflow for certain layers - you may use that check to toggle the visibility of the fields. Quartz screenshots:
... View more
05-13-2016
10:15 AM
|
0
|
2
|
257
|
POST
|
I see you are using AGLegendInfo class. Is that meant to be AGSLegendInfo? Which version of the SDK are you using (or intend to use)? I ask because AGSLegendInfo class is present only in the Quartz beta release and AGSGraphicLayer is in 10.2.5 (AGSGraphicsOverlay in Quartz)
... View more
04-19-2016
10:38 AM
|
0
|
2
|
386
|
POST
|
Hi, thanks for reporting. This is a known issue with 64 bit devices and we'll work on fixing it in the next release. Can you try this workaround? Build the project with only 32 architectures. You can then run the app on all devices without a crash - the trade off being you would be unable to benefit from 64-bit computing. Suganya
... View more
04-19-2016
10:23 AM
|
0
|
1
|
284
|
POST
|
What error are you getting? Can you post your code so I can take a look? Thanks. Suganya
... View more
04-12-2016
04:47 PM
|
0
|
5
|
386
|
POST
|
Can you check what is the state at this line and this? Are the 5 templates getting appended fine? You mentioned you have added an outlet to the table. How about the datasource and delegate? Are these methods getting called successfully?
... View more
04-11-2016
02:45 PM
|
1
|
1
|
293
|
POST
|
Can you try using AGSGDBFeature class instead of AGSFeature protocol? However, either one should work. If that doesn't work, can you provide the stack trace of the crash? You can get this info by typing bt on the console window after the crash.
... View more
10-05-2015
04:26 PM
|
0
|
1
|
349
|
Title | Kudos | Posted |
---|---|---|
1 | 08-04-2015 12:58 PM | |
1 | 01-08-2019 03:59 PM | |
1 | 05-16-2016 11:22 AM | |
1 | 11-19-2019 11:29 AM | |
1 | 11-28-2016 10:01 AM |
Online Status |
Offline
|
Date Last Visited |
06-05-2023
05:23 PM
|