Ah - synchronicity! I answered this very question just a couple of weeks ago. The user seemed happy so here's my response...
-------------------------------------------------------------- I think the issue is that in batch deploy each input dataset creates a separate output dataset. In this case a separate dataset means separate directories because MapInfo TAB [in this case Shape] is a directory based format - if FME wrote it all to the same folder it would really be one big dataset with many individual feature types. The other issue is how many feature types are in the data? If you're writing Line, Name, Point etc as separate feature types then it becomes even more awkward because they will clash for each source dataset. I think a fanout is the intended way to do this - but it would be a Feature Type fanout. That works a lot better than Dataset Fanout in terms of performance. You'd probably want to create a combined fme_basename and fme_featuretype_name attribute and fanout by that (to give SN43NE-line, SN43NE-point, SN43NW-line etc and avoid the FT name clash) The other way to go is to save the batch as a bat/tcl and edit this to produce output in the same folder. I've had a try and think I've got it. The basis is to change... set destDataset "$destDir$baseName$suffix" to... set destDataset "$destDir" It's line 73 in the attached file. [haven't attached it here] You'll also need to expose fme_basename and set up a FT fanout, but there is no overhead because you're still using batch deploy (the fanout is just to make sure the names don't conflict). OK - I realize this is a bit of a hack, but I tried it myself using some NTF data and it all seemed to be OK. -------------------------------------------------------------- So even if you edit the TCL I'd still recommend a fanout, unless you can guarantee only a single feature type per original dataset. Mark Mark Ireland, Senior Product Specialist Safe Software Inc. Surrey, BC, CANADA [EMAIL PROTECTED] http://www.safe.com Solutions for Spatial Data Translation, Distribution and Access --- In [email protected], "Jeff Konnen" <[EMAIL PROTECTED]> wrote: > > Hi Carly, > > perhaps you could try a DataSet Fanout rather than a Batch Deploy? > > For editing the .tcl file, you will have to wait for Peter to be back from > the BC mountains :)) > > Cheerio, > Jeff > > On 9/26/06, clambert_aamh <[EMAIL PROTECTED]> wrote: > > > > Hello All :) > > > > Is it possible to batch deploy to ESRI shapefile format to the same > > destination directory, rather than a new folder being created for each > > output file? > > > > If I save the batch deploy file to run at a later stage - is there a > > part of the .tcl file that can be edited to manage this? > > > > Many Thanks, > > Carly > > > > > > > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/fme/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/fme/join (Yahoo! ID required) <*> To change settings via email: mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] <*> 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/
