Reading or Writing VISION using FME
When you undertake a data translation using FME Universal Translator or Workbench, FME builds an FME Mapping File that controls the mapping of the source to destination format schemas. For the vast majority of formats that FME supports, FME can automatically generate the FME Mapping File (or Workbench equivalent) with little or no intervention from the user. FME can extract all the geometry and attribute information for each table or feature type in the source dataset, and make a reasonable guess at how this data should be represented in the destination dataset. The mapping file can then be fine tuned, either in the FME Workbench, or using an ASCII editor, to get exactly the desired results - for example, changing attribute or table names, adding coordinate transformations, etc.
FME can be used to read & write VISION* data in two ways, using the GINA format or native VISION* Oracle. The GINA reader/writer is simple to use (drag & drop translations are available) but is slower and requires two steps - conversion from VISION* to GINA using the VISION* tools, then the GINA translation using FME. The GINA reader/writer supports Version 3.4 GINA only.
FME can also be used to read VISION* data using the FME Oracle reader. The FME Oracle reader is configured to extract the appropriate VISION* tables and merge the geometry and business table records into individual features. This tends to give better results than going vis GINA, but requires considerably more configuration effort. Safe's Professional Services Group can create a set of FME Posting Scripts (mapping files) to read the Oracle database and create the necessary relationships as defined by the VISION* schema to pull all attribute and coordinate information from Oracle as part of a Solution Assistance engagement.
For each VISION* implementation there is likely be further development work required on the mapping files before a complete solution could be provided.
In conclusion, to read native VISION* data you need a good understanding of FME, the VISION* format, the VISION* schema and your destination data schema. It essential to have a well defined schema specification for the VISION* database. The requirements specification should detail the schema for the VISION* database (including themes, custom attributes and any data hierarchies), and how the source data will map to the required destination format themes & attributes.
Please contact us to find out how Safe Software can help customize a VISION* solution to meet your needs.