|
34 | 34 | \usepackage{listings} |
35 | 35 | \usepackage{ltablex} |
36 | 36 | \usepackage{seqsplit} |
| 37 | +\usepackage{graphicx} |
37 | 38 |
|
38 | 39 |
|
39 | 40 | \begin{document} |
@@ -2010,14 +2011,16 @@ \subsubsection{Doppler/Redshift datasets} |
2010 | 2011 | specification. This can be indicated by specifying an appropriate value for the optional em\_ucd attribute, defining |
2011 | 2012 | the type of velocity on the axis. The following UCD values are defined to represent velocities: |
2012 | 2013 |
|
| 2014 | +\newpage % Force a new page |
2013 | 2015 | \begin{tabularx}{\textwidth}{|p{0.3\textwidth}|p{0.5\textwidth}|} |
2014 | 2016 | \hline |
2015 | | -Ucd & Definition\\\hline |
| 2017 | +UCD & Definition\\\hline |
2016 | 2018 | spect.dopplerVeloc.opt & Radial velocity derived from a wavelength shift using the optical convention\\\hline |
2017 | 2019 | spect.dopplerVeloc.radio & Radial velocity derived from a frequency shift using the radio convention\\\hline |
2018 | 2020 | spect.dopplerVeloc.rel & Radial velocity, derived using the relativistic convention\\\hline |
2019 | 2021 | spect.doppler.z & Redshift derived from a spectral feature\\\hline |
2020 | | -\end{tabularx} |
| 2022 | +\end{tabularx}% |
| 2023 | + |
2021 | 2024 |
|
2022 | 2025 | If em\_ucd contains one of these strings, then the discovered datasets can be any velocity or redshift data product. |
2023 | 2026 | However the spectral coverage of the dataset should still be specified in em\_min, em\_max as the vacuum wavelength in |
@@ -2199,10 +2202,11 @@ \subsection{Implementing a package of multiple data products} |
2199 | 2202 |
|
2200 | 2203 | For example, for High Energy datasets we could have as the table response of an ObsTAP query: |
2201 | 2204 |
|
2202 | | -\begin{tabularx}{\textwidth}{|p{0.07\textwidth}|p{0.09\textwidth}|p{0.23\textwidth}|p{0.12\textwidth}|p{0.19\textwidth}|p{0.3\textwidth}|} |
| 2205 | +\newpage % Force a new page |
| 2206 | +\begin{tabularx}{\textwidth}{|p{0.07\textwidth}|p{0.09\textwidth}|p{0.23\textwidth}|p{0.12\textwidth}|p{0.18\textwidth}|p{0.28\textwidth}|} |
2203 | 2207 | \hline |
2204 | 2208 | obs\_id & data product type & data product subtype & Calibration Level & Access Format & Title\\\hline |
2205 | | - 123 & event & chandra.hrc.pkg & 1 & application/x-tar-gzip & Chandra ACS-XYZ observation package (event,refimage)\\\hline |
| 2209 | +123 & event & chandra.hrc.pkg & 1 & application/x-tar-gzip & Chandra ACS-XYZ observation package (event,refimage)\\\hline |
2206 | 2210 | 123 & image & chandra.hrc.refimage & 2 & image/fits & ACS-XYZ reference image\\\hline |
2207 | 2211 | 123 & image & chandra.hrc.preview & 2 & image/jpeg & Chandra ACS-XYZ preview image\\\hline |
2208 | 2212 | 345 & event & rosat.foo.pkg & 1 & application/x-tar-gzip & ROSAT observation package\\\hline |
@@ -2256,6 +2260,7 @@ \subsection{Implementing a package of multiple data products} |
2256 | 2260 | %TITOTOTO |
2257 | 2261 | \begin{sidewaystable} |
2258 | 2262 | %\begin{longtable}[hbt] |
| 2263 | +\small |
2259 | 2264 | \begin{tabular}{|l|l|l|l|l|l|}% 6 left justified |
2260 | 2265 | \hline |
2261 | 2266 | Column Name & Datatype & Size & Units & ObsCoreDM Utype & UCD \\\hline |
@@ -2380,6 +2385,7 @@ \subsection{Implementing a package of multiple data products} |
2380 | 2385 |
|
2381 | 2386 | \begin{sidewaystable} |
2382 | 2387 | %\begin{longtable}[hbt] |
| 2388 | +\small |
2383 | 2389 | \begin{tabular}{|l|l|l|l|l|l|}% 9 left justified |
2384 | 2390 | \hline |
2385 | 2391 | Column Name & Datatype & Size & Units & ObsCoreDM Utype & UCD \\\hline |
@@ -2486,8 +2492,9 @@ \subsection{Implementing a package of multiple data products} |
2486 | 2492 | \end{sidewaystable} |
2487 | 2493 |
|
2488 | 2494 | % |
2489 | | - \newpage |
| 2495 | +\newpage |
2490 | 2496 | \begin{sidewaystable} |
| 2497 | +\small |
2491 | 2498 | \begin{tabular}{ | l | l | l | l | l | l | l | l}% 9 left justified |
2492 | 2499 | \hline |
2493 | 2500 | Column Name & Datatype & Size & Units & ObsCoreDM Utype & UCD \\\hline |
|
0 commit comments