Sep' 2122, 2006

1
v
Sep. 21-22, 2006
FME Worldwide User Conference - Vancouver
Flexible Extraction and Transformation from
ArcSDE to AutoCad Ulf Månsson, SWECO Position AB,
Sweden
2
Flexible extraction and transformation from
ArcSDE to AutoCAD

• Ulf Månsson

3
www.sweco.se
4
www.malmo.se

• 3rd city in Sweden Malmö
• 1.Stockholm 765 044
• 2.Gothenburg 481 410
• 3.Malmö 269 142

5
Wanted

• A flexible (but understandable) FME-approach to
  extract data from an existing SDE-database (40-50
  tables) to DWG.

6
Background

• Everything will change
• The contents
• The database model
• The attributes
• The coordinate system

7
Defining the Output-Schema

• Examine existing DWG-files (created with other
  tools and manually edited)

8
Defining the Output-Schema

• Create a database with all
• combinations of format attributes

• In FME DWG to MS ACCESS

9
Defining the Input-Schema

• Examine existing documentation of the database
• Create a database with all combinations of format
  attributes

10
Transforming the Input to the Output

• We have a database with the input schema and the
  output schema
• -How do we define the rules and use them when we
  have optional attributes and values ?
• (Like wildcard matching).

11
Transforming the Input to the Output

• Options
• Manually using testers/valuemappers etc. in a
  workbench. - Not very flexible..
• Use the SchemaMapper.
• - Honestly, we could not figure this one out.

12
Option C

• We dynamically create a key-attribute by using
  the concatenator
• So all the SDE-features will get a query-like
  attribute
• TELLUS_GDBS.LEDNINGAR_PUNKTOBJEKT?Objekttyp652St
  atusKvalitetsursprung2

13
Option C

• We create a table describing the mapping rules
• Then by using a joiner we set the autocad
  format attributes.

14
Schema - Conclusion

• Without changing the workbench the user may
  select what features should be extracted and how
  they will be presented in Autocad. This is done
  by changing the rules in the MS Access database.

15
Clipping Data

• The entire database according to map tiling
  standards.
• Selected tiles.
• User defined areas.

16
Clipping Data

• The clipper and fan-out functions are great !
• But
• It is not always a great idea to read all the
  rows from 50 big SDE-tables, clipping them by
  hundreds of tiles and then fan them out in one
  session

17
Clipping Data

• The entire database according to map tiling
  standards.
• A shape-file defines the different tiles.
• The workbench is called by arguments
• We use the ArcSDE-querier to extract one tile at
  the time.

18
Clipping data

• Selected tiles. (We just leave those lines with
  tiles we intend to keep.)
• A shape-file defines the different tiles.
• The workbench is called by arguments
• We use the ArcSDE-querier to extract one tile at
  the time.

19
Clipping Data

• 3. User defined areas.
• Each user keeps a local folder where they can put
  any shape-file (s)
• By calling the workbench by pointing to this
  folder they can clip with any area.
• We use the ArcSDE-querier to extract one tile at
  the time.

20
Conclusion

• Two FME Workbench files (.FMW)
• One Command line file (.BAT)
• One MS Access Database (.MDB)
• Its a very flexible combination !