Re: [Geoserver-users] ImageMosaic index not updating due to ClassCastException

[Andrew Chamberlain via Geoserver-users]

 Hi Ian,
By way of an update, and for anyone else who might see this, the issue boiled 
down to a lack of a primary key on the table.  As mentioned here, without a 
primary key, Geoserver will regard the table as read-only.  So you were 
absolutely right: as far as Geoserver was concerned, the source was indeed 
read-only.
Finally, to allow the index to be updated, the UseExistingSchema property had 
to be set to false.
Thanks again,
Andy

On Friday, 4 November 2022 at 18:06:30 GMT, Andrew Chamberlain 
 wrote:  
 
  Hi Ian,
Thanks for the prompt reply.  Yes, the datastore is configured with the same 
user with which I populate the index in the database.
In case it matters, I'm still on versions 9.6/2.5 for Postgres/Postgis.
Thanks,
Andy


On Friday, 4 November 2022 at 16:50:42 GMT, Ian Turton  
wrote:  
 
 Is your source writable by the user that GeoServer is using? I think that 
error usually means it is read only.
Ian 
On Fri, 4 Nov 2022, 16:40 Andrew Chamberlain via Geoserver-users, 
 wrote:

Hi All,
Has anyone recently seen this when adding a granule to an imagemosaic?
java.lang.ClassCastException: org.geotools.jdbc.JDBCFeatureSource cannot be 
cast to org.geotools.data.simple.SimpleFeatureStore
at 
org.geotools.gce.imagemosaic.catalog.AbstractGTDataStoreGranuleCatalog.removeGranules(AbstractGTDataStoreGranuleCatalog.java:391)at
 
org.geotools.gce.imagemosaic.catalog.GTDataStoreGranuleCatalog.removeGranules(GTDataStoreGranuleCatalog.java:37)...
As far as I can tell from here, the JDBCFeatureSource doesn't directly 
implement SimpleFeatureStore, so the above is understandable.  What's not clear 
is how this has come about.
My datastore.properties references an existing PostGIS datastore:
StoreName=postgres
SPI=org.geotools.data.postgis.PostgisNGDataStoreFactory
Any clues or pointers would be very much appreciated.
Thank you in advance,
Andy
Geoserver version: 2.20.4___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] ImageMosaic index not updating due to ClassCastException

[Andrew Chamberlain via Geoserver-users]

 Hi Ian,
Thanks for the prompt reply.  Yes, the datastore is configured with the same 
user with which I populate the index in the database.
In case it matters, I'm still on versions 9.6/2.5 for Postgres/Postgis.
Thanks,
Andy


On Friday, 4 November 2022 at 16:50:42 GMT, Ian Turton  
wrote:  
 
 Is your source writable by the user that GeoServer is using? I think that 
error usually means it is read only.
Ian 
On Fri, 4 Nov 2022, 16:40 Andrew Chamberlain via Geoserver-users, 
 wrote:

Hi All,
Has anyone recently seen this when adding a granule to an imagemosaic?
java.lang.ClassCastException: org.geotools.jdbc.JDBCFeatureSource cannot be 
cast to org.geotools.data.simple.SimpleFeatureStore
at 
org.geotools.gce.imagemosaic.catalog.AbstractGTDataStoreGranuleCatalog.removeGranules(AbstractGTDataStoreGranuleCatalog.java:391)at
 
org.geotools.gce.imagemosaic.catalog.GTDataStoreGranuleCatalog.removeGranules(GTDataStoreGranuleCatalog.java:37)...
As far as I can tell from here, the JDBCFeatureSource doesn't directly 
implement SimpleFeatureStore, so the above is understandable.  What's not clear 
is how this has come about.
My datastore.properties references an existing PostGIS datastore:
StoreName=postgres
SPI=org.geotools.data.postgis.PostgisNGDataStoreFactory
Any clues or pointers would be very much appreciated.
Thank you in advance,
Andy
Geoserver version: 2.20.4___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

  ___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] ImageMosaic index not updating due to ClassCastException

[Andrew Chamberlain via Geoserver-users]

