Task B-4: Planetary Geodesy USGS Astrogeology Program Presentation to Planetary Cartography and Geologic Mapping Working Group by Brent Archinal USGS Astrogeology.

Slides:



Advertisements
Similar presentations
Open Source Tools and Proprietary Software Who we are Why are we developing software and using Open Source Tools What we are doing How we are implementing.
Advertisements

Tivoli Service Request Manager
The North American Carbon Program Google Earth Collection Peter C. Griffith, NACP Coordinator; Lisa E. Wilcox; Amy L. Morrell, NACP Web Group Organization:
PG&G USGS Jun Submitting Geologic.
Project Proposal.
Spillman Sentryx 6.0.
Business Process Modeling in Microsoft Visio® Interfacing’s BPMN Modeler: Overview.
Programming Tools for Visualization of GIS Data Garret Suen Wednesday, March 5, 2003 CPSC –Advanced Algorithms in GIS and Scientific Applications.
International Ice Charting Working Group IICWG V Data, Information & Customer Support Standing Committee Report Co-Chairs Ari Seina & Florence Fetterer.
The CEGIS Online Bibliography Holly K. Caro In late May of 2009, the Center of Excellence for Geospatial Information Science (CEGIS) decided to consolidate.
1 of 6 Parts of Your Notebook Below is a graphic overview of the different parts of a OneNote 2007 notebook. Microsoft ® OneNote ® 2007 notebooks are digital.
Navigation and Ancillary Information Facility NIF Shape Model Subsystem Preview (DSK) November 2014.
Unrestricted © Siemens AG 2014 All rights reserved.Smarter decisions, better products. What’s New Femap /
Corporation For National Research Initiatives NSF SMETE Library Building the SMETE Library: Getting Started William Y. Arms.
Database System Development Lifecycle Transparencies
March 2010 PDS Imaging Node 1 NASA PDS Imaging Node: NASA PDS Imaging Node: Digital Data Archives and Distribution Archiving and distributing data and.
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
HP Project & Portfolio Management Resource Management July 11, 2007 CIMpleBS.com/HP-PPM/Training-Resource Management.pps By Dan Gallagher See NOTES page.
The Need to Restart NASA Planetary Cartography Planning Brent Archinal Astrogeology Science Center U. S. Geological Survey, Flagstaff, AZ U.S. Department.
Using the Supplier Relationship Management (SRM) CDW-G Punch-out Catalog.
James B. McCarthy - County Executive Summit County Department of Community and Economic Development and The Emergency Management.
Database Planning, Design, and Administration Transparencies
IPDA Update Dan Crichton Tom Stein August 2014 International Planetary Data Alliance.
A Guide to the BIZNET Online Filing System STATE OF CONNECTICUT DEPARTMENT OF CHILDREN & FAMILIES (DCF) DEPARTMENT OF DEVELOPMENTAL SERVICES (DDS) DEPARTMENT.
Kuali Rice at Indiana University Rice Setup Options July 29-30, 2008 Eric Westfall.
What is Sure BDCs? BDC stands for Batch Data Communication and is also known as Batch Input. It is a technique for mass input of data into SAP by simulating.
Data Management Subsystem: Data Processing, Calibration and Archive Systems for JWST with implications for HST Gretchen Greene & Perry Greenfield.
1 U.S. Department of the Interior U.S. Geological Survey National Center for EROS Remote Sensing Technologies Group The Proposed USGS Plan for Digital.
1 The INSPIRE Geoportal Ioannis Kanellopoulos Spatial Data Infrastructures Unit European Commission Joint Research Centre Institute for Environment and.
Publish Calendars to the Web. CCUweb Presentation (10 Minutes) 1 Demonstration of published calendars (10 minutes) 2 Demonstration of importing calendar.
Max Planck Institute for Psycholinguistics Tool development report H. Brugman MPI Nijmegen.
Nightly Releases and Testing Alexander Undrus Atlas SW week, May
Collaborative Work Package Criteria Suitable for accomplishing in a period of 90 days to 1 year. Work should fall within the expertise of one or more consortium.
Usability Issues Documentation J. Apostolakis for Geant4 16 January 2009.
Enterprise GIS Planning and Framework Jennifer Reek GIS Coordinator City of Brookfield, WI.
Navigation and Ancillary Information Facility NIF SPICE Introduction January 2008.
© 2007 by Prentice Hall 1 Introduction to databases.
Thomas C. Stein PDS Geosciences Node Washington University in St. Louis 1MS Supporting Active Surface Missions and Adding Value.
Database System Development Lifecycle 1.  Main components of the Infn System  What is Database System Development Life Cycle (DSDLC)  Phases of the.
IBM Software Group ® Overview of SA and RSA Integration John Jessup June 1, 2012 Slides from Kevin Cornell December 2008 Have been reused in this presentation.
قسم الجيوماتكس Geomatics Department King AbdulAziz University Faculty of Environmental Design GIS Components GIS Fundamentals GEOM 121 Reda Yaagoubi, Ph.D.
Data Issues & Recommendations. Data Issues AON meeting last week—18 AON PIs, plus collaborating groups & programs –CADIS, an AON project for cooperative.
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
Putting the Pieces Together Access DB You Excel Spreadsheet HQ Staff SQLServer DB Standard AF DB (Gunter) Unit POCS Oracle DB Base Web Services Photo &
Intermediate 2 Software Development Process. Software You should already know that any computer system is made up of hardware and software. The term hardware.
Slide 12.1 Chapter 12 Implementation. Slide 12.2 Learning outcomes Produce a plan to minimize the risks involved with the launch phase of an e-business.
Mars in the Planetary Decadal Survey Steve Squyres Cornell University Chairman, Planetary Science Decadal Survey Steve Squyres Cornell University Chairman,
VIPER Quality Assessment Overview Presenter: Sathyadev Ramachandran, SPS Inc.
My Workspace ELearning in Sakai Randy Graff, PhD HSC Training.
NAIF Node C. Acton/B. Semenov MC Face-to-Face Meeting Westwood, California 26,27 August 2014.
USGS DIGITAL TERRAIN MODELS AND MOSAICS FOR LMMP M. R. Rosiek, E. M. Lee, E. T. Howington-Kraus, R. L. Fergason, L. A. Weller, D. M. Galuszka, B. L. Redding,
Using the AccuGlobe Software with the IndianaMap Using the AccuGlobe Software.
Navigation and Ancillary Information Facility NIF Introduction to WebGeocalc October 2014 SPICE components and services are not restricted under ITAR and.
March 2004 At A Glance autoProducts is an automated flight dynamics product generation system. It provides a mission flight operations team with the capability.
Task B-5: Lunar Control Network Improvement USGS Astrogeology Team Brent Archinal Mark Rosiek Flagstaff AZ 26 August 2004.
The System Life Cycle The systems lifecycle is the set of stages that are followed when developing an information system.
INTRODUCTION TO GIS  Used to describe computer facilities which are used to handle data referenced to the spatial domain.  Has the ability to inter-
Application Software System Software.
TSS Database Inventory. CIRA has… Received and imported the 2002 and 2018 modeling data Decided to initially store only IMPROVE site-specific data Decided.
Program design and algorithm development We will consider the design of your own toolbox to be included among the toolboxes already available with your.
July 29, MEPAG Goals Committee Update Jeffrey R. Johnson Chair, MEPAG Goals Committee USGS Astrogeology Science Center Flagstaff,
SPI NIGHTLIES Alex Hodgkins. SPI nightlies  Build and test various software projects each night  Provide a nightlies summary page that displays all.
APEC-TPT ITS Group Action Plan (proposed) March 2000 DRAFT.
+ UVIS Data Visualization UVIS Team Meeting Braunschweig, Deutschland June 18, 2012.
Shape Model Subsystem Preview (DSK)
INTRODUCTION TO GEOGRAPHICAL INFORMATION SYSTEM
Editing Your Website on SharePoint 2013
Increased Efficiency and Effectiveness
Present and Future Deep Space Projects
APE EAD3 introduction - DARIAH - Brussels
Presentation transcript:

