<?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 geocoding ToS limitations in ArcGIS Online Questions</title>
    <link>https://community.esri.com/t5/arcgis-online-questions/geocoding-tos-limitations/m-p/536783#M27214</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I currently build a custom route planning webapp for delivery service providers. I would like to use the ESRI geocoding API to process the customers datasets and was wondering if any of my intended uses would breach the ToS:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. User uploads a list of addresses and I use ESRI services to geocode them (and store the latlon values in my DB). The user is then able to view the results on a map and build the delivery route with my GUI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. The user is allowed to download the resulting route (addresses &amp;amp; coordinates) as a csv file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. The user can access the service via an API&lt;BR /&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am referring to the paid ESRI developer subscriptions of course.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 14 Feb 2016 13:38:40 GMT</pubDate>
    <dc:creator>ChristophMayrhofer</dc:creator>
    <dc:date>2016-02-14T13:38:40Z</dc:date>
    <item>
      <title>geocoding ToS limitations</title>
      <link>https://community.esri.com/t5/arcgis-online-questions/geocoding-tos-limitations/m-p/536783#M27214</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I currently build a custom route planning webapp for delivery service providers. I would like to use the ESRI geocoding API to process the customers datasets and was wondering if any of my intended uses would breach the ToS:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. User uploads a list of addresses and I use ESRI services to geocode them (and store the latlon values in my DB). The user is then able to view the results on a map and build the delivery route with my GUI.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. The user is allowed to download the resulting route (addresses &amp;amp; coordinates) as a csv file.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. The user can access the service via an API&lt;BR /&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am referring to the paid ESRI developer subscriptions of course.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 14 Feb 2016 13:38:40 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-questions/geocoding-tos-limitations/m-p/536783#M27214</guid>
      <dc:creator>ChristophMayrhofer</dc:creator>
      <dc:date>2016-02-14T13:38:40Z</dc:date>
    </item>
    <item>
      <title>Re: geocoding ToS limitations</title>
      <link>https://community.esri.com/t5/arcgis-online-questions/geocoding-tos-limitations/m-p/536784#M27215</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We did an evaluation of the Esri geocoding service previously - we didn't notice any particular ToS limitations in regards to items 1 and 2. Item 3 may need some more research - I'm not sure if you can roll your own API and then publish for your users. Something else to look into - whether or not you'd need an ASP license (application service provider).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Really, I'd probably give your Esri rep a call and discuss your use case.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Feb 2016 15:22:28 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-questions/geocoding-tos-limitations/m-p/536784#M27215</guid>
      <dc:creator>ChrisSmith7</dc:creator>
      <dc:date>2016-02-15T15:22:28Z</dc:date>
    </item>
  </channel>
</rss>

