Custom Query (2765 matches)
Results (64 - 66 of 2765)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#2746 | fixed | FIX - WMS should support CRS:84 CRS | ||
Description |
According to OGC WMS 1.3.0 standard: The <EX_GeographicBoundingBox> element (see 7.2.4.6.6) is conceptually similar to a BoundingBox in which the attribute CRS="CRS:84" is implicit. However, <EX_GeographicBoundingBox> shall not be used as a substitute for <BoundingBox CRS="CRS:84">. If the server wishes to provide bounding box information in the CRS:84 CRS, then a separate BoundingBox element explicitly naming CRS:84 shall be included in the service metadata
In WMS
<BoundingBox CRS="CRS:84" minx="-180.0" miny="-90.0" maxx="180.0" maxy="90.0"/> // NEW element <BoundingBox CRS="EPSG:4326" minx="-90.0" miny="-180.0" maxx="90.0" maxy="180.0"/> // Existing element
Also WMS http://localhost:8080/rasdaman/ows? service=WMS&version=1.3.0&request=GetMap&bbox=145.178167420814475,-41.74864253393665336,155.9749999999999943,-32.29864253393665052&crs=CRS:84&width=1010&height=884&layers=test_raster:output&styles=&format=image/png&transparent=TRUE |
|||
#2745 | fixed | FIX - WSClient - if coverage's metadata is invalid, DescribeCoverage tab should still show update metadata component for admin to update | ||
Description |
In case a coverage's metadata is invalid, in WSClient > |
|||
#2744 | fixed | FIX - WMS returns wrong result for coverage has geo extents less than its pyramid | ||
Description |
For example, coverage Lat: [27.042738498772914, 72.21573849877291] Lon: [-31.90040474382762, 46.19489525617238]
and its pyramid member Lat: [24.28426966834437012, 72.66326966834436] Lon: [-56.50514190170437, 72.9058580982956189] then this WMS request will return wrong result (it is stretched): curl 'http://localhost:8080/rasdaman/ows?service=WMS&request=GetMap&version=1.3.0&transparent=TRUE&layers=CLMS_Grassland_GRA_10m&styles=&format=image/png&width=256&height=256&crs=EPSG:4326&bbox=14,36,66,72.0' -o local_base_subset.png |