Current provider documentation
The guides behind
the capabilities.
Start with the P1 contracts, configure an approved source, and qualify the target environment. Full guides are published here with the website, so visitors can read them without a GitLab account.
Scope: A read-only provider with locally tested core capabilities. ArcGIS 12.1 Linux, production cloud accounts and operational certification remain release gates. Earlier research documents are not deployment guidance.
Start and configure
Provider overview
Supported source types, current scope, local execution and core boundaries.
Read the overview →Quick start
Install the dependencies and run the included sample locally.
Start locally →Configuration
Declare sources, geometry, CRS, approved schemas, budgets and authentication.
Configure the provider →Query and data contracts
P1 capabilities and migration
The supported query subset, projections, field mapping, freshness and worker behavior.
Read the P1 contracts →Diagnostic API
Source, schema and query endpoints, health checks and protected metrics.
Read the API reference →Approved sample configuration
A CSV point source with pass-through queries, strict fields and local stat freshness.
Inspect the example →Deploy and operate
ArcGIS 12.1 Linux certification
Use the matching CDF scaffold, package the adapter and record staging acceptance evidence.
Follow the certification procedure →Operations and capacity
Preflight, source freshness, load measurements, queue recovery and monitoring.
Read the runbook →Container and Kubernetes deployment
Configuration, Secret references, rollout, rollback and environment checks.
Read deployment guidance →CloudFS compatibility
Read-adapter scope, provider credentials, pinned-engine build gates and blocked transports.
Review CloudFS requirements →Grafana dashboard
Classic JSON import asset for Prometheus-backed provider and source observations.
Open the dashboard asset →Security boundaries
Diagnostic tokens, parameter limits, secret handling and platform responsibilities.
Review the security model →Evidence and development
Production-readiness review
Local checks, native compatibility evidence, known limits and external release gates.
Review the evidence →Roadmap
Delivered P1 work, required P0 qualification and recommended future capabilities.
Read the roadmap →Design decisions
Architecture, data contracts, resource ownership and implementation tradeoffs.
Read the design →