<?xml version="1.0" encoding="ISO-8859-1"?>
<metadata>
<idinfo>
<citation>
<citeinfo>
<origin>Earth Systems Research Center, University of New Hampshire</origin>
<pubdate>20170712</pubdate>
<title>Land Use 2015 - Southeastern New Hampshire</title>
<edition>One</edition>
<geoform>vector digital data</geoform>
<pubinfo>
<pubplace>Durham, New Hampshire</pubplace>
<publish>Earth Systems Research Center, University of New Hampshire</publish>
</pubinfo>
<othercit>None</othercit>
<onlink>&lt;URL:http://www.granit.unh.edu/cgi-bin/nhsearch?dset=lu2015/nh&gt;</onlink>
<lworkcit>
<citeinfo>
<origin>Earth Systems Research Center, University of New Hampshire</origin>
<pubdate>19860101</pubdate>
<title>NH GRANIT Database</title>
<pubinfo>
<pubplace>Durham, New Hampshire</pubplace>
<publish>Earth Systems Research Center, University of New Hampshire</publish>
</pubinfo>
<onlink>&lt;URL:http://www.granit.unh.edu&gt;</onlink>
</citeinfo>
</lworkcit>
</citeinfo>
</citation>
<descript>
<abstract>
This data set contains detailed land use data (polygons) for 45 communities in southeastern
New Hampshire. The primary source used to map the land use was high resolution (1-foot),
true color aerial photography, collected in the spring of 2015.  Data development was
completed by Rockingham Planning Commission (27 communities) and Strafford Regional Planning
Commission (18 communities), with GRANIT providing technical support, metadata development,
and standardizing/merging of the datasets into a regional product.
</abstract>
<purpose>
These photo-interpreted land use data are intended for use by state, regional,
and municipal resource managers, planning agencies, and other stakeholders.
</purpose>
<supplinf>Data distribution tile:  full 45-town coverage area</supplinf>
</descript>
<timeperd>
<timeinfo>
<sngdate>
<caldate>2015</caldate>
</sngdate>
</timeinfo>
<current>source photography date</current>
</timeperd>
<status>
<progress>Complete</progress>
<update>Irregular</update>
</status>
<spdom>
<bounding>
<westbc>-71.45251</westbc>
<eastbc>-70.69919</eastbc>
<northbc>43.57577</northbc>
<southbc>42.73424</southbc>
</bounding>
</spdom>
<keywords>
<theme>
<themekt>None</themekt>
<themekey>Land use</themekey>
<themekey>Landuse</themekey>
<themekey>Land cover</themekey>
<themekey>Landcover</themekey>
<themekey>Photo interpretation</themekey>
</theme>
<place>
<placekt>None</placekt>
<placekey>United States</placekey>
<placekey>Northeast</placekey>
<placekey>New England</placekey>
<placekey>New Hampshire</placekey>
<placekey>Carroll County</placekey>
<placekey>Rockingham County</placekey>
<placekey>Strafford County</placekey>
<placekey>Atkinson</placekey>
<placekey>Barrington</placekey>
<placekey>Brentwood</placekey>
<placekey>Brookfield</placekey>
<placekey>Danville</placekey>
<placekey>Dover</placekey>
<placekey>Durham</placekey>
<placekey>East Kingston</placekey>
<placekey>Epping</placekey>
<placekey>Exeter</placekey>
<placekey>Farmington</placekey>
<placekey>Fremont</placekey>
<placekey>Greenland</placekey>
<placekey>Hampstead</placekey>
<placekey>Hampton</placekey>
<placekey>Hampton Falls</placekey>
<placekey>Kensington</placekey>
<placekey>Kingston</placekey>
<placekey>Lee</placekey>
<placekey>Madbury</placekey>
<placekey>Middleton</placekey>
<placekey>Milton</placekey>
<placekey>New Castle</placekey>
<placekey>New Durham</placekey>
<placekey>Newfields</placekey>
<placekey>Newington</placekey>
<placekey>Newmarket</placekey>
<placekey>Newton</placekey>
<placekey>North Hampton</placekey>
<placekey>Northwood</placekey>
<placekey>Nottingham</placekey>
<placekey>Plaistow</placekey>
<placekey>Portsmouth</placekey>
<placekey>Raymond</placekey>
<placekey>Rochester</placekey>
<placekey>Rollinsford</placekey>
<placekey>Rye</placekey>
<placekey>Salem</placekey>
<placekey>Sandown</placekey>
<placekey>Seabrook</placekey>
<placekey>Somersworth</placekey>
<placekey>South Hampton</placekey>
<placekey>Strafford</placekey>
<placekey>Stratham</placekey>
<placekey>Wakefield</placekey>
</place>
</keywords>
<accconst>None</accconst>
<useconst>Not for legal use.</useconst>
<ptcontac>
<cntinfo>
<cntperp>
<cntper>GRANIT Database Manager</cntper>
<cntorg>Earth Systems Research Center</cntorg>
</cntperp>
<cntpos>GRANIT Database Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>Morse Hall, University of New Hampshire</address>
<city>Durham</city>
<state>NH</state>
<postal>03824</postal>
<country>US</country>
</cntaddr>
<cntvoice>603-862-1792</cntvoice>
<cntfax>603-862-0188</cntfax>
<cntemail>granit@unh.edu</cntemail>
<hours>8:30AM-5PM, EST</hours>
</cntinfo>
</ptcontac>
<browse>
<browsen>&lt;URL:http://www.granit.sr.unh.edu/cgi-bin/load_file?PATH=/data/database/d-webdata/lu/lu2015/browse.gif&gt;</browsen>
<browsed>gif image file</browsed>
<browset>GIF</browset>
</browse>
<datacred>GRANIT database, Earth Systems Research Center, University of New Hampshire</datacred>
<native>ESRI ArcGIS 10x</native>
</idinfo>
<dataqual>
<attracc>
<attraccr>
Data were digitized on-screen by photo-interpreting the 1-foot resolution aerial
photography. Attribute coding was checked by on-screen overlay of the delineated land
use polygons, displayed using transparent symbology, on the source photography.  This
scrutiny detected any missing or erroneously labeled polygons.  Data capture occurred at
a scale of no less than 1:2,400.  Evaluation occurred at a scale of 1:5,000.

