Using FME to Build an                                 2010:
                                                     An FME
En...
Project Purpose


  Build an Enterprise Database
    Parcels integrated with Finance
    Addresses integrated with Perm...
Source Data
Target Data Model
Target Data Model
Target Data Model
Challenges and Solutions
Address Points


  Rotated text in CAD (Magenta)
  STNUMBER layer
  No identifiers
Solution
Boundary Line Types
Boundary Line Types


   Source	
  CAD	
  Layer	
     Feature	
  Class	
             Boundary	
  Type	
     Carto	
  Line	...
Solution
Parcels/Roll Numbers


    Parcel lines
    Roll Number text (multi-value)
    Parcel Polygons/Topology in target
    ...
Solution
Annotation


  Annotation relatively clean and consistent in
   source data
    Layers
    Attributes
  ArcGIS Desktop...
Solution
Automation


  Multiple loads to refine load process and data
   model
  Mapping files a deliverable of the project
  F...
Solution


  .bat files to run individual models for all CAD
   drawings:
  REM loop through Land Parcel Base dwg files a...
Thank You!


  Questions?

  For more information:
    Steve Grisé
    Steve@vertex3.com
    http://www.vertex3.com
Upcoming SlideShare
Loading in …5
×

Using FME to Build an Enterprise Geodatabase

1,895 views

Published on

A recent project at the City of Barrie involved building a Geodatabase for Land Parcel Base and Planning datasets. This Geodatabase is a foundation that is part of an overall plan to build an Enterprise GIS Server that is linked to multiple business systems and web applications. The presentation will provide an overview of the project approach, and discuss some of the challenges and solutions getting 12 large CAD drawings into the target data model using FME.

Published in: Technology
  • Be the first to comment

Using FME to Build an Enterprise Geodatabase

  1. 1. Using FME to Build an 2010: An FME Enterprise Geodatabase Odyssey Steve Grisé Geo Solution Architect and Founder, Vertex3 Inc.
  2. 2. Project Purpose   Build an Enterprise Database   Parcels integrated with Finance   Addresses integrated with Permitting   Planning vertical aligned with Parcels   Move from 12 large CAD drawings, multiple shapefiles, and multiple copies of data/maps   Set a foundation for other projects such as asset/work management
  3. 3. Source Data
  4. 4. Target Data Model
  5. 5. Target Data Model
  6. 6. Target Data Model
  7. 7. Challenges and Solutions
  8. 8. Address Points   Rotated text in CAD (Magenta)   STNUMBER layer   No identifiers
  9. 9. Solution
  10. 10. Boundary Line Types
  11. 11. Boundary Line Types Source  CAD  Layer   Feature  Class   Boundary  Type   Carto  Line  Type   SourceType   PCL_ASSUMED   ePARCEL_BOUNDARY   Parcel   Assumed  Right  of  Way   Unknown   PCL-­‐UNASSUMED   ePARCEL_BOUNDARY   Parcel   Unassumed  Right  of  Way   Unknown   PCL-­‐URA   ePARCEL_BOUNDARY   Parcel   Unopened  Road  Allowance   Unknown   PCL-­‐PL   ePARCEL_BOUNDARY   Parcel   Plan   Registered  Plan   PCL   ePARCEL_BOUNDARY   Parcel   Parcel   Other   PCL-­‐RAIL   ePARCEL_BOUNDARY   Parcel   Rail   Other   PCL-­‐CON   ePARCEL_BOUNDARY   Parcel   Concession   Other   CON-­‐LT   ePARCEL_BOUNDARY   Parcel   Concession  -­‐  Lot   Other   ROW   ePARCEL_BOUNDARY   Parcel   Private  ROW   Other   PCL-­‐RDCL   ePARCEL_BOUNDARY   Parcel   Closed  Road   Other   PCL-­‐PRIVATE   ePARCEL_BOUNDARY   Parcel   Private  ROW   Other   PCL-­‐LAKE   ePARCEL_BOUNDARY   Parcel   Water   Unknown   EASEMENT   ePARCEL_BOUNDARY   Easement   Easement   Other   RESERVE   ePARCEL_BOUNDARY   Reserve   Reserve   Other   PCL-­‐LAKE   eWATER_LINE   N/A   N/A   N/A   PL-­‐LT   eHISTORICAL_LOT   N/A   N/A   N/A   ROAD  EXTENSIONS   eROAD_EXTENSION   N/A   N/A   N/A   LAKE   eWATER_LINE   N/A   N/A   N/A   CITY_BOUNDARY   eMUNICIPAL_BOUNDARY_LINE   N/A   N/A   N/A   CITY_BOUNDARY   eMUNICIPAL_BOUNDARY   N/A   N/A   N/A  
  12. 12. Solution
  13. 13. Parcels/Roll Numbers   Parcel lines   Roll Number text (multi-value)   Parcel Polygons/Topology in target   Also Lot/Block text/pointss
  14. 14. Solution
  15. 15. Annotation   Annotation relatively clean and consistent in source data   Layers   Attributes   ArcGIS Desktop reads CAD Annotation well   Import option to do the same in FME   Performance on load…
  16. 16. Solution
  17. 17. Automation   Multiple loads to refine load process and data model   Mapping files a deliverable of the project   Final load to occur after project completion
  18. 18. Solution   .bat files to run individual models for all CAD drawings: REM loop through Land Parcel Base dwg files and load boundary features using FME mapping file in this folder for %%f in ("Land Parcel Base/*.dwg") do "c:program filesfmefme.exe" "1. Boundaries.fmw" -- SourceDataset_ACAD "Land Parcel Base/%%f" --DestDataset_GEODATABASE_FILE "Barrie.gdb" -- LOG_FILE "%%f_load.log"   Spreadsheet to document steps for loading
  19. 19. Thank You!   Questions?   For more information:   Steve Grisé   Steve@vertex3.com   http://www.vertex3.com

×