Hi Wallace, Take a look at the example I posted to our ftp site... ftp://ftp.safe.com/outgoing/measureLister.zip
I'm wondering - if this isn't too obvious - if you neglected to insert a delimiter character into the AttributeSplitter, or used the wrong character. If I put a space instead of a comma I get what looks like the same measures attribute under a different name. In the above example, with a comma as the delimiter in the AttributeSplitter, the measures are split into elements in a list structure. If you then explode the list I think you even get a new ID for each feature (by default called _element_index). In fact in the example I use _element_index to pull the coordinate x/y/z values from the line element. If you're still having problems then send me your workspace and some source data and I'll see if I can diagnose the problem. Regards, Mark --- In [email protected], "wallace_tobin" <[EMAIL PROTECTED]> wrote: > > Hi Mark. > > Thanks for your reply. Yes I now see how I can control the order in > which points are added to my line and am now able to deal with that > however i am still experiencing problems in obtaiung the 3d lengths to > each point within the line. > > Prior to receiving your response I actually had started down the road > you suggested using the MeasuresGenrerator however I seem to having > problems getting the output Measures recreated as a list using the > AttributeSplitter. It seems that the splitter simply reproduces the > measures as a comma separated list, not a formatted list as I > expected. This prevents me from exploding the list using a counter id > as an index and hence I cannot associate the measure values with the > corresponding point along the route. > > Are you able to split output from the MeasuresGenrerator into a > structured list? Could you explain why I am unable to do so? On a > bright note at the very least the MeasuresGenrerator does not seem to > have a problem calcualting 3D lengths along the route. No errors or > warnings are genrated from this. > > Thanks. > > Wallace > > > --- In [email protected], "mark2atsafe" <mark.ireland@> wrote: > > > > Hi, > > Sorry if this response is a little late. > > > > Basically FME does everything in the order that the points are read > > in; so whatever order is contained in the CSV source will be the order > > the points are created and thus the order that they appear in the line > > in. You can - if you need - use a Sorter transformer to get features > > into a different order. > > > > I think my first attempt at this would be to create the line, then use > > a MeasureGenerator transformer. This creates a list of measures which > > you need. Then use an AttributeSplitter to split the measure attribute > > into a list. Then use a ListExploder to get a separate record per > > measure. At some point in there you may also want a CoordinateFetcher > > to grab the coordinate of the point on the line, if that's info you > > are wanting to preserve. (may need a Counter too if you don't have > an ID). > > > > I'm not sure why you are getting zero length. It could be as you think > > that the order of the points is not quite correct. As I said, a Sorter > > is the easiest way to resolve that problem. It might also be the > > FeatureMerger that is over-writing the measure. I'd suggest adding a > > Visualizer at each step of the process so that you can inspect the > > data at each stage to see where it is going wrong. > > > > Hope this helps. What I'll do is try to generate something using our > > test data, and if it works will post it to fmepedia. > > > > Regards, > > > > Mark > > > > Mark Ireland, Senior Product Specialist > > Safe Software Inc. Surrey, BC, CANADA > > support@ http://www.safe.com > > Solutions for Spatial Data Translation, Distribution and Access > > > > --- In [email protected], "wallace_tobin" <wtobin@> wrote: > > > > > > I am attempting to export the chainage lengths for various points > > > along a single route line. > > > > > > I actually created the points for the line from coordinates contained > > > in a csv file. I then used the points created to construct a route > > > line. Without any sorting whatsoever FME appears to create the line > > > joining all the points apparently without overlaps. > > > > > > I then use a feature merger between the original points and the new > > > line in an attempt to create a unique record for each point with the > > > distance to each point output into a new csv file. > > > > > > The output seems to generate a number of points having a chainage > > > length value of 0. I would expect a single point at either end of the > > > line to have this value with the remainderr ascending appropriately. > > > > > > Upon creation of the line from the points can I order the points in > > > the point connector. Can anyone enlighten me as to how points are > > > ordered when create a line using the PointConnector transformer? > > > > > > When using the LengthToPointCalculator can you define which is the > > > starting point in a line? > > > > > > I'd appreciate if anyone could provide soem direction on how this > > > might be accomplished. > > > > > > Thanks. > > > > > > 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/
