feat(add-data): add OGC API - Features collections as vector layers (#1449)

* feat(add-data): add OGC API - Features collections as vector layers

GeoLibre could reach OGC feature services only through WFS, so a modern
OGC API - Features endpoint (the WFS successor: no capabilities document,
JSON-native, paged) had no way in.

Add an "OGC API - Features" source to the Add Data menu:

- `lib/ogc-api-features.ts` owns the client. `parseOgcFeaturesUrl` accepts
  whatever URL the user has in hand -- a landing page, `/collections`, a
  collection, or the full `/collections/{id}/items` URL a service's own HTML
  browser puts in the address bar -- and splits it into a base URL plus
  collection id, keeping non-OGC query params (an API key) and dropping the
  request params the builder sets itself, so a pasted `f=html&limit=10`
  cannot fight the request built on top of it.
- The items fetch follows the service's `next` links until the requested
  feature count is reached. This is the part a single request gets wrong:
  pygeoapi's demo caps `limit` at 10, so a naive fetch yields 10 of 25
  features. Paging stops on an empty page (many services advertise `next`
  even on the last one), refuses a `next` that leaves the service's origin,
  and shares one deadline across every page.
- `OgcFeaturesSource` retrieves the collection list, preselects the one a
  pasted URL named, and offers optional bbox and datetime filters.
- The layer persists its request, so `Refresh` replays the same paged walk
  instead of silently shrinking to the stored first page.

The JSON fetch that works around missing CORS headers (Tauri native HTTP /
dev proxy / direct) moves to `lib/ogc-json.ts` and is now shared with the
OGC API - Tiles client, which had the only copy; it also surfaces a service's
JSON problem-document description alongside the status on a failed request.

Fixes #1446

* Address CodeRabbit review feedback

- Propagate the refreshed paging metadata for OGC API - Features layers.
  `refreshGeoJsonLayer` now returns an optional `metadata` patch, and the
  OGC branch fills it with the `numberMatched`/`truncated` from the fetch it
  just ran; LayerPanel merges it alongside `featureCount`, so a refreshed
  layer no longer reports the counts it was originally added with. The
  legacy single-page fallback deliberately sends no patch: it has no
  `numberMatched` to compare against, so leaving the stored values alone
  beats overwriting them with a guess.
- Spell the default layer name "OGC API - Features Layer", matching the
  hyphenated official name every other new string already uses.

Author: giswqs

apps/geolibre-desktop/src/components/layout/AddDataDialog.tsx

@@ -14,6 +14,7 @@ import { GdbSource } from "./add-data/sources/GdbSource";
 import { GeoRssSource } from "./add-data/sources/GeoRssSource";
 import { GpxSource } from "./add-data/sources/GpxSource";
 import { MbtilesSource } from "./add-data/sources/MbtilesSource";
+import { OgcFeaturesSource } from "./add-data/sources/OgcFeaturesSource";
 import { OgcVectorTilesSource } from "./add-data/sources/OgcVectorTilesSource";
 import { PhotosSource } from "./add-data/sources/PhotosSource";
 import { PostgresSource } from "./add-data/sources/PostgresSource";
@@ -64,6 +65,8 @@ function renderSource(
       return <WfsSource />;
     case "wmts":
       return <WmtsSource />;
+    case "ogc-features":
+      return <OgcFeaturesSource />;
     case "ogc-vector-tiles":
       return <OgcVectorTilesSource />;
     case "gpx":

apps/geolibre-desktop/src/components/layout/add-data/apply-service.ts

@@ -26,6 +26,7 @@ import type { MapController } from "@geolibre/map";
 import type { ArcGISLayerType, ArcGISSourceType } from "@geolibre/plugins";
 import type { FeatureCollection } from "geojson";
 import type { RefObject } from "react";
+import { OGC_FEATURES_SOURCE_KIND } from "../../../lib/ogc-api-features";
 import type { ResolvedXyzTileUrl } from "../../../lib/xyz-url";
 import {
   attributionForTileUrl,
@@ -295,6 +296,63 @@ export function buildWfsGeoJsonLayer(params: WfsLayerParams): GeoLibreLayer {
   };
 }
 
+// --- OGC API - Features ----------------------------------------------------
+
+export interface OgcFeaturesLayerParams {
+  name: string;
+  /** The first page's `/items` request URL, replayed on refresh. */
+  itemsUrl: string;
+  data: FeatureCollection;
+  baseUrl: string;
+  collectionId: string;
+  maxFeatures: number;
+  bbox?: string;
+  datetime?: string;
+  extraQuery?: string;
+  /** The server's `numberMatched`, when it advertised one. */
+  numberMatched?: number;
+  /** True when the collection holds more features than were loaded. */
+  truncated: boolean;
+}
+
+/**
+ * Builds a GeoJSON layer from fetched OGC API - Features items. The request
+ * parameters are persisted alongside the data so a refresh can replay the same
+ * paged walk rather than re-reading only the first page.
+ *
+ * @param params - The layer name, items URL, fetched data, and request metadata.
+ * @returns The constructed GeoJSON layer.
+ */
+export function buildOgcFeaturesLayer(params: OgcFeaturesLayerParams): GeoLibreLayer {
+  return {
+    ...createBaseLayer(
+      params.name,
+      "geojson",
+      {
+        type: "geojson",
+        url: params.itemsUrl,
+        service: "ogc-features",
+        baseUrl: params.baseUrl,
+        collectionId: params.collectionId,
+        maxFeatures: params.maxFeatures,
+        bbox: params.bbox || undefined,
+        datetime: params.datetime || undefined,
+        extraQuery: params.extraQuery || undefined,
+      },
+      {
+        featureCount: params.data.features.length,
+        service: "ogc-features",
+        sourceKind: OGC_FEATURES_SOURCE_KIND,
+        collectionId: params.collectionId,
+        ...(params.numberMatched !== undefined ? { numberMatched: params.numberMatched } : {}),
+        truncated: params.truncated,
+      },
+    ),
+    geojson: params.data,
+    sourcePath: params.itemsUrl,
+  };
+}
+
 // --- ArcGIS ----------------------------------------------------------------
 
 export interface ArcGISOptions {

apps/geolibre-desktop/src/components/layout/add-data/constants.ts

@@ -16,6 +16,7 @@ export type KindI18nKey =
   | "wms"
   | "wfs"
   | "wmts"
+  | "ogcFeatures"
   | "ogcVectorTiles"
   | "gpx"
   | "georss"
@@ -39,6 +40,7 @@ export const KIND_I18N_KEY: Record<AddDataKind, KindI18nKey> = {
   wms: "wms",
   wfs: "wfs",
   wmts: "wmts",
+  "ogc-features": "ogcFeatures",
   "ogc-vector-tiles": "ogcVectorTiles",
   gpx: "gpx",
   georss: "georss",
@@ -87,6 +89,11 @@ export const DEFAULT_WMTS_URL =
 // this to any EOX tile layer, however it was added.
 export const EOX_S2CLOUDLESS_ATTRIBUTION =
   'Sentinel-2 cloudless 2025 by <a href="https://s2maps.eu" target="_blank" rel="noreferrer">EOX IT Services GmbH</a> (contains modified Copernicus Sentinel data 2025)';
+// pygeoapi's public demo, the reference OGC API - Features implementation. Its
+// `lakes` collection is a small global polygon set, and the server caps `limit`
+// at 10 per page, so the sample also exercises the `next`-link paging walk.
+export const DEFAULT_OGC_FEATURES_ENDPOINT = "https://demo.pygeoapi.io/master";
+export const DEFAULT_OGC_FEATURES_COLLECTION = "lakes";
 // PDOK BGT (Dutch large-scale base map) served as OGC API - Tiles vector tiles.
 // The style document carries the source-layer names the TileJSON omits; both
 // are prefilled so the sample works out of the box (zoom into the Netherlands).