[Geoserver-devel] ImageMosaic documentation ignores DBMS index capabilities

GeoServer GeoServer Developer
,
1

I have recently been testing out various ImageMosaic functionality, and have ran into a fairly blatant error in the ImageMosaic tutorial in the GeoServer documentation (http://docs.geoserver.org/latest/en/user/tutorials/image_mosaic_plugin/imagemosaic.html):

In order to configure a new CoverageStore and a new Coverage with this plugin, an index file needs to be generated first in order to associate each granule to its bounding box. Currently we support only a Shapefile as a proper index, although it would be possible to extend this and use other means to persist the index.

(Emphasis mine)

Looking at the codebase however, I can see that there is support for other indexing stores, including PostGIS and H2.

Documentation on how to set up such an imagemosaic can be found on the GeoSolutions site at http://geoserver.geo-solutions.it/multidim/en/imagemosaic/mosaic_datastore.html

Could someone who has worked on this functionality and/or this documentation comment as to why this has not been included in the GeoServer documentation, and is only documented on the GeoSolutions site?

Thanks,

Torben Barsballe

2

On Mon, Nov 23, 2015 at 11:36 PM, Torben Barsballe <
tbarsballe@anonymised.com> wrote:

I have recently been testing out various ImageMosaic functionality, and
have ran into a fairly blatant error in the ImageMosaic tutorial in the
GeoServer documentation (
http://docs.geoserver.org/latest/en/user/tutorials/image_mosaic_plugin/imagemosaic.html
):

In order to configure a new CoverageStore and a new Coverage with this

plugin, an index file needs to be generated first in order to associate
each granule to its bounding box. *Currently we support only a Shapefile
as a proper index*, although it would be possible to extend this and use
other means to persist the index.

(Emphasis mine)

Looking at the codebase however, I can see that there is support for other
indexing stores, including PostGIS and H2.

Correct. And Oracle too.

Documentation on how to set up such an imagemosaic can be found on the
GeoSolutions site at
http://geoserver.geo-solutions.it/multidim/en/imagemosaic/mosaic_datastore.html

Could someone who has worked on this functionality and/or this
documentation comment as to why this has not been included in the GeoServer
documentation, and is only documented on the GeoSolutions site?

I find it unbelievable that someone from a company that is shipping a
GeoServer with extra functionality, that is not contributed back to
GeoServer, thinks to have the
right to call out other developers out on outdated docs, but for
functionality that is actually contributed and improved over time for
everybody's benefit.

But even without going there, just to show you a counter example, can you
tell me where in the GeoServer guide we can find the equivalent of this?
http://suite.opengeo.org/4.1/cartography/rt/barnes.html
To paraphrase, why is that documented only in the OpenGeo Suite site?

docs.geoserver.org has various bits of outdated and incomplete
documentation, if you find bits are lacking you're more than welcomed
to improve them. Or to provide help in other ways, thus freeing other devs
time for writing more docs. Don't know, answering mails on the
users list, fixing bugs found in the tracker, helping to keep the build
servers going, updating the CITE tests, and so on

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V 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

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

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

3

On Mon, Nov 23, 2015 at 3:15 PM, Andrea Aime <andrea.aime@anonymised.com>
wrote:

On Mon, Nov 23, 2015 at 11:36 PM, Torben Barsballe <
tbarsballe@anonymised.com> wrote:

I have recently been testing out various ImageMosaic functionality, and
have ran into a fairly blatant error in the ImageMosaic tutorial in the
GeoServer documentation (
http://docs.geoserver.org/latest/en/user/tutorials/image_mosaic_plugin/imagemosaic.html
):

In order to configure a new CoverageStore and a new Coverage with this

plugin, an index file needs to be generated first in order to associate
each granule to its bounding box. *Currently we support only a
Shapefile as a proper index*, although it would be possible to extend
this and use other means to persist the index.

(Emphasis mine)

Looking at the codebase however, I can see that there is support for
other indexing stores, including PostGIS and H2.

Correct. And Oracle too.

Documentation on how to set up such an imagemosaic can be found on the
GeoSolutions site at
http://geoserver.geo-solutions.it/multidim/en/imagemosaic/mosaic_datastore.html

Could someone who has worked on this functionality and/or this
documentation comment as to why this has not been included in the GeoServer
documentation, and is only documented on the GeoSolutions site?

I find it unbelievable that someone from a company that is shipping a
GeoServer with extra functionality, that is not contributed back to
GeoServer, thinks to have the
right to call out other developers out on outdated docs, but for
functionality that is actually contributed and improved over time for
everybody's benefit.

I did not intend to call out GeoSolutions on not updating the docs, but
rather verify that I am not stepping on anyone's toes by adapting this
existing content to the GeoServer docs (see below). Given how busy many of
the core GeoServer developers are, "The docs haven't been looked at since
before this functionality was added" is a perfectly valid response. Sorry
if this was not clear from my original message.
Also, the views of Boundless do not necessarily reflect my own (and vice
versa).

But even without going there, just to show you a counter example, can you
tell me where in the GeoServer guide we can find the equivalent of this?
opengeo.org
To paraphrase, why is that documented only in the OpenGeo Suite site?

Perfectly fair criticism (although the geoserver docs do give a full sld

example of a HeatMap, with the adaptation of the Transform syntax to other
rendering transforms left as an excercise to the reader). As you noted,
everyone is busy and doesn't seem to find time to update the community docs.

docs.geoserver.org has various bits of outdated and incomplete
documentation, if you find bits are lacking you're more than welcomed
to improve them. Or to provide help in other ways, thus freeing other devs
time for writing more docs. Don't know, answering mails on the
users list, fixing bugs found in the tracker, helping to keep the build
servers going, updating the CITE tests, and so on

If it is just a case of outdated docs I am happy to improve them. Given

that the content at
http://geoserver.geo-solutions.it/multidim/en/imagemosaic/mosaic_datastore.html
is the property of GeoSolutions, may I adapt the content there while
updating the GeoServer docs, or would you prefer that I merely link to that
content instead?

Torben

4

Ciao Torben,
the explanation is as usual lack of time and changing priorities.
We created that material for training purposes and then we never had
the time to contribute (portion of ) it back.

I am perfectly fine with you pushing (after adapting) some portions of
it into the GeoServer doc.

Regards,
Simone Giannecchini

GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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

-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate.
Il loro utilizzo è consentito esclusivamente al destinatario del
messaggio, per le finalità indicate nel messaggio stesso. Qualora
riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
cortesemente di darcene notizia via e-mail e di procedere alla
distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
diverse, costituisce comportamento contrario ai principi dettati dal
D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely
for the attention and use of the named addressee(s) and may be
confidential or proprietary in nature or covered by the provisions of
privacy act (Legislative Decree June, 30 2003, no.196 - Italy's New
Data Protection Code).Any use not in accord with its purpose, any
disclosure, reproduction, copying, distribution, or either
dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the
intended recipient, please contact immediately the sender by
telephone, fax or e-mail and delete the information in this message
that has been received in error. The sender does not give any warranty
or accept liability as the content, accuracy or completeness of sent
messages and accepts no responsibility for changes made after they
were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.

On Tue, Nov 24, 2015 at 1:48 AM, Torben Barsballe
<tbarsballe@anonymised.com> wrote:

On Mon, Nov 23, 2015 at 3:15 PM, Andrea Aime <andrea.aime@anonymised.com>
wrote:

On Mon, Nov 23, 2015 at 11:36 PM, Torben Barsballe
<tbarsballe@anonymised.com> wrote:

I have recently been testing out various ImageMosaic functionality, and
have ran into a fairly blatant error in the ImageMosaic tutorial in the
GeoServer documentation
(http://docs.geoserver.org/latest/en/user/tutorials/image_mosaic_plugin/imagemosaic.html):

In order to configure a new CoverageStore and a new Coverage with this
plugin, an index file needs to be generated first in order to associate each
granule to its bounding box. Currently we support only a Shapefile as a
proper index, although it would be possible to extend this and use other
means to persist the index.

(Emphasis mine)

Looking at the codebase however, I can see that there is support for
other indexing stores, including PostGIS and H2.

Correct. And Oracle too.

Documentation on how to set up such an imagemosaic can be found on the
GeoSolutions site at
http://geoserver.geo-solutions.it/multidim/en/imagemosaic/mosaic_datastore.html

Could someone who has worked on this functionality and/or this
documentation comment as to why this has not been included in the GeoServer
documentation, and is only documented on the GeoSolutions site?

I find it unbelievable that someone from a company that is shipping a
GeoServer with extra functionality, that is not contributed back to
GeoServer, thinks to have the
right to call out other developers out on outdated docs, but for
functionality that is actually contributed and improved over time for
everybody's benefit.

I did not intend to call out GeoSolutions on not updating the docs, but
rather verify that I am not stepping on anyone's toes by adapting this
existing content to the GeoServer docs (see below). Given how busy many of
the core GeoServer developers are, "The docs haven't been looked at since
before this functionality was added" is a perfectly valid response. Sorry if
this was not clear from my original message.
Also, the views of Boundless do not necessarily reflect my own (and vice
versa).

But even without going there, just to show you a counter example, can you
tell me where in the GeoServer guide we can find the equivalent of this?
http://suite.opengeo.org/4.1/cartography/rt/barnes.html
To paraphrase, why is that documented only in the OpenGeo Suite site?

Perfectly fair criticism (although the geoserver docs do give a full sld
example of a HeatMap, with the adaptation of the Transform syntax to other
rendering transforms left as an excercise to the reader). As you noted,
everyone is busy and doesn't seem to find time to update the community docs.

docs.geoserver.org has various bits of outdated and incomplete
documentation, if you find bits are lacking you're more than welcomed
to improve them. Or to provide help in other ways, thus freeing other devs
time for writing more docs. Don't know, answering mails on the
users list, fixing bugs found in the tracker, helping to keep the build
servers going, updating the CITE tests, and so on

If it is just a case of outdated docs I am happy to improve them. Given that
the content at
http://geoserver.geo-solutions.it/multidim/en/imagemosaic/mosaic_datastore.html
is the property of GeoSolutions, may I adapt the content there while
updating the GeoServer docs, or would you prefer that I merely link to that
content instead?

Torben

------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple
OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

5

Pull request for the doc update: https://github.com/geoserver/geoserver/pull/1349/files

I have adapted portions (mostly the JDBC configuration) of the GeoSolutions materials to flesh out the configuration section.

I have also added a bunch of updates based on my testing/usage of imagemosaic.

Torben

···

On Tue, Nov 24, 2015 at 6:06 AM, Simone Giannecchini <simone.giannecchini@anonymised.com> wrote:

Ciao Torben,
the explanation is as usual lack of time and changing priorities.
We created that material for training purposes and then we never had
the time to contribute (portion of ) it back.

I am perfectly fine with you pushing (after adapting) some portions of
it into the GeoServer doc.

Regards,
Simone Giannecchini

GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate.
Il loro utilizzo è consentito esclusivamente al destinatario del
messaggio, per le finalità indicate nel messaggio stesso. Qualora
riceviate questo messaggio senza esserne il destinatario, Vi preghiamo
cortesemente di darcene notizia via e-mail e di procedere alla
distruzione del messaggio stesso, cancellandolo dal Vostro sistema.
Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
diverse, costituisce comportamento contrario ai principi dettati dal
D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely
for the attention and use of the named addressee(s) and may be
confidential or proprietary in nature or covered by the provisions of
privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New
Data Protection Code).Any use not in accord with its purpose, any
disclosure, reproduction, copying, distribution, or either
dissemination, either whole or partial, is strictly forbidden except
previous formal approval of the named addressee(s). If you are not the
intended recipient, please contact immediately the sender by
telephone, fax or e-mail and delete the information in this message
that has been received in error. The sender does not give any warranty
or accept liability as the content, accuracy or completeness of sent
messages and accepts no responsibility for changes made after they
were sent or for other risks which arise as a result of e-mail
transmission, viruses, etc.

On Tue, Nov 24, 2015 at 1:48 AM, Torben Barsballe
<tbarsballe@anonymised.com> wrote:

On Mon, Nov 23, 2015 at 3:15 PM, Andrea Aime <andrea.aime@anonymised.com>
wrote:

On Mon, Nov 23, 2015 at 11:36 PM, Torben Barsballe
<tbarsballe@anonymised.com> wrote:

I have recently been testing out various ImageMosaic functionality, and
have ran into a fairly blatant error in the ImageMosaic tutorial in the
GeoServer documentation
(http://docs.geoserver.org/latest/en/user/tutorials/image_mosaic_plugin/imagemosaic.html):

In order to configure a new CoverageStore and a new Coverage with this
plugin, an index file needs to be generated first in order to associate each
granule to its bounding box. Currently we support only a Shapefile as a
proper index, although it would be possible to extend this and use other
means to persist the index.

(Emphasis mine)

Looking at the codebase however, I can see that there is support for
other indexing stores, including PostGIS and H2.

Correct. And Oracle too.

Documentation on how to set up such an imagemosaic can be found on the
GeoSolutions site at
http://geoserver.geo-solutions.it/multidim/en/imagemosaic/mosaic_datastore.html

Could someone who has worked on this functionality and/or this
documentation comment as to why this has not been included in the GeoServer
documentation, and is only documented on the GeoSolutions site?

I find it unbelievable that someone from a company that is shipping a
GeoServer with extra functionality, that is not contributed back to
GeoServer, thinks to have the
right to call out other developers out on outdated docs, but for
functionality that is actually contributed and improved over time for
everybody’s benefit.

I did not intend to call out GeoSolutions on not updating the docs, but
rather verify that I am not stepping on anyone’s toes by adapting this
existing content to the GeoServer docs (see below). Given how busy many of
the core GeoServer developers are, “The docs haven’t been looked at since
before this functionality was added” is a perfectly valid response. Sorry if
this was not clear from my original message.
Also, the views of Boundless do not necessarily reflect my own (and vice
versa).

But even without going there, just to show you a counter example, can you
tell me where in the GeoServer guide we can find the equivalent of this?
http://suite.opengeo.org/4.1/cartography/rt/barnes.html
To paraphrase, why is that documented only in the OpenGeo Suite site?

Perfectly fair criticism (although the geoserver docs do give a full sld
example of a HeatMap, with the adaptation of the Transform syntax to other
rendering transforms left as an excercise to the reader). As you noted,
everyone is busy and doesn’t seem to find time to update the community docs.

docs.geoserver.org has various bits of outdated and incomplete
documentation, if you find bits are lacking you’re more than welcomed
to improve them. Or to provide help in other ways, thus freeing other devs
time for writing more docs. Don’t know, answering mails on the
users list, fixing bugs found in the tracker, helping to keep the build
servers going, updating the CITE tests, and so on

If it is just a case of outdated docs I am happy to improve them. Given that
the content at
http://geoserver.geo-solutions.it/multidim/en/imagemosaic/mosaic_datastore.html
is the property of GeoSolutions, may I adapt the content there while
updating the GeoServer docs, or would you prefer that I merely link to that
content instead?

Torben

Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple
OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140

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