Options for Building Maps

The table lists and describes fields and options on tabs on the Build tab, and indicates whether they are typically used when building or rebuilding maps.

Table 1. MapMaker Build Tab Options - Origin Tab
Item	Description	Regular build (after loading)	Rebuilding map
Keep Current	If selected, the map origin is not changed. Typically used when rebuilding map dependencies.	No	Yes
Recalculate	If selected, the origin is recalculated based on latitudes and longitudes in the mapSEG table.	Yes	No
Take From	If selected, the origin is taken from the data source chosen from the drop-down list. Used when merging from another data source to ensure internal coordinates do not shift.	No	No
Specify	If selected, the origin is specified using the longitude and latitude fields.
Standard Parallel
Current
Fixed
Automatic
Custom

Table 2. MapMaker Build Tab Options - Metrics Tab
Item	Description	Regular build (after loading)	Rebuilding map
Update Span	If selected, the system determines the map span and grid parameters used for generating the display network.	Yes	If edges of map were edited
Default Cell Size	If selected, grid cells are set to approximately 3 by 3 kilometers (2 by 2 miles).	No	Yes
Keep Current Cell Size	If selected, the system keeps the size previously defined in the mapHEAD table.	No	No
Keep Current Rows and Columns	If selected, the system keeps the current number of rows and columns.	No	No
Update XY and Length	If selected, the system generates internal (XY) coordinates in the mapSEG and mapSHP tables based on the longitudes and latitudes in the map SHP table, and updates the length in the mapSEG table.	Yes	Yes
Only update NULL XYs	If selected, the system only generates missing internal (XY) coordinates.

Table 3. MapMaker Build Tab Options - Binary Path Tab
Item	Description	Regular build (after loading)	Rebuilding map
Binary Path	Specifies the folder for saving the map.bin file.	Yes	Yes
Apply	Select if you want to use the specified file path.

Table 4. MapMaker Build Tab Options - Street Names Tab
Item	Description	Regular build (after loading)	Rebuilding map
General Soundex	If selected, the system creates soundex codes used in Address Matching to locate similar-sounding names.	Yes	Yes
Change Case	If selected, street names are converted to the selected format: Uppercase, Lowercase, or Capitalized. The system also eliminates any name irregularity, such as visible characters and trailing blanks.	No
Update Type Aliases	If selected, the system adds street type aliases (for example, BLVD, BL, Boulevard) rather than only using street types in the original map data. This information is used for parsing street names in address matching.	Yes	Yes
Update Directions Aliases

Table 5. MapMaker Build Tab Options - Network Tab
Item	Description	Regular build (after loading)	Rebuilding map
Display Network Grid
Reset Attribute List		Yes	Yes
Update Attribute List		Yes	Yes
Generate Spatial Index	If selected, the system generates an extended index that allows you to index a spatial column.	Yes	Yes
Generate Binary Data	If selected, the system generates data whose unit can take only two possible states according to the binary numeral system and Boolean algebra.	Yes	Yes
Write Binary File	If selected, the system generates the map.bin file that contains information necessary for displaying the street network and locating the object closest to a given point. Note: Trapeze4 applications prior to version 9 sometimes use map.net and xrting.srt files as well as the map.bin file. If your transit site uses Trapeze4 applications prior to version 9, you must build these files using an earlier version of MapMaker.	Yes	Yes

Table 6. MapMaker Build Tab Options - Nodes Tab
Item	Description	Regular build (after loading)	Rebuilding map
Generate Node List	If selected, the system saves the map.bin file in the specified folder.	Yes	Yes
Generate Cross Street List	If selected, the system generates data in the mapXST table, identifying all nodes where segments with different street names join together. The mapXST option is selected by default. Note: Data should be generated in the mapXST table unless Trapeze directs you to generate data in the mapCROSS table	Yes	Yes

Table 7. MapMaker Build Tab Options - Address Points Tab
Item	Description	Regular build (after loading)	Rebuilding map
Compress Location	If selected, the system concatenates the address elements indicating location.	Yes
Compress Street	If selected, the system concatenates the address elements indicating street name.	Yes
Compress Place	If selected, the system concatenates the address elements indicating place.	Yes
Compress Postal Code	If selected, the system concatenates the address elements indicating the postal code.	Yes
Expand Postal Code
Convert to Lat/Long
Convert Lat/Long to XY		Yes
Compress using Upper Case	If selected, data is shown in upper case (capital letters).
Note: Address Points tab options are not typically used in North American transit sites.

Table 8. MapMaker Build Tab Options - Other Tab
Item	Description	Regular build (after loading)	Rebuilding map
Polygons	For each selected polygon type, an internal (XY) coordinates for the polygon vertices is generated. Needed only once after loading polygons from an external source.	Yes	No
Update Bounding Boxes	If selected, the system generates data in the mapXST table, identifying all nodes where segments with different street names join together. Note: Data should be generated in the mapXST table unless Trapeze directs you to generate data in the mapCROSS table.	Yes	Yes
Generate Spatial Index	If selected, the system generates an extended index that allows you to index a spatial column.
Zip Codes (Numeric Only)
Clear ZIP Codes	If selected, the system clears existing ZIP/Postal codes from the mapZIP table, in preparation for their extraction. This process applies to numeric (US) ZIP codes, and must be done after loading data from a flexible format.
Extract numeric ZIP codes	If selected, the system generates a list of unique existing ZIP/Postal codes in the mapZIP table. This process applies to MapInfo, ArcInfo, and ASCII data. It is not necessary after loading TIGER/Line data. The procedure causes problems if the map contains alphanumeric ZIP/Postal codes.
Map Pages
Update Bounding Boxes	If selected, and map pages are supported, the system generates bounding boxes for the map
Note: The Info tab is not used for the map.bin file, and the Coordinates tab is not used when building map data.

TRADE SECRET. Trapeze Proprietary and Confidential. © Trapeze Software ULC, its subsidiaries and affiliates. All rights reserved.