Opened 6 years ago
Closed 6 years ago
#1800 closed enhancement (fixed)
WCS_Prettify coverage's extra metadata in JSON string from DescribeCoverage request
Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
---|---|---|---|
Priority: | major | Milestone: | 9.7 |
Component: | petascope | Version: | development |
Keywords: | Cc: | Dimitar Misev, Vlad Merticariu, bciurezu | |
Complexity: | Medium |
Description
With WCS DescribeCoverage on a coverage with extra metadata in JSON, the result is not human readable, e.g:
<covMetadata> { "Type of level": "Type of level", "Grib1_Parameter_name": "Parameter name", "MARS type": "MARS type", "Grib1_Parameter_id": "Parameter id", "GRIB_table_version": "Mars Param", "Originating_or_generating_Center": "European Centre for Medium-Range Weather Forecasts" } </covMetadata>
It should be prettified for this JSON string with indentations, e.g:
<covMetadata> { "Type of level": "Type of level", "Grib1_Parameter_name": "Parameter name", "MARS type": "MARS type", "Grib1_Parameter_id": "Parameter id", "GRIB_table_version": "Mars Param", "Originating_or_generating_Center": "European Centre for Medium-Range Weather Forecasts" } </covMetadata>
Then in WSClient it will just need to show the coverage's extra metadata with code prettifier library as same as it is in XML string.
Change History (3)
follow-up: 2 comment:1 by , 6 years ago
comment:2 by , 6 years ago
Replying to dmisev:
How are we certain that this extra metadata is in json format?
It has 2 format XML and JSON (just check first character "{" or "<").
comment:3 by , 6 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
How are we certain that this extra metadata is in json format?