In response to the count starting at 0 v 1, a simple solution is to just add one to the count when you call the function

@Evaluate(@Count()+1)

After looking through the rest of your problem the above can be easily done in the @Count() function.

See the screen shot below:

• output of 'testa' ranges from 10-1009
• output of 'testb' ranges from 99-1098
• output of 'test' ranges from 321-2320

Hi @hkingsbury​ ,

Thanks for the reply. I indeed noticed that it is possible to set the startVal directly in the @Count() function (as some of my examples also illustrated). But in your and my examples the @Count() function uses a 'Global' Count Scope, as opposed to the the preferred 'Local' Count Scope. That's an essential part of my question.

So the thing with the Local Count Scope is that it doesn't remember the result of the previous Counter, and thus, each invocation starts counting at the startVal.

When using the @Count() FME Feature function, each domain that you use is logged, and the counter continues counting from the previous count value for that domain. Thus, if you want to get the same result as in a local count, then you would need to make sure that each invocation of the @Count() FME Feature function uses a different domain (and thus in particular you need to keep track of the domains that you already used in the rest of the workspace). That's not ideal.

Initially I thought that the NO_LOG option of the @Count() function would make sure that the function would behave similar to a Local Count Scope, but I just noticed that also that option doesn't provide me with the desired result.

See also the below screenshot

II think the Counter transformer with Local Scope also uses the implementation of the @Count() function. FME just generates unique domain name implicitly for each local Counter, I guess.

Isn't it? @danminneyatsaf​ 

I remember that FME logged the domain name (prefixed by the transformer name, so it can be considered as unique) of a local Counter too, in an old version of FME.

II think the Counter transformer with Local Scope also uses the implementation of the @Count() function. FME just generates unique domain name implicitly for each local Counter, I guess.

Isn't it? @danminneyatsaf​ 

I remember that FME logged the domain name (prefixed by the transformer name, so it can be considered as unique) of a local Counter too, in an old version of FME.

Not so essential though, but I am still wondering about the parameters/options of the Count() function. At the FME Feature Function documentation page it states:

@Count(s<domain>i,<startVal>i,<modulo>]]]l,NO_LOG])

If I look at this (particularly the nested brackets), it seems that NO_LOG option can be suffixed in the Count() function, with whatever other options that are used. Furthermore it seems to indicate that the <startVal> can only be used when a <domain> is specified. 

So this led me to believe that I could use the <domain> and <startVal> option, as well as the NO_LOG option, but not the <modulo> option, but when I try to do so, I get a translation error. 

So is there any way to exclude the <modulo> option, but still use both the <startVal> and NO_LOG options?

So some examples:

@Count(a,1,2,NO_LOG) -> OK

@Count(a,1,NO_LOG) -> ERROR

@Count(a,1,,NO_LOG) -> ERROR

@Count(a,1,"",NO_LOG) -> ERROR

@Count(a,1) -> OK

@Count(a,NO_LOG) -> OK

Thats interesting, it looks like there may be a bug with the modulo part of the count

ERROR |Count -- 3rd parameter `1' is not an integer greater than 0

It almost looks like the default when no modulo is specified is a numeral 1 as a string(?) rather than an int, hence that error. (but see below, it seems to transpose strings to ints successfully)

From your tests above, i'd expect the second one to pass successfully, and i would expect the next two to fail as the modulo is required (as an int) and in the first example you're passing it a NULL/NONE and the second you're passing an empty string - neither of which are an int.

However, if you call @Count(a,1,"1",NO_LOG) it works as expected, so internally it does transpose strings to ints. If you pass it @Count(a,1,"a",NO_LOG) it does fail

Thats interesting, it looks like there may be a bug with the modulo part of the count

ERROR |Count -- 3rd parameter `1' is not an integer greater than 0

It almost looks like the default when no modulo is specified is a numeral 1 as a string(?) rather than an int, hence that error. (but see below, it seems to transpose strings to ints successfully)

From your tests above, i'd expect the second one to pass successfully, and i would expect the next two to fail as the modulo is required (as an int) and in the first example you're passing it a NULL/NONE and the second you're passing an empty string - neither of which are an int.

However, if you call @Count(a,1,"1",NO_LOG) it works as expected, so internally it does transpose strings to ints. If you pass it @Count(a,1,"a",NO_LOG) it does fail

Thats interesting, it looks like there may be a bug with the modulo part of the count

ERROR |Count -- 3rd parameter `1' is not an integer greater than 0

It almost looks like the default when no modulo is specified is a numeral 1 as a string(?) rather than an int, hence that error. (but see below, it seems to transpose strings to ints successfully)

From your tests above, i'd expect the second one to pass successfully, and i would expect the next two to fail as the modulo is required (as an int) and in the first example you're passing it a NULL/NONE and the second you're passing an empty string - neither of which are an int.

However, if you call @Count(a,1,"1",NO_LOG) it works as expected, so internally it does transpose strings to ints. If you pass it @Count(a,1,"a",NO_LOG) it does fail