1 / 19

Integrating CADD and GIS Data

Integrating CADD and GIS Data. CADD. GIS. BAAMA Sept. 27, 2007 Presented by: Reneé Gerasimtchouk , GIS Specialist Lysée Moyaert , GIS / CADD Manager Mineta San Jos é International Airport. Case Study. Problem Have many CADD files, how to get into GIS? How to keep these two in sync?

jola
Download Presentation

Integrating CADD and GIS Data

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. Integrating CADD and GIS Data CADD GIS BAAMA Sept. 27, 2007 Presented by: Reneé Gerasimtchouk, GIS SpecialistLysée Moyaert, GIS / CADD ManagerMineta San José International Airport

  2. Case Study • Problem • Have many CADD files, how to get into GIS? • How to keep these two in sync? • Requirements • Solution must preserve our CADD Standards while importing and exporting (Airport uses modified National CADD Standards) • CADD files must be imported into our SDSFIE schema in Oracle (Spatial Data Standards for Facilities, Infrastructure, and Environment) • Airport’s custom Coordinate System must be maintained • Error trapping prior to loading • Easy loading and exporting of large amounts of CADD data • Solution • A custom application using FME that is user friendly and can both import and export CADD files to and from GIS.

  3. CADD Standards

  4. Solution • What is the Data Integration Application? • The Data Integration Application is a combination of a thick client application using FME Suite for Oracle and server side database objects, including tables, triggers, and PL/SQL packages. • Focuses on a three-tier deployment: data storage in Oracle, rules about how data is processed, and a presentation layer or user interface.

  5. Loading Data Data Integration Application first runs series of checks • Scans CADD file & displays a list of layers found • References the CROSSWALK table for valid CADD and GIS relationship • Allows user to select layers to be loaded

  6. Crosswalk table • Crosswalk table managed directly in the Data Integration Tool • Manages the relationship between CADD layers and GIS tables • Used as a template for both importing and exporting data

  7. Validation of CADD File • Validate button transfers data to the CADD Staging Table • Runs a series of Oracle scripts designed to validate the data • Verify GIS table has “USER_FLAG” column (will load CADD layer name here) • Verify geometry is valid for Oracle • Runs logic for “-N” , “-E”, and “-R” status • (-N = new, -E = existing, -R = remove) • Option of “Initial Load” and “Regular Load” • Reports findings to user

  8. Validation Results CADD layers with a valid status can be loaded into Oracle Invalid status layers must be corrected and revalidated again

  9. GIS data • Data now loaded into Oracle • Application loads CADD layer name into USER_FLAG field • Used for exporting and maintains CADD standard layer name • Data added (STRUCT_B and FLOOR_NUM are required for exporting)

  10. Application also has a log file Reports the CADD layers loaded Number of features loaded into the GIS Number of features that were not loaded Log File

  11. Data Input flow diagram

  12. Exporting • Data Integration Application can easily export data from GIS back into a CADD drawing • Again uses the CROSSWALK table for relationship from GIS back to CADD • Also uses a Drawing Set .mdb file as a template to extract the various CADD levels from the GIS table and group into individual drawing sets • Uses the STRUCT_B and FLOOR_NUM fields from the GIS table for grouping

  13. Data export flow diagram

  14. Exported CADD File

  15. Pros Easy to load large amounts of CADD data quickly Uses automated rules to validate data Easy to export Automatically updates GIS field with the CADD level name Manages CADD layer status with –E, –N, and –R Maintains our CADD Standard format Pros and Cons Cons • Can be cumbersome process for very small amounts of CADD data • Client software written in VB .NET – need to know programming to change or update the application as well as package and procedure maintainence • Troubleshooting error messages can be difficult due the various components • Have to keep CROSSWALK table and Drawing Set file up to date

  16. Other Methods Import using GeoMedia • Connect to Oracle • Display CADD files • Change feature class • Run topological rules • Or directly drawing in or deleting elements • Can be quicker in dealing with small amounts of data

  17. Other Methods Export from GeoMedia • Easy to export however does not keep CADD layer name • Exports all elements from GIS table – no grouping • Only way to group is query out data from GIS prior to exporting – too time consuming

  18. Data Integration Application is a client side application Uses Safe Software’s Feature Manipulation Engine (FME) Suite for Oracle to import data Uses a series of PL/SQL procedures to validate data Built on Oracle 9i, now using Oracle 10g Easy to use for large amounts of data Maintains our CADD Standards as well as correlates to our SDS spatial database schema Summarize

  19. Questions? Thank You! RGerasimtchouk@sjc.org LMoyaert@sjc.org www.nationalcadstandard.org www.sdsfie.org www.safe.com

More Related