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

HY - intersectsCurve test seems to produce invalid gml:posList #236

Closed
robblis opened this issue Aug 24, 2022 · 8 comments · Fixed by #243
Closed

HY - intersectsCurve test seems to produce invalid gml:posList #236

robblis opened this issue Aug 24, 2022 · 8 comments · Fixed by #243
Assignees
Labels
Projects
Milestone

Comments

@robblis
Copy link

robblis commented Aug 24, 2022

Hi OGC Validator Team,

We are testing our HY feature services.

We see the following test failure regarding Spatial Filter > intersectsCurve test.

The POST Body is the following...

<wfs:GetFeature xmlns:wfs="http://www.opengis.net/wfs/2.0" count="10" service="WFS"
version="2.0.0">
<wfs:Query xmlns:ns21="http://inspire.ec.europa.eu/schemas/hy-p/4.0"
typeNames="ns21:ShorelineConstruction">
<fes:Filter xmlns:fes="http://www.opengis.net/fes/2.0">
fes:Intersects
<fes:ValueReference xmlns:tns="http://inspire.ec.europa.eu/schemas/hy-p/4.0">tns:geometry</fes:ValueReference>
<gml:LineString xmlns:gml="http://www.opengis.net/gml/3.2" gml:id="d1e1"
srsName="urn:ogc:def:crs:EPSG::4258">
gml:posList54.3 9.66 54.3 9.66</gml:posList>
</gml:LineString>
</fes:Intersects>
</fes:Filter>
</wfs:Query>
</wfs:GetFeature>

It seems the gml:posList is not correct with both Lat Lon values being identical. (i.e. 54.3 9.66) which causes an error when requesting the feature.

The GetCapabilities URL is: https://inspiredemo.esri.com/arcgis/rest/services/A4IGDS/GeoDataServer/exts/InspireFeatureDownload/service?VERSION=2.0.0&SERVICE=WFS&REQUEST=GetCapabilities&STOREDQUERY_ID=&LANGUAGE=&TYPENAMES=&MAXFEATURES=&COUNT=&f=image

I've attached the report files.

Thanks for any help,
Robert

HY_WFS_Test_s0038.zip

@dstenger
Copy link
Contributor

Thank you for reporting.
We will do further investigation.

@dstenger dstenger added this to To do in CITE via automation Aug 25, 2022
@dstenger dstenger moved this from To do to In progress in CITE Aug 25, 2022
@dstenger dstenger moved this from In progress to To do in CITE Aug 25, 2022
@dstenger dstenger moved this from To do to In progress in CITE Sep 29, 2022
@bpross-52n
Copy link
Contributor

@robblis The service is currently not reachable. Could you provide the service again?

@robblis
Copy link
Author

robblis commented Oct 6, 2022

Hi @bpross-52n,
Our apologies, the service is back online.

@dstenger dstenger added the bug label Oct 20, 2022
@bpross-52n bpross-52n linked a pull request Nov 2, 2022 that will close this issue
@dstenger dstenger assigned dstenger and unassigned bpross-52n Nov 3, 2022
@dstenger dstenger moved this from In progress to To verify in CITE Nov 3, 2022
@dstenger dstenger added this to the 1.39 milestone Nov 3, 2022
@dstenger
Copy link
Contributor

@robblis We created a fix for your problem. Is it possible to bring the service back online so that we can verify if the fix solves your reported problem?

@robblis
Copy link
Author

robblis commented Nov 14, 2022

Hi @dstenger ,

The service is back online.

Thanks,
Robert

dstenger added a commit that referenced this issue Nov 15, 2022
CITE automation moved this from To verify to Done Nov 15, 2022
@dstenger
Copy link
Contributor

@robblis Thank you!
A functional test was successful and I merged the pull request.
We will install a new release of this test suite on Beta (https://cite.ogc.org/te2/) in the coming weeks.

@robblis
Copy link
Author

robblis commented Nov 16, 2022

Hi @dstenger ,
Thanks for the fix. Please let me know when the new release is on Beta.

Robert

@dstenger
Copy link
Contributor

@robblis We just updated Beta (https://cite.ogc.org/te2/) which now contains the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
CITE
  
Done
Development

Successfully merging a pull request may close this issue.

3 participants