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
<daniele.romagn...@geosolutionsgroup.com> 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 <geo.ccancelli...@gmail.com>
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
<geoserver-users@lists.sourceforge.net> 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 <geoserver-users@lists.sourceforge.net> 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
_______________________________________________
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
