Changes between Version 15 and Version 16 of PetascopeSubsets

Timestamp:

Nov 15, 2016, 10:34:10 AM (9 years ago)

Author:

Bang Pham Huu

Comment:

add the output CRS for encoding coverage.

PetascopeSubsets

@@ -143 +143 @@
 Practical examples will now follow. For open discussions on the policies we adopted, you are suggested to reply to [https://groups.google.com/d/msg/rasdaman-users/3Zaz6snbtgU/KSsEj2oIqAIJ this] post in our mailing list.
 
+== Set CRS for output coverage
+Suppose you have a 3D coverage which has 3 axes (Lat, Long and ansi) and the compoundCRS for this coverage is:
+ 
+{{{
+ http://localhost:8080/def/crs-compound?
+ 1=http://localhost:8080/def/crs/EPSG/0/4326&
+ 2=http://localhost:8080/def/crs/OGC/0/AnsiDate
+}}}
+
+so when you want to slice on the ansi axis (i.e: subset with slicing on this axis, example:
+{{{
+ localhost:8080/rasdaman/ows?&SERVICE=WCS&VERSION=2.0.1&REQUEST=GetCoverage&COVERAGEID=test_AverageTemperature&SUBSET=ansi(150455)&FORMAT=image/tiff
+}}}
+the output image will have EPSG:4326 as geo-referenced CRS. 
+
+{{{
+ Coordinate System is:
+GEOGCS["WGS 84",
+    DATUM["WGS_1984",
+        SPHEROID["WGS 84",6378137,298.257223563,
+            AUTHORITY["EPSG","7030"]],
+        AUTHORITY["EPSG","6326"]],
+    PRIMEM["Greenwich",0],
+    UNIT["degree",0.0174532925199433],
+    AUTHORITY["EPSG","4326"]]
+}}}
+
+However, if you want to slice on Latitude axis or Longitude axis.
+{{{
+localhost:8080/rasdaman/ows?&SERVICE=WCS&VERSION=2.0.1&REQUEST=GetCoverage&COVERAGEID=test_AverageTemperature&SUBSET=Lat(0)&FORMAT=image/tiff
+}}}
+
+the output image will have axes combined from Long&ansi or Lat&ansi (depend on which axis you want to slice above (Long or Lat)). ''There is non-existing CRS which made of a geo-referenced axis (Long or Lat) and a time axis (ansi).'' '''Therefore, the output coverage in 2D will have no CRS'''.
+
+
+
+
 
 == Examples