I'm working on trying to send data to a (closed-source) WMS client that doesn't like my GeoServer WMS GetCapabilities response.
The data is wave height (from the WaveWatch III model, thanks to all those who worked on 4D support, and on netCDF and GRIB support). From the logs, the problem appears to be the time dimension: <Dimension name="time" default="2015-03-09T00:00:00Z" units="ISO8601">2015-03-09T00:00:00.000Z/2015-03-09T00:00:00.000Z/PT1S,2015-03-09T03:00:00.000Z/2015-03-09T03:00:00.000Z/PT1S,2015-03-09T06:00:00.000Z/2015-03-09T06:00:00.000Z/PT1S,2015-03-09T09:00:00.000Z/2015-03-09T09:00:00.000Z/PT1S,2015-03-09T12:00:00.000Z/2015-03-09T12:00:00.000Z/PT1S</Dimension> (it keeps going, I've just trimmed the data here). Specifically, that client doesn't like the end time not being greater than the start time. I'm going to have to fix this on the server side (or perhaps via some XSLT magic on the client side), but I'm wondering if that is really "legal" per the WMS 1.3.0 spec and OGC 12-111r1 best practice guide. If the start and end are the same, should we really be doing just a list of instants: <Dimension name="time" default="2015-03-09T00:00:00Z" units="ISO8601">2015-03-09T00:00:00.000Z,2015-03-09T03:00:00.000Z,2015-03-09T06:00:00.000Z,2015-03-09T09:00:00.000Z,2015-03-09T12:00:00.000Z,2015-03-09T15:00:00.000Z</Dimension> Irrespective of whether it is legal / compliant, are there interoperability reasons why we need to keep the start/start/PT1S convention anyway? Basically, I'm trying to figure out if I should try to put this change upstream or just keep it local. Brad ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
