Hi!
In the wms spec, there is a description of a Dimension/Time format which gives clients the possibility to request maps for a given time/period.
I've got a mysql datastore connected to geoserver, and registered featuretypes to the datastore on top of that. In the featuretypeconfiguration, the time-column is recognized as a "date" type, and when I choose to use schema base "gml:AbstractFeatureType" I can even specify the date-format used. Excellent.
The problem, is that it seems like Geoserver _ignores_ TIME=xxx param in requests. Is this because I am doing something wrong, - or is it because getmap requests using the "time" param is not implemented?
In the featuretype configuration, I have specified the date as "gYearMonth" and the requests are typically like: http://localhost:9090/geoserver/wms?VERSION=1.1.0&REQUEST=GetMap&SERVICE=WMS&SRS=EPSG:4326&BBOX=78.4205493615305,12.9005030619421,78.4830606614971,12.953397238837&WIDTH=650&HEIGHT=550&LAYERS=hisp:CTR235&FORMAT=image/gif&STYLES=normal&TRANSPARENT=TRUE&UNIQUEID=&TIME=2002-01
The mysql column format is "date", and a typical value looks like this: 2002-01-01
Any help or ideas for eventual workarounds/solutions would be greatly appreciated
regards
Fredrik M Klausen
On 12/9/05, Fredrik Melsom Klausen <fredrik@...378...> wrote:
Hi!
In the wms spec, there is a description of a Dimension/Time format which
gives clients the possibility to request maps for a given time/period.
I've got a mysql datastore connected to geoserver, and registered
featuretypes to the datastore on top of that. In the
featuretypeconfiguration, the time-column is recognized as a "date"
type, and when I choose to use schema base "gml:AbstractFeatureType" I
can even specify the date-format used. Excellent.
The problem, is that it seems like Geoserver _ignores_ TIME=xxx param in
requests. Is this because I am doing something wrong, - or is it because
getmap requests using the "time" param is not implemented?
In the featuretype configuration, I have specified the date as
"gYearMonth" and the requests are typically like:
http://localhost:9090/geoserver/wms?VERSION=1.1.0&REQUEST=GetMap&SERVICE=WMS&SRS=EPSG:4326&BBOX=78.4205493615305,12.9005030619421,78.4830606614971,12.953397238837&WIDTH=650&HEIGHT=550&LAYERS=hisp:CTR235&FORMAT=image/gif&STYLES=normal&TRANSPARENT=TRUE&UNIQUEID=&TIME=2002-01
The mysql column format is "date", and a typical value looks like this:
2002-01-01
Any help or ideas for eventual workarounds/solutions would be greatly
appreciated
I believe the TIME argument is curently ignored. I would love to be
wrong on this one though.
As to a workaround, depending on the sutiation, I do the following:
1) I encode the time step in the file name (for coverages).
2) For a FeatureType, I just construct the appropriate filter in the SLD.
3) I create (or replace) a view for a large RDBMS table, prior to
making a GetMap request.
Alex
Currently time and dimensions are ignore/ not implelmented - there is a long statnding jira out to implement them for me. I really will start to look at it soon, especially as more of my new job relates to this sort of stuff. Of course if some one else wants to start implementing them don’t let my vauge promises stop you.
Ian
–
Ian Turton
http://www.geotools.org