From 6e7a480eaa6ec5c09c9c1e08f8f9fc12937544a7 Mon Sep 17 00:00:00 2001
From: Ross Beyer <rbeyer@rossbeyer.net>
Date: Mon, 13 Feb 2023 10:19:53 -0800
Subject: [PATCH] Updates from Brent and Ross following discussion at meeting.
---
content/moon/standards/cartographic_standards.md | 6 +++---
content/moon/standards/data_formats.md | 8 ++++----
content/moon/standards/data_standards.md | 11 ++++++-----
3 files changed, 13 insertions(+), 12 deletions(-)
diff --git a/content/moon/standards/cartographic_standards.md b/content/moon/standards/cartographic_standards.md
index 0d585c9..63d8c8e 100644
--- a/content/moon/standards/cartographic_standards.md
+++ b/content/moon/standards/cartographic_standards.md
@@ -6,10 +6,10 @@ weight: 51
### Map Projections
- Data are provided in a simple cylindrical (equirectangular) map projection.
-- Data are orthorectified to a sphere using the IAU radius => 1737.4km (sphere)
+- Data are orthorectified to a sphere using the IAU radius => 1737.4km ([Archinal, et al. 2018](https://doi.org/10.1007/s10569-017-9805-5))
- Data are made available in 0 – 360 positive East coordinate system with a center longitude of 180 degrees using planetocentric latitude.
-- For observational data, pixel scale or resolution should be maintained at native scale, (i.e., do not up sample or down sample data.)
-- For derived data (e.g., DTMs), data should be made available at a reasonable resolution that avoids extrapolation of information.
+- For observational data, pixel scale or resolution should be maintained at native scale or better, (i.e., do not average data.)
+- For derived data (e.g., DTMs), data should be made available at a reasonable resolution that avoids interpolation of information.
- Data for polar areas (latitudes > 65˚ North or South) should use a polar stereographic projection centered at the pole.
### Vector Symbology
diff --git a/content/moon/standards/data_formats.md b/content/moon/standards/data_formats.md
index fb76faf..cdc173d 100644
--- a/content/moon/standards/data_formats.md
+++ b/content/moon/standards/data_formats.md
@@ -5,12 +5,12 @@ weight: 60
**DRAFT**
### Formats for Offline Data Access
-- Data in raster format will be provided as [cloud optimized GeoTiffs](https://www.cogeo.org)(COG), complying with the above projection standards.
+- Data in raster format will be provided as [cloud optimized GeoTiffs](https://www.cogeo.org)(COG), complying with the [cartographic standards]({{< ref "cartographic_standards" >}}).
- Data in vector format will be provided in [OGC GeoPackage format](https://www.geopackage.org) with information stored in decimal degrees (i.e., no map projection applied)
### Formats for Online Data Access
- Data in raster format can be provided as [cloud optimized GeoTiffs](https://www.cogeo.org), complying with the above projection standards. These data will be accessed via their [STAC](https://www.google.com/search?client=safari&rls=en&q=spatio-temporal+asset+catalog&ie=UTF-8&oe=UTF-8) data files.
-- Data in raster format can be provided using OGC compliant WMS service. Said service must encode a proper IAU 2015 projection code.
-- Data in vector format can be served using an OCG compliant WFS or WMTS service using the standards defined above. The server must encode a proper IAU 2015 projection code.
-- The STAC-API specification (a remotely accessible search service) will be used to support metadata query and data discoverability.
+- Data in raster format can be provided using an OGC compliant [WMS](https://www.ogc.org/standards/wms) service. This service must encode a proper [IAU 2015/2018 projection code](https://ui.adsabs.harvard.edu/abs/2021LPICo2549.7012H).
+- Data in vector format can be served using an OCG compliant [WFS](https://www.ogc.org/standards/wfs) or [WMTS](https://www.ogc.org/standards/wmts) service using the standards defined above. The server must encode a proper IAU 2015/2018 projection code.
+- The [STAC](https://stacspec.org)-API specification (a remotely accessible search service) will be used to support metadata query and data discoverability.
diff --git a/content/moon/standards/data_standards.md b/content/moon/standards/data_standards.md
index 625819b..1635f85 100644
--- a/content/moon/standards/data_standards.md
+++ b/content/moon/standards/data_standards.md
@@ -6,22 +6,23 @@ weight: 31.1
**DRAFT**
### Body Parameters
-The Report of the IAU Working Group on Cartographic Coordinates and Rotational Elements: 2015 (2018) and the [Final Report of the Lunar Critical Data Products Specific Action Team](https://www.lpi.usra.edu/mapsit/standup-committees/LCDP-SAT-REPORT-20211110.pdf) (LCDP-SAT) body parameters will be used. This includes a sphere radius of 1737.4km, the 2008 JPL DE 421 ephemeris rotated to the mean Earth/polar axis (ME) system and rotation parameters as defined in Table 2 (Archinal, et al., 2018).
+The [Report of the IAU Working Group on Cartographic Coordinates and Rotational Elements: 2015 (Archinal, et al. 2018)](https://doi.org/10.1007/s10569-017-9805-5) and the [Final Report of the Lunar Critical Data Products Specific Action Team](https://www.lpi.usra.edu/mapsit/standup-committees/LCDP-SAT-REPORT-20211110.pdf) (LCDP-SAT) body parameters will be used. This includes a sphere radius of 1737.4km, the 2008 JPL DE 421 ephemeris (but soon expected to change to the DE 440 ephemeris) rotated to the mean Earth/polar axis (ME) system and rotation parameters as defined in Table 2 (Archinal, et al., 2018).
### Horizontal and Vertical Datum
-Reference sphere defined as 1737.4km as defined by the IAU (IAU;2018). Proxy products usable to tie to the vertical reference frame (and have topography or shape) include:
-- Gridded Lunar Orbiter Laser Altimeter (LOLA)
+Reference sphere defined as 1737.4km as defined by the IAU ([Archinal, et al. 2018](https://doi.org/10.1007/s10569-017-9805-5)). Proxy products usable to tie to the vertical reference frame (and have topography or shape) include:
+- [Gridded Lunar Orbiter Laser Altimeter (LOLA)](https://doi.org/10.17189/1520642)
- SLDEM 2015
- Lunar Polar Gridded Data Record
-The horizontal datum to be used is the 2008 JPL DE 421, which, as per the LCDP-SAT, is only slightly different than the 2021 JPL DE 440 ephemerides. The proxy products that data creators can use to tie new data products to the horizontal reference frames include:
+The standard horizontal datum to be used is the 2008 JPL DE 421, which is expected to shift to the 2021 JPL DE 440 ephemeris (and new projects should begin using the DE 440). The proxy products that data creators can use to tie new data products to the horizontal reference frames include:
- Gridded Lunar Orbiter Laser Altimeter (LOLA)
- SLDEM 2015
- Lunar Polar Gridded Data Record
+
At this time, no global visible observations are usable to rigorously align to the horizontal reference frame.
### Map Projections
- See [cartographic standards]({{< ref "cartographic_standards" >}}).
### Ephemeris Information
-- All sun, spacecraft, sensor, and target body ephemeris information is to be provided either by [Navigation and Ancillary Information Facility (NAIF)](https://naif.jpl.nasa.gov/naif/) as SPICE kernels or in NAIF SPICE compliant format by another provider (e.g., a mission team). This includes sensor and target positions, velocities, and orientations as well as sensor parameters such as distortion models.
\ No newline at end of file
+- All sun, spacecraft, sensor, and target body ephemeris information is to be provided either by [Navigation and Ancillary Information Facility (NAIF)](https://naif.jpl.nasa.gov/naif/) as SPICE kernels or in NAIF SPICE compliant format by another provider (e.g., a mission team). This includes sensor and target positions, velocities, and orientations as well as sensor parameters such as distortion models.
--
GitLab