Summary and Structure of Metadata and Data

The following tutorial and example sections describes the metadata and data attribute requirements for uploading manual and short-term duration count data into BikePed Portal. Metadata must be created prior to uploading or adding any count data.

The general relationship between metadata and data are shown in Figure 1. Segment Area, Facility, Flow, Detector, and Flow Detector are the main sections defining metadata. A single location, or Segment Area, can capture multiple types of count data based on combinations of facility types, flow types, and detector(s).

Fig. 1. A general depiction of the one to many relationship of a single location representing different types of count data.

Figure 2 is an example describing how one Segment Area can capture multiple types of count data. For each Segment Area there can be multiple Facilities (e.g. sidewalk, roadway). For each Facility there can be multiple Flows (e.g. direction, mode). For each Flow there can be multiple detectors, or just one detector. Which then produces a unique Flow Detector for each type of data being recorded (e.g. bicycles traveling northbound on a roadway can be different from bicycles traveling southbound on a roadway). For each Flow Detector there is only one type of Data being counted.

Fig. 2. Example of how one location (Segment Area) represents multiple types of count data.

The proceeding documentation sections for Metadata and Data lists and describes the required and optional attributes recorded in BikePed Portal. Examples are provided in each section. If there are any examples that are not listed that would be helpful, or more clarity is required, please let us know so that we can continue to improve the documentation.