Task B-4: Planetary Geodesy USGS Astrogeology Program Presentation to Planetary Cartography and Geologic Mapping Working Group by Brent Archinal USGS Astrogeology Team 2004 August 26 U. S. Geological Survey Flagstaff, AZ

Purpose and Project Description Provide and improve the infrastructure for NASA planetary Geodesy needs, i.e. to support “the development and production of cartographic products of planetary data sets” (PG&G NRA), by efforts to: Modernize, document, and further develop RAND/USGS planetary geodesy software. Modernize, document, and further develop RAND/USGS planetary geodesy software. Document, study, improve, and archive existing RAND/USGS control networks. Document, study, improve, and archive existing RAND/USGS control networks. Assist planetary geodesy community generally, e.g. via coordinating with various working groups (MGCWG, IAU/IAG). Assist planetary geodesy community generally, e.g. via coordinating with various working groups (MGCWG, IAU/IAG).

Outline Current Planetary Geodesy Needs Current Planetary Geodesy Needs FY04 Accomplishments FY04 Accomplishments FY05 Planned Course of Work FY05 Planned Course of Work Long-Range Activities Long-Range Activities Questions from PCGMWG Questions from PCGMWG Summary Summary

Current (NASA & USGS) Planetary Geodesy Needs RAND (and now USGS) defining networks and software need to continually be documented and maintained, as the basis of nearly all existing planetary cartographic products. “Old” images and coordinate systems will never go out of use. RAND (and now USGS) defining networks and software need to continually be documented and maintained, as the basis of nearly all existing planetary cartographic products. “Old” images and coordinate systems will never go out of use. New data needs to be continually tied to these networks in order to be useful, from whatever data source, location, or purpose. Whether from cameras or altimeters, near or far from planetary surfaces, and for various scales of mapping or for navigation and landing this is an essential feature of all planetary missions. New data needs to be continually tied to these networks in order to be useful, from whatever data source, location, or purpose. Whether from cameras or altimeters, near or far from planetary surfaces, and for various scales of mapping or for navigation and landing this is an essential feature of all planetary missions. Coordination needed with various individuals, working groups, missions, etc. on defining these networks, coordinate systems, planetary constants, and standards, particularly with the NASA MGCWG and (internationally) the IAU/IAG. Coordination needed with various individuals, working groups, missions, etc. on defining these networks, coordinate systems, planetary constants, and standards, particularly with the NASA MGCWG and (internationally) the IAU/IAG.

FY04 Accomplishments A) Consolidation and Improvement of RAND/USGS Data Handling and Adjustment Software Soon (next release) will have executables provided as package with ISIS, replacing ISIS “jigsaw” function. Soon (next release) will have executables provided as package with ISIS, replacing ISIS “jigsaw” function. Running under Solaris, Linux, Mac. Running under Solaris, Linux, Mac. ISIS, preprocessing, and “randlsq” adjustment programs interfaced using 3 Perl scripts. ISIS, preprocessing, and “randlsq” adjustment programs interfaced using 3 Perl scripts.  “build-meas.pl” – Creates mm measurement file from pixel measurement file(s).  “build-ppp.pl” – Collects a priori information.  “run-randlsq.pl” – Performs photogrammetric solution.  Currently supporting: Moon (LO, Clementine), Mars (Mariner 9, Viking), and Saturnian moons (Voyager, Cassini); Soon: Mariner 10, Galileo.

FY04 Accomplishments, continued A) Consolidation and Improvement of RAND/USGS Data Handling and Adjustment Software, continued Cassini ISS processing added (using Cassini funding). Cassini ISS processing added (using Cassini funding). Consolidation of multiple version RAND programs nearly complete. Consolidation of multiple version RAND programs nearly complete.  (15+2 new) Line/sample to x/y in mm programs merged into 1 or 2. A few RAND programs converted for Linux use. A few RAND programs converted for Linux use. Main “randlsq” adjustment program being changed to use sparse matrix and vector routines, in order to conserve memory and to allow output of solution variance-covariance information. Main “randlsq” adjustment program being changed to use sparse matrix and vector routines, in order to conserve memory and to allow output of solution variance-covariance information.

Existing RAND Planetary Control Networks

