User-Defined Territories

 

It is possible for MultiRate to analyze data that has been grouped into territories by the user. For example, a company may have already defined specific sales regions, and the MultiRate user may want to analyze these regions using Variable Gradient Geospatial Smoothing to reflect similarities of nearby regions (i.e. by selecting the territory as a Custom Geographic field).

 

This can be accomplished by providing a few key pieces of information to MultiRate about these user- defined territories. The following data needs to be placed into the SQL database that will be used for the MultiRate analysis:

 

Territory Column: A territory column must be included in the Training Table. This column indicates the territory for each record.

 

Territory Table: A table must be added which contains a record for each territory and the XY centroid of that territory. As many or as few territories can be created as desired. MultiRate is expecting that these (X,Y) coordinates are map projections stated in meters. While it is not necessary that these coordinates are actually in meters, the user must be aware that the Variable Gradient Geospatial Smoothing will be governed by radii that are stated in multiples of a thousand to whatever is used (normally this would be kilometers). If territory centroids are only available in latitude and longitude, use the Add XY Columns From Latitude and Longitude tool to transform them to (X,Y) coordinates.

 

Map Data Table (Optional): A table may be added if the user wants to see the territory factors on a map. It must include a list of ZIP Codes to be mapped and the territory where each ZIP Code is located. For most territory definitions, this will be an approximate mapping based on the ZIP Codes included in the table, but still can be very helpful for visualizing geographic factors. For example, when MultiRate is used to generate territories from latitude and longitude data (see Create New Territory Column), a list of the ZIP Codes in the area of the original data are assigned territories based on their centroids.

 

Naming Conventions:

The naming of these tables and columns must be exact. Follow the Table and Field Names shown in the table diagrams below.

 

Territory Table

 

Table Name: TrainingTable_TerritoryColumnName

 

Territory Table Layout:

 

Field Name

Data Type

Explanation

TerritoryColumnName

int

The territory number.

Centroid_X

int

The X value of the centroid of the territory.

Centroid_Y

int

The Y value of the centroid of the territory.

          

*Note: While these three columns must be present in the Territory Table, the presence of other columns is not an issue. (i.e. If the Add XY Columns From Latitude and Longitude tool is used, the latitude and longitude columns do not need to be deleted.)

 

Map Data Table (Optional)

 

Table Name: TrainingTable_TerritoryColumnName_mapData

 

Map Data Table Layout:

 

Field Name

Data Type

Explanation

ZIP

varchar

The ZIP code.

TerritoryColumnName

int

The territory which contains the centroid of the ZIP code.

 

 

For example, to be able to use a territory column called 'Region' from within a Training Table named 'InputData', do the following:

 

Create a table named 'InputData_Region' containing the columns 'Region', 'Centroid_X', and 'Centroid_Y'.

(Optional) Create a table named 'InputData_Region_mapData' containing the columns 'ZIP' and 'Region'.