From d85b72c0fdbca6c90d38fe5b793d2fa6d40c3286 Mon Sep 17 00:00:00 2001 From: "Laura, Jason R" <jlaura@usgs.gov> Date: Thu, 17 Nov 2022 14:32:31 -0700 Subject: [PATCH] Adds draft lunar standards for discussion at our next meeting --- .../moon/standards/cartographic_standards.md | 9 ++++++ content/moon/standards/data_formats.md | 16 ++++++++++ content/moon/standards/data_standards.md | 30 ++++++++++++++++++- content/moon/standards/metadata_standards.md | 18 +++++++++++ content/moon/standards/spatial_standards.md | 6 ---- 5 files changed, 72 insertions(+), 7 deletions(-) create mode 100644 content/moon/standards/cartographic_standards.md create mode 100644 content/moon/standards/data_formats.md create mode 100644 content/moon/standards/metadata_standards.md delete mode 100644 content/moon/standards/spatial_standards.md diff --git a/content/moon/standards/cartographic_standards.md b/content/moon/standards/cartographic_standards.md new file mode 100644 index 0000000..7a52853 --- /dev/null +++ b/content/moon/standards/cartographic_standards.md @@ -0,0 +1,9 @@ +--- +title: Cartographic Standards +weight: 51 +--- +**DRAFT** + +Many geologic maps exist which can be used as a basis for setting cartographic standards. What other symbologies should be standardized with the Lunar SDI? + + diff --git a/content/moon/standards/data_formats.md b/content/moon/standards/data_formats.md new file mode 100644 index 0000000..fb76faf --- /dev/null +++ b/content/moon/standards/data_formats.md @@ -0,0 +1,16 @@ +--- +title: Data Format Standards +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 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. diff --git a/content/moon/standards/data_standards.md b/content/moon/standards/data_standards.md index 1176371..b92c227 100644 --- a/content/moon/standards/data_standards.md +++ b/content/moon/standards/data_standards.md @@ -3,4 +3,32 @@ title: Data Interoperability Standards weight: 31.1 --- -**DRAFT** \ No newline at end of file +**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 (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). + +### 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) +- 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: +- 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 +- 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 made available in a -180 – 180 (CLON 0; web maps hate this) OR 0 – 360 (lots of data in this system; historical argument) Positive East coordinate system with a center longitude of 180 degrees and use 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. +- Data for large spatial scale (e.g., 1:24000), small spatial extent maps, (e.g. landing sites) can be provided in a local stereographic (candidate to also have a grab bag to also include gnomonic and orthographic) centered on image. +- Data at mid-latitudes (35˚ - 65˚ N/S) data providers are encouraged to also provide data in a Lambert Conformal Conic Projection with a longitude origin of 0 and standard parallels of 33˚ and 45˚ N/S (as appropriate). (discuss; this is a classic North America LCC) +- Data for polar areas (latitudes > ??˚ North or South) should use a polar stereographic projection centered at the pole. + +### 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 diff --git a/content/moon/standards/metadata_standards.md b/content/moon/standards/metadata_standards.md new file mode 100644 index 0000000..3160607 --- /dev/null +++ b/content/moon/standards/metadata_standards.md @@ -0,0 +1,18 @@ +--- +title: Metadata Standards +weight: 70 +--- + +**DRAFT** + +### Metadata Content +- Data will have qualitative process and usability information available in text format that describes (1) a description of the data set, (2) the process used to create the data, (3) the available assets or files within a data set, (4) the accuracy, errors, and identification of known issues with the data set, (5) the qualitative usability of the data set (as mediated by the data provider or steward), (6) textual description of the proposed update cadence for this data set, and (7) optionally textual links to other data sets of potential interest to users of this data set. + +### Accuracy Descriptions +- Accuracy should be described using the [ISO 19157:2013 standard](https://wiki.icaci.org/index.php?title=ISO_19157:2013_Geographic_information_-_Data_quality). + +### File Formats +- Data will have an FGDC compliant XML metadata file. This file is to be as compliant as possible and should use the planetary domain extension. +- Data will have a Spatio-Temporal Asset Catalog (STAC) metadata JSON file. +- Data should have a provenance file that minimally describes the creation of the data. When possible, the provenance file will support complete reproduction of a derived data product by replicating commands provided to processing tools. + diff --git a/content/moon/standards/spatial_standards.md b/content/moon/standards/spatial_standards.md deleted file mode 100644 index 0083afa..0000000 --- a/content/moon/standards/spatial_standards.md +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Spatial Standards -weight: 31.0 ---- - -**DRAFT** \ No newline at end of file -- GitLab