FY04 Accomplishments, cont. B) Maintenance and Archiving of Current Planetary Control Networks RAND data files and solutions exist for 23 planetary bodies (previous slide), and in most of these cases the RAND solutions define the coordinate system for these objects. Making USGS and RAND solutions available on the web. Will be complete for most bodies at end of this FY. See ControlNetworks/ for Moon and Mars and soon Saturnian moons, and Schenk solutions.  Making USGS and RAND solutions available on the web. Will be complete for most bodies at end of this FY. See ControlNetworks/ for Moon and Mars and soon Saturnian moons, and Schenk solutions.  ControlNetworks/ ControlNetworks/ Continuing to archive copies of control network data files (and software) off-site. Continuing to archive copies of control network data files (and software) off-site. Working on a (delayed) Mars control network publication. Will be based on ISPRS paper already published. Working on a (delayed) Mars control network publication. Will be based on ISPRS paper already published.

FY04 Accomplishments, cont. C) Planetary Geodesy Community Assistance – E.g. IAU/IAG Working Group on Cartographic Coordinates and Rotational Elements This working group sets the defining constants for planetary bodies, e.g. size, shape, rotation, and reference frame This working group sets the defining constants for planetary bodies, e.g. size, shape, rotation, and reference frame Archinal now Vice-Chair. Archinal now Vice-Chair report submitted for publication last week report submitted for publication last week. Important to stay involved so that USGS, NASA standards are adopted internationally, or in conjunction with others (ESA, DLR, Japan, etc.) Important to stay involved so that USGS, NASA standards are adopted internationally, or in conjunction with others (ESA, DLR, Japan, etc.) Other groups: Provided info on standards to ESRI and to ISO group – for incorporation into GIS software. Provided info on standards to ESRI and to ISO group – for incorporation into GIS software. Also liaison to NASA MGCWG. Also liaison to NASA MGCWG.

IAU/IAG Working Group, cont IAU/IAG report includes: 2003 IAU/IAG report includes:  Specific MOLA reference surface defined for Mars – based on NASA MGCWG work.  Adopted system for asteroids and comets: planetocentric (east) longitude and right handed (positive and negative pole).  Allowed for alternate use (all bodies) of Cartesian coordinates.  Addition of several asteroids and first comet (19P/Borrelly).

FY05 Planned Course of Work A) Consolidation and Improvement of RAND/USGS Data Handling and Adjustment Software Carried over (with funding) from FY04: Carried over (with funding) from FY04:  New routine to add image statistics to data in order to check correlations with solution residuals.  New routine to interpolate radii from a digital radius model.  Add Mariner 9 preprocessing program for Mariner 9 data (for those wishing to update pointing for use of such images). Further improvements regarding ISIS integration, e.g. in Perl scripts and preprocessing programs, based on user input. Further improvements regarding ISIS integration, e.g. in Perl scripts and preprocessing programs, based on user input. Search for and testing of faster sparse matrix inversions routines. Search for and testing of faster sparse matrix inversions routines.

FY05 Planned Course of Work, cont. B) Maintenance and Archiving of Current Planetary Control Networks Continue making planetary control network information available on the web. Continue making planetary control network information available on the web.  Any New USGS solutions (Moon, Saturnian moons).  Solutions from others (Schenk and DLR – Saturnian Moons; Duxbury – Deimos and Phobos; others?). Continue to investigate and verify the measurements and control networks for Saturnian moons. Continue to investigate and verify the measurements and control networks for Saturnian moons.  Examine, compare USGS, Schenk networks for Rhea and Enceladus; Decide on best or combine.  Iapetus and Mimas in FY06. Tethys, Hyperion(?), Dione, in FY07 or 08.

FY05 Planned Course of Work, cont. C) Participation in IAU/IAG Working Group on Cartographic Coordinates and Rotational Elements of the Planets and Satellite Archinal will: Continue as WG member. Continue as WG member. Post preprint version of 2003 report to the web. Post preprint version of 2003 report to the web. Provide web site for WG. Also add other related information (best “other” or new constants). Provide web site for WG. Also add other related information (best “other” or new constants). Collect possible changes for 2006 report. Collect possible changes for 2006 report.  Saturnian moons, more asteroids, Wild 2.

