Difference: UCDList_1-3_RFM (2 vs. 3)

Revision 32018-05-20 - MireilleLouys

 
META TOPICPARENT name="RFMforUCD"

Request for Modification for the UCD list v1.4 - from May 2017 to Feb 2018

This page is proposed in the new process for UCDs update discussed at the Interop meeting in Shanghai in May 2017. The new Note Maintenance for UCD specification mentions the details of the updating process. When a new UCD term seems necessary to include in the UCD list, a record describing the request for addition can be expressed as followed : new term proposed, rationale, example of usage, etc , as show in the list below.

The term is then discussed within the maintenance committee and the semantics working group and answers from the maintenance committee is given within 1 month.

Every 6 months the list of proposed changes are examined by the TCG and the validated changes are ingested in the new version of Endorsed Note for the UCD1+ list of terms.

Proposals from Solar and Planetary community ( B. Cecconi et al.)

Concept family : electric charge and current

  • Family : plasma environment
  • Proposal : phys.flux;phys.charge
  • Requires : phys.charge with definition : Electric charge and tag : Q
  • Answer: we understood the need for two concepts : electric current density and electric charge proposal for update:
add Q | phys.electCharge | Electric charge
add Q | phys.current | Electric current
add Q | phys.current.density | Electric current density

  • Status : inserted
  • Benefits : introduces phys.current; this definition is more focused on the requested concept --> implies better assignment
Concept family: Observation geometry ; Illumination conditions

  • Case:
    • Representation of the various angles : Explained in paper https://doi.org/10.1016/j.pss.2015.06.004
    • See figure attached here
    • theta_i = Incidence Angle, theta_e = Emergence Angle, alpha = Phase Angle
    • The angle phi (azimuth) is not required for illumination condition description (and we already have a UCD for this) from Baptiste Cecconi
  • Rationale: -from B. Cecconi - 06 July 2017 - see semantics list for the email threads
    • In planetary sciences ... our use cases are the following:
    • In EPNcore, the illumination conditions are search parameters, we have 6 separate columns for the min/max values of those 3 angles.
    • For planetary images or spectra, the product metadata must contain the observation geometry, and those 3 angles are to be there, altogether.
Concept: Incidence angle

  • Proposal: pos.incidenceAng
  • Requires:
    • definition : Incidence angle
    • tag : Q
  • preliminary answer proposed: pos.posAng.incidence with definition : "Angle of incidence of a vector e.g illumination vector"
  • Discussion: There is a debate about this (S.Erard): incidence and emergence are physical angles of an optical ray on an interface / can be like pos.phaseAng; then it could logically be hooked under pos directly , as pos.phaseAng
  • answer: This is understood that we deal here with generic optical angles.
add Q | pos.incidenceAng | Incidence angle of optical ray on an interface
Concept: Emergence angle

  • proposal: pos.emergenceAng
  • Requires:
    • definition : Emergence angle
    • tag : Q
  • Answer: see discussion about incidence angle
add Q | pos.emergenceAng | Emergence angle of optical ray on an interface

Concept: Azimuth angle

  • Proposal: pos.azimuthAng
  • Requires:
    • definition : Azimuthal angle
    • tag : Q
  • Discussion: azimuthal angle is already defined in the ucd tree by:
    • pos.az.azi exists but implies an alt-azimuthal ccordinate system.
  • Answer: see discussion about incidence angle
add Q | pos.azimuth | azimuthal angle in a generic reference plane
Concept family: spectroscopic measures
Concept : radiance
Changed:
<
<
  • Proposal: definition of phot.radiance is not completely adequate. It should be radiant power from the source per unit area (of source) and unit solid angle
>
>
  • Proposal: definition of phot.radiance is not completely adequate. It should be radiant power from the source per unit area (of source) and unit solid angle
 
  • Discussion: TBD
Concept : reflectance

Reflectances are relative quantities comparing input radiance or flux to the observed radiance, with various adimensional nomalization, so that their units can't be used for decide which actual physical quantity is shared or plotted. As current spectral analysis tools are using UCDs to decide how to combine data from various sources, there is a need for high level descriptors to sort out the most obvious kinds of normalization of processing. Without this, comparisions between dataset may lead to meaningless results.

  • proposal: phys.reflectance
  • rationale: different from albedo, which is valid at a given wavelength or frequency.
