Issues with Packaging Offline Areas Consistently

Question

Hi,

I've been having some issues with packaging offline areas in Field Maps both through the browser (Field Maps Designer > Offline > Map areas) and in the Android and iOS apps (Add offline area in Map options).

When I originally created the map towards the end of last year, I was able to create an offline area for it through Field Maps Designer without issue. I have since edited the map on multiple occasions, but all subsequent efforts to recreate the offline area to account for the changes have failed. I've had some success in creating offline areas through the Field Maps app, but the results are inconsistent.

In trying to diagnose the issue, I noticed the following error message was occurring in the REST endpoint of the packaging service:

"error": "{\"code\": 4, \"messageCode\": \"OffPkg_  4\", \"message\": \"Failed to get status for item ca12989e9fef467ca3675824279108e9 error Error in adding url file item Data length is more than max allowed.\", \"params\": {\"itemId\": \"ca12989e9fef467ca3675824279108e9\", \"error\": \"Error in adding url file item Data length is more than max allowed.\"}}",

The hosted feature layer the error pertains to has an item title length of 56 characters. However, this layer has been in the map since I first created it when I was able to package it successfully, and also has been taken offline through the in-app method previously.

If anyone has any ideas about what might be going wrong, I'd love to hear them!

Thanks

MACI · Answer

@MJBiazar thanks for the info - I've tried playing around with extents and levels of detail, and even with packages in the ~50MB range I'm still getting the same error as I mentioned in my initial post, so it seems that the overal package size is not the factor causing the error.

Do you know anything more about the below error?

Error in adding url file item Data length is more than max allowed.

MJBiazar · Answer

@MACI thanks for sharing the additional information. If you are creating pre-defined offline areas, as noted on our documentation, the size of the package for a web layer cannot exceed 4 GB. So if you have a really large dataset, or a lot of attachments, you should try creating smaller areas.

To answer your question, there is no hard limit on the number of features per se, the only limit would be the size of the web layer when packaged (including features and attachments).

MACI · Answer

Hi @ChristopherCounsell @MJBiazar,

Thanks for the responses - the layer throwing the error has 18 fields and around 500 features, each of which have a couple of photo attachments - the offline area is also quite large at roughly 350sqkm (although a lot of this space contains no features), which when downloaded successfully using the tiling levels of 'Building' to 'County' results in a package around 7GB in size (imagery being ~261MB of that).

Downsizing the offline area extent/choosing an area with no features/starting again with a fresh web map all seem to yield the same results - sometimes the area downloads (often then also fails to sync), but mostly it just fails.

Is there guidance around the maximum number of features with attachments that an offline area should be able to handle reliably?