Thanks Mark, I tried your suggestion without much luck.
I am having trouble running a translation from the command line. Using
the command from the log works fine. If I want to run a different file
it still reads the original source file.
fme.exe Flight_diagrams25.fmw
--DestDataset_GEODATABASE_MDB
C:\DATA\Flight\Aerial_Photography.mdb
--SourceDataset_CSV
C:\DATA\Flight\CSV\Zone49\000080_MGA-z49.csv
I haven't been able to find documentation (FMEpedia and Help) that
suitable explains how to use the command line with a workbench. By this
I mean - Do you remove the source and destination datasets from the
workbench? If so, how are the geodatabase user settings and parameters
set?
I tried this syntax and it didn't work.
fme Flight_diagrams25.fmw --SOURCE_DATASET
C:\DATA\Flight\CSV\Zone49\000082_MGA-z49.csv --GEODB_FEATURE_DATASET
000082.00
I think I am missing something here.
Martin Olney
Senior Geospatial Officer
Geospatial Maintenance
Landgate
(08) 9273 0952
www.landgate.wa.gov.au
-----Original Message-----
From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of
mark2atsafe
Sent: Tuesday, 9 January 2007 6:38 AM
To: [email protected]
Subject: [fme] Re: Fanout feature datasets
Hi Martin,
I checked around and am fairly sure the answer is you can't do this
using a fanout.
What I think you'd have to do is a batch process - so if all your
photos are currently in a single dataset you'll need to run it as a
two-part translation to a) separate them out then b) process them in
batch, setting the GEODB_FEATURE_DATASET keyword for each one.
eg fme workspacename.fmw --SOURCE_DATASET x --GEODB_FEATURE_DATASET x
I can see that creating a batch file with a command for each index
would be potentially as time-consuming as doing everything manually,
so what I'd suggest is creating the batch file using the
separate-dataset part of the translation.
ie Create a workspace that...
Reads the source for the index
Uses Concatenator to create a string...
"fme workspacename.fmw --SOURCE_DATASET" + (INDEXNAME attribute) +
"--GEODB_FEATURE_DATASET" + (INDEXNAME attribute)
Write the string to a text writer
Do a Dataset Fanout on the source data to create the separate inputs
Secondly create a workspace to take a single index as input and write
it to the geodatabase
Run the first workspace
Run the batch file created by the first workspace (that calls the
second workspace once for each index)
You get the idea? It might need tweaking a bit (eg for full pathnames)
but I think it should work fairly well.
I will also file a PR to see if there's a way that we can expose this
writer keyword on a fanout (would probably be dataset fanout, but with
the same effect)
Hope this helps,
Mark
Mark Ireland, Senior Product Specialist
Safe Software Inc. Surrey, BC, CANADA
[EMAIL PROTECTED] <mailto:support%40safe.com> http://www.safe.com
<http://www.safe.com>
Solutions for Spatial Data Translation, Distribution and Access
--- In [email protected] <mailto:fme%40yahoogroups.com> , "Martin
Olney" <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> ________________________________
>
> From: Martin Olney
> Sent: Fri 5/01/2007 10:00 AM
> To: '[email protected] <mailto:%27fme%40yahoogroups.com> '
> Subject: Fanout feature datasets
>
> Hello to all
>
> I sent this question on the Friday before Christmas (msg #13109) but
> haven't had any response. Either this has been put into the too
> basket or most people are still on holidays or both. Just in case it
> slipped through unnoticed I have sent it again.
>
> I have more than 3000 aerial photography indexes that I would like
> to have in 1 Personal Geodatabase. Each index will be a separate
> Feature Dataset containing Feature Classes for frames, points and
> runs. Is there a way to create Feature Datasets as a fanout from an
> attribute? I can fanout to a Geodatabase and Feature Class with no
> problem, but a Feature Dataset appears to be a manual parameter
> setting.
>
> Regards
>
> Martin Olney
>
> Geospatial Maintenance - Topo Section
> Geographic Services Branch
> Information Services Division
> Landgate
>
This e-mail and any files transmitted with it are intended only for the use of
the addressee(s). It may contain information that is confidential and
privileged, in which case neither is intended to be waived or lost by mistaken
delivery to you. If you are not an intended recipient, any use, interference
with, disclosure, distribution or copying of this material is unauthorised and
prohibited. If you receive this e-mail in error, please notify the sender by
return e-mail and delete the message and any attachments from your system.
Unless specifically indicated, this e-mail does not constitute formal advice or
commitment by the sender or the Western Australian Land Information Authority
(Landgate). Information in this message not relating to the official business
of Landgate shall be understood as neither given nor endorsed by it. It is your
responsibility to check any attachments for viruses and defects before opening
or sending them on. Landgate’s liability is limited to re-supplying affected
attachments.
<<attachment: image001.jpg>>
