Saturday, March 30, 2019

LPSC 50th – Tech Lunch notes, March 20th, 2019

What and Where: In 2019, at the 50th Lunar and Planetary Science Conference (LPSC), several participants gathered to discuss planetary technology-based topics. This meeting was held over lunch at the restaurant in the conference center and lasted about 1.5 hours. This is the 3rd or 4th such technology lunches held at LPSC. The unofficial tag-line for this meeting was “this is a no science zone”.
Why: LPSC is generally heavily science focused for talks and discussions, thus there are not many opportunities to discuss planetary technologies as a group. We note that abstracts and poster sessions are an excellent method to present technology topics, but again a larger group interaction is missing.
Who: The initial email invite went out from Trent Hare (Astrogeology) to essentially a random list of community members known to support various technology initiatives. Several others were able to attend from word of mouth. In total about 25 participants were able to attend. Facilities represented included NASA facilities (e.g. AMES), JPL (e.g. NAIF, PDS nodes, MIPL), USGS (Astrogeology), RPIF, APL, PSI, and many from U.S. and international universities (mission teams and students).
How: Due to the size of the group, the main topics discussed were guided. One of the main intents was to allow participants to see what others in the room are working on to hopefully spur on future collaborations. If you find a topic you are interested in, please reach out to share ideas, methods, software, and hopefully increase partnerships.

Topics:
Quick introduction for new Astrogeology community contacts:
·        Robin Fergason (rfergason@usgs.gov) has taken over as lead technology manager for Astrogeology. Please contact her for any comments or issues related to any services Astrogeology supports.
·        Jay Laura (jlaura@usgs.gov) took over as software lead at Astrogeology (including ISIS3). Jay introduced several community software initiatives at Astrogeology as we move to a more open source initiative for ISIS3 and other supported software tasks. https://github.com/USGS-Astrogeology. GitHub issues are being used for all projects. We want to hear about issues, feature requests, documentation improvements, etc.
o   To facilitate this, Astrogeology software will also have oversite from a Technical Steering Committee (TSC) for several of their projects. For more see: https://github.com/USGS-Astrogeology/TSC.
o   New discussion forums are available. https://astrodiscuss.usgs.gov. Sign-in using a github acnt.
o    Please follow the Astrodiscuss to see updates and community Requests for Comments (RFCs). These will also available at the ISIS3 Wiki: https://github.com/USGS-Astrogeology/ISIS3/wiki.
o   Note ISIS3 is also moving to a new versioning system. Thus, be prepared that version 4 is coming. This updated versioning better follows industry standards for software.
Image Matching and Change Detection
·        The first question posed to the group was, “how many are interested in image matching techniques”. About 60% or more of participants raised their hands. This obviously has wide uses across several applications including automating image-to-image registration methods, image to “ground” registration (tying one image type to another image type or tying to a controlled base), terrain generation using stereo-pairs, facilitating change detection, etc.  
·        There are lots of papers and research in this topic. Simple searches provide many of the initial results below thus consider this a sampling of available resources (please send me more to add or include below in comments):
o   Multi-instrument coregistration: https://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=8077748
Machine Learning (and Feature Extraction)
·        While not as popular as image matching, ML topics were also popular among participants. This is probably one of the fastest growing research areas for planetary (and Earth-based) domains. Like above, a simple search provides many papers and abstracts (please send me more to include or add in the comments below):
o    Machine learning session at 2018 AGU: https://agu.confex.com/agu/fm18/prelim.cgi/Session/50013
o    Lots of automatic crater detection papers!
NAIF and SPICE
·        Chuck Acton stated the transition to a multi-thread SPICE library is proceeding well.
·        Syncing SPICE kernels remains to be a large community issue. For example, if SPICE kernels are updated, how are they to be released? Sent back to NAIF? And how and who reviews them? As more groups are creating controlled mosaics, this issue will continue to grow.
·        Cosmographia continues to be supported by NAIF. One idea stated by the group included making SPICE kernels more easily integrated into Cosmographia. For morehttps://naif.jpl.nasa.gov/naif/cosmographia.html
·        SpiceyPy, supported by Andrew Annex, has recently been updated to v2.2.0. https://github.com/AndrewAnnex/SpiceyPy.
·        There is an upcoming (free) SPICE training (June 4-6, 2019). I believe all materials will be made available to all. To attend, please register: https://naif.jpl.nasa.gov/naif/WS2019_announcement.html
·        While Astrogeology attempted to use Cosmographia for ISIS3’s control environment, it has been deprecated.
Planetary Web Mapping Services (WMS)
·    Lunaserv is still being updated. It is the first WMS server to support Planetary codes. http://lunaserv.lroc.asu.edu/about.html
·    There is a new branch of Mapserver by Jean-Christophe Malapert which also uses planetary codes. It is not yet pushed back into Mapserver baseline. For more information, contact Jean-Christophe on github. 
Planetary Data System (PDS)
·      There was a strong attendance of PDS personnel at LPSC.
·     Thanks to Nick Estes’ idea, we have an initial method to archive GIS data in the PDS. We are using a variant of GeoCSV with a PDS4 label: https://giswiki.hsr.ch/GeoCSV. An early implementation is now in GDAL for testing: https://www.gdal.org/frmt_pds4.html
·      Upcoming technical session for PDS personnel in April will cover many topics listed here and including PDS4, tools for PDS4, facilitating search, using Github, long-term roadmap, etc. Supporting the community and better advertising updates and direction for the PDS is also a main goal.