In addition, code domain checks ensured that only valid codes were assigned to
features, and polygon &quot;dissolve&quot; operations identified any cases where adjacent
polygons shared the same land use code.
</attraccr>
</attracc>
<logic>
Polygon and arc-node topology exists.  Topology checks were used to identify and
eliminate any sliver polygons, dangling nodes, and/or other potential errors.
</logic>
<complete>The complete 45-town area was mapped and classified.</complete>
<posacc>
<horizpa>
<horizpar>
Data were generated primarily from interpretation of the 1-ft. resolution photos.
However, variable scale vector data sets, as well as computer scripts, were
used as guides to digitize certain land use polygons (see Process Steps).
</horizpar>
</horizpa>
</posacc>
<lineage>
<srcinfo>
<srccite>
<citeinfo>
<origin>Quantum Spatial</origin>
<pubdate>2016</pubdate>
<title>2015 Orthophotography</title>
</citeinfo>
</srccite>
<srccite>
<citeinfo>
<origin>Earth Systems Research Center, University of New Hampshire</origin>
<pubdate>2011</pubdate>
<title>2010 Land Use</title>
</citeinfo>
</srccite>
<typesrc>online</typesrc>
<typesrc>online</typesrc>
<srctime>
<timeinfo>
<sngdate>
<caldate>2015</caldate>
</sngdate>
</timeinfo>
<srccurr>source photography date</srccurr>
</srctime>
<srctime>
<timeinfo>
<sngdate>
<caldate>2010</caldate>
</sngdate>
</timeinfo>
<srccurr>source photography date</srccurr>
</srctime>
<srccitea>ORTHO2015</srccitea>
<srccitea>LU2010</srccitea>
<srccontr>
Provided the basic source photography for the delineation and interpretation
of the land use features.
</srccontr>
<srccontr>Provided the initial land use delineations that were updated to 2015.</srccontr>
</srcinfo>
<procstep>
<procdesc>
A set of data standards was developed to govern key technical components
of the land use mapping, including definitions of the land use classes
and identification of feature automation protocols.   The land use
classification codes were based on a hybrid of the USGS Anderson
land-use and land-cover classification system (Levels I and II),
(http://landcover.usgs.gov/classes.html), as modified to satisfy the modeling
component of a previously-funded CICEET project.

Note also that the residential mapping protocols, described further
below, were developed jointly with staff from the Rockingham Planning
Commission, Exeter, NH, and were reviewed/approved by staff from the
Strafford Regional Planning Commission, Dover, NH.
</procdesc>
<procdate>2008</procdate>
<srcprod>LUSTANDARDS.doc</srcprod>
</procstep>
<procstep>
<procdesc>
Land use features were digitized by displaying the 2010 and use data over the
2015 orthophography, and &quot;heads-up&quot; interpretation of features that appeared to
change over the 5-year period.  Features were generally digitized to the
visible extent of their edge as interpreted by the analyst.

The mapping of the residential class was subject to additional delineation
&quot;rules&quot;. As with other classes, features were digitized to visible use boundaries
when possible.  In these cases, yard edges/natural features guided the
delineation. However, where boundaries (or partial boundaries) were indistinct,
one of several approaches was utilized:

1a)  For indistinct boundaries of houses within 250&apos; of one another and within
public water/sewer zones (based on TOWN_SW):  a .5-acre circle centered
on the edge of the structure furthest from the associated road was used as a
guide for the polygon delineation.

