Ah! On top of all this Dale suggested that you could open the workspace as it is (ie retaining the group-by and fanout-by fme_basename settings) and change the source dataset location to point to all your files at once!
To point to more than one file the Swizzler is the best thing to use. This is the little icon which looks like [+] and is right next to the [...] icon you'd normally click to locate a file. The best thing about the Swizzler is that you can specify a directory instead of a single file. If you do this FME will read all the data in a single process which is way better than my method which would involve stopping and starting FME 150,000 times (euggh). My only excuse is I thought that even FME would have problems reading 150,000 files at once. Dale assures me that this is not so - FME will read the data, create the bounding box and then expunge the source data from memory. 150,000 bounding boxes will be well within FME's memory limits. Hope this helps - let us know how it goes. Regards, Mark Mark Ireland, Product Support Engineer Safe Software Inc. Surrey, BC, CANADA [EMAIL PROTECTED] http://www.safe.com Solutions for Spatial Data Translation, Distribution and Access > -----Original Message----- > From: Mark Ireland > Sent: January 11, 2005 1:35 PM > To: [email protected] > Subject: RE: [fme] Re: Bounding Box for an entire drawing > > Create a workbench solution that works on a single file and > then run it in batch mode. > > To run in batch either use File->Batch Deploy or run the > workspace from the command line using the command I specified > before (for %%f in etc > etc) > > When running in batch mode make sure that all the Feature > Types (levels) that are in your DGN files are in the > workspace - which they often aren't when you create it from a > single file. The easy way around this is to open the > properties of one level and set a 'merge filter' to * which > will let all features in (if you are only calculating > bounding box that probably won't be a problem). > > Attached is an example workspace. > fme_basename is exposed and used to fanout the destination > (so each file won't just over-write the previous) and there > are two bounding box transformers - one to create the entire > box and the next to get the coords of it. Group-by is set so > that fme_basename can be carried through to the output. > > I copied it into my dgn directory and in a command window entered... > > for %f in (*.dgn) do fme bounding-boxes.fmw --SourceDataset %f > > ...which ran OK (except it doesn't permit spaces in the file names). > You don't need a destination dataset since it is set in the workspace. > > Can't really guess how fast it will be - you'll have to test > it; but if you want an FME solution I can't think of any > other method, let alone another method that will be faster. > It seemed to take a second or two per file - but my files > aren't very large. > > Hope this helps. > > Regards, > > Mark > > Mark Ireland, Product Support Engineer > Safe Software Inc. Surrey, BC, CANADA > [EMAIL PROTECTED] http://www.safe.com > Solutions for Spatial Data Translation, Distribution and Access > > Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our Professional Services team. Visit www.safe.com/services for details. Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/fme/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