Hi All,
Has anyone recently seen this when adding a granule to an imagemosaic?
java.lang.ClassCastException: org.geotools.jdbc.JDBCFeatureSource cannot be 
cast to org.geotools.data.simple.SimpleFeatureStore
at 
org.geotools.gce.imagemosaic.catalog.AbstractGTDataStoreGranuleCatalog.removeGranules(AbstractGTDataStoreGranuleCatalog.java:391)at
 
org.geotools.gce.imagemosaic.catalog.GTDataStoreGranuleCatalog.removeGranules(GTDataStoreGranuleCatalog.java:37)...
As far as I can tell from here, the JDBCFeatureSource doesn't directly 
implement SimpleFeatureStore, so the above is understandable.  What's not clear 
is how this has come about.
My datastore.properties references an existing PostGIS datastore:
StoreName=postgres
SPI=org.geotools.data.postgis.PostgisNGDataStoreFactory
Any clues or pointers would be very much appreciated.
Thank you in advance,
Andy
Geoserver version: 2.20.4___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] ImageMosaic PNG8 Transparency

[Andrew Chamberlain via Geoserver-users]

Hi All,
Does anyone know a way of forcing Geoserver to (always) preserve transparent 
pixels beyond the bounds of source granule footprints?
I only ask because I've noticed that when the area not covered by granules 
falls below a certain threshold, the Transparent setting for "Footprint 
Behaviour" is no longer respected.  I suspect this happens when the 8-bit 
palette is calculated from the colours used in 24-bit colour space, and the 
smaller number of pixels that need to be transparent can't compete numerically 
with the rest of the image.
I was just wondering if there might be a way of forcing the colour recoding 
algorithm to always allocate a palette entry for transparency?
Many thanks,
Andy___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Image Mosaic Time Support with Existing DB Schema

[Andrew Chamberlain via Geoserver-users]

 Hi Jakub,
Your example content for the Primary configuration file was spot on.  
Specifically, the TimeAttribute being in there rather than the 
indexer.properties.  This was the only change I made and it now works - thank 
you!
It seems as though the documentation needs updating, but there may be something 
else going on.
Thanks again,
Andy

On Wednesday, 21 July 2021, 14:19:44 BST, Andrew Chamberlain 
 wrote:  
 
  Hi Jakub,
Thank you for your reply.
I'll take a look at your example configuration.  What's interesting is that you 
seem to have TimeAttribute in the Primary configuration file, rather than 
indexer.properties.  Will certainly give this a go.
What is reassuring to hear from everyone is that the scenario we're trying 
should indeed be possible.
Thank you all, it's much appreciated.
Andy

On Tuesday, 20 July 2021, 15:59:26 BST, Jakub Sawicki 
 wrote:  
 
  
We actually cover a similiar use case in our product. As we populate the DB 
tables ourselves, we don't use indexer at all, you probably don't need it 
either.
 
The datastore.properties to connect to the DB looks the following:
 
 

 SPI=org.geotools.data.postgis.PostgisNGJNDIDataStoreFactory
jndiReferenceName=java:comp/env/jdbc/somename
schema=public
Loose\ bbox=true
preparedStatements=false 
 then some of the most relevant fields in the mosaic.properties file: 
 

 Name=layer_name
TypeName=target_table_name
Caching=false
LocationAttribute=name_of_the_location_column
TimeAttribute=name_of_the_timestamp_column
  
 You may also need to specify at least some other, but as Carlo mentioned you 
can find it in the tutorials.
 Anyway, some of the other properties that we use in mosaic.properties, but 
they are not directly tied to the core issue here (we use custom SPI to fetch 
data from S3 and it needs some specific workarounds):
 
 Levels=1,1
LevelsNum=1
MosaicCRS=EPSG\:3857
Heterogeneous=true
HeterogeneousCRS=false
ExpandToRGB=false
CheckAuxiliaryMetadata=false
PathType=URL
SuggestedSPI=it.geosolutions.imageioimpl.plugins.tiff.TIFFImageReaderSpi
SuggestedFormat=org.geotools.s3.geotiff.S3GeoTiffFormat
SuggestedIsSPI=org.geotools.s3.S3ImageInputStreamImplSpi 
 Best,
 Jakub
 On 20.07.2021 13:43, carlo cancellieri wrote:
  
 
Yes its possible you are probably missing tha datastore.properties pointing to 
the database? Please (google) follow the time series howto with imagemosaic to 
check if/what else you are missing. 
  
  Il giorno mar 20 lug 2021 alle 11:43 Andrew Chamberlain via Geoserver-users 
 ha scritto:
  
   Hi All 
  Apologies for the self-reply.  I feel this is a bug, but before I can raise 
one, I understand that it first needs to be confirmed by a third party.  I was 
therefore wondering if anyone might be able to confirm the following: 
  1) It should be possible for an ImageMosaic layer to use a pre-populated 
timestamp column in an existing granule index (i.e. database table). 2) The 
indexer.properties file below looks reasonable. 
  Many thanks in advance, 
  Andrew 
  
  
On Monday, 12 July 2021, 14:43:50 BST, Andrew Chamberlain via 
Geoserver-users  wrote:  
  
  Hi All, 
  Not sure if this should be possible, but I'm trying to configure an 
ImageMosaic layer, whereby the index is pre-populated in a Postgres database 
and includes a timestamp column for when the imagery was captured.  My 
indexer.properties file looks like: 
  
 TimeAttribute=datecaptured
Schema=*geometry:Polygon,location:String,datecaptured:java.util.Date   
PropertyCollectors=  UseExistingSchema=true Caching=false 
AbsolutePath=true Name=metadata   
   
   However, when creating the layer, the TIME dimension remains unavailable, 
with the message "Cannot enable, no attribute of type Date found".  I've also 
created an index in the database, in case this mattered. 
  I can't find an example of using a mosaic index with a pre-populated time, so 
was starting to wonder whether it's possible at all? 
  Have tried on versions 2.17 and 2.19.  Any pointers would be greatly 
appreciated.  
Many thanks, 
  Andrew Chamberlain 
  
  P.S. The only hint of any issue is the following from the logs, but I imagine 
this is a red herring and just a minor UI issue?     2021-07-12 14:21:27,263 
WARN [wicket.Localizer] - Tried to retrieve a localized string for a component 
that has not yet been added to the page. This can sometimes lead to an invalid 
or no localized resource returned. Make sure you are not calling 
Component#getString() inside your Component's constructor. Offending component: 
[DimensionEditor [Component id = time]] 
   
  ___
 Geoserver-users mailing list
 
 Please make sure you read the following two resources before posting to this 
list:
 - Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
 - The GeoServer user list posting guid

Re: [Geoserver-users] Image Mosaic Time Support with Existing DB Schema

[Andrew Chamberlain via Geoserver-users]

 Hi Jakub,
Thank you for your reply.
I'll take a look at your example configuration.  What's interesting is that you 
seem to have TimeAttribute in the Primary configuration file, rather than 
indexer.properties.  Will certainly give this a go.
What is reassuring to hear from everyone is that the scenario we're trying 
should indeed be possible.
Thank you all, it's much appreciated.
Andy

On Tuesday, 20 July 2021, 15:59:26 BST, Jakub Sawicki 
 wrote:  
 
  
We actually cover a similiar use case in our product. As we populate the DB 
tables ourselves, we don't use indexer at all, you probably don't need it 
either.
 
The datastore.properties to connect to the DB looks the following:
 
 

 SPI=org.geotools.data.postgis.PostgisNGJNDIDataStoreFactory
jndiReferenceName=java:comp/env/jdbc/somename
schema=public
Loose\ bbox=true
preparedStatements=false 
 then some of the most relevant fields in the mosaic.properties file: 
 

 Name=layer_name
TypeName=target_table_name
Caching=false
LocationAttribute=name_of_the_location_column
TimeAttribute=name_of_the_timestamp_column
  
 You may also need to specify at least some other, but as Carlo mentioned you 
can find it in the tutorials.
 Anyway, some of the other properties that we use in mosaic.properties, but 
