tag:blogger.com,1999:blog-4451657389087868432.post7976939586686595267..comments2023-05-29T02:10:01.374-06:00Comments on sworldwatch: FME as a Spatial Intelligence tool for SmallworldAlfred Sawatzkyhttp://www.blogger.com/profile/15845723068853240174noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-4451657389087868432.post-22378210993130617652008-08-19T09:14:00.000-06:002008-08-19T09:14:00.000-06:00Hello Angela,You could use FME from www.safe.com ....Hello Angela,<BR/><BR/>You could use FME from www.safe.com . Or, you could used SEPM Translator from http://www.sepm.ch/translator.htm .<BR/><BR/>AlfredAlfred Sawatzkyhttps://www.blogger.com/profile/15845723068853240174noreply@blogger.comtag:blogger.com,1999:blog-4451657389087868432.post-51555190435210482882008-08-19T08:47:00.000-06:002008-08-19T08:47:00.000-06:00Hello Someone knows how can i export information f...Hello <BR/>Someone knows how can i export information from the smallworld to shapefile? <BR/>Thank you, <BR/>AngelaAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4451657389087868432.post-27073768862754801732007-04-02T10:58:00.000-06:002007-04-02T10:58:00.000-06:00Hello Diego,I think the question you raise about p...Hello Diego,<BR/><BR/>I think the question you raise about performance is a good one. Clearly if all you were doing was a simple report that read each record/geometry from VMDS one time without any further querying, then Magik would be quicker than having to pipe the data through to FME via TICS. But my guess is that your thematic querying does various kinds of attribute querying/parsing. In that case using FME might actually be faster than using Magik.<BR/><BR/>One trick you might consider while developing your Workbench...<BR/> Depending on the amount of data that you are processing from Smallworld in FME, it might take a long time to run the workbench each time. You can speed things up by doing a one-time straight-across translation from the Smallworld format into <A HREF="http://www.fmepedia.com/index.php/Category:FME_FFS_Format_FAQ" REL="nofollow">FFS (FME Feature Store)</A> format. FFS is the internal format that FME uses to do all of its transformations on before it converts it back to the target format. Storing Smallworld data in FFS data is a good way to do your development because your source data is stored in the format that FME can read the quickest. Once you are happy with the Workbench that you have created, you can change the Source Dataset back to Smallworld format in order to always get the most recent data from VMDS.<BR/><BR/>Regards,<BR/><BR/>AlfredAlfred Sawatzkyhttps://www.blogger.com/profile/15845723068853240174noreply@blogger.comtag:blogger.com,1999:blog-4451657389087868432.post-60984904045362569562007-04-01T20:15:00.000-06:002007-04-01T20:15:00.000-06:00Hi Alfred and Dale, mi name is Diego, I work for E...Hi Alfred and Dale, mi name is Diego, I work for Edinfor in Brazil.<BR/><BR/>We recently had a similar situation with one of our clients who use SI to create thematic maps. (SI=>low performance)<BR/><BR/>We've developed some magik code to calculate a thematic map and create the CSV. The process takes something like 4 hours.<BR/><BR/>I was thinking to propose the use of FME Workbench to create some thematics maps like that, but I'm worry about that, because if it takes 4 hours using the geometry primitives inside magik, which could be the performance using FME, that should to read all the data through TICS, create the temporary FME format files, and so apply the transformers, etc... ?<BR/><BR/>do you think the performance will be better using FME ?<BR/><BR/>we was also trying to construct the query in ArcView reading from a shape file... Something must to was wrong, because last time I saw, the query was yet running and the time elapsed=10hours...::eldiego::https://www.blogger.com/profile/08014574030616354291noreply@blogger.comtag:blogger.com,1999:blog-4451657389087868432.post-49534379670036305452007-01-20T21:42:00.000-07:002007-01-20T21:42:00.000-07:00Hi Alfred,
Thanks for the insightful article. We...Hi Alfred,<br /><br />Thanks for the insightful article. We too have found that FME has an amazing variety of uses -- in the past year we've begun using it ourselves in house to do such things as query our CRM, "spatialize" the data, and then visualize it using tools like Google Earth. (I've also used FME to build a catalog of all the FME source code change comments, and years ago we migrated CRM and later accounting systems using FME as the data pump.)<br /><br />What we've found is that any time you might be tempted to write some kind of special code to manipulate data, you're always better off to use the FME graphical tools.<br /><br />Anyway, good article, thanks. (I might just read a blog entry myself pointing to this one!)<br /><br />Dale Lutz<br />Safe Software Inc.Unknownhttps://www.blogger.com/profile/00975044161878343409noreply@blogger.com