Opened 8 years ago
Closed 7 years ago
#1491 closed enhancement (fixed)
WMS style management
| Reported by: | Dimitar Misev | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 9.5 |
| Component: | petascope | Version: | development |
| Keywords: | Cc: | Peter Baumann, Vlad Merticariu, Bang Pham Huu | |
| Complexity: | Medium |
Description
I think it would be good to have WMS style management capabilities in the WCS client. This tab could also contain a WCPS → rasql query fragment translation tool (#1490).
On this occasion, maybe OGC WS client is a better name than WCS client?
Change History (4)
comment:1 by , 7 years ago
| Milestone: | 9.4 → Future |
|---|
comment:2 by , 7 years ago
| Milestone: | Future → 9.5 |
|---|
comment:4 by , 7 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
although it is not urgent but can be done soon,
I propose to add a parent tab to differentiate WCS and WMS in WCS-Client, when changing parent tab, the children tabs will appear accordingly.
WCS | WMS
GetCapabilities | DescribeCoverage | GetCoverage | ProcessCoverage | InsertCoverage | DeleteCoverage
For WMS, it will have GetCapabilities tab as WCS which list imported layers, when clicking on a layer name, it will move to DescribeLayer tab where users can see the layer's bounding box, CRS, and styles of this layer, and can edit (insert, update, delete) the style here if they want.
Do you see any problems?