Hi Rich

If you work with mapping files this is the way to do it, break it into a lot 
( I think i have more than 100 in one projet I am working on ), this way it 
is mutch simpler to mentain and update the system, and by keeping one 
function in one file we can focus on one problem at a time.

I have been doing this for years now and never had the problem you write 
about, so somhow you must have changed somthing

If you add the directive below to the top off your mapping files, fme will 
print it to the logfile, you can now compare the old an new and check if 
there is any differences

FME_DEBUG MAPPING_FILE

Peter



>From: "exn99" <[EMAIL PROTECTED]>
>Reply-To: [email protected]
>To: [email protected]
>Subject: [fme] Proximity Factory
>Date: Wed, 11 Oct 2006 18:02:46 -0000
>
>Hi All
>
>We have a mapping file in FME imports one geodatabase to another.
>All the factories are in one huge file. When we try to break it down
>to smaller files in order to manage the factories better, we got to a
>strange problem.
>We found that the devices changes phase.
>I delve through the code and found this factory here is causing this.
>Nothing has been changed in this factory from the original file and
>it's in the same sequence that it should be. The only thing is that
>readers and writers are now kept in different files. How can that
>cause this factory give a different output?
>Our source data is the same geodatabase as before. Had anyone had any
>problem with ProximityFactory before? Is there anything I should
>change in this Factory now that is in different file?
>
>
>FACTORY_DEF * ProximityFactory                         \
>FACTORY_NAME "Assign Phase Proximity Factory"          \
>INPUT CANDIDATE FEATURE_TYPE span                      \
>INPUT BASE FEATURE_TYPE ServiceLocation                \
>INPUT BASE FEATURE_TYPE SwitchBank                     \
>SPATIAL_MATCH CLOSEST 15                               \
>OUTPUT MATCHED FEATURE_TYPE *                                  \
>OUTPUT UNMATCHED_BASE FEATURE_TYPE *
>
>Thanks
>Rick
>
>
>
>
>
>For insights into what's up at Safe Software and what's on the development 
>horizon, visit Safe's blog at spatial-etl.blogspot.com.
>
>Safe Software has also made slides available that outline enhancements 
>planned for FME 2007. The slides are from the "Road Ahead" presentation 
>given on Day 2 of the FME Worldwide Users Conference. To view these slides, 
>visit www.safe.com/2006uc.
>
>
>Yahoo! Groups Links
>
>
>
>

_________________________________________________________________
Vælg selv hvordan du vil kommunikere - skrift, tale, video eller billeder 
med MSN Messenger:  http://messenger.msn.dk




For insights into what's up at Safe Software and what's on the development 
horizon, visit Safe's blog at spatial-etl.blogspot.com.

Safe Software has also made slides available that outline enhancements planned 
for FME 2007. The slides are from the "Road Ahead" presentation given on Day 2 
of the FME Worldwide Users Conference. To view these slides, visit 
www.safe.com/2006uc.

 
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/
 

Reply via email to