Show/Hide Toolbars

MPMileage for Maptitude

Navigation: Running MPMileage for Maptitude

Setting the Input Location Fields

Scroll Prev Top Next More

The input location fields are set on the Input Locations dialog box. This is displayed by pressing the Set Columns button in the Input Columns box on the Database Parameters dialog box.

 

Locations can be specified using three different methods. These are specified using the Locations are: drop-down box on the Database Parameters dialog box. Locations can be specified using pushpins, street addresses (i.e. geocoding), or coordinates. Each method will result in a different appearance for the Input Locations dialog box. These are described separately below:

 

 

Setting Named Data Point Locations

 

For named data point (aka 'pushpin') locations, each source and destination location is specified using a text field that gives the name of the data point. These data point locations are found in the dataset in the Input Columns box in the Database Parameters dialog box.

 

The Input Locations dialog box will look like this:

 

input_locs_pushpins

 

There are only two drop-down boxes that need to be set: select the data fields that store the data point names for the start and end locations (Source and Destination respectively, in this example).

 

These data point names are used to find the required locations in the Dataset with a lookup of the Name Field. Both of these are set in the Input Columns box in the Database Parameters dialog box. These names should be unique in the Dataset. If two data points in Dataset have the same name, there is no guarantee which point will be chosen by Maptitude.

Setting Coordinate Locations

 

For coordinate locations, each source and destination location is specified using geographic coordinate. This is specified by two fields (longitude, latitude) that use decimal degrees. Hemisphere conventions follow those of Maptitude and most GPS systems (North and East = Positive). Maptitude data view coordinates may also be specified using integer fields using the Maptitude convention of millionths of a degree.

 

The Input Locations dialog box will look like this:

 

input_locs_coords

 

The longitude and latitude data fields must be specified for both the start and end locations.

 

Finally, you must specify a Primary Key for all non-Maptitude databases. This can be any text or integer field with a set of unique values for each row. This might use an existing data field where this can be guaranteed, or more likely, it will be a database identifier code ("ID" in the above example). This field is used to ensure the correct data rows are updated with the calculated values.

 

MPMileage does not require a primary key for Maptitude data views because Maptitude implements its own record handles that MPMileage can use.

Setting Street Address Locations

 

MPMileage can also geocode locations on-the-fly, converting street addresses into points on a map. This is potentially unreliable because geocoding will often have errors due to spelling mistakes or old road data. Therefore although this option can be very convenient, you should only use it when you know Maptitude can geocode your data satisfactorily. Otherwise, you should expect lots of location errors in your results.

 

Maptitude will locate addresses using the current country/region. This can be set by selecting Edit -> Preferences to display the User Preferences dialog box.

 

The Input Locations dialog box will look like this:

 

input_locs_addresses

 

A street address is specified using a number of different fields. Select all that are relevant and "<none>" for those where you do not have a data field. If you were only working with zipcodes, you would only set the Postcode (Zipcode) fields.

 

Maptitude can report multiple matches when locating points with partial addresses. MPMileage's behavior in this situation is controlled with the Multiple address matches will be considered ambiguous, and skipped checkbox. If you set this checkbox, MPMileage will consider all such results as "ambiguous", i.e. not found. If you clear this checkbox, MPMileage will use the first location returned by Maptitude. If population data is available (e.g. cities and zipcodes) then Maptitude will sort the results according to population. Hence the match with the highest population is assumed to be correct.

 

Finally, you must specify a Primary Key for all non-Maptitude database. This can be any text or integer field with a set of unique values for each row. This might use an existing data field where this can be guaranteed (as above), or more likely, it will be a database identifier code. This field is used to ensure the correct data rows are updated with the calculated values.