[Geoserver-devel] Following up on geotools structured coverage grid readers proposal

GeoServer GeoServer Developer
1

Hi,
I’ve just created a new pull request that follows up the GeoTools one about structured coverage grid readers:

https://github.com/geoserver/geoserver/pull/264

The pull is split in a few commits:

  1. https://github.com/aaime/geoserver/commit/ffb91e62a40ed235e8a627c9ea633d8d44e16733

Adds support for the structured grid coverage readers in GeoServer, and prepares the land in main for the other commits by sharing a resource pool method in CatalogBuilder (that rest config then needs) and adds some test data

https://github.com/aaime/geoserver/commit/e0d28130565615ed2ec14bf31229b85fefdcdc35

Adds a number of improvements to the WCS 2.0 module that we have been working on during the last months and that build partly upon the structured grid coverage reader API

  1. https://github.com/aaime/geoserver/commit/8a7f0a49525f294f9ac7e6d5f1e65ac2dac561b9

This one adds the WCS earth observation community modules, that heavily build on the structured grid coverage API

https://github.com/aaime/geoserver/commit/527a28d7178178ca7b441459b26c42e00dcb761f

This one is the most interesting one, it adds two things:

  • support configuration of new mosaics by uploading a zip file with the mosaic config and at least one granule, and configuration of all the coverages inside of it (unless configure=none is provided, just like with geotiff sources)
  • an extension to the REST api that allows to leverage structured grid coverage readers by allowing to harvest new files into a mosaic, list the contents of a mosaic, get the feature type structure of the attributes attached to the granules, and remote selected granules from the mosaic as well

I still don’t have the commit for the documentation, but in attachment you can find a draft of it that provides a list of the new capabilities and sample outputs.
Not sure if this particular change (rest config api) warrants a proposal, but if you feel like it should I’ll make one.

Feedback welcomed :slight_smile:

Cheers
Andrea

–

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

(attachments)

structured-rest-api.pdf (239 KB)

2

On Wed, Jul 3, 2013 at 4:56 PM, Andrea Aime <andrea.aime@anonymised.com>wrote:

Hi,
I've just created a new pull request that follows up the GeoTools one
about structured coverage grid readers:

https://github.com/geoserver/geoserver/pull/264

The pull is split in a few commits:
1)
https://github.com/aaime/geoserver/commit/ffb91e62a40ed235e8a627c9ea633d8d44e16733

Adds support for the structured grid coverage readers in GeoServer, and
prepares the land in main for the other commits by sharing a resource pool
method in CatalogBuilder (that rest config then needs) and adds some test
data

4)

https://github.com/aaime/geoserver/commit/527a28d7178178ca7b441459b26c42e00dcb761f

This one is the most interesting one, it adds two things:
* support configuration of new mosaics by uploading a zip file with the
mosaic config and at least one granule, and configuration of all the
coverages inside of it (unless configure=none is provided, just like with
geotiff sources)
* an extension to the REST api that allows to leverage structured grid
coverage readers by allowing to harvest new files into a mosaic, list the
contents of a mosaic, get the feature type structure of the attributes
attached to the granules, and remote selected granules from the mosaic as
well

I still don't have the commit for the documentation, but in attachment you
can find a draft of it that provides a list of the new capabilities and
sample outputs.
Not sure if this particular change (rest config api) warrants a proposal,
but if you feel like it should I'll make one.

Feedback welcomed :slight_smile:

Hi,
any feedback? Generally speaking, the points that might need some
discussion are 1 and 4, since 2 and 3 are really hitting
community modules

Cheers
Andrea

--

Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

3

Took a quick look and provided some feedback on the pr.

···

On Fri, Jul 5, 2013 at 2:52 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Wed, Jul 3, 2013 at 4:56 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:

This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

Hi,
I’ve just created a new pull request that follows up the GeoTools one about structured coverage grid readers:

https://github.com/geoserver/geoserver/pull/264

The pull is split in a few commits:

  1. https://github.com/aaime/geoserver/commit/ffb91e62a40ed235e8a627c9ea633d8d44e16733

Adds support for the structured grid coverage readers in GeoServer, and prepares the land in main for the other commits by sharing a resource pool method in CatalogBuilder (that rest config then needs) and adds some test data

https://github.com/aaime/geoserver/commit/527a28d7178178ca7b441459b26c42e00dcb761f

This one is the most interesting one, it adds two things:

  • support configuration of new mosaics by uploading a zip file with the mosaic config and at least one granule, and configuration of all the coverages inside of it (unless configure=none is provided, just like with geotiff sources)
  • an extension to the REST api that allows to leverage structured grid coverage readers by allowing to harvest new files into a mosaic, list the contents of a mosaic, get the feature type structure of the attributes attached to the granules, and remote selected granules from the mosaic as well

I still don’t have the commit for the documentation, but in attachment you can find a draft of it that provides a list of the new capabilities and sample outputs.
Not sure if this particular change (rest config api) warrants a proposal, but if you feel like it should I’ll make one.

Feedback welcomed :slight_smile:

Hi,
any feedback? Generally speaking, the points that might need some discussion are 1 and 4, since 2 and 3 are really hitting
community modules

Cheers

Andrea

–

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime

@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it