A06-MappingNewInfrastructure.pdf

National Park Service

ROW Permit Mapping Requirements: New Infrastructure

All reported Global Positioning System (GPS) point features noted herein require, at a minimum, field-collected GPS data differentially corrected to sub-meter accuracy (differential GPS or

DGPS). The correction process can be achieved either in real-time or by post-processing the data using a service like the Online Positioning User Service (OPUS) operated by United States

National Geodetic Survey (NGS).

The following deliverables are required as part of every ROW permit application:

1. AutoCAD (.dwg or .dxf), GIS (.shp or .gdb), or Google Earth (.kmz) files including the required information and meeting the following requirements:

a. AutoCAD or GIS files shall be projected to the local state plane coordinate system covering the project area in NAD83 or future state plane systems (ensure that the datum realization is specified in the files).1

b. Features will include:

i. points, lines or polygons2 identifying the permit area, and associated control points;

ii. all DGPS points as required below; and

iii. feature attributes (e.g., acreage, Permittee name) or applicable layer names.

c. Each file shall include an associated metadata file with fields describing the attributes, data collection method and accuracy of the dataset. Metadata must be

Federal Geographic Data Committee (FGDC) compliant (see the FGCD website).

2. Four 24” x 36” hard copies of the map(s). Linen or rag paper is not required.

3. A PDF file of each map, Adobe file version 1.7 or higher

Regardless of this standard, in any situation where the NPS unit and the regional ROW

Coordinator deem it appropriate, they may require the applicant to provide a formal survey and legal description. This survey and legal description must be signed by a licensed surveyor.

1 The current state plane coordinate system is NAD83. A new version, NAD 2022, is expected to be released in

2022.

2 Park staff may request point, line, or polygon data, depending on park needs and on the project. Generally, nonlinear ROW permit requests (such as for cell towers) will require polygons, while parks may vary between requiring points, lines, or polygons for linear ROW permit requests (such as power lines) depending on the project.

https://www.fgdc.gov/dataandservices/fgdcmeta

If the infrastructure has not yet been built, the maps must show:

1. Proposed permit area and associated features:

a. If the permitted area is a linear feature

i. DGPS points at the proposed beginning and terminus points within the park boundary, labeled with their respective coordinate pairs.

ii. Proposed centerline and proposed location of any poles or ground disturbance.

iii. The proposed width, length, and acreage of the permit area.

b. If the permit area is a non-linear feature

i. DGPS points at all proposed corners and angle points of the permit area, labeled with their respective coordinate pairs.

ii. Proposed tower location, and location of proposed appurtenances (buildings, fuel, etc.).

iii. The proposed acreage and dimensions of the permit area.

2. Crossings of property lines and NPS unit boundaries3

a. DGPS points must be included on all crossings of NPS property lines and NPS unit boundaries.

b. If within ¼ mile of NPS unit boundary, unit boundary must be shown if the map scale allows.

c. Identify any lands that are not administered by the NPS (e.g., such as inholdings) being crossed by the project area within the NPS unit.

d. Buildings, existing roads, and utilities located within 25 feet of the project area must be shown.

3. Access:

a. If access is along a road within the NPS unit, list the name of the road and the distance along the road needed for access to the permit area. Note whether the roads to be used for access are open to the public or are administrative access only.

3 NPS unit boundaries are the legislated (or proclaimed) boundaries of an NPS unit. Property lines are lines where NPS-managed land borders land owned by another entity or individual and may occur along a boundary or elsewhere inside a park if another entity or individual owns land within the NPS boundary.

b. If access is not along a public or administrative road, include DGPS points at the beginning and terminus points of the proposed project area access route(s).

4. Also include:

a. Township, section, and range if Public Land Survey System (PLSS) state, or the equivalent survey grid if it is not a PLSS state.

b. County, State, and NPS unit name (i.e., Yellowstone National Park)

c. The scale should be appropriate to show the requested ROW. The park may request a different scale as needed.

d. Map legend.

e. North arrow.

f. The map base may be aerial photography, USGS topographic base, or another base, subject to park approval.

5. Legal Description (may be attached as an exhibit to the map):

a. Linear ROWs

i. Legal description must be based on DGPS points for the centerline.

ii. Legal description must include courses and distances of the centerline.

iii. The entire area (in acres and square feet) must be included.

b. Nonlinear ROWs

i. Legal description must be based on DGPS points for all corners of the proposed ROW area.

ii. The entire area (listed in both acres and square feet) must be included.

6. Within 90 days of the completion of construction, the applicant must then provide a final as-built map and legal description meeting the standards for infrastructure that already exists, as set forth below. These final documents must be delivered to the NPS unit Superintendent.

This includes remeasuring all DGPS points to match actual as-built conditions.