Upcoming Technical Workshops for the Planetary Domain
·   The 4th Planetary Data Workshop (not free), June 18-20, Flagstaff, AZ: https://www.hou.usra.edu/meetings/planetdata2019/. It will have presentations, posters, tutorial demos, and discussions.
·   The 2nd Planetary Mapping and Virtual Observatory Workshop, July 1-3, Domaine de St. Paul, Saint-Rémy-lès-Chevreuse, France. This a great “partner” workshop for the Planetary Data Workshop and covers many related technical topics. It will have presentations, discussion workshop, and tutorials. https://epn-vespa.github.io/mapping2019/
Recent Published Books (many technical chapters available)
·  Planetary Remote Sensing and Mapping: https://www.taylorfrancis.com/books/9780429000515
·  Planetary Cartography and GIS: https://www.springer.com/us/book/9783319628486

Saturday, March 2, 2019

JPL Geospatial Technology Round Tables, Feb 11-13, 2019


Table of Contents

Introduction

Between February 11-13 a series of discussion style round tables were held at the NASA Jet Propulsion Laboratory (JPL) in Pasadena, CA. The meetings were hosted by the Instrument Software and Science Data Systems Section 398, and largely represented by members of the Multimission Image Processing Lab (MIPL) and Planetary Data Systems (PDS) Imaging Node, although others were able to join the discussions in person or via webex. The Astrogeology Science Center (ASC) of the U.S. Geological Survey (USGS; Flagstaff, AZ) was represented by Trent Hare and ASC software developers during the camera model discussions. These discussions were initiated by Dr. Thomas Logan and Paul Ramirez and who also provided travel support for Mr. Hare.


These notes are a summary/overview of the discussions as prepared by Mr. Hare, with minor changes provided by JPL participants (R. Deen and T. Logan).


Planetary and Earth Data Format Interoperability, Mon Feb 11

We began the discussion by listing many of the formats commonly used in the planetary (and Earth) community. The formats included: VICAR, ISIS3, PDS4, FITS (GeoFITS), GeoTiff, Jpeg2000, NITF, etc.

