Opened 20 years ago

Closed 20 years ago

Last modified 20 years ago

#666 closed defect (fixed)

PARAMETER= not matched on RangeSet's Name

Reported by: warmerdam Owned by: sdlime
Priority: high Milestone:
Component: WCS Server Version: 4.3
Severity: normal Keywords:
Cc:

Description

Good news, I have succeeded with band selection.  However, I think there is
at least one issue.  I had to include "BANDS=" in the request, but the
describe coverage looks like this:

      <RangeSet>
        <name>Bands Rangeset?</name>
<!-- WARNING: Mandatory metadata '..._rangeset_label' was missing in this
context. -->
        <AxisDescription>
          <description>TM Bands 1-7</description>
          <name>Band</name>

          <label>Band number</label>
          <values>
            <singleValue>1</singleValue>
            <singleValue>2</singleValue>
            <singleValue>3</singleValue>
            <singleValue>4</singleValue>

            <singleValue>5</singleValue>
            <singleValue>6</singleValue>
            <singleValue>7</singleValue>
          </values>
        </AxisDescription>
      </RangeSet>

The mapfile definition looked like:

    "wcs_rangeset_axes" "bands"
    "wcs_rangeset_name" "Bands Rangeset?"
    "wcs_bands_description" "TM Bands 1-7"
    "wcs_bands_name" "Band"
    "wcs_bands_label" "Band number"
    "wcs_bands_values" "1,2,3,4,5,6,7"
    "wcs_bands_rangeitem" "_bands"

I read over the PARAMETER= stuff, and it should be matching the parameter
name against the <Name> of the AxisDescription, not our internal name for
the rangeset.   Either the parameter name should be based on the <Name> of
the axis, or we should get rid of the wcs_<rangeset>_name altogether and 
just use our internal rangeset axis name as the <Name>.  I would suggest the
second option.

Change History (3)

comment:1 by sdlime, 20 years ago

Status: newassigned
I agree with the second option. I'll make the change...

comment:2 by sdlime, 20 years ago

Resolution: fixed
Status: assignedclosed
I believe this has been fixed. The rangeset name is now generated from
"wcs_rangeset_axes" values so wcs_xxxxx_name is no longer necessary.

Steve

comment:3 by fwarmerdam, 20 years ago

Steve,

Cool, thanks.

I see the describecoverage result still shows some required items missing.
I will change the code to auto-generate these values as well so by default
the bands describecoverage works smoothly if bands is listed in the axes
list. 

    <rangeSet>
      <RangeSet>
<!-- WARNING: Mandatory metadata '..._rangeset_name' was missing in this
context. -->
<!-- WARNING: Mandatory metadata '..._rangeset_label' was missing in this
context. -->
        <AxisDescription>
          <name>bands</name>
<!-- WARNING: Mandatory metadata '..._bands_label' was missing in this context. -->
          <values>
          </values>

        </AxisDescription>
      </RangeSet>
Note: See TracTickets for help on using tickets.