Outline

  • Needs and drivers
  • OGC state of the art
  • EO v.s Astronomy/VO
  • (Web-accessible) Archives
  • (pre)Processing tools
  • Web processing services:
    • on-demand processing
    • (near) real-time processing
  • Mapping and integration/GIS
    • Desktop
    • WebGIS (e.g. Jmars)
  • (Partial) Compilation of resources

Mapping needs and drivers

  • Needs of the planetary community for On-line mapping services
  • Same as most any Earth-based mapping community
  • Need for common projections
  • Accurate data (to support robotic and human missions)
  • Support for huge data sets (e.g. 1TB, 16bit Kaguya Lunar mosaic)
  • Data portals
  • Formats
  • Usability / Interoperability
  • True 3D surfaces (asteroids, in-situ)
  • Metadata

State of the Art Summary (OGC)

WMS/WCS/WCPS implementations, e.g. (see yesterday's live stream...)

  • PlanetServer, Rasdaman hyperspectral WCS/WCPS/WMS server - Jacobs University
  • Lunarserv - Custom WMS/WCS and processing server -  Arizona State University
  • MarsTrek, MoonTrek, VestaTrek – WMTS Server (and 3D interface) by JPL
  • JMars (mission planning, data viewer) -  Arizona State University
  • Mars, Moon, Venus - Esri (S3) WMTS support – currently under beta
  • Supports optimized WMS and tile server code in GDAL - (by Lucian Plesea)
  • Best-of image bases (as WMS), WFS Nomenclature, ArcGIS Server – USGS
  • German Aerospace Center (Freie University/DLR)
  • Japan Aerospace eXploration Agency (JAXA)

Earth Observation

Quite ahead (like astronomy VO...)

Processing levels

Definitions

  • Telemetry: An encoded byte stream used to transfer data from one or more instruments to temporary storage where the raw instrument data will be extracted
  • Raw: Original data from an instrument
  • Partially Processed: Data that have been processed beyond the raw stage but which have not yet reached calibrated status.
  • Calibrated: Data converted to physical units, which makes values independent of the instrument.
  • Derived: Results that have been distilled from one or more calibrated data products (for example, maps, gravity or magnetic fields, or ring particle size distributions).
  • Supplementary: such as calibration tables or tables of viewing geometry
Source: NASA PDS

Processing levels

Examples

Mobile vs desktop users

Source: NASA/MRO/CTX/MSSS

Archives

Tools

general aspects

  • Tools for planetary data access, processing and analysis are very diverse
  • Higher processing level needed for mapping
  • GIS/RS tools used on Earth are effectively usable almost unchanged on Solar System bodies
  • Underlying planetary cartography (CRS) critical (see Trent's talk of yesterday)
  • Tools are evolving FAST. These slides in 1 year (1 month?) might well be outdated.

Archives

PDS Geosciences Node

Archives

PDS Geosciences Node

Archives

PDS: Standards, nodes, etc.

Archives

PDS Geosciences Node

Archives

Experiment teams (not necessarily long term)

  • CRISM (MRO)
    • CRISM MAP - http://crism-map.jhuapl.edu/
  • HIRISE (MRO)
    • http://hirise.lpl.arizona.edu
  • HRSC (MRO)
    • http://hrscview.fu-berlin.de
  • THEMIS Mars image explorer / ASU Data Viewer
    • http://themis-data.asu.edu
  • LROC ASU
    • http://lroc.sese.asu.edu

Workflow

Tyical for observations/mapping

  • Decide where to work (scientific literature) [recent development ]View on easily accessible mosaicked data (e.g. Google Earth Mars version or the growing set of virtual globes….
  • Data search
  • Data download
  • Data processing / post-processing
  • Analysis / Mapping

Workflow

Old school (1990s / 2000s)

  • Get a set of data at comparable resolution and perform the observation on a purely photogeological basis (more or less until the ‘90s)
  • Use no or low-quality topography (pre-mid ‘90s), i.e. no ortho-products (distortions)
  • No detailed compositional information (pre-mid 2000s)
  • People in lander teams (e..g Viking) drive observation campaigns (‘70s-‘80s).
  • Archived data are available to all

Workflow

Recent (e.g. Mars)

  • Collect all available data from a variety of missions and experiments
  • Analyse all data in combination (GIS-like)
  • Use high-accuracy, high-resolution topography
  • Use hyperspectral data ➔ compositional information
  • Recent attempts to integrate orbital and lander/rover data

Alternative paths

  • 1) Format conversion

    • 2006 - added PDS3 / ISIS2 read support to GDAL
    • 2007 – ISIS3 read support added
    • 2014 – VICAR read support added
    • 2017 – ”Geo”FITS to be added (github also fits2vrt script)
    • 2017 – ISIS3 writer, plans for PDS4 reader/writers
  • 2) Direct application support

    • Wrap planetary data in supported headers
    • To support: Esri, ERDAS, PCI Geomatic, ENVI (raw headers) or use graphical formats with Worldfiles
    • GDAL support greatly helped

Tools

Isis3

VICAR

Video Image Communication And Retrieval

NASA ASP

Ames Stereo Pipeline

Resources

Planetary gazeteer (USGS)

  • Download GIS-ready Shapefiles (point file for each body, approx. bounds)
  • USGS, NASA, and IAU work collaboratively to uniquely identify planetary nomenclature for features on terrestrial bodies.

Resources

PILOT (USGS)

  • download GIS shapefiles for each supported instrument
  • Geospatially search a subset of the PDS Imaging Node EDR archives
  • Served Data sets include
    • Cassini, MGS, MRO
    • Odyssey, Viking,
    • Messenger,
    • Clementine, ...
  • PILOT can connect to POW

Resources

POW (USGS) - Processing on demand

Resources

MarsSI (Univ. Lyon) - Processing on demand

Resources

Map-a-Planet v2 (USGS) - Processing on demand

Resources

VESPA

Resources

JMARS: GIS client

Resources

Data workshops

Resources

Tutorials

Resources

Github et al.

Resources

Python and surroundings

Resources

Python packages/modules

Resources

Python packages/modules

Resources

Python packages/modules

  • SpiceyPy : SpiceyPy: The NASA JPL NAIF SPICE toolkit wrapper written in Python.
  • Spectral Python 0.16.0 : Spectral Python (SPy) is a pure Python module for processing hyperspectral image data.m
  • SETI GitHub PDS tools : Python tools to parse PDS3 labels, interface to the spice library, and do sundry other tasks.
  • PySAT : Python Spectral Analysis Tool (PySAT) is both a Python (2.7+) library, accessible via an API, and a Graphic User Interface
  • scikit-spectra : Python pandas-based toolkit for explorative spectroscopy, in particular UVVis spectroscopic data.

Resources

  • PDS Tools (including NASAview)
    • http://pds.nasa.gov/tools/release/software_download.cfm
  • ISIS3
    • http://isis.astrogeology.usgs.gov/
  • HiRISE IAS Viewer
    • http://hiweb.lpl.arizona.edu/iasclient/

Resources

Getting started tips

(old)

  • Consider investing some time
  • Consult all relevant documentation and try to repeat simple examples here or on the software documentation page.
  • Check the forums (e.g. isis3 support) and post questions (after having carefully searched for possible answers already available!!!).
  • Check for new data/software releases (and sign up for notifications, e.g. isis3).
  • Keep in touch (ask/provide help) with your friends/colleagues, e.g. with mailing lists, etc. Some critical mass of users in your professional neighborhood helps a lot!

Getting started tips

(new)

  • Still, it takes some time to be invested ;)




Thank you

Have a nice workshop

Hashtag (and OP Slack channel): #vespamap17

Full Image (with Optional Header)

www.flickr.com/photos/25797459@N06/5438799763/