geocoding ToS limitations

[ChristophMayrhofer]

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:

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.

2. The user is allowed to download the resulting route (addresses & coordinates) as a csv file.

3. The user can access the service via an API

I am referring to the paid ESRI developer subscriptions of course.

[ChrisSmith7]

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).

Really, I'd probably give your Esri rep a call and discuss your use case.