I had this exact problem. It looks like the QLF reader/writer no longer makes use of the 'gQlfPrecision' and 'gQlfNumFields' environment variables. I solved this problem in my scripts by simply replacing the 'INCLUDE [set env(gQLF...)]' lines with actual definitions. In your case, 'QLF_PRECISION $(QLF_PRECISION_QLF_1)' and 'QLF_NUMFIELDS $(QLF_NUMFIELDS_QLF_1)'. By the way, it also looks like these can't be DEFAULT_MACROs. Hope this helps.
Cheers, Kevin Jodouin, Sylvie wrote: >Hi, > >I am testing the new QLF reader/writer using FME beta, build 1619. Before, I >was able to define de precision and the number of attributes to write. This >new version does not seem to work the same way. > >I have define in my workbench header the macros as follow: ># >============================================================================ ># Sets the precision of output coordinates. > >DEFAULT_MACRO QLF_PRECISION_QLF_1 3 >#####GUI OPTIONAL INTEGER QLF_PRECISION_QLF_1 Output Precision: > >INCLUDE [set env(gQlfPrecision) $(QLF_PRECISION_QLF_1)] > ># >============================================================================ ># Sets the number of output fields or attributes. > >DEFAULT_MACRO QLF_NUMFIELDS_QLF_1 21 >#####GUI OPTIONAL INTEGER QLF_NUMFIELDS_QLF_1 Number of Fields: > >INCLUDE [set env(gQlfNumFields) $(QLF_NUMFIELDS_QLF_1)] > > >Just like before and it does not work anymore. The result is with 15 decimal >and only 9 attributes. > >Can someone help me. For other reasons also, this new built (1619) will >provide solution to other bugs we are having. If this QLF problem can not be >solve, we will have to wait.... > > > >>Sylvie Jodouin >>Natural Resources Canada >>Centre for Topographique Information - Sherbrooke >>Phone: (819) 564-5600 ext.:272 >> >> >[EMAIL PROTECTED] > > >-----Original Message----- >From: Dale Lutz [mailto:[EMAIL PROTECTED] >Sent: 7 f�vrier, 2005 01:16 >To: [email protected] >Subject: RE: [fme] CITS / QLF writer [safe.com #13722] > > > >Hello QLF fans, > >I'm pleased to announce that the recently uploaded FME beta, build 1609, >available from ftp://ftp.safe.com/fme/fme_beta.exe, features the completely >rewritten QLF reader/writer. We've seen some situations where it is 100 >times faster than the old one. > >It also behaves a bit better in Workbench than it used to. It can also >correctly read/write polygons with holes (it used to not read these quite >right), and, while we're at it, it supports automatic gzipping of the qlf >data files -- all you need to do is name the output file with a .qlf.gz >extension and it will be compressed, and on input, if the name ends with >.gz, >it will be decompressed during read. > >For extra fun, if a coordinate system was known for the file, a companion >.prj file (containing ESRI wkt equivalent to what a shape file would have in >its .prj for the same coordinate system) is written out. And if a companion >.prj is present during read, it is also examined and the coordinate system >extracted from it. E.g. for roads.qlf (or roads.qlf.gz), roads.prj is the >companion coordinate system file. Note that the .prj is completely >optional. > >It is all new code, so it deserves a bit of a shakeout yet perhaps. But it >has passed internal testing. > >Let the [EMAIL PROTECTED] folks know if you have good or bad experiences with >it. > >Enjoy. > >(And oh yes, it can be used as the source for a custom format now >too...looks >like all my qlf dreams have come true after all.) > > >Dale > >---------------------------------------------------------------------- >Dale Lutz Safe Software Inc. [EMAIL PROTECTED] >VP Development Surrey, BC, CANADA phone: (604) 501-9985 > http://www.safe.com fax: (604) 501-9965 >---------------------------------------------------------------------- > > > > > > >>-----Original Message----- >>From: Dale Lutz [mailto:[EMAIL PROTECTED] >>Sent: Tuesday, January 25, 2005 7:17 PM >>To: [email protected] >>Subject: RE: [fme] CITS / QLF writer >> >> >>It seems that everywhere I go these days, QLF is the talk of the town. >> >>The most recent betas let you set the # of F fields, so that is now >>something >>you can do without much problem I think. In the worst case, you may need >>to >>"expose" the F10.... in the feature type properties. >> >>The 20 character limit is completely ignored by the writer. So you can >>ignore that too. Really it should just say that the type of those >>attributes >>is "buffer" or something that conveys that its really typeless. >> >>Having said all that, I have a dream of a rewritten QLF writer that is >>drastically faster. And why not a faster QLF reader while we're at it. >>(And >>QLF Reader that can be used in a custom format -- I embarrassingly found >>out >>live in front of thankfully forgiving group that the existing reader >>doesn't >>play by the rules and as such can't be used in a custom format...). >>Perhaps >>one day my dreams will come true... >> >> >>Dale >> >>---------------------------------------------------------------------- >>Dale Lutz Safe Software Inc. [EMAIL PROTECTED] >>VP Development Surrey, BC, CANADA phone: (604) 501-9985 >> http://www.safe.com fax: (604) 501-9965 >>---------------------------------------------------------------------- >> >> >> >> >> >> >>>-----Original Message----- >>>From: kev_neufeld [mailto:[EMAIL PROTECTED] >>>Sent: Tuesday, January 25, 2005 2:41 PM >>>To: [email protected] >>>Subject: [fme] CITS / QLF writer >>> >>> >>> >>> >>>Has anyone ever used the QLF writer before? It seems that the writer >>>is limited to 9 fields (F1-F9) of only 20 characters each. How do I >>>write a feature with more than 9 attributes and greater than 20 >>>characters? >>> >>> >>> >>> >>> >>> >>> >>> >>>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 >>> >>> >>> >>> >>> >>> >>> >> >> >>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 >> >> >> >> >> >> >> > > > > >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 > > > > > > > > > > > >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 > > > > > > > > > -- Kevin Neufeld, Refractions Research Inc., [EMAIL PROTECTED] Phone: (250) 383-3022 Fax: (250) 383-2140 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/
