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
GetCoverage_TemporalSubset_TimePeriod_With_Resolution has problem #72
Comments
Thank you for reporting. I agree with your conclusion that the time format should be as defined in specification OGC 07-067r2:
However, the test retrieves the value of Code: ets-wcs11/src/main/scripts/ctl/GetCoverage.xml Line 4095 in 9af4849
ets-wcs11/src/main/scripts/ctl/GetCoverage.xml Line 4120 in 9af4849
@greatzzk Unfortunately, I cannot access your test service but I assume that it returns an invalid time format in element BeginPosition (please check XPath in referenced code) when requested via DescribeCoverage. |
@dstenger thank you! |
@greatzzk Is this issue still occurring? |
@ghobona yes it is still occurring |
@ghobona are you able to reproduce the problem with my service? |
@greatzzk Thank you for providing the endpoint. Yes, we are able to reproduce the problem. |
A pull request solving the problem was created: #73 |
thanks. let me know when the issue is verified on te2 so that i can turn off the aws instance. |
can this be deployed to te2 so that i can verify the issue? |
@greatzzk We will create a new Beta release within coming week (by October 31). An announcement will be sent to the cite-forum mailing list. |
The test is to verify that when a GetCoverage request with a TimePeriod with resolution is submitted, the response is not an exception.
In my test, after describe coverage, it is making get coverage with the following request:
http://myserver:6080/arcgis/services/mynetcdf_111/ImageServer/WCSServer?&request=GetCoverage&identifier=mynetcdf&Format=image/GeoTIFF&service=WCS&BoundingBox=0,0,400,611,urn:ogc:def:crs:OGC::imageCRS&TimeSequence=2013-1-17T00:00:00Z/2013-5-17T00:00:00Z/P1D&version=1.1.1
The problem is at Time Sequence parameter. The parameter the test sends doesn't follow iso8601 time spec.
Instead of using 2013-1-17T00:00:00Z/2013-5-17T00:00:00Z/P1D, it should be using 2013-01-17T00:00:00Z/2013-05-17T00:00:00Z/P1D
The text was updated successfully, but these errors were encountered: