date:20170301

Re: [Geoserver-devel] Modifying Netcdf Output to include other variables

2017-03-01 Thread Ben Caradoc-Davies

And (2a), sometimes the extra variables might need to be full coverages 
themselves to ensure that output NetCDF files are fully self-describing. 
For example, if a coverage is dimensioned by a sigma vertical dimension, 
it might be necessary to include a pressure coverage to permit 
interpretation.

Kind regards,
Ben.

On 02/03/17 10:29, Ben Caradoc-Davies wrote:
> Jerry,
>
> I am looking at a similar problem. I would like a solution that also
> works with ImageMosaic to take a collection of scalar
> forecast_reference_time and output forecast_reference_time(t) as an
> extra variable alongside a data variable delivered by WCS.
>
> This problem is also related to the need to gather GRIB/NetCDF variable
> attributes and add them to NetCDF output. See the analysis here:
> https://github.com/geotools/geotools/pull/1417
> https://osgeo-org.atlassian.net/browse/GEOS-7901
>
> Again, the situation is more complicated when the output is created with
> ImageMosaic. I think I have found a spot in GranuleDescriptor where the
> required information can be passed with a small API change. I am
> investigating. My goal is to avoid duplication.
>
> I suspect that we will need an API change, and thus a change proposal.
>
> I see three things that we need:
>
> (1) Collection of NetCDF/GRIB2 variable attributes from input and their
> application to WCS NetCDF output. What to do with ImageMosaic when
> attributes from different granules are mismatched is an open question.
>
> (2) Identification of extra variables from input NetCDF/GRIB2 files for
> inclusion in WCS NetCDF output. This will include their attributes. We
> will probably have to discard attributes like "coordinates" as there is
> much renaming on output. This part will likely need a UI change.
>
> (3) ImageMosaic of extra variables, for example forecast_reference_time
> mosaicked to forecast_reference_time(t). Whether this is generic or
> forecast_reference_time is handled as a special case is an open question.
>
> Kind regards,
> Ben.
>
> On 02/03/17 01:02, Wilwerding, Jerry wrote:
>> I have netcdf weather data that includes the following variables (I've left 
>> off the attributes and data):
>>
>> byte wxVariable(t, z, y, x);
>> double t(t);
>> double z(z);
>> double y(y);
>> double z(z)
>> double start_time;
>> double stop_time;
>> double expiration_time;
>> double forecast_period(t);
>> double forecast_reference_time;
>> int grid_mapping;
>>
>> The end user wants all of the 'extra' time variables included in the WCS 
>> netcdf output.
>> I can either alter Geoserver code to change the way the netcdf is written or 
>> I can modify the netcdf file outside of Geoserver before returning to the 
>> client.
>> First step is to determine if modifying Geoserver code to do this is 
>> possible within the current overall design.
>>
>> I've been looking at the NetCDFOutputManager.  Everything is based upon a 
>> GranuleStack associated with the wxVariable (assuming wxVariable is the 
>> CoverageId in a GetCoverage request).  I don't see a clean way to associate 
>> other variables within the netcdf data with the wxVariable.
>>
>> Looking for options:
>> Is there a way to associate the other variables (start_time, stop_time, etc) 
>> with the wxVariable that simply overlooked?
>> Is there a clean way to have a GranuleStack include these extra variables?  
>> This idea seems incompatible with the current design, but figured I'd ask 
>> anyway.
>>
>> Is there a clean way to include the original netcdf file path in the 
>> GranuleStack?  If so, I could modify netcdf-out behavior to include 'extra' 
>> netcdf variables based upon configuration settings by reading the original 
>> file and extracting these 'extra' time variables and include them when 
>> writing the netcdf variable.  I'm currently storing the netcdf file on disk. 
>>  Not sure if this idea completely falls apart if data is stored differently.
>>
>> Any suggestions is appreciated.
>>
>> Thanks,
>>
>> Jerry Wilwerding
>>
>>
>>
>>
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>
>>
>>
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Geoserver 2.8->2.10.2 upgrade: Windows disk path issues?

2017-03-01 Thread Jody Garnett

Hi Richard - during the release of GeoServer 2.9 we asked for help testing;
in part to head off any issues like this. Considerable work was done on how
geoserver interacts with the data directory and the file system at that
time.

One thing that does not make sense to me is the URL provided
"file://E:\luchtfotos2016"
- when I use firefox in a windows VM I get something like "
file:///C:/java/target/".

When teaching on windows (my only chance to use it) I often use firefox to
construct the correct URL as above. Can you do so now - I would expect
something like file://E:/lunchfotos2016/"

--
Jody Garnett

On 1 March 2017 at 03:07, Richard Duivenvoorde  wrote:

> Hi Devs,
>
> running 2.8 on Window server here, having a datastore on another disk
> then the GEOSERVER_DATA_DIR.
>
> GEOSERVER_DATA_DIR is on D:
> a directory with GeoTiffs is on E:\luchtfotos2016
>
> In 2.8 the store was created as a imagemosaic store using the filepath
>
> file://E:\luchtfotos2016
>
> and worked.
>
> After upgrade to 2.10 that store was INVALID, giving the stacktrace [0]
> below
>
> I was also NOT able to create other datastores which were on E
>
> Going to back to 2.8 all was fine again...
>
> Another issue I see is that in the 'create store dropdown' I only see
> the paths in the GEOSERVER_DATA_DIR, others are not viewable (white
> characters, see attached screendump. BUT the paths are there, you can
> select the third item and you will see the directories on that disk.
> BUT... the store will not work (also tries a shp store).
>
> THEN... I thought to try:
>
> file://E:/luchtfotos2016
>
> (switched path-separator to linux (normal ;-) ) style... and WORKS!
>
> So question: what has changed between 2.8 and 2.10.2 that makes that old
> datastore definitions do not work anymore.
> Also creating a new definition by browsing to it, geoserver itself
> creates "file://E:\luchtfotos2016" and then does not create the store.
>
> Is this considered a bug, and should I create an issue for this?
>
> Regards,
>
> Richard Duivenvoorde
>
>
> [0] stacktrace:
>
> 2017-03-01 11:09:17,106 WARN [geoserver.catalog] - Unable to convert
> coverage URL to a URI, attempting to use it as a path
> 2017-03-01 11:09:17,106 INFO [geoserver.web] - Getting list of coverages
> for saved store file://E:\luchtfotos2016
> java.lang.RuntimeException: Could not list layers for this store, an
> error occurred retrieving them: Failed to create reader from
> file://E:\luchtfotos2016 and hints null
> at
>
> org.geoserver.web.data.layer.NewLayerPageProvider.getItemsIn
> ternal(NewLayerPageProvider.java:158)
> at
> org.geoserver.web.data.layer.NewLayerPageProvider.getItems(N
> ewLayerPageProvider.java:61)
> at
> org.geoserver.web.wicket.GeoServerDataProvider.fullSize(GeoS
> erverDataProvider.java:243)
> at
> org.geoserver.web.wicket.GeoServerTablePanel$PagerDelegate.
> updateMatched(GeoServerTablePanel.java:583)
> at
> org.geoserver.web.wicket.GeoServerTablePanel$PagerDelegate.<
> init>(GeoServerTablePanel.java:576)
> at
> org.geoserver.web.wicket.GeoServerTablePanel.(GeoServe
> rTablePanel.java:176)
> at
> org.geoserver.web.wicket.GeoServerTablePanel.(GeoServe
> rTablePanel.java:97)
> at
> org.geoserver.web.data.layer.NewLayerPage$1.(NewLayerPage.java:105)
> at org.geoserver.web.data.layer.NewLayerPage.(NewLayerPag
> e.java:105)
> at
> org.geoserver.web.data.store.CoverageStoreNewPage.onSuccessf
> ulSave(CoverageStoreNewPage.java:86)
> at
> org.geoserver.web.data.store.CoverageStoreNewPage.onSave(Cov
> erageStoreNewPage.java:74)
> at
> org.geoserver.web.data.store.AbstractCoverageStorePage$1.onS
> ubmit(AbstractCoverageStorePage.java:122)
> at
> org.apache.wicket.ajax.markup.html.form.AjaxSubmitLink$1.onS
> ubmit(AjaxSubmitLink.java:110)
> at
> org.apache.wicket.ajax.form.AjaxFormSubmitBehavior$AjaxFormS
> ubmitter.onSubmit(AjaxFormSubmitBehavior.java:215)
> at org.apache.wicket.markup.html.form.Form.delegateSubmit(Form.
> java:1307)
> at org.apache.wicket.markup.html.form.Form.process(Form.java:974)
> at org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form
> .java:795)
> at
> org.apache.wicket.ajax.form.AjaxFormSubmitBehavior.onEvent(A
> jaxFormSubmitBehavior.java:171)
> at
> org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBe
> havior.java:155)
> at
> org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest
> (AbstractDefaultAjaxBehavior.java:588)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at
> org.apache.wicket.RequestListenerInterface.internalInvoke(Re
> questListenerInterface.java:258)
> at
>

Re: [Geoserver-devel] Modifying Netcdf Output to include other variables

2017-03-01 Thread Ben Caradoc-Davies

Jerry,

I am looking at a similar problem. I would like a solution that also 
works with ImageMosaic to take a collection of scalar 
forecast_reference_time and output forecast_reference_time(t) as an 
extra variable alongside a data variable delivered by WCS.

This problem is also related to the need to gather GRIB/NetCDF variable 
attributes and add them to NetCDF output. See the analysis here:
https://github.com/geotools/geotools/pull/1417
https://osgeo-org.atlassian.net/browse/GEOS-7901

Again, the situation is more complicated when the output is created with 
ImageMosaic. I think I have found a spot in GranuleDescriptor where the 
required information can be passed with a small API change. I am 
investigating. My goal is to avoid duplication.

I suspect that we will need an API change, and thus a change proposal.

I see three things that we need:

(1) Collection of NetCDF/GRIB2 variable attributes from input and their 
application to WCS NetCDF output. What to do with ImageMosaic when 
attributes from different granules are mismatched is an open question.

(2) Identification of extra variables from input NetCDF/GRIB2 files for 
inclusion in WCS NetCDF output. This will include their attributes. We 
will probably have to discard attributes like "coordinates" as there is 
much renaming on output. This part will likely need a UI change.

(3) ImageMosaic of extra variables, for example forecast_reference_time 
mosaicked to forecast_reference_time(t). Whether this is generic or 
forecast_reference_time is handled as a special case is an open question.

Kind regards,
Ben.

On 02/03/17 01:02, Wilwerding, Jerry wrote:
> I have netcdf weather data that includes the following variables (I've left 
> off the attributes and data):
>
> byte wxVariable(t, z, y, x);
> double t(t);
> double z(z);
> double y(y);
> double z(z)
> double start_time;
> double stop_time;
> double expiration_time;
> double forecast_period(t);
> double forecast_reference_time;
> int grid_mapping;
>
> The end user wants all of the 'extra' time variables included in the WCS 
> netcdf output.
> I can either alter Geoserver code to change the way the netcdf is written or 
> I can modify the netcdf file outside of Geoserver before returning to the 
> client.
> First step is to determine if modifying Geoserver code to do this is possible 
> within the current overall design.
>
> I've been looking at the NetCDFOutputManager.  Everything is based upon a 
> GranuleStack associated with the wxVariable (assuming wxVariable is the 
> CoverageId in a GetCoverage request).  I don't see a clean way to associate 
> other variables within the netcdf data with the wxVariable.
>
> Looking for options:
> Is there a way to associate the other variables (start_time, stop_time, etc) 
> with the wxVariable that simply overlooked?
> Is there a clean way to have a GranuleStack include these extra variables?  
> This idea seems incompatible with the current design, but figured I'd ask 
> anyway.
>
> Is there a clean way to include the original netcdf file path in the 
> GranuleStack?  If so, I could modify netcdf-out behavior to include 'extra' 
> netcdf variables based upon configuration settings by reading the original 
> file and extracting these 'extra' time variables and include them when 
> writing the netcdf variable.  I'm currently storing the netcdf file on disk.  
> Not sure if this idea completely falls apart if data is stored differently.
>
> Any suggestions is appreciated.
>
> Thanks,
>
> Jerry Wilwerding
>
>
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>
>
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Add back the possibility to externalize GWC configuration using GEOWEBCACHE_CACHE_DIR

2017-03-01 Thread Nuno Oliveira

Hi,

Pull request:

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

updated to take in account the GEOWEBCACHE_CONFIG_DIR property.

Tests cases were added for this and manually tested the various
possibilities and everything seems to be working fine.

Regards,

Nuno Oliveira

On 02/28/2017 09:29 AM, Nuno Oliveira wrote:
Sorry misunderstood your comment, no I'm no accounting for
GEOWEBCACHE_CONFIG_DIR only for GEOWEBCACHE_CACHE_DIR.

Let me see if I got this right:

If only GEOWEBCACHE_CACHE_DIR is defined both the configuration and
the tiles cache should be stored in that directory, this is backward
compatible.
If only GEOWEBCACHE_CONFIG_DIR is defined the configuration should be
stored in that directory but the tiles cache should use the default
location.
If both are defined GEOWEBCACHE_CONFIG_DIR should only contain the
configuration and GEOWEBCACHE_CACHE_DIR should only contain the tiles
cache.

If none of them are defined the default location should be used for both.

Let me see if can fix me current PR.

Thanks for the warning Kevin.

On 02/28/2017 09:00 AM, Nuno Oliveira wrote:
Yes if the GEOWEBCACHE_CONFIG_DIR is set this location will also be
used to store the cache.

On 02/24/2017 07:15 PM, Kevin Smith wrote:

Did you account for GEOWEBCACHE_CONFIG_DIR as well? That's the newer
way to specify the config location for GWC independent of the cache
location. It defaults to GEOWEBCACHE_CACHE_DIR for backward compatibility.

Other than that, +1 on including it in the RC.

On 17-02-23 03:13 PM, Nuno Oliveira wrote:

Hi,

The option to externalize GWC configuration using Java property
GEOWEBCACHE_CACHE_DIR was removed by this commit:
https://github.com/geoserver/geoserver/commit/a72682bc5f86114dc56ba9d68f19b670da76cd99#diff-5b32e54953013fe49c4405ac132f9d3eR18

Since the documentation has not been updated and I don't remember seeing
any discussion about this change I guess it was just a unfortunate
collateral effect of the resource API refactoring.

In my point of view this is a bug and is correctly reported by this issue:
https://osgeo-org.atlassian.net/browse/GEOS-8004

I made a pull request that fix it, no public APIs have been changed and
the changes are only additive:
https://github.com/geoserver/geoserver/pull/2131

Since this is a fix that brings back a mistakenly removed feature I
would like to have it in the release candidate (and consequently in the
up coming release) otherwise we will have to wait until September to
have this in a release. The changes are relatively small and isolated in
the GWC module with some small changes in the back-restore community
module. I would also like to backport this to 2.10.x and 2.9.x.

Any objections against this to be merged ?

Regards,

Nuno Oliveira

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org!http://sdm.link/slashdot

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

--
==
GeoServer Professional Services from the experts!
Visithttp://goo.gl/it488V for more information.
==
Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

GeoSolutions S.A.S.
Via di Montramito 3/A
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

Re: [Geoserver-devel] [Geotools-devel] netcdf runtime pull requests

2017-03-01 Thread Niels Charlier


Hello Andrea,

Indeed, that is fine. But in the meantime it is there already for review 
when it suits.


Regards

Niels


On 01-03-17 12:03, Andrea Aime wrote:

Hi Niels,
cannot comment on the pull request contents, but just in case you're 
not aware,
we're in feature freeze for the 2.11-RC1 release, new features will 
have to wait

for the master branch to switch to 18-snapshot/2.12-snapshot to be merged

Cheers
Andrea


On Wed, Mar 1, 2017 at 11:43 AM, Niels Charlier > wrote:


Hello Simone, Daniele,

I have made two pull requests with the aim of supporting "runtime"
as an
additional dimension in netcdf-java:

The first is in the netcdf-java module itself:

https://github.com/geotools/geotools/pull/1472


Rather than just adding runtime to the supported time and
elevation, it
is implemented in such a way that the VariableAdapter is now
generalised
for any number of dimensions, which is something I discussed
months ago
with Daniele and I thought it was a very good idea.

The second is in geoserver, which supports parsing custom
dimensions to
Date (or other data types) before sending them to the geotools store,
rather than always sending them as a String:

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



If you could have a look at these, that would be great. Thanks in
advance.

Kind Regards

Niels



--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
GeoTools-Devel mailing list
geotools-de...@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/geotools-devel





--
==
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.



---


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Modifying Netcdf Output to include other variables

2017-03-01 Thread Wilwerding, Jerry

I have netcdf weather data that includes the following variables (I've left off 
the attributes and data):

byte wxVariable(t, z, y, x);
double t(t);
double z(z);
double y(y);
double z(z)
double start_time;
double stop_time;
double expiration_time;
double forecast_period(t);
double forecast_reference_time;
int grid_mapping;

The end user wants all of the 'extra' time variables included in the WCS netcdf 
output.
I can either alter Geoserver code to change the way the netcdf is written or I 
can modify the netcdf file outside of Geoserver before returning to the client.
First step is to determine if modifying Geoserver code to do this is possible 
within the current overall design.

I've been looking at the NetCDFOutputManager.  Everything is based upon a 
GranuleStack associated with the wxVariable (assuming wxVariable is the 
CoverageId in a GetCoverage request).  I don't see a clean way to associate 
other variables within the netcdf data with the wxVariable.

Looking for options:
Is there a way to associate the other variables (start_time, stop_time, etc) 
with the wxVariable that simply overlooked?
Is there a clean way to have a GranuleStack include these extra variables?  
This idea seems incompatible with the current design, but figured I'd ask 
anyway.

Is there a clean way to include the original netcdf file path in the 
GranuleStack?  If so, I could modify netcdf-out behavior to include 'extra' 
netcdf variables based upon configuration settings by reading the original file 
and extracting these 'extra' time variables and include them when writing the 
netcdf variable.  I'm currently storing the netcdf file on disk.  Not sure if 
this idea completely falls apart if data is stored differently.

Any suggestions is appreciated.

Thanks,

Jerry Wilwerding

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Geoserver 2.8->2.10.2 upgrade: Windows disk path issues?

2017-03-01 Thread Richard Duivenvoorde

Hi Devs,

running 2.8 on Window server here, having a datastore on another disk
then the GEOSERVER_DATA_DIR.

GEOSERVER_DATA_DIR is on D:
a directory with GeoTiffs is on E:\luchtfotos2016

In 2.8 the store was created as a imagemosaic store using the filepath

file://E:\luchtfotos2016

and worked.

After upgrade to 2.10 that store was INVALID, giving the stacktrace [0]
below

I was also NOT able to create other datastores which were on E

Going to back to 2.8 all was fine again...

