Rust API and integration
Use the matched sqs-map core source revision for Rust integration. These crates are workspace/path dependencies, not a claimed published crates.io package. Rust/renderer capabilities share the same source/layer/camera/state semantics as the documented C/WASM bindings; platform graphics and host resources retain their explicit boundaries.
| Crate | Purpose |
|---|---|
| sqs-map | Map sessions, camera, sources/layers, styles and shared media/playback |
| sqs-map-render | wgpu rendering and scene primitives |
| sqs-map-camera | Shared camera math without application UI |
| sqs-geo | Portable geometry and GeoJSON types |
| sqs-map-capi / sqs-map-wasm | Native ABI and browser bindings |
Generate the actual public Rust signatures/examples from the matched core checkout:
cargo doc --locked -p sqs-map -p sqs-map-render -p sqs-map-camera -p sqs-geo --no-deps
Open target/doc/sqs_map/index.html. Rustdoc is generated locally from source and can be checked with cargo test --doc; C/SDK declarations are not substitutes for its Rust ownership/lifetime rules.
Matching standalone source examples:
Version/capability index · C ownership and host resources · Scenes/media limits
The core contains no application UI, HTTP client or GDAL dependency. Native applications inject resource transports and rendering integration; browser/WASM uses its matched SDK host. Device validation and formal distribution remain separate from Rust compilation.