[Geoserver-users] ImageMosaic drop bbox table

Hello,

I'm working with ImageMosaics layers with multiple timesteps.

I knew that when creating such an ImageMosaics layer, a specific table is
always created in the PostGIS database to hold on the bounding boxes of each
timestep.

But I just realized that this table is not dropped when I remove the
ImageMosaic layer from GeoServer.

Is this a normal behaviour ?
Is there a way to force GeoServer to remove the table it created when
dropping the layer ?

Thanks for you consideration,

Cyril

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/ImageMosaic-drop-bbox-table-tp5271113.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

On Fri, Jun 10, 2016 at 4:53 PM, CGA <cgallay.artal@anonymised.com> wrote:

Hello,

I'm working with ImageMosaics layers with multiple timesteps.

I knew that when creating such an ImageMosaics layer, a specific table is
always created in the PostGIS database to hold on the bounding boxes of
each
timestep.

But I just realized that this table is not dropped when I remove the
ImageMosaic layer from GeoServer.

Is this a normal behaviour ?
Is there a way to force GeoServer to remove the table it created when
dropping the layer ?

Hi Cyril,
right now removing the geoserver store from the GUI won't also remove the
database tables.
You can use the REST interface to perform a coverageStore delete using the
purge parameter. (=metadata).
http://docs.geoserver
.org/stable/en/user/rest/api/coveragestores.html#rest-api-coveragestores-
purge

Please, let me know if that satisfies your needs.
Cheers,
Daniele

Thanks for you consideration,

Cyril

--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/ImageMosaic-drop-bbox-table-tp5271113.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and
traffic
patterns at an interface-level. Reveals which users, apps, and protocols
are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

--

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

Ing. Daniele Romagnoli
Senior Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

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 Fri, Jun 10, 2016 at 4:53 PM, CGA <cgallay.artal@anonymised.com> wrote:

Hello,

I'm working with ImageMosaics layers with multiple timesteps.

I knew that when creating such an ImageMosaics layer, a specific table is
always created in the PostGIS database to hold on the bounding boxes of
each
timestep.

But I just realized that this table is not dropped when I remove the
ImageMosaic layer from GeoServer.

Is this a normal behaviour ?

It is, nothing In the GeoServer UI drops the data or metadata when a layer
is dropped. Once upon a time we just did not have the tools.
Now we have some of the tools, but we lack the time to implement such an
option
in the UI (deletion is generic, and can cascade from containers to
contained objects, so should be the deletion of metadata and data, generic,
not available only for a specific format).

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 di Montramito 3/A
55054 Massarosa (LU)
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.

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

Hi Daniele,

I am already working with the REST API with OWSLib.

I tried using purge='all' and recurse=True and here is the output I get in
GeoServer logs :

The thing is that the table is apparently removed so I don't see why
GeoServer is complaining.

But the purge = 'all' does no do exactely as I expected : it removed all the
granules and the table, but the directory that was holding the granules
still exists after the purge and contains datastore.properties,
indexer.properties, timeregex.properties and sample_image. I was expecting
this folder and all its content to disappear.

Cyril

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/ImageMosaic-drop-bbox-table-tp5271113p5271810.html
Sent from the GeoServer - User mailing list archive at Nabble.com.