CAD/GIS Software Consultant | helps customers think of possible solutions in a constructive way, committed and enthusiastic, with a sense of humor
The Province of Utrecht has made a big step forward in the direction of comming to a single source of standardized (definitive) CAD-data in an Oracle Spatial enviroment. Main target is the common, organization wide use of data -doesn’t matter if this is admin or geodata.
AutoCAD Map/FDO <=> ESRI ArcSDE
Before AutoCAD Map can make an FDO-connection into ESRI ArcSDE server, there have to be 3 so called DLL’s ( pe.dll, sde.dll and sg.dll ) copied into the “AutoCAD Map software”/FDO/bin-folder.
Using “Map Display Manager => Data => Connect to Data” to add an ArcSDE connection in the Data Connect UI. In this connection screen the server name and instance needs to be entered and after that the username/password of a registered ArcSDE-user.
Map will research, with the ArcSDE-credentials of that user, which feature-tables are available and analyse those tables to determine the correct structure. Note: if the ArcSDE-user has full access to the database, than this analyse will take longer – take care that the user has restricted credentials only for the desired tables for a better performance.
After this analyse the list with available features will be displayed and the user can select one or mutiple tables to connect to the Map-session. Next the data is displayed, with the option to filter on location and/or attributes.
AutoCAD Map/FDO <=> Oracle Spatial
Before AutoCAD Map can make an FDO-connecton into an Oracle 9i or 10g Spatial server, there have to be an Oracle 10g Client ( or an Instant Client ) installed on the Map-machine. Besides that Map needs Oracle Workspace Manager to be installed on the Oracle server – this is used for Long Transactions and Versioning.
Using “Map Display Manager => Data => Connect to Data” to add an Oracle connection in the Data Connect UI. In this connection screen the service name needs to be entered and after that the username/password of a registered Oracle-user.
Map will search by default for FDO-schema’s ( tables with FDO-metadata ) and display these in the DataStore overview. Map can analyse also schema’s without FDO-metadata en determine the structure ( comparable with the description above for ArcSDE ).
After this the list with available features will be displayed and the user can select one or mutiple tables to connect to the Map-session. Next the data is displayed, with the option to filter on location and/or attributes.
see also: Direct access to Spatial Data using FDO-technology
Direct access to Spatial Data in an open structures stored by other software or processes in files and databases is very important for a flexible organization.
For example AutoCAD Map can combine design drawings from AutoCAD or AutoCAD Civil 3D with available data from other systems.
AutoCAD Map can connect to Oracle Spatial, ESRI ArcSDE, Microsoft SQL Server and MySQL databases. There are also FDO-providers to connect to file based datasource, like SDF, ESRI Shape and several raster-formats. And also FDO-providers that enables Map to connect to OGC-webservices.
Some FDO-provincers are developed by Autodesk, some by the opensource community.
Goto http://fdo.osgeo.org for more info about the opensource FDO-technology.
|
functionality |
2006 |
2007 |
2008 |
2009 |
2010 |
| coordinaat systems |  |
|
|
|
|
| import/export from files | |
|
|
|
|
| ( geometry ) cleanup for drawings | |
|
|
|
|
| data classification | |
|
|
|
|
| FDO technology | |
|
|
|
|
| Oracle Spatial and ESRI ArcSDE read/write | |
|
|
|
|
| FDO styles ( Display Manager ) | . | |
|
|
|
| direct publish into MapGuide Enterprise | . | |
|
|
|
| create and manage metadata | . | . | |
|
|
| ad hoc joins and buffers based on FDO-data | . | . | |
|
|
| split and merge rules for FDO-data | . | . | . | |
|
| constraint-based attribute creation for FDO-data | . | . | . | |
|
| new FDO-attributes from calculations | . | . | . | |
|
| workflows | . | . | . | . | |
| overlay analysis for FDO-data | . | . | . | . | |
| data capture and survey functionality | . | . | . | . | |