·       Jpeg2000 was discussed to help understand its limitations and its seemingly decline in popularity (although it still is used within the NITF format). Issues listed included: 1) while current open source implementations are available, they are not very robust, 2) the popular encoder/decoder Kakadu, while it used to be open access, continues to be locked down, and (3), while 32bit floating point is defined in the specification, it is not widely supported. Jpeg2000 is currently allowed in PDS3 archives (HiRISE and LOLA archives), but is now banned from PDS4 archives. This is due to PDS4 archives only allowing raw binary streams, thus no compression of any style is allowed.
·       Both Video Image Communication And Retrieval (VICAR) and the Integrated Software for Imagers and Spectrometers (ISIS3) formats are critical for the processing environments and missions they support. Changing formats would be difficult for either to support. Because VICAR uses an in-line label followed a binary stream, it is recognized that a simple reader could be written. Also, VICAR meets the PDS4 criteria to allow a VICAR image to be archived (as-is) along-side a PDS4 label which describes how to skip the in-line label.  Because ISIS3, by default, supports tiled data streams, reading and supporting PDS4 archives is a little tougher (note that ISIS3 also support raw binary streams). Also, VICAR does have limited compression support throught it’s Automated Fusion of Image Data System (AFIDS) branch of VICAR. The main branch of VICAR at JPL is used for in-situ missions like InSight, Mars2020, and other planetary mission activities.
·       The AFIDS team has implemented a robust reader/writer in the Geospatial Data Abstraction Library (GDAL) for the VICAR format (which is available in the current Open VICAR distribution).  However, it has not been pushed back into GDAL’s baseline code release. This is a stated goal for the group. There is already a limited VICAR driver in GDAL (by Sebastian Walter, Freie University Berlin), which needs to be taken into consideration prior to merging the AFIDS version.
·       GDAL does have read support for PDS3 and the older ASC ISIS2 format. ASC has funded support for a basic ISIS3 reader and writer. Lastly, GDAL does have basic support for PDS4 but requires a well-defined template label to make it ready for archival.
·       The FITS format now has a proposed and implemented extension, called GeoFITS, allowing for more standardized geospatial map projection definitions. GDAL contains the first implementation as written by Chiara Marmo (University of Paris-Sud). It is still new and not yet widely used. Reference: Marmo, C., Hare, T. M., Erard, S., Minin, M., Pineau, F.‐X., Zinzi, A., et al. (2018). FITS format for planetary surfaces: Definitions, applications, and best practices. Earth and Space Science, 5, 640–651, https://doi.org/10.1029/2018ea000388.
·       The JPL-created and now Esri-supported format, called the Meta Raster Format (MRF) by Lucian Plesea, was discussed for its ability to optimize streaming services like Web Mapping Services (WMS). It is analogous to a file-based database since it supports an index into packed image tiles. It supports tiles as compressed by JPEG, PNG, the new Limited Error Raster Compression (LERC) to name a few. LERC, originally written by Thomas Maurer, is an open specification by Esri and an open source implementation is available within GDAL. Because it can be lossless or lossy (with user defined precision), it has the potential to take on compressions like LZW and even Jpeg2000.
·       The group seemed to agree that the GeoTiff format is the current best choice for interoperability between applications. As a free and open source library, GDAL also maintains the reference implementation. GeoTiff is well supported within AFIDS (a VICAR branch) and the NASA AMES Stereo Pipeline (ASP), but for other planetary applications (like ISIS3), the GeoTiff format must be converted into their native format. Using a raw (uncompressed and untiled) GeoTIff allows one to use the format in a PDS4 archive. Actually, in GDAL, when converting to a PDS4 image, GDAL optionally allows one to store the output image within a properly labeled GeoTiff (with a PDS4 label pointing into the GeoTiff). Lastly, it was noted that several projects like the Lunar Mapping and Modeling Project (LMMP) and related Trek projects, the Phobos Working Group, and the ASC-supported PDS Annex portal all prefer GeoTiff as their primary format (optionally with a PDS label).
·       In the process of discussing image file formats, a number of useful file attributes were identified. These include: 1) Support for multiple bit structures such as 8-64 bit integer, floating point, real and imaginary; 2) Open source (100% non-propriety); 3) Support for Compression; 4) Support for tiling; 5) Support for Georeference; 6) Straight-forward binary layout; 7) Straight-forward label design (possibly integrated and/or detached); and 8) Support for multiple bands.

