[gdal-dev] WCS driver

[Peter Baumann]

On 10/23/2017 05:31 PM, Ari Jolma wrote:
>
>
> Peter Baumann kirjoitti 23.10.2017 klo 18:01:
>> Hi all,
>>
>> splendid idea! Anybody who feels like working on WCS 2 support, feel free to
>> contact me or my group for any sort of explanations sought (I am the spec writer
>> of the coverages, admittedly). Note that the Coverage Implementation Schema
>> (CIS) 1.1 is out.  Maybe this is a good starter:
>> http://external.opengeospatial.org/twiki_public/CoveragesDWG/WebHome .
>
> "universe of optional extensions"
>
> sounds like a fun software development project :)

indeed - you can start with the Core (and even there specialize, cf CIS 1.1
conformance class modularization) and then can add support for extensions one by
one, whenever you feel like :)

>
> In short, how well do you see WCS 2 / the coverage model fits GDAL data model?
> It's not just raster anymore, right?

coverages are a strict superset of rasters, and they can be nD. But an
implementation does not need to support all cases.

>
> I guess the basic question is that do you think the existing WCS driver is not
> an appropriate starting point?

as said, I do not know the code, maybe it can be reused to some large part as
the WCS Core functionality in the end still is subsetting. But a careful check
for semantics (especially corner cases) is certainly appropriate.

>
> In any case I don't have at this point any real funding / time for this so I'd
> start incrementally and just reading the capabilities response for coverage
> list is enough. But, I see the importance.
>
> Ari
>
>>   I' be
>> most happy to see GDAL WCS2-enabled!
>>
>> cheers,
>> Peter
>>
>>
>> On 10/23/2017 12:19 PM, Even Rouault wrote:
>>> Hi Ari,
>>>
>>>> It seems to me that the WCS driver could benefit from some love.
>>> That would be a good initiative!
>>>
>>> In the wished feature list, I could add:
>>>
>>> * improve test coverage, which is really low currently:
>>> https://rawgit.com/rouault/gdalautotest-coverage-results/master/coverage_html/frmts/wcs/wcsdataset.cpp.gcov.html
>>>
>>> One issue we have for testing is the lack of stable & reliable servers.
>>> One potential way of addressing this is to use a local HTTP server, like I
>>> did recently with the /vsis3/ (and similar)
>>> subsystems, where you can add stub endpoints. An extra advantage is that you
>>> can also easily test error situations.
>>> See
>>> - example of server start and end
>>>     https://trac.osgeo.org/gdal/browser/trunk/autotest/gcore/vsis3.py#L126
>>>        https://trac.osgeo.org/gdal/browser/trunk/autotest/gcore/vsis3.py#L1906
>>> - example of installation of HTTP answers to expected requests:
>>>         https://trac.osgeo.org/gdal/browser/trunk/autotest/gcore/vsis3.py#L1258
>>>
>>> * WCS 2.0 support
>>>
>>>
>>> Even
>>>
>
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/gdal-dev

-- 
Dr. Peter Baumann
 - Professor of Computer Science, Jacobs University Bremen
   www.faculty.jacobs-university.de/pbaumann
   mail: p.baumann at jacobs-university.de
   tel: +49-421-200-3178, fax: +49-421-200-493178
 - Executive Director, rasdaman GmbH Bremen (HRB 26793)
   www.rasdaman.com, mail: baumann at rasdaman.com
   tel: 0800-rasdaman, fax: 0800-rasdafax, mobile: +49-173-5837882
"Si forte in alienas manus oberraverit hec peregrina epistola incertis ventis dimissa, sed Deo commendata, precamur ut ei reddatur cui soli destinata, nec preripiat quisquam non sibi parata." (mail disclaimer, AD 1083)