Caching

[simongis]

Can someone elaborate on how Route Planner caches routes and and addresses.
If my daily orders contain 90% the same customers as the previous day, and I am using the credit-based AGO services, what is best practise for minimising use of these services?

Looking for some best practise on how to go about using Route Planner as efficiently as possible.

[rConger]

Something that may not be readily apparent is that Route Planner uses the address search AGOL endpoint – not the batch – so technically, you are not using AGOL credits to geocode within Route Planner if you are using the standard endpoint defined in services.xml.

That being said, I would not consider leveraging the geocoding features in Route Planner to be best practices anyway. I think best practices would invoke a location management strategy for customer locations where those locations are geocoded, QA’d, persisted, and life cycle managed and then provided to Route Planner for use in daily plans via reference to location (lat/lon). If you are importing orders into Route Planner, lat/lon are fields available.

From: Simon Jackson [mailto:notifications@github.com] Sent: Sunday, March 06, 2016 14:59 To: Esri/route-planner-csharp Subject: [route-planner-csharp] Caching (#25)

Can someone elaborate on how Route Planner caches routes and and addresses.

If my daily orders contain 90% the same customers as the previous day, and I am using the credit-based AGO services, what is best practise for minimising use of these services?

Looking for some best practise on how to go about using Route Planner as efficiently as possible.

— Reply to this email directly or view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Esri_route-2Dplanner-2Dcsharp_issues_25&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=-A4AYYiEJOVeNWm0UFk04A&m=oV64jQZaBOxThLPEKqbGuwDHiese09tkrxjKFi8LXaY&s=WNyRWurUL5uOA3eeyF20zprIp-UHYLnMClWNKVt69uo&e=.

[simongis]

Thanks @rConger. Will look at providing some steps on how they can leverage AGO batch geocoding to update customers in their SQL Server table outside of the Route Planne app.

How about the routes. Is their any best practise tips on how to reduce route calculations on a daily basis. Perhaps someone has the same run 3 days a week for instance.

[rConger]

The route calculations; those are tougher to reduce. Route Planner assumes a contract and it’s that things are always current. So, as I am sure you have noticed, any time you make the slightest change that will impact a route, ETA, etc., it will invoke either a new VRP or route solve. There is no notion of batching up edits and solving in bulk, nor is there a notion that you should just be able copy a route and its orders to a new calendar day without resolving. I could think of a half dozen ways to change this, but none of them are supported in the application logic in the current Route Planner.

From: Simon Jackson [mailto:notifications@github.com] Sent: Sunday, March 06, 2016 15:54 To: Esri/route-planner-csharp Cc: Rodney Conger Subject: Re: [route-planner-csharp] Caching (#25)

Thanks @rCongerhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_rConger&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=-A4AYYiEJOVeNWm0UFk04A&m=dX-9Q9pA3M3np9EMnGUwHvC5s5fqD86oQV0jkmJFdGY&s=NwZ21EKkMXshEigdxZzoagLpisUEscldRe4POR3iWbE&e=. Will look at providing some steps on how they can leverage AGO batch geocoding to update customers in their SQL Server table outside of the Route Planne app.

How about the routes. Is their any best practise tips on how to reduce route calculations on a daily basis. Perhaps someone has the same run 3 days a week for instance.

— Reply to this email directly or view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_Esri_route-2Dplanner-2Dcsharp_issues_25-23issuecomment-2D193018128&d=CwMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=-A4AYYiEJOVeNWm0UFk04A&m=dX-9Q9pA3M3np9EMnGUwHvC5s5fqD86oQV0jkmJFdGY&s=iEH_fiG1Tmv-4uO8QFdRYd_MD1iF0mM5eVU6_7txEow&e=.