What Customers Are Saying

Visit here often (or even subscribe to the blog) in order to catch tidbits of knowledge from our geo-spatial and software experts.


RouteSavvy Tips & Tricks - Prepare Your Address Data

There is an old saying in the IT world “Bad data in means bad data out”. This is certainly true with RouteSavvy. The better the address data you start with, the better the map display and route optimization with RouteSavvy. Here are some tips to improve address data to be used with RouteSavvy route optimization…

  • Make sure your address is complete e.g. “123 Main Street, City, State, Zip
    (Postal Code) and Country”. If you are missing elements of the address, your locations may still locate, but you may have issues. All addresses require a street number and name and a zip code (postal code). City, State and Country are not required to locate an address if you have a good zip or postal code, however it is good to include city, state and country in case there is a discrepancy in the zip/postal code.
  • Provide separate address elements in separate fields. You should upload a separate field for street number and name (address1), city, state, zip (postal code), and country etc. Also, be sure to include the street number and street name are together in one field (we call it address1). Address2 is for suite numbers.
  • Make sure address fields match the fields that appear in the RouteSavvy interface. If your import data field names are different than the import field names for RouteSavvy, you will need to be sure to manually check that all fields are correctly mapped after you’ve uploaded the routing data.  The fastest way to speed up data upload is to rename your data columns to exactly match import fields in the RouteSavvy interface. If you do this, RouteSavvy can automatically detect the fields in your upload file to the fields.
  • RouteSavvy typically supports 1000s of locations (depending on computer and browser performance), but RouteSavvy will perform better if you break up your dataset before import. E.g. import one territory, one driver, or one day of stops. A few hundred locations will load and display faster than 1000s. Using different folders in RouteSavvy is a good way to separate the data uploads, and you can hide/show folders as address data is needed.
  • Include Stop Time Minutes and Notes in your imports. Stop Time Minutes are how long a driver will stay at a stop. If you include this when routing, then the total route drive time will be more accurate. Notes can be included with address import. These are very useful for providing additional information to drivers (for example contact name, purchase history, dock hours, or other customer information). Notes will be maintained in the routes and hence will show in route exports and mobile.

Here are RouteSavvy import sample files in Excel or CSV formats. Also, check out our new tutorial document and tutorial videos.

To sign up for a free trial visit http://web.routesavvy.com/register

 If you have questions, Contact Us




If you have questions, email routesavvy@onterrasystems.com or visit our support portal.


Also, check out our new tutorial document and tutorial videos.


Bing Maps AJAX v7 and SOAP APIs Discontinuation

Recently Microsoft announced that the Bing Maps AJAXv7 and SOAP API were being discontinued. This is because the Bing Maps v8 control has been released with newer/better technology and should be used moving forward. Some of the advantages of the Bing Maps v8 release include better performance and new features like autosuggest for address search, heat maps and other advanced features. You can read more about the Bing Maps v8 release here. Also, here are some recent updates to the Bing Maps v8 API if you are interested.

So what does this mean? Well, the bottom line is that after June 30th 2017 the Bing Maps v7 and SOAP APIs will stop working, and we need to migrate our apps to the newer APIs before then.

Additional details...

  • Here is a migration guide from Bing Maps v7 to v8. 
  • If you are using the Bing Maps AJAXv7 API, then it is a pretty straight forward migration to Bing Maps v8 and will depend on what features and/or extra libraries you are using.
  • If you are using the Bing Maps SOAP API, then you will need to move to the Bing Maps REST API.
  • If you are using a Bing Maps key or OnTerra's WMS inside a GIS/CAD application, you can ignore this information.
  • If you are using Bing Maps Silverlight or AJAX v6.3 APIs, which most people are not, these APIs will be discontinued this year on November 30th 2016.

Are you building a new application and considering using the Bing Maps platform?  Maybe you have an existing app built on another platform and are considering a move to Bing? OnTerra is an authorized Bing Maps reseller. Please Contact Us for more information about our Bing Maps enterprise license offerings and pricing.


Are you still using MapPoint? RouteSavvy has better map data that is updated regularly.

It is well known that MapPoint and Streets & Trips products were discontinued by Microsoft. If you are still using these products consider RouteSavvy which has regularly updated map data.

MapPoint 2013 was the last version of MapPoint released by Microsoft and this product was discontinued on December 31st 2014. Also support ended for MapPoint on July 14th 2015. The reality is the map data in MapPoint is from around 2011 and cannot be updated. As a result, the map data in MapPoint is getting more and more out of date which will effect mapping and routing tasks.

Here are some comparisons between MapPoint and RouteSavvy map data.

MapPoint 2013


MapPoint 2013


RouteSavvy map data gets updated approximately every 90 days. You don’t have to do anything to get the map updates, they automatically get updated as you use RouteSavvy.

For more information and a free trial of RouteSavvy visit http://www.onterrasystems.com/routesavvy-route-planning/


RouteSavvy Territories Release

We have released the new RouteSavvy Territory Creation features into production which concludes the beta trial period. If you were part of the the group that tried the beta thanks for your feedback, you can switch back to production to access these great new RouteSavvy features. If you are interested in trying the new territory features sign up for a free trial.


RouteSavvy team @ OnTerra Systems


New RouteSavvy Create Territories Beta

We are excited to announce a new beta version of RouteSavvy that allows the creation of territories and shapes based on defined political boundaries. This includes US Zip codes, US Counties, US States and Countries. You can import a list of these areas or you can build on the fly by clicking individual polygons on the map.  This beta version is designed to allow customers to test the new territory features and provide feedback.  These territory features will then be released in the production version in the next month or two. To access the beta, Contact OnTerra and we’ll send you the access details.

To get started with the new Territory features login to the beta version, then click on the Create Territory option in the Map tab:

Then in the Create Territory dialog choose the boundary type, Country, State, US County or US Zipcode:

Then in the Create Territory dialog choose the Build or Import option:

For Build, the boundaries will display on the Map, click inside each boundary to add it to the territory:

After the territory is created by clicking in the boundaries, right click inside your new territory and choose Save to Shapes. This will allow you to save the territory inside RouteSavvy. You can choose color and opacity for display:

Alternatively, you can Import an existing list of boundaries to represent your territory. Note, this can only be done 1 territory at a time. So if you have multiple territories you would need to upload separate files and repeat the process 1 territory at a time.

Click Browse and choose the Excel or CSV file to import:

(Note: you can upload a file with multiple columns and simply select the pertinent zip / county / state / country field.  Countries must be spelled exactly as displayed on Country layer once activated for a manual build.  US States can be either spelled out or 2-letter abbreviations.  US Counties must be spelled exactly correctly and contain 2-letter state abbreviation, separated by either one single comma “,” or a single comma followed by a single space “, “.  US Zip codes must be 5 digit.)

The territory will be processed and then displayed.  The user can continue adding more additional polygons to the selection manually by clicking on them.  (Note that polygons cannot be removed from the selection once added.)  Once the selection is complete, use the same method as above to right-click in the grey shape to save the final shape.  

To access the beta, Contact OnTerra and we’ll send you the access details. We’d love to get your feedback as we finalize the new territory features for production release.