Another issue I see is that in the 'create store dropdown' I only see
the paths in the GEOSERVER_DATA_DIR, others are not viewable (white
characters, see attached screendump. BUT the paths are there, you can
select the third item and you will see the directories on that disk.
BUT... the store will not work (also tries a shp store).

THEN... I thought to try:

file://E:/luchtfotos2016

(switched path-separator to linux (normal ;-) ) style... and WORKS!

So question: what has changed between 2.8 and 2.10.2 that makes that old
datastore definitions do not work anymore.
Also creating a new definition by browsing to it, geoserver itself
creates "file://E:\luchtfotos2016" and then does not create the store.

Is this considered a bug, and should I create an issue for this?

Regards,

Richard Duivenvoorde


[0] stacktrace:

2017-03-01 11:09:17,106 WARN [geoserver.catalog] - Unable to convert
coverage URL to a URI, attempting to use it as a path
2017-03-01 11:09:17,106 INFO [geoserver.web] - Getting list of coverages
for saved store file://E:\luchtfotos2016
java.lang.RuntimeException: Could not list layers for this store, an
error occurred retrieving them: Failed to create reader from
file://E:\luchtfotos2016 and hints null
at

org.geoserver.web.data.layer.NewLayerPageProvider.getItemsInternal(NewLayerPageProvider.java:158)
at
org.geoserver.web.data.layer.NewLayerPageProvider.getItems(NewLayerPageProvider.java:61)
at
org.geoserver.web.wicket.GeoServerDataProvider.fullSize(GeoServerDataProvider.java:243)
at
org.geoserver.web.wicket.GeoServerTablePanel$PagerDelegate.updateMatched(GeoServerTablePanel.java:583)
at
org.geoserver.web.wicket.GeoServerTablePanel$PagerDelegate.(GeoServerTablePanel.java:576)
at
org.geoserver.web.wicket.GeoServerTablePanel.(GeoServerTablePanel.java:176)
at
org.geoserver.web.wicket.GeoServerTablePanel.(GeoServerTablePanel.java:97)
at
org.geoserver.web.data.layer.NewLayerPage$1.(NewLayerPage.java:105)
at 
org.geoserver.web.data.layer.NewLayerPage.(NewLayerPage.java:105)
at
org.geoserver.web.data.store.CoverageStoreNewPage.onSuccessfulSave(CoverageStoreNewPage.java:86)
at
org.geoserver.web.data.store.CoverageStoreNewPage.onSave(CoverageStoreNewPage.java:74)
at
org.geoserver.web.data.store.AbstractCoverageStorePage$1.onSubmit(AbstractCoverageStorePage.java:122)
at
org.apache.wicket.ajax.markup.html.form.AjaxSubmitLink$1.onSubmit(AjaxSubmitLink.java:110)
at
org.apache.wicket.ajax.form.AjaxFormSubmitBehavior$AjaxFormSubmitter.onSubmit(AjaxFormSubmitBehavior.java:215)
at 
org.apache.wicket.markup.html.form.Form.delegateSubmit(Form.java:1307)
at org.apache.wicket.markup.html.form.Form.process(Form.java:974)
at 
org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:795)
at
org.apache.wicket.ajax.form.AjaxFormSubmitBehavior.onEvent(AjaxFormSubmitBehavior.java:171)
at
org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:155)
at
org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:588)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:258)
at
org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:241)
at
org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:248)
at
org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:234)
at
org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:865)
at
org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
at
org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:265)
at
org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:222)
at
org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293)
at
org.apache.wicket.protocol.http.WicketFilter.processRequestCycle(WicketFilter.java:261)
at

Re: [Geoserver-devel] [Geotools-devel] netcdf runtime pull requests

2017-03-01 Thread Andrea Aime

Hi Niels,
cannot comment on the pull request contents, but just in case you're not
aware,
we're in feature freeze for the 2.11-RC1 release, new features will have to
wait
for the master branch to switch to 18-snapshot/2.12-snapshot to be merged

Cheers
Andrea

On Wed, Mar 1, 2017 at 11:43 AM, Niels Charlier  wrote:

