Opened 3 years ago

Closed 6 months ago

#731 closed defect (fixed)

Evaluate removal of axis type knowledge in WCS/WCPS

Reported by: pcampalani Owned by: vmerticariu
Priority: major Milestone: 9.3
Component: petascope Version: development
Keywords: axis type Cc: pbaumann, mdumitru
Complexity: Medium

Description

Petascope has always been assigning an type to an axis:

petascopedb_8=# select * from ps_axistype;
 id | axistype  
----+-----------
  1 | x
  2 | y
  3 | temporal
  4 | elevation
  5 | other
  6 | t
(6 rows)

Some constraints apply to the overall set of axis types owned by a coverage:

if (previous.getLabel().equals(next.getLabel())) {
    throw new PetascopeException(ExceptionCode.InvalidMetadata, "Duplicate domain "
    + "element name encountered for coverage " + coverageName);
}
if (previous.getType().equals(AxisTypes.ELEV_AXIS) && next.getType().equals(AxisTypes.ELEV_AXIS)) {
    throw new PetascopeException(ExceptionCode.InvalidMetadata, "Domain can contain"
    + " at most one elevation axis for coverage " + coverageName);
}
if (previous.getType().equals(AxisTypes.X_AXIS) && next.getType().equals(AxisTypes.X_AXIS)) {
    throw new PetascopeException(ExceptionCode.InvalidMetadata, "Domain can contain"
    + " at most one x axis for coverage " + coverageName);
}
if (previous.getType().equals(AxisTypes.Y_AXIS) && next.getType().equals(AxisTypes.Y_AXIS)) {
    throw new PetascopeException(ExceptionCode.InvalidMetadata, "Domain can contain"
    + " at most one y axis for coverage " + coverageName);
}

Going towards n-dimensional datasets, the type of axis can blur (eg using Index CRSs), moreover for instance more than a single time dimension should be possible in the same coverage.

Completely removing the notion of axis type should be evaluated in Petascope. Alternatively the constraints should be relaxed.

Current issues are:

Change History (6)

comment:1 Changed 3 years ago by pcampalani

Corrige: the uniqueness constraints regard spatial XYZ axes only, not time.

comment:2 Changed 3 years ago by pcampalani

  • Status changed from new to accepted

comment:3 Changed 3 years ago by pcampalani

  • Status changed from accepted to assigned

comment:4 Changed 2 years ago by dmisev

  • Milestone changed from 9.1 to 10.0

I thought axis type association has been removed from petascope, didn't know we still have this. Deferring to v10

comment:5 Changed 16 months ago by dmisev

  • Cc mdumitru added
  • Owner changed from pcampalani to vmerticariu

Not sure if it's still valid?

comment:6 Changed 6 months ago by bphamhuu

  • Milestone changed from 10.0 to 9.3
  • Resolution set to fixed
  • Status changed from assigned to closed

This ticket can be closed as the problem with contrainst axis does not occur anymore, for example: one can ingest a 5 D coverages (Lat, Long, Time, Ensemble, Forecast) and the axis type is (X, Y, t, other, other).

Note: See TracTickets for help on using tickets.