Changes between Version 3 and Version 4 of PetascopeTimeHandling


Ignore:
Timestamp:
Feb 7, 2013 2:55:14 PM (4 years ago)
Author:
pcampalani
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PetascopeTimeHandling

    v3 v4  
    2828A temporal axis is thus recognized by ''Petascope'' by its
    2929"'''[[span(`t`, style=color: DodgerBlue; font-size: 90%)]]'''" label (binding the label in the request subset and the value in
    30 [[span(`petascopedb::ps_domain.name`, style=color: IndianRed; font-size: 90%)]]), on which it assumes its `rasdaman` grid indexes are [http://en.wikipedia.org/wiki/Julian_day#Alternatives ANSI date] numbers. [[BR]]
     30[[span(`petascopedb::ps_domain.name`, style=color: IndianRed; font-size: 90%)]]), on which it assumes its coordinates are [http://en.wikipedia.org/wiki/Julian_day#Alternatives ANSI date] numbers. [[BR]]
    3131The `gml:RectifiedGridCoverage` of a response including a time-dimension fills temporal coordinates with ANSI integers at the domain ''"external CRS"'' level (e.g. `gml:offsetVector`, `gml:boundedBy`), and `rasdaman` indexes at the grid level (`gml:GridEnvelope`). [[BR]]
    3232Direct grid indexes can as well be directly set in the WCS request by forcing the "CRS:1" coordinate system (the current label for the internal grid-CRS of a coverage), like: "[[span(`...subset=t,CRS:1(0,10)...`), style=color: DarkBlue; font-size: 90%)]]".