Collaboration Topics

·       The group agreed that we are not all going to move everyone over to one format. There is no “killer” format or “one format to rule them all”. Thus, it was agreed that supporting GDAL seemed to be the best method to help support interoperability across applications. One collaboration idea would be a test suite providing results in GDAL for these conversions. For example, converting VICAR to GeoTIff back to VICAR and document what is lost. This could be applied across many of the popular formats like ISIS3 to VICAR and back to ISIS3. If too much information is lost, potentially teams could update the drivers in GDAL to help. Also supporting a side-car metadata file during conversion might also help. This metadata side-car file is already supported in GDAL, but the drivers would need to take advantage of it.
·       The AFIDS group agreed to find resources to push their current in-house GDAL-based VICAR reader/writer back into the public release of GDAL. This would require assessing the impact to the current VICAR driver already in GDAL.

Open Source Software Issues, Tue Feb 12

  • Discussions in this topic were not about the benefits of open source as all persons and projects represented have goals for making their code open source. Mostly this discussion focused on perceptions on open source projects and ideas around supporting open source projects.
  • In 2015, Bob Deen (JPL) helped make a majority of VICAR open source. However, there are parts of VICAR that still have not been released. These include: 1) code which contain ITAR constraints; 2) code that uses licensed software (notably Numerical Recipes); 3) parts of the in-situ code-base; and 4) the AFIDS branch of VICAR. Besides the ITAR constraints, there are goals to open source both the in-situ and AFIDS versions.
  • For ASC, all products, including software, are mandated to be public domain. Only recently though has ASC pushed their code-base to Github and will strive to “behave” like an open source project (see below for more).
  • The image processing package Opensource Multi-INstrument Analysis Software (OMINAS), created by Joseph Spitale, is now mainly maintained by PSI and JPL, has also stated plans to open source their code. OMINAS is built on the commercial application IDL, currently owned by Harris Geospatial Solutions. The OMINAS maintainers currently support a free run-time for IDL and their code which users can take advantage of without an IDL license.
  • It was discussed that releasing one’s code can be difficult for all members of a team when it is perceived as a specialized capability that potentially maintains future funding opportunities. Within the group, most stated that the benefits and importance of releasing their code outweighed this potential risk.

Collaboration Topics

  • The group ended with discussions on what it is to be an open source project and ideas on how to fund it. It was pointed that the key behind successful open source projects is your user community. While releasing the source code is a great first step, if there is no support to foster and work with your user community, the project probably won’t make it for the long-term. Thus, calling out resources within your funding opportunities to foster your community and fund other open source projects you rely on is viewed as an extremely important aspect for any open source project.  This includes the ability to take community input, whether they are bug reports, new ideas, or even the ability to accept user supplied code into your project (granted it must meet your coding standards).
  • Since we all support the same or closely tied communities within both the planetary and Earth-based domains for image processing, we should continue to discuss how to better support our user community across our different applications. For example, allowing them to interoperate (e.g. formats, camera models, shared capabilities), would be a great step forward.
  • A good resource for this topic includes this free publication: National Academies of Sciences, Engineering, and Medicine. 2018. Open Source Software Policy Options for NASA Earth and Space Sciences. Washington, DC: The National Academies Press. https://doi.org/10.17226/25217.


Talk: Activities at the USGS Astrogeology Science Center, Mon Feb 11

  • presentation: available from dropbox.



“Big Data” Streaming Technologies and GeoSpatial Data Portals, Tue Feb 12

