search?t=product&i=10&o=%40astro%3Asearch_rank&d=1&p=6&m=application%2Fzip<pre class="debug"><?xml version="1.0" encoding="UTF-8"?>
<data>
  <lucene>TYPE:"astro:doc" AND PATH:"/app:company_home/cm:Products//*" AND @astro\:search_enable:true AND @\content.mimetype:application/zip</lucene>
  <count>72</count>
  <results>
    <item>
  <link>/Docs/Photogrammetry/April-29-May-1-2014-Files.zip</link>
  <thumb>/Docs/Photogrammetry/April-29-May-1-2014-Files.zip/thumb.png</thumb>
  <browse>/Docs/Photogrammetry/April-29-May-1-2014-Files.zip/browse.jpg</browse>
  <title>Files to Bring with you for April 29 - May 1 2014 Training</title>
  <description><![CDATA[Files to Bring by Participants in the  April 29 - May 1 2014 Training]]></description>
  <publicationDate></publicationDate>
  <minimumLatitude>null</minimumLatitude>
  <maximumLatitude>null</maximumLatitude>
  <minimumLongitude>null</minimumLongitude>
  <maximumLongitude>null</maximumLongitude>
  <wmsMap></wmsMap>
  <wmsLayer></wmsLayer>
  <size>9002682</size>
  <mimetype>application/zip</mimetype>
  <extension>zip</extension>
</item>
<item>
  <link>/Docs/Cartography/AstroNASAHQ-SMD-201210_v4.zip</link>
  <thumb>/Docs/Cartography/AstroNASAHQ-SMD-201210_v4.zip/thumb.png</thumb>
  <browse>/Docs/Cartography/AstroNASAHQ-SMD-201210_v4.zip/browse.jpg</browse>
  <title>Planetary Cartography Issues & Concerns</title>
  <description><![CDATA[]]></description>
  <publicationDate></publicationDate>
  <minimumLatitude>null</minimumLatitude>
  <maximumLatitude>null</maximumLatitude>
  <minimumLongitude>null</minimumLongitude>
  <maximumLongitude>null</maximumLongitude>
  <wmsMap></wmsMap>
  <wmsLayer></wmsLayer>
  <size>2991725</size>
  <mimetype>application/zip</mimetype>
  <extension>zip</extension>
</item>
<item>
  <link>/Docs/Cartography/Carto-recommendations-USGS-for-VEXAG_Nov.1.13.zip</link>
  <thumb>/Docs/Cartography/Carto-recommendations-USGS-for-VEXAG_Nov.1.13.zip/thumb.png</thumb>
  <browse>/Docs/Cartography/Carto-recommendations-USGS-for-VEXAG_Nov.1.13.zip/browse.jpg</browse>
  <title>The Status of Cartography Planning for NASA</title>
  <description><![CDATA[]]></description>
  <publicationDate></publicationDate>
  <minimumLatitude>null</minimumLatitude>
  <maximumLatitude>null</maximumLatitude>
  <minimumLongitude>null</minimumLongitude>
  <maximumLongitude>null</maximumLongitude>
  <wmsMap></wmsMap>
  <wmsLayer></wmsLayer>
  <size>2543544</size>
  <mimetype>application/zip</mimetype>
  <extension>zip</extension>
</item>
<item>
  <link>/Docs/Photogrammetry/TUTORIALS_JUNE2009.zip</link>
  <thumb>/Docs/Photogrammetry/TUTORIALS_JUNE2009.zip/thumb.png</thumb>
  <browse>/Docs/Photogrammetry/TUTORIALS_JUNE2009.zip/browse.jpg</browse>
  <title>Photogrammetry Tutorial SOCET SET - Stereo process with HiRISE images, ISIS3 and SOCET SET v5.x</title>
  <description><![CDATA[]]></description>
  <publicationDate></publicationDate>
  <minimumLatitude>null</minimumLatitude>
  <maximumLatitude>null</maximumLatitude>
  <minimumLongitude>null</minimumLongitude>
  <maximumLongitude>null</maximumLongitude>
  <wmsMap></wmsMap>
  <wmsLayer></wmsLayer>
  <size>12999483</size>
  <mimetype>application/zip</mimetype>
  <extension>zip</extension>
