![]() Spatially joined CTU events and mnctu09 feature classĤ. Created CTU events (from the CTU records centroid X,Y coordinates) in ArcMapģ. Downloaded CTU records from the Minnesota CTU database: Ģ. The checks were done using ESRI's ArcSDE and ArcMap software:ġ. Geological Survey's Geographic Names Information System or GNIS). MnGeo staff compared the attributes created for this project (the mnctu09 feature class - see Lineage field for description of how attributes were created) with the Minnesota CTU database (derived from the U.S. ![]() Initial Data Accuracy when CTU data was first created: Features that have had recent approved adjustments are generally more accurate than features that have not been edited since the first data was created. ![]() There is a continual effort to capture each approved boundary change at the highest possible accuracy and then to adjust the surrounding area to match. General accuracy varies between features due to initial content creation and subsequent boundary adjustment updates. The dataset is not intended for legal land survey use, and is best suited for general reference. All of the data sources reviewed and the final dataset were within the National Map Accuracy Standards for 1:24,000-scale maps which is +/- 40 feet (12 meters).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |