topic Re: MMPK: Bad Symbol Rotation in .NET Maps SDK Questions

MMPK: Bad Symbol Rotation

MarkCederholm — Thu, 06 Jul 2017 16:45:12 GMT

Attached is a small MMPK, created in Pro 2.0, that demonstrates a bad symbol rotation in Runtime 100.1 [I don't recall seeing this issue in Pro 1.4.1/Runtime 100.0, but I may be wrong].

Here's how it appears imported into Pro:

And here's how it appears in Runtime:

Re: MMPK: Bad Symbol Rotation

JenniferNery — Sun, 12 Dec 2021 03:28:55 GMT

Thanks, Mark. I'm able to reproduce the issue in v100.1 and it looks like it did not render at all in v100.

Also, I find that when you opt-out advanced symbology, it renders just at it would in ArcGIS Pro. Do you mind trying the following workaround?

var mmpk = await MobileMapPackage.OpenAsync(path);
var map = mmpk.Maps.FirstOrDefault();
foreach(var layer in map.OperationalLayers.OfType<FeatureLayer>())
{
    var table = (ArcGISFeatureTable)layer.FeatureTable;
    table.UseAdvancedSymbology = false;
}
MyMapView.Map = map;‍‍‍‍‍‍‍‍

I have logged the issue so our team can investigate further.

Thanks.

Jennifer

Re: MMPK: Bad Symbol Rotation

MarkCederholm — Fri, 07 Jul 2017 21:12:01 GMT

That works for me. Thanks!

Re: MMPK: Bad Symbol Rotation

JenniferNery — Fri, 07 Jul 2017 21:13:25 GMT

No problem, I updated the workaround a bit - no need to load and clone.

Re: MMPK: Bad Symbol Rotation

MarkCederholm — Wed, 12 Jul 2017 17:39:09 GMT

Is there any way to determine the geometry of a feature layer without loading the table? I would like to be able to apply the workaround only to point layers (I have polyline layers with advanced symbology).

Re: MMPK: Bad Symbol Rotation

AnttiKajanus1 — Thu, 13 Jul 2017 09:16:46 GMT

Hi Mark, I'm not aware a way to that without loading the metadata for the table since the layer doesn't have any information about it's content before that is done. If you are using MMPKs the loading operation shouldn't be too expensive since no network calls are done at that point.

Re: MMPK: Bad Symbol Rotation

MarkCederholm — Thu, 13 Jul 2017 14:57:16 GMT

Unfortunately, I can't change the UseAdvancedSymbology setting once the table is loaded. I tried cloning the layers, closing the GDB, even opening the MMPK a second time, but in those cases I couldn't get the map to load.

Re: MMPK: Bad Symbol Rotation

AnttiKajanus1 — Sun, 12 Dec 2021 03:28:58 GMT

Does this work? it's not very pretty but after I go through UseAdvancedSymbology values on loaded event, i get thing set properly. I didn't have a service that clearly has different symbology so not sure if the correct symbols was used though.

offlineMapPackage = await MobileMapPackage.OpenAsync(offlineDataFolder);
offlineMap = offlineMapPackage.Maps.First();

var featureLayers = offlineMap.OperationalLayers.OfType<FeatureLayer>().ToList();
var featureLayer = featureLayers.First();
var gdbTable = featureLayer.FeatureTable as GeodatabaseFeatureTable;
var gdb = await Geodatabase.OpenAsync(gdbTable.Geodatabase.Path);

var pointLayers = new List<int>();
for (int i = 0; i < gdb.GeodatabaseFeatureTables.Count; i++)
{
    var table = gdb.GeodatabaseFeatureTables[i] as GeodatabaseFeatureTable;
    await table.LoadAsync();
    if (table.GeometryType == GeometryType.Point)
        pointLayers.Add(i);
}

foreach (var index in pointLayers)
{
    var table = gdbTable.Geodatabase.GeodatabaseFeatureTables[index];
    table.UseAdvancedSymbology = false;
}‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: MMPK: Bad Symbol Rotation

MarkCederholm — Thu, 13 Jul 2017 16:51:17 GMT

Nope. Still can't get the map to load. I'm using the same MMPK that I originally attached to this thread.

Re: MMPK: Bad Symbol Rotation

MarkCederholm — Thu, 13 Jul 2017 16:57:03 GMT

More info: I'm getting a FileNotFound exception at the Geodatabase.OpenAsync step.

Re: MMPK: Bad Symbol Rotation

AnttiKajanus1 — Sun, 12 Dec 2021 03:29:01 GMT

Ah, ofc. I was using an offline map and not mmpk file so you cannot access the geodatabase directly. As a workaround you need to do something like this then.

offlineMapPackage = await MobileMapPackage.OpenAsync(offlineDataFolder);
offlineMap = offlineMapPackage.Maps.First();

await offlineMap.LoadAsync();
var featureLayers = offlineMap.OperationalLayers.OfType<FeatureLayer>().ToList();
var featureLayer = featureLayers.First();
var gdbTable = featureLayer.FeatureTable as GeodatabaseFeatureTable;
var gdb = gdbTable.Geodatabase;

var pointLayers = new List<int>();
for (int i = 0; i < gdb.GeodatabaseFeatureTables.Count; i++)
{
    var table = gdb.GeodatabaseFeatureTables[i] as GeodatabaseFeatureTable;
    if (table.GeometryType == GeometryType.Point)
         pointLayers.Add(i);
}

offlineMapPackage = await MobileMapPackage.OpenAsync(offlineDataFolder);
offlineMap = offlineMapPackage.Maps.First();
featureLayers = offlineMap.OperationalLayers.OfType<FeatureLayer>().ToList();
featureLayer = featureLayers.First();
gdbTable = featureLayer.FeatureTable as GeodatabaseFeatureTable;

foreach (var index in pointLayers)
{
     var table = gdbTable.Geodatabase.GeodatabaseFeatureTables[index];
     table.UseAdvancedSymbology = false;
}‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I couldn't figure other ways to workaround with this and the solution includes opening the mmpk twice. You can clean up the approach a bit but at least it works. The code below only work directly with mmpk that only has one geodatabase inside of it so if you have multiple, then you need to add logic to iterate the layers etc. I'm not sure what we can do to make this easier but I'll log an enhancement ticket for it.(EDIT: except fix the original issue so the workaround isn't needed)

