Custom Query (2765 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (64 - 66 of 2765)

Ticket Resolution Summary Owner Reporter
#2746 fixed FIX - WMS should support CRS:84 CRS Bang Pham Huu Bang Pham Huu
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 GetCapabilities response, for each Layer element, it should contain the <BoundingBox> element for CRS:84 CRS

  • NOTE: OGC CITE WMS 1.3.0 conformance tests requires WMS GetMap requests with CRS:84 CRS e.g.
<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 GetMap request should support the request with bbox in CRS:84 (minLong,minLat,maxLong,maxLat), e.g.

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 Bang Pham Huu Bang Pham Huu
Description

In case a coverage's metadata is invalid, in WSClient > DescribeCoverage tab, it should still show the component to update coverage's metadata if the logged in user is admin. With that, he can update the coverage's metadata to fix the metadata issue.

#2744 fixed FIX - WMS returns wrong result for coverage has geo extents less than its pyramid Bang Pham Huu Bang Pham Huu
Description

For example, coverage CLMS_Grassland_GRA_10m has geo extent:

Lat: [27.042738498772914, 72.21573849877291]
Lon: [-31.90040474382762, 46.19489525617238]

and its pyramid member CLMS_Grassland_GRA_100m_4 has geo extent:

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
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.