Thanks Mark for the additional comments. I got it working with the 9 strings of text in place. The parameters stored in a csv file is a good idea for maintaining the 9 copies of the custom transformer in the workspace.
How would you recommend the link to the csv file. Via an input source in the main workspace or via a join or ? Thanks, Annette --- In [email protected], "mark2atsafe" <[EMAIL PROTECTED]> wrote: > > Hi David, > Glad to hear your positive thoughts on FME. > > I think yours is a good solution; it's certainly the one I first > thought of and certainly what we designed custom transformers for. > > The only suggestion I could add would be to store the parameters in a > text or csv file. Then you can read the file into the workspace and > use its values for the offsets. The advantage there is that you can > change the offsets w/o having to edit the workspace, plus there could > be a different file for different scales of mapping. Just a thought. > > FYI I think there is an Australian user doing something similar with > framing - they use FME to convert to SVG then another package to > convert to PDF. I saw an output and it looked pretty good. > See http://www.ipe.nt.gov.au/whatwedo/landinformation/newsletter.html > > This sort of cartographic use of FME isn't something we really > encourage, btw, but it can be useful at times. > > Mark > > Mark Ireland, Product Support Engineer > Safe Software Inc. Surrey, BC, CANADA > [EMAIL PROTECTED] http://www.safe.com > Solutions for Spatial Data Translation, Distribution and Access > > --- In [email protected], "David" <d.hayes@> wrote: > > > > If your FME allows it, Custom Transformers. > > > > Design your custom transformer to do the offsetting replacing of > > points and text, and then add some parameters to your custom > > transformer to allow you to control it externally (i.e > > postion=TOPLEFT,...). > > > > Then all you need to really worry about is maintaining your custom > > Transformer, or your files that use it, but not both. > > > > This is a fantastic inclusion in FME, and everybody should be using it > > like there was no tomorrow. And NO, I am in no way affiliated with > > Safe ;-) > > > > David Hayes > > > > --- In [email protected], "annettefarrell" <afarrell@> wrote: > > > > > > > > > Hi there, > > > > > > I'm building coordinates to frame Ordnance Survey Ireland NTF > (like OSGB > > > NTF) tiles as this is no longer provided. > > > > > > I use the border of the tile, get the bounding extents and manipulate > > > this to get 8 strings of text and place the coordinate outside the > > > border of the tile using multiple series of the following > transformers: > > > EXPRESSIONEVALUATOR (to offset text placement) , 2DPOINTREPLACER > (place > > > point), LABELPOINTREPLACER (place text at offset point), > > > ATTRIBUTECREATOR (justify and rotate for design file output) > > > > > > It works but my workspace is very messy with no modularity and will be > > > hard to maintain in the long term as I've nearly got one of the above > > > transformers for each string of text to place. This is because each > > > string has a specific justification, rotation etc. So I'm > wondering if > > > any one has any other ideas on how they approach this that I'm > missing. > > > > > > Thanks > > > > > > Annette > > > > > > P.S. Happy Saint Patrick's Day > > > > > > 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/
