Digital Mapping Techniques 04 MIGRATING FROM ARCINFO WORKSTATION

  • Slides: 37
Download presentation
Digital Mapping Techniques ‘ 04 MIGRATING FROM ARCINFO WORKSTATION TO ARCGIS By Vic Dohar,

Digital Mapping Techniques ‘ 04 MIGRATING FROM ARCINFO WORKSTATION TO ARCGIS By Vic Dohar, Natural Resources Canada

Scope 4 Managing datasets in a map production environment 4 No intention to create

Scope 4 Managing datasets in a map production environment 4 No intention to create a data model or replicate NADM 4 Geodatabase used for map production 4 Snapshot of current migration strategies from workstation to Arc. GIS (work in progress)

Current Map Production at GSC 4 A-series and Open File geology maps since 4

Current Map Production at GSC 4 A-series and Open File geology maps since 4 4 1994, 50 to 70 maps per year Data is managed in the coverage model using Arc. Info Workstation 8. 3 GEMS application Digital data adheres to Cartographic Digital Standards (CDS) Stored/archived in Arc. SDE (not in a geodatabase)

Migrating to Arc. GIS 4 Change in ESRI technology forces us to change 4

Migrating to Arc. GIS 4 Change in ESRI technology forces us to change 4 Geodatabases provide domains and custom 4 4 topology, used to validate features Arc. GIS is not restricted to coverages model, various formats from various sources Arc. GIS provides connections to databases Open development for customizing Arc. Map Tiered license: Arc. View, Arc. Editor, Arc. Info

Migration Goals 4 Develop a geodatabase schema for managing spatial geology data 4 Make

Migration Goals 4 Develop a geodatabase schema for managing spatial geology data 4 Make use of domains for standardizing feature names and validating features 4 Produce similar maps with Arc. Map as with workstation, faster and more efficiently

Migration Strategy 4 Three stages (Arc. GIS Help): 1. Use existing data with Arc.

Migration Strategy 4 Three stages (Arc. GIS Help): 1. Use existing data with Arc. Map 2. Data management and editing using the geodatabase 3. Convert to geo-processing tools, Arc. GIS 9. 0 4 Decided to bundle stages 1 and 2, due to available resources, training, and managing a production environment

What is a Geodatabase? 4 Arc. GIS Help 4 ESRI press • Publications: Modeling

What is a Geodatabase? 4 Arc. GIS Help 4 ESRI press • Publications: Modeling Our World 4 Resources available from www. esri. com • Download sample geodatabases

Geodatabase Case Studies

Geodatabase Case Studies

Designing a Geodatabase 4 Several different methods 1) Arc. Catalog menus and wizards 2)

Designing a Geodatabase 4 Several different methods 1) Arc. Catalog menus and wizards 2) CASE tools using Visio (UML) 3) Geodatabase Designer (XML) 4 Experimented with importing existing coverages into a personal geodatabase. 4 Organizing data into manageable features

Geodatabase Designer 4 Export schema to XML. Edit, modify using an XML editor 4

Geodatabase Designer 4 Export schema to XML. Edit, modify using an XML editor 4 XML schema can be imported or distributed 4 Integrated with Arc. Catalog 4 Free!

Geodatabase for Map Production 4 Separate geodatabase schemas for bedrock 4 4 geology data,

Geodatabase for Map Production 4 Separate geodatabase schemas for bedrock 4 4 geology data, surficial geology data and cartographic elements Store datasets, simple features and tables Domains and topology used to validate features Sub-types used with domains to group/categorize simple features Use relationship classes to define relates

Surficial Units Feature Class 4 Single field used to differentiate geology polygon units

Surficial Units Feature Class 4 Single field used to differentiate geology polygon units

Surficial Geodatabase 4 Map with compound units and veneers

Surficial Geodatabase 4 Map with compound units and veneers

Surficial Unit Composition Table

Surficial Unit Composition Table

Surficial Unit Composition Table

Surficial Unit Composition Table

Surficial Legend Table

Surficial Legend Table

Surficial Unit Composition Table

Surficial Unit Composition Table

Complex IDs Table 4 Description of relationship involving complex units for all surficial maps

Complex IDs Table 4 Description of relationship involving complex units for all surficial maps

Surficial Geodatabase 4 Labeling polygons using a table

Surficial Geodatabase 4 Labeling polygons using a table

Surficial Unit Label Table

Surficial Unit Label Table

How it all fits together! Feature class MAPUNIT * Unit labels table MAPUNIT *

