New additional web client

“Neo” PlanetServer client

neo.planetserver.eu hosts an additional client. It is reachable through the URL:

http://neo.planetserver.eu/

The web client derives from the classical client of PlanetServer on http://planetserver.eu, incorporating existing features and additional ones in a more streamlined GUI.

neo-gui

Among additional features (which will be covered also in future posts), to start with there is a new search widget for easily accessing available data. The search functionality (either using pre-determined locations or latitude/longitude range) is available from a button located on the top left portion of the main web interface:

search-button

The Search function triggers a widget for selecting the Region of Interest:

search-window-neo

Both clients can be used simultaneously

http://planetserver.eu

http://neo.planetserver.eu

and they both query the same server, hosting the PlanetServer database.

 

Export GeoTiff from PlanetServer

 GeoTiff Export from web client

PlanetServer can also export the screen in GeoTiff format, in order to exchange data and images with Desktop GIS systems and alike.

One should point the client towards a certain CRISM observation/data product, either interactively from http://planetserver.eu selecting a certain region or directly.

e.g.

http://planetserver.jacobs-university.de/?productid=HRL0000B63A_07_IF181S_TRR3

geotiff-1

The “Save for GIS” option should be ticked in the lower right corner of the console

geotiff-2

image[2]

the selection of the filename can be done interactively on the console:

WCPS>filename = "geotiff-olindex2.tif"
geotiff-olindex2.tif
WCPS> image(sp.olindex2)

geotiff-3

and a GeoTiff file called “geotiff-olindex.tif” is created (see Console in-depth)

The resulting GeoTiff, from gdalinfo, returns, e.g.


Driver: GTiff/GeoTIFF
Files: geotiff-olindex2.tif
Size is 420, 580
Coordinate System is `'
Origin = (2435019.832500000018626,-1195241.430099999997765)
Pixel Size = (36.000000000000000,-36.000000000000000)
Image Structure Metadata:
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( 2435019.833,-1195241.430)
Lower Left ( 2435019.833,-1216121.430)
Upper Right ( 2450139.833,-1195241.430)
Lower Right ( 2450139.833,-1216121.430)
Center ( 2442579.833,-1205681.430)
Band 1 Block=420x19 Type=Byte, ColorInterp=Gray
NoData Value=0

The Coordinate Reference System for GeoTiff files generated by PlanetServer is an Equirectangular:

Expressed as proj4:
+proj=eqc +lat_ts=0 +lat_0=0 +lon_0=0 +x_0=0 +y_0=0 +a=3396190 +b=3396190 +units=m +no_defs

Expressed as ESRI .prj:
PROJCS["Mars Equicylindrical clon=0",GEOGCS["GCS_Mars_2000_Sphere",DATUM["D_Mars_2000_Sphere",SPHEROID["Mars_2000_Sphere_IAU_IAG",3396190.0,0.0]],PRIMEM["Reference_Meridian",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Equidistant_Cylindrical"],PARAMETER["False_Easting",0.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",0.0],PARAMETER["Standard_Parallel_1",0.0],UNIT["Meter",1.0]]

Expressed as Petascope CRS:

http://kahlua.eecs.jacobs-university.de:8080/def/crs/PS/0/2/

This applies to bands, or indices, band depths or any results obtained from WCPS calculations through the console.

New Regions on PlanetServer: Nili & Mawrth

New Regions of Interest added

Two new regions of interest have been added to PlanetServer: Nili Fossae and Mawrth Vallis, both characterized by a large compositional diversity and geological complexity.

A direct access URL for each region is available, similarly to already available ROIs. The updated global coverage of PlanetServer CRISM data is available in ESRI shapefile and KML.

Nili Fossae

Direct URL: http://planetserver.jacobs-university.de/?region=nili

nili

Mawrth Vallis

Direct URL: http://planetserver.jacobs-university.de/?region=mawrth

mawrth

Console in-depth

Console basics

PlanetServer (PS) console allows for quick and easy access to certain functions, either restricted to the console itself (e.g. return or a certain value, parameter), or affecting the various views or widget, such as Map, Diagram. It is available when a certain CRISM observation (data product/granule) is loaded, either interactively from the main WebGUI or directly with a URL.

For example, CRISM IR could be reached through (see spectral range in “Diagram” widget):

http://planetserver.jacobs-university.de/?productid=frt00012613_07_if164l_TRR3

while CRISM VNIR of the same granule (see spectral range in “Diagram” widget):

http://planetserver.jacobs-university.de/?productid=frt00012613_07_if164s_TRR3

Please note that features and capabilities are evolving. Updates will be posted in this blog and eventual corrections applied to existing documentation/blog posts, including this one. Current information refers to the stable client on http://planetserver.eu (September 2013).

More general information is contained in the PlanetServer 101 post.

Binning

Averaging pixels for extracting spectra is possible on PlanetServer, using a certain kernel size, e.g. the default in collecting a spectra is a 3×3 pixel kernel over the point of collection/query. The maximum bin is 7×7. The bin size can be changed using the bin() function in the console:

WCPC> bin(5)
Using bin 5x5

WCPC> bin(100)
Using maximum bin of 7×7

Stretch

The stretch applied to the original floating point values of each band of the hyperspectral CRISM cube can be modified, when rendering in 8-bit (0:255) original data for display on the WebGUI. The default is zero.

WCPS> minstretch
0

setting it to a different value affects all following image display (either single band or e.g. indexes) e.g.

WCPS> minstretch = 0.01

Single band, RGB composites

To load a single bands on the main window through a console command one could directly call for a single band number (as listed in the Table of Contents), e.g. for

http://planetserver.jacobs-university.de/?productid=frt00012613_07_if164l_TRR3

WCPS>  image("band197")

The same could be expressed in nanometers, e.g.:

WCPS> image(nm2band(2300))

which shows in both cases such a result:

band197

 

RGB images with a band colour composite can be obtained with, e.g.:

WCPS> rgbimage("band402","band247","band99")

which provides, as a result:

rgb

Band ratios

Ratios between different bands can be produced and visualised with, e.g.:

WCPS> image("band200 / band24")

corresponding to:

ratio

Indexes / summary products

Mineral indexes are implemented in PS and its console, their formula is returned as console output, e.g., after loading a certain CRISM observation and its IR channel:

WCPS> sp.olindex
(data.106 / (0.1*data.12 + 0.1*data.32 + 0.4*data.50 + 0.4*data.71 ) ) - 1

where “sp” stands for “summary product”.

Indexes can also be visualized interactively in the map window, e.g. on this data product (CRISM VNIR):

http://planetserver.jacobs-university.de/?productid=frt00012613_07_if164l_TRR3

WCPS> image(sp.olindex)

returns on the console:

WCPS> image(sp.olindex)
for data in ( frt00012613_07_if164l_trr3_1_01 ) return encode( (char) (255 / (max((data.106 / (0.1*data.12 + 0.1*data.32 + 0.4*data.50 + 0.4*data.71 ) ) - 1) - 0)) * (((data.106 / (0.1*data.12 + 0.1*data.32 + 0.4*data.50 + 0.4*data.71 ) ) - 1) - 0), "png" )

and on the main window:

olindex-image

This list summarizes the summary products one could extract and visualize with PS (see Pelkey et al., 2007, DOI:10.1029/2006JE002831 for description and explanations).

Summary products can be listed from the console (also reproduced in the lists below) with:

WCPS> show(sp)

Hyperspectral Summary Products IR:

olindex2

bd1900r

bd1980

bd2200

doub2200

bd2230

bd2500

Spectral Summary Products VNIR:

r770rbr

bd530

sh600

bd640

bd860

bd920

rpeak1

bdi1000

visr440

irr1

Spectral Summary Products IR

bdi1000ir

ira

olindex

lcpindex

hcpindex

var

islope1

bd1435

bd1500

icer1

bd1750

bd1900

bdi2000

bd2100

bd2210

bd2290

d2300

sindex

icer2

bdcarb

bd3000

bd3100

bd3200

bd3400

cindex

bd1270o2

bd1400h2o

bd2000co2

bd2350

bd2600

irr2

r2700

bd2700

irr3

CAVEAT: on the stable client/WebGUI the IR and VNIR channels are separate and not all indexes are available (e.g. sp.olindex is not available on VNIR, but only on the IR spectral range), e.g. in VNIR the console returns:

WCPS> sp.olindex
(data.0 / (0.1*data.0 + 0.1*data.0 + 0.4*data.0 + 0.4*data.0 ) ) - 1

Metadata and other parameters

Similarly, available metadata can be listed with:

WCPS> show(hsdataset)
crs
prj
productid
point
mapoptions
collection
nodata
metadata
xmin
xmax
ymin
ymax
width
height
bands
bbox
lonlat
 

Minimum, maximum of a certain band can be returned by the console, either expressed as band number or, as in this example, in nanometers:

WCPS> max(nm2band(2300))
0.249158
WCPS> min(nm2band(2300))
0.169802
Alternatively, once could query by band number,  such as:
WCPS> max("band24")
0.249158
WCPS> min("band48")
0.169802

Band depths

A function for calculating band depth is also available, providing low, center, high in nanometers, e.g, for

http://planetserver.jacobs-university.de/?productid=frt00012613_07_if164s_TRR3

WCPS> banddepth(440, 530, 709)
(1 - (data.25 / ((0.6588279348436623 * data.12) + (0.3411720651563377 * data.53))))

one could visualise the image of the desired band depth:

WCPS> bdimage(440, 530, 709)

image-banddepth

Console interaction with Menu button functions

The console can returns the point coordinate (p) and spectrum (s) of the points clicked using the Spectrum button .
Once a spectrum point is collected, e.g. on
spectrum-collected
The console returns the ascii spectrum (µm, value) with
WCPS> s(1)
The position of the collected spectrum is returned with
WCPS> p(1)
lon=-48.123179292514,lat=-8.6719934825689
This can also be expressed in latitude and longitude, separately:
WCPS> p(1).lon
-48.123179292514
or
WCPS> p(1).lat
-8.671993482568

Spectral ratios

Similarly, after collecting 2 spectra (first=red, second=green) from the WebGUI (previous section), one could visualise their ratio:

2spectra

e.g. the 2 collected spectra, in order:

WCPS> spectrum(s1)

s1

WCPS> spectrum(s2)

s2

WCPS> spectrum(s(1)/s(2))

spectrum-ratio

Histogram

As an alternative to selecting a certain band from the Table of Contents and visualising its histogram from from the “Diagrams” widget, one could interactively visualise the histogram of a certain band, e.g. expressed in nanometers, from the console. The second argument is the number of bins:

 

WCPS> histogram(nm2band(550), 10)

results in:
histogram-console

Resources from fellow services

PlanetServer has few other fellow services, namely:

Cryospheric Data Service

Climate Data Service

Geology Data Service

Ocean Data Service

All of those services have specific applications and tools, all based on EarthServer technology. Some general documentation can be useful for anyone approaching PlanetServer/EarthServer, such as the PML WCPS guide or the general How-tos of the Ocean Data Service.

 

 

 

Direct URL access to data granules, regions & KML/Shapefile

Data Product direct URL

PlanetServer CRISM data can be accessed and analyzed directly from the address bar of any supported browser (Chrome, ~Safari):

e.g.

http://planetserver.jacobs-university.de/?productid=HRL0000B63A_07_IF181S_TRR3

providing access to a CRISM TRR3 data product (for naming conventions, e.g. see page 28 of 2009 CRISM users’ workshop introductory slide)

In order to make  data access and availability easier, one could also access each ingested crism data product so far, by using either a shapefile or a KML. Both are linked and available on the main PlanetServer GitHub page.

The original vector files used for creating PlanetServer-specific shp/kml derive  from the PDS Mars Orbital Data Explorer.

KML of PlanetServer CRISM products

SHP of PlanetServer CRISM products

ROI direct URL

Available regions of interest (ROI) on PlanetServer can also be accessed directly knowing the name of the feature, e.g. as

planetserver.jacobs-university.de/?region=<NAME>

http://planetserver.jacobs-university.de/?region=gale

with gale indicating Gale Crater direct URL

or. e.g.

gangesGanges Chasma direct URL

capriCapri Chasma direct URL

juventaeJuventae Chasma direct URL

 

 

 

New Regions of Interest on PlanetServer

New ROI / regional data access on PlanetServer

New Regions of Interest (ROI) and related data coverage/access are available on PlanetServer. They can be selected on the entry page, using the top bar (its left portion) drop-down menu:

toolbar-left

 

 

ROIs/areas added so far (August 2013) include:

Gale Crater

roi-gale

Capri Chasma

roi-capri

Ganges Chasma

roi-ganges

Juventae Chasma

roi-juventae

PlanetServer 101

PlanetServer 101: basics

Planetserver’s stable web client (WebGUI) basic functionalities are listed and briefly explained below

Main Interface

The main interface is a pan & zoom full screen map with an upper toolbar

Toolbar (left portion)  toolbar-left

Toolbar (right portion), containing several buttons (see below) toolbar-right

Buttons

The first buttons that might provide info and help are:

@ - provides access to further sources of information (including this blog)

? – opens the tutorial PDF

Once a user pans over an area and selects a certain footprint (orange = unselected, blue = selected), a dialog for choosing the spectral range appears.

crism-choice

After that the main analysis set of widgets is visualized:

screen-crism

Analytical and query dialogs are then available

Dialogs/widgets

Each dialog/widget will have its own (or combined) in-depth blog post describing functionalities.

Table of Contents

It gives access to the selected data granule and each of its bands, including grayscale, RGB combinations

toc

Diagrams

Provide spectral graphing capabilities, histogram, spectral library visualisation, etc.

diagrams

Console

It allows spectral calculations, band queries, and other functions.

console

More info

For more info, please consult the PlanetServer PDF tutorial.

Also, a screencast (and eventual more to come will be added) is available from the EarthServer Vimeo page.

 

Welcome

This is the welcome post for PlanetServer (Planetary Service of EarthServer).

Posts on this blog will be either general announcements (e.g. service downtime, new data ingestion, new functionalities, or alike) or specific topics, such as tutorial bits, scientific use cases, guest posting from partners and colleagues.

What you can do with PlanetServer is essentially data exploration and analysis online, focusing currently on CRISM hyperspectral data (coverage and regional focus to increase). It is actually not an archive, such as existing PDS or PSA, but a tool/environment to collaboratively work on higher-level data online, through web standards.

All relevant info is contained in the About page. Contacts, including social media ones, are listed in the Contacts page.

For more details on the overall architecture and current (updated at ~Spring 2013) capabilities, please look at the 2013 ASR paper (also pdf linked on the About page).

Start exploring PlanetServer.