</item>
<item>
  <link>/Software/GISTutorials/USGS_Sep2010_GIS-wkshp_examples.zip</link>
  <thumb>/Software/GISTutorials/USGS_Sep2010_GIS-wkshp_examples.zip/thumb.png</thumb>
  <browse>/Software/GISTutorials/USGS_Sep2010_GIS-wkshp_examples.zip/browse.jpg</browse>
  <title>September 2010 GIS Workshop for Planetary Mappers Examples</title>
  <description><![CDATA[]]></description>
  <publicationDate></publicationDate>
  <minimumLatitude>null</minimumLatitude>
  <maximumLatitude>null</maximumLatitude>
  <minimumLongitude>null</minimumLongitude>
  <maximumLongitude>null</maximumLongitude>
  <wmsMap></wmsMap>
  <wmsLayer></wmsLayer>
  <size>324658119</size>
  <mimetype>application/zip</mimetype>
  <extension>zip</extension>
</item>
<item>
  <link>/Hyperion/ControlNetworks/Hyperion_data.zip</link>
  <thumb>/Hyperion/ControlNetworks/thumbnails/Hyperion_Voyager.jpg</thumb>
  <browse>/Hyperion/ControlNetworks/thumbnails/Hyperion_Voyager.jpg</browse>
  <title>Hyperion_data.zip</title>
  <description><![CDATA[<p>This page has been created as part of a project to put planetary control networks on the web. These control network measurements for Saturn’s moon, Hyperion, originated from Merton Davies and Tim Colvin and Frank Katayama at the RAND Corporation, and Peter Thomas from Cornell University, and were provided to the USGS in 2000. Although control-network measurements exist for Hyperion, no control network was ever completed for it due to its chaotic rotation. The input files included here consist of measurements of common points (control points, sometimes called tie points) on images of a planetary body. The output files include the body coordinates of the control points in latitude, longitude, and radius, and revised orientation information (camera pointing) for the images. The primary use of such information is for the creation of image mosaics of the planetary body. However, controlled solutions can also provide fundamental data on the size and shape of the body, its rotation period, and the direction of its polar axis in space. The control point coordinates also usually serve as a coordinate reference frame that defines the fundamental coordinate reference system for the body in question. Formatting of these control network data for Saturn’s moon, Hyperion, has yet to be updated for compatibility with the USGS ISIS2 and ISIS3 cartography software.
 <p><b><u>References:</u></b><br>
<a href="http://www.rand.org/pubs/notes/N3330.html"><font color="#0000ff">Colvin, Tim R. (1992). "Photogrammetric Algorithms and Software for Spacecraft Optical Imaging Systems, A RAND Note”, N-3330-JPL. Available from http://www.rand.org/pubs/notes/N3330.html</font></a></p>
<p><a href=" http://www.sciencedirect.com/science/article/pii/001910358590065X?via%3Dihub "><font color="#0000ff"">P. Thomas and J. Veverka, 1985, Hyperion: Analysis of Voyager observations,  Icarus (ISSN 0019-1035), vol. 64, Dec. 1985, p. 414-424. </font></a></p>
<p><b><u>Image Description:</u></b><br>
This global mosaic of Hyperion utilizes only 4 images: 4394328, 4395906, 4396802 and 4397243. Simple cylindrical map projection. Images have been high-pass filtered. 
<p> <p/>

]]></description>
  <publicationDate></publicationDate>
  <minimumLatitude>null</minimumLatitude>
  <maximumLatitude>null</maximumLatitude>
  <minimumLongitude>null</minimumLongitude>
  <maximumLongitude>null</maximumLongitude>
  <wmsMap></wmsMap>
  <wmsLayer></wmsLayer>
  <size>3513250</size>
  <mimetype>application/zip</mimetype>
  <extension>zip</extension>
