Problem
A simple map with only two ArcGIS Online service layers produces a 100k+ line layers.json file on snapshot. This makes the export unnecessarily large and slow to parse.
Expected Behavior
layers.json should contain a concise summary of layer metadata — not the full service definition or all sublayer details. For service layers (map services, feature services, etc.), we should export only the essential properties needed for CLI queries.
Suggested Approach
- Identify which fields are being serialized that cause the bloat (likely full service metadata, renderer details, or field definitions)
- Filter exported properties to a relevant subset (name, URL, type, visibility, spatial reference, etc.)
- Consider a
--full flag if users ever need the complete dump
Reproduction
- Create a new map in ArcGIS Pro
- Add two ArcGIS Online service layers
- Run a snapshot export
- Observe
layers.json is 100k+ lines
Problem
A simple map with only two ArcGIS Online service layers produces a 100k+ line
layers.jsonfile on snapshot. This makes the export unnecessarily large and slow to parse.Expected Behavior
layers.jsonshould contain a concise summary of layer metadata — not the full service definition or all sublayer details. For service layers (map services, feature services, etc.), we should export only the essential properties needed for CLI queries.Suggested Approach
--fullflag if users ever need the complete dumpReproduction
layers.jsonis 100k+ lines