Column Usage

Forward and reverse GeoCoding both have similar sets of required data columns. For both operations to function the following columns must be present in the GBFS file:

BASENAME, ID, L_REGION, LPOSTCODE, NAME, NM_PREF, NM_SUFF, R_REGION, RPOSTCODE, TYP_AFT, TYP_BEF

To ensure optimal precision the following columns should also be present in the GBFS file, in addition to those immediately above:

EXITNUMBER, LADDRSCH, LNREFADDR, LREFADDR, MANEUVER, POSTALNAME, RADDRSCH, RNREFADDR, RREFADDR, STALENAME

For mapping to function the following data columns must be present in the GBFS file:

ID, LANE_CAT, NAME, FUNC_CLASS, TOLLWAY

To ensure map clarity and optimal usability the following columns should be present in the GBFS file, in addition to those immediately above:

AR_AUTO, AR_BUS, AR_CARPOOL, AR_DELIV, AR_EMERVEH, AR_PEDEST, AR_TAXIS, AR_TRAFF, AR_TRUCK, DIR_TRAVEL, EXIT_NUMBER, FERRY_TYPE, MANEUVER, MULTIDIGIT, PAVED, ROUNDABOUT, TUNNEL, ZLEVEL

For navigation services to function in a sensible manner the following columns immediately below must be present in the GBFS file. These required columns include all those columns required for routing to function correctly.

BASENAME, CONTRACC, DIR_TRAVEL, DIRONSIGN, DIVIDER, FERRY_TYPE, ID, INTERINTER, ISMAJOR, MANEUVER, MULTIDIGIT, PRIVATE, RAMP, FUNC_CLASS, ROUNDABOUT, ROUTE_TYPE, SPEED_CAT, ZLEVEL

To ensure optimal usability and performance the following columns should be present in the GBFS file, in addition to those immediately above:

AR_AUTO, AR_BUS, AR_CARPOOL, AR_DELIV, AR_EMERVEH, AR_PEDEST, AR_TAXIS, AR_TRAFF, AR_TRUCK, BRIDGE, DIVIDERLEG, EXIT_NUMBER, LANE_CAT PAVED, SPEED_LIM, TOLLWAY

For routing to function correctly the columns listed immediately below must be present in the GBFS file. These columns are also required by navigation services.

CONTRACC, DIR_TRAVEL, DIVIDER, FERRY_TYPE, ID, INTERINTER, ISMAJOR, MANEUVER, PRIVATE, RAMP, FUNC_CLASS, ROUTE_TYPE, SPEED_CAT, ZLEVEL

To ensure optimal routing performance and precision the following columns should be present in the GBFS file, in addition to those immediately above:

AR_AUTO, AR_BUS, AR_CARPOOL, AR_DELIV, AR_EMERVEH, AR_PEDEST, AR_TAXIS, AR_TRAFF, AR_TRUCK, BRIDGE, DIVIDERLEG, LANE_CAT PAVED, ROUNDABOUT, SPEED_LIM, TOLLWAY

Tip
If the following columns are present (in addition to those columns required and recommended for Routing) Navigation will function correctly (but not optimally): BASENAME, DIRONSIGN, MULTIDIGIT

The following table indicates which GeoBase columns should be populated by Alchemy in order for different functions to behave sensibly.