Preparing Map Data for Loading Using MapMaker

Before loading map data using MapMaker, you must prepare the data for loading into the Trapeze4 map database.

This section provides general guidelines for preparing data for loading using MapMaker. The exact process is unique for each transit site. For more information, contact your Trapeze representative.
  1. Ensure that your map data file is projected to the WGS 84 standard and in a format supported by MapMaker.
  2. Merge all streets to one layer, ensuring that all tabular data is maintained.
  3. Optional: If you have more than one coverage for the same type of data, merge all layers into a single coverage.

    For example, if you have street data for multiple counties, merge the data to create one multiple-county street layer.

  4. Optional: If you have other layer types (for example, rail, county polygons), merge each layer type using the same process you used for merging street data.
  5. Do one or more of the following steps to ensure that the map data is consistent with the Trapeze4 map format:
    • Parse street names - Save direction prefixes, street names, street types, and direction suffixes as separate strings in flexible format map data.
    • Classify segments using CFCC codes - CFCC codes distinguish between types of roads and non-road segments. For example, to classify a segment as a highway, specify A10 as its CFCC code.
    • Ensure that location coordinates are specified as longitude and latitude coordinates in degrees and decimal parts of degrees, and not in degrees, minutes and seconds.
    • Specify address ranges - Specify the lowest and highest street number on each side of each segment.
    • Identify one-way streets - Type a greater than (>) sign for a segment that is one-way from the From point to the To point. Type a less than (<) for a segment that is one-way from the To point to the From point.
    • Identify physical turn restrictions - Type different end-point values for segment intersections where vehicles can not turn.
    • Identify street name aliases - When a segment is known by more than one name, use a field value to identify segments that represent street aliases.
    • Identify zip/postal codes - Specify separate zip or postal codes for the right and left side of each street segment.
      Note: Be careful when entering Canadian postal codes. A single street in Canada can have multiple postal codes.
  6. Fill in missing data values.
    The following table lists recommended values for missing data.
    Note: Use uppercase for all character field values

    Missing Data

    		Recommended Value

    Street Name

    		 UNNAMED
    Street Type ST

    CFFC Classification

    		 A41
    Railroad Name RAILROAD
    Water name WATER
    Address Range Value 0 (zero)
  7. Make a backup copy of the map data.