AnsweredAssumed Answered

Beta Elevation Profile Geoprocessing Service - m value issues

Question asked by geonetadmin on Jan 24, 2014
Latest reply on Apr 22, 2014 by david.shaeffer
Original User: david.shaeffer

I think this is the correct forum to post this question to.

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 the returnM parameter to true, I don't always 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

[ATTACH=CONFIG]30813[/ATTACH]

Attachments

Outcomes