</item>
<item>
  <link>/Iapetus/ControlNetworks/Iapetus_data.zip</link>
  <thumb>/Iapetus/ControlNetworks/thumbnails/Iapetus_photomosaic_100.jpg</thumb>
  <browse>/Iapetus/ControlNetworks/thumbnails/Iapetus_photomosaic_512.jpg</browse>
  <title>Iapetus Voyager Image Control Network (RAND)</title>
  <description><![CDATA[<p>This page has been created as part of a project to put planetary control networks on the web. This control network for Saturn’s moon, Iapetus, originated from Merton Davies and Tim Colvin at the RAND Corporation and was provided to the USGS in 2000. The control network solution was originally performed with software developed at RAND, and documented by <a href="http://www.rand.org/pubs/notes/N3330.html"><font color="#0000ff">Colvin (1992)</font></a>. It has been converted into files that could be used with (successively) the RAND/USGS Planetary Geodesy (RUPG) Software, and the <a href="https://isis.astrogeology.usgs.gov/documents/Isis2UserDocs/index.html"><font color="#0000ff">USGS ISIS2</font></a> software (using the application, described by <a href="http://adsabs.harvard.edu/abs/2012ISPAn..I4..203E"><font color="#0000ff">Edmundson et al. 2012</font></a>). Each control network is essentially a set of photogrammetric solution (input and output) files. The input files consist of, aside from a priori information, measurements of common points (control points, sometimes called tie points) on images of a planetary body. The output files include the body coordinates of the control points in latitude, longitude, and radius, and revised orientation information (camera pointing) for the images. The primary use of such information is for the creation of image mosaics of the planetary body. However, these solutions can also provide fundamental data on the size and shape of the body, its rotation period, and the direction of its polar axis in space. The control point coordinates also usually serve as a coordinate reference frame that defines the fundamental coordinate reference system for the body in question. Formatting of this control network data for Saturn’s moon, Iapetus, has been updated for compatibility with the USGS ISIS2 cartography software. This network consists of 462 control points and incorporates 27 images from the Voyager I and II missions (<a href="http://onlinelibrary.wiley.com/doi/10.1029/JA088iA11p08729/abstract"><font color="#0000ff">Davies and Katayama, 1983</font></a>). This release is comprised of data from original RAND control network solutions, the ISIS2 <i><a href="https://isis.astrogeology.usgs.gov/Isis2/isis-bin//pdfs2.cgi?qmatch"><font color="#0000ff">qmatch</font></a></i>-formatted control network, Voyager I and II images (processed to the ISIS2 format), ISIS scripts to process PDS (.imq) images into ISIS2 formats, and file-format description files. </p> 
<p><b><u>References:</u></b><br>
<a href="http://www.rand.org/pubs/notes/N3330.html"><font color="#0000ff">Colvin, Tim R. (1992). "Photogrammetric Algorithms and Software for Spacecraft Optical Imaging Systems," A RAND Note, N-3330-JPL. Available from http://www.rand.org/pubs/notes/N3330.html</font></a></p>
<p><a href="http://www.sciencedirect.com/science/article/pii/001910358490023X"><font color="#0000ff"">Davies, M. E.; Katayama, F. Y. (1983), Davies, M. E.; Katayama, F. Y. (1983), The control network of Iapetus, Icarus (ISSN 0019-1035), vol. 59, Aug. 1984, p. 199-204, DOI: 10.1016/0019-1035(84)90023-X</font></a></p>
<p><b><u>Image Description:</u></b><br>
This image is a USGS <a href=http://pubs.usgs.gov/imap/2157/plate-2.pdf><font color=”#0000ff”>controlled photomosaic of Iapetus</font></a>, compiled from Voyager 1 and 2 images. We believe this 1992 image was created either form the RAND control network provided here, or from an updated version of the same network. </p>

<p> <p/>
]]></description>
  <publicationDate></publicationDate>
  <minimumLatitude>null</minimumLatitude>
  <maximumLatitude>null</maximumLatitude>
  <minimumLongitude>null</minimumLongitude>
  <maximumLongitude>null</maximumLongitude>
  <wmsMap></wmsMap>
  <wmsLayer></wmsLayer>
  <size>16349006</size>
  <mimetype>application/zip</mimetype>
  <extension>zip</extension>
