Geodetic Database: Minnesota Department of Transportation (Mn/DOT)

The Geodetic Database contains information on permanent geodetic control marks located in Minnesota or just outside its boundaries. Permanent geodetic control marks are established for the purpose of providing precise horizontal and vertical control positions for the registration of surveying and mapping activities in the local area. Information about the location of an object based on its geodetic location locates that object in a worldwide geographic information system. The marks have unique identification and year established stamped on the monument disk, usually an 89 mm (3.5 inch) diameter brass or aluminum disk. Monuments consist of material (concrete or metal) that is meant to stay in place for 50 to 100 years or more, and have little or no movement due to frost action or activity near the monument. The marks have been established by all levels of government in Minnesota, and they are referenced to the National Geodetic Reference System (NAD 1927, NAD 1983, NGVD 1929, and NAVD 1988). The Federal Government supports monumentation at the state level by providing technical expertise, adjustments of the data, and maintenance of the National Geodetic Reference System through its State Advisor Program.

Additional Info

Field Value
Last Updated August 25, 2015, 10:02
Created September 30, 2014, 14:13
dsAccessConst Contact Distributor
dsCurrentRef Starts with the year the mark was set with history of years that the mark was adjusted and recovered.
dsModifiedDate 2015-05-19 23:49:50
dsOriginator Minnesota Department of Transportation (Mn/DOT)
dsPurpose To provide geodetic control information in an electronic medium that will allow convenient data access, modification, and distribution. The data stored in the database allows the user to: 1. Create reports on all geodetic control monuments that reside in a specified area (by county, by township, range, or section, by Latitude and Longitude, etc.) 2. Create a computer file of geodetic control mark data 3. Create a file for input in a GIS format

Dataset extent