search

opengeospatial / ets-ogcapi-features10

Public Repository for the OGC API - Features Compliance Test Suite
Other
16 stars 6 forks source link

Bounding box numberMatched test failures due to loss of precision in extent coordinates #239

Open code-akki opened 1 month ago

code-akki commented 1 month ago

Describe the bug The precision of coordinates (> 7 decimals) returned in the actual extent of FeatureResponse is rounded off to 7 digits by the compliance test which leads to inconsistency in the response returned by the _validateFeaturesWithBoundingBoxResponseNumberMatched. The round off might be the consequence of this.

The extent returned in the featureResponse is (-7.557159806905192, 49.76680723514262, 1.112473832170855, 57.70488356766183) [see Parameter No. 1 in the image below] is rounded off to (-7.5571598,49.7668072,1.1124738,57.7048836) [see Parameter No. 2 in the image below]

The above issue is not the same as the one mentioned in #188, but rather due to the truncation of digits during a round-off. The missing points fall just outside the bounding-box because the extent is rounded-off.

To Reproduce Steps to reproduce the behavior:

  1. Test against our test server

Expected behavior NA

Screenshots ogc_compliance_error_1

Additional context

dstenger commented 1 month ago

Thank you for reporting. We will do further investigation.