How it all fits together! Feature class MAPUNIT * Unit labels table MAPUNIT * 1 1 Unit composition table MAPUNIT VENEER PRIMARY_UNIT * 1 * Legend table LEGUNIT DESCRIPTION MAPLABEL SECONDARY_UNIT * 1 COMPLEX_ID * Complex ID table COMPLEX_ID DESCRIPTION

How it all fits together! 4 Expressed in relationship classes

How it all fits together! 4 Expressed in relationship classes

How it all fits together! 4 Shown when performing a query or identify

How it all fits together! 4 Shown when performing a query or identify

Surficial Geology Topology 4 Topology can only exist for participating features within a dataset

Surficial Geology Topology 4 Topology can only exist for participating features within a dataset 4 Implementing two simple rules: 1. Surficial units polygons must not overlap 2. Contacts must overlap boundary of surficial units

Geomorphology Line, Point and Area Features 4 Remaining surficial features are classified into point,

Geomorphology Line, Point and Area Features 4 Remaining surficial features are classified into point, line and area simple feature classes 4 Each of the feature classes contains a subtype field used to classify or categorize the features 4 Features are assigned a coded value from a domain that pertains to the sub-type to which it belongs

Coded Value Domain 4 Domains are properties of the geodatabase

Coded Value Domain 4 Domains are properties of the geodatabase

Sub-Type Field 4 Sub-types are properties of the feature class

Sub-Type Field 4 Sub-types are properties of the feature class

Geomorphology Line Feature Class Sub-type Coded value from domain

Geomorphology Line Feature Class Sub-type Coded value from domain

Making Maps with Arc. Map

Making Maps with Arc. Map

Style Files and Symbols 4 Symbolsets from Workstation that utilize custom fonts (IGL, True.

Style Files and Symbols 4 Symbolsets from Workstation that utilize custom fonts (IGL, True. Type) do not import into style files 4 All line, marker, and pattern symbols require to be created from scratch 4 Thus far have converted all shade colours, and most line and marker symbols 4 Created true type font of point symbols

Map Surround Generation 4 Insert Word, Corel. Draw, other files as objects 4 Custom

Map Surround Generation 4 Insert Word, Corel. Draw, other files as objects 4 Custom application for generating title block, and recommended citation, and other surround information 4 Design specifications and content are XML based 4 Uses metadata that user enters in forms 4 Ensures consistent high quality map product, facilitates map production

Legend Generation 4 Current legend generation using Arc. Info workstation is accomplished using a

Legend Generation 4 Current legend generation using Arc. Info workstation is accomplished using a text file and an AML 4 Proposing to store legend information in an XML file • Contain units, minerals, lithology, and symbols • Contain description as well as hierarchical levels 4 Currently developing a XML schema to store this information

Legend Generation 4 Design interface to populate XML file 4 VBA script to render

Legend Generation 4 Design interface to populate XML file 4 VBA script to render legend in Arc. Map using native graphics (boxes, lines, text, etc…) 4 XML file is portable and can be used for other applications

Connections to Databases 4 Connect to geochronology database to display point data • Script

Connections to Databases 4 Connect to geochronology database to display point data • Script to generate graphic GSC lab # Elevation Age Material • Not required to store age data 4 Minerals database x Mn • Use of table for labeling point data 4 Field observations database, others ? ? ?

Remaining Issues and Goals 4 The verdict is not in on a final geodatabase

Remaining Issues and Goals 4 The verdict is not in on a final geodatabase schema 4 Better labeling of features to avoid managing/editing annotation (Maplex) 4 Implement in map production 4 Next year have all pieces/connections in place (GDR, SDE geodatabase, NADM)

Acknowledgements Parm Dhesi, GIS Specialist & Symbols Roger Mac. Leod, GIS Specialist & Symbols

Acknowledgements Parm Dhesi, GIS Specialist & Symbols Roger Mac. Leod, GIS Specialist & Symbols Norah Brown, Arc. Objects & XML Dave Everett, GIS Specialist Sheila Hynes, GIS Specialist Barb Szlavko, Arc. SDE/Oracle Admin Terry Houlahan, Arc. SDE/Oracle Admin

Contact me at… Vic Dohar Cartographic Applications Specialist Publishing Services Subdivision ESS Info Division

Contact me at… Vic Dohar Cartographic Applications Specialist Publishing Services Subdivision ESS Info Division Earth Sciences Sector Natural Resources Canada 601 Booth Street Ottawa, Ontario, Canada K 1 A 0 E 8 telephone: 613 -943 -2693 fax: 613 -952 -7308 email: vdohar@NRCan. gc. ca web: www. nrcan. gc. ca/ess/carto