This round table covered several ongoing projects at JPL which are tackling these big-data topics. Like JPL, ASC has also been supporting streaming methods since the late 90s. Several projects were discussed including:

  • Science Data Analytics Platform (SDAP). “SDAP is a technology software solution currently geared to better enable scientists involved in advancing the study of the Earth's physical oceanography”. As an Apache incubator project, it has been an open source project from the start.  While centered around oceanography data, many of the core capabilities could be used in other projects. Instead of the generation of derived products on-disk, they are working towards real-time calculations. These products can be recalculated based on an encoded URL. The goal is to try to limit the need to large mosaics to be downloaded. If results must be provided, try to summarize results as small tables. Again, the encoded URL can be used to recreate the derived maps.
  • The Global Imagery Browse Services (GIBS) are a set of standard services to deliver global, full-resolution satellite imagery in a highly responsive manner. This project is riding on technologies created at JPL and use OGC web standards including Web Map Tile Service (WMTS) and the similar Tiled Web Map Service (TWMS). Most all of their code is made available from within GDAL or from their Github site.
  • There was some discussion on the JPL Trek system. Like GIBS, Trek builds on many of the same standardized services and Open Geospatial Consortium (OGC) technologies. The interface they support, and have extended for planetary, is Cesium. CesiumJS is an open-source JavaScript library for 3D globes and maps as founded by Analytical Graphics, Inc.
  • ASC has been recently working with Esri and Caltech to test Web serving a couple of extremely large mosaics including the Caltech Mars CTX mosaic (~1TB in size, lossy, at 5m/p) a USGS- and Esri-create uncontrolled Mars HiRISE mosaic (19TB in size, lossy, at 0.25 m/p). These should be released by March 2019.

Collaboration Topics

  • The grouped talked about goals of providing cloud services (applications) next to these cloud-provided data sets. They also discussed how such systems can be maintained for the long-term. For example, how are researchers able to recreate their results if the service is no longer provided. This is an area for rapid growth and support as data sets continue to get larger.




End-to-End Processing of Planetary Data, Camera Models to GIS Products, Wed Feb 13

While this round table provided time for both camera model discussions and GIS products, largely we discussed the Camera Sensor Model (CSM) standardized API. ASC provided an introduction to the CSM standard. In short, the CSM API was conceived and implemented by the U.S. Air Force to standardize the use of camera models across different photogrammetric applications. The CSM standard provides a standardized API only, not the actual implementation of the camera model. It is now maintained by the CSM Working Group, which has several government, university, and industry members. The CSM is currently used by several photogrammetric applications including commercial applications like BAE’s Socet GXP, Harris Geospatial Solution’s ENVI, and Hexagon’s ERDAS Imagine. ASC is currently working on CSM support in ISIS3 and is helping to support the CSM within NASA’s Ames Stereo Pipeline (ASP).
·       ASC is currently working both a CSM open source framing and a pushbroom (line scanner) implementation. The pushbroom was originally developed by BAE and updated by ASC. With support from BAE, it is now released on Github using a permissive BSD license. ASC in collaboration with the CSM Working Group, the 3.0.3 API supports variable radii for planetary applications. Previously it was locked to WGS84 (Earth).  ASC has also created a Simplified Wrapper and Interface Generator (SWIG) for the CSM library which provides Python access to the API. It can also provide access to JAVA, Ruby, and many other languages. Note that ASC supported camera models in ISIS3 (more than 50 instruments) are currently developed using a unique in-house design, but they are working on supporting CSM implementations also.
·       The AFIDS Team provided background for their software called “Mars Nest”. The software is a georeferencing pipeline that automatically co-registers most two map-projected images to each other. For unmapped (EDR) images, they have developed procedures to use a Replacement Sensor Model (RSM) as an approximation for a rigorous camera model. Current implementations use the NITF format to store the RSM metadata (called Tagged Record Extensions or TREs), which could potentially be stored inside a PDS4 file. Similar to a CSM, an RSM implementation is another method to provide interoperability across photogrammetric applications. 
·       The CAHVOR camera model is used by several at JPL for in-situ and orbital cases.
·       The NASA Ames Stereo Pipeline (ASP) currently uses both ISIS3 available camera models and their own camera models mainly for Earth-based instruments. The ASP team is currently implementing capabilities to incorporate CSM.
·       Lastly, for GIS data products, we did have a short discussion from Caltech providing details for their recently released CTX near-global mosaic for Mars. Not only did they optimize the input data to remove hazy images, they also optimized their workflow to maintain the ability to map every pixel in the mosaic back to the input image. They have also been provided funding, via a PDART, to make an even better version (~2 years). Input from the community is welcome. The current version will soon be available as a streaming cloud service hosted by Esri.

