Beta Elevation Profile Geoprocessing Service - m value issues

Discussion created by DShaeffer.Regulatory on Jan 23, 2014
Guess this thread is as good as any to post this question.

I am developing a flex elevation profile widget based on the beta elevation analysis profile geoprocessing service.

When I pass the InputLineFeature via a feature set and set returnM to true, I don't get back the m value and point elevation coordinates that I expect. I would expect the geoprocessing service to set m=0 (start) to the first point in the path/line that was passed to the service. That way the profile always starts where the user clicked first. It SEEMS like the geoprocessing service is setting m=0 to the smallest x value. I am a relatively new flex developer so perhaps I am missing something. 

I know it is still in beta. Hopefully someone on that team can respond!?!?!?!

Dave Shaeffer