Re: MMPK: Bad Symbol Rotation

MarkCederholm — Fri, 14 Jul 2017 15:50:06 GMT

It works for a single-layer map, but in a multilayer map, only the first table is being loaded and has geometry info.

Re: MMPK: Bad Symbol Rotation

JenniferNery — Sun, 12 Dec 2021 03:29:05 GMT

Alternatively, you can load the map to get to its FeatureLayers and load their table to get GeometryType. Since UseAdvancedSymbology can only be set before table is loaded, you will need to clone the original layer and get its unloaded table and modify this property. Also, be sure to replace the original layer with cloned layer. Very similar to Antti's proposed workaround the only difference is not having to open MobileMapPackage twice and I believe you already attempted the clone.

var mmpk = await MobileMapPackage.OpenAsync(path);
var map = mmpk.Maps.FirstOrDefault();
await map.LoadAsync();
var layers = map.OperationalLayers.OfType<FeatureLayer>().ToArray();
foreach (var l in layers)
{
    await l.FeatureTable.LoadAsync();
    if (l.FeatureTable.GeometryType == GeometryType.Point)
    {
        var clone = l.Clone() as FeatureLayer;
        var table = (ArcGISFeatureTable)clone.FeatureTable;
        table.UseAdvancedSymbology = false;
        map.OperationalLayers.Remove(l);
        map.OperationalLayers.Add(clone);
    }
}
MyMapView.Map = map;‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Re: MMPK: Bad Symbol Rotation

MarkCederholm — Sun, 12 Dec 2021 03:29:08 GMT

Cloning a layer messes it up, I've discovered. For example, the definition expression goes away, and somewhere a spatial reference goes away.

I tried loading every table some time ago, but then the second time I try to load the map, it crashes. After some more playing around with Antti's approach, I finally found a way to get it to work by loading each layer rather than the table itself:

          private async Task<List<int>> GetPointLayers(string sPath, int iMapIndex)
          {
               MobileMapPackage mmpk = await MobileMapPackage.OpenAsync(sPath);
               Map map = mmpk.Maps[iMapIndex];
               Geodatabase gdb = null;
               foreach (FeatureLayer fLyr in map.OperationalLayers.OfType<FeatureLayer>())
               {
                    await fLyr.LoadAsync();
                    GeodatabaseFeatureTable gfTab = fLyr.FeatureTable as GeodatabaseFeatureTable;
                    if (gdb != null)
                         continue;
                    gdb = gfTab.Geodatabase;
               }
               await map.LoadAsync();
               List<int> PointLayers = new List<int>();
               for (int i = 0; i < gdb.GeodatabaseFeatureTables.Count; i++)
               {
                    GeodatabaseFeatureTable gfTab = gdb.GeodatabaseFeatureTables[i];
                    if (gfTab.GeometryType != GeometryType.Point)
                         continue;
                    PointLayers.Add(i);
               }
               return PointLayers;
          }
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

As Antti said, hopefully the symbology problem will be fixed in the next release.

--Mark

Re: MMPK: Bad Symbol Rotation

JenniferNery — Fri, 14 Jul 2017 16:20:42 GMT

I see, thanks for posting the workaround that worked for you. I'm able to reproduce that Clone omits DefinitionExpression when set in the original. Apparently this clone issue is already logged. Hopefully these issues you found are resolved in future versions of the API. Thanks.

If table is already loaded and you only want to do this workaround when necessary, you can add this filter.

var useworkaround = ((ArcGISFeatureTable)l.FeatureTable).LayerInfo?.DrawingInfo?.Renderer?.ToJson()?.Contains("visualVariables") ?? false;‍‍‍

Re: MMPK: Bad Symbol Rotation

MichaelBranscomb — Mon, 12 Feb 2018 21:41:39 GMT

Hi,

The original issue should now be resolved in the recent v100.2 release.

Please download the latest Visual Studio extension from ArcGIS for Developers or update your NuGet packages via the NuGet package manager.

Cheers

Mike

Re: MMPK: Bad Symbol Rotation

MarkCederholm — Tue, 23 Apr 2019 17:20:01 GMT

Looks like this problem has resurfaced in 100.5. The old 100.1 workaround fixes it.

Re: MMPK: Bad Symbol Rotation

MarkCederholm — Tue, 10 Sep 2019 20:21:59 GMT

The problem is still present in 100.6. That's just plain pathetic!

Re: MMPK: Bad Symbol Rotation

PreetiMaske — Thu, 12 Sep 2019 20:59:47 GMT

We are currently working on solidifying the symbols with visual variables. I am hopeful issues like these will get resolved as part of that work. Sorry about the inconvenience.

I tested with your test data that workaround to use simple symbols continues to work with 100.6.

Also feel free to let us know if you have other test cases for symbology that aren't working correctly.

Thanks,

Preeti

Re: MMPK: Bad Symbol Rotation

MarkCederholm — Mon, 28 Oct 2019 18:22:07 GMT

FYI, the layer clone bug is still present at 100.6