Using GeoServer I want to deliver some objects/features with WFS and WMS. The objects and their attributes have a date range during which they are valid. Say, we have street lamps and each street lamp has an ID
, POINT (geom)
, start_date
, end_date
.
The WMS and WFS request can use the time
parameter to filter the resulting objects (see WFS GetFeature with time, WMS GetMap with time). Using the time filter, only the street lamps that a within start_date
and end_date
would be returned by GeoServer .
However, I now saw that for time
the respective time column must be stored with a date
type. That is, in geoserver one cannot configure start or end date columns for a WMS or WFS layer. It is only possible to configure a single date column (same for MapServer).
What's the best way to store my street lamps in PostgreSQL/PostGIS? For a lamp that was created on Jan 01, 2014 and destroyed on Jan 20, 2014 would I need to have 20 data sets in my database:
ID GEOM DATE
01 xy 2014-01-01
01 xy 2014-01-02
...
01 xy 2014-01-19
01 xy 2014-01-20
Is there a way to store date ranges in PostgreSQL/PostGIS that can be used by GeoServer? Or is this impossible?
tsrange
data type, but just a pair of timestamps would be quite sufficient in a pinch. – Craig Ringer May 15 '14 at 12:31tsrange
as GeoServer (and GeoTools) have to function over a lot of datastores – Ian Turton♦ May 15 '14 at 13:13