they are not directly tied to the core issue here (we use custom SPI to fetch 
data from S3 and it needs some specific workarounds):
 
 Levels=1,1
LevelsNum=1
MosaicCRS=EPSG\:3857
Heterogeneous=true
HeterogeneousCRS=false
ExpandToRGB=false
CheckAuxiliaryMetadata=false
PathType=URL
SuggestedSPI=it.geosolutions.imageioimpl.plugins.tiff.TIFFImageReaderSpi
SuggestedFormat=org.geotools.s3.geotiff.S3GeoTiffFormat
SuggestedIsSPI=org.geotools.s3.S3ImageInputStreamImplSpi 
 Best,
 Jakub
 On 20.07.2021 13:43, carlo cancellieri wrote:
  
 
Yes its possible you are probably missing tha datastore.properties pointing to 
the database? Please (google) follow the time series howto with imagemosaic to 
check if/what else you are missing. 
  
  Il giorno mar 20 lug 2021 alle 11:43 Andrew Chamberlain via Geoserver-users 
 ha scritto:
  
   Hi All 
  Apologies for the self-reply.  I feel this is a bug, but before I can raise 
one, I understand that it first needs to be confirmed by a third party.  I was 
therefore wondering if anyone might be able to confirm the following: 
  1) It should be possible for an ImageMosaic layer to use a pre-populated 
timestamp column in an existing granule index (i.e. database table). 2) The 
indexer.properties file below looks reasonable. 
  Many thanks in advance, 
  Andrew 
  
  
On Monday, 12 July 2021, 14:43:50 BST, Andrew Chamberlain via 
Geoserver-users  wrote:  
  
  Hi All, 
  Not sure if this should be possible, but I'm trying to configure an 
ImageMosaic layer, whereby the index is pre-populated in a Postgres database 
and includes a timestamp column for when the imagery was captured.  My 
indexer.properties file looks like: 
  
 TimeAttribute=datecaptured
Schema=*geometry:Polygon,location:String,datecaptured:java.util.Date   
PropertyCollectors=  UseExistingSchema=true Caching=false 
AbsolutePath=true Name=metadata   
   
   However, when creating the layer, the TIME dimension remains unavailable, 
with the message "Cannot enable, no attribute of type Date found".  I've also 
created an index in the database, in case this mattered. 
  I can't find an example of using a mosaic index with a pre-populated time, so 
was starting to wonder whether it's possible at all? 
  Have tried on versions 2.17 and 2.19.  Any pointers would be greatly 
appreciated.  
Many thanks, 
  Andrew Chamberlain 
  
  P.S. The only hint of any issue is the following from the logs, but I imagine 
this is a red herring and just a minor UI issue?     2021-07-12 14:21:27,263 
WARN [wicket.Localizer] - Tried to retrieve a localized string for a component 
that has not yet been added to the page. This can sometimes lead to an invalid 
or no localized resource returned. Make sure you are not calling 
Component#getString() inside your Component's constructor. Offending component: 
[DimensionEditor [Component id = time]] 
   
  ___
 Geoserver-users mailing list
 
 Please make sure you read the following two resources before posting to this 
list:
 - Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
 - The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html
 
 If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
 
 
 Geoserver-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/geoserver-users
 ___
 Geoserver-

Re: [Geoserver-users] Image Mosaic Time Support with Existing DB Schema

[Andrew Chamberlain via Geoserver-users]

 Hi Daniele,