</item>
<item>
  <link>/Gaspra/ControlNetworks/Gaspra_data.zip</link>
  <thumb>/Gaspra/ControlNetworks/thumbnails/Gaspa_100.jpg</thumb>
  <browse>/Gaspra/ControlNetworks/thumbnails/Gaspa_512.jpg</browse>
  <title>Gaspra_data.zip</title>
  <description><![CDATA[<p>This page has been created as part of a project to put planetary control networks on the web. This control network for asteroid 951 Gaspra originated from Merton Davies and Tim Colvin at the RAND Corporation and was provided to the USGS in 1995. The control network solution was originally performed with software developed at RAND, and documented by <a href="http://www.rand.org/pubs/notes/N3330.html"><font color="#0000ff">Colvin (1992)</font></a>. Each control network is essentially a set of photogrammetric solution (input and output) files. The input files consist of, aside from a priori information, measurements of common points (control points, sometimes called tie points) on images of a planetary body. The output files include the body coordinates of the control points in latitude, longitude, and radius, and revised orientation information (camera pointing) for the images. The primary use of such information is for the creation of image mosaics of the planetary body. However, these solutions can also provide fundamental data on the size and shape of the body, its rotation period, and the direction of its polar axis in space. The control point coordinates also usually serve as a coordinate reference frame that defines the fundamental coordinate reference system for the body in question. This network consists of 130 control points and incorporates 14 images from the Galileo SSI instrument (<a href="https://www.sciencedirect.com/science/article/pii/S0019103584710037"><font color="#0000ff">Davies et al., 1994</font></a>). This release is comprised of data from original RAND control network solutions raw Galileo SSI images and file-format description files. </p> <p><b><u>References:</u></b><br> <a href="http://www.rand.org/pubs/notes/N3330.html"><font color="#0000ff">Colvin, Tim R. (1992). "Photogrammetric Algorithms and Software for Spacecraft Optical Imaging Systems," A RAND Note, N-3330-JPL. Available from http://www.rand.org/pubs/notes/N3330.html</font></a></p> <p><a href=" https://www.sciencedirect.com/science/article/pii/S0019103584710037"><font color="#0000ff"">Davies, M. E., et al., (1994), The Direction of the North Pole and the Control Network of Asteroid 951 Gaspra, Icarus, vol. 107 #1, January 1994, p. 18-22. DOI: 10.1006/icar.1994.1003</font></a></p> <p><b><u>
]]></description>
  <publicationDate></publicationDate>
  <minimumLatitude>null</minimumLatitude>
  <maximumLatitude>null</maximumLatitude>
  <minimumLongitude>null</minimumLongitude>
  <maximumLongitude>null</maximumLongitude>
  <wmsMap></wmsMap>
  <wmsLayer></wmsLayer>
  <size>2003895</size>
  <mimetype>application/zip</mimetype>
  <extension>zip</extension>
</item>
<item>
  <link>/Ida/ControlNetworks/Ida_data.zip</link>
  <thumb>/Ida/ControlNetworks/thumbnails/Ida_100.jpg</thumb>
  <browse>/Ida/ControlNetworks/thumbnails/Ida_512.jpg</browse>
  <title>Ida_data.zip</title>
  <description><![CDATA[<p>This page has been created as part of a project to put planetary control networks on the web. This control network for asteroid 243 Ida originated from Merton Davies and Tim Colvin at the RAND Corporation and was provided to the USGS in 1995. The control network solution was originally performed with software developed at RAND, and documented by <a href="http://www.rand.org/pubs/notes/N3330.html"><font color="#0000ff">Colvin (1992)</font></a>. Each control network is essentially a set of photogrammetric solution (input and output) files. The input files consist of, aside from a priori information, measurements of common points (control points, sometimes called tie points) on images of a planetary body. The output files include the body coordinates of the control points in latitude, longitude, and radius, and revised orientation information (camera pointing) for the images. The primary use of such information is for the creation of image mosaics of the planetary body. However, these solutions can also provide fundamental data on the size and shape of the body, its rotation period, and the direction of its polar axis in space. The control point coordinates also usually serve as a coordinate reference frame that defines the fundamental coordinate reference system for the body in question. This network consists of 255 control points and incorporates 10 images from the Galileo SSI instrument (<a href="https://www.sciencedirect.com/science/article/pii/S0019103596900342"><font color="#0000ff">Davies et al., 1994</font></a>). This release is comprised of data from original RAND control network solutions raw Galileo SSI images and file-format description files. </p> <p><b><u>References:</u></b><br> <a href="http://www.rand.org/pubs/notes/N3330.html"><font color="#0000ff">Colvin, Tim R. (1992). "Photogrammetric Algorithms and Software for Spacecraft Optical Imaging Systems," A RAND Note, N-3330-JPL. Available from http://www.rand.org/pubs/notes/N3330.html</font></a></p> <p><a href="https://ac.els-cdn.com/S0019103596900342/1-s2.0-S0019103596900342-main.pdf?_tid=012184b6-2188-48eb-aba8-c1bd49a3dede&acdnat=1523578932_7ce0f0281a020b8105355ea010e9e816"><font color="#0000ff"">Davies, M. E., et al., (1994), The Direction of the North Pole and the Control Network of Asteroid 243 Ida, Icarus, vol. 107 #1, January 1994, p. 18-22. DOI: 10.1006/icar.1994.1003</font></a></p> <p><b><u>
]]></description>
  <publicationDate></publicationDate>
  <minimumLatitude>null</minimumLatitude>
  <maximumLatitude>null</maximumLatitude>
  <minimumLongitude>null</minimumLongitude>
  <maximumLongitude>null</maximumLongitude>
  <wmsMap></wmsMap>
  <wmsLayer></wmsLayer>
  <size>838075</size>
  <mimetype>application/zip</mimetype>
  <extension>zip</extension>