1b)  For indistinct boundaries of houses within 250&apos; of one another and outside
of public water/sewer zones (based on TOWN_SW):  the 1a) protocol was applied
using a 1-acre circle.

2a) For indistinct boundaries of houses greater than 250&apos; apart and within
public water/sewer zones (based on TOWN_SW):  a .5-acre box was generated,
centered on the structure (or centered in the approximate midpoint of multiple
structures on what appeared to be a single parcel).  If the structure(s) was
within 700&apos; of a road, the box was oriented parallel to the nearest road.
In cases where the rotated box intersected the road edge, it was repositioned
further away from the road to preserve as much of the box area as possible.
Where the box intersected the road buffer, the road edge became the polygon
edge.  In these cases, the box became somewhat smaller than the original .5-acre.
If the house was further than 700&apos; from the road, or did not appear to be
associated with a nearby road, the box was not rotated.

2b)  For indistinct boundaries of houses greater than 250&apos; apart and outside
of public water/sewer zones (based on TOWN_SW):  the 2a) protocol was applied
using a 1-acre box.

Note that forested areas that were completely enclosed within a developed
polygon were assumed to &quot;belong&quot; to the developed polygon, and were generally
not distinguished.
</procdesc>
<srcused>LU2010</srcused>
<srcused>ORTHO2015</srcused>
<srcused>LUSTANDARDS.doc</srcused>
<procdate>2017</procdate>
</procstep>
<procstep>
<procdesc>
The land use feature delineations were checked by visually checking the symbolized
features displayed over the source DOQs.  Modifications were made, as warranted,
during the quality control process - to correct incorrectly classed lands,
and to fix digitizing errors such as overshoots and sliver polygons.
</procdesc>
<procdate>2017</procdate>
</procstep>
<procstep>
<procdesc>
The individual regional land use data sets (from Rockingham Planning Commission and
Strafford Regional Planning Commission) were provided to GRANIT at UNH, where
attributes where attributes were standardized and the data sets were merged.
No additional QC or processing was performed on the composite data set.
</procdesc>
<procdate>2017</procdate>
</procstep>
</lineage>
</dataqual>
<spdoinfo>
<direct>Vector</direct>
<ptvctinf>
<sdtsterm>
<sdtstype>Complete chain</sdtstype>
<ptvctcnt>61808</ptvctcnt>
</sdtsterm>
</ptvctinf>
</spdoinfo>
<spref>
<horizsys>
<planar>
<gridsys>
<gridsysn>State Plane Coordinate System 1983</gridsysn>
<spcs>
<spcszone>2800</spcszone>
<transmer>
<sfctrmer>0.999967</sfctrmer>
<longcm>-71.666667</longcm>
<latprjo>42.500000</latprjo>
<feast>984250.000000</feast>
<fnorth>0.000000</fnorth>
</transmer>
</spcs>
</gridsys>
<planci>
<plance>coordinate pair</plance>
<coordrep>
<absres>0.000512</absres>
<ordres>0.000512</ordres>
</coordrep>
<plandu>survey feet</plandu>
</planci>
</planar>
<geodetic>
<horizdn>North American Datum of 1983</horizdn>
<ellips>Geodetic Reference System 80</ellips>
<semiaxis>6378137.000000</semiaxis>
<denflat>298.257222</denflat>
</geodetic>
</horizsys>
</spref>
<eainfo>
<overview>
<eaover>
The dataset includes 7 attributes, as follows:

1.  LU4 - 4-digit integer describing the land use feature.  See
LUSTANDARDS.doc for further information on the code values.
2.  LU4_Desc - a text field containing the description of LU4
3.  Developed - a 0/1 field to flag land use features that are considered
developed.  A value of 1 was applied to all land use codes in the general
&quot;Urban and Built-up Land&quot; category (all LU4 codes between 1120 and 1800),
as well as the features coded as &quot;Other Agricultural Land&quot; (LU4 code 2900).
4.  Town - a text field containing the town name
5.  FIPS - 4-digit Federal Information Processing System code for the town
6.  RPA - with value of 8 (Rockingham Planning Commission) or 9 (Strafford
Regional Planning Commission)
7.  Acres - the size of the land use feature as calculated by the software.
</eaover>
<eadetcit>
None
</eadetcit>
</overview>
</eainfo>
<distinfo>
<distrib>
<cntinfo>
<cntorgp>
<cntorg>Earth Systems Research Center, University of New Hampshire</cntorg>
<cntper>GRANIT Database Manager</cntper>
</cntorgp>
<cntpos>GRANIT Database Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>Morse Hall, University of New Hampshire</address>
<city>Durham</city>
<state>NH</state>
<postal>03824</postal>
<country>US</country>
</cntaddr>
<cntvoice>603-862-1792</cntvoice>
<cntfax>603-862-0188</cntfax>
<cntemail>granit@unh.edu</cntemail>
<hours>8:30AM-5PM. EST</hours>
</cntinfo>
</distrib>
<resdesc>Downloadable Data</resdesc>
<distliab>
Digital data in NH GRANIT represent the efforts of the contributing agencies to record
information from the cited source materials. Earth Systems Research Center, under
contract to the NH Office of Energy and Planning, and in consultation with cooperating
agencies, maintains a continuing program to identify and correct errors in these
data. OEP, ESRC, and the cooperating agencies make no claim as to the validity or
reliability or to any implied uses of these data.
</distliab>
<stdorder>
<digform>
<digtinfo>
<formname>ESRI shapefile</formname>
<transize>90 MB</transize>
</digtinfo>
<digtopt>
<onlinopt>
<computer>
<networka>
<networkr>&lt;URL:  http://www.granit.unh.edu&gt;</networkr>
</networka>
</computer>
</onlinopt>
</digtopt>
</digform>
<fees>
No charge when downloaded from the Internet.  Cost of reproduction for provision on
CD/ROM or other media.
</fees>
<ordering>Email GRANIT (granit@unh.edu) or order from web site (www.granit.unh.edu).</ordering>
<turnarnd>Two weeks.</turnarnd>
</stdorder>
<techpreq>None.</techpreq>
</distinfo>
<metainfo>
<metd>20170712</metd>
<metc>
<cntinfo>
<cntorgp>
<cntorg>Earth Systems Research Center, University of New Hampshire</cntorg>
<cntper>GRANIT Database Manager</cntper>
</cntorgp>
<cntpos>GRANIT Database Manager</cntpos>
<cntaddr>
<addrtype>mailing and physical address</addrtype>
<address>Morse Hall, University of New Hampshire</address>
<city>Durham</city>
<state>NH</state>
<postal>03824</postal>
</cntaddr>
<cntvoice>603-862-1792</cntvoice>
<cntfax>603-862-0188</cntfax>
<cntemail>granit@unh.edu</cntemail>
<hours>8:30AM-5PM, EST</hours>
</cntinfo>
</metc>
<metstdn>FGDC Content Standards for Digital Geospatial Metadata</metstdn>
<metstdv>FGDC-STD-001-1998</metstdv>
<mettc>local time</mettc>
<metextns>
<onlink>http://www.esri.com/metadata/esriprof80.html</onlink>
<metprof>ESRI Metadata Profile</metprof>
</metextns>
</metainfo>
</metadata>
