1 / 27

CadNSDI_MT and the MT CATSPAW Project

CadNSDI_MT and the MT CATSPAW Project. CadNSDI_MT - CadNSDI Montana is a GIS representation of the best estimated positions of the components of the PLSS.

cayla
Télécharger la présentation

CadNSDI_MT and the MT CATSPAW Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CadNSDI_MT and the MT CATSPAW Project

  2. CadNSDI_MT - CadNSDI Montana is a GIS representation of the best estimated positions of the components of the PLSS. Vision – is the vision of BLM’s National PLSS Data Steward, that digital PLSS information be maintained, integrated, enhanced and distributed in a manner where one trusted data source is accepted by users as the best available and most current. It should meet the needs of the geospatial, GIS, mapping, planning and surveying communities – In Montana that trusted source will be Montana State Library Geographic Information Program • Not a surveying vs. GIS thing • Not a new GCDB • Not a hostile takeover • Not really asking permission – this has to be done

  3. Why State Custodianship of CadNSDI? • The BLM Cadastral Survey does not understand GIS user needs • Raw measurements from original plats and notes are removed from CadNSDI – it is a GIS product • The BLM Cadastral Survey does not have staff with the GIS skills to maintain and enhance a GIS product • Turn around times are too slow between federal CadNSDI updates

  4. Why New Workflows? • Montana is a PLSS state – many GIS databases require and accurate digital representation • Vertically integrated data needs to adjust as the PLSS adjusts • US Census and USGS will be incorporating CadNSDI into their products • Local Governments are adopting new cadastral workflows • Rigid GMM processes aren’t resulting in needed change • We need to quit whining and take charge

  5. CadNSDI – One Sick Kitty

  6. The Birth of the Cat

  7. Where We Have Been – Where we are at • November – Project kickoff; two days of onsite meetings in Helena • December - Migrate pilot data (Missoula County) • CadNSDI 2 • Original Measurements and survey info from GCDB • Missoula County Control • Document workflows • January – Training, testing with Esri – 3 days • February, March, April – Data Migration • May – learning and testing the adjustment processes, testing and documenting boundary work flows

  8. Streamlined Parcel Workflows • Control • PLSS • Parcels • Administrative Boundaries • Other Data

  9. Vertically integrated data is auto adjusted using Esri software

  10. Documentation CadNSDI Preparation and Migration Procedure 1. Because you will need to process a large amount of data, Esri recommends using an SDE database. We ultimately encountered issues with permissions, versioning, and processing time associated with using an SDE and/or network issues which required us to use a FileGDB on a local machine. a.Create a new feature dataset in your SDE or FileGDB. Select the NAD_1983_2011_StatePlane_Montana_FIPS_2500 projection and a Vertical Coordinate System of NAVD 1988. Use this feature dataset to project all of the CadNSDI data into, as described in step 7. 2. Ideally, whatever machine you are using should have ArcGIS Desktop 10.2.1. 3. Copy the Tools folder containing the Models_edited, LayerFiles,and Scripts folder from \\Mslhlnfileprn01\geoinfo\MSDI\Cadastral\PLSS_Stewardship\Implementation as well as the TOPO_LOADER_6_RULES.rul and place it on the local drive. 4. Create a folder connection in ArcCatalog. 4. From \\mslhlnfileprn01\geoinfo\MSDI\Cadastral\CadNSDI\CadNSDI_V2_2014-02-11 copy CadNSDI v.2 to the local drive.

  11. Lessons Learned • Your bible http://www.esri.com/library/whitepapers/pdfs/loading_data_parcel_fabric.pdf • Loading twemtu parcels is a lot easier than loading to two million • Start cleaning your data now • Allow plenty of time • Plan and document

  12. Minimum Requirements • A full-time cadastral expert • Must understand the CadNSDI schema • Preferably has worked with the parcel fabric • A close working relationship with your geodetic control steard • A robust system architecture • We are still trying to document what that is • Conducting an Esri Health Check of our system • Patience – there will be good days and bad

  13. Where We Are Going CadNSDI_MT CadNSDI_MT Data Xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx CadNSDI_MT_Documentation Xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Applications None at this time About CadNSDI_MT is a GIS representation of the best estimated positions of the components of the Public Land Survey System. The custodian for CadNSDI_MT is the Montana State Library. Document link 1 Document link 1 Contact Info CadNSDI_MT Accuracy Enhancement Projects

  14. Change Management • MSL Geographic Information Program are MSDI stewards for Cadastral, Geodetic Control and Boundaries • MSL has proposed state custodianship of the GIS database associated with the PLSS – BLM has accepted • Change Management Board would operate much like other MSDI workgroups and advise the MSDI stewards (MSL) • Would represent stakeholders and interest groups • A working group of MLIAC • Has BLM buy in. BLM’s National Data Steward (Bob Ader) and FGDC Cadastral Co-chair (Nancy Von Meyer)request observer status to develop this as a national model – 35K task order to fix priority areas

  15. Tracking the Cat

More Related