Opened 7 months ago

Closed 3 weeks ago

#1491 closed enhancement (fixed)

WMS style management

Reported by: dmisev Owned by:
Priority: major Milestone: 9.5
Component: petascope Version: development
Keywords: Cc: pbaumann, vmerticariu, bphamhuu
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 Changed 5 months ago by dmisev

  • Milestone changed from 9.4 to Future

comment:2 Changed 6 weeks ago by bphamhuu

  • Milestone changed from Future to 9.5

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?

comment:3 Changed 6 weeks ago by dmisev

I like the idea, +1
See also #1604

comment:4 Changed 3 weeks ago by bphamhuu

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.