-
Notifications
You must be signed in to change notification settings - Fork 40
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #181 from Data4Democracy/crash_import
Crash import
- Loading branch information
Showing
13 changed files
with
372 additions
and
48 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,51 @@ | ||
# City name | ||
city: brisbane | ||
# City centerpoint latitude & longitude (default geocoded values set) | ||
city_latitude: -27.4697707 | ||
city_longitude: 153.0251235 | ||
# Radius of city's road network from centerpoint in km, required if OSM has no polygon data (defaults to 20km) | ||
city_radius: 20 | ||
# The folder under data where this city's data is stored | ||
name: brisbane | ||
# If given, limit crashes to after start_year and before end_year | ||
# Recommended to limit to just a few years for now | ||
start_year: | ||
end_year: | ||
|
||
|
||
################################################################# | ||
# Configuration for data standardization | ||
|
||
# crash file configurations | ||
crashes_files: | ||
locations_2014_2017.csv: | ||
required: | ||
id: Crash_Ref_Number | ||
latitude: Crash_Latitude_GDA94 | ||
longitude: Crash_Longitude_GDA94 | ||
# If date supplied in single column: | ||
date_complete: Crash_Date | ||
# If date is separated into year/month/day: | ||
date_year: | ||
date_month: | ||
# Leave date_day empty if not available | ||
date_day: | ||
# If time is available and separate from date: | ||
time: | ||
# If time specified, time_format is one of: | ||
# default (HH:MM:SS) | ||
# seconds (since midnight) | ||
# military (HHMM) | ||
time_format: | ||
optional: | ||
summary: Crash_DCA_Description | ||
address: Crash_Street | ||
vehicles: | ||
bikes: | ||
|
||
# week on which to predict crashes (week, year) | ||
# Best practice is to choose a week towards the end of your crash data set | ||
# in format [month, year] | ||
time_target: [30, 2017] | ||
# specify how many weeks back to predict in output of train_model | ||
weeks_back: 1 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
# City name | ||
city: Pittsburgh, PA, USA | ||
# City centerpoint latitude & longitude (default geocoded values set) | ||
city_latitude: 40.44062479999999 | ||
city_longitude: -79.9958864 | ||
# Radius of city's road network from centerpoint in km, required if OSM has no polygon data (defaults to 20km) | ||
city_radius: 20 | ||
# The folder under data where this city's data is stored | ||
name: pittsburgh | ||
# If given, limit crashes to after start_year and before end_year | ||
# Recommended to limit to just a few years for now | ||
start_year: | ||
end_year: | ||
|
||
|
||
################################################################# | ||
# Configuration for data standardization | ||
|
||
# crash file configurations | ||
crashes_files: | ||
pittsburgh_2017.csv: | ||
required: | ||
id: _id | ||
latitude: DEC_LAT | ||
longitude: DEC_LONG | ||
# If date supplied in single column: | ||
date_complete: | ||
# If date is separated into year/month/day: | ||
date_year: CRASH_YEAR | ||
date_month: CRASH_MONTH | ||
# Leave date_day empty if not available | ||
date_day: | ||
# If time is available and separate from date: | ||
time: TIME_OF_DAY | ||
# If time specified, time_format is one of: | ||
# default (HH:MM:SS) | ||
# seconds (since midnight) | ||
# military (HHMM) | ||
time_format: military | ||
optional: | ||
summary: | ||
address: | ||
|
||
# week on which to predict crashes (week, year) | ||
# Best practice is to choose a week towards the end of your crash data set | ||
# in format [month, year] | ||
time_target: [30, 2017] | ||
# specify how many weeks back to predict in output of train_model | ||
weeks_back: 1 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.