Long-Range Plans (FY06 and beyond) Investigate improved (statistical) methods of looking for problem measurements, i.e. automatic editing of data. Investigate improved (statistical) methods of looking for problem measurements, i.e. automatic editing of data. Finish investigation and improvement of control networks for Saturnian moons. Proceed (FY08 or later) to examining other networks. Cross reference control and nomenclature databases? Finish investigation and improvement of control networks for Saturnian moons. Proceed (FY08 or later) to examining other networks. Cross reference control and nomenclature databases? Continue to participate in MGCWG, IAU/WG on Cartographic Coordinates and Rotational Elements. Continue to participate in MGCWG, IAU/WG on Cartographic Coordinates and Rotational Elements. Under separate funding, continue model and software development allowing for new types of sensors, data, and constraints, e.g. integration of orbiter, descent, lander, and rover images. Under separate funding, continue model and software development allowing for new types of sensors, data, and constraints, e.g. integration of orbiter, descent, lander, and rover images. Similarly, allow for further types of data, e.g. Cassini radar at Titan. Similarly, allow for further types of data, e.g. Cassini radar at Titan. Develop models and software for mission simulation for planning data collection before a mission is undertaken. Develop models and software for mission simulation for planning data collection before a mission is undertaken. Other software improvements… Other software improvements…

Questions from PCGMWG – 1 “At the PCGMWG meeting, a presentation of the 4 proposed general software improvements would be helpful. Such a discussion would be beneficial for supporting the future direction of this task... Bringing the radargrammetric software up to speed as well is a good idea for future work”. 1. Convert control network information to NAIF SPICE Control Net Kernel.  Drafted by NAIF in  Apparently no data in this format yet.  Use/extend some other existing format?  Work with NAIF, others, to draft new format and use? 2. Extract “postage stamps” of control points.  Would help (with appropriate software) to let others identify and use points. (Part of NAIF draft above.)  Possibly could be used automatically, i.e. for automatic tie pointing or even autonomous navigation.

Questions from PCGMWG – 1, continued 3. Bring the general radargrammetric solution program (now called “radar”) up to date. For Magellan only, not a high priority, but we want to check Venus control at some point. For Magellan only, not a high priority, but we want to check Venus control at some point. More likely would want to adapt for Cassini RADAR use (but should leverage with other funding). More likely would want to adapt for Cassini RADAR use (but should leverage with other funding). Other option is to extend and merge with photogrammetric solutions, e.g. for Titan or Moon. Other option is to extend and merge with photogrammetric solutions, e.g. for Titan or Moon. 4. Software to display differences between solutions  Currently labor intensive, using home-grown, Excel, and ArcMap.  Write custom software. Possibly not too ideal, but might provide most desired results.  Write scripts and use commercial software, e.g. ArcWorkstation.

Questions from PCGMWG - 2 “Rigorous development of control net solutions is timely for the outer satellites. Much is said about algorithmic improvement, but insufficient details have been published, even in abstract form, so it is hard to assess the scientific impact of the ‘better mousetrap’.” Not clear if about the “algorithmic” development of the software or about the improvements being made to the control networks. Which? For either publications are proceeding… Not clear if about the “algorithmic” development of the software or about the improvements being made to the control networks. Which? For either publications are proceeding… As to scientific impact, certainly one of our goals is to assist in providing products that will assist with scientific investigations and particularly geologic mapping. But we hope it’s clear that this task (if not much of the USGS effort) is largely the support of NASA planetary mapping and navigation “infrastructure”. As to scientific impact, certainly one of our goals is to assist in providing products that will assist with scientific investigations and particularly geologic mapping. But we hope it’s clear that this task (if not much of the USGS effort) is largely the support of NASA planetary mapping and navigation “infrastructure”.

Summary Continue work begun at RAND to maintain and improve planetary control networks on which most planetary cartographic products are based. Continue work begun at RAND to maintain and improve planetary control networks on which most planetary cartographic products are based. Begin to allow for combination of new types of data from whatever data source, location or purpose. Begin to allow for combination of new types of data from whatever data source, location or purpose. Continue cooperation regarding defining constants, networks, etc. Continue cooperation regarding defining constants, networks, etc.