> Hello Simone, Daniele,
>
> I have made two pull requests with the aim of supporting "runtime" as an
> additional dimension in netcdf-java:
>
> The first is in the netcdf-java module itself:
>
> https://github.com/geotools/geotools/pull/1472
>
> Rather than just adding runtime to the supported time and elevation, it
> is implemented in such a way that the VariableAdapter is now generalised
> for any number of dimensions, which is something I discussed months ago
> with Daniele and I thought it was a very good idea.
>
> The second is in geoserver, which supports parsing custom dimensions to
> Date (or other data types) before sending them to the geotools store,
> rather than always sending them as a String:
>
> https://github.com/geoserver/geoserver/pull/2117
>
>
> If you could have a look at these, that would be great. Thanks in advance.
>
> Kind Regards
>
> Niels
>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> ___
> GeoTools-Devel mailing list
> geotools-de...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>

-- 
==
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.

---
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] netcdf runtime pull requests

2017-03-01 Thread Niels Charlier

Hello Simone, Daniele,

I have made two pull requests with the aim of supporting "runtime" as an 
additional dimension in netcdf-java:

The first is in the netcdf-java module itself:

https://github.com/geotools/geotools/pull/1472

Rather than just adding runtime to the supported time and elevation, it 
is implemented in such a way that the VariableAdapter is now generalised 
for any number of dimensions, which is something I discussed months ago 
with Daniele and I thought it was a very good idea.

The second is in geoserver, which supports parsing custom dimensions to 
Date (or other data types) before sending them to the geotools store, 
rather than always sending them as a String:

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


If you could have a look at these, that would be great. Thanks in advance.

Kind Regards

Niels


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-8010) Regression: dbtype and filetype store arguments should not be visible

2017-03-01 Thread Andrea Aime [Administrator] (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrea Aime [Administrator] created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8010  
 
 
  Regression: dbtype and filetype store arguments should not be visible   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.10.2, 2.11-beta  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Wicket UI  
 
 
Created: 
 01/Mar/17 11:21 AM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Andrea Aime [Administrator]  
 

  
 
 
 
 

 
 The two fields should not be made available and editable to the end user. There is logic to prevent that, but apparently during the wicket upgrade it got botched.  
 

  
 
 
  
 

 
 
 

 
 
 Add Comment

[Geoserver-devel] [JIRA] (GEOS-8009) Saving requests withs errors fails in Postgres due to LOB usage

2017-03-01 Thread Andreas W (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas W created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-8009  
 
 
  Saving requests withs errors fails in Postgres due to LOB usage   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Affects Versions: 
 2.7.1.1  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 Monitoring  
 
 
Created: 
 01/Mar/17 9:41 AM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Andreas W  
 

  
 
 
 
 

 
 Saving request data to a Postgresql backend fails if an error occured with the request: The writing of the error into a LOB column fails: 

 
2017-03-01 08:19:42,480 ERROR [def.AbstractFlushingEventListener] - Could not synchronize database state with session
org.hibernate.exception.GenericJDBCException: could not update: [org.geoserver.monitor.RequestData#80643]
at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126)
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:114)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2453)
at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2335)
at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2635)
at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:115)
at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:279)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:263)
at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:168)
at

Re: [Geoserver-devel] Modifying Netcdf Output to include other variables

Re: [Geoserver-devel] Geoserver 2.8->2.10.2 upgrade: Windows disk path issues?

Re: [Geoserver-devel] Modifying Netcdf Output to include other variables

Re: [Geoserver-devel] Add back the possibility to externalize GWC configuration using GEOWEBCACHE_CACHE_DIR

Re: [Geoserver-devel] [Geotools-devel] netcdf runtime pull requests

[Geoserver-devel] Modifying Netcdf Output to include other variables

[Geoserver-devel] Geoserver 2.8->2.10.2 upgrade: Windows disk path issues?

Re: [Geoserver-devel] [Geotools-devel] netcdf runtime pull requests

[Geoserver-devel] netcdf runtime pull requests

[Geoserver-devel] [JIRA] (GEOS-8010) Regression: dbtype and filetype store arguments should not be visible

[Geoserver-devel] [JIRA] (GEOS-8009) Saving requests withs errors fails in Postgres due to LOB usage

11 matches

Site Navigation

Mail list logo

Footer information