Wednesday, 23 September 2015

tile map service - Tileserver with time dimension



We are preparing a Tileserver to serve tiles with a time dimension that updates every day. I was wondering what could be the best approach for that or the ideas we had are a good way.


To illustrate the problem:


We have observations for every full hour over 10 hours. That would be then 10 timesteps if implemented with a timeslider. The observations change every day.


Our idea was to make 10 layers which are accessible over a different layername. The layername would reflect the time of the observation(e.g. ISO 8601 timestring) or could be a simple number like 1, 2, 3, ... for every timestep with a corresponding meta.xml containing the date of the first layer and the interval between the timesteps.


Of course it would be the best if the meta.xml would be something like a WMS GetCapabilities. Different tile serving softwares as MapProxy or Mapcache serve some kind of metadata.xml for TMS and WMTS GetCapabilities for WMTS but seem unable to insert a time dimension. How could we implement this? There was a post asking for implementations of the WMS time dimension for a WMTS but maybe in the meantime there where some developments. There is also a blog post on how the guys at nasa added a Dimension block to the WMTS GetCapabilites but I don't know which software they used for it. In the end we would prefer to use some existing standards over implementing our own structure.


Is this a good way to go? Do you think there is a better solution?




No comments:

Post a Comment

arcpy - Changing output name when exporting data driven pages to JPG?

Is there a way to save the output JPG, changing the output file name to the page name, instead of page number? I mean changing the script fo...