Collaboration Topics


  • After the introduction to CSM, there were many questions about whether the standardized CSM API would be capable enough for current applications. While the relatively simple API does lock the user into the standard (for the sake of interoperability), the implementation is left up to the user. Thus, it should be able to support most applications (but more research or pilot studies should be done). It was also brought up that the CSM API doesn’t make the implementation of a camera model any easier. But by providing several open source implementations, there is hope it might help with adoption.
  • Specifically, for in-situ applications, there was discussion if the CSM would be beneficial. Within the planetary community, there has been a long-time goal for the better integration of orbital and in-situ mission data. By allowing both orbital and in-situ photogrammetric applications to share the same camera model should actually help to realize this goal. Of course, a collaboration across projects to pilot this would be needed.

Tuesday, January 8, 2019

Uncontrolled Global HiRISE Mosaic

Mars High-Resolution Tiled Web Services


linked from: http://bit.ly/HiRISE_mosaic

This Mars service highlights controlled "foundational" mosaics including Viking MDIM v2.1 [231 m/p], MOLA/HRSC Blended Hillshade [200 m/p], and the USGS-created THEMIS Daytime and Nighttime mosaics [100 m/p]. We have also included the preliminary uncontrolled but high-resolution mosaics created by the Caltech Murray Lab for CTX [5 m/p] and USGS-generated HiRISE PSP/ESP mosaic [0.25 m/p]. Note on disk the CTX is lossy compressed to 1TB (originally at ~5TB) and the HiRISE PSP/ESP is lossy compressed to 19TB (originally nearly 100TB). Datasets have been compiled together and gratefully hosted as a Tiled Web Services by Esri (using AWS cloud). Data descriptions and their creators are provided on the simple viewer page (and referenced below).

As stated in our abstract, this is really a technology evaluation to push our current limits for available processing clusters and data storage capabilities. We also used novel raster formats (MRF) and compression techniques (10-bit Jpeg/ZEN), and optimized distributed cloud capabilities. All capabilities to create and serve the data are using open source software (e.g. GDAL) and open OGC standards.

See below for references and additional download data resources.

Access the layers:

please be nice: using this test server to scrape large swaths of data is not allowed. But use (view) the resources in your GIS or web GIS viewers all you want. Also there is no need to build statistics - this will bog down the application and the server. 
  • A simple web viewer to take the layers for a test ride (click "Open in Map Viewer")
  • list of many of the individual services.
  • For ArcMap and ArcGIS Pro, simply head to ArcGIS Online (also just called Portal). See animations below.


  • For other applications you can use the addresses found here (zip). Drag the *.til or *.dem into your Desktop GIS. Note these files are simply text files defining the tiled WMS address (crack open in a text editor to take a peak). Some of these are 16-bit (*.dem) and 10-bit services, thus desktop GIS applications should have no problem loading, but web viewers may not support some of these layers directly. Again - no need to build stats ever!
References

Plesea, L. and Hare, T.M. (2019). Uncontrolled Global HiRISE Mosaic, In Lunar and Planetary Science Conference (Vol. 50, pp. 1–2), The Woodlands, TX,  abstract #1986, PDF poster.

McEwen, A. S., Eliason, E. M., Bergstrom, J. W., Bridges, N. T., Hansen, C. J., Delamere, W. A., Grant, J. A., Gulick, V. C., Herkenhoff, K. E., Keszthelyi, L., Kirk, R. L., Mellon, M. T., Squyres, S. W., Thomas, N., & Weitz, C. M. (2007). Mars Reconnaissance Orbiter's High Resolution Imaging Science Experiment (HiRISE).  JGR-Planets112 (E05S02). Download map projected HiRISE Images.