Many thanks for your reply.  We certainly have a datastore.properties file, as 
well as a primary configuration file.
The datatype in the Postgresql database is "timestamp without time zone".  
Judging from the message on the Dimensions tab ("Cannot enable, no attribute of 
type Date found"), I was wondering if this needed to be of type "date".  But 
there seemed to be examples where this hasn't been necessary.
I'll investigate further.  It does feel like some criteria is failing to be met 
to allow Time to be enabled on the Dimensions tab.
Thank you again,
Andy

On Tuesday, 20 July 2021, 15:06:51 BST, Daniele Romagnoli 
 wrote:  
 
 Hi Andrew,
Yes, it's possible.I agree with Carlo's suggestion.You might need to check that 
a datastore.properties file is available on the mosaic configuration folder 
containing the connection parameters to the DB containing the populated index.
Which datatype is being used on the table for the datecaptured field?
BTW, for a different need I just had to configure an ImageMosaic with 
timeDimension and then I did the test by setting up a new ImageMosaic from the 
previously populated schema and it worked.Please, Let us know if you have any 
other questions.


Regards,

Daniele Romagnoli

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.
==

Daniele Romagnoli
Senior Software Engineer

GeoSolutions Group
phone: +39 0584 962313
fax:      +39 0584 1660272

https://www.geosolutionsgroup.com/ 
http://twitter.com/geosolutions_it 
---

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa 
che ogni circostanza inerente alla presente email (il suo contenuto, gli 
eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i 
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per 
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei 
comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed 
and may contain information that is privileged, confidential or otherwise 
protected from disclosure. We remind that - as provided by European Regulation 
2016/679 “GDPR” - copying, dissemination or use of this e-mail or the 
information herein by anyone other than the intended recipient is prohibited. 
If you have received this email by mistake, please notify us immediately by 
telephone or e-mail.


On Tue, Jul 20, 2021 at 1:54 PM carlo cancellieri  
wrote:

Yes its possible you are probably missing tha datastore.properties pointing to 
the database?Please (google) follow the time series howto with imagemosaic to 
check if/what else you are missing.

Il giorno mar 20 lug 2021 alle 11:43 Andrew Chamberlain via Geoserver-users 
 ha scritto:

 Hi All
Apologies for the self-reply.  I feel this is a bug, but before I can raise 
one, I understand that it first needs to be confirmed by a third party.  I was 
therefore wondering if anyone might be able to confirm the following:
1) It should be possible for an ImageMosaic layer to use a pre-populated 
timestamp column in an existing granule index (i.e. database table).2) The 
indexer.properties file below looks reasonable.
Many thanks in advance,
Andrew


On Monday, 12 July 2021, 14:43:50 BST, Andrew Chamberlain via 
Geoserver-users  wrote:  
 
 Hi All,
Not sure if this should be possible, but I'm trying to configure an ImageMosaic 
layer, whereby the index is pre-populated in a Postgres database and includes a 
timestamp column for when the imagery was captured.  My indexer.properties file 
looks like:

TimeAttribute=datecapturedSchema=*geometry:Polygon,location:String,datecaptured:java.util.DatePropertyCollectors=UseExistingSchema=trueCaching=falseAbsolutePath=trueName=metadata

However, when creating the layer, the TIME dimension remains unavailable, with 
the message "Cannot enable, no attribute of type Date found".  I've also 
created an index in the database, in case this mattered.
I can't find an example of using a mosaic index with a pre-populated time, so 
was starting to wonder whether it's possible at all?
Have tried on versions 2.17 and 2.19.  Any pointers would be greatly 
appreciated.
Many thanks,
Andrew Chamberlain

P.S. The only hint of any issue is the following from the logs, but I imagine 
this is a red herring and just a minor UI issue? 2021-07-12 14:21:27,263 WARN 
[wicket.Localizer] - Tried to retrieve a localized string for a component that 
has not yet been added to the page. This can sometimes lead to an invalid or no 
localized resource returned. Make sure you are not calling 
Component#getString() inside your Component's constructor. Offending component: 
[DimensionEditor [Component id = time]]

Re: [Geoserver-users] Image Mosaic Time Support with Existing DB Schema

[Andrew Chamberlain via Geoserver-users]

 Hi Carlo,
Thank you for your reply.  We have the datastore.properties, and it allows the 
mosaic datastore to connect fine.  We know this because we can configure and 
use a layer which has no time dimension.  It's definitely something which is 
preventing Geoserver from recognising the availability of the time attribute.
Thanks again,
Andy


On Tuesday, 20 July 2021, 12:43:51 BST, carlo cancellieri 
 wrote:  
 
 Yes its possible you are probably missing tha datastore.properties pointing to 
