@bijection/connectors/wfs entrypoint to declare OGC WFS 2.0 resources.
Availability
This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.Resources and modes
Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.
Feature type
keyset: GeoJSON keyset walk
The following example matches configurationroads.
Inferred record types
Inferred record types
Configuration: roads
Case:wfs/featureType/keyset/roads.
Connection and resource configuration are declared by this exact case.
Credential kind: wfs. Keep credential material in the private credential inventory.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
Provider guidance
Compiled declaration examples and configuration details are published in the connector reference. Setup:endpoint is the WFS service URL (for example
https://maps.example.org/geoserver/wfs) and is connection-owned; typeName
selects the feature type (typeNames). Install a wfs credential
(wfs.credential(name)); its deployment presentation (bearer, header or query
API key) authenticates requests. The connection check reads
GetCapabilities (sections=ServiceIdentification) through the host xml
codec and requires a WFS_Capabilities root naming a WFS service type.
One record per feature, keyed by featureId, the declared integer
idProperty read as an exact integer. The id must be published as a feature
property (GeoServer: expose primary keys); gml:id alone is not a key.
geometry is the GeoJSON geometry or null, published in the
WGS84 XY coordinate space (WGS84_XY_SPACE, sphere distances).
What the declaration establishes
GetFeaturewithoutputFormat=application/jsonandsrsName=urn:ogc:def:crs:OGC:1.3:CRS84, so axis order is longitude then latitude. Any reprojection is the server’s; nothing is converted, repaired or reprojected here, and geometry the 2D profile refuses (3D positions, an uncut antimeridian edge) fails admission.- A keyset walk:
sortBy=<id> ASCwithcount=<n>, and from the second page a FES 2.0filter<id> > K, whereKis the host’s last-record-key continuation. The value joined into the filter is the host’s exact integer key, so it cannot alter the filter markup. startIndexis not used: it is an offset the guest would choose, which the host cannot verify, over an ordering an insert or delete shifts. A response’snextlink (the GMLnextattribute, or a GeoJSONlinksmember some servers add) cannot be followed either: a records listing has no retained next-page capability; that capability is admitted only for traversal and resource listings.- The reader refuses keys that are not strictly ascending after the
continuation (a server without the Sorting conformance class, or one that
ignored the filter), geometry of an undeclared type, and a page larger than
count.
What it does not establish
WFS has no change feed: this is a periodic re-walk of the current features, never a change history. Coverage isnone: a completed walk proves the values
each page returned at the moment it was read, is not a snapshot, and never
withdraws a feature it did not see. Server-side access rules and layer
filters narrow results silently.
A watermark mode over a timestamp property (ResumeSource::MaximumField) is
not provided. Its continuation lives within one pass, so each pass still starts
from the beginning and saves nothing over the id keyset; and because its bound
is inclusive and advances only when the page maximum grows, more than count
features sharing one timestamp end the pass early. Change-only polling needs a
position retained across passes, which the record-observation protocol does
not have.
GML output is not built. The xml codec decodes elements into declared
objects and never into numbers, so GML coordinates could only be retained as
text, not as a profile geometry, and GML’s next paging is a provider URL the
records contract cannot follow. Hosted qualification against a real server has
not been run.
Provider references
Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.Source and evidence
Canonical connector source, native analysis and check receipts. Connector artifact:905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305.
The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.