What problem does it solve? Working with Parquet datasets across local files, ArcGIS Portal items, and Azure Blob or ADLS storage involves distinct tools, ownership models, and failure modes that are easy to confuse, leading to accidental public uploads, wrong-item mutations, or failed CDN-dependent deliveries. ## Core Features & Use Cases - Parquet Inspection: Run meta, schema, kv, stats, and bounded queries against local files, URLs, or Portal items, and save filtered subsets while preserving schema and metadata. - Portal Publishing: Create and replace ArcGIS Parquet Feature Layer items with explicit item IDs, generate _spatial.json metadata, and verify every mutation instead of trusting exit status. - Azure Delivery: Upload datasets to Azure Blob or ADLS, sync CDN routes, generate remote spatial metadata, and open ArcGIS Play documents. - Use Case: A GIS analyst needs to publish a counties dataset as a Parquet Feature Layer, regenerate its spatial metadata after an update, and open it in ArcGIS Play without accidentally sharing it publicly or overwriting the wrong item. ## Quick Start Inspect the attached counties.parquet file and show its geometry metadata, schema, and a few sample records using the portal CLI.
