Hi Jeff, thanks for the help! Unfortunately...I still can't get it. Expose the "geodb_mesures" field of your destination feature type.
Done, as well as for the source polyline (although in this case they are shape_measures) Convert your line to points (Chopper)... Sounds good, but the measures don't get carried over like we expect. Source dataset to Chopper to AttributeSetter to Visualizer (or Destination dataset) and the measure field is empty. I tried Char and Num datatypes. Maybe I'm doing something else wrong? ...then snap your points to be located to the nearest of this points (Neighbourfinder).... Attention: If you use an AchoredSnapper, it will always snap to a vertex and not to the edge!The "Locating Features Along Route" - function in ArcView also snaps to the edge! I used the AnchoredSnapper because it snapped to the closest point.... I found that (please correct me if I'm wrong) the Neighborfinder grabbed the attributes of all the candidate features within the tolerance and put them in a list which I assume then needs to be sorted by distance and indexed but I really have no idea...that would be complex than I wanted :) You could write a batch script that calls your FME file throughthe command line and afterwards a Python Script calling the "LocateFeatures along line" from ArcView... Also sounds good but it seems that the ArcView working "Locate Features Along Route" is in VBA?? I fully expected to find a script in the <Install>\Arctoolbox\Scripts location. If you have FME ESRI Edition, you could extend the FME Extension for ArcGIS so that you could integrate your FME Workbench logic into a Geoprocessing model. I am going to look into that - I didn't even know it existed. Well kind of, but well...did I? Handling measures in FME 2006 GB is not easy. In FME 2007 this should get easier Aha...Cheers to that - should be a great release Thanks again, Grant Huntington