the database?Please (google) follow the time series howto with imagemosaic to 
check if/what else you are missing.

Il giorno mar 20 lug 2021 alle 11:43 Andrew Chamberlain via Geoserver-users 
 ha scritto:

 Hi All
Apologies for the self-reply.  I feel this is a bug, but before I can raise 
one, I understand that it first needs to be confirmed by a third party.  I was 
therefore wondering if anyone might be able to confirm the following:
1) It should be possible for an ImageMosaic layer to use a pre-populated 
timestamp column in an existing granule index (i.e. database table).2) The 
indexer.properties file below looks reasonable.
Many thanks in advance,
Andrew


On Monday, 12 July 2021, 14:43:50 BST, Andrew Chamberlain via 
Geoserver-users  wrote:  
 
 Hi All,
Not sure if this should be possible, but I'm trying to configure an ImageMosaic 
layer, whereby the index is pre-populated in a Postgres database and includes a 
timestamp column for when the imagery was captured.  My indexer.properties file 
looks like:

TimeAttribute=datecapturedSchema=*geometry:Polygon,location:String,datecaptured:java.util.DatePropertyCollectors=UseExistingSchema=trueCaching=falseAbsolutePath=trueName=metadata

However, when creating the layer, the TIME dimension remains unavailable, with 
the message "Cannot enable, no attribute of type Date found".  I've also 
created an index in the database, in case this mattered.
I can't find an example of using a mosaic index with a pre-populated time, so 
was starting to wonder whether it's possible at all?
Have tried on versions 2.17 and 2.19.  Any pointers would be greatly 
appreciated.
Many thanks,
Andrew Chamberlain

P.S. The only hint of any issue is the following from the logs, but I imagine 
this is a red herring and just a minor UI issue? 2021-07-12 14:21:27,263 WARN 
[wicket.Localizer] - Tried to retrieve a localized string for a component that 
has not yet been added to the page. This can sometimes lead to an invalid or no 
localized resource returned. Make sure you are not calling 
Component#getString() inside your Component's constructor. Offending component: 
[DimensionEditor [Component id = time]]

___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

-- 
Mr. Carlo Cancellieri
skype: ccancellieriTwitter: @cancelliericLinkedIn: 
http://it.linkedin.com/in/ccancellieri/  ___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Image Mosaic Time Support with Existing DB Schema

[Andrew Chamberlain via Geoserver-users]

 Hi All
Apologies for the self-reply.  I feel this is a bug, but before I can raise 
one, I understand that it first needs to be confirmed by a third party.  I was 
therefore wondering if anyone might be able to confirm the following:
1) It should be possible for an ImageMosaic layer to use a pre-populated 
timestamp column in an existing granule index (i.e. database table).2) The 
indexer.properties file below looks reasonable.
Many thanks in advance,
Andrew


On Monday, 12 July 2021, 14:43:50 BST, Andrew Chamberlain via 
Geoserver-users  wrote:  
 
 Hi All,
Not sure if this should be possible, but I'm trying to configure an ImageMosaic 
layer, whereby the index is pre-populated in a Postgres database and includes a 
timestamp column for when the imagery was captured.  My indexer.properties file 
looks like:

TimeAttribute=datecapturedSchema=*geometry:Polygon,location:String,datecaptured:java.util.DatePropertyCollectors=UseExistingSchema=trueCaching=falseAbsolutePath=trueName=metadata

However, when creating the layer, the TIME dimension remains unavailable, with 
the message "Cannot enable, no attribute of type Date found".  I've also 
created an index in the database, in case this mattered.
I can't find an example of using a mosaic index with a pre-populated time, so 
was starting to wonder whether it's possible at all?
Have tried on versions 2.17 and 2.19.  Any pointers would be greatly 
appreciated.
Many thanks,
Andrew Chamberlain

P.S. The only hint of any issue is the following from the logs, but I imagine 
this is a red herring and just a minor UI issue? 2021-07-12 14:21:27,263 WARN 
[wicket.Localizer] - Tried to retrieve a localized string for a component that 
has not yet been added to the page. This can sometimes lead to an invalid or no 
localized resource returned. Make sure you are not calling 
Component#getString() inside your Component's constructor. Offending component: 
[DimensionEditor [Component id = time]]

