If I understand you correctly you can use the count function.

Just directly add the following code to one of your input or output 
factory definitions.

  @SupplyAttributes(foo_sequence_number,@Count())

If you need more than one sequence number just add a unique name to each 
count function as an argument.  So it might look like this

FACTORY_DEF POSTGIS TeeFactory                          \
     INPUT FEATURE_TYPE in_data_name                    \
     OUTPUT FEATURE_TYPE out_data_name1                  \
@SupplyAttributes(foo_sequence_number1,@Count(seed1))    \
     OUTPUT FEATURE_TYPE  out_data_name2                \
@SupplyAttributes(foo_sequence_number2,@Count(seed2))    \
     OUTPUT FEATURE_TYPE  out_data_name3                 \
@SupplyAttributes(foo_sequence_number3,@Count(seed3))


Don't forget to add the new sequence attribute your transformation
and output definitions.  For more information refer to the Count 
function in the factory and functions manual.

Geordie Hobart
GIS Analyst
Refractions Research Ltd.
400-1207 Douglas St.
Victoria,B.C.,
V8W 2E7
[EMAIL PROTECTED]
www.refractions.net
(phone)1-250-383-3022
(fax) 1-250-383-2140


Bala Murugan wrote:
> Dear FME Friends
>  
> I have some queries in migrating the data from CAD file to Personal GDB. 
> I have the request to automatically populate the field name called 
> "S_NO" with start number say 100001 while migrating the data from CAD 
> file to Personal GDB. Let us say i have 100000 records. Is there any 
> transformers to do the job like creating "SEQUENCE " in Oracle ------ 
> populating unique sequence number incremented by 1.
>  
> It is very urgent
>  
> Regards
> Balu
> 
> */Hans van der Maarel <[EMAIL PROTECTED]>/* wrote:
> 
>     Martin Olney wrote:
>      > Is there any documentation for the LineSmoother Transformer?
> 
>     This is from the interactive manual (F1)
> 
>     LineSmoother
>     NEW!
> 
>     Category: Manipulators
> 
>     Smooths the feature's boundary lines by determining a new location for
>     each vertex.
> 
>     Smoothing Algorithm:
> 
>     The McMaster algorithm calculates a new location for each point by
>     first
>     taking the average value of the x and y coordinates of the point and a
>     number of neighboring points. It then slides the averaged point towards
>     the original point according to a specified displacement value. The
>     overall effect is that each point will be pulled towards its
>     neighboring
>     points. Note that for lines, the McMaster algorithm does not change the
>     first and last N points (where N is the number of neighbors), because
>     they don't have enough neighbors for the averaging calculations to work
>     with. A wrap-around is used with polygons, so each point in a polygon
>     will be changed. In the case of adjacent polygons, collinear
>     portions of
>     their boundaries will be smoothed together. The remaining parts of
>     their
>     boundaries will be smoothed as lines. This means that no wrap-around
>     wi ll be used for adjacent polygons.
> 
>     The McMaster Weighted Distance algorithm performs the same
>     operations as
>     the McMaster algorithm only it uses inverse distance weighting to take
>     into account the distance from each neighbor to the point being moved.
>     The overall effect is that points further away will have less "pull"
>     than points close by. The McMaster Weighted Distance algorithm takes a
>     Weighting Power as an additional parameter. The Weighting Power is used
>     to determine the weight of each neighboring point.
> 
>     The Number of Neighbors parameter specifies the number of neighbors to
>     consider for each point. For example, a value of 2 specifies that the 2
>     points to the left of each point, the point itself, and the 2 points to
>     the right will be considered.
> 
>     The Displacement Percentage parameter specifies the location between
>     the
>     original and average points to move the point. For example, a value of
>     50 will place the point at th e halfway point between the averaged
>     point
>     and the point's original location.
> 
>     Alternatively, the AreaGeneralizer transformer can be used to simplify
>     area features without modifying each vertex's location.
> 
>     -- 
>     Hans van der Maarel
>     Red Geographics
>     www.redgeographics.com / [EMAIL PROTECTED]
> 
> 
> 
> 
> 
>     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
> 
> 
> 
> 
> 
> 
> 
> Send instant messages to your online friends http://uk.messenger.yahoo.com
> 
> 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
> 
>     *  Visit your group "fme <http://groups.yahoo.com/group/fme>" on the
>       web.
>        
>     *  To unsubscribe from this group, send an email to:
>        [EMAIL PROTECTED]
>       <mailto:[EMAIL PROTECTED]>
>        
>     *  Your use of Yahoo! Groups is subject to the Yahoo! Terms of
>       Service <http://docs.yahoo.com/info/terms/>.
> 
> 
> 




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/
 


Reply via email to