PUBLIC DATA CONSUMERS
Assets HTTP API and Resource Package v3
Use the read-only API for catalogs, coverage blocks, overlap and bounded reverse lookup. Use Resource Package v3 when you need verified MOCs and provenance offline.
INTEGRATION STATUS / VERSIONED CONTRACTS
Choose a contract, not a catch-all SDK
Astro Survey Atlas currently exposes stable HTTP, package and scan contracts. A single cross-project SDK and its long-term owner have not been defined.
CURRENT DECISION
Shared scientific Core is established; client SDK ownership remains open
MOC-Core-SDK is now the organization-level home for the offline scientific implementation. Assets publishes the verified Python wheel, Workspace consumes it, and Warehouse keeps its Java scanner compatible through conformance fixtures. A hosted cross-project client should be assigned only after its surface, version policy and real consumers are agreed.
SUPPORTED PATHS
Start from what you need to integrate
SCAN AND EXECUTION DEVELOPERS
Warehouse ScanPlan v2 and ScanRequest
Use Warehouse when you need bounded local, S3 or OSS enumeration, spatial extraction, Kubernetes execution status, current file/coverage indices or scan evidence.
USER DATA AND WORKFLOWS
Workspace API and installed public packages
Use Workspace for user assets, connectors, local scans, workflows and user MOCs. It installs verified Assets packages and can optionally submit a namespace-local Warehouse scan.
SHARED SCIENTIFIC LIBRARY
astro-survey-moc-core 1.0.0
MOC-Core-SDK deterministically builds and validates IVOA FITS MOCs, fixed-order projections and Resource Package v3 archives from locked local inputs. Assets owns the public release workflow, Workspace installs the wheel, and Warehouse uses shared fixtures to keep its Java implementation compatible. It is not a hosted service or a general client for all three projects.
python3 -m astro_survey_moc_core.cli --version
astro-survey-moc-core project --moc merged.fits --order 8 --output query-order8.json