A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Summary | |||||||||||||||||||||||||
2 | The project components view contains all components across all projects. Each row contains information about the component and also data about the project the component is mapped in. | |||||||||||||||||||||||||
3 | ||||||||||||||||||||||||||
4 | Integrations | Name in Moped database | ||||||||||||||||||||||||
5 | Microsoft Power BI, ArcGIS Online | component_arcgis_online_view | ||||||||||||||||||||||||
6 | ||||||||||||||||||||||||||
7 | Column Name | Column Description | Project-level or component-level data | |||||||||||||||||||||||
8 | project_id | The unique project ID that the component is mapped in. | Project | |||||||||||||||||||||||
9 | project_component_id | The unique component ID. | Component | |||||||||||||||||||||||
10 | feature_ids | A comma-separated list of the component's unique feature IDs. Components can have zero or more features, each of which contains a geography. | Component | |||||||||||||||||||||||
11 | component_id | ID that corresponds to the component type in the internal moped_components table. For example, Bike Box is ID 5 | Component | |||||||||||||||||||||||
12 | geometry | A GeoJSON object which holds all of the component's features' geographies. The object may be of any type (MultiPoint, MultiLineString, etc), and this type is determined automatically by the PostGIS ST_AsGeoJSON function used to convert the PostGIS geometry to GeoJSON. | Component | |||||||||||||||||||||||
13 | line_geometry | A GeoJSON object which holds all of the component's features' geographies as LineString or MultiLineString types. Point geographies are converted to line types using the ST_ExteriorRing function. This column is used to create a single AGOL layer of all moped component geographies. It is intended to address a limit of AGOL that all features in a layer must have the same geography type (point or line, but not both). | Component | |||||||||||||||||||||||
14 | signal_ids | A comma-separated list of the component's signal IDs that correspond to signal assets managed in Data Tracker. | Component | |||||||||||||||||||||||
15 | council_districts | A comma-separated list of council districts which intersect with the component's geometry. | Component | |||||||||||||||||||||||
16 | council_districts_searchable | A comma-separated list of council districts formatted with leading zeroes like 01, 02... 09, 10. This field is needed in the ArcGIS Online layers so that it is possible to filter for council district 1 but not district 10. | Component | |||||||||||||||||||||||
17 | is_within_city_limits | A boolean value which indicates if any of the component's features are within the COA limits. It is determined based on if any of the component's features have at least one council district as defined in the internal features_council_districts table. | Component | |||||||||||||||||||||||
18 | length_feet_total | The whole number sum of the length of all of the component's line features that references the length_feet column of features | Component | |||||||||||||||||||||||
19 | length_miles_total | The length_feet_total column converted to miles rounded to two decimal places. For example, 2.37 miles. | Component | |||||||||||||||||||||||
20 | component_name | The name of the component type that references the internal moped_components table. | Component | |||||||||||||||||||||||
21 | component_subtype | The name of the component sub-type that references the internal moped_components table. | Component | |||||||||||||||||||||||
22 | component_name_full | The component's name and subtype joined and separated by a dash. | Component | |||||||||||||||||||||||
23 | geometry_type | The name of the component's geometry type with value of "Line" or "Point". | Component | |||||||||||||||||||||||
24 | component_subcomponents | A comma-separated list of the component's subcomponents names that references the internal moped_subcomponents table. | Component | |||||||||||||||||||||||
25 | component_work_types | A comma-separated list of the component's work types that references the internal moped_work_types table. | Component | |||||||||||||||||||||||
26 | component_tags | A comma-separated list of the component's tags that references the internal moped_component_tags table. | Component | |||||||||||||||||||||||
27 | component_description | The component description used for additional project component details and comments. | Component | |||||||||||||||||||||||
28 | interim_project_component_id | The component's unique "facility" ID in the Access DB. Indicates the component was migrated from the ATSD Access DB in October 2023 when Moped 2.0 was released. | Component | |||||||||||||||||||||||
29 | substantial_completion_date | The component's completion date if there is one along with a component level phase of "Post-construction" or "Complete". If there is a component phase and no completion date, then this date is null. If there is no component phase, then this date is the project-level substantial completion date which is defined as the earliest confirmed start date of a "Post-construction" or "Complete" phase. | Component or Project | |||||||||||||||||||||||
30 | substantial_completion_date_estimated | If substantial_completion_date is null, this is the earliest "estimated" project phase start or end date for a phase of "Post-construction" or "Complete". | Component or Project | |||||||||||||||||||||||
31 | srts_id | The Safe Routes to School plan identifier documented on a component. | Component | |||||||||||||||||||||||
32 | component_location_description | The component location description. | Component | |||||||||||||||||||||||
33 | project_name | The project name. | Project | |||||||||||||||||||||||
34 | project_name_secondary | The project secondary name. | Project | |||||||||||||||||||||||
35 | project_name_full | The full project name composed of the project name and secondary project name separated by a dash. | Project | |||||||||||||||||||||||
36 | project_description | The project description. | Project | |||||||||||||||||||||||
37 | ecapris_subproject_id | The subproject ID of the eCapris project associated with the component's Moped project. | Project | |||||||||||||||||||||||
38 | project_website | The project website. | Project | |||||||||||||||||||||||
39 | project_created_at | Date when the project was created. | Project | |||||||||||||||||||||||
40 | project_updated_at | Date when the project was last edited. | Project | |||||||||||||||||||||||
41 | component_phase_id | The component's phase ID that references phases in the internal moped_phases table. | Component | |||||||||||||||||||||||
42 | component_phase_name | The component's phase name that corresponds with the component_phase_id. | Component | |||||||||||||||||||||||
43 | component_phase_name_simple | The component's simple phase name that corresponds with the component_phase_id. | Component | |||||||||||||||||||||||
44 | project_phase_id | The project's current phase ID that references phases in the internal moped_phases table. | Project | |||||||||||||||||||||||
45 | project_phase_name | The project's current phase name that corresponds with the project_phase_id. | Project | |||||||||||||||||||||||
46 | project_phase_name_simple | The project's current simple phase name that corresponds with the project_phase_id. | Project | |||||||||||||||||||||||
47 | current_phase_name | The component's phase name if there is one, otherwise the current project phase name. | Project | |||||||||||||||||||||||
48 | current_phase_name_simple | The component's simple phase name if there is one, otherwise the current project simple phase name. | Project | |||||||||||||||||||||||
49 | project_team_members | A comma-separated list of team members and their roles delimited with a colon (First Last:Project Manager,First Last: Designer...). | Project | |||||||||||||||||||||||
50 | project_sponsor | The project's sponsor. | Project | |||||||||||||||||||||||
51 | project_lead | The project's lead. | Project | |||||||||||||||||||||||
52 | public_process_status | The project's public status. | Project | |||||||||||||||||||||||
53 | interim_project_id | The project's unique "facility" ID in the Access DB. Indicates the project was migrated from the ATSD Access DB in October 2023 when Moped 2.0 was released. | Project | |||||||||||||||||||||||
54 | project_partners | A comma-separated list of the project's partners. | Project | |||||||||||||||||||||||
55 | task_order_names | A comma-separated list of the task orders in a project's work activities. For example, "24ART81006 | CAMPO Grant PHBs, ..." | Project | |||||||||||||||||||||||
56 | funding_sources | A comma-separated list of the component's project funding row sources and programs separated by a dash. For example, "2020 Bond - Bikeways, 2018 Bond - Bikeways". | Project | |||||||||||||||||||||||
57 | project_status_update | The latest project status update from Moped or eCAPRIS if project has an associated eCAPRIS subproject id. | Project | |||||||||||||||||||||||
58 | project_status_update_date_created | The date that the latest status update was added. | Project | |||||||||||||||||||||||
59 | construction_start_date | The earliest start date of a construction phase on the component's project. | Project | |||||||||||||||||||||||
60 | project_inspector | A comma-separated list of project personnel who have the role of Inspector. | Project | |||||||||||||||||||||||
61 | project_designer | A comma-separated list of project personnel who have the role of Designer. | Project | |||||||||||||||||||||||
62 | project_tags | A comma-separated list of project tags. | Project | |||||||||||||||||||||||
63 | workgroup_contractors | A comma-seprated list of workgroup contractors documented in a project's work activities. | Project | |||||||||||||||||||||||
64 | contract_numbers | A comma-seprated list of contract numbers documented in a project's work activities. | Project | |||||||||||||||||||||||
65 | parent_project_id | The project ID of the parent project if there is one. | Project | |||||||||||||||||||||||
66 | parent_project_name | The project name of the parent project if there is one. | Project | |||||||||||||||||||||||
67 | parent_project_url | A URL that links to the parent project's view in Moped. | Project | |||||||||||||||||||||||
68 | parent_project_name_full | The project name and secondary name separated by a dash if there is a parent project. | Project | |||||||||||||||||||||||
69 | related_project_ids | A comma-separated list of related projects' IDs. | Project | |||||||||||||||||||||||
70 | related_project_ids_searchable | A comma-separated list of related projects' IDs with some amount of zero-padding to make it possible to search for a specific project ID with a string of them. For example, "000001, 000231, 0102910". | Project | |||||||||||||||||||||||
71 | knack_data_tracker_project_record_id | The unique ID of a Moped project as tracked in Data Tracker. | Project | |||||||||||||||||||||||
72 | project_url | A URL that links to the project's view in Moped. | Project | |||||||||||||||||||||||
73 | component_url | A URL that links to the component in the project map view in Moped. | Component | |||||||||||||||||||||||
74 | project_development_status | The next upcoming stage of project development (such as start of development, public meeting construction). | Project | |||||||||||||||||||||||
75 | project_development_status_date | The date of the next upcoming stage of project development (such as start of development, public meeting construction). | Project | |||||||||||||||||||||||
76 | project_development_status_date_calendar_year | Calendar year of the project development status date. For example, 2022. | Project | |||||||||||||||||||||||
77 | project_development_status_date_calendar_year_month | Calendar year and month of the project development status date. For example, October 2022. | Project | |||||||||||||||||||||||
78 | project_development_status_date_calendar_year_month_numeric | Numeric calendar year and month of the project development status date. For example, 2022-10. | Project | |||||||||||||||||||||||
79 | project_development_status_date_calendar_year_quarter | Calendar year quarter of the project development status date. For example, 4. | Project | |||||||||||||||||||||||
80 | project_development_status_date_fiscal_year | Fiscal year of the project development status date. For example, calendar year 2022 quarter 4 is fiscal year 2023. | Project | |||||||||||||||||||||||
81 | project_development_status_date_fiscal_year_quarter | Fiscal year quarter of the project development status date. For example, calendar year quarter 4 is fiscal year quarter 1. | Project | |||||||||||||||||||||||
82 | project_added_by | The Moped user who created the project. | Project | |||||||||||||||||||||||
83 | is_mapped | True if a component has a geometry; False if not. | Component | |||||||||||||||||||||||
84 | ||||||||||||||||||||||||||
85 | ||||||||||||||||||||||||||
86 | ||||||||||||||||||||||||||
87 | ||||||||||||||||||||||||||
88 | ||||||||||||||||||||||||||
89 | ||||||||||||||||||||||||||
90 | ||||||||||||||||||||||||||
91 | ||||||||||||||||||||||||||
92 | ||||||||||||||||||||||||||
93 | ||||||||||||||||||||||||||
94 | ||||||||||||||||||||||||||
95 | ||||||||||||||||||||||||||
96 | ||||||||||||||||||||||||||
97 | ||||||||||||||||||||||||||
98 | ||||||||||||||||||||||||||
99 | ||||||||||||||||||||||||||
100 |