Skip to content

feat(map): pass geometryName and geometryType to SITNA - #217

Merged
fjlopez merged 2 commits into
devfrom
feat/wfs-geometry-options
Oct 24, 2026
Merged

fjlopez merged 2 commits into
devfrom
feat/wfs-geometry-options

Conversation

@fjlopez

@fjlopez fjlopez commented Oct 24, 2026

Copy link
Copy Markdown
Contributor

Why

SITNA needs the geometry property the administrator marked. A specific GML type should stay with DescribeFeatureType. An explicit type is sent only for generic Geometry.

What changed

  • Adding a WFS layer passes geometryName when the profile publishes one.
  • geometryType is set only when the profile publishes preferredGeometryType.
  • The identify table skips a feature-information field whose format is Geometry.

Scope

Covers WFS layer options and the identify table. Leaves GeometryCollection and name-only geometry for later work.

Blast Radius

WFS layers added from the catalog or used as a base layer. Layers without a published geometry name are unchanged.

Verification

  • A prior layers-form run passed 54 tests. Viewer specs for this behavior are in the branch.
  • The changelog immutability script passed in a prior check.
  • Front and backend images were healthy in that prior check.

A WFS layer uses the published property name. geometryType is set
only when the profile publishes a preferred geometry type.
The import belongs after the virtual WMS capabilities import.
@fjlopez
fjlopez merged commit 1deac8f into dev Oct 24, 2026
3 checks passed
@fjlopez
fjlopez deleted the feat/wfs-geometry-options branch October 24, 2026 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant