<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Beta Elevation Profile Geoprocessing Service - m value issues in Water Resources Questions</title>
    <link>https://community.esri.com/t5/water-resources-questions/beta-elevation-profile-geoprocessing-service-m/m-p/160843#M749</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am developing a flex elevation profile widget based on the beta elevation analysis profile geoprocessing service.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I know it is still in beta. Hopefully someone on that team can respond.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Dave Shaeffer&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 28 Jan 2014 11:08:12 GMT</pubDate>
    <dc:creator>DavidShaeffer</dc:creator>
    <dc:date>2014-01-28T11:08:12Z</dc:date>
    <item>
      <title>Beta Elevation Profile Geoprocessing Service - m value issues</title>
      <link>https://community.esri.com/t5/water-resources-questions/beta-elevation-profile-geoprocessing-service-m/m-p/160843#M749</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am developing a flex elevation profile widget based on the beta elevation analysis profile geoprocessing service.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;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.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I know it is still in beta. Hopefully someone on that team can respond.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Dave Shaeffer&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Jan 2014 11:08:12 GMT</pubDate>
      <guid>https://community.esri.com/t5/water-resources-questions/beta-elevation-profile-geoprocessing-service-m/m-p/160843#M749</guid>
      <dc:creator>DavidShaeffer</dc:creator>
      <dc:date>2014-01-28T11:08:12Z</dc:date>
    </item>
  </channel>
</rss>

