Show/Hide Toolbars

Ultra Mileage

Navigation: Ultra One2One Mileage

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 Input Columns button in the Input Columns box on the Database Parameters dialog box.

 

Locations can be specified using two different methods. These are specified using the Locations are: drop-down box on the Database Parameters dialog box. Locations can be specified using named points, or coordinates. Each method will result in a different appearance for the Input Locations dialog box. These are described separately below:

 

 

Setting Coordinate Locations

 

For coordinate locations, each source and destination location is specified using a geographic coordinate. The coordinate is specified by two fields (longitude, latitude) that use decimal degrees. Hemisphere conventions follow those of most GIS and GPS systems (North and East = Positive).

 

The Input Locations dialog box will look like this:

 

one2one_inputlocs_coords

 

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

 

Finally, you must specify a Primary Key. 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 uniqueness can be guaranteed, or more likely, it will be a database primary key ("ID" in the above example). This field is used to ensure the correct data rows are updated with the calculated values.

 

 

Setting Named Point Locations

 

Named points are what MapPoint used to call 'pushpins'. These are points that are referenced by name instead of coordinate. However, you still need to provide the definitions. One2OneMileage can accept definitions in a point layer within a Maptitude point layer, or in a second table in the input database. Use the Points are in a drop-down box on the main Database Parameters dialog box.

 

If you select Database Table, the Input Locations dialog box will look like this:

 

one2one_inputlocs_named

 

As with the coordinates (see above), you must specify a Primary Key. 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 uniqueness can be guaranteed, or more likely, it will be a database primary key. This field is used to ensure the correct data rows are updated with the calculated values.

 

The input database table refers to locations using names in a text field. Specify these using the Point Name fields in the Start Locations and End Locations boxes.

 

The named point settings are found in the Named Point Source box in the bottom half of the dialog box. The Table drop-down box will list the available tables in the current database. Select the table that defines the named points. Then set the columns from this table. Each row in the table defines a named point. Three columns are required: a text name (text), and floating point columns for longitude and latitude.

 

If you set the points to be in a Maptitude Layer, then the Input Locations dialog box will look like this:

 

one2one_inputlocs_mapt

 

You should set the start and location point names, and the primary key as per the Database Table option (see above).

 

The Named Point Source box contains an information box, and the Set Maptitude Parameters button. Press this button to set the Maptitude input layer information using the Input Locations: Maptitude Map dialog box:

 

one2one_maptlocs

 

Set the input Maptitude MAP file by pressing the "..." button. One2OneMileage will then load the map and present you with a list of the available point layers. You can use the Show Selection Sets check box to add selection sets to this list of point layers. A typical Maptitude country pack can contain a lot of layers. Set the Only Show User Data check box to limit the list to user layers (i.e. filter out all base map / country pack layers).

 

After selecting the input point layer, select the data field that stores the point names (Locations.label in this example). Note that you do not have to select any coordinate fields because this information is already supplied by Maptitude.