20250106
14570700
1.0
FALSE
TOPO_Contours_01ft_2022
002
218882.495446
432368.897869
22874.715266
341244.053592
1
Projected
GCS_NAD_1983_2011
Linear Unit: Foot_US (0.304801)
NAD_1983_2011_StatePlane_Rhode_Island_FIPS_3800_Ft_US
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.5.0'><WKT>PROJCS["NAD_1983_2011_StatePlane_Rhode_Island_FIPS_3800_Ft_US",GEOGCS["GCS_NAD_1983_2011",DATUM["D_NAD_1983_2011",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Transverse_Mercator"],PARAMETER["False_Easting",328083.3333333333],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",-71.5],PARAMETER["Scale_Factor",0.99999375],PARAMETER["Latitude_Of_Origin",41.08333333333334],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",6568]]</WKT><XOrigin>-18120300</XOrigin><YOrigin>-47742100</YOrigin><XYScale>3048.0060960121928</XYScale><ZOrigin>-710.06182350000699</ZOrigin><ZScale>4194304001953.124</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.0032808333333333331</XYTolerance><ZTolerance>0.0032808333333333331</ZTolerance><MTolerance>0.001</MTolerance><HighPrecision>true</HighPrecision><WKID>103144</WKID><LatestWKID>6568</LatestWKID></ProjectedCoordinateSystem>
20251027
12255000
20251027
12255000
150000000
5000
FGDC
Suzee Parsons
Fugro Geospatial
301-948-8550
4991 New Design Road, Suite 105
Frederick
MD
21703
US
s.parsons@fugro.com
Monday to Friday 8:00am to 5:00pm EST
20251027
ArcGIS Metadata
1.0
Enterprise Geodatabase Feature Class
TOPO_Contours_01ft_2022
2025-10-27
Fugro Geospatial, Fugro Geospatial
vector digital data
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This hosted feature layer has been published in RI State Plane Feet NAD 83 (2011).</SPAN></P><P><SPAN>RI_StatewideEnhancements_D24 project called for the planning, processing, and derivative products of lidar data that were collected at an aggregate nominal pulse spacing (ANPS) of 0.35 meters (8ppsm). Project specifications are based on the U.S. Geological Survey National Geospatial Program Lidar Base Specification, 2022 rev. A. The data was developed based on a horizontal projection/datum of NAD83 (2011), State Plane Coordinate System, Rhode Island, FIPS 3800, US Survey Feet vertical datum of NAVD88 (GEOID18). Contour data was delivered as 1ft contours, via feature class in file geodatabase format.</SPAN></P></DIV></DIV></DIV>
1-ft contours developed from the RI_2022 Lidar project.
USGS, Fugro, RIGIS
Suzee Parsons
Fugro Geospatial
301-948-8550
4991 New Design Road, Suite 105
Frederick
MD
21703
US
s.parsons@fugro.com
Monday to Friday 8:00am to 5:00pm EST
Geographic Names Information System
United State, New England, Rhode Island
ISO 19115 Topic Category
elevation
ISP 19115 Topic Category
Model, LAS Point Cloud, Classified LAS, Swath LAS, Remote Sensing, Lidar, Contours
elevation
Model
LAS Point Cloud
Classified LAS
Swath LAS
Remote Sensing
Lidar
Contours
United State
New England
Rhode Island
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>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. Any conclusions drawn from the analysis of this information are not the responsibility of the U.S. Geological Survey or its partners. Acknowledgement of the U.S. Geological Survey would be appreciated for products derived from these data.</SPAN></P></DIV></DIV></DIV>
This dataset is provided 'as is.' The producer(s) of this dataset, contributors to this dataset, the Rhode Island Geographic Information System (RIGIS) consortium, the State of Rhode Island, and the University of Rhode Island do not make any warranties of any kind for this dataset, and are not liable for any loss or damage however and whenever caused by any use of this dataset.
No restrictions apply to these data
Esri ArcGIS 13.5.3.57366
true
-71.902075
-71.116225
42.019836
41.145008
-27.000000
811.000000
ground condition
2022-03-26
2023-03-30
-27.000000
811.000000
CONTRACTOR: Fugro Geospatial, Inc. Derived from: USGS Contract No. G17PC00015 CONTRACTOR: Fugro Geospatial, Inc. SUBCONTRACTOR: Terrasurv, Inc. Ground control and checkpoints collected by Terrasurv, Inc. All processing was completed by the prime contractor.
Contour File Type = GDB Contour Elevation Units = Feet
1
-71.901863
-71.116225
42.019834
41.145433
For the prior data, from which this project was derived: Compliance with the accuracy standard was ensured by the collection of ground control and the establishment of GPS base stations in the project area. The following checks were performed: 1) The lidar data accuracy was validated by performing a full boresight adjustment and then checking it against the ground control prior to generating a digital terrain model (DTM) or other products. 2) Lidar elevation data was validated through an inspection of edge matching and visual inspection for quality (artifact removal). The following software was used for the validation: 1) RiProcess 1.8.3, RiWorld 5.0.2, RiAnalyze 6.2, RiServer 1.99.5; and 2) Fugro proprietary software; 20220520.
The DSM is based on the lidar first returns. First returns will have some no-data areas, especially in water (where topographic lidar does not reflect well) and on some low-reflective building materials. Unlike a hydro-flattened bare-earth DEM, the no-data areas in a DSM are not interpolated. It is possible to interpolate these areas, but this would introduce interpolation artifacts, and therefore the data was not interpolated. Also, the DSM is not hydro-flattened as that would result in flattening trees overhanging the hydro features, which should be avoided in a DSM product.
This data was produced to meet ASPRS Positional Accuracy Standards for Digital Geospatial Data (2014) for a 10-cm RMSEz Vertical Accuracy Class.
Fugro produced one foot topographic contours from the RI_StatewideLidar_2022_D22_QL1 hydro breaklines and lidar data. The following step-by-step procedure was utilized for DTM development and contour generation. The DTM file is composed of random data points (X,Y and Z) and three dimensional breaklines. The relationship of points to breaklines and the density and position of points will vary depending on the complexity and severity of the terrain. Breaklines were requested to collect as needed along the edges of roads, stream banks and centerlines, ridges, and other features where the slope of the terrain changes and where necessary. Scanning over the Mr Sids, we decided the quality of the Lidar defined the road edges well enough that the extra breaklines were not needed. Some single line drainage was added to shape the contours. No topology was run to search for crossing contours in this auto generation process. 1) In editing, TerraSolid modules TerraScan and TerraModeler were used to automatically define and thin the points needed for any terrain change. 2) The filtered DSM and breaklines compiled along streams, ridge lines, roads, hydrographic features, bridges, and other areas of topographic significance were QCed in MicroStation before generating the contour deliverables. 3) Following the compilation of the breaklines a technician brings the LAS data and the breakline data into the TerraSolid software suite. A process within the TerraScan module known as Contour Keypoint is run. This process analyzes all available data (LAS and breaklines) and filters it leaving only those critical points and breaklines necessary to support the desired output, in this case 1 foot contours. The results are reviewed for quality and completeness and then a batch contour generation process is started. During this step contours are generated over the entire project area. A conversion from Microstation dgn format to an Arc GeoDatabase was than processed. 4) In an ESRI Arc environment the technician set the required project datum and projection and created a TIN (triangulated irregular network). Final edit work is done on the data to convert it to the desired GeoDataBase deliverable. The dataset was viewed over the orthos before the final conversion. The contours were then converted to Arc/Info where final QC ARC Topology was run to verify that no contours were crossing. The contours were delivered as a merged file in ArcGIS File-GeoDataBase.
2025-04-18
Suzee Parsons
Fugro Geospatial
301-948-8550
4991 New Design Road, Suite 105
Frederick
MD
21703
US
s.parsons@fugro.com
Monday to Friday 8:00am to 5:00pm EST
Lidar Data, Hydro Breaklines
Contours
Data was delivered as 6 separate feature layers. A_Contours, B_Contours, C_Contours, D_Contours, E_Contours, Island_Contours. These layers were combined using the APPEND command to create one statewide contour layer.
2025-10-23
RIGIS Data Manager
URI Environmental Data Center
401
Kingston
RI
02881
rigis@uri.edu
Ran check geometry command on the layer - 25 short segments were reported. Ran REPAIR GEOMETRY to fix this error.
2025-10-23
RIGIS Data Manager
URI Environmental Data Center
401
Kingston
RI
02881
rigis@uri.edu
Data contributed to RIGIS by Fugro. Minor formatting and content updates made to metadata before publication to RIGIS.
2025-10-23
RIGIS Data Manager
URI Environmental Data Center
401
Kingston
RI
02881
rigis@uri.edu
0
TOPO_Contours_05ft_2022
Feature Class
0
OBJECTID
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
OBJECTID
OID
4
10
0
SHAPE
Feature geometry.
Esri
Coordinates defining the features.
shape
Geometry
8
0
0
Elevation
Elevation
Double
8
38
8
DGN_Level
DGN_Level
Double
8
38
8
ContourType
ContourType
Integer
4
10
0
UnitFT
UnitFT
String
50
0
0
Interval
Interval
Integer
4
10
0
st_length(shape)
st_length(shape)
Double
0
0
0
dataset
EPSG
8.2.10(10.3.1)
Simple
FALSE
0
TRUE
FALSE