</item>
<item>
  <link>/Triton/ControlNetworks/triton_data.zip</link>
  <thumb>/Triton/ControlNetworks/thumbnails/Triton_Voyager_mosaic.jpg</thumb>
  <browse>/Triton/ControlNetworks/thumbnails/Triton_Voyager_mosaic.jpg</browse>
  <title>Triton Voyager Image Control Network (RAND)</title>
  <description><![CDATA[<p>This page has been created as part of a project to put planetary control networks on the web. This control network for Neptune’s moon, Triton, originated from Merton Davies and Tim Colvin and Frank Katayama at the RAND Corporation, and Peter Thomas from Cornell University, and was provided to the USGS in 2000. The control network solution was originally performed with software developed at RAND, and documented by <a href="http://www.rand.org/pubs/notes/N3330.html"><font color="#0000ff">Colvin (1992)</font></a>. Each control network is essentially a set of photogrammetric solution (input and output) files. The input files consist of, aside from a priori information, measurements of common points (control points, sometimes called tie points) on images of a planetary body. The output files include the body coordinates of the control points in latitude, longitude, and radius, and revised orientation information (camera pointing) for the images. The primary use of such information is for the creation of image mosaics of the planetary body. However, these solutions can also provide fundamental data on the size and shape of the body, its rotation period, and the direction of its polar axis in space. The control point coordinates also usually serve as a coordinate reference frame that defines the fundamental coordinate reference system for the body in question. Formatting of this control network data for Neptune’s moon, Triton, has yet to be updated for compatibility with the USGS ISIS2 and ISIS3 cartography software. The RAND control network available here has 105 points (with 505 measurements) spanning 57 images, and is described in (<a href="https://agupubs.onlinelibrary.wiley.com/doi/10.1029/91JE00976"><font color="#0000ff">Davies et al., 1991</font></a>). This release is comprised of data from original RAND control network solutions from Voyager I and II images.</p>
 
<p><b><u>References:</u></b><br>
<a href="http://www.rand.org/pubs/notes/N3330.html"><font color="#0000ff">Colvin, Tim R. (1992). "Photogrammetric Algorithms and Software for Spacecraft Optical Imaging Systems, A RAND Note”, N-3330-JPL. Available from http://www.rand.org/pubs/notes/N3330.html</font></a></p>
<p><a href="https://agupubs.onlinelibrary.wiley.com/doi/10.1029/91JE00976"> Davies, Merton E.; Rogers, Patricia G.; Colvin, Tim R., 1991, A control network of Triton, Journal of Geophysical Research (ISSN 0148-0227), vol. 96, p. 15,675-15,681.</font></a></p>
<p><b><u>Image Description:</u></b><br>
This global mosaic of Triton utilizes the best image quality and moderate resolution coverage supplied by the Voyager I and II spacecraft. This mosaic was prepared by the RAND Corporation. The image data was selected on the basis of overall image quality, reasonable input resolution and availability of moderate viewing and sun angles for topography.
<p> <p/>
]]></description>
  <publicationDate></publicationDate>
  <minimumLatitude>null</minimumLatitude>
  <maximumLatitude>null</maximumLatitude>
  <minimumLongitude>null</minimumLongitude>
  <maximumLongitude>null</maximumLongitude>
  <wmsMap></wmsMap>
  <wmsLayer></wmsLayer>
  <size>12633450</size>
  <mimetype>application/zip</mimetype>
  <extension>zip</extension>
</item>

  </results>
</data>
</pre>