Internal Storage

In collaboration with the KIT, the binary xyz data is being stored in a repository of simple ASCII.txt files. From here data can be uploaded and downloaded by the members within the joint research project.

Future output will be stored in a collective repository in order for data to be studied by a wide array of people and fields of interest.

primary site information

primary site information

All data will be hosted by the KIT server, and the xyz data by the Irods repository.

Data will be managed, handled and processed in standardised procedures in order to build sustainable data life cycles.

Metadata scheme for LiDAR data will be developed and adapted accordingly to the ISO 19115 standard and the Federal Geographic Data Commitee:

Lidar Metadata Example
<?xml version=”1.0” encoding=”UTF-8”?>
<!–DOCTYPE metadata SYSTEM “fgdc-std-001-1998.dtd”–>
<metadata>
<idinfo>
<citation>
<citeinfo>
<origin>We Map 4U, Inc.</origin>
<pubdate>20101208</pubdate>
<title>Lidar data for Phelps and Dent Counties, MO
MO_Phelps-Dent-CO_2010
</title>
<geoform>Lidar point cloud</geoform>
</citeinfo>
</citation>
<descript>
<abstract>Geographic Extent: This dataset is lidar point cloud
data, which encompasses a 1,000 meter buffer around Phelps and Dent Counties
in Missouri, approximatly 829 square miles.
Dataset Description: This dataset consists of 457 lidar point cloud .LAS
swath files. Each .LAS file contains lidar point information, which has been
calibrated, controlled, and classified. Each file represents a separate
swath of lidar. Collected swath files that were larger than 2GB were
initially written in multiple sub-swath files, each less than 2GB.
Ground Conditions: water at normal levels; no unusual innundation; no snow;
leaf off
</abstract>
<lidar>
<ldrinfo>
<ldrspec>USGS NGP Base Specification v1</ldrspec>
<ldrsens>Optech Gemini Airborne Laser Terrain Mappers (ALTM)</ldrsens>
<ldrmaxnr>4</ldrmaxnr>
<ldrnps>0.7071</ldrnps>
<ldrdens>2</ldrdens>
<ldrfltht>3000</ldrfltht>
<ldrfltsp>115</ldrfltsp>
<ldrscana>26</ldrscana>
<ldrscanr>40</ldrscanr>
<ldrpulsr>120</ldrpulsr>
<ldrpulsd>10</ldrpulsd>
<ldrpulsw>3</ldrpulsw>
<ldrwavel>1064</ldrwavel>
<ldrmpia>0</ldrmpia>
<ldrbmdiv>4.5</ldrbmdiv>
<ldrswatw>1200</ldrswatw>
<ldrswato>15</ldrswato>
<ldrcrs> NAD_1983_UTM_Zone_15N_Meters</ldrcrs>
<ldrgeoid>National Geodetic Survey (NGS) Geoid09</ldrgeoid>
</ldrinfo>
<ldraccur>
<ldrchacc>0.5</ldrchacc>
<rawfva>0.11</rawfva>
<clsfva>0.09</clsfva>
<clscva>0.188</clscva>
<clssvas>
<svalctyp>Forest</svalctyp>
<svavalue>0.38</svavalue>
</clssvas>
<clssvas>
<svalctyp>Agriculture</svalctyp>
<svavalue>0.21</svavalue>
Appendix 4. Lidar Metadata Example 29
</clssvas>
<clssvas>
<svalctyp>Pasture/Meadow</svalctyp>
<svavalue>0.15</svavalue>
</clssvas>
<clssvas>
<svalctyp>Scrub/Shrub</svalctyp>
<svavalue>0.11</svavalue>
</clssvas>
</ldraccur>
<lasinfo>
<lasver>1.3</lasver>
<lasprf>6</lasprf>
<laswheld>Withheld (ignore) points were identifed in these files using the
standard LAS Withheld bit
</laswheld>
<lasolap> Swath “overage” points were identified in these files by adding
16 to the standard classification values.
</lasolap>
<lasintrz>11-bit</lasintrz>
<lasclass>
<clascode>0</clascode>
<clasitem>Never Processed</clasitem>
</lasclass>
<lasclass>
<clascode>1</clascode>
<clasitem>Undetermined/Unclassified</clasitem>
</lasclass>
<lasclass>
<clascode>2</clascode>
<clasitem>Bare-earth</clasitem>
</lasclass>
<lasclass>
<clascode>4</clascode>
<clasitem>All vegetation</clasitem>
</lasclass>
<lasclass>
<clascode>6</clascode>
<clasitem>All structures except bridges</clasitem>
</lasclass>
<lasclass>
<clascode>7</clascode>
<clasitem>All noise</clasitem>
</lasclass>
<lasclass>
<clascode>8</clascode>
<clasitem>Bare-earth Key Points</clasitem>
</lasclass>
<lasclass>
<clascode>9</clascode>
<clasitem>Water</clasitem>
</lasclass>
<lasclass>
<clascode>10</clascode>
<clasitem>Bridges</clasitem>
</lasclass>
</lasinfo>
</lidar>
<purpose>The purpose of these LiDAR data was to produce a high accuracy 3D
hydro-flattened Digital Elevation Model (DEM) with a 1.0 foot cell size.
The data will be used by Federal Emergency Management Agency (FEMA) for
floodplain mapping.
30 Lidar Base Specification Version 1.0
These raw lidar point cloud data were used to create classified lidar LAS files,
intensity images, 3D breaklines, hydro-flattened DEMs as necessary.
</purpose>
<supplinf>
USGS Contract No. G10PC01234
CONTRACTOR: We Map4U, Inc.
SUBCONTRACTOR: Aerial Scanning Services, LLC
Lidar data were acquired and calibrated by Aerial Scanning Services.
All follow-on processing was completed by the prime contractor.
</supplinf>
</descript>
<timeperd>
<timeinfo>
<rngdates>
<begdate>20100216</begdate>
<enddate>20100218</enddate>
</rngdates>
</timeinfo>
<current>ground condition</current>
</timeperd>
<status>
<progress>Partial: Lot 2 of 5</progress>
<update>None planned</update>
</status>
<spdom>
<bounding>
<westbc>-91.750000</westbc>
<eastbc>-91.250000</eastbc>
<northbc>38.000000</northbc>
<southbc>37.250000</southbc>
</bounding>
<lboundng>
<leftbc>584800.00</leftbc>
<rightbc>664800.00</rightbc>
<topbc>4225400.00</topbc>
<bottombc>4141400.00</bottombc>
</lboundng>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>Elevation data</themekey>
<themekey>Lidar</themekey>
<themekey>Hydrology</themekey>
</theme>
<place>
<placekt>None</placekt>
<placekey>Missouri</placekey>
<placekey>Phelps County</placekey>
<placekey>Dent County</placekey>
<placekey>Mark Twain National Forest</placekey>
</place>
</keywords>
<accconst>No restrictions apply to this data.</accconst>
<useconst>None. However, users should be aware that temporal changes may have occurred
since this dataset was collected and that some parts of these data may no longer
represent actual surface conditions. Users should not use these data for critical
applications without a full awareness of its limitations. Acknowledgement of the U.S.
Geological Survey would be appreciated for products derived from these data.
</useconst>
<ptcontac>
<cntinfo>
Appendix 4. Lidar Metadata Example 31
<cntorgp>
<cntorg>We Map 4U, Data Acquisition Department</cntorg>
<cntper>Jane Smith</cntper>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>123 Main St.</address>
<city>Anytown</city>
<state>MO</state>
<postal>61234</postal>
<country>USA</country>
</cntaddr>
<cntvoice>555-555-1234</cntvoice>
<cnttdd>555-555-1122</cnttdd>
<cntfax>555-5550-1235</cntfax>
<cntemail>jsmith@wemap4u.com</cntemail>
<hours>Monday through Friday 8:00 AM to 4:00 PM (Central Time)</hours>
<cntinst>If unable to reach the contact by telephone, please send an email.
You should get a response within 24 hours.
</cntinst>
</cntinfo>
</ptcontac>
<native>Optech DASHMap 4.2200; ALS Post Processor 2.70 Build#15;
GeoCue Version 6.1.21.4; Windows XP Operating System
\\server\directory path\*.LAS
17 GB
</native>
</idinfo>
<dataqual>
<logic>Data cover the entire area specified for this project.</logic>
<complete>These raw LAS data files include all data points collected.
No points have been removed or excluded.
A visual qualitative assessment was performed to ensure data completeness.
There are no void areas or missing data. The raw point cloud is of good
quality and data passes Fundamental Vertical Accuracy specifications.
</complete>
<posacc>
<vertacc>
<vertaccr>The specifications require that only Fundamental Vertical Accuracy (FVA)
be computed for raw lidarpoint cloud swath files. The vertical accuracy
was tested with 25 independent survey located in open terrain. These
check points were not used in the calibration or post processing of the
lidar point cloud data. The survey checkpoints were distributed
throughout the project area. Specifications for this project require
that the FVA be 25 cm or better AccuracyZ at 95 percent confidence level.
</vertaccr>
<qvertpa>
<vertaccv>0.19 meters AccuracyZ at 95 percent Confidence Interval</vertaccv>
<vertacce>The FVA was tested using 25 independent survey located in open terrain
terrain. The survey checkpoints were distributed throughout the project area.
The 25 independant check points were surveyed using xxxx technique. Elevations
from the unclassified lidar surface were measured for the x,y location of each
check point. Elevations interpolated from the lidar surface were then compared
to the elevation values of the surveyed control. The RMSE was computed to be
0.097cm.
AccuracyZ has been tested to meet 9.7 cm Fundamental Vertical Accuracy at 95
Percent confidence level using RMSE(z) x 1.9600 as defined by the National
Standards for Spatial Data Accuracy (NSSDA); assessed and reported using
National Digital Elevation Program (NDEP)/ASPRS Guidelines.
</vertacce>
</qvertpa>
</vertacc>
32 Lidar Base Specification Version 1.0
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>Jiffy Survey, Inc</origin>
<pubdate> 20100115</pubdate>
<title>Ground Control for Phelps and Dent County, MO lidar project</title>
<geoform>vector digital data and tabular data</geoform>
<pubinfo>
<pubplace>Jiffy Survey, Inc.</pubplace>
<publish>Jiffy Survey, Inc., GPS department</publish>
</pubinfo>
<othercit>None</othercit>
<onlink>ftp://JiffySurveyftp.com/data/outgoing/Task1/</onlink>
</citeinfo>
</srccite>
<srcscale>50</srcscale>
<typesrc>CD-ROM</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate> 201001003</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>Phelps_Co_lidar_gnd_ctrl</srccitea>
<srccontr>This data source was used (along with the airborne GPS/IMU data)
to georeference the lidar point cloud data.
</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>USDA</origin>
<pubdate> 20090606</pubdate>
<title>NAIP Imagery for Phelps and Dent County, MO lidar project</title>
<geoform>raster orthoimagery</geoform>
<pubinfo>
<pubplace>USGS-EROS</pubplace>
<publish>USGS-EROS</publish>
</pubinfo>
<othercit>None</othercit>
<onlink></onlink>
</citeinfo>
</srccite>
<srcscale>50</srcscale>
<typesrc>online</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>20090101</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>Phelps-Dent_Co_NAIP_Imagery</srccitea>
<srccontr>This data source was used (along with the lidar intensity imagery)
to classify the lidar point cloud data.
</srccontr>
</srcinfo>
Appendix 4. Lidar Metadata Example 33
<srcinfo>
<srccite>
<citeinfo>
<origin>We Map 4U, Inc.</origin>
<pubdate>20101208</pubdate>
<title>Lidar Intensity Imagery for Phelps and Dent County, MO</title>
<geoform>raster orthoimagery</geoform>
<pubinfo>
<pubplace>USGS-EROS</pubplace>
<publish>USGS-EROS</publish>
</pubinfo>
<othercit>None</othercit>
<onlink></onlink>
</citeinfo>
</srccite>
<srcscale>50</srcscale>
<typesrc>online</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>20100216</begdate>
<enddate>20100218</enddate>
</rngdates>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>Phelps-Dent_Co_Lidar_Intensity_Imagery</srccitea>
<srccontr>This data source was used (along with NAIP imagery)
to classify the lidar point cloud data.
</srccontr>
</srcinfo>
<procstep>
<procdesc>Lidar Pre-Processing: Airborne GPS and IMU data were merged to develop
a Single Best Estimate (SBET) of the lidar system trajectory for each lift.
Lidar ranging data were initially calibrated using previous best parameters
for this instrument and aircraft. Relative calibration was evaluated using
advanced plane-matching analysis and parameter corrections derived. This
was repeated iteratively until residual errors between overlapping swaths,
across all project lifts, was reduced to 2cm or less. Data were then block
adjusted to match surveyed calibration control. Raw data FVA were checked
using independently surveyed checkpoints. Swath overage points were identified
and tagged within each swath file. The results of the final calibration, FVA
and horizontal accuracy assessments, and the “raw” swaths were forwarded
to the client to obtain a Notice To Proceed on classification and derivative
product generation.
</procdesc>
<srcused>Phelps_Co_lidar_gnd_ctrl</srcused>
<procdate>20100131</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>We Map 4U, Data Acquisition Department</cntorg>
<cntper>Manny Puntas</cntper>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>123 Main St.</address>
<city>Anytown</city>
<state>MO</state>
<postal>61234</postal>
<country>USA</country>
</cntaddr>
34 Lidar Base Specification Version 1.0
<cntvoice>555-555-556</cntvoice>
<cntfax>555-5550-1236</cntfax>
<cntemail>mpuntas@wemap4u.com</cntemail>
<hours>Monday through Friday 8:00 AM to 4:00 PM (Central Time)</hours>
<cntinst>If unable to reach the contact by telephone, please send an email.
You should get a response within 24 hours.
</cntinst>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>Lidar Post-Processing: The calibrated and controlled lidar
swaths were processed using automatic point classification routines
in proprietary software. These routines operate against the entire
collection (all swaths, all lifts), eliminating character differences
between files. Data were then distributed as virtual tiles to experienced
lidar analysts for localized automatic classification, manual editing,
and peer-based QC checks. Supervisory QC monitoring of work in progress
and completed editing ensured consistency of classification character and
adherence to project requirements across the entire project area.
All classification tags are stored in the original swath files.
After completion of classification and final QC approval, the FVA,
SVAs, and CVA for the project are calculated. Sample areas for each
Land cover type present in the project area was extracted and forwarded
to the client, along with the results of the accuracy tests. Upon acceptance,
the complete classified lidar swath files were delivered to the client.
</procdesc>
<srcused>Phelps-Dent_Co_NAIP_Imagery</srcused>
<srcused>Phelps-Dent_Co_Lidar_Intensity_Imagery</srcused>
<procdate>20100530</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>We Map 4U, Data Acquisition Department</cntorg>
<cntper>Manny Puntas</cntper>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>123 Main St.</address>
<city>Anytown</city>
<state>MO</state>
<postal>61234</postal>
<country>USA</country>
</cntaddr>
<cntvoice>555-555-556</cntvoice>
<cntfax>555-5550-1236</cntfax>
<cntemail>mpuntas@wemap4u.com</cntemail>
<hours>Monday through Friday 8:00 AM to 4:00 PM (Central Time)</hours>
<cntinst>If unable to reach the contact by telephone, please send an email.
You should get a response within 24 hours.
</cntinst>
</cntinfo>
</proccont>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct>Vector</direct>
<ptvctinf>
<sdtsterm>
<sdtstype>Point</sdtstype>
<ptvctcnt>764,567,423</ptvctcnt>
Appendix 4. Lidar Metadata Example 35
</sdtsterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<planar>
<gridsys>
<gridsysn>Universal Transverse Mercator</gridsysn>
<utm>
<utmzone>15</utmzone>
<transmer>
<sfctrmer>0.9996</sfctrmer>
<longcm>-117.000000</longcm>
<latprjo>0.0</latprjo>
<feast>500000</feast>
<fnorth>0.0</fnorth>
</transmer>
</utm>
</gridsys>
<planci>
<plance>coordinate pair</plance>
<coordrep>
<absres>0.01</absres>
<ordres>0.01</ordres>
</coordrep>
<plandu>meters</plandu>
</planci>
</planar>
<geodetic>
<horizdn>North American Datum of 1983</horizdn>
<ellips>Geodetic Reference System 80</ellips>
<semiaxis>6378137</semiaxis>
<denflat>298.257222101</denflat>
</geodetic>
</horizsys>
<vertdef>
<altsys>
<altdatum>North American Vertical Datum of 1988</altdatum>
<altres> 0.01</altres>
<altunits>meters</altunits>
<altenc>Explicit elevation coordinate included with horizontal coordinates</altenc>
</altsys>
</vertdef>
</spref>
<distinfo>
<distrib>
<cntinfo>
<cntperp>
<cntper>Jim Brooks, GISP</cntper>
<cntorg>Phelps-Dent Council of Government (PDCOG), GIS and Data Division</cntorg>
</cntperp>
<cntpos>Director</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>PDCOG, GIS Division</address>
<address>123 ABD Street</address>
<address> Suite 456</address>
<city>Sometown</city>
<state>MO</state>
<postal>99999</postal>
<country>USA</country>
</cntaddr>
36 Lidar Base Specification Version 1.0
<cntvoice>555-555-9999</cntvoice>
<cntemail>jim.brooks@PDCOG.org</cntemail>
</cntinfo>
</distrib>
<resdesc>The Phelps-Dent Council of Government (PDCOG)distributes data
directly to program partners.
Public access to the data is available from the USGS as listed below.
</resdesc>
<distliab>In no event shall the creators, custodians, or distributors of these
data be liable for any damages arising out of its use, or from the inability
of the customer to use these data for their intended application.
</distliab>
</distinfo>
<metainfo>
<metd> 20101206</metd>
<metrd> 20101207</metrd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>We Map 4U, Data Acquisition Department</cntorg>
<cntper>John Smith</cntper>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>123 Main St.</address>
<city>Anytown</city>
<state>MO</state>
<postal>61234</postal>
<country>USA</country>
</cntaddr>
<cntvoice>555-555-1234</cntvoice>
<cnttdd>555-555-1122</cnttdd>
<cntfax>555-5550-1235</cntfax>
<cntemail>jsmith@wemap4u.com</cntemail>
<hours>Monday through Friday 8:00 AM to 4:00 PM (Central Time)</hours>
<cntinst> If unable to reach the contact by telephone, please send an email.
You should get a response within 24 hours.
</cntinst>
</cntinfo>
</metc>
<metstdn>FGDC Content Standard for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
<metac>None</metac>
<metuc>None</metuc>
<metsi>
<metscs>None</metscs>
<metsc>Unclassified</metsc>
<metshd>None</metshd>
</metsi>
<metextns>
<onlink>None</onlink>
<metprof>None</metprof>
</metextns>
</metainfo>
</metadata>
Appendix 5. Lidar Metadata Template 37
Appendix 5. Lidar Metadata Template
<?xml version=”1.0” encoding=”UTF-8”?>
<!–DOCTYPE metadata SYSTEM “fgdc-std-001-1998.dtd”–>
<metadata>
<idinfo>
<citation>
<citeinfo>
<origin> EXAMPLE: We Map 4U, Inc.
<!–REQUIRED Element: Originator
Name of the contractor that developed the dataset.
Domain: “Unknown” free text
–>
</origin>
<pubdate> 20101208
<!–REQUIRED Element: Publication Date
Date that the dataset was RELEASED. The field MUST be formatted YYYYMMDD
Domain: “Unknown” “Unpublished Material” YYYYMMDD free text
–>
</pubdate>
<title> EXAMPLE: Lidar data for Phelps and Dent Counties, MO
MO_Phelps-Dent-CO_2010
<!–REQUIRED Element: Title
The name by which the dataset is known.
If a Project ID in the following format has been issued for this project,
include it in the title element [State_description_aquisition-date].
Domain: free text
–>
</title>
<geoform> EXAMPLE: Lidar point cloud
<!–REQUIRED Element: Geospatial Data Presentation Form
The mode in which the geospatial data are represented.
Domain: free text
–>
</geoform>
</citeinfo>
</citation>
<descript>
<abstract> EXAMPLE: Geographic Extent: This dataset is lidar point cloud
data, which encompasses a 1,000 meter buffer around Phelps and Dent Counties
in Missouri, approximatly 829 square miles.
Dataset Description: This dataset consists of 457 lidar point cloud .LAS
swath files. Each .LAS file contains lidar point information, which has been
calibrated, controlled, and classified. Each file represents a separate
swath of lidar. Collected swath files that were larger than 2GB were
initially written in multiple sub-swath files, each less than 2GB.
Ground Conditions: water at normal levels; no unusual innundation; no snow; leaf
off
<!–REQUIRED Element: Abstract
A brief narrative summary of the dataset.
It is desireable for the Abstract to include a consolidated summary other
elements that are included elsewhere in this metadata file, for ease of use.
Domain: free text
–>
</abstract>
<lidar>
<!– REQUIRED Section: for Project, Swath, and Classified LAS metadata files –>
<ldrinfo>
<!–REQUIRED Group: This group of tags contains metadata about the sesnor and
collection conditions.
–>
38 Lidar Base Specification Version 1.0
<ldrspec>EXAMPLE: USGS-NGP Base Lidar Specification v1.0
<!–REQUIRED Element: the lidar specification applicable to the point cloud
–>
</ldrspec>
<ldrsens>EXAMPLE: Optech Gemini Airborne Laser Terrain Mappers (ALTM)
<!–REQUIRED Element: the lidar sensor make and model –>
</ldrsens>
<ldrmaxnr>EXAMPLE: 4
<!–REQUIRED Element: the maximum number of returns per pulse –>
</ldrmaxnr>
<ldrnps>EXAMPLE: 1.2
<!–REQUIRED Element: the Nominal Pulse Spacing, in Meters –>
</ldrnps>
<ldrdens>EXAMPLE: 2
<!–REQUIRED Element: the Nominal Pulse Spacing, in Points Per Square Meter
–>
</ldrdens>
<ldrfltht>EXAMPLE: 3000
<!–REQUIRED Element: the nominal flight height for the collection, in Meters
–>
</ldrfltht>
<ldrfltsp>EXAMPLE: 115
<!–REQUIRED Element: the nominal flight speed for the collection, in Knots
–>
</ldrfltsp>
<ldrscana>EXAMPLE: 26
<!–REQUIRED Element: the sensor scan angle, total, in Degrees –>
</ldrscana>
<ldrscanr>EXAMPLE: 40
<!–REQUIRED Element: the scan frequency of the scanner, in Hertz –>
</ldrscanr>
<ldrpulsr>EXAMPLE: 120
<!–REQUIRED Element: the pulse rate of the scanner, in Kilohertz –>
</ldrpulsr>
<ldrpulsd>EXAMPLE: 10
<!–REQUIRED Element: the pulse duration of the scanner, in Naonseconds –>
</ldrpulsd>
<ldrpulsw>EXAMPLE: 3
<!–REQUIRED Element: the pulse width of the scanner, in Meters –>
</ldrpulsw>
<ldrwavel>EXAMPLE: 1064
<!–REQUIRED Element: the central wavelength of the sensor laser, in
Nanometers
–>
</ldrwavel>
<ldrmpia>EXAMPLE: 0
<!–REQUIRED Element: Whether the sensor was operated with Multiple Pulses In
The Air, 0=No; 1=Y
–>
</ldrmpia >
<ldrbmdiv>EXAMPLE: 0.3
<!–REQUIRED Element: the beam divergence, in Milliradians –>
</ldrbmdiv>
<ldrswatw>EXAMPLE: 1200
<!–REQUIRED Element: the nominal swath width on the ground, in Meters –>
</ldrswatw>
<ldrswato>EXAMPLE: 15
<!–REQUIRED Element: the nominal swath overlap, as a Percentage –>
</ldrswato>
<ldrcrs> EXAMPLE: NAD_1983_UTM_Zone_15N_Meters
<!–REQUIRED Element: This is the Horizontal Coordinate Reference System for
the data.
Appendix 5. Lidar Metadata Template 39
Details for the desired format are below.
Go to the website: http://spatialreference.org/ref/
Search for your CRS, then select the name that reflects your CRS,
Select ESRI WKT
Use the name that is within the first set of quotation marks.
This name should consist of datum, coordinate system, and sometimes units
all separated by underscores instead of spaces.
When units are not already present, the units must be appended to the end
of the string: “_Meters”, “_Feet_US”, “_Feet_Intl”
–>
</ldrcrs>
<ldrgeoid>EXAMPLE: National Geodetic Survey (NGS) Geoid09
<!–REQUIRED Element: Geoid used for vertical reference. –>
</ldrgeoid>
</ldrinfo>
<ldraccur>
<!– REQUIRED Group: This group of tags contains information on point cloud
accuracy. Not all tags within this group are mandatory.
The FVA of the raw point cloud is required. CVA and SVA values for the
classified point cloud are optional,but are required to be reported if they
are available.
ALL Values are reported in METERS.
–>
<ldrchacc>EXAMPLE: 0.5
<!–REQUIRED Element: the calculated horizontal accuracy of the point cloud data
–>
</ldrchacc>
<rawfva>EXAMPLE: 0.11
<!–REQUIRED Element: the calculated fundamental vertical accuracy of the raw
point cloud data
–>
</rawfva>
<clsfva>EXAMPLE: 0.09
<!–OPTIONAL Element: the calculated fundamental vertical accuracy of the
classified point cloud data (required if available)
–>
</clsfva>
<clscva>EXAMPLE: 0.188
<!–OPTIONAL Element: the calculated consolidated vertical accuracy of the
classified point cloud data (required if available)
–>
</clscva>
<clssvas>
<!–OPTIONAL Group for Raw swath points, REQUIRED Group for Classified LAS
Tiles: Each land cover besides open ground will have a Supplemental
Vertical Accuracy.
The two tags under <clssvas> document the land cover type and the SVA value
(Forest, in this case)
This clssvas group will be repeated for each land cover class
–>
<svalctyp>EXAMPLE: Forest</svalctyp>
<svavalue>EXAMPLE: 0.38</svavalue>
</clssvas>
<clssvas>
<svalctyp>EXAMPLE: Agriculture</svalctyp>
<svavalue>EXAMPLE: 0.21</svavalue>
</clssvas>
<clssvas>
<svalctyp>EXAMPLE:Pasture/Meadow</svalctyp>
<svavalue>EXAMPLE: 0.15</svavalue>
</clssvas>
<clssvas>
40 Lidar Base Specification Version 1.0
<svalctyp>EXAMPLE: Scrub/Shrub</svalctyp>
<svavalue>EXAMPLE: 0.11</svavalue>
</clssvas>
<clssvas>
<svalctyp>EXAMPLE: Urban</svalctyp>
<svavalue>EXAMPLE: 0.13</svavalue>
</clssvas>
</ldraccur>
<lasinfo>
<!– REQUIRED Group: This group of tags contains information on the LAS version
and classification values for the point cloud.
–>
<lasver>EXAMPLE: 1.3
<!– REQUIRED Element: The version of the LAS Standard applicable to this data
set.
–>
</lasver>
<lasprf>EXAMPLE: 6
<!– REQUIRED Element: The Point Data Record Format used for the point cloud.
–>
</lasprf>
<laswheld>EXAMPLE: Withheld (ignore) points were identifed in these files using
the standard LAS Withheld bit.
<!– REQUIRED Element: Describe how withheld points are identified.–>
</laswheld>
<lasolap>EXAMPLE: Swath “overage” points were identified in these files by
adding 16 to the standard classification values.
<!– REQUIRED Element: This describes how overage points are identified.–>
</lasolap>
<lasintr>EXAMPLE: 11
<!– REQUIRED Element: This specifies the radiometric resolution of intensity
values, in Bits.
–>
</lasintr>
<lasclass>
<!– REQUIRED Section if LAS data are classified: Each lasclass section
provides a code value and a description for that code.
–>
<clascode>EXAMPLE: 0</clascode>
<clasitem>EXAMPLE: Never Processed</clasitem>
</lasclass>
<lasclass>
<clascode>EXAMPLE: 1</clascode>
<clasitem>EXAMPLE: Undetermined/Unclassified</clasitem>
</lasclass>
<lasclass>
<clascode>EXAMPLE: 2</clascode>
<clasitem>EXAMPLE: Bare-earth</clasitem>
</lasclass>
<lasclass>
<clascode>EXAMPLE: 4</clascode>
<clasitem>EXAMPLE: All vegetation</clasitem>
</lasclass>
<lasclass>
<clascode>EXAMPLE: 6</clascode>
<clasitem>EXAMPLE: All structures except bridges</clasitem>
</lasclass>
<lasclass>
<clascode>EXAMPLE: 7</clascode>
<clasitem>EXAMPLE: All noise</clasitem>
</lasclass>
<lasclass>
Appendix 5. Lidar Metadata Template 41
<clascode>EXAMPLE: 8</clascode>
<clasitem>EXAMPLE: Bare-earth Key Points</clasitem>
</lasclass>
<lasclass>
<clascode>EXAMPLE: 9</clascode>
<clasitem>EXAMPLE: Water</clasitem>
</lasclass>
<lasclass>
<clascode>EXAMPLE: 10</clascode>
<clasitem>EXAMPLE: Bridges</clasitem>
</lasclass>
</lasinfo>
</lidar>
<purpose>The purpose of these lidar data was to produce high accuracy 3D
hydro-flattened Digital Elevation Model (DEM) with a 1.0 foot cell size.
The data will be used by FEMA for flood-plain mapping.
These raw lidar point cloud data were used to create classified lidar LAS files,
intensity images, 3D breaklines, hydro-flattened DEMs as necessary.
<!–REQUIRED Element: Purpose
Why was the dataset was created? For what applications?
What other products this dataset will be used to create: tiled classified LAS,
DEM, and others, required deliverables, or interim products necessary to
complete the project. What scales are appropriate or inappropriate for use?
Domain: free text
–>
</purpose>
<supplinf>
USGS Contract No. G10PC01234
CONTRACTOR: We Map4U, Inc.
SUBCONTRACTOR: Aerial Scanning Services, LLC
Lidar data were acquired and calibrated by Aerial Scanning Services.
All follow-on processing was completed by the prime contractor.
<!–OPTIONAL Element: Supplemental Information
Enter other descriptive information about the dataset.
Desirable information includes any deviations from project specifications and
reasons. It also may include any other information that the contractor finds
necessary or useful, such as contract number or summary of lidar technology.
Remove this tag or clear the contents of this tag if none.
Domain: free text
–>
</supplinf>
</descript>
<timeperd>
<timeinfo>
<!–REQUIRED Group: Time info: will be either:
single date,
OR multiple dates,
OR a range of dates.
Examples are provided for all three formats.
Delete the ones that do not apply.
–>
<sngdate>
<!–Begin the example of Single Date–>
<caldate> 20100216
<!–REQUIRED Element: Calendar Date
This is the date of the LiDAR collection, if the collection
was completed in one day. &#13
The field MUST be formatted YYYYMMDD
–>
</caldate>
</sngdate>
<mdattim>
42 Lidar Base Specification Version 1.0
<!– Begin example of a multiple dates –>
<sngdate>
<caldate> 20100216
<!–REQUIRED Element: Calendar Date
This is the first date of the LiDAR collection, when
multiple collection dates are specified.
The field MUST be formatted YYYYMMDD
–>
</caldate>
</sngdate>
<sngdate>
<caldate> 20100218
<!–REQUIRED Element: Calendar Date
This is the second date of the LiDAR collection, when
multiple collection dates are specified.
The field MUST be formatted YYYYMMDD
REPEAT the sngdate and caldate tags for each collection date
–>
</caldate>
</sngdate>
</mdattim>
<rngdates>
<!– Begin example of a date range –>
<begdate> 20100216
<!–REQUIRED Element: Beginning Date
This is the beginning date of LiDAR collection.
The field MUST be formatted YYYYMMDD
–>
</begdate>
<enddate> 20100218
<!–REQUIRED Element: Ending Date
This is the ending date of LiDAR collection.
The field MUST be formatted YYYYMMDD
–>
</enddate>
</rngdates>
</timeinfo>
<current> EXAMPLE: ground condition
<!–REQUIRED Element: Currrentness Reference
Enter the basis on which the time period of content information is determined.
Domain: “ground condition” “publication date” free text
–>
</current>
</timeperd>
<status>
<progress> EXAMPLE: Partial: Lot 2 of 5
<!–REQUIRED ELEMENT: Progress
Enter the state of the dataset.
Domain: “Complete” “Partial: Lot x of n”
–>
</progress>
<update> EXAMPLE: None planned
<!–REQUIRED ELEMENT: Maintenance and Update Frequency
Enter the repeat cycle for the project.
Domain: “Annually” “Unknown” “None planned” free text
–>
</update>
</status>
<spdom>
<bounding>
<westbc> -91.750000
<!–REQUIRED Element: West Bounding Coordinate
Appendix 5. Lidar Metadata Template 43
This value is the Western-most limit of coverage of the dataset
expressed as longitude.
This value will be negative in the United States.
This value MUST be expressed in Decimal Degrees.
Domain: -180.0<= West Bounding Coordinate< 180.0
–>
</westbc>
<eastbc> -91.25000
<!–REQUIRED Element: East Bounding Coordinate
This value is the Eastern-most limit of coverage of the dataset
expressed as longitude.
This value will be negative in the United States.
This value MUST be expressed in Decimal Degrees.
Domain: -180.0<= East Bounding Coordinate<= 180.0
–>
</eastbc>
<northbc> 38.00000
<!–REQUIRED Element: North Bounding Coordinate
This value is the Northern-most limit of coverage of the dataset
expressed as latitude.
This value will be positive in the United States.
This value MUST be expressed in Decimal Degrees.
Domain: -90.0<= North Bounding Coordinate<= 90.0
–>
</northbc>
<southbc> 37.250000
<!–REQUIRED Element: South Bounding Coordinate
This value is the Southern-most limit of coverage of the dataset
expressed as latitude.
This value will be positive in the United States.
This value MUST be expressed in Decimal Degrees.
Domain: -90.0<= South Bounding Coordinate<= 90.0
–>
</southbc>
</bounding>
<lboundng>
<leftbc> 584800
<!–REQUIRED Element: This value is the Western-most coordinate of limit of
coverage of the dataset expressed in the Coordinate Reference System in
which the data are delivered.
–>
</leftbc>
<rightbc> 664800
<!–REQUIRED Element: This value is the Eastern-most coordinate of limit of
coverage of the dataset expressed in the Coordinate Reference System in
which the data are delivered.
–>
</rightbc>
<topbc> 4225400
<!–REQUIRED Element: This value is the Northern-most coordinate of limit of
coverage of the dataset expressed in the Coordinate Reference System in
which the data are delivered.
–>
</topbc>
<bottombc> 4141400
<!–REQUIRED Element: This value is the Southern-most coordinate of limit of
coverage of the dataset expressed in the Coordinate Reference System in
which the data are delivered.
–>
</bottombc>
</lboundng>
</spdom>
44 Lidar Base Specification Version 1.0
<keywords>
<theme>
<themekt> EXAMPLE: None
<!–REQUIRED Element: Theme Keyword Thesaurus
A formally registered thesaurus or a similar authoritative source of theme
keywords.
Domain: “None” free text
–>
</themekt>
<themekey> EXAMPLE: Elevation data
<!–REQUIRED Element: Theme Keyword: Elevation data (required)–>
</themekey>
<themekey> EXAMPLE: Lidar
<!–REQUIRED Element: Theme Keyword: Lidar (required)–>
</themekey>
<themekey> EXAMPLE: Hydrology
<!–Enter any additional applicable theme keywords, use only ONE keyword for each
themekey tag. Repeat the themekey tag as many times as necessary.
Domain: free text
–>
</themekey>
</theme>
<place>
<placekt> EXAMPLE: None
<!–REQUIRED Element: Place Keyword Thesaurus
Reference to a formally registered thesaurus or a similar authoritative
source of place keywords.
Domain: “None” “Geographic Names Information System” free text
–>
</placekt>
<placekey> EXAMPLE: Missouri
<!–REQUIRED Element: Place Keyword
For multi-state projects, make a separate entry for each state.
List only one state for each placekey tag.
–>
</placekey>
<placekey> EXAMPLE: Phelps County
<!–REQUIRED Element: Place Keyword
For multi-county projects, make a separate entry for each county.
List only one county for each placekey tag.
–>
</placekey>
<placekey> EXAMPLE: Dent County
</placekey>
<placekey> EXAMPLE: Mark Twain National Forest
<!–Enter any additional applicable place keywords, for example cities or
landmarks.
Use only one keyword for each placekey tag.
Repeat the placekey tag as many times as necessary.
Domain: free text
–>
</placekey>
</place>
</keywords>
<accconst> EXAMPLE: No restrictions apply to these data.
<!–REQUIRED Element: Access Constraints.
Enter restrictions and legal prerequisites for
accessing the dataset. These include any access constraints applied
to assure the protection of privacy or intellectual property, and
any special restrictions or limitations on obtaining the dataset.
Domain: “None” free text
–>
Appendix 5. Lidar Metadata Template 45
</accconst>
<useconst> EXAMPLE: None. However, users should be aware that temporal changes may
have occurred since this dataset was collected and that some parts of these data may
no Longer represent actual surface conditions. Users should not use these data for
critical applications without a full awareness of it’s limitations. Acknowledgement
of the U.S. Geological Survey would be appreciated for products derived from these
data.
<!–REQUIRED Element: Enter restrictions and legal prerequisites for
using the dataset after access is granted. These include any use
constraints applied to assure the protection of privacy or intellectual
property, and any special restrictions or limitations on using the dataset.
Domain: “None” free text
–>
</useconst>
<ptcontac>
<cntinfo>
<cntorgp>
<cntorg> EXAMPLE: We Map 4U, Data Acquisition Department
<!–REQUIRED Element: Contact Organization:
Name of the organization that created the data and is knowledgeable about
the data.
Domain: free text
–>
</cntorg>
<cntper> EXAMPLE: Jane Smith
<!–REQUIRED Element: Contact Person
The name of the individual who is knowledgeable about the data.
Domain: free text
–>
</cntper>
</cntorgp>
<cntaddr>
<addrtype> EXAMPLE: mailing and physical
<!–REQUIRED Element: Address Type
The type of address that follows.
Only required for “mailing” or “mailing and physical”. If the contractor
has a different mailing and physical address, the physical address
does not need to be included. This section may be repeated if you would
like to provide a separate physical address.
Domain: “mailing” “physical” “mailing and physical”, free text
–>
</addrtype>
<address> EXAMPLE: 123 Main St.
<!–REQUIRED Element: Address
The address of the contractor.
For multiple line addresses the address tag may be repeated as many times
as needed.
Domain: free text
–>
</address>
<city> EXAMPLE: Anytown
<!–REQUIRED Element: City
The city of the address.
Domain: free text
–>
</city>
<state> EXAMPLE: MO
<!–REQUIRED Element: State
The state or province of the address.
Domain: free text
–>
</state>
46 Lidar Base Specification Version 1.0
<postal> EXAMPLE: 61234
<!–REQUIRED Element: Postal Code
Enter the ZIP or other postal code of the address.
Domain: free text
–>
</postal>
<country> EXAMPLE: USA
<!–OPTIONAL Element: Country
The country of the address.
Domain: free text
–>
</country>
</cntaddr>
<cntvoice> EXAMPLE: 555-555-1234
<!–REQUIRED Element: Contact Voice Telephone
The telephone number by which individuals can speak to the
organization or individual responsible for the data.
Domain: free text
–>
</cntvoice>
<cnttdd> EXAMPLE: 555-555-1122
<!–OPTIONAL Element: Contact TDD/TTY Telephone
The telephone number by which hearing-impaired individuals
can contact the organization or individual.
Domain: free text
–>
</cnttdd>
<cntfax> EXAMPLE: 555-5550-1235
<!–OPTIONAL Element: Contact Fax
The telephone number of a facsimile machine of the organization
or individual.
Domain: free text
–>
</cntfax>
<cntemail> EXAMPLE: jsmith@wemap4u.com
<!–OPTIONAL Element: Contact E-mail Address
The email address of the organization or individual.
Domain: free text
–>
</cntemail>
<hours> EXAMPLE: Monday through Friday 8:00 AM to 4:00 PM (Central Time)
<!–OPTIONAL Element: Hours of Service
The time period when individuals can speak to the organization or individual.
Domain: free text
–>
</hours>
<cntinst> EXAMPLE: If unable to reach the contact by telephone,
please send an email. You should get a response within 24 hours.
<!–OPTIONAL Element: Contact Instructions
Supplemental instructions on how or when to contact the individual or
organization.
Domain: free text
–>
</cntinst>
</cntinfo>
</ptcontac>
<native> EXAMPLE: Optech DASHMap 4.2200; ALS Post Processor 2.70 Build#15;
GeoCue Version 6.1.21.4; Windows XP Operating System
\\server\directory path\*.LAS
17 GB
<!–REQUIRED: Native Data Set Environment
Description of the dataset in the producer’s processing
Appendix 5. Lidar Metadata Template 47
environment, including items such as the name of the software (including version),
the computer operating system, file name (including host-, path-, and filenames),
and the dataset size.
Domain: free text
–>
</native>
</idinfo>
<dataqual>
<logic> EXAMPLE: Data cover the entire area specified for this project.
<!–REQUIRED Element: Logical Consistency Report
Describe the fidelity of relations in the data
structure of the lidar data: tests of valid values
or topological tests. Identify software used and
the date of the tests.
Domain: free text
–>
</logic>
<complete> EXAMPLE: These raw LAS data files include all data points collected.
No points have been removed or excluded.
A visual qualitative assessment was performed to ensure data completeness.
There are no void areas or missing data. The raw point cloud is of good
quality and data passes Fundamental Vertical Accuracy specifications.
<!–REQUIRED Element: Completeness Report
Document the inclusion or omissions of features for
the dataset. Minimum width or area thresholds.
Selection criteria or other rules used to derive the
dataset.
Domain: free text
–>
</complete>
<posacc>
<vertacc>
<vertaccr> EXAMPLE: The specifications require that only Fundamental Vertical
Accuracy (FVA) be computed for raw lidarpoint cloud swath files.
The vertical accuracy was tested with 25 independent survey located in open
terrain. These check points were not used in the calibration or post
processing of the lidar point cloud data. The survey checkpoints were
distributed throughout the project area. Specifications for this project
require that the FVA be 25 cm or better AccuracyZ at 95 percent confidence
level.
<!–REQUIRED Element: Vertical Positional Accuracy Report
An explanation of the accuracy of the vertical coordinate measurements
and a description of the tests used.
Domain: free text
–>
</vertaccr>
<qvertpa>
<vertaccv> EXAMPLE: 0.19 meters AccuracyZ at 95 percent Confidence Interval
<!–REQUIRED Element: Vertical Positional Accuracy Value
Vertical accuracy expressed in (ground) meters.
Clearly state whether this value is RMSEz or AccuracyZ
Domain: free text
–>
</vertaccv>
<vertacce> The FVA was tested using 25 independent survey located in open
terrain terrain. The survey checkpoints were distributed throughout the
project area. The 25 independant check points were surveyed using xxxx
technique. Elevations from the unclassified lidar surface were measured
for the x,y location of each check point.
Elevations interpolated from the lidar surface were then compared to the
elevation values of the surveyed control. The RMSE was computed to be
0.097m. AccuracyZ has been tested to meet 9.7 cm Fundamental Vertical
48 Lidar Base Specification Version 1.0
Accuracy at 95 Percent confidence level using RMSE(z) x 1.9600 as defined
by the National Standards for Spatial Data Accuracy (NSSDA); assessed and
reported using National Digital Elevation Program (NDEP)/ASRPS Guidelines.
<!–REQUIRED Element: Vertical Positional Accuracy Explanation
Identification of the test that yielded the Vertical Positional Accuracy
Value.
Domain: free text
–>
</vertacce>
</qvertpa>
</vertacc>
</posacc>
<lineage>
<srcinfo>
<!– The srcinfo section of the metadata MUST be repeated for each data source
that contributed making this unclassified LAS swath dataset. This includes,
but is not limited to, 1) ground control used for calibrating the lidar data,
2) the actual lidar aquistion data, and 3) independent ground control used to
assess the accuracy of the lidar point cloud.
–>
<srccite>
<citeinfo>
<origin> EXAMPLE: Jiffy Survey, Inc
<!–REQUIRED Element: Originator
This the name of an organization or individual that
developed the dataset. If the creation of this data source was created
by a subcontractor, the subcontractors name and contact information
should be entered as the source for that contributing data set.
Domain: “Unknown” free text
–>
</origin>
<pubdate> 20100115
<!–REQUIRED element: Date of Publication
Enter the date when the dataset is published or otherwise made available
for release.
The format of this date must be YYYMMDD.
Domain: “Unknown” “Unpublished material” free date
–>
</pubdate>
<title> EXAMPLE: Ground Control for Phelps and Dent County, MO lidar project
<!–REQUIRED Element: Title
The name by which the first contributing dataset is known.
Domain: free text
–>
</title>
<geoform> EXAMPLE: vector digital data and tabular data
<!–OPTIONAL Element: Enter the mode in which the geospatial data are
represented.
Domain: (the listed domain is partially from pp. 88-91 in Anglo-American
Committee on Cataloguing of Cartographic Materials, 1982, Cartographic
materials: A manual of interpretation for AACR2: Chicago,
American Library Association):
“atlas” “audio” “diagram” “document” “globe” “map” “model” “multimedia
presentation” “profile” “raster digital data” “remote-sensing image”
“section” “spreadsheet” “tabular digital data” “vector digital data”
“video” “view” free text
–>
</geoform>
<pubinfo>
<pubplace> EXAMPLE: Jiffy Survey, Inc.
<!–REQUIRED Element: Publication Place
The name of the city (and state or province, and country, if needed to
Appendix 5. Lidar Metadata Template 49
identify the city) the originator of the dataset.
Domain: free text
–>
</pubplace>
<publish> EXAMPLE: Jiffy Survey, Inc., GPS department
<!–Enter the name of the individual or organization that published the
dataset.
Domain: free text
–>
</publish>
</pubinfo>
<othercit> EXAMPLE: None.
<!–OPTIONAL Element: Other Citation Details
Other information required to complete the citation.
Domain: free text
–>
</othercit>
<onlink> EXAMPLE: ftp://JiffySurveyftp.com/data/outgoing/Task1/
<!–OPTIONAL Element: Online Linkage
IF APPLICABLE: The URL of an online computer resource that contains the
dataset.
Domain: free text
–>
</onlink>
</citeinfo>
</srccite>
<srcscale> Example: 50
<!–OPTIONAL Element: Source Scale Denominator
IF APPLICABLE: The denominator of the representative fraction on a map
(for example, on a 1:24,000-scale map, the Source Scale Denominator is 24000).
Domain: Source Scale Denominator > 1
–>
</srcscale>
<typesrc> EXAMPLE: CD-ROM
<!–REQUIRED Element: Type of Source Media
The medium of the first source dataset.
Domain: “paper” “stable-base material” “microfiche” “microfilm”
“audiocassette” “chart” “filmstrip” “transparency” “videocassette”
“videodisc” “videotape” “physical model” “computer program” “disc”
“cartridge tape” “magnetic tape” “online” “CD-ROM”
“electronic bulletin board” “electronic mail system” free text
–>
</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate> 201001003
<!–REQUIRED Element: Calendar Date
This is the date of the first source dataset was created.
The field MUST be formatted YYYYMMDD
–>
</caldate>
</sngdate>
</timeinfo>
<srccurr> EXAMPLE: ground condition
<!–REQUIRED Elemenet: Source Currentness Reference
The basis on which the source time period of content information of the
source dataset is determined.
Domain: “ground condition” “publication date” free text
–>
</srccurr>
</srctime>
50 Lidar Base Specification Version 1.0
<srccitea> EXAMPLE: Phelps_Co_lidar_gnd_ctrl
<!–REQUIRED Element: Source Citation Abbreviation
Enter short-form alias for the source citation.
Each source MUST HAVE A UNIQUE ID.
This ID will be used to reference these source data in the Process Step
sections below.
Domain: free text
–>
</srccitea>
<srccontr> EXAMPLE: This data source was used (along with the airborne GPS/IMU
Data) to georeferencing of the lidar point cloud data.
<!–REQUIRED Element: Source Contribution
Brief statement identifying the information contributed.
Domain: free text
–>
</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>USDA</origin>
<pubdate> 20090606</pubdate>
<title>NAIP Imagery for Phelps and Dent County, MO lidar project</title>
<geoform>raster orthoimagery</geoform>
<pubinfo>
<pubplace>USGS-EROS</pubplace>
<publish>USGS-EROS</publish>
</pubinfo>
<othercit>None</othercit>
<onlink></onlink>
</citeinfo>
</srccite>
<srcscale>50</srcscale>
<typesrc>online</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>20090101</caldate>
</sngdate>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>Phelps-Dent_Co_NAIP_Imagery</srccitea>
<srccontr>This data source was used (along with the lidar intensity imagery)
to classify the lidar point cloud data.
</srccontr>
</srcinfo>
<srcinfo>
<srccite>
<citeinfo>
<origin>We Map 4U, Inc.</origin>
<pubdate>20101208</pubdate>
<title>Lidar Intensity Imagery for Phelps and Dent County, MO</title>
<geoform>raster orthoimagery</geoform>
<pubinfo>
<pubplace>USGS-EROS</pubplace>
<publish>USGS-EROS</publish>
</pubinfo>
<othercit>None</othercit>
<onlink></onlink>
</citeinfo>
</srccite>
Appendix 5. Lidar Metadata Template 51
<srcscale>50</srcscale>
<typesrc>online</typesrc>
<srctime>
<timeinfo>
<rngdates>
<begdate>20100216</begdate>
<enddate>20100218</enddate>
</rngdates>
</timeinfo>
<srccurr>ground condition</srccurr>
</srctime>
<srccitea>Phelps-Dent_Co_Lidar_Intensity_Imagery</srccitea>
<srccontr>This data source was used (along with NAIP imagery)
to classify the lidar point cloud data.
</srccontr>
</srcinfo>
<procstep>
<procdesc> EXAMPLE: Lidar Pre-Processing: Airborne GPS and IMU data were merged
to develop a Single Best Estimate (SBET) of the lidar system trajectory for
each lift. Lidar ranging data were initially calibrated using previous best
parameters for this instrument and aircraft. Relative calibration was evaluated
using advanced plane-matching analysis and parameter corrections derived. This
was repeated iteratively until residual errors between overlapping swaths,
across all project lifts, was reduced to 2cm or less. Data were then block
adjusted to match surveyed calibration control. Raw data FVA were checked
using independently surveyed checkpoints. Swath overage points were identified
and tagged within each swath file. The results of the final calibration, FVA
and horizontal accuracy assessments, and the “raw” swaths were forwarded
to the client to obtain a Notice To Proceed on classification and derivative
product generation.
<!–Enter an explanation of the event and related parameters or tolerances.
Domain: free text
–>
</procdesc>
<srcused> EXAMPLE: Phelps_Co_lidar_gnd_ctrl
<!–Enter the Source Citation Abbreviation of a dataset used in the processing
step.
Domain: Source Citation Abbreviations from the Source Information entries for
the dataset.
–>
</srcused>
<procdate> 20100131
<!–Enter the date when the event was completed.
Domain: “Unknown” “Not complete” free date
–>
</procdate>
<srcprod> EXAMPLE: LiDAR datasets with USGS classifications
<!–Enter the Source Citation Abbreviation of an intermediate dataset that
(1) is significant in the opinion of the data producer, (2) is generated in
the processing step, and (3) is used in later processing steps.
Domain: Source Citation Abbreviations from the Source Information entries
for the dataset.
–>
</srcprod>
<proccont>
<cntinfo>
<cntorgp>
<cntorg> EXAMPLE: We Map 4U, Data Acquisition Department
<!–Enter the name of the organization to which the contact type applies.
Domain: free text
–>
</cntorg>
52 Lidar Base Specification Version 1.0
<cntper> EXAMPLE: Manny Puntas
<!–Enter the name of the individual to which the contact type applies.
Domain: free text
–>
</cntper>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>123 Main St.</address>
<city>Anytown</city>
<state>MO</state>
<postal>61234</postal>
<country>USA</country>
</cntaddr>
<cntvoice>555-555-556</cntvoice>
<cntfax>555-5550-1236</cntfax>
<cntemail>mpuntas@wemap4u.com</cntemail>
<hours>Monday through Friday 8:00 AM to 4:00 PM (Central Time)</hours>
<cntinst> If unable to reach the contact by telephone, please send an email.
You should get a response within 24 hours.
</cntinst>
</cntinfo>
</proccont>
</procstep>
<procstep>
<procdesc>Lidar Post-Processing: The calibrated and controlled lidar
swaths were processed using automatic point classification routines
in proprietary software. These routines operate against the entire
collection (all swaths, all lifts), eliminating character differences
between files. Data were then distributed as virtual tiles to experienced
lidar analysts for localized automatic classification, manual editing,
and peer-based QC checks. Supervisory QC monitoring of work in progress
and completed editing ensured consistency of classification character and
adherence to project requirements across the entire project area.
All classification tags are stored in the original swath files.
After completion of classification and final QC approval, the FVA,
SVAs, and CVA for the project are calculated. Sample areas for each
land cover type present in the project area were extracted and forwarded
to the client, along with the results of the accuracy tests. Upon acceptance,
the complete classified lidar swath files were delivered to the client.
</procdesc>
<srcused>Phelps-Dent_Co_NAIP_Imagery</srcused>
<srcused>Phelps-Dent_Co_Lidar_Intensity_Imagery</srcused>
<procdate>20100530</procdate>
<proccont>
<cntinfo>
<cntorgp>
<cntorg>We Map 4U, Data Acquisition Department</cntorg>
<cntper>Manny Puntas</cntper>
</cntorgp>
<cntaddr>
<addrtype>mailing and physical</addrtype>
<address>123 Main St.</address>
<city>Anytown</city>
<state>MO</state>
<postal>61234</postal>
<country>USA</country>
</cntaddr>
<cntvoice>555-555-556</cntvoice>
<cntfax>555-5550-1236</cntfax>
<cntemail>mpuntas@wemap4u.com</cntemail>
<hours>Monday through Friday 8:00 AM to 4:00 PM (Central Time)</hours>
Appendix 5. Lidar Metadata Template 53
<cntinst> If unable to reach the contact by telephone, please send an email.
You should get a response within 24 hours.
</cntinst>
</cntinfo>
</proccont>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct> EXAMPLE: Vector
<!–REQUIRED Element: Enter the system of objects used to represent space in the
dataset.
Domain: “Point” “Vector” “Raster”
–>
</direct>
<ptvctinf>
<sdtsterm>
<sdtstype> EXAMPLE: Point
<!–REQUIRED Element: SDTS Point and Vector Object Type
Enter name of point and vector spatial objects used to l
ocate zero-, one-, and two-dimensional spatial locations
in the dataset.
Domain: (The domain is from “Spatial Data Concepts,” which is Chapter 2 of
Part 1 in Department of Commerce, 1992, Spatial Data Transfer Standard
(SDTS) (Federal Information Processing Standard 173): Washington,
Department of Commerce, National Institute of Standards and Technology):
“Point” “Entity point” “Label point” “Area point” “Node, planar graph”
“Node, network” “String” “Link” “Complete chain” “Area chain”
“Network chain, planar graph” “Network chain, nonplanar graph”
“Circular arc, three point center” “Elliptical arc” “Uniform B-spline”
“Piecewise Bezier” “Ring with mixed composition”
“Ring composed of strings” “Ring composed of chains”
“Ring composed of arcs” “G-polygon” “GT-polygon composed of rings”
“GT-polygon composed of chains”
“Universe polygon composed of rings”
“Universe polygon composed of chains”
“Void polygon composed of rings” “Void polygon composed of chains”
–>
</sdtstype>
<ptvctcnt> EXAMPLE: 764,567,423
<!–OPTIONAL Element: Point and Vector Count
Enter the total number of the point or vector object type occurring in the
dataset.
Domain: Point and Vector Object Count > 0
–>
</ptvctcnt>
</sdtsterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<planar>
<gridsys>
<!–REQUIRED Section: The section should be filled out with the relevant
parameters for the coordinate reference system for the data. Usually it will
be UTM or a State Plane Zone. Delete the irrelevant section below.
–>
<gridsysn> EXAMPLE: Universal Transverse Mercator
<!–Enter name of the grid coordinate system.
Domain: “Universal Transverse Mercator” “Universal Polar Stereographic”
“State Plane Coordinate System 1927” “State Plane Coordinate System 1983”
“ARC Coordinate System” “other grid system”
54 Lidar Base Specification Version 1.0
–>
</gridsysn>
<utm>
<utmzone> EXAMPLE: 15
<!–Enter the identifier for the UTM zone.
Type: integer
Domain:
1 <= UTM Zone Number <= 60 for the northern hemisphere;
-60 <= UTM Zone Number <= -1 for the southern hemisphere
–>
</utmzone>
<transmer>
<sfctrmer>0.9996
<!–Enter a multiplier for reducing a distance obtained from a map by
computation or scaling to the actual distance along the Central Meridian.
Domain: Scale Factor at Central Meridian > 0.0
–>
</sfctrmer>
<longcm>-117.000000
<!–Enter the line of longitude at the center of a map projection
generally used as the basis for constructing the projection.
Type: real
Domain: -180.0 <= Longitude of Central Meridian < 180.0
–>
</longcm>
<latprjo>0.0
<!–Enter latitude chosen as the origin of rectangular coordinates for
a map projection.
Domain: -90.0 <= Latitude of Projection Origin <= 90.0
–>
</latprjo>
<feast>500000
<!–Enter the value added to all “x” values in the rectangular
coordinates for a map projection. This value frequently is assigned
to eliminate negative numbers.
Expressed in the unit of measure identified in Planar Coordinate Units.
Domain: free real
–>
</feast>
<fnorth>0.0
<!–Enter the value added to all “y” values in the rectangular
coordinates for a map projection. This value frequently is assigned
to eliminate negative numbers.
Expressed in the unit of measure identified in Planar Coordinate Units.
Domain: free real
–>
</fnorth>
</transmer>
</utm>
<spcs>
<spcszone>
<!–Enter identifier for the SPCS zone.
Domain: Four-digit numeric codes for the State Plane Coordinate Systems
based on the North American Datum of 1927 are found in Department of
Commerce, 1986, Representation of geographic point locations for
information interchange (Federal Information Processing Standard 70-1):
Washington: Department of Commerce, National Institute of Standards and
Technology. Codes for the State Plane Coordinate Systems based on the
North American Datum of 1983 are found in Department of Commerce, 1989
(January), State Plane Coordinate System of 1983 (National Oceanic and
Atmospheric Administration Manual NOS NGS 5): Silver Spring, Maryland,
National Oceanic and Atmospheric Administration, National Ocean Service,
Appendix 5. Lidar Metadata Template 55
Coast and Geodetic Survey.
–>
</spcszone>
<!———————————————————————————->
<lambertc>
<stdparll>
<!–Enter line of constant latitude at which the surface of the Earth
and the plane or developable surface intersect.
Domain: -90.0 <= Standard Parallel <= 90.0
–>
</stdparll>
<longcm>
<!–Enter the line of longitude at the center of a map projection
generally used as the basis for constructing the projection.
Domain: -180.0 <= Longitude of Central Meridian < 180.0
–>
</longcm>
<latprjo>
<!–Enter latitude chosen as the origin of rectangular coordinates for
a map projection.
Domain: -90.0 <= Latitude of Projection Origin <= 90.0
–>
</latprjo>
<feast>
<!–Enter the value added to all “x” values in the rectangular
coordinates for a map projection. This value frequently is assigned
to eliminate negative numbers.
Expressed in the unit of measure identified in Planar Coordinate Units.
Domain: free real
–>
</feast>
<fnorth>
<!–Enter the value added to all “y” values in the rectangular
coordinates for a map projection. This value frequently is assigned
to eliminate negative numbers.
Expressed in the unit of measure identified in Planar Coordinate Units.
Domain: free real
–>
</fnorth>
</lambertc>
<!———————————————————————————->
<transmer>
<sfctrmer>
<!–Enter a multiplier for reducing a distance obtained from a map by
computation or scaling to the actual distance along the central
meridian.
Domain: Scale Factor at Central Meridian > 0.0
–>
</sfctrmer>
<longcm>
<!–Enter the line of longitude at the center of a map projection
generally used as the basis for constructing the projection.
Type: real
Domain: -180.0 <= Longitude of Central Meridian < 180.0
–>
</longcm>
<latprjo>
<!–Enter latitude chosen as the origin of rectangular coordinates for
a map projection.
Domain: -90.0 <= Latitude of Projection Origin <= 90.0
–>
</latprjo>
56 Lidar Base Specification Version 1.0
<feast>
<!–Enter the value added to all “x” values in the rectangular
coordinates for a map projection. This value frequently is assigned
to eliminate negative numbers.
Expressed in the unit of measure identified in Planar Coordinate Units.
Domain: free real
–>
</feast>
<fnorth>
<!–Enter the value added to all “y” values in the rectangular
coordinates for a map projection. This value frequently is assigned
to eliminate negative numbers.
Expressed in the unit of measure identified in Planar Coordinate Units.
Domain: free real
–>
</fnorth>
</transmer>
<!———————————————————————————->
<obqmerc>
<sfctrlin>
<!–Enter a multiplier for reducing a distance obtained from a map by
computation or scaling to the actual distance along the center line.
Domain: Scale Factor at Center Line > 0.0
–>
</sfctrlin>
<obqlazim>
<azimangl>
<!–Enter angle measured clockwise from north, and expressed in degrees.
Domain: 0.0 <= Azimuthal Angle < 360.0
–>
</azimangl>
<azimptl>
<!–Enter longitude of the map projection origin.
Domain: -180.0 <= Azimuth Measure Point Longitude < 180.0
–>
</azimptl>
</obqlazim>
<obqlpt>
<obqllat>
<!–Enter latitude of a point defining the oblique line.
Domain: -90.0 <= Oblique Line Latitude <= 90.0
–>
</obqllat>
<obqllong>
<!–Enter longitude of a point defining the oblique line.
Domain: -180.0 <= Oblique Line Longitude < 180.0
–>
</obqllong>
</obqlpt>
<latprjo>
<!–Enter latitude chosen as the origin of rectangular coordinates for
a map projection.
Domain: -90.0 <= Latitude of Projection Origin <= 90.0
–>
</latprjo>
<feast>
<!–Enter the value added to all “x” values in the rectangular
coordinates for a map projection. This value frequently is assigned
to eliminate negative numbers.
Expressed in the unit of measure identified in Planar Coordinate Units.
Domain: free real
–>
Appendix 5. Lidar Metadata Template 57
</feast>
<fnorth>
<!–Enter the value added to all “y” values in the rectangular
coordinates for a map projection. This value frequently is assigned
to eliminate negative numbers.
Expressed in the unit of measure identified in Planar Coordinate Units.
Domain: free real
–>
</fnorth>
</obqmerc>
<!———————————————————————————->
<polycon>
<longcm>
<!–Enter the line of longitude at the center of a map projection
generally used as the basis for constructing the projection.
Domain: -180.0 <= Longitude of Central Meridian < 180.0
–>
</longcm>
<latprjo>
<!–Enter latitude chosen as the origin of rectangular coordinates
for a map projection.
Domain: -90.0 <= Latitude of Projection Origin <= 90.0
–>
</latprjo>
<feast>
<!–Enter the value added to all “x” values in the rectangular
coordinates for a map projection. This value frequently is assigned
to eliminate negative numbers.
Expressed in the unit of measure identified in Planar Coordinate Units.
Domain: free real
–>
</feast>
<fnorth>
<!–Enter the value added to all “y” values in the rectangular
coordinates for a map projection. This value frequently is assigned
to eliminate negative numbers.
Expressed in the unit of measure identified in Planar Coordinate Units.
Domain: free real
–>
</fnorth>
</polycon>
<!———————————————————————————->
</spcs>
</gridsys>
<planci>
<plance>coordinate pair</plance>
<coordrep>
<absres>0.01</absres>
<ordres>0.01</ordres>
</coordrep>
<plandu>meters</plandu>
</planci>
</planar>
<geodetic>
<horizdn>EXAMPLE: North American Datum of 1983
<!–REQUIRED Element: Enter the identification given to the reference system
used for defining the coordinates of points.
Domain: “North American Datum of 1927” “North American Datum of 1983”
free text
–>
</horizdn>
<ellips>EXAMPLE: Geodetic Reference System 80
58 Lidar Base Specification Version 1.0
<!–REQUIRED Element: Enter identification given to established representations
of the Earth’s shape.
Domain: “Clarke 1866” “Geodetic Reference System 80” free text
–>
</ellips>
<semiaxis>6378137
<!–REQUIRED Element: Enter radius of the equatorial axis of the ellipsoid.
Domain: Semi-major Axis > 0.0
–>
</semiaxis>
<denflat>298.257222101
<!–REQUIRED Element: Enter the denominator of the ratio of the difference
between the equatorial and polar radii of the ellipsoid when the numerator
is set to 1.
Domain: Denominator of Flattening > 0.0
–>
</denflat>
</geodetic>
</horizsys>
<vertdef>
<altsys>
<altdatum> EXAMPLE: North American Vertical Datum of 1988
<!–REQUIRED Element: Vertical Datum: The surface of reference from which
vertical distances are measured.
Domain: “National Geodetic Vertical Datum of 1929”
“North American Vertical Datum of 1988”
free text
–>
</altdatum>
<altres> 0.01
<!– REQUIRED Element: Vertical Resolution: The minimum distance possible
between two adjacent elevation (altitude) values, expressed in Altitude
Distance Units of measure.
Domain: Altitude Resolution > 0.0
–>
</altres>
<altunits> EXAMPLE: meters
<!–REQUIRED Element: Units in which altitudes are recorded.
Domain: “meters” “feet” free text
–>
</altunits>
<altenc> EXAMPLE: Explicit elevation coordinate included with horizontal
coordinates
<!–REQUIRED Element: Altitude Encoding Method: The means used to encode the
elevations.
Domain: “Explicit elevation coordinate included with horizontal coordinates”
“Implicit coordinate” “Attribute values”
–>
</altenc>
</altsys>
</vertdef>
</spref>
<eainfo>
<!–SECTION: Entity and Attribute Information
THIS SECTION IS NOT REQUIRED FOR LIDAR LAS DELIVERABLES.
It is only required for deliverable data classified as a Feature Class.
–>
</eainfo>
<distinfo>
<!–SECTION: Distribution Information: Information about the distributor of and
options for obtaining the dataset.
THIS SECTION SHOULD ONLY BE POPULATED IF SOME ORGANIZATION OTHER THAN USGS HAS
Appendix 5. Lidar Metadata Template 59
DISTRIBUTION RIGHTS TO THE DATA.
–>
<distrib>
<cntinfo>
<cntorgp>
<cntorg> Leave blank unless an organization outside of USGS has distribution
rights to the data.
</cntorg>
<cntper> Leave blank unless an organization outside of USGS has distribution
rights to the data.
</cntper>
</cntorgp>
<cntaddr>
<addrtype> Leave blank unless an organization outside of USGS has distribution
rights to the data.
</addrtype>
<address> Leave blank unless an organization outside of USGS has distribution
rights to the data.
</address>
<city> Leave blank unless an organization outside of USGS has distribution
rights to the data.
</city>
<state> Leave blank unless an organization outside of USGS has distribution
rights to the data.
</state>
<postal> Leave blank unless an organization outside of USGS has distribution
rights to the data.
</postal>
<country> Leave blank unless an organization outside of USGS has distribution
rights to the data.
</country>
</cntaddr>
<cntvoice> Leave blank unless an organization outside of USGS has distribution
rights to the data.
</cntvoice>
<cntemail> Leave blank unless an organization outside of USGS has distribution
rights to the data.
</cntemail>
</cntinfo>
</distrib>
<resdesc> Leave blank unless an organization outside of USGS has distribution
rights to the data.
</resdesc>
<distliab> Leave blank unless an organization outside of USGS has distribution
rights to the data.
</distliab>
</distinfo>
<metainfo>
<!– REQUIRED SECTION: Metadata Reference Information: Information on the
currentness of the metadata information, and the party responsible for the
metadata.
–>
<metd> 20101206
<!–REQUIRED Element: Metadata Date: The date that the metadata were created or
last updated.
Must be in the format YYYYMMDD.
–>
</metd>
<metrd> 20101207
<!–OPTIONAL Element: Metadata Review Date: The date of the latest review of the
metadata entry.
Must be in the format YYYYMMDD.
60 Lidar Base Specification Version 1.0
Domain: Metadata Review Date later than Metadata Date
–>
</metrd>
<metc>
<cntinfo>
<cntorgp>
<cntorg> EXAMPLE: We Map 4U, Data Acquisition Department
<!–REQUIRED Element: Contact Organization: The name of the organization
which is responsible for creating the metadata.
Domain: free text
–>
</cntorg>
<cntper> EXAMPLE: John Smith
<!–REQUIRED Element: Contact Person: The name of the individual who is the
contact person concerning the metadata.
Domain: free text
–>
</cntper>
</cntorgp>
<cntaddr>
<addrtype> EXAMPLE: mailing and physical
<!–REQUIRED Element: Address Type: The type of address that follows.
Only required for “mailing” or “mailing and physical”. If the contractor
has a different mailing and physical address, the physical address does
not need to be included.
Domain: “mailing” “physical” “mailing and physical”, free text
–>
</addrtype>
<address> EXAMPLE: 123 Main St.
<!–REQUIRED Element: Address: The address of the contractor responsible
for the metadata. For multiple line addresses the address tag may be
repeated as many times as needed.
Domain: free text
–>
</address>
<city> EXAMPLE: Anytown
<!–REQUIRED Element: City: The city of the address.
Domain: free text
–>
</city>
<state> EXAMPLE: MO
<!–REQUIRED Element: State: The state or province of the address.
Domain: free text
–>
</state>
<postal> EXAMPLE: 61234
<!–REQUIRED Element: Postal Code: Enter the ZIP or other postal code
of the address.
Domain: free text
–>
</postal>
<country> EXAMPLE: USA
<!–OPTIONAL Element: Country: The country of the address.
Domain: free text
–>
</country>
</cntaddr>
<cntvoice> EXAMPLE: 555-555-1234
<!–REQUIRED Element: Contact Voice Telephone: The telephone number by which
individuals can speak to the organization or individual responsible for the
metadata.
Domain: free text
Appendix 5. Lidar Metadata Template 61
–>
</cntvoice>
<cnttdd> EXAMPLE: 555-555-1122
<!–OPTIONAL Element: Contact TDD/TTY Telephone: The telephone number by which
hearing-impaired individuals can contact the organization or individual.
Domain: free text
–>
</cnttdd>
<cntfax> EXAMPLE: 555-5550-1235
<!–OPTIONAL Element: Contact Fax: The telephone number of a facsimile machine
of the organization or individual.
Domain: free text
–>
</cntfax>
<cntemail> EXAMPLE: jsmith@wemap4u.com
<!–OPTIONAL Element: Contact E-mail Address: The email address of the
organization or individual.
Domain: free text
–>
</cntemail>
<hours> EXAMPLE: Monday through Friday 8:00 AM to 4:00 PM (Central Time)
<!–OPTIONAL Element: Hours of Service: The time period when individuals can
speak to the organization or individual.
Domain: free text
–>
</hours>
<cntinst> EXAMPLE: If unable to reach the contact by telephone, please send an
email. You should get a response within 24 hours.
<!–OPTIONAL Element: Contact Instructions: Supplemental instructions on how
or when to contact the individual or organization.
Domain: free text
–>
</cntinst>
</cntinfo>
</metc>
<metstdn> EXAMPLE: FGDC Content Standard for Digital Geospatial Metadata
<!–REQUIRED Element: Metadata Standard: Enter the name of the metadata
standard used to document the dataset.
Domain: “FGDC Content Standard for Digital Geospatial Metadata” free text
–>
</metstdn>
<metstdv> EXAMPLE: FGDC-STD-001-1998
<!–REQUIRED Element: Metadata Standard Veriosn: Enter identification of the
version of the metadata standard used to document the dataset.
Domain: free text
–>
</metstdv>
<metac> EXAMPLE: None.
<!–OPTIONAL Element: Metadata Access Constraints: Restrictions and legal
prerequisites for accessing the metadata. These include any access constraints
applied to assure the protection of privacy or intellectual property, and any
special restrictions or limitations on obtaining the metadata.
Domain: free text
–>
</metac>
<metuc> EXAMPLE: None.
<!–OPTIONAL Element: Metadata Use Constraints: Restrictions and legal prerequisites
for using the metadata after access is granted. These include any metadata use
constraints applied to assure the protection of privacy or intellectual property,
and any special restrictions or limitations on using the metadata.
Domain: free text
–>
62 Lidar Base Specification Version 1.0
</metuc>
<metsi>
<metscs> EXAMPLE: None.
<!–REQUIRED IF APPLICABLE: Metadata Security Classification System: Name of
the classification system for the metadata.
Domain: free text
–>
</metscs>
<metsc> EXAMPLE: Unclassified
<!–REQUIRED IF APPLICABLE: Metadata Security Classification: Name of the
handling restrictions on the metadata.
Domain: “Top secret” “Secret” “Confidential” “Restricted” “Unclassified”
“Sensitive” free text
–>
</metsc>
<metshd> EXAMPLE: NONE
<!–REQUIRED IF APPLICABLE: Metadata Security Handling Description: Additional
information about the restrictions on handling the metadata.
Domain: free text
–>
</metshd>
</metsi>
<metextns>
<!– Metadata Extensions Group: REQUIRED IF APPLICABLE. A reference to extended
elements to the standard which may be defined by a metadata producer or a user
community. Extended elements are elements outside the Standard, but needed by
the metadata producer. If extended elements are created, they must follow the
guidelines in Appendix D, Guidelines for Creating Extended Elements to the
Content Standard for Digital Geospatial Metadata.
–>
<!–This section may be repeated as necessary–>
<onlink> EXAMPLE: None
<!–REQUIRED IF APPLICABLE: Online Linkage: URL for the resource that contains
the metadata extension information for thedataset.
–>
</onlink>
<metprof> EXAMPLE: None
<!–REQUIRED IF APPLICABLE: Profile Name: Name of a document that describes the
application of the Standard to a specific user community.
–>
</metprof>
</metextns>
</metainfo>
</metadata>

Leave a Reply

Your email address will not be published. Required fields are marked *