POST
|
any updated timeline on this capability? If implemented, would I be able to use the network from StreetMapPremium Custom over the imagery (ie, instead of the cartoon map currently included?) We're navigating two-track farm roads, forest roads and/or oil field service roads that may or may not be included in StreetMap, and until we are able to add these to the road network ourselves, we'd like to have the imagery for heads-up navigation where StreetMap doesn't exist. The reason I'm asking for a timeline is that we are prototyping a potential custom application to be deployed by March 2018, and really want to understand the technological limitations of an MMPK with an imagery basemap might cost in extent and scale limitations on a mobile platform. (I assume the existing streetmap is a vector tile map, whereas the imagery would required a tiled map cache.) Any chance you have any parameters that have been used during development of this capability that could educate our decision-making? For example, you might give me something like this, for your own specific scenarios being tested: "20 levels from 1:1,500,000 to 1:11,000 , for 20K sq km area, is 2 GB". If not, perhaps you can give me some indication of what content size you are imagining Navigator can realistically support in driving mode on a mobile device (in our case iOS tablets)? Thank you!
... View more
03-08-2017
12:18 PM
|
0
|
0
|
422
|
IDEA
|
In our case, we have a single publisher in each business unit (mining, forestry, petroleum, etc). Each has many users, and among those users, some may be doing reconnaissance in the morning and inspection in the afternoon, or on a single field trip, using topos for contextual feature reference, but then imagery for data collection once hiked into a remote site. In some cases we generate our own tiled map cache, in order to burn large extents of vector data into imagery (such as land ownership and relatively static business data). It would be useful to have that basemap at one scale range (often smaller scale, which helps because the imagery doesn't need so many levels), then switch to a different at a different scale range once 'in the neighborhood'. My assumption is that performance would be enhanced if a user was rendering one cache at smaller scales (with fewer levels), then rendering a different one when at larger scales (more levels).
... View more
01-26-2017
05:25 PM
|
1
|
0
|
604
|
IDEA
|
in our workflow, this would require a prohibitive amount of manual oversight to generate the various extents and scales that different users need (because their devices are limited in storage capacity) and then to maintain the TPK files on the filesystem. This is why I want the user be able to select multiple basemaps according to their own extent and scale parameters.
... View more
01-26-2017
05:05 PM
|
1
|
0
|
780
|
POST
|
woohoo! But, wait, EARLIER than 4.4, so this is a feature that will not be supported going forward?! My phone is >2 years old and I'm on Android 6.0... are there even any devices still using Android < 4.4
... View more
01-26-2017
03:43 PM
|
0
|
7
|
1116
|
POST
|
Does anyone know if this limitation still exists? I'm not finding it in the list of current features, and I find lots of talk about offline basemaps but nothing about using on external SD.
... View more
01-26-2017
03:36 PM
|
0
|
9
|
1116
|
Title | Kudos | Posted |
---|---|---|
1 | 01-26-2017 05:25 PM | |
1 | 01-26-2017 05:05 PM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:25 AM
|