You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: metrics/metrics_methodology.md
+26-30Lines changed: 26 additions & 30 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,43 +8,39 @@ This section provides methodologies and sample calculations of [MDS metrics](/me
8
8
9
9
**Note 2:** While metrics are designed to be flexible, and allow calculations using any time interval (hourly, daily, monthly), samples in this document are aggregated into 15-mins intervals for simplicity and illustrative purposes.
10
10
11
-
```
12
-
This document will be updated to match in accordance with MDS version 1.0.0
-[Compatibility with Mobility Data Collaborative Metrics](#compatibility-with-mobility-data-collaborative-metrics)
40
36
41
37
## 1. MDS Core Metrics
42
38
43
39
Reference to MDS Core Metrics specification in Github: [link](/metrics/core_metrics.md)
44
40
45
41
### 1.1 `vehicles.[state].avg`
46
42
47
-
The average number of vehicles in an [MDS state](https://github.com/openmobilityfoundation/mobility-data-specification/tree/release-0.4.1/agency#vehicle-events) during the interval within a geographic area. To calculate **vehicles.[state].avg**, we will take a snapshot of vehicle status every N-period, and average the number of vehicles shown to be in status. The default for N is a 1-minute snapshot, with the goal to compute metrics at the largest interval where the least amount of change will occur. Although depending on use cases and computational capabilities, the snapshot frequency can be configurable.
43
+
The average number of vehicles in an [MDS state](../general-information.md#vehicle-states) during the interval within a geographic area. To calculate **vehicles.[state].avg**, we will take a snapshot of vehicle status every N-period, and average the number of vehicles shown to be in status. The default for N is a 1-minute snapshot, with the goal to compute metrics at the largest interval where the least amount of change will occur. Although depending on use cases and computational capabilities, the snapshot frequency can be configurable.
48
44
49
45
**Sample**
50
46
@@ -148,7 +144,7 @@ The sample dataset above will return **vehicles.[state].duration.sum** as shown
148
144
149
145
### 1.5 `events.[event_type].count`
150
146
151
-
The number of [MDS events](https://github.com/openmobilityfoundation/mobility-data-specification/tree/release-0.4.1/agency#vehicle-events) received during the time interval within a geographical area.
147
+
The number of [MDS events]../agency#vehicle---event) received during the time interval within a geographical area.
152
148
153
149
**Sample**
154
150
@@ -255,7 +251,7 @@ A sample metric output table for **trips.[start_loc/end_loc]_distance.sum**.
255
251
256
252
## 2. MDS Dockless Metrics
257
253
258
-
Reference to MDS Dockless Metrics specification in Github: [link](https://github.com/lacuna-tech/mobility-data-specification/blob/add_metrics_definitions/metrics/dockless_metrics.md)
254
+
Reference to MDS Dockless Metrics specification in Github: [link](../metrics/dockless_metrics.md)
0 commit comments