|
POST
|
Thanks Nimesh - It seemed like this was a supported workflow, but I was having trouble finding specific documentation for creating vtpk files using ESRI base maps. I just thought I'd check this forum to see if anyone else had done one. I'll post something in the Pro forum.
... View more
12-28-2018
04:22 PM
|
0
|
1
|
4147
|
|
POST
|
I've tried these: https://basemaps.arcgis.com/arcgis/rest/services/World_Basemap_v2/VectorTileServer https://basemaps.arcgis.com/arcgis/rest/services/World_Basemap_Export_v2/VectorTileServer Both return the error in ArcGIS Pro
... View more
12-28-2018
01:17 PM
|
0
|
0
|
4147
|
|
POST
|
Hi Nimesh - For our initial development and testing we were hoping to generate a vtpk of the ESRI Navigation vector basemap (export version) in ArcGIS Pro to "bake in" with the app install package. Further down the road I think the plans are to develop a custom basemap specific for the app. Regardless of the vector tile layer used I get this error: 001852: Layer type is not supported for vector tile packages.—Help | ArcGIS Desktop
... View more
12-28-2018
10:52 AM
|
0
|
6
|
4147
|
|
POST
|
Is there a supported workflow to create a vector tile cache (.vtpk) from an ESRI vector basemap? There are export versions of the vector basemap layers available and the "Create Vector Tile Package" tool in ArcGIS Pro mentions generating vector tiles from a basemap, but I have yet to get one to actually export. The ArcGIS Pro tool returns an error every time saying the layer type is not supported for vector tile packages. Does anyone have a method that actually works for this?
... View more
12-26-2018
01:38 PM
|
1
|
9
|
5366
|
|
BLOG
|
This is fantastic. The UI similarities with the Collector Aurora Beta are great and I want you all to know we plan to steal liberally from this 😉 Great work.
... View more
11-08-2018
03:19 PM
|
1
|
0
|
290
|
|
POST
|
Woah - nice. Totally missed that change. Guess I should start reading all those ESRI emails a little more closely!
... View more
10-09-2018
11:15 AM
|
1
|
0
|
1498
|
|
POST
|
At this point I assume this is never going to happen. Just one more roadblock to adopting Pro across the org.
... View more
10-09-2018
10:57 AM
|
1
|
2
|
7803
|
|
POST
|
Seriously though - we've run into similar issues... especially when using external GNSS units like the iSXBlue and the EOS Arrow. We have found that keeping the units in the shade helps. We've also found that the newer 10.5" iPad Pro does much better WRT battery life when using either the internal or external GPS. That said we always include a battery booster when we send units out into the field.
... View more
08-21-2018
04:47 PM
|
3
|
1
|
1632
|
|
POST
|
Sorry - I realize now you are editing directly against a feature service an not using an offline database.
... View more
08-14-2018
12:17 PM
|
0
|
4
|
1270
|
|
POST
|
That makes sense. In some of my other apps (that only have one editable geodatabase to manage) I side-step the issue by naming the downloaded file with the project name and a timestamp and storing the result in NSUserDefaults. If they need to reset their database I just download a new file with a new timestamp and update the stored value. I was really hoping to avoid having to go that route with the apps that have multi-project support, but maybe that's what I'll have to do.
... View more
08-09-2018
05:14 PM
|
0
|
0
|
1624
|
|
POST
|
That is what I'm suspecting as well. The strange thing is that the SDK seems to be having trouble letting go of the cached copy even if we switch to using a completely different database. For example we have a wetland determination app where every project has a dedicated SDE/Feature Service. Users are able to switch between projects by checking one in a list view. When that happens the app rebuilds our map and list views to point at the new data source. When we get into our "phantom database" state after a reset the user can switch to a different project and then back and it will still use the phantom in-memory geodatabase instead of the one that is actually living in the file system. Currently the only way to stop that behavior is to kill and re-lauch the app. I've tried rolling through our code and invalidating every AGSGDBGeodatabase and AGSGDBFeatureService variable to see if that frees up the in-memory object but no luck yet.
... View more
08-09-2018
03:57 PM
|
0
|
0
|
1624
|
|
POST
|
You can implement text-to-speech yourself with AVSpeechSynthesizer: AVSpeechSynthesizer - NSHipster
... View more
08-08-2018
10:30 AM
|
1
|
1
|
1268
|
|
POST
|
I'm hoping someone can explain what is going on under the hood when I create an AGSGDBGeodatabase (runtime 10.2.5) object using the geodatabaseWithPath method. Is there any caching of the file going on? I ask because we have run into frequent enough issues with ArcGIS Server that our apps now contain a "Reset" switch to archive runtime geodatabase and downloads a fresh copy. In recent months (since iOS11) I've noticed some very strange behavior related to this. When the geodatabase file is reset the current .geodatabase, .geodatabse-wal, and .geodatabse-shm files are added to a zip file and deleted. A new version is then downloaded and copied to the same location (with the same name). After this is completed our Map View and various list/table views are rebuilt. The new geodatabase is downloaded, placed in the correct locations, with the correct name, but when a new AGSGDBGeodatabase object is created using the geodatabseWithPath method it appears to be using the information from the old version of the file. Worse yet, new data saved to an AGSGDBFeatureTable created from the AGSGDBGeodatabase is not written to the file, but appears to only exist in memory somehow. Re-starting the app results in that cached data disappearing and the app correctly builds AGSGDBGeodatabase objects using the downloaded replacement file. It is pretty obvious this is happening when looking at the file system in the simulator. The .geodatabase-wal and .geodatabase-shm files are never created when the map is rebuilt, but are instantly created for other .geodatabase files as soon as AGSGDBGeodatabase and AGSGDBFeatureTable objects are created. Is there someone at ESRI that can shed some light on what is happening behind the scenes when an AGSGDBGeodatabase object is created? I know the stock answer is probably "you should be using v100, but this is a three year old app and this code had been working fine up until the shift to iOS 11 (and the new APFS file system). Thanks
... View more
08-07-2018
11:58 PM
|
0
|
4
|
1772
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | 03-06-2024 10:15 AM | |
| 1 | 05-18-2022 03:07 PM | |
| 2 | 06-05-2023 09:15 AM | |
| 2 | 12-04-2022 10:01 AM | |
| 1 | 12-13-2022 12:38 PM |
| Online Status |
Offline
|
| Date Last Visited |
2 weeks ago
|