Kirk, R. L. M., Holmberg, I. M., Keszthelyi, L. P., Redding, B. L., Delamere, W. A., Gallagher, D., Chapel, J. D., Eliason, E. M., King, R., & McEwen, A. S., Ultrahigh resolution topographic mapping of Mars with MRO HiRISE stereo images: Meter‐scale slopes of candidate Phoenix landing sites. (2008). JGR-Planets 113 (E00A24). Download HiRISE DTMs,

Dickson, J. L., Kerber, L. A., Fassett, C. I., & Ehlmann, B. L. (2018). A Global, Blended CTX Mosaic of Mars with Vectorized Seam Mapping: A New Mosaicking Pipeline Using Principles of Non‐Destructive Image Editing. Lunar and Planetary Science Conference (Vol. 49, pp. 1–2), The Woodlands, TX, abstract #2480. Download the data.

Fergason, R. L., Lee, E. M., Weller L. (2013). THEMIS Geodetically Controlled Mosaics of Mars, Lunar and Planetary Science Conference (Vol. 44, pp. 1–2), The Woodlands, TX . abstract #1642. Download the data.

Archinal, B. A., Kirk, R. L., Duxbury, T. C., Lee, E. M., Sucharski, R., Cook, D. (2003), Mars Digital Image Model 2.1 control network, Lunar and Planetary Science Conference (Vol. 34, pp. 1–2), abstract #1485. Download the data.

For more information see the simple viewer page.


Sunday, July 23, 2017

ISIS3 on Windows 10 Bash

Based on a tweet by MarsLakes, I also decided to give ISIS3 on Windows 10 a try. Note this is for Windows 10 Anniversary update or higher. Anyway, here is my current cheat sheet. It works better that I thought it would but still has GUI issues. However, using this environment as a processing machine - seems to work like a charm. Warning: this requires a lot of downloading.

(1) get Bash on Windows 10
Update: (Oct. 2018): Just get Ubuntu installed via the Windows 10 app store


And if you don't have access to the App store, try to download: Without MS store access, https://docs.microsoft.com/en-us/windows/wsl/install-manual


Old short cuts:
-- In Windows head to Settings > Update & Security > For Developers > Developer Mode
-- Next, find "Turn Windows Features On or Off" -- and check on "Windows Subsystem for Linux"
-- reboot and start Bash from the  Windows' start bar.
for picture instructions see:
or

(2) update Bash (just in case)
> sudo apt-get update 
-- this just gets your Ubuntu system up to date. It is worth running this at the end too.

(3) For Windows, install Xming and launch

(4) From Windows, start bash and let's get the GUI working.
> sudo apt install x11-apps
> sudo apt-get install lxde

(5) To solve a missing library, download this package and install: https://packages.ubuntu.com/trusty/amd64/libicu52/download
or  run these lines:
> sudo dpkg -i libicu52_52.1-3ubuntu0.6_amd64.deb

(optional...?). I didn't have an issue with this missing lib, but here is a potential helpful comment from another user who was missing this library -- which he solved by running:
> sudo apt-get install libnss3-1d

(6) Get ISIS3
> cd ~
> mkdir isis3
> cd isis3
> rsync -azv --delete --partial isisdist.astrogeology.usgs.gov::x86-64_linux_UBUNTU/isis .
> rsync -azv --delete --partial isisdist.astrogeology.usgs.gov::isis3data/data/base data/
-- optional for testing CTX processing below (which doesn't require image kernels)
> rsync -azv --delete --partial --exclude='kernels' isisdist.astrogeology.usgs.gov::isis3data/data/mro data/
> cd ~

> vi .bashrc
or for a GUI editor
> sudo apt-get install gedit
> gedit .bashrc
## add these lines to bottom of .bashrc
export DISPLAY=:0

ISISROOT=~/isis3/isis
export ISISROOT
.  $ISISROOT/scripts/isis3Startup.sh
## end of add lines

6.1) close your Bash terminal and restart it. This will now initialize ISIS3 in your new terminal.
-- Try something (I still get a warning but it seems to work). The warning is QXcbConnection: XCB error: 170 for future reference
> qview $ISIS3DATA/base/dems/MSGR_DEM_USG_EQ_I_V02_prep.cub
-- BTW, LOLA DEM opened but MOLA didn't...? Same size so odd