Changed:
<
<
  • definition: This is a radiance factor: observed radiance divided by input radiance. This quantity derives from the surface or interface properties.
  • annotation master : to check ; consequence : change definition to albedo and remove reflectance
>
>
  • definition: This is a radiance factor: observed radiance divided by input radiance. This quantity derives from the surface or interface properties.
  • annotation master : to check ; consequence : change definition to albedo and remove reflectance
 
    • | phys.albedo | Albedo or reflectance
  • Discussion: it is preferable to add a new term
  • Possible derived usage : Radiance Factor : arith.factor;phys.reflectance
  • Answer: the reflectance term is added.
add Q | phys.reflectance | Radiance factor (received radiance divided by input radiance)

Changed:
<
<
  • Proposal: phys.reflectance.I_over_F
  • Rationale: This a specific measured reflectance, which may include the thermal emission of the body. This is defined as the observed radiance, divided by the input illumination flux (solar flux for planetary bodies). No correction for the black body emission is done on this quantity.
>
>
  • Proposal: phys.reflectance.I_over_F
Added:
>
>
  • Rationale: This a specific measured reflectance, which may include the thermal emission of the body. This is defined as the observed radiance, divided by the input illumination flux (solar flux for planetary bodies). No correction for the black body emission is done on this quantity.
 
  • Discussion: open
  • Proposal: phys.reflectance.bidirectional
Changed:
<
<
  • definition: bidirectional reflectance
>
>
  • Definition: bidirectional reflectance
 
    • tag : Q
Changed:
<
<
  • Discussion:The current accepted short name is bidir
>
>
  • Discussion:The current accepted short name is bidir
 
  • Answer: add new term
add Q | phys.reflectance.bidirectional | Bidirectional reflectance
  • Proposal: phys.brdf
Changed:
<
<
  • definition: bidirectional reflectance distribution function
>
>
  • Definition: bidirectional reflectance distribution function
 
    • tag: Q
Changed:
<
<
  • discussion: check if phys.reflectance.bidirectional;instr.det.psf would do ?
>
>
  • Discussion: check if phys.reflectance.bidirectional;instr.det.psf would do ?
 
    • no, this is specific to normalization
Changed:
<
<
  • Answer: add new term (the current accepted short name is BRDF )
>
>
  • Answer: add new term (the current accepted short name is BRDF )
 add Q | phys.reflectance.bidirectional.df | Bidirectional reflectance distribution function
Deleted:
<
<
 
Changed:
<
<
  • Proposal: phys.reflectance.factor
  • Definition: reflectance normalized per direction cosine of incidence angle ??
>
>
  • Proposal: phys.reflectance.factor
  • Definition: reflectance normalized per direction cosine of incidence angle ??
 
    • tag : Q
  • Answer: add new term
add Q | phys.reflectance.factor | Reflectance normalized per direction cosine of incidence angle

  • NB : check relevance and possible ambiguity with radiance factor...
    • for normalized reflectance concept
    • proposal arith.ratio;phys.reflectance
Changed:
<
<
    • definition : reflectance normalized per reflectance at one wavelength
>
>
    • definition : reflectance normalized per reflectance at one wavelength
 
Concept family: Coordinate frames
Concept : Cylindrical coordinates
Changed:
<
<		proposal: pos.cylindrical
family : SSIG coordinates systems
rationale: no such coordinate branch in the UCD tree yet
definition : Cylindrical coordinates
tag : S
>
>
  • Proposal: pos.cylindrical
Added:
>
>
  • Rationale : SSIG coordinates systems. No such coordinate branch in the UCD tree yet.
  • Definition : Cylindrical coordinates
    • tag : S
  • Answer: add new term
add S |pos.cylindrical |Related to cylindrical coordinates
 
