You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit a29bd9c
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: README.md
+25-8Lines changed: 25 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,7 +129,7 @@ node examples/stac-query.js
129
129
130
130
The library includes support for the [OGC API — Connected Systems](https://ogcapi.ogc.org/connectedsystems/) standard ([Part 1: Feature Resources](https://docs.ogc.org/is/23-001/23-001.html), [Part 2: Dynamic Data](https://docs.ogc.org/is/23-002/23-002.html)). This standard extends the OGC API family into the IoT/sensor domain, providing a REST API for discovering and querying sensor systems, deployments, datastreams, observations, commands, and related resources.
131
131
132
-
CSAPI is available as an **opt-in sub-path export**, meaning it is only included in your production bundle if you explicitly import it.
132
+
CSAPI remains behind an **opt-in module boundary**. The preferred `endpoint.csapi(...)` facade loads it dynamically when needed; parsers and the advanced factory are also available from the `@camptocamp/ogc-client/csapi` sub-path.
133
133
134
134
### If you don't need Connected Systems
135
135
@@ -139,27 +139,44 @@ Nothing changes. Use the library exactly as before:
The `createCSAPIBuilder()` factory function connects to the endpoint and discovers available CSAPI resources. The returned `CSAPIQueryBuilder` provides methods for all 9 resource types: systems, deployments, sampling features, procedures, properties, datastreams, observations, control streams, and commands.
160
+
The returned `CSAPIQueryBuilder` provides methods for all 9 resource types: systems, deployments, sampling features, procedures, properties, datastreams, observations, control streams, and commands.
161
+
162
+
Advanced consumers who already hold a collection descriptor and a discovered resource-URL map can use the pure factory directly:
Unlike `endpoint.csapi(...)`, `createCSAPIBuilder(collection, resourceUrls)` performs no discovery or network I/O. The endpoint facade is the preferred entry point for normal consumers.
162
179
163
180
### Why a separate import path?
164
181
165
-
The OGC Connected Systems standard is large — it spans 9 resource types across 2 specification parts with multiple response formats (GeoJSON, SWE Common, SensorML). By isolating CSAPI behind a sub-path export, users who only need WMS/WFS/WMTS/etc. don't pay the bundle-size cost for functionality they're not using. Modern bundlers (Webpack 5+, Vite, Rollup, esbuild) handle this automatically.
182
+
The OGC Connected Systems standard is large — it spans 9 resource types across 2 specification parts with multiple response formats (GeoJSON, SWE Common, SensorML). By isolating CSAPI behind a dynamic boundary and sub-path export, users who only need WMS/WFS/WMTS/etc. don't pay the bundle-size cost for functionality they're not using. Modern bundlers (Webpack 5+, Vite, Rollup, esbuild) handle this automatically.
0 commit comments