{"action":"create","ckan_id":null,"date_created":"Sat, 07 Feb 2026 20:32:09 GMT","date_finished":null,"harvest_job_id":"5e5e88d9-683a-467f-8bee-1d6cfcb471c0","harvest_source_id":"31f41541-38a0-400b-b240-10ebcb0acd9a","id":"e4e3b05b-9bf3-46e6-a2c3-08457db4d310","identifier":"https://dggs.alaska.gov/webpubs/metadata/RDF2011-3M_gp.xml","parent_identifier":null,"source_hash":"63bd08db331ac18c610080e7e93c4bc6c35173dbcb19f77b9c5bd9cb695ab27c","source_raw":"<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<metadata>\n<idinfo>\n<citation>\n<citeinfo>\n<origin>Hubbard, T.D.</origin>\n<origin>Braun, M.L.</origin>\n<origin>Westbrook, R.E.</origin>\n<origin>Gallagher, P.E.</origin>\n<pubdate>2012</pubdate>\n<title>High-resolution lidar data for infrastructure corridors, Healy Quadrangle, Alaska</title>\n<geoform>LAS v. 1.2 point-cloud data</geoform>\n<serinfo>\n<sername>Raw Data File</sername>\n<issue>RDF 2011-3M</issue>\n</serinfo>\n<pubinfo>\n<pubplace>Fairbanks, Alaska USA</pubplace>\n<publish>State of Alaska, Department of Natural Resources, Division of Geological &amp; Geophysical Surveys</publish>\n</pubinfo>\n<onlink>http://dx.doi.org/10.14509/23163</onlink>\n<lworkcit>\n<citeinfo>\n<origin>Hubbard, T.D.</origin>\n<origin>Koehler, R.D.</origin>\n<origin>Combellick, R.A.</origin>\n<pubdate>2011</pubdate>\n<title>High-resolution lidar data for Alaska infrastructure corridors</title>\n<geoform>document</geoform>\n<serinfo>\n<sername>Raw Data File</sername>\n<issue>RDF 2011-3</issue>\n</serinfo>\n<pubinfo>\n<pubplace>Fairbanks, AK USA</pubplace>\n<publish>State of Alaska, Department of Natural Resources, Division of Geological &amp; Geophysical Surveys</publish>\n</pubinfo>\n<onlink>http://dx.doi.org/10.14509/22722</onlink>\n</citeinfo>\n</lworkcit>\n</citeinfo>\n</citation>\n<descript>\n<abstract>In advance of design, permitting, and construction of a pipeline to deliver North Slope natural gas to out-of-state customers and Alaska communities, the Division of Geological &amp; Geophysical Surveys (DGGS) has acquired lidar (Light Detection and Ranging) data along proposed pipeline routes, nearby areas of infrastructure, and regions where significant geologic hazards have been identified. Lidar data will serve multiple purposes, but have primarily been collected to (1) evaluate active faulting, slope instability, thaw settlement, erosion, and other engineering constraints along proposed pipeline routes, and (2) provide a base layer for the state-federal GIS database that will be used to evaluate permit applications and construction plans. The dataset represents ground-classified laser returns from the lidar survey and their associated geospatial coordinates.</abstract>\n<purpose>Provide high-resolution terrain elevation and land cover elevation data.</purpose>\n<supplinf>\nThis metadata file was written to document and describe, as a whole, all points classified as ground points generated for this project. For each data delivery area, reports documenting data collection methodology, accuracy, and quality control were provided by Watershed Sciences and the Oregon Department of Geology and Mineral Industries (DOGAMI). These reports have been combined into single comprehensive reports organized by delivery region. The lidar QC report (the comprehensive report from DOGAMI) and the lidar delivery report (the comprehensive report from Watershed Sciences) can be found at http://dx.doi.org/10.14509/22722. Information about the quadrangles included in individual delivery regions can be found in the lidar delivery index report included with the data download. The DGGS metadata standard extends the FGDC standard to also include several elements that are required to facilitate internal data management. These elements relate individual data items to a common dataset. This dataset describes a single layer titled:\n&gt;ground_points:\tground-classified laser returns from the lidar survey and their associated geospatial coordinates.\n</supplinf>\n</descript>\n<timeperd>\n<timeinfo>\n<rngdates>\n<begdate>2010</begdate>\n<enddate>2011</enddate>\n</rngdates>\n</timeinfo>\n<current>ground condition</current>\n</timeperd>\n<status>\n<progress>Complete</progress>\n<update>As needed</update>\n</status>\n<spdom>\n<bounding>\n<westbc>-150</westbc>\n<eastbc>-147</eastbc>\n<northbc>64</northbc>\n<southbc>63</southbc>\n</bounding>\n</spdom>\n<keywords>\n<theme>\n<themekt>ISO 19115 Topic Category</themekt>\n<themekey>geoscientificInformation</themekey>\n</theme>\n<theme>\n<themekt>Alaska Division of Geological &amp; Geophysical Surveys</themekt>\n<themekey>Alaska Pipeline</themekey>\n<themekey>Gasline</themekey>\n<themekey>Geomorphology</themekey>\n<themekey>Lidar</themekey>\n<themekey>Proposed Natural Gas Pipeline</themekey>\n<themekey>Remote Sensing</themekey>\n<themekey>Point Cloud Data</themekey>\n<themekey>Lidar LAS File Format</themekey>\n</theme>\n<place>\n<placekt>Alaska Division of Geological &amp; Geophysical Surveys</placekt>\n<placekey>Healy Quadrangle</placekey>\n<placekey>Alaska Highway Corridor</placekey>\n<placekey>Alaska, State of</placekey>\n<placekey>Trans-Alaska Pipeline</placekey>\n</place>\n</keywords>\n<accconst>The dataset(s) is (are) available directly from the State of Alaska, Department of Natural Resources, Division of Geological &amp; Geophysical Surveys (see contact information below).</accconst>\n<useconst>Any hard copies or published datasets utilizing these datasets shall clearly indicate their source. If the user has modified the data in any way, the user is obligated to describe the types of modifications the user has made. The user specifically agrees not to misrepresent these datasets, nor to imply that changes made by the user were approved by the State of Alaska, Department of Natural Resources, Division of Geological &amp; Geophysical Surveys. The State of Alaska makes no express or implied warranties (including warranties for merchantability and fitness) with respect to the character, functions, or capabilities of the electronic data or products or their appropriateness for any user&apos;s purposes. In no event will the State of Alaska be liable for any incidental, indirect, special, consequential, or other damages suffered by the user or any other person or entity whether from the use of the electronic services or products or any failure thereof or otherwise. In no event will the State of Alaska&apos;s liability to the Requestor or anyone else exceed the fee paid for the electronic service or product.</useconst>\n<ptcontac>\n<cntinfo>\n<cntorgp>\n<cntorg>Alaska Division of Geological &amp; Geophysical Surveys</cntorg>\n</cntorgp>\n<cntpos>GIS Data Manager/GIS Analyst</cntpos>\n<cntaddr>\n<addrtype>mailing and physical address</addrtype>\n<address>3354 College Rd</address>\n<city>Fairbanks</city>\n<state>AK</state>\n<postal>99709-3707</postal>\n<country>USA</country>\n</cntaddr>\n<cntvoice>907-451-5029</cntvoice>\n<cntvoice>907-451-5020</cntvoice>\n</cntinfo>\n</ptcontac>\n<datacred>Data collection was was supported by funding from the Department of Natural Resources, Division of Geological &amp; Geophysical Surveys (DGGS) and the Alaska Gas Pipeline Project Office and the Office of the Federal Coordinator. Lidar data was collected by Watershed Sciences, Inc., Corvallis, OR, Survey data was collected by McClintock Land Associates, Eagle River, AK, Quality control check for data was done by State of Oregon Department of Geology &amp; Mineral Industries, Portland, OR.</datacred>\n<native>Microsoft Windows XP Version 5.1 (Build 2600) Service Pack 3; ALS Post Processing software v.2.70; Terra Scaan v. 11.009; TerraModeler v.11.004; TerraMatch v. 11.006</native>\n</idinfo>\n<dataqual>\n<attracc>\n<attraccr>Absolute accuracy refers to the mean vertical offset of lidar laser point data relative to measured ground-control points (GCP) obtained throughout the lidar sampling area. The contractor used a surveying system to measure GCP&apos;s. GPS survey techniques allow surveyors to collect many precisely located GCP&apos;s which can be used as a control comparison with lidar elevations. A licensed surveyor is often able to post process GPS survey data to accuracies less than 1 cm both horizontally and vertically. Lidar 1 m grids were loaded into ArcGIS software for visual analysis. Data were examined through slope and hillshade models of bare earth returns. Both bare earth and highest hit models were examined for calibration offsets, tiling artifacts, seam line offsets, pits and birds. Please see the lidar delivery report and the lidar QC report for specific information about laser point processing and accuracy evaluation.</attraccr>\n</attracc>\n<logic>Lidar returns have been examined to ensure that data from overlapping flight lines have consistent elevation values. Project specifications require that lidar consistency, measured as vertical offsets of data between adjacent flight lines, must average less than 0.15 meters. Flight lines have been examined to ensure that there was at least 60% sidelap and that there are no data gaps. All file naming conventions and formats have been checked for consistency. Refer to the lidar QC report and the lidar delivery report for statistics from consistency analyses of individual delivery sets.</logic>\n<complete>All data have been loaded and viewed to ensure completeness. LAS file headers have been scanned to ensure completeness and readability</complete>\n<posacc>\n<horizpa>\n<horizpar>Horizontal accuracy refers to the ability to place laser points from multiple flight lines in the same location. Horizontal accuracy is measured as the divergence between points from overlapping flight lines. Accuracy is affected by system attitude offsets, scale and GPS/IMU drift. Manual system calibration and automated attitude calibration techniques were used to resolve divergence of data. Please see the lidar QC report and lidar delivery report for specific information about accuracy of lidar data.</horizpar>\n</horizpa>\n<vertacc>\n<vertaccr>Vertical accuracy refers to the elevation difference between measured GPS control data and lidar bare-earth digital elevation models. Project specifications require the root mean square vertical offset to be less than 0.2 meters. Please see the lidar QC report and lidar delivery report for specific information about accuracy and quality of lidar data, including a comparison of GCP elevations with bare-earth digital elevation model elevations.</vertaccr>\n</vertacc>\n</posacc>\n<lineage>\n<srcinfo>\n<srccite>\n<citeinfo>\n<origin>The American Society for Photogrammetry &amp; Remote Sensing (ASPRS)</origin>\n<pubdate>02092008</pubdate>\n<title>LAS Specification Version 1.2</title>\n<geoform>document</geoform>\n<onlink>http://www.asprs.org/a/society/committees/standards/asprs_las_format_v12.pdf</onlink>\n</citeinfo>\n</srccite>\n<typesrc>online</typesrc>\n<srctime>\n<timeinfo>\n<sngdate>\n<caldate>02092008</caldate>\n</sngdate>\n</timeinfo>\n<srccurr>publication date</srccurr>\n</srctime>\n<srccitea>ASPRS, 2008</srccitea>\n<srccontr>point classification categories</srccontr>\n</srcinfo>\n<procstep>\n<procdesc>Acquisition: The lidar data were collected between September and October 2010 and between May and July 2011. The survey used the Leica ALS60 system. Near-nadir scan angles were used to increase penetration of vegetation to ground surfaces. Ground-level GPS and aircraft IMU were collected during the flight.</procdesc>\n<procdate>2010 and 2011</procdate>\n</procstep>\n<procstep>\n<procdesc>Processing lidar data: (1) Flight lines and data were reviewed to ensure complete coverage of the study area and positional accuracy of the laser points. (2) Laser point-return coordinates were computed using ALS Post Processor software, IPAS Pro GPS/INS software, and Waypoint GPS, based on independent data from the lidar system, IMU, and aircraft. (3) The raw lidar file was assembled into flight lines per return with each point having an associated x, y, and z coordinate. (4) Visual inspection of swath-to-swath laser point consistencies in the study area were used to perform manual refinements of system alignment. (5) Custom algorithms were designed to evaluate points between adjacent flight lines. Automated system alignment was computed based on randomly selected swath-to-swath accuracy measurements that consider elevation, slope, and intensities. Specifically, refinement in the combination of system pitch, roll, and yaw-offset parameters optimize internal consistency. (6) Noise (e.g., pits and birds) was filtered using ALS post-processing software, based on known elevation ranges, and included the removal of any cycle slips.</procdesc>\n<procdate>2010, 2011, 2012</procdate>\n</procstep>\n<procstep>\n<procdesc>Lidar data points were classified through automated point processing algorithms and manual inspection. See the lidar delivery report for details regarding classification of lidar data points.</procdesc>\n<srcused>ASPRS, 2008</srcused>\n<procdate>2010, 2011, 2012</procdate>\n</procstep>\n<procstep>\n<procdesc>Lidar data points that were classified as &quot;ground&quot; were extracted to create the ground point data file.</procdesc>\n<procdate>2010, 2011, 2012</procdate>\n</procstep>\n<procstep>\n<procdesc>A metadata file has been written to document and describe, as a whole, all of the ground point files generated for this project.</procdesc>\n<procdate>2012</procdate>\n</procstep>\n</lineage>\n</dataqual>\n<spdoinfo>\n<direct>Raster</direct>\n<rastinfo>\n<rasttype>Pixel</rasttype>\n</rastinfo>\n</spdoinfo>\n<spref>\n<horizsys>\n<planar>\n<gridsys>\n<gridsysn>Universal Transverse Mercator</gridsysn>\n<utm>\n<utmzone>6</utmzone>\n<transmer>\n<sfctrmer>0.999600</sfctrmer>\n<longcm>-147</longcm>\n<latprjo>0.000000</latprjo>\n<feast>500000.000000</feast>\n<fnorth>0.000000</fnorth>\n</transmer>\n</utm>\n</gridsys>\n<planci>\n<plance>row and column</plance>\n<coordrep>\n<absres>2.83</absres>\n<ordres>2.83</ordres>\n</coordrep>\n<plandu>meters</plandu>\n<pclname>ground_points</pclname>\n</planci>\n</planar>\n<geodetic>\n<horizdn>North American Datum of 1983</horizdn>\n<ellips>Geodetic Reference System 80</ellips>\n<semiaxis>6378137</semiaxis>\n<denflat>298.257222</denflat>\n</geodetic>\n</horizsys>\n<vertdef>\n<altsys>\n<altdatum>North American Vertical Datum of 1988</altdatum>\n<altres>.000001</altres>\n<altunits>meters</altunits>\n<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>\n</altsys>\n</vertdef>\n</spref>\n<eainfo>\n<detailed>\n<enttyp>\n<enttypl>LAS</enttypl>\n<enttypd>LAS v. 1.2</enttypd>\n<enttypds>this report</enttypds>\n<ealname>ground_points</ealname>\n</enttyp>\n<attr>\n<attrlabl>Class</attrlabl>\n<attrdef>Number used to identify the type of return</attrdef>\n<attrdefs>Watershed Sciences, Inc.</attrdefs>\n<attrdomv>\n<edom>\n<edomv>2</edomv>\n<edomvd>Ground</edomvd>\n<edomvds>ASPRS</edomvds>\n</edom>\n</attrdomv>\n</attr>\n</detailed>\n<overview>\n<eaover>Attributes include point classification (as outlined above) as well as additional attributes described in the ASPRS document. These attributes include: Flight Line Edge, GPS Time, Return Number, X, Y, Elevation, Intensity, Scan Angle Rank, Point Number, Number of Returns, Scan Direction Flag, V.1.1 Synthetic Pt, V.1.1 Key-point, V.1.1 Withheld, User data and Point Source ID.</eaover>\n<eadetcit>ASPRS</eadetcit>\n<eadetcit>Watershed Sciences, Inc.</eadetcit>\n</overview>\n</eainfo>\n<distinfo>\n<distrib>\n<cntinfo>\n<cntorgp>\n<cntorg>Alaska Division of Geological &amp; Geophysical Surveys</cntorg>\n</cntorgp>\n<cntaddr>\n<addrtype>mailing and physical</addrtype>\n<address>3354 College Road</address>\n<city>Fairbanks</city>\n<state>AK</state>\n<postal>99709-3707</postal>\n<country>USA</country>\n</cntaddr>\n<cntvoice>907 451-5010</cntvoice>\n<cntfax>907-451-5050</cntfax>\n<cntemail>dggspubs@alaska.gov</cntemail>\n<hours>8 am to 4:30 pm, Monday through Friday, except State holidays</hours>\n<cntinst>Please view our website (http://www.dggs.alaska.gov) for the latest information on available data. Please contact us using the e-mail address provided above when possible.</cntinst>\n</cntinfo>\n</distrib>\n<resdesc>RDF 2011-3</resdesc>\n<distliab>The State of Alaska makes no express or implied warranties (including warranties of merchantability and fitness) with respect to the character, function, or capabilities of the electronic services or products or their appropriateness for any user&apos;s purposes. In no event will the State of Alaska be liable for any incidental, indirect, special, consequential, or other damages suffered by the user or any other person or entity whether from the use of the electronic services or products, any failure thereof, or otherwise, and in no event will the State of Alaska&apos;s liability to the requester or anyone else exceed the fee paid for the electronic service or product.</distliab>\n<stdorder>\n<digform>\n<digtinfo>\n<formname>LAS</formname>\n<formvern>v.1.2</formvern>\n</digtinfo>\n<digtopt>\n<offoptn>\n<offmedia>Hard Drive</offmedia>\n<recfmt>HDD</recfmt>\n</offoptn>\n</digtopt>\n</digform>\n<fees>You will be charged $56 per hour (11 AAC 05.010) for data processing for any staff time in excess of one hour.</fees>\n</stdorder>\n<custom>DGGS is developing options to make the data available to users directly from the internet; however, it is currently only available via hard drive. There are two options for copying the data to a hard drive: (1) DGGS will purchase a brand-new, 2 TB hard drive that you will be billed for when the data is picked up or sent, OR (2) you may provide a new, unopened* (in original packaging, including shrink-wrap - *The State of Alaska IT security policy prohibits non-State resources from being connected to a State of Alaska network. Thus, only unused drives can be used.) 2 TB or larger hard drive. Upon release, the complete set of point-cloud data will be available to users in LAS 1.2 format. The point-cloud files total approximately 1.2 TB. The data will be copied onto the drive in gzip (gz) file format. DGGS recommends uncompressing this data using 7-Zip, a free program available from http://www.7zip.org. For all orders, please include: title and publication number.</custom>\n</distinfo>\n<metainfo>\n<metd>20120320</metd>\n<metc>\n<cntinfo>\n<cntperp>\n<cntper>Metadata manager</cntper>\n</cntperp>\n<cntaddr>\n<addrtype>mailing and physical</addrtype>\n<address>State of Alaska, Department of Natural Resources, Division of Geological &amp; Geophysical Surveys</address>\n<city>Fairbanks</city>\n<state>AK</state>\n<postal>99709-3707</postal>\n<country>USA</country>\n</cntaddr>\n<cntvoice>907-451-5020</cntvoice>\n</cntinfo>\n</metc>\n<metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>\n<metstdv>FGDC-STD-001-1998</metstdv>\n<metuc>If the user has modified this metadata file in any way, the user is obligated to describe the types of modifications the user has made. User specifically agrees not to misrepresent this metadata file, nor to imply that changes made by the user were approved by the State of Alaska, Department of Natural Resources, Division of Geological &amp; Geophysical Surveys.</metuc>\n<metextns>\n<onlink>http://www.dggs.alaska.gov/metadata/dggs.ext</onlink>\n<metprof>dggs metadata extensions</metprof>\n</metextns>\n</metainfo>\n</metadata>\n","source_transform":null,"status":"error"}
