1 / 37

MIGRATING FROM ARCINFO WORKSTATION TO ARCGIS

Digital Mapping Techniques ‘04. MIGRATING FROM ARCINFO WORKSTATION TO ARCGIS. By Vic Dohar, Natural Resources Canada. Scope. Managing datasets in a map production environment No intention to create a data model or replicate NADM Geodatabase used for map production

Leo
Download Presentation

MIGRATING FROM ARCINFO WORKSTATION TO ARCGIS

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. Digital Mapping Techniques ‘04 MIGRATING FROM ARCINFO WORKSTATION TO ARCGIS By Vic Dohar, Natural Resources Canada

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

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

  4. Migrating to ArcGIS • Change in ESRI technology forces us to change • Geodatabases provide domains and custom topology, used to validate features • ArcGIS is not restricted to coverages model, various formats from various sources • ArcGIS provides connections to databases • Open development for customizing ArcMap • Tiered license: ArcView, ArcEditor, ArcInfo

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

  6. Migration Strategy • Three stages (ArcGIS Help): • Use existing data with ArcMap • Data management and editing using the geodatabase • Convert to geo-processing tools, ArcGIS 9.0 • Decided to bundle stages 1 and 2, due to available resources, training, and managing a production environment

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

  8. Geodatabase Case Studies

  9. Designing a Geodatabase • Several different methods1) ArcCatalog menus and wizards2) CASE tools using Visio (UML) 3) Geodatabase Designer (XML) • Experimented with importing existing coverages into a personal geodatabase. • Organizing data into manageable features

  10. Geodatabase Designer • Export schema to XML. Edit, modify using an XML editor • XML schema can be imported or distributed • Integrated with ArcCatalog • Free!

  11. Geodatabase for Map Production • Separate geodatabase schemas for bedrock 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

  12. Surficial Units Feature Class • Single field used to differentiate geology polygon units

  13. Surficial Geodatabase • Map with compound units and veneers

  14. Surficial Unit Composition Table

  15. Surficial Unit Composition Table

  16. Surficial Legend Table

  17. Surficial Unit Composition Table

  18. Complex IDs Table • Description of relationship involving complex units for all surficial maps

  19. Surficial Geodatabase • Labeling polygons using a table

  20. Surficial Unit Label Table

  21. How it all fits together! Feature class Unit labels table * 1 * Unit composition table 1 * * * * Complex ID table Legend table 1 1

  22. How it all fits together! • Expressed in relationship classes

  23. How it all fits together! • Shown when performing a query or identify

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

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

  26. Coded Value Domain • Domains are propertiesof the geodatabase

  27. Sub-Type Field • Sub-types are properties of the feature class

  28. Coded value from domain Sub-type Geomorphology Line Feature Class

  29. Making Maps with ArcMap

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

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

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

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

  34. Connections to Databases • Connect to geochronology database to display point data • Script to generate graphic • Not required to store age data • Minerals database • Use of table for labeling point data • Field observations database, others ??? xMn

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

  36. Acknowledgements Parm Dhesi, GIS Specialist & SymbolsRoger MacLeod, GIS Specialist & SymbolsNorah Brown, ArcObjects & XMLDave Everett, GIS SpecialistSheila Hynes, GIS SpecialistBarb Szlavko, ArcSDE/Oracle AdminTerry Houlahan, ArcSDE/Oracle Admin

  37. Contact me at… Vic DoharCartographic Applications SpecialistPublishing Services SubdivisionESS Info DivisionEarth Sciences SectorNatural Resources Canada601 Booth StreetOttawa, Ontario, CanadaK1A 0E8telephone: 613-943-2693fax: 613-952-7308email: vdohar@NRCan.gc.ca web: www.nrcan.gc.ca/ess/carto

More Related