SEPM Products Release Notes

Transcription

1 SEPM Products Release Notes September 2009 SEPM X-Translator SEPM X-Raster Copyright SEPM 2009

2 Contents 1 Release Notes Product Versions SEPM X-Translator SEPM X-Raster Licensing Free Smallworld and TFM/TFD Formats License files Translator Feature Model Model Style Sets Rework of the Smallworld Source Overview Model Mode Dataless Mode Display Style Mode Data sources clipboard, objects and geometries Other X-Translator Improvements Export of alphanumeric tables New text source and target Spatial target DXF Model Properties for Model Styles Value Mapping 'Main geometries' feature User Interface Special Attributes SEPM X-Raster Internal file format for ECW and TIFF export formats

3 1 Release Notes 1.1 Product Versions SEPM X-Translator X-Translator Version Core Spatial Technology Version ( ) Smallworld SWAF Smallworld SWAF Smallworld SWAF SEPM X-Raster X-Translator Version Core Spatial Technology Version ( ) Smallworld SWAF Smallworld SWAF Smallworld SWAF 1-3

4 1.2 Licensing Free Smallworld and TFM/TFD Formats In a move to further push the X-Translator, the Smallworld and TFM/TFD licenses can now be freely used. A Smallworld X-Translator user can use this, for example, to copy data from one Smallworld collection to another or to temporarily store some data in TFM/TFD XML files License files You can now license individual formats by copying a xxx.lic file into the directory..\x_translator\licenses The licenses are dynamically read before each transfer. This makes it easier to add and remove licenses to an existing image without recompiling the x_translator_client_settings.magik. In previous releases the licenses dxf and dwg were defined, though this was referring to the same product (100.E0.003 on the SEPM price list). This is now simplified so that only a dxf license (dxf.lic) is needed. 1-4

5 1.3 Translator Feature Model Model Style Sets This X-Translator release introduces the Model Style Set structure: A Model Geometry may have 0, one or more Model Styles Sets. A model style set provides a classification of the Geometry or Collection into a set of Model Styles. Model Model Context Model Dataset Model Enumerator Model Relation Model Collection Model Enumerator Value Model Geometry Model Attribute Model Style Set Model Style More than one model style sets are created by the Smallworld source in the new Display Style Modes Display Scales and Style scales, as described below. A new XML schema file xtr_2009_03.xsd is provided to cover these changes. 1-5

6 1.4 Rework of the Smallworld Source Overview A rework of the Smallworld source covers the following requirements: New model generation modes: Parameter or Option Model Mode (In Smallworld Source options) Dataless Mode (In Smallworld Source options) Display Style Mode (in Smallworld Source Specification dialog) Description Collection Mode: A model collection has the same geometries as the Smallworld collection. This corresponds to the implementation of previous X-Translator releases. Geometry Mode: For each model geometry, a model collection is generated. Also in this mode only one dataset Geography is generated. The model collections are ordered on their geometry's ACE priority. By using the Geometry Mode, a similar order of the geometries in exported DXF oder DWG data can be achieved as in Smallworld (some restrictions apply, see below). Dataless is geometry: In this mode a dataless RWO leads to a model geometry of the owning collection. Dataless is collection: In this mode a dataless RWO table is treated like a real collection. Selected Display Style: Only one model style set is generated for the selected Display Style. This corresponds to the implementation of previous X-Translator releases. Display Scales: Model style sets are generated for all display scales (display styles) in which the owning geometry is visible. Style Scales: Model style sets are generated for all style scales (using the style attribute in the display scale object, similar to the presentation in the style system) in which the owning geometry is visible. Different implementation of the clipboard, objects and geometries data sources: In previous releases, the objects of the clipboard were only exported, if they were also visible in the selected display style. This implementation is now changed. The previous parameter export_only_objects (available only through using the API) has been renamed to objects. The new parameter geometries allows exporting a geometry set. In the new implementation, the Translator Feature Model is generated directly from the objects in the clipboard or from the objects/geometries parameters. This greatly simplifies the use of the X-Translator as an engine. 1-6

7 1.4.2 Model Mode The following examples shows the effect of the model mode: Lets say parks and footpaths in the Cambridge database are visible: When exporting to TFM/TFD, the following models are generated: Collection Mode The model collection park has two geometries annotation and coverage. Geometry Mode Only one dataset Geography is generated. For each visible geometry, one model collection is generated. Note also that the order of the collections depends on the ACE-priority: First park coverage, then footpath centreline, and then park annotation. 1-7

8 Using Geometry Mode to control the order of the DXF geometries You can use the Geometry Mode to create a similar order of the DXF or DWG entities. The following restrictions apply: If geometries have the same ACE priority, the order in the DXF/DWG data may still be different to Smallworld. In the case of mapped geometries, the Smallworld source Geometry Export Mode Top only creates one model geometry. In this case the priority used for the ordering in the TFM is the highest priority of all mapped geometry fields. If the mapped geometries have different ACE-priorities set, the order in the DXF/DWG data will not be the same as in Smallworld. The following screens from AutoCAD show the effects of using the geometry mode: Collection Mode The order is likely to not the same as in Smallworld Geometry Mode The oder of the geometries is the same as in Smallworld (see restrictions above). 1-8

9 1.4.3 Dataless Mode The following example shows the effect of the Dataless Mode for the Cambridge Road and Road Annotation objects: Dataless is geometry The Road Annotation appears as a model geometry of the collection Road. Dataless is collection In this mode, the Road Annotation is modelled as a separate table. 1-9

10 1.4.4 Display Style Mode Let's use again the Road collection to show the effect of the Display Style Mode. The following styles are defined for this collection: Not counting the Auto display style, there are six display styles defined in the Cambridge database (Detail, Block, Neighbourhood, City, Region, Country). The Centreline geometry is set visible in the following display styles: Display Style Mode = Selected Display Style One Model Style Set Detail is created. 1-10

11 Display Style Mode = Display Scales In this mode, Model Style Sets are created for each display scale in which the geometry is visible. Display Style Mode = Style Scales In this mode, Model Style Sets are created for those display scales that correspond to the different visibilities (e.g. "Detail etc." and "Neighbourhood etc." in the Style System). 1-11

12 1.4.5 Data sources clipboard, objects and geometries The data model of the Smallworld source is now directly generated from the objects or given through the objects or geometries properties: Let's say you select a bunch of objects in the map: The corresponding model is automatically derived from the given set of objects. The following code snippet shows how you could export a set of geometries through the X-Translator API and the new geometries property: _local l_geoms << l_maps.current_map.current_selection l_source_spec << x_translator_smallworld_source_spec.new( :data_source, :geometries, :geometries, l_geoms, :ace_context, "Electricity", :ace_control, l_ace_control, :gs_factory, l_gs_factory, :display_style_name, "Detail", :style_category, "Default", :geometry_export_mode, :top, :export_area, export_area, :source_world, source_world, :is_unit, _false, :unit_name, :mm, :csys_name, l_csys_name, ) _local l_target_spec << x_translator_dxf_target_spec.new( :path, "D:\Temp\new_sw_source\roads.dxf", :scale, , :is_unit, _false, :csys_name, l_csys_name, :unit_name, :m ) _local l_mapping << x_translator_mapping.new() _local l_engine << x_translator.new() l_engine.source_spec << l_source_spec l_engine.target_spec << l_target_spec l_engine.mapping << l_mapping l_engine.options << l_options l_engine.x_transfer() 1-12

13 1.5 Other X-Translator Improvements Export of alphanumeric tables You can now select tables with no geometries in the Smallworld source Tables tab for export. You could, for example, use the new text target specification to export this data to comma-separated text files. 1-13

14 1.5.2 New text source and target Text source and target specifications allow import and export of comma-delimited Ascii files. The following features are available: Lines with #Dataset and #Collection headers lead to automatically searching for the target dataset and collection, which is then used in the Connect Matching command. The external names of the datasets and collections are used. Lines with headers #x#<external geometry field name>, #y#.. and optionally #z#.. lead to a point geometry in the source model #id#<external name of an identifier field>. If set, the field is connected with the Connect ID to the target identifier field. For example, when using this file Select the directory with the file in the dialog Text Source Specification Select the corresponding target dataset in the Smallworld target: 1-14

15 The following source model is created and can be connected automatically to target collection with Connect Matching: You can now update the existing data in the database with the new data from the text file. 1-15

16 1.5.3 Spatial target The spatial target specification was already part of the X-Translator package for some time. You can now purchase this module as a separate product. Note that this feature is only available through Magik scripting and usually needs some time for setting up. The following functionality is available: Generation of the instance metadata shared constant based on a source TFM model Generation of SQL scripts to create data structures inside Oracle The x_translator_spatial_target_spec class to copy data from Smallworld to Oracle The following example shows how to replicate the Road table of the Cambridge database to Oracle: Create a x_translator_smallworld_source_spec, use the collection_predicates property to define the tables to export Create a x_translator_spatial_target_spec. Use the method x_create_database() to create SQL and instance metadata Install the data model in Oracle using Oracle tools Setup an x_oracle configuration using the Magik file generated in x_create_database() above Open the database with x_oracle_manager.connect_all(). Make the SDO Geometries visible in the ACE with the command: sw:x_translator_ace_interface.make_all_visible(:oradb, "Electricity") Use x_transfer() as shown below to copy data from Smallworld to Oracle _method system.export_oracam( p_is_create_model )... _local l_source_spec << x_translator_smallworld_source_spec.new( :data_source, :all, :ace_context, "Electricity", :collection_predicates, hash_table.new_with( :gis, { "min_road" } ), :display_style_name, "Region", :source_world, l_world, :is_unit, _false, :csys_name, :uk_british_national_grid, :unit_name, :mm ) _local l_target_spec << x_translator_spatial_target_spec.new( :ora_dataset_name, :oradb, :dir, l_dir, :configuration_name, :cambridge_bng_m, :is_unit, _false, :csys_name, :uk_british_national_grid, :unit_name, :mm 1-16

17 ) _if p_is_create_model _is _true _then l_source_spec.x_set_options(l_options) l_source_spec.x_open_read() _local l_model << l_source_spec.x_get_source_model(:initial) _else l_target_spec.x_create_database(l_model) _local l_mapping << x_translator_mapping.new() _local l_engine << x_translator.new() l_engine.source_spec << l_source_spec l_engine.target_spec << l_target_spec l_engine.mapping << l_mapping l_engine.options << l_options l_engine.log_dir << l_dir _endif _endmethod $ l_engine.x_transfer() DXF Model Properties for Model Styles You can now set DXF model style properties on individual model styles. (In previous releases it was only possible to set DXF properties for model geometries and model collections) 1-17

18 1.5.5 Value Mapping The value mapping allows mapping source values to target values. This is most useful to map source enumerator values to target enumerators, but the function can also be used for any data type. As an example, let's assume you would like to copy rail lines to roads in the Cambridge database: Create a new value mapping by selecting a source and a target attribute in the source and target model. Note that only the data type of the model attributes are used. In the mapping tree, select Add Value Mapping... with right-mouse-button menu. In the value mapping screen, you can now add mappings. For other data types you will have to enter the value in the text item. You can now select a value mapping for a given attribute mapping using the Assign Value Mapping... command When the data is now loaded, the values are converted accordingly 1-18

19 1.5.6 'Main geometries' feature When exporting to the Shape format, it was possible in previous SEPM Translator versions to tag special geometries of a collection as a 'Main Geometry'. Alphanumeric attributes were only exported for those main geometries to the Shape/DBF target files. The same behaviour can now be achieved through the following settings: In the model properties of the main geometry, set the Maingeometry toggle: In the Shape options, select the value Create attributes for main geometries only for Attribute mode User Interface The areas for the source model, target model and mapping can now be individually resized. 1-19

20 1.5.8 Special Attributes In some case, the definition of Special Source Attributes is useful to get around specific loading problems. You can add special attributes by using the right mouse menu Special Attributes... command, which launches the following dialog: The following special attributes are defined: Special Attribute System Date System Time Collection Counter Transfer Counter UVA Counter Fixed Value Description The current data The current time A counter which is set per source collection A counter which is set per transfer process The value is determined through a UVA. You can configure the UVA to use in the x_translator_settings. A fixed value (a string). 1-20

21 1.6 SEPM X-Raster Internal file format for ECW and TIFF export formats When exporting to ECW and TIFF files, the Smallworld data is first saved into temporary raster files. The previously used JPEG format is now changed to PNG, which removes the quality problem which was present with the JPEG format. 1-21