Changed:
<
<		##answer accepted S pos.cylindrical "Related to cylindrical coordinates"
>
>
Added:
>
>
  • Proposal: pos.cylindrical.r
  • Requires :pos.cylindrical
  • Definition : Cylindrical coordinate (radial distance from z-axis)
    • tag : Q
  • Answer: add new term
add Q | pos.cylindrical.r | Radial distance from z-axis (cylindrical coordinates)
 
Changed:
<
<		proposal: pos.cylindrical.r
requires :pos.cylindrical
definition : Cylindrical coordinate (radial distance from z-axis)
tag : Q
>
>
  • Proposal: pos.cylindrical.th
Added:
>
>
  • Definition : Cylindrical coordinate (Azimuthal angle around z-axis)
    • tag : Q
  • Discussion The conventions for the name of the angles varies : see http://mathworld.wolfram.com/CylindricalCoordinates.html prefered azi instead of th
  • Answer: add new term
add Q | pos.cylindrical.azi | Azimuthal angle around z-axis (cylindrical coordinates)
 
Changed:
<
<		##answer accepted as pos.cylindrical.r "Radial distance from z-axis (cylindrical coordinates)"
>
>
  • Proposal: pos.cylindrical.z
Added:
>
>
  • Definition : Cylindrical coordinate (height from reference plane)
    • tag : Q
  • Answer: add new term
add Q | pos.cylindrical.z | Height or altitude from reference plane (cylindrical coordinates)
 
Changed:
<
<		proposal: pos.cylindrical.th
definition : Cylindrical coordinate (Azimuthal angle around z-axis)
tag : Q
>
>		 NB: less ambiguous as for angle names
 
Deleted:
<
<		##answer The conventions for the name of the angles varies : seehttp://mathworld.wolfram.com/CylindricalCoordinates.html

##answer accepted as pos.cylindrical.azi "Azimuthal angle around z-axis (cylindrical coordinates)"

proposal: pos.cylindrical.z

definition : Cylindrical coordinate (height from reference plane)
tag : Q

##answer accepted as pos.cylindrical.z "Height or altitude from reference plane (cylindrical coordinates)"

## less ambiguous as for angle names

 
Concept: Spherical Coordinates
Changed:
<
<		proposal: pos.spherical
Rationale: not present in UCD tree definition : spherical coordinates
tag : S
>
>
  • Proposal: pos.spherical
Added:
>
>
  • Rationale: not present in UCD tree definition : spherical coordinates
    • tag : S
  • Answer: add new term
add S | pos.spherical | Related to cylindrical coordinates
 
Changed:
<
<		##answer accepted pos.spherical "Related to cylindrical coordinates"
>
>
  • Proposal: pos.spherical.r
Added:
>
>
  • Definition : spherical coordinate (radial distance from origin)
    • tag : Q
  • Answer: add new term
add Q | pos.spherical.r | Radial distance or radius (spherical coordinates)
 
Changed:
<
<		proposal: pos.spherical.r
definition : spherical coordinate (radial distance from origin)
tag : Q
>
>
  • Proposal: pos.spherical.th
Added:
>
>
  • definition : spherical coordinate (colatitude angle)
    • tag : Q
  • Answer: add new term
  • Discussion: same as for cylindrical : various angle names depending on definitions ( http://mathworld.wolfram.com/SphericalCoordinates.html )
  • proposed to use the physical name for this angle : colatitude to avoid any notation dependency/ambiguity
add Q | pos.spherical.colat |Polar or Colatitude angle (spherical coordinates)
 
Changed:
<
<		## answer accepted as pos.spherical.r "Radial distance or radius (spherical coordinates)"
>
>
  • Proposal: pos.spherical.ph
Added:
>
>
  • definition : spherical coordinate (Azimuth angle)
    • tag : Q
  • Answer: add new term
add Q | pos.spherical.azi | Azimuthal angle (spherical coordinates)
 
Changed:
<
<		proposal: pos.spherical.th
definition : spherical coordinate (colatitude angle)
tag : Q
>
>		Concept : orbital parameters
 
Changed:
<
<		##answer same as for cylindrical : various angle names depending on definitions ( http://mathworld.wolfram.com/SphericalCoordinates.html )
>
>		%Comment perifocal "src.orbital.periastron" exists but is slightly different
%Comment periapsis : check variation in meaning
 
Changed:
<
<		##answer proposed as pos.spherical.colat "Polar or Colatitude angle (spherical coordinates)"

proposal: pos.spherical.ph
definition : spherical coordinate (Azimuth angle)
tag : Q

>
>
  • Proposal: src.orbital.periapsis
  • Definition : minimal distance to the center of mass for an orbit
    • tag : P
  • Answer discussion postponed not yet decided
Deleted:
<
<		##answer proposed as pos.spherical.azi " Azimuthal angle (spherical coordinates)"

Concept : orbital parameters

%Comment perifocal "src.orbital.periastron" exists but is slightly different
%Comment periapsis : check variation in meaning
proposal: src.orbital.periapsis
definition : minimal distance to the center of mass for an orbit
tag : P

##discussion postponed (time to go to lunch)

 
Concept : rotation params for 3D parameters
Changed:
<
<		 ##answer
>
>		Discussion pos. is the right branch to hook these rotation concepts.
 
Changed:
<
<		##pos. is the right branch to hook these rotation concepts
_##pos.wcs exist for 2D transformation ; pos.rotation will handle the 3D case --> propose pos.rotation3d_
##theses parameters will be used soon with real data . We decide to delay the addition and will consider several examples
>
>		pos.wcs exist for 2D transformation ;
 
Changed:
<
<
proposal: pos.rotation
definition : Relative to rotation
tag : S
proposal: pos.rotation.eulerAngle
definition : Euler angles vector
tag : V
proposal: pos.rotation.quaternion
definition : rotation quaternion vector
tag : V
proposal: pos.rotation.matrix
definition : rotation matrix
tag : V
proposal: pos.rotation.axis
definition : rotation axis vector
tag : V
>
>		pos.rotation will handle the 3D case --> propose pos.rotation3d_
Deleted:
<
<
Concept: spatial resolution
 
Changed:
<
<		rationale: linear resolution on cartesian or linear spatial axis as opposed to angular resolution
proposal: pos.resolution
definition : Spatial linear resolution (not angular)
tag : Q
>
>		Theses parameters will be used soon with real data .
Added:
>
>
  • Answer: We decide to delay the addition and will consider several examples
 
Changed:
<
<		##answer add Q | pos.resolution | Spatial linear resolution (not angular)
##inserted
>
>
  • proposal : pos.rotation
Added:
>
>
  • definition : Relative to rotation
    • tag : S
  • proposal: pos.rotation.eulerAngle
  • definition : Euler angles vector
    • tag : V
  • proposal : pos.rotation.quaternion
  • definition : rotation quaternion vector
    • tag : V
  • proposal: pos.rotation.matrix
  • definition : rotation matrix
    • tag : V
  • proposal : pos.rotation.axis
  • definition : rotation axis vector
    • tag : V
Concept: spatial resolution
 
Changed:
<
<
Concept: heliocentric coordinates
>
>
  • Proposal : pos.resolution
  • Rationale : linear resolution on cartesian or linear spatial axis as opposed to angular resolution
Added:
>
>
  • Definition : Spatial linear resolution (not angular)
    • tag : Q
  • Answer: add new term
add Q | pos.resolution | Spatial linear resolution (not angular)
 
Changed:
<
<		longitude and latitude can be expressed as
proposal: pos.bodyrc.lon;pos.heliocentric
proposal: pos.bodyrc.lat;pos.heliocentric
% induced changes in assign tool: if heliocentric, or centric except geocentric , --> not earth .... change token

##answer agreed to modify assigning tool - done
>
>
Concept: heliocentric coordinates
 
Changed:
<
<		##discussion: In body-centric coordinates, longitudes are defined from sub-observer point, while body-graphic coordinates are defined from a standard body reference frame
>
>
  • Discussion longitude and latitude can be expressed in the heliocentric coordinate system
Added:
>
>
  • Proposal : pos.bodyrc.lon;pos.heliocentric pos.bodyrc.lat;pos.heliocentric
% induced changes in assign tool: if heliocentric, or centric except geocentric , --> not earth .... change token
  • Decision : agreed to modify assigning tool - done
  • Discussion : In body-centric coordinates, longitudes are defined from sub-observer point, while body-graphic coordinates are defined from a standard body reference frame
TODO: VESPA team to check consistency between heliocentric and planetocentric definitions
  • Answer: add new term
add S | pos.bodycentric | Body-centric related coordinate
 
Changed:
<
<		VESPA team to check consistency between heliocentric and planetocentric definitions
>
>		 add S | pos.bodygraphic | Body-graphic related coordinate
Added:
>
>
 
Deleted:
<
<		##answer add S | pos.bodycentric | Body-centric related coordinate <br/> ##answer add S | pos.bodygraphic | Body-graphic related coordinate

##inserted

 
Metadata branch

Changed:
<
<
Concept: checksum
>
>		Concept: checksum
 
Changed:
<
<		 proposal: meta.checksum
>
>
  • Proposal: meta.checksum
Added:
>
>
  • rationale : to check integrity of data
  • definition : numerical signature of digital data
    • tag : Q
  • Answer: add new term
add Q | meta.checksum | Numerical signature of digital data
 
Changed:
<
<		rationale: to check integrity of data
>
>		Concept: modification date of a dataset
 
Changed:
<
<		 definition : numerical signature of digital data
>
>
  • proposal: time.update
Added:
>
>
  • definition : modification date for a dataset
  • discussion :time.processing already exists and can be used here . only the definition of the ucd term to be modified
??? update of the definition in the UCD list
 
Changed:
<
<		 tag : Q
>
>
 
Changed:
<
<		##answer add Q | meta.checksum | Numerical signature of digital data <br/>##inserted
>
>		Other items
Deleted:
<
<
Concept: modification date of a dataset
 
Deleted:
<
<		 proposal: time.update

definition : modification date for a dataset

##answer : use *time.processing*

done : add update in the definition of this ucd

Other item
 
Changed:
<
<
Concept: shape of planetary objects
>
>
Concept: shape of planetary objects
 
Changed:
<
<		%this is used to represent the 3D shape of object: a 3D lattice

proposal: phys.shape
definition : 3D shape of an object
tag : Q
usage : phys.shape;meta.modelled for a 3D shape model
usage : phys.shape;pos.bodyrc.alt for elevation or terrain model (distribution of altitude on top of a reference ellipsoid or geoid )

##discussion: postponed until a real case is met

>
>		%this is used to represent the 3D shape of object: a 3D lattice
  • proposal : phys.shape
  • definition : 3D shape of an object
Added:
>
>
    • tag : Q
  • Rationale : consider usage like phys.shape;meta.modelled for a 3D shape model, or phys.shape;pos.bodyrc.alt for elevation or terrain model (distribution of altitude on top of a reference ellipsoid or geoid )
  • Answer discussion: postponed until a real case is met
 
Concept: spectral polarization data

#concept :spatial matrix
rationale: helps to identify or characterize measurement type

Changed:
<
<
proposal: phys.polarization.coherenceMatrix
definition: coherence matrix of radio signals
usage phys.polarisation.coherenceMatrix:instr
tag:Q
>
>
  • proposal : phys.polarization.coherenceMatrix
Added:
>
>
  • definition : coherence matrix of radio signals
  • rationale phys.polarisation.coherenceMatrix:instr
    • tag:Q
  • Answer: add new term
add Q | phys.polarization.coherency | Matrix of the correlation between components of an electromagnetic wave
 
Changed:
<
<		##answer add Q | phys.polarization.coherency | Matrix of the correlation between components of an electromagnetic wave
>
>		NB: This will work for all electromagnetic signals and not only in radio regime
 
Changed:
<
<		This will work for all electromagnetic signals and not only in radio regime
>
>		caveat: not compatible to instr branch in the UCD tree.
Deleted:
<
<		 not compatible to instr branch in the UCD tree.
 

<!--

* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->

View topic | History: r11 < r10 < r9 < r8 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback