GeoPackage operates as a normal JDBC DataStore, you may be able to improve the implementation to recognize the iso-date strings.
Looking in the geotools issue tracker there is one issue resolved <https://osgeo-org.atlassian.net/browse/GEOT-5355?jql=project%20%3D%20%22GEOT%22%20AND%20component%20%3D%20%22geopkg%22> with respect to dates being parsed incorrectly (MM and mm swapped). The issue was resolved but not confirmed, still it shows some support for time -- Jody Garnett On Tue, 5 Nov 2019 at 23:24, Richard Duivenvoorde <[email protected]> wrote: > > Forwarding from users list, hoping somebody of the dev's happens to know > if it should (or not) be possible to use a GeoPackage with a > time-dimension in Geoserver. > > For what I tested not ('Datetime' columns are always shown as 'String'), > but I'm hoping somebody tells me here, I am wrong... > > Regards, > > Richard Duivenvoorde > > > -------- Original Message -------- > Subject: Re: [Geoserver-users] Geopackage (Vectors) as Time Dimension / > WMS-T store. Experience? > Date: 2019-11-04 10:29 > From: Richard Duivenvoorde <[email protected]> > To: [email protected] > Reply-To: [email protected] > > Didn't :-) > Next try: not attached but downloadable: https://duif.net/dt.zip > In the meantime I also created an issue: > https://osgeo-org.atlassian.net/browse/GEOS-9392 > > Follow up (well I hope this attachment makes it through spamfilters...). > > Attached a minimal gpkg created with QGIS with a dt column being type > DATETIME. Both in QGIS and in sqlitebrowser the type of the column is > shown as DATETIME, attached also a screenie of sqlitebrowser. > > But registring this gpkg in Geoserver, the dt column is determined as a > String column (also screenie attached). > > Maybe I'll create an issue for this with same files attached. > > Regards, > > Richard Duivenvoorde > > On 04/11/2019 09.37, Richard Duivenvoorde wrote: > > Nobody? Trying to use Geopackage with datetime columns? > > > > I tried to edit a gpkg in QGIS with DB Manager to change the column to > > a > > DATETIME. Which seems > > > > Opening that gpkg in Sqlitebrowser revealed the columns as: > > > > CREATE TABLE "foo" > > ("fid" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, > > "geom" MULTIPOLYGON, > > "cell" REAL, > > "value" REAL, > > "datumtijd" DATETIME NOT NULL) > > > > But still GeoServer does not offer me a TimeDimension.. > > > > Anybody? > > > > Regards, > > > > Richard Duivenvoorde > > > > On 29/10/2019 20.44, Richard Duivenvoorde wrote: > >> Hi, > >> > >> I'm trying to get a Geopackage working in latest (2.16) Geoserver as > >> WMS-T (WMS with a Time Dimension). > >> The data has a geom table with a polygon-"grid" column, a dataset with > >> several time-based values per 'cell', AND a view which joins them > >> together. > >> The 'Time'-column is a seconds since epoch column. > >> > >> I found that Sqlite does not have a real datetime format, but does > >> have > >> several options to produce Datetime's based on text or integer columns > >> [0]. > >> But I failed to create a view which could be understand by Geoserver > >> that the column created was an actual 'datetime' > >> Anybody experience with this, or maybe have some more info? > >> > >> I also found that the geopackage spec defines a DATE and DATETIME type > >> [1] Requirement 5, but saves it as an sort of iso-string. Creating > >> such > >> a column did not work either. > >> With Geoserver I had the same issue: geoserver did not recognize the > >> column as a DateTime. > >> > >> So I wonder: should I be able to use a Geopackage as a DataStore for a > >> layer, to serve as a WMS-T with a TIME dimension? > >> Did I miss something? > >> Maybe do some remapping of types? > >> > >> Any hints/tips would be appreciated. > > > > > > _______________________________________________ > > 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 > > > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >
_______________________________________________ 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
