nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Rendering Mobile Map Packages

MarkCederholm

I'm seeing the same problems with Mobile Map Packages in the 100.0 release that I saw in the Beta. I cannot zoom or pan to the full extent of the data, and not all features are rendering properly. Is this issue still being worked on for a future release?

Encontre mais publicações marcadas com

Accepted answers

All comments

KyleGruber

Is scale-based sizing supported in the runtime SDK with mmpk's generated from ArcGIS Pro 2.0 (or will it ever be)? That still doesn't seem to be carrying over.

MichaelBranscomb

Hi Mark,

What version of ArcGIS Pro are you using to create your MMPK?

Cheers

Mike

MarkCederholm

Well, I don't know which issue you think is fixed, but I'm still having to use the add baselayer workaround on my example MMPK in order to zoom out beyond a certain scale. However, I can at least pan to the end of the data now. Anyway, I'll keep looking into MMPK issues with 100.1, and report any problems directly to tech support.

MarkCederholm

Great, I look forward to checking it out.

DonKemlage

Hey Mark,

Great news! This issue has been fixed with ESRI's latest version of the ArcGIS Runtime for .NET (v100.1) that was just released yesterday (6/29/2017). Read all about the Update 1 capabilities in the blog post: https://blogs.esri.com/esri/arcgis/2017/06/29/arcgis-runtime-sdk-update-1-is-now-available/

-Don

DonKemlage

Hi Mark,

This may be a bug that we are currently working on. Try the following workaround and see if is helps:

Before you set the MapView.Map property to contain the .MMPK's map, add a base layer that has a larger initial extent (ideally the same base layer that you might have used in ArcGIS Pro to create the .MMPK). Then after you set the MapView.Map property, remove the base layer. The layers in the .MMPK will display at the extent as they were originally created in ArcGIS Pro. The unintended side effect of this workaround is that you can now zoom out past the original extent that was specific in ArcGIS Pro (but at least you can see all of the data).

Here is some sample code to demonstrate the workaround:

<SPAN class="keyword token">string</SPAN> thePathToMMPK <SPAN class="operator token">=</SPAN> <SPAN class="string token">"C:\\Temp\\CurrentDisplayExtent.mmpk"</SPAN><SPAN class="punctuation token">;</SPAN>
MobileMapPackage theMMPK <SPAN class="operator token">=</SPAN> Await MobileMapPackage<SPAN class="punctuation token">.</SPAN><SPAN class="token function">OpenAsync</SPAN><SPAN class="punctuation token">(</SPAN>thePathToMMPK<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN>
IReadOnlyList<SPAN class="operator token"><</SPAN>Map<SPAN class="operator token">></SPAN> theMaps <SPAN class="operator token">=</SPAN> theMMPK<SPAN class="punctuation token">.</SPAN>Maps<SPAN class="punctuation token">;</SPAN>
Map myMap <SPAN class="operator token">=</SPAN> theMaps<SPAN class="punctuation token">[</SPAN><SPAN class="number token">0</SPAN><SPAN class="punctuation token">]</SPAN><SPAN class="punctuation token">;</SPAN>

<SPAN class="comment token">// WORKAROUND - Part1 (Add a base layer with a larger viewable extent)</SPAN>
<SPAN class="keyword token">var</SPAN> serviceUri <SPAN class="operator token">=</SPAN> <SPAN class="keyword token">new</SPAN> <SPAN class="token class-name">Uri</SPAN><SPAN class="punctuation token">(</SPAN>http<SPAN class="punctuation token">:</SPAN><SPAN class="operator token">/</SPAN><SPAN class="operator token">/</SPAN>services<SPAN class="punctuation token">.</SPAN>arcgisonline<SPAN class="punctuation token">.</SPAN>com<SPAN class="operator token">/</SPAN>arcgis<SPAN class="operator token">/</SPAN>rest<SPAN class="operator token">/</SPAN>services<SPAN class="operator token">/</SPAN>Canvas<SPAN class="operator token">/</SPAN>World_Light_Gray_Base<SPAN class="operator token">/</SPAN>MapServer<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN>
ArcGISMapImageLayer baseLayer <SPAN class="operator token">=</SPAN> <SPAN class="keyword token">new</SPAN> <SPAN class="token class-name">ArcGISMapImageLayer</SPAN><SPAN class="punctuation token">(</SPAN>serviceUri<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN>
myMap<SPAN class="punctuation token">.</SPAN>Basemap<SPAN class="punctuation token">.</SPAN>BaseLayers<SPAN class="punctuation token">.</SPAN><SPAN class="token function">Add</SPAN><SPAN class="punctuation token">(</SPAN>baseLayer<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN>

MyMapView<SPAN class="punctuation token">.</SPAN>Map <SPAN class="operator token">=</SPAN> myMap<SPAN class="punctuation token">;</SPAN>

<SPAN class="comment token">// WORKAROUND - Part2 (Remove the base layer)</SPAN>
LayerCollection myLayerCollection <SPAN class="operator token">=</SPAN> MyMapView<SPAN class="punctuation token">.</SPAN>Map<SPAN class="punctuation token">.</SPAN>Basemap<SPAN class="punctuation token">.</SPAN>BaseLayers<SPAN class="punctuation token">;</SPAN>
myLayerCollection<SPAN class="punctuation token">.</SPAN><SPAN class="token function">RemoveAt</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="number token">0</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN>
<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

I hope this helps.

-Don

MarkCederholm

After revisiting the issue, I've determined that while ArcGIS Pro has no trouble re-importing MMPKs that I create, there seem to be some bugs and/or compatibility issues with Runtime. These are the three issues I'm running into:

Definition queries are not being honored
Labels do not display by default if enabled in the MMPK
Layers symbolized on multiple fields will not appear in the map

While the first two seem like actual bugs, the third may simply be a feature that's not yet supported. Esri did create a bug number (BUG-000102308 ) but I don't think it's worded well: it's not the MMPK itself that has problems, but the way Runtime is creating a map from it.

MarkCederholm

I've been explicitly setting the extent, and even when it's zoomed WAY out it makes no difference.

MichaelBranscomb

Hi Mark,

Have you tried setting the extent of your map before creating the mmpk?

http://pro.arcgis.com/en/pro-app/tool-reference/data-management/create-mobile-map-package.htm

"If an extent is not specified, the visible extent of your map will be used to define the area of interest and consolidate only those features that intersect that extent."

Cheers

Mike

MarkCederholm

FYI, I was able to work around the pan/zoom issue by moving the layers to a new map instead of just assigning the MMPK map to the mapview. However, not all layers are present when I try to grab them, which is a head-scratcher. I may need to get tech support involved with this one.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.