oscarfonts
commented
12 years ago Timestamps in "layers.json" will be rendered in a way that reflect the actual "granularity" of the data (determined in GeoStore):
- Yearly layers: "YYYY"
- Monthly layers: "YYYY-MM"
- Daily layers: "YYYY-MM-DD"
The client will parse them to build: a) the full ISO compliant timestamp, needed for WMS requests, where:
- Yearly date will be set to January 1st at 0:00 UTC.
- Monthly date will be set to the 1st day of the month at 0:00 UTC. b) the human-readable time string used in GUI. V. gr.:
- "Sept. 26, 2012"
- "Sept. 2012", or
- "Year 2012"
Note that human-readable representations have to be internationalized as well.
The time slider will render consecutive stops equispaced (aka, not keeping proportionality with time dimension).
For backwards compatibility, client part will also be capable of reading full ISO strings in layers.json, and will consider them as yearly data. The use of full ISO strings in layers.json will be considered deprecated (implying that documentation and actual custom configurations have to be changed).
Adapt time management to work with year, month and day.