___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Image Mosaic Time Support with Existing DB Schema

[Andrew Chamberlain via Geoserver-users]

Hi All,
Not sure if this should be possible, but I'm trying to configure an ImageMosaic 
layer, whereby the index is pre-populated in a Postgres database and includes a 
timestamp column for when the imagery was captured.  My indexer.properties file 
looks like:

TimeAttribute=datecapturedSchema=*geometry:Polygon,location:String,datecaptured:java.util.DatePropertyCollectors=UseExistingSchema=trueCaching=falseAbsolutePath=trueName=metadata

However, when creating the layer, the TIME dimension remains unavailable, with 
the message "Cannot enable, no attribute of type Date found".  I've also 
created an index in the database, in case this mattered.
I can't find an example of using a mosaic index with a pre-populated time, so 
was starting to wonder whether it's possible at all?
Have tried on versions 2.17 and 2.19.  Any pointers would be greatly 
appreciated.
Many thanks,
Andrew Chamberlain

P.S. The only hint of any issue is the following from the logs, but I imagine 
this is a red herring and just a minor UI issue? 2021-07-12 14:21:27,263 WARN 
[wicket.Localizer] - Tried to retrieve a localized string for a component that 
has not yet been added to the page. This can sometimes lead to an invalid or no 
localized resource returned. Make sure you are not calling 
Component#getString() inside your Component's constructor. Offending component: 
[DimensionEditor [Component id = time]]

___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Re: [Geoserver-users] Keycloak Roles

[Andrew Chamberlain via Geoserver-users]

 Hi Alessio,
Thank you for your quick reply.
Yes, I assigned the role to the user in Keycloak.  I'm thinking that it's the 
way I'm implementing the authentication chain.  It's useful to know that the 
user roles should all be picked up by Geoserver, and that what I'm trying 
should indeed work.  I suspect it's the way I'm defining the rules, but will 
investigate further and report back once I've solved the issue.
Many thanks for your help,

Andy

  
On Tuesday, 21 January 2020, 13:01:54 GMT, Alessio Fabiani 
 wrote:  
 
 Hello Andrew,in theory the role should be mapped to the user. You shouldn't 
need a new role service.
Have you assigned the new role to the user on Keycloak "geoserver-cleint" as 
shown at point 4?

Il giorno mar 21 gen 2020 alle ore 13:24 Andrew Chamberlain via Geoserver-users 
 ha scritto:

Hi All,
I'm in the process of integrating Keycloak in the manner described here:
https://docs.geoserver.org/latest/en/user/community/keycloak/index.html
This all works fine, but when I'm getting unexpected results when adding 
further roles to protect individual layers.  Having added the new role in both 
Keycloak and Geoserver, and then a rule to give that role read access to a 
particulat layer, the layer in question *disappears* from the layer preview, 
rather than being the only one available.  The Keycloak user being used to 
login has the role mapped to them, and their name appears in the top-right to 
indicate Geoserver has picked up the identity.
The roles must be getting passed, as the use of ROLE_AUTHENTICATED wouldn't 
work otherwise.  Do I need to add a Role Service, in addition to the Keycloak 
Adapter?

Any help would be much appreciated.
Many thanks,
Andy
Geoserver 2.15.2Keycloak 4.8.13


___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


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. Alessio Fabiani

