Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed LatLongBoundingBox in WFS 1.0.0 capabilities to use SRS of FeatureType #697

Merged
merged 1 commit into from
Aug 17, 2016

Conversation

dstenger
Copy link
Contributor

@dstenger dstenger commented May 4, 2016

Currently, the LatLongBoundingBox of a FeatureType is always exported in EPSG:4326 in WFS 1.0.0.
If the SRS of a FeatureType differs from EPSG:4326, the LatLongBoundingBox should be exported in that SRS (defined in WFS 1.0.0 Specification; Chapter 12.3.5).

Excerpt of WFS 1.0.0 Specification:

The LatLongBoundingBox element is used to indicate the edges of an
enclosing rectangle in the SRS of the associated feature type. Its purpose is
to facilitate geographic searches by indicating where instances of the
particular feature type exist. Since multiple LatLongBoundingBoxes can
be specified, a WFS can indicate where various clusters of data may exist.

This fix corrects this behaviour in WFS 1.0.0 and exports LatLongBoundingBoxes in the corresponding FeatureType SRS.

Conflicts:
	deegree-services/deegree-services-wfs/src/main/java/org/deegree/services/wfs/GetCapabilitiesHandler.java
@tfr42
Copy link
Member

tfr42 commented Aug 9, 2016

TMC votes:
[15:54] tfr42 +1
[15:54] Dirk_ +1
[15:54] copierrj +1
[15:55] lg +1
[15:55] StephanR +1

@tfr42 tfr42 added ready and removed in progress labels Aug 9, 2016
@copierrj copierrj merged commit cbdd96e into deegree:master Aug 17, 2016
@copierrj copierrj removed the ready label Aug 17, 2016
@lgoltz lgoltz deleted the fixWMS100BBox-3.4-3374 branch December 8, 2022 09:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug error issue and bug (fix)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants