span8
span4
span8
span4
The Smallworld (ACP) Reader/Writer (short name SWORLD) is for use with Smallworld v3.x databases.You can use FME Workbench with the older Smallworld 3.x reader / writer - originally only mapping files supported this reader/writer.
You should use the Smallworld SWAF reader / writer (shortname SWORLDSWAF) to access your Smallworld 4.x databases - see the article onSmallworld configuration options.
FME should work fine with all these versions.
The only difference between v3.1 & v3.2 and v3.3 is in the Smallworld FME Interface Magik code you should install.There are versions available for v3.2.1 and v3.2 – the v3.2 code is what you should use for a v3.1 installation.Contact your GE Smallworld support representative if you are unsure which version or DLLs are necessary.Training materialsfor using FME with Smallworld 3.x are attached to this article.
Be awarethat we no longer support these versions,so if there are any problems exclusive to this application we are very unlikely to issue fixes or updates.
Note that the SpatialBiz plugin for Smallworld also supports versions 3.1sp2 and above.Some of the newer features of the plugin are not available though.The SpatialBiz Smallworld reader/writer is developed and supported by Spatial Business Systems:http://www.spatialbiz.com/You should contact Spatial Business Systems for any help regarding the SpatialBiz Smallworld reader/writer:support@spatialbiz.com.
Smallworld data is stored using a coordinate system based on world units which are usually mm,cm or in,and you are probably reading the data with a coordinate system that is defined in some other units (usually meters or feet).Most FME predefined coordinate systems are in units of meters or feet.
You can create a custom coordinate system that defines the data as having world units (mm,cm or in) then the data will automatically be converted when it is written to a destination that is defined with a coordinate system in metres or feet.Refer to theCoordinate System documentationfor information on how to create a custom coordinate system.
Attached to this article is an example coordinate system you can use with the Smallworld Cambridge database - British National Grid (mm).
An alternative is to rescale the data using aScalertransformer in Workbench.This isn't the recommended solution since you'd need to do this on every workspace you created,for every feature type.The preferred option is to create a custom coordinate system as described above.
FME is supported by 亚搏在线Safe Software.Contact us via oursupport contact form.
The Smallworld-FME Interface and Magik code is written and supported by GE/Smallworld.You should contact them for issues on this aspect of the software.
Q)Smallworld v3.3 doesn't appear in the list of reader formats in Workbench – what is wrong?
A)Smallworld 3 isn't in the list of source formats because you need to create such a workspace using the Smallworld-FME Interface within GE Smallworld itself.When you have done that then you will be able to edit it in Workbench.Refer to the FME for Smallworld 3.x training materials on the the FTP site listed above
Q)Can I use ‘Import Feature Type Definitions' to create Smallworld v3.3 destination Feature Types?
A)No.You cannot import feature type definitions from Smallworld.You need to create those parts of the workspace using the Smallworld-FME Interface.Alternatively you can create object definitions in an existing workspace using Destination Data > Add Feature Type from the menubar.
Q)When using the v3.3 Smallworld-FME Interface do I need to convert workspaces to a Mapping File to run them?
A)No.When selecting the script to run,instead of using a file suffix of ".fme" use ".fmw".
Q)Where can I find further information on Reading and Writing data for Smallworld v3.3?
A)Have a look at the FME for Smallworld 3 training materials on the attached to this article orhere.
Q)Where can I find FME for Smallworld v3.3 User Documentation?
A)You can find the documentationhere.
Q)When writing to Smallworld v3.3 I get the message..."Field count returned from FME is rediculously (sic) large" ...what does it mean?
A)The "rediculously large" error condition was added as a sanity check,presumably by someone who doesn't own a dictionary.What this message tells us is that at least one objects has more than 60,000 coordinate values.You have an object with great detail.You can increase the check on the fields to get pass the object with the large field counts.
If you do increase this value the packed string will become larger,this is going to use up more of your static space which will result in more garbage collects and a slow down to the overall translation process.So you may only want to increase this value when using large objects.You may also want to investigate why a particular object has so many coordinates.
Modify the latest code.
_if .field_cnt > _self.max_count _then _if .field_cnt > 185668 _then condition.raise(:fme_exe_error,:what,"Field count returned from FME is rediculously large!") _else _global !maximum_collection_size!!maximum_collection_size!<< (.field_cnt + 1) condition.raise(:fme_info,:string,write_string("Increasing vector size to ",!maximum_collection_size!)) _endif _endif
You may get a TB saying something like the packed string is too large.Increase the size of the packed string with...
Magik2> packed_string.define_shared_constant(:max_strings,100,_false)
Q)I have a license to read Smallworld,but it still isn't in the available source formats.
A)In the case of Smallworld v3 the Smallworld 3 reader isn't available in the source dataset list because you have to export from Smallworld using the Smallworld/FME Magik interface.
In other words you can't create a Smallworld v3 reader from within Workbench,only from the Smallworld FME Interface (you can edit the subsequent workspace in Workbench,but have to return to the Smallworld/FME interface to run it)
© 2019 亚搏在线Safe Software Inc |Legal