@alfa7691
Founder/Technical Lead




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


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

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 
2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa 
che ogni circostanza inerente alla presente email (il suo contenuto, gli 
eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i 
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per 
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei 
comunque grato se potesse darmene notizia.


This email is intended only for the person or entity to which it is addressed 
and may contain information that is privileged, confidential or otherwise 
protected from disclosure. We remind that - as provided by European Regulation 
2016/679 “GDPR” - copying, dissemination or use of this e-mail or the 
information herein by anyone other than the intended recipient is prohibited. 
If you have received this email by mistake, please notify us immediately by 
telephone or e-mail.

  ___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Keycloak Roles

[Andrew Chamberlain via Geoserver-users]

Hi All,
I'm in the process of integrating Keycloak in the manner described here:
https://docs.geoserver.org/latest/en/user/community/keycloak/index.html
This all works fine, but when I'm getting unexpected results when adding 
further roles to protect individual layers.  Having added the new role in both 
Keycloak and Geoserver, and then a rule to give that role read access to a 
particulat layer, the layer in question *disappears* from the layer preview, 
rather than being the only one available.  The Keycloak user being used to 
login has the role mapped to them, and their name appears in the top-right to 
indicate Geoserver has picked up the identity.
The roles must be getting passed, as the use of ROLE_AUTHENTICATED wouldn't 
work otherwise.  Do I need to add a Role Service, in addition to the Keycloak 
Adapter?

Any help would be much appreciated.
Many thanks,
Andy
Geoserver 2.15.2Keycloak 4.8.13


___
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Return to slow loading of Oracle layers

[Andrew Chamberlain]

Hello All,
Following the welcome improvement in 2.8.0 for the faster loading of Oracle 
layer configurations, it seems that this enhancement is not as noticeable in 
subsequent versions (e.g. 2.9.x and the current 2.10 build).  Does anyone know 
why this might be?
The difference in startup times is significant: 15 seconds as opposed to 15 
minutes!
Many thanks,

Andy
--
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. http://sdm.link/zohodev2dev___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] GEOS-6812 (Oracle Start-up SQL Exception)

[Andrew Chamberlain]

Hi All,
I've just encountered the same problem as described in the above bug report 
(https://osgeo-org.atlassian.net/browse/GEOS-6812), and notice that the fix is 
said to be part of the master version of 2.9.x.  I've trawled the release notes 
and change logs, but can't find any mention of its inclusion.  Of course, I'll 
give the current master version (2.10) build a go anyway, but I was wondering 
if anyone could confirm if there's a target stable release that it's likely to 
be in?
Many thanks in advance,
Andy--
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. http://sdm.link/zohodev2dev___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] Logging of Web Admin Logins?

[Andrew Chamberlain]

Hi All,
Hope this isn't a noddy question.  Just wondering if anyone knew whether it's 
possible to audit (i.e. log to file) login attempts to the Geoserver web admin 
interface?

I've had a look at the monitoring extension, but that only seems to audit data 
requests.

Many thanks in advance,
Andy
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

[Geoserver-users] New LayerGroup via REST ignores styles in a workspace

[Andrew Chamberlain]

Hi All, Just trying to create a layergroup via Geoserver's REST APIand it seems 
that any style in a workspace is ignored in favour of thedefault style for the 
layer (as is the case for an empty  element). For example, if I copy the 
styles used by the "tasmania"layer group into the "topp" workspace, and specify 
them in the XML (see below),the created layer group does not use them. Am I 
doing anything wrong here? For information, the curl command I’m using (which 
seemsfine) is:   curl –u admin: –XPOST –H 'Content-type:text/xml' 
-d...@tasmania.xml http://localhost:8080/geoserver/rest/layergroups where 
tasmania.xml contains the XML below. Many thanks, Andy   
tasmania_new  SINGLE       tasmania_state_boundaries  
http://www.w3.org/2005/Atom"; 
rel="alternate"href="http://localhost:8080/geoserver/rest/layers/tasmania_state_boundaries.xml"type="application/xml"/>
          
tasmania_water_bodies  
http://www.w3.org/2005/Atom"; 
rel="alternate"href="http://localhost:8080/geoserver/rest/layers/tasmania_water_bodies.xml"type="application/xml"/>
          tasmania_roads   
   http://www.w3.org/2005/Atom"; 
rel="alternate"href="http://localhost:8080/geoserver/rest/layers/tasmania_roads.xml"type="application/xml"/>
          tasmania_cities  
    http://www.w3.org/2005/Atom"; 
rel="alternate"href="http://localhost:8080/geoserver/rest/layers/tasmania_cities.xml"type="application/xml"/>