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 <[email protected]> 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
[email protected]
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
