Geometry cannot have Z values error when packaging a mobile map

[GWThompson]

So I am having an issue when packaging a mobile map for offline viewing. This is a package that I normally do every week, but just recently I have started getting the Z value error

unfortunately the error message isn't very helpful, and the log doesn't show much either

Through trial and error I narrowed it down to one layer, and checking out the layer it doesn't have Z or M values enabled, yet I am still getting the error

I've tried creating a new feature class and copying records over, tried deleting the last 2 months of new/edited records. I've ran the repair geometry tool which fixed some lines with short sections, and one null geometry, but still did not solve the problem.

Any ideas???

[EgorNozdrya]

For me, fix was to delete all online hosted feature service layers from the map/layer before packaging (or export 'em to file geodatabase first). In my case error message was completely misleading and issue has nothing to do with Z value.

ESRI Support reply was (though fix described did not work for me):
"Thank you for the update! This issue is associated with a known bug (BUG-000167727). This defect is currently in review status, and our team is actively investigating the issue. I will attach the defect to your case and you will be able to get updates on the defect from your My Esri Portal (My Esri > Support > Bugs and Enhancements).

I sincerely hope that this defect does not disrupt your operations. If you have any further questions or need additional assistance, please feel free to reach out."

[BrianHall7]

This just fixed the issue for me. Re-sourced a boundaries layer from the ArcOnline-hosted version to a local geodatabase version. I was then able to publish.

[Miralem_Zeljo]

When is this issue getting resolved? Why would we not be able to package map with 3d layers or z enabled features?

[RoanokeDave]

I went through my layers and moved them one by one to a new map, and made a mobile map package and discovered which one is causing this. It's my parcels layer, so I can't really re-make that layer very easily. The Z values are inactive and the elevation is set to ground - I don't know where else to look for anything related to a Z value. What I MAY try next is to write a model that will export all of the layers to a local GDB with the Z values disabled, make the mobile map package, then delete the copies. 

[Miralem_Zeljo]

Yeah. that is really frustrating. We had this issue when we were packaging layers or project package. This is really inconvenient especially if you have multiple layers with Z values. I hope esri gets this addressed quick. 

[Miralem_Zeljo]

By the way, we have this problem with  packaging standard map as well.

[RoanokeDave]

I feel like something Esri did as an enhancement cause this unintended consequence, because last October I made all the mobile map packages with this exact data and it worked fine. 

[Jeremy_Z]

I was working on an update for BLM's National Recreation MMPK system and ran into this same problem yesterday. Took all day to figure out what happened and how to work around it. Essentially, I changed a layer, and added two new layers, so I knew it had to be one of these.

We exported the suspect layer by itself, and it worked, and none of the new layers showed Z or M values enabled or present in the Attribute Table. What we did find though, the GNIS dataset from USGS has a vertical reference system defined for it.

PROJECT! Re-Projecting the data didn't work, for some reason we kept getting an error that it couldn't begin writing, no matter what settings we used. In the end, I created a new GDB, with a feature class in it in Web Mercator, and then used the IMPORT function to bring in the affected data without the vertical reference.

I imported my symbology from a .lyrx file I made, and now can export again.

[SCCOGGIS]

Same Problem - never used to run into these issues, or at least the error message was more clear.

[RoanokeDave]

In a discussion with a colleague, I was told of another bug with z-values. It seems that if you have a multi-part true curve there are issues with it not being z-aware - and our issue seems to be if it IS z-aware:  

BUG-000170356: Unable to modify hosted feature layer with multipart true curves https://lnkd.in/gYSKqpu7

BUG-000175572: 'Geometry cannot have Z values' error returned when attempting to edit the geometry (Move, Rotate, etc.) of ArcGIS Online hosted feature layers that are not z-aware

Is it possible that the addition of true curves was the trigger that did something to the z-value processing that caused the mobile map package error?