Appendix A: Spatially-enabled data: Frequently Asked Questions

Table 1. Frequently Asked Questions
Question	Answer
Does Trapeze support layers in its mapping?	Trapeze does not refer to its spatially-enabled data sets as layers, but they can be interpreted as layers.
Does Trapeze support the loading of bus stops and route traces, including spatial information?	Yes. Originally, Trapeze supported only attribute data loads but can now load spatial data (that is, coordinates) for stops and lines.
Is loading bus stops and route traces a standard process?	No. Because there is no standard for this type of data, site-specific manual data manipulation is required. For example, you could import data into Microsoft Access in a form similar to the source data, and then packed into Trapeze tables using custom queries.
After map-related Trapeze FX data is loaded, is it ready to be used?	Not for all purposes. Trapeze FX, a transit scheduling system, establishes and maintains intricate relationships between lines (routes) and stops, and between nodes and patterns. An external source might not be able to create or maintain these relationships. For example, some third-party sources do not use patterns. Once data is loaded, relationships must be established manually in FX, to ensure that you have fully-functioning FX data.
Does Trapeze support the loading of multiple maps?	Yes, but Trapeze cannot guarantee that map-related transit data developed with a previous map is compatible with a new map. The loading process does not introduce differences, but map-related transit data is affected if base maps are offset.
Does Trapeze support multiple loads of map-related FX data?	Multiple loads are supported, but the manual work required following such loads is impractical.
Can Trapeze export map-related FX data?	Yes. FX tools in the Trapeze4 workstation can export map-related data into ASCII, MapInfo MIF/MID, and ArcView Shape File formats.
Are polygons used in address matching?	No. Although polygons can represent city or ZIP code boundaries, Trapeze4 does not use them in address matching. Instead, separate fields for the left and right side of each segment contain place and ZIP/Postal code information. This address matching method is faster and more precise than if polygons were used.
Is there a way to fill in missing address information?	Although Trapeze cannot interpret missing address information from the street layer, you can load address points to use for geocoding instead of the street layer. You can also use Trapeze MapEdit to manipulate address ranges and street names/aliases. For more information, see the MapEdit User Guide.
Is there a limit to the number of polygons in the map?	There is no limit to the number of polygons in a map. However, map performance is related to how many polygons are displayed and the type of network in which Trapeze is operating. Sites are advised to load all required polygons that are applicable to paratransit clients, and then determine an appropriate threshold for displaying polygons.

Does Trapeze support layers in its mapping?

Trapeze does not refer to its spatially-enabled data sets as layers, but they can be interpreted as layers.

Does Trapeze support the loading of bus stops and route traces, including spatial information?

Yes. Originally, Trapeze supported only attribute data loads but can now load spatial data (that is, coordinates) for stops and lines.

Is loading bus stops and route traces a standard process?

No. Because there is no standard for this type of data, site-specific manual data manipulation is required. For example, you could import data into Microsoft Access in a form similar to the source data, and then packed into Trapeze tables using custom queries.

After map-related Trapeze FX data is loaded, is it ready to be used?

Not for all purposes. Trapeze FX, a transit scheduling system, establishes and maintains intricate relationships between lines (routes) and stops, and between nodes and patterns. An external source might not be able to create or maintain these relationships. For example, some third-party sources do not use patterns.

Once data is loaded, relationships must be established manually in FX, to ensure that you have fully-functioning FX data.

Does Trapeze support the loading of multiple maps?

Yes, but Trapeze cannot guarantee that map-related transit data developed with a previous map is compatible with a new map. The loading process does not introduce differences, but map-related transit data is affected if base maps are offset.

Does Trapeze support multiple loads of map-related FX data?

Multiple loads are supported, but the manual work required following such loads is impractical.

Can Trapeze export map-related FX data?

Yes. FX tools in the Trapeze4 workstation can export map-related data into ASCII, MapInfo MIF/MID, and ArcView Shape File formats.

Are polygons used in address matching?

No. Although polygons can represent city or ZIP code boundaries, Trapeze4 does not use them in address matching. Instead, separate fields for the left and right side of each segment contain place and ZIP/Postal code information. This address matching method is faster and more precise than if polygons were used.

Is there a way to fill in missing address information?

Although Trapeze cannot interpret missing address information from the street layer, you can load address points to use for geocoding instead of the street layer.

You can also use Trapeze MapEdit to manipulate address ranges and street names/aliases. For more information, see the MapEdit User Guide.

Is there a limit to the number of polygons in the map?

There is no limit to the number of polygons in a map. However, map performance is related to how many polygons are displayed and the type of network in which Trapeze is operating.

Sites are advised to load all required polygons that are applicable to paratransit clients, and then determine an appropriate threshold for displaying polygons.