create
Create a renderable layer for one WFS feature type. Capabilities are fetched from the server (or supplied via serviceMetadata), an output format is negotiated, and the GetFeature response is decoded into Renderables.
Parameters
WFS service address
WFS feature type name to be requested
Optional WFS capabilities XML string to avoid online capabilities request
Optional layer display name
Optional bounding box filter (BBOX); defaults to the feature type's WGS84BoundingBox
Optional limit on the number of features fetched (translated to the WFS 2.0 count parameter)
Optional CQL_FILTER expression evaluated server-side (GeoServer / MapServer / QGIS Server extension)
Optional callback invoked once per feature with the created renderable as this and the feature's properties as the argument — use it to style placemarks/paths/polygons from server-side attributes. Works uniformly for the GeoJSON and GML decode paths.
Optional WFS 2.0 page size. When set the factory issues repeated GetFeature requests with STARTINDEX, accumulating into a single layer, until the server returns a short page or maxFeatures is reached. Ignored for WFS 1.1.0 endpoints (the spec lacks STARTINDEX before 2.0); pass maxFeatures alone for those.
Optional HttpClientConfig customizer applied to every Ktor client created here — use it to install basic auth, a bearer token, custom headers, or other request-shaping behaviour required by private endpoints.