topic Re: 100.8: New MMPK Issue in .NET Maps SDK Questions

100.8: New MMPK Issue

MarkCederholm — Tue, 12 May 2020 15:51:21 GMT

Heads up, looks like 100.8 has introduced a new MMPK problem, centered around GetLegendInfosAsync. As soon as I can isolate the problem and set up a working example, I'll get it off to tech support. Has anyone else seen this yet?

"Cannot call this method in this context: Object failed to load, unable to execute task."

This is only happening with a particular MMPK and not the others I work with, so I wouldn't be surprised if it's a symbology issue.

Re: 100.8: New MMPK Issue

KimberlySaballett — Tue, 12 May 2020 22:12:25 GMT

Does the same mmpk with the same code work with the 100.7 release?

Re: 100.8: New MMPK Issue

MarkCederholm — Tue, 12 May 2020 22:22:03 GMT

Yes, works fine at 100.7.

Re: 100.8: New MMPK Issue

KimberlySaballett — Tue, 12 May 2020 22:48:12 GMT

If you can provide the mmpk file I would be interested to test it.

Re: 100.8: New MMPK Issue

MarkCederholm — Tue, 12 May 2020 23:03:21 GMT

It's big, about 600M. I've been busy with other issues today, but tomorrow I'll see if I can come up with a smaller, simpler example.

Re: 100.8: New MMPK Issue

MarkCederholm — Wed, 13 May 2020 18:55:03 GMT

FYI, I was able to trace the error to two empty annotation classes. However, there's another empty annotation class, and also other annotation classes with no problems. I created a small MMPK with just a few features, and a simple Visual Studio project that duplicates the problem. Attached.

Re: 100.8: New MMPK Issue

KimberlySaballett — Wed, 13 May 2020 23:28:41 GMT

I was able to reproduce the issue with your annotation layers but not with my own empty annotation layers. I'm thinking the issue is originating somewhere in how the annotation layers were created. Do you know of any differences in how yours that are giving the error were created compared to how the one you have that works was created?

I did note that yours had a lyr.MinScale and lyr.MaxScale of "NaN" while mine were 0 and that yours has a red font symbology embedded?

Re: 100.8: New MMPK Issue

MarkCederholm — Thu, 14 May 2020 14:04:46 GMT

I've been scratching my head about it; I'm dealing with bookoo layers over multiple MMPKs, and all I did was set them up in manually Pro to match the original ArcMap MXDs, because direct imports in earlier versions of Pro led to other problems. I do have an open tech support case now, #02555784. I can upload Pro projects, mapx files, data, whatever through FTP for that case.

Re: 100.8: New MMPK Issue

MichaelBranscomb — Wed, 20 May 2020 19:50:22 GMT

Mark,

We still have further investigation to do, but I wanted to give you an update with what we know so far:

The problem appears to be due to the presence of an instance of the color type `CIMHSLColor` where currently we expect `CIMRGBColor`.

This information may allow you modify your map to choose an appropriate RGB color in ArcGIS Pro and repackage. Color—ArcGIS Pro | Documentation.

Specifically the layers containing symbols with this color type are the two annotation layers:

- OH Fiber Optic Anno

- UG Fiber Optic Anno

I'll update you with more information when available.

Thanks

Mike

Re: 100.8: New MMPK Issue

MarkCederholm — Thu, 21 May 2020 20:23:57 GMT

I have verified that updating the annotation class symbols works around the problem. It requires a data model change, however. Substituting a color without changing the data model doesn't work.

Re: 100.8: New MMPK Issue

MichaelBranscomb — Fri, 22 May 2020 16:36:25 GMT

Mark,

What changes were required to the data model?

Thanks

Mike

Re: 100.8: New MMPK Issue

MarkCederholm — Fri, 22 May 2020 16:48:47 GMT

Annotation symbols are defined in the annotation classes. Changing the symbol is not allowed, so new classes were created and the old ones removed.

Re: 100.8: New MMPK Issue

MarkCederholm — Sat, 11 Dec 2021 10:42:48 GMT

Here's a workaround, using ArcObjects, that can be applied to the temporary file GDB as part of an automated workflow. As far as I can tell, it is currently impossible to do the same thing in ArcGIS Pro*, so this change must be applied before the annotation feature class is upgraded.

using System.Collections.Generic;

using ESRI.ArcGIS.Carto;
using ESRI.ArcGIS.DataSourcesGDB;
using ESRI.ArcGIS.Display;
using ESRI.ArcGIS.esriSystem;
using ESRI.ArcGIS.Geodatabase;

namespace UpdateAnnoSym
{

	public static class AnnoHelper
	{

		public static void UpdateAnno(string sWorkspacePath, string sAnnoClass)
		{

			// Open workspace and annotation class
			// [Assumes a file GDB]

			IWorkspaceFactory pWSF = new FileGDBWorkspaceFactoryClass();
			IWorkspace pWS = pWSF.OpenFromFile(sWorkspacePath, 0);
			IFeatureWorkspace pFWS = pWS as IFeatureWorkspace;
			IFeatureClass pFC = pFWS.OpenFeatureClass(sAnnoClass);

			// Get the class extension

			object ext = pFC.Extension;
			IAnnotationClassExtension pAnnoExt = ext as IAnnotationClassExtension;

			// Get symbol collection and loop through symbols

			bool bUpdated = false;
			ISymbolCollection pSC = pAnnoExt.SymbolCollection;
			Dictionary<int, ISymbol> SymbolTab = new Dictionary<int, ISymbol>();
			pSC.Reset();
			while (true)
			{

				// Check text symbol for HSL color definition

				ISymbolIdentifier pSI = pSC.Next();
				if (pSI == null)
					break;
				ISymbol pSym = pSI.Symbol;
				ITextSymbol pTextSym = pSym as ITextSymbol;
				IColor pCol = pTextSym.Color;
				if (!(pCol is IHlsColor pHSL))
					continue;

				// Replace with RGB color

				int iID = pSI.ID;
				IClone pClone = pSym as IClone;
				pTextSym = pClone.Clone() as ITextSymbol;
				int iRGB = pHSL.RGB;
				IRgbColor pRGB = new RgbColorClass() { RGB = iRGB };
				pTextSym.Color = pRGB;
				SymbolTab[iID] = pTextSym as ISymbol;
				bUpdated = true;

			}
			if (!bUpdated)
				return;

			// Update annotation classes

			IAnnotateLayerPropertiesCollection pAPC = pAnnoExt.AnnoProperties;
			int iCount = pAPC.Count;
			for (int i = 0; i < iCount; i++)
			{
				pAPC.QueryItem(i, out IAnnotateLayerProperties pAnnoProp, out IElementCollection pPlaced, out IElementCollection pUnplaced);
				ILabelEngineLayerProperties pLabelProp = pAnnoProp as ILabelEngineLayerProperties;
				int iID = pLabelProp.SymbolID;
				if (!SymbolTab.ContainsKey(iID))
					continue;
				pLabelProp.Symbol = SymbolTab[iID] as ITextSymbol;
			}

			// Update symbol collection
			// [Not really necessary?]

			ISymbolCollection2 pSC2 = pSC as ISymbolCollection2;
			foreach (int iID in SymbolTab.Keys)
				pSC2.Replace(iID, SymbolTab[iID]);

			// Save changes

			IAnnoClassAdmin3 pAdmin = pAnnoExt as IAnnoClassAdmin3;
			pAdmin.UpdateProperties();

		}

	}
}
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

*Feel free to vote up this idea if you agree with it: Geoprocessing Toolset for Creating and Manipulating Annotation Feature Classes