SqsMap Map SDK
Choose an integration
| Integration | Use case | Documentation |
|---|---|---|
| Native C ABI | Build a desktop or mobile host that manages lifecycle, input, resources, and frames | Native library API |
| Browser SDK | Create maps on the web with data, interaction, and Workers | Browser SDK |
| Application scripts | Automate operations inside a SqsMap script host | Script API |
Native library
Start with Native library quick start and its minimal program. Then read Host loop and resource management for threads, events, downloads, and output lifetimes.
Start with the native map C API for lifecycle, thread, and memory rules. Consult the signature reference, host resources, and host pointer input.
Browser SDK
Start with Web SDK quick start to install the npm release and run a complete Vite example.
Read the browser API reference and matching SDK distribution guide. Use matching JavaScript, declarations, and wasm files.
Shared capabilities and versions
Camera, source, style, and event guides cover shared behavior and identify supported subsets or host differences. Check developer API and platform support for current coverage.
The drawing and editing API provides shared JS SDK and C ABI sessions, point/line/polygon drawing, vertex tools, snapping, tracing and undo/redo.
sqs-map supplies rendering and map interaction. Broad local GIS format support and spatial computation belong to the spatial engine and application integration. The native library does not automatically include all application GIS script APIs.
Use declarations, headers, and examples matching the SDK or library version you deploy. A development snapshot is not a released package. Consult each guide for device support and validation scope.