(7) Test a Linux windowing env. (not really needed and it is still awkward).
> startlxde
-- Use "cntl c" to kill it.

(8) Download other packages for testing the GUI
> sudo apt-get install synaptic
> sudo synaptic
-- try to search and install firefox
-- once installed, launch firefix
> firefox

(9) to run a test CTX image in ISIS3
> sudo apt-get install csh
> cd ~
> mkdir isis3_test
> cd isis3_test
> chmod +x CTX_process_all.csh
> printf "Group = Mapping\n  ProjectionName  = SimpleCylindrical\n   CenterLongitude = 0.0\n  CenterLatitude  = 0.0\nEnd_Group\nEnd" > simp0.map
> ./CTX_process_all.csh simp0.map  0
-- wait several minutes for ISIS3 to do its thing.
> qview P22_009816_1745_XI_05S073W.lev1eo.cub
example: qview with CTX P22_009816_1745_XI_05S073W calibrated only



> sudo apt-get install gpicview
> gpicview P22_009816_1745_XI_05S073W.png
example: gpicview with CTX P22_009816_1745_XI_05S073W.png all map projected


(10) Now use GDAL to create a GIS-ready image (GeoTiff) not just a PNG. 
> sudo add-apt-repository ppa:ubuntugis/ppa && sudo apt-get update
-- Hit enter when prompted, then:
> sudo apt-get install gdal-bin
-- First stretch to 8bit using ISIS3 (0.5% to 99.5% linear stretch -- optional):
stretch from=P22_009816_1745_XI_05S073W.lev2.cub to=P22_009816_1745_XI_05S073W_8bit.cub+8bit+
1:254 USEPERCENTAGES=true pairs="0:1 0.5:1 99.5:254 100:254" null=0 lis=1 lrs=1 his=255 hrs=255
> gdal_translate P22_009816_1745_XI_05S073W_8bit.cub P22_009816_1745_XI_05S073W_8bit.tif
> gpicview P22_009816_1745_XI_05S073W_8bit.tif



(11) Now run ISIS commands from (really a shell script) from Powershell. I guess this means ArcMap or Socet GXP might be able to run ISIS3 commands. hmmm...?

From Windows, start powershell (not the (x86) version). From the horrible blue background (do yourself a favor and turn the background black) run:
> bash -i -c "cd /home/thare/isis3_test ; ./CTX_process_all.csh simp0.map  0"


-- so the trick here is the "-i" which setups the env. for ISIS3 and "-c" runs the command in quotes.
-- Also the Windows locations for /home/thare is here (you may need to show hidden files in Windows to see it): C:\Users\<WIN_USER>\AppData\Local\lxss\home\thare\
-- In Bash, your Windows files are: /mnt/c or /mnt/d, etc.
-- more tricks: https://www.howtogeek.com/262086/how-to-run-linux-commands-from-outside-the-bash-shell-on-windows-10/

reference: https://msdn.microsoft.com/en-us/commandline/wsl/faq





tip: To get an Anconda Python 3.x with GDAL  (and a few other good packages)
Once Miniconda w/ python 3 *.sh is installed, I had to update several missing items


conda install -c conda-forge gdal jupyter basemap mathplotlib xerces-c kealib
-- note putting all the packages on the same line, can help with getting all dependencies correct.

When you run from your Ubuntu side:
> jupyter notebook
you can then run the browser on the Windows-side using the link provided - cool.