diff --git a/doc/Makefile b/doc/Makefile index 22949f0..2c8a8f1 100644 --- a/doc/Makefile +++ b/doc/Makefile @@ -7,10 +7,10 @@ DOCNAME = MANGO DOCVERSION = 0.1 # Publication date, ISO format; update manually for "releases" -DOCDATE = 2025-05-19 +DOCDATE = 2025-06-02 # What is it you're writing: NOTE, WD, PR, REC, PEN, or EN -DOCTYPE = WD +DOCTYPE = PR # An e-mail address of the person doing the submission to the document # repository (can be empty until a make upload is being made) diff --git a/doc/ivoatexmeta.tex b/doc/ivoatexmeta.tex index dc82371..d3729a6 100644 --- a/doc/ivoatexmeta.tex +++ b/doc/ivoatexmeta.tex @@ -1,7 +1,7 @@ % GENERATED FILE -- edit this in the Makefile \newcommand{\ivoaDocversion}{0.1} -\newcommand{\ivoaDocdate}{2025-05-19} -\newcommand{\ivoaDocdatecode}{20250519} -\newcommand{\ivoaDoctype}{WD} +\newcommand{\ivoaDocdate}{2025-06-02} +\newcommand{\ivoaDocdatecode}{20250602} +\newcommand{\ivoaDoctype}{PR} \newcommand{\ivoaDocname}{MANGO} \renewcommand{\ivoaBaseURL}{https://www.ivoa.net/documents/MANGO} diff --git a/doc/mango.latex b/doc/mango.latex new file mode 100644 index 0000000..e69de29 diff --git a/doc/model.tex b/doc/model.tex index ed2d071..95bcf3f 100644 --- a/doc/model.tex +++ b/doc/model.tex @@ -64,7 +64,7 @@ \section{Model: mango } \subsection{Brightness} \label{sect:Brightness} - Observed brightness of the \texttt{MangoObject}. The distinction between fluxes and magnitudes is made by the unit. This property should refer to a photometric calibration as defined by the \texttt{Phot} data model (1.1). + Observed brightness of the \texttt{MangoObject}. The purpose of this property is to gather a brightness value with its error and the its photometric calibration The distinction between fluxes and magnitudes is made by the unit. The photometric calibration is modeled by the \texttt{Phot} data model (1.1). \subsubsection{Brightness.value} \textbf{vodml-id: Brightness.value} \newline @@ -86,7 +86,7 @@ \section{Model: mango } \subsection{Color} \label{sect:Color} - Property that describes a color of the \texttt{MangoObject}. The color is not an intrinsic property of the MANGO object, but a value relative to two filters or energy bands. + Property that describes a color of the \texttt{MangoObject}. The purpose of this property is to gather a color value with its error and the 2 related filters (high and low) The color can be given as a magnitude difference or an hardness ratio. \subsubsection{Color.value} \textbf{vodml-id: Color.value} \newline @@ -182,19 +182,19 @@ \section{Model: mango } \label{sect:EpochPosition} - This class (fig \ref{fig:EpochPosition}) is a flattened view of objects/concepts from the Astronomical Measurements Model \citep{2022ivoa.specQ1004R} that have been put together to form a consistent description of the position of an object moving over time. It consists of a celestial position, a proper motion, a radial velocity and a parallax and their associated errors encapsulated into the \texttt{EpochPositionErrors} class. The values of these properties are pulled from the underlying Astronomical Coordinates and Coordinate Systems model \citep{2022ivoa.spec.1004R} At a high level the properties map as follows: \begin{itemize} \item celestial position -> \texttt{meas:Position} \item proper motion -> \texttt{meas:ProperMotion} \item radial velocity -> \texttt{meas.Velocity} \item parallax -> no suitable counterpart at this time \end{itemize} All components use the same coordinate systems for both time and space coordinates. \begin{itemize} \item Both position and proper motion reuse \texttt{coords:LonLatPoint} elements. \item The space coordinate system is imported from \texttt{coords:spaceSys}. \item The time coordinate system is imported from \texttt{coords:timeSys}. \end{itemize} All components have their own units which must be consistent with each other. This consistency is not enforced by the model. Possible correlations between \texttt{EpochPosition} parameters are handled by the \texttt{EpochPositionCorrelations} class. Errors along the different axes are grouped in the \texttt{EpochPositionErrors} class. In some cases the errors might conflict with the correlations: \begin{itemize} \item \texttt{Ellipse} errors on position or proper motion must not be used together with the \texttt{longitudeLatitude} (or \texttt{pmLongitudePmLatitude}) correlation fields. In fact, using elliptical errors implies a correlation between the two spatial axes which must not conflict with the correlations defined in \texttt{EpochPositionCorrelations}. \end{itemize} + This class (fig \ref{fig:EpochPosition}) is a flattened view of objects/concepts from the Astronomical Measurements Model \citep{2022ivoa.specQ1004R} that have been put together to form a consistent description of the position of an object moving over time. It consists of a celestial position, a proper motion, a radial velocity and a parallax and their associated errors encapsulated into the \texttt{EpochPositionErrors} class. The values of these properties are pulled from the underlying Astronomical Coordinates and Coordinate Systems model \citep{2022ivoa.spec.1004R} At a high level the properties map as follows: \begin{itemize} \item celestial position -> \texttt{meas:Position} \item proper motion -> \texttt{meas:ProperMotion} \item radial velocity -> \texttt{meas.Velocity} \item parallax -> no suitable counterpart at this time \end{itemize} All components use the same coordinate systems for both time and space coordinates. \begin{itemize} \item Both position and proper motion reuse \texttt{coords:LonLatPoint} elements. \item The space coordinate system is imported from \texttt{coords:spaceSys}. \item The time coordinate system is imported from \texttt{coords:simeSys}. \end{itemize} It is recommended to use the \texttt{ObsDate} field to store the epoch of the observation instead of the \texttt{epoch} field of \texttt{coords:spaceSys}. There are 2 reasons for this: \begin{itemize} \item Using the epoch of \texttt{coords:spaceSys} requires to work with the \texttt{coords:CustomRefLocation} class to carry the reference location. This class does not support the standard reference locations such as e.g. BARYCENTER. \item the observation date can be read in a column and therefore change with each data row. I this case, it cannot be stored as an element of the space coordinate system but as an \texttt{EPochPosition} attribute. \end{itemize} All components have their own units which must be consistent with each other. This consistency is not enforced by the model. Possible correlations between \texttt{EpochPosition} parameters are handled by the \texttt{EpochPositionCorrelations} class. Errors along the different axes are grouped in the \texttt{EpochPositionErrors} class. In some cases the errors might conflict with the correlations: \begin{itemize} \item \texttt{Ellipse} errors on position or proper motion must not be used together with the \texttt{longitudeLatitude} (or \texttt{pmLongitudePmLatitude}) correlation fields. In fact, using elliptical errors implies a correlation between the two spatial axes which must not conflict with the correlations defined in \texttt{EpochPositionCorrelations}. \end{itemize} \subsubsection{EpochPosition.longitude} \textbf{vodml-id: EpochPosition.longitude} \newline \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline \textbf{multiplicity: 1} \newline - The longitude of the Point, as a Quantity with angular units (see \texttt{coords:LonLatPoint.lon}. + This parameter is a clone of the \texttt{coords:LonLatPoint.lat} component of \texttt{meas:Position} but applied to the \texttt{mango:EpochPosition} context. It matches the description given by \texttt{coords} data model: The longitude of the Point, as a Quantity with angular units (see \texttt{coords:LonLatPoint.lon}. \subsubsection{EpochPosition.latitude} \textbf{vodml-id: EpochPosition.latitude} \newline \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline \textbf{multiplicity: 1} \newline - The latitude of the Point, as a Quantity with angular units (see \texttt{coords:LonLatPoint.lat}. + This parameter is a clone of the \texttt{coords:LonLatPoint.lat} component of \texttt{meas:Position} but applied to the \texttt{mango:EpochPosition} context. It matches the description given by \texttt{coords} data model: The latitude of the Point, as a Quantity with angular units (see \texttt{coords:LonLatPoint.lon}). \subsubsection{EpochPosition.parallax} \textbf{vodml-id: EpochPosition.parallax} \newline @@ -206,25 +206,25 @@ \section{Model: mango } \textbf{vodml-id: EpochPosition.radialVelocity} \newline \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline \textbf{multiplicity: 1} \newline - The measured Velocity along of the radius axis (see \texttt{meas:Velocity.coord} in \cite{2022ivoa.spec.1004R}). + This parameter is a clone of the \texttt{coords:Coords.point} component of \texttt{meas:Velocity} but applied to the \texttt{mango:EpochPosition} context. It matches the description given by the \texttt{coords} data model: The measured Velocity along of the radial axis (see \texttt{meas:Velocity.coord} in \cite{2022ivoa.spec.1004R}). \subsubsection{EpochPosition.pmLongitude} \textbf{vodml-id: EpochPosition.pmLongitude} \newline \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline \textbf{multiplicity: 1} \newline - Velocity along the longitude axis in angular distance per unit time (see \texttt{meas:ProperMotion.coord}). + This parameter is a clone of the \texttt{coords:LonLatPoint.lon} component of \texttt{meas:ProperMotion} but applied to the \texttt{mango:EpochPosition} context. It matches the description given by \texttt{coords} data model: Velocity along the longitude axis in angular distance per unit time (see \texttt{meas:ProperMotion.coord}). \subsubsection{EpochPosition.pmLatitude} \textbf{vodml-id: EpochPosition.pmLatitude} \newline \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline \textbf{multiplicity: 1} \newline - Velocity along the latitude axis in angular distance per unit time (see \texttt{meas:ProperMotion.coord}). + This parameter is a clone of the \texttt{coords:LonLatPoint.lat} component of \texttt{meas:ProperMotion} but applied to the \texttt{mango:EpochPosition} context. It matches the description given by \texttt{coords} data model: Velocity along the latitude axis in angular distance per unit time (see \texttt{meas:ProperMotion.coord}). \subsubsection{EpochPosition.obsDate} \textbf{vodml-id: EpochPosition.obsDate} \newline \textbf{type: \hyperref[sect:DateTime]{mango:DateTime}} \newline \textbf{multiplicity: 0..1} \newline - Observation date expressed within the common time system if present. This attribute, if set, supersedes the epoch possibly given with the spatial coordinate system. + Observation date expressed within the common time system if present. This attribute, if set, supersedes the epoch possibly given with the spatial coordinate system(see the above). \subsubsection{EpochPosition.pmCosLat\_applied} \textbf{vodml-id: EpochPosition.pmCosLat\_applied} \newline diff --git a/doc/model_toc.tex b/doc/model_toc.tex index 411665f..d67a72c 100644 --- a/doc/model_toc.tex +++ b/doc/model_toc.tex @@ -116,19 +116,19 @@ \section{Epoch Position Properties} \label{fig:EpochPosition} \end{figure} \label{sect:EpochPosition} - This class (fig \ref{fig:EpochPosition}) is a flattened view of objects/concepts from the Astronomical Measurements Model \citep{2022ivoa.specQ1004R} that have been put together to form a consistent description of the position of an object moving over time. It consists of a celestial position, a proper motion, a radial velocity and a parallax and their associated errors encapsulated into the \texttt{EpochPositionErrors} class. The values of these properties are pulled from the underlying Astronomical Coordinates and Coordinate Systems model \citep{2022ivoa.spec.1004R} At a high level the properties map as follows: \begin{itemize} \item celestial position -> \texttt{meas:Position} \item proper motion -> \texttt{meas:ProperMotion} \item radial velocity -> \texttt{meas.Velocity} \item parallax -> no suitable counterpart at this time \end{itemize} All components use the same coordinate systems for both time and space coordinates. \begin{itemize} \item Both position and proper motion reuse \texttt{coords:LonLatPoint} elements. \item The space coordinate system is imported from \texttt{coords:spaceSys}. \item The time coordinate system is imported from \texttt{coords:timeSys}. \end{itemize} All components have their own units which must be consistent with each other. This consistency is not enforced by the model. Possible correlations between \texttt{EpochPosition} parameters are handled by the \texttt{EpochPositionCorrelations} class. Errors along the different axes are grouped in the \texttt{EpochPositionErrors} class. In some cases the errors might conflict with the correlations: \begin{itemize} \item \texttt{Ellipse} errors on position or proper motion must not be used together with the \texttt{longitudeLatitude} (or \texttt{pmLongitudePmLatitude}) correlation fields. In fact, using elliptical errors implies a correlation between the two spatial axes which must not conflict with the correlations defined in \texttt{EpochPositionCorrelations}. \end{itemize} + This class (fig \ref{fig:EpochPosition}) is a flattened view of objects/concepts from the Astronomical Measurements Model \citep{2022ivoa.specQ1004R} that have been put together to form a consistent description of the position of an object moving over time. It consists of a celestial position, a proper motion, a radial velocity and a parallax and their associated errors encapsulated into the \texttt{EpochPositionErrors} class. The values of these properties are pulled from the underlying Astronomical Coordinates and Coordinate Systems model \citep{2022ivoa.spec.1004R} At a high level the properties map as follows: \begin{itemize} \item celestial position -> \texttt{meas:Position} \item proper motion -> \texttt{meas:ProperMotion} \item radial velocity -> \texttt{meas.Velocity} \item parallax -> no suitable counterpart at this time \end{itemize} All components use the same coordinate systems for both time and space coordinates. \begin{itemize} \item Both position and proper motion reuse \texttt{coords:LonLatPoint} elements. \item The space coordinate system is imported from \texttt{coords:spaceSys}. \item The time coordinate system is imported from \texttt{coords:simeSys}. \end{itemize} It is recommended to use the \texttt{ObsDate} field to store the epoch of the observation instead of the \texttt{epoch} field of \texttt{coords:spaceSys}. There are 2 reasons for this: \begin{itemize} \item Using the epoch of \texttt{coords:spaceSys} requires to work with the \texttt{coords:CustomRefLocation} class to carry the reference location. This class does not support the standard reference locations such as e.g. BARYCENTER. \item the observation date can be read in a column and therefore change with each data row. I this case, it cannot be stored as an element of the space coordinate system but as an \texttt{EPochPosition} attribute. \end{itemize} All components have their own units which must be consistent with each other. This consistency is not enforced by the model. Possible correlations between \texttt{EpochPosition} parameters are handled by the \texttt{EpochPositionCorrelations} class. Errors along the different axes are grouped in the \texttt{EpochPositionErrors} class. In some cases the errors might conflict with the correlations: \begin{itemize} \item \texttt{Ellipse} errors on position or proper motion must not be used together with the \texttt{longitudeLatitude} (or \texttt{pmLongitudePmLatitude}) correlation fields. In fact, using elliptical errors implies a correlation between the two spatial axes which must not conflict with the correlations defined in \texttt{EpochPositionCorrelations}. \end{itemize} \subsubsection{EpochPosition.longitude} \textbf{vodml-id: EpochPosition.longitude} \newline \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline \textbf{multiplicity: 1} \newline - The longitude of the Point, as a Quantity with angular units (see \texttt{coords:LonLatPoint.lon}. + This parameter is a clone of the \texttt{coords:LonLatPoint.lat} component of \texttt{meas:Position} but applied to the \texttt{mango:EpochPosition} context. It matches the description given by \texttt{coords} data model: The longitude of the Point, as a Quantity with angular units (see \texttt{coords:LonLatPoint.lon}. \subsubsection{EpochPosition.latitude} \textbf{vodml-id: EpochPosition.latitude} \newline \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline \textbf{multiplicity: 1} \newline - The latitude of the Point, as a Quantity with angular units (see \texttt{coords:LonLatPoint.lat}. + This parameter is a clone of the \texttt{coords:LonLatPoint.lat} component of \texttt{meas:Position} but applied to the \texttt{mango:EpochPosition} context. It matches the description given by \texttt{coords} data model: The latitude of the Point, as a Quantity with angular units (see \texttt{coords:LonLatPoint.lon}). \subsubsection{EpochPosition.parallax} \textbf{vodml-id: EpochPosition.parallax} \newline @@ -140,25 +140,25 @@ \section{Epoch Position Properties} \textbf{vodml-id: EpochPosition.radialVelocity} \newline \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline \textbf{multiplicity: 1} \newline - The measured Velocity along of the radius axis (see \texttt{meas:Velocity.coord} in \cite{2022ivoa.spec.1004R}). + This parameter is a clone of the \texttt{coords:Coords.point} component of \texttt{meas:Velocity} but applied to the \texttt{mango:EpochPosition} context. It matches the description given by the \texttt{coords} data model: The measured Velocity along of the radial axis (see \texttt{meas:Velocity.coord} in \cite{2022ivoa.spec.1004R}). \subsubsection{EpochPosition.pmLongitude} \textbf{vodml-id: EpochPosition.pmLongitude} \newline \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline \textbf{multiplicity: 1} \newline - Velocity along the longitude axis in angular distance per unit time (see \texttt{meas:ProperMotion.coord}). + This parameter is a clone of the \texttt{coords:LonLatPoint.lon} component of \texttt{meas:ProperMotion} but applied to the \texttt{mango:EpochPosition} context. It matches the description given by \texttt{coords} data model: Velocity along the longitude axis in angular distance per unit time (see \texttt{meas:ProperMotion.coord}). \subsubsection{EpochPosition.pmLatitude} \textbf{vodml-id: EpochPosition.pmLatitude} \newline \textbf{type: \hyperref[sect:ivoa]{ivoa:RealQuantity}} \newline \textbf{multiplicity: 1} \newline - Velocity along the latitude axis in angular distance per unit time (see \texttt{meas:ProperMotion.coord}). + This parameter is a clone of the \texttt{coords:LonLatPoint.lat} component of \texttt{meas:ProperMotion} but applied to the \texttt{mango:EpochPosition} context. It matches the description given by \texttt{coords} data model: Velocity along the latitude axis in angular distance per unit time (see \texttt{meas:ProperMotion.coord}). \subsubsection{EpochPosition.obsDate} \textbf{vodml-id: EpochPosition.obsDate} \newline \textbf{type: \hyperref[sect:DateTime]{mango:DateTime}} \newline \textbf{multiplicity: 0..1} \newline - Observation date expressed within the common time system if present. This attribute, if set, supersedes the epoch possibly given with the spatial coordinate system. + Observation date expressed within the common time system if present. This attribute, if set, supersedes the epoch possibly given with the spatial coordinate system(see the above). \subsubsection{EpochPosition.pmCosLat\_applied} \textbf{vodml-id: EpochPosition.pmCosLat\_applied} \newline @@ -312,7 +312,7 @@ \section{Photometric Properties} \subsection{Brightness} \label{sect:Brightness} - Observed brightness of the \texttt{MangoObject}. The distinction between fluxes and magnitudes is made by the unit. This property should refer to a photometric calibration as defined by the \texttt{Phot} data model (1.1). + Observed brightness of the \texttt{MangoObject}. The purpose of this property is to gather a brightness value with its error and the its photometric calibration The distinction between fluxes and magnitudes is made by the unit. The photometric calibration is modeled by the \texttt{Phot} data model (1.1). \subsubsection{Brightness.value} \textbf{vodml-id: Brightness.value} \newline @@ -334,7 +334,7 @@ \section{Photometric Properties} \subsection{Color} \label{sect:Color} - Property that describes a color of the \texttt{MangoObject}. The color is not an intrinsic property of the MANGO object, but a value relative to two filters or energy bands. + Property that describes a color of the \texttt{MangoObject}. The purpose of this property is to gather a color value with its error and the 2 related filters (high and low) The color can be given as a magnitude difference or an hardness ratio. \subsubsection{Color.value} \textbf{vodml-id: Color.value} \newline diff --git a/doc/usecases.tex b/doc/usecases.tex index 66fe79b..7ff9964 100644 --- a/doc/usecases.tex +++ b/doc/usecases.tex @@ -172,7 +172,7 @@ \subsubsection{Vizier catalog archive} MANGO is not meant to replace the current management of the ViZier metadata, but rather to make those understandable/interoperable for a wide panel of VO-compliant clients. -\subsubsection{Client Requirements} +\subsubsection{Client Use-cases} Right now, the meta-data provided within the VOTable allow client software such Aladin or Topcat to run most of the functionalities expected by the user, either for data analysis or plotting. This information is often inferred from UCDs, UTypes or column names. It can also be given by the user. diff --git a/mivot/mango/mango.Brightness.xml b/mivot/mango/mango.Brightness.xml index 60fb92e..04fd6b6 100644 --- a/mivot/mango/mango.Brightness.xml +++ b/mivot/mango/mango.Brightness.xml @@ -1,7 +1,8 @@ +The photometric calibration is modeled by the \texttt{Phot} data model (1.1)." --> diff --git a/mivot/mango/mango.Color.xml b/mivot/mango/mango.Color.xml index 7fa11b1..ca78d8a 100644 --- a/mivot/mango/mango.Color.xml +++ b/mivot/mango/mango.Color.xml @@ -1,7 +1,7 @@ diff --git a/mivot/mango/mango.EpochPosition.xml b/mivot/mango/mango.EpochPosition.xml index a7ccb6a..9487e1f 100644 --- a/mivot/mango/mango.EpochPosition.xml +++ b/mivot/mango/mango.EpochPosition.xml @@ -21,10 +21,22 @@ All components use the same coordinate systems for both time and space coordinat \begin{itemize} \item Both position and proper motion reuse \texttt{coords:LonLatPoint} elements. \item The space coordinate system is imported from \texttt{coords:spaceSys}. - \item The time coordinate system is imported from \texttt{coords:timeSys}. + \item The time coordinate system is imported from \texttt{coords:simeSys}. \end{itemize} +It is recommended to use the \texttt{ObsDate} field to store the epoch of the observation instead +of the \texttt{epoch} field of \texttt{coords:spaceSys}. +There are 2 reasons for this: +\begin{itemize} + \item Using the epoch of \texttt{coords:spaceSys} requires to work with the + \texttt{coords:CustomRefLocation} class to carry the reference location. + This class does not support the standard reference locations such as e.g. BARYCENTER. + \item the observation date can be read in a column and therefore change with each data row. + I this case, it cannot be stored as an element of the space coordinate system + but as an \texttt{EPochPosition} attribute. +\end{itemize} + All components have their own units which must be consistent with each other. This consistency is not enforced by the model. diff --git a/vo-dml/desc.mango.vo-dml.xml b/vo-dml/desc.mango.vo-dml.xml index 5497b4d..44270e7 100644 --- a/vo-dml/desc.mango.vo-dml.xml +++ b/vo-dml/desc.mango.vo-dml.xml @@ -539,8 +539,8 @@ in \url{http://www.ivoa.net/rdf/processing-level} Color Color Property that describes a color of the \texttt{MangoObject}. -The color is not an intrinsic property of the MANGO object, -but a value relative to two filters or energy bands. +The purpose of this property is to gather a color value with its error and the 2 related filters (high and low) +The color can be given as a magnitude difference or an hardness ratio. mango:Property @@ -719,10 +719,22 @@ All components use the same coordinate systems for both time and space coordinat \begin{itemize} \item Both position and proper motion reuse \texttt{coords:LonLatPoint} elements. \item The space coordinate system is imported from \texttt{coords:spaceSys}. - \item The time coordinate system is imported from \texttt{coords:timeSys}. + \item The time coordinate system is imported from \texttt{coords:simeSys}. \end{itemize} +It is recommended to use the \texttt{ObsDate} field to store the epoch of the observation instead +of the \texttt{epoch} field of \texttt{coords:spaceSys}. +There are 2 reasons for this: +\begin{itemize} + \item Using the epoch of \texttt{coords:spaceSys} requires to work with the + \texttt{coords:CustomRefLocation} class to carry the reference location. + This class does not support the standard reference locations such as e.g. BARYCENTER. + \item the observation date can be read in a column and therefore change with each data row. + I this case, it cannot be stored as an element of the space coordinate system + but as an \texttt{EPochPosition} attribute. +\end{itemize} + All components have their own units which must be consistent with each other. This consistency is not enforced by the model. @@ -744,7 +756,10 @@ In some cases the errors might conflict with the correlations: EpochPosition.longitude longitude - The longitude of the Point, as a Quantity with angular units (see \texttt{coords:LonLatPoint.lon}. + This parameter is a clone of the \texttt{coords:LonLatPoint.lat} component of \texttt{meas:Position} +but applied to the \texttt{mango:EpochPosition} context. +It matches the description given by \texttt{coords} data model: +The longitude of the Point, as a Quantity with angular units (see \texttt{coords:LonLatPoint.lon}. ivoa:RealQuantity @@ -756,7 +771,11 @@ In some cases the errors might conflict with the correlations: EpochPosition.latitude latitude - The latitude of the Point, as a Quantity with angular units (see \texttt{coords:LonLatPoint.lat}. + This parameter is a clone of the \texttt{coords:LonLatPoint.lat} component of \texttt{meas:Position} +but applied to the \texttt{mango:EpochPosition} context. +It matches the description given by \texttt{coords} data model: +The latitude of the Point, as a Quantity with angular units (see \texttt{coords:LonLatPoint.lon}). + ivoa:RealQuantity @@ -781,7 +800,10 @@ In some cases the errors might conflict with the correlations: EpochPosition.radialVelocity radialVelocity - The measured Velocity along of the radius axis (see \texttt{meas:Velocity.coord} in \cite{2022ivoa.spec.1004R}). + This parameter is a clone of the \texttt{coords:Coords.point} component of \texttt{meas:Velocity} +but applied to the \texttt{mango:EpochPosition} context. +It matches the description given by the \texttt{coords} data model: +The measured Velocity along of the radial axis (see \texttt{meas:Velocity.coord} in \cite{2022ivoa.spec.1004R}). ivoa:RealQuantity @@ -794,7 +816,10 @@ In some cases the errors might conflict with the correlations: EpochPosition.pmLongitude pmLongitude - Velocity along the longitude axis in angular distance per unit time (see \texttt{meas:ProperMotion.coord}). + This parameter is a clone of the \texttt{coords:LonLatPoint.lon} component of \texttt{meas:ProperMotion} +but applied to the \texttt{mango:EpochPosition} context. +It matches the description given by \texttt{coords} data model: +Velocity along the longitude axis in angular distance per unit time (see \texttt{meas:ProperMotion.coord}). ivoa:RealQuantity @@ -807,7 +832,10 @@ In some cases the errors might conflict with the correlations: EpochPosition.pmLatitude pmLatitude - Velocity along the latitude axis in angular distance per unit time (see \texttt{meas:ProperMotion.coord}). + This parameter is a clone of the \texttt{coords:LonLatPoint.lat} component of \texttt{meas:ProperMotion} +but applied to the \texttt{mango:EpochPosition} context. +It matches the description given by \texttt{coords} data model: +Velocity along the latitude axis in angular distance per unit time (see \texttt{meas:ProperMotion.coord}). ivoa:RealQuantity @@ -821,7 +849,7 @@ In some cases the errors might conflict with the correlations: EpochPosition.obsDate obsDate Observation date expressed within the common time system if present. -This attribute, if set, supersedes the epoch possibly given with the spatial coordinate system. +This attribute, if set, supersedes the epoch possibly given with the spatial coordinate system(see the above). mango:DateTime @@ -1091,8 +1119,9 @@ providers to convey whether or not the factor has been applied (see \texttt{meas Brightness Brightness Observed brightness of the \texttt{MangoObject}. +The purpose of this property is to gather a brightness value with its error and the its photometric calibration The distinction between fluxes and magnitudes is made by the unit. -This property should refer to a photometric calibration as defined by the \texttt{Phot} data model (1.1). +The photometric calibration is modeled by the \texttt{Phot} data model (1.1). mango:Property diff --git a/vo-dml/desc/desc.DateTime.datetime.txt b/vo-dml/desc/desc.DateTime.dateTime.txt similarity index 100% rename from vo-dml/desc/desc.DateTime.datetime.txt rename to vo-dml/desc/desc.DateTime.dateTime.txt diff --git a/vo-dml/desc/desc.EpochPosition.obsDate.txt b/vo-dml/desc/desc.EpochPosition.obsDate.txt index 732b457..39d4c40 100644 --- a/vo-dml/desc/desc.EpochPosition.obsDate.txt +++ b/vo-dml/desc/desc.EpochPosition.obsDate.txt @@ -1,2 +1,2 @@ Observation date expressed within the common time system if present. -This attribute, if set, supersedes the epoch possibly given with the spatial coordinate system. \ No newline at end of file +This attribute, if set, supersedes the epoch possibly given with the spatial coordinate system(see the above). \ No newline at end of file diff --git a/vo-dml/desc/desc.EpochPosition.radialVelocity.txt b/vo-dml/desc/desc.EpochPosition.radialVelocity.txt index a1377bb..cc180e1 100644 --- a/vo-dml/desc/desc.EpochPosition.radialVelocity.txt +++ b/vo-dml/desc/desc.EpochPosition.radialVelocity.txt @@ -1,4 +1,4 @@ This parameter is a clone of the \texttt{coords:Coords.point} component of \texttt{meas:Velocity} but applied to the \texttt{mango:EpochPosition} context. -It matches the description given by \texttt{coords} data model: +It matches the description given by the \texttt{coords} data model: The measured Velocity along of the radial axis (see \texttt{meas:Velocity.coord} in \cite{2022ivoa.spec.1004R}). diff --git a/vo-dml/desc/desc.EpochPosition.txt b/vo-dml/desc/desc.EpochPosition.txt index e0f645a..e50fb27 100644 --- a/vo-dml/desc/desc.EpochPosition.txt +++ b/vo-dml/desc/desc.EpochPosition.txt @@ -20,10 +20,22 @@ All components use the same coordinate systems for both time and space coordinat \begin{itemize} \item Both position and proper motion reuse \texttt{coords:LonLatPoint} elements. \item The space coordinate system is imported from \texttt{coords:spaceSys}. - \item The time coordinate system is imported from \texttt{coords:timeSys}. + \item The time coordinate system is imported from \texttt{coords:simeSys}. \end{itemize} +It is recommended to use the \texttt{ObsDate} field to store the epoch of the observation instead +of the \texttt{epoch} field of \texttt{coords:spaceSys}. +There are 2 reasons for this: +\begin{itemize} + \item Using the epoch of \texttt{coords:spaceSys} requires to work with the + \texttt{coords:CustomRefLocation} class to carry the reference location. + This class does not support the standard reference locations such as e.g. BARYCENTER. + \item the observation date can be read in a column and therefore change with each data row. + I this case, it cannot be stored as an element of the space coordinate system + but as an \texttt{EPochPosition} attribute. +\end{itemize} + All components have their own units which must be consistent with each other. This consistency is not enforced by the model.