Dear Brian,
You could consider using an ImageMosaic coverageStore of NetCDF file(s).
At the moment it’s the only format implementing the harvest method (which is invoked when you send a REST update request similarly to what you did).
Harvest allows to add new granules to the collection or update existing ones.
Moreover, when the underlying NetCDF Reader (involved by ImageMosaic) notices that a file has been updated, it also does a reset of its internal index.
If my memory serves me right, some users already used this approach for time-growing NetCDFs.
That being said (in order to answer your questions):
- you can take a look here: http://docs.geoserver.org/latest/en/user/rest/examples/curl.html#uploading-and-modifying-a-image-mosaic
the XPOST commands
-
yes, using imageMosaic. From a “pure NetCDF coverageStore” point of view, the harvest method isn’t implemented yet so the NetCDF reader should be reinit (GeoServer cache cleanup is probably needed).
-
coverageStore is the right one.
Hope this helps.
Cheers,
Daniele
···
On Wed, Sep 16, 2015 at 12:16 AM, Brian Farrell <brian.farrell@anonymised.com3…> wrote:
I’m attempting to use the REST API to update an existing netCDF data store without any success.
For a bit of background: my group has built a system to harvest data from various sources on an hourly basis and put it all in a netCDF file. We hope to be able to update the existing data store rather than creating a new one with every update.
This is my current curl command:
curl -v -u username:password -XPUT -H “Content-Type: text/plain” -d “file///2015_archive_replacement_testing.nc” http://198.82.152.38:8080/geoserver/rest/workspaces/netCDFtesting/coveragestores/replacement_testing/file.netcdf
The error I get back is “Error while storing uploaded file::Unable to delete file: /path/to/file/replacement_testing.netcdf* Closing connection 1” I’ve checked, and the chmod of that file is 777.
Here are some questions I’ve been developing:
- Is the curl command correct?
- Does Geoserver 2.7.2 (with netCDF and netCDF output extensions) support updating netCDF files? If no, is there information about what needs to be implemented to build this functionality?
- Is the curl command using the correct interface (should it be datastores instead of coveragestores)? If it should be using datastores, then the answer to 2) is likely “no”, since that error message states: “Unsupported format: netcdf* Closing connection 1”
Thanks,
Brian
–
Brian Farrell
Project Associate
Center for Geospatial Information Technology
Geoserver-users mailing list
Geoserver-users@anonymised.comsts.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 Poggio alle Viti 1187
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.