|
|
Jonathan Meyer created an issue |
|
Issue Type: |
|
|---|---|
|
Affects Versions: |
2.6.1, 2.5.3, 2.4.8 |
|
Assignee: |
|
|
Components: |
WCS, WMS |
|
Created: |
20/Nov/14 10:50 AM |
|
Environment: |
All platforms and currently released versions of GeoServer |
|
Labels: |
wms wcs |
|
Priority: |
|
|
Reporter: |
Major|
WMS TIME parameter currently has no support for specifying a relative time. For example, if I wanted to create a KML overlay that could be loaded into Google Earth and remain up to date with the last 24 hours of data I would have to create a service outside of GeoServer to accomplish this. Providing a means to specify a sliding period of time to display back from present time would be valuable for temporal datasets with a constant stream of data. I’ve reviewed both WMS and WCS specs and the closest thing to this is the ‘current’ and ‘now’ keywords which are somewhat misleading. Both mean the latest available data within the dataset, not the present point in time. I’d like to propose a new capability that would provide capability beyond these specs to allow relative time to be specified. Allow ‘present’ to represent the present date/time in the locale of the GeoServer and ‘back’ to represent some specified interval back from the present date/time. Here are some example values for the TIME parameter based on this convention:
As a side note, I’ve ensured that all unit tests for existing ‘current’/‘now’ keywords within WMS/WCS/OWS projects still pass |
|
|
|
This message was sent by Atlassian JIRA (v6.1.6#6162-sha1:7af547c) |
|
|
