{"version":"1.3.0","commands":{"clear-cache":{"id":"clear-cache","description":"Some commands in this toolkit download files to a temporary directory. These files can be rather large, and it can be helpful to clear this data to reclaim disk space.","pluginName":"movement-data-toolkit","pluginType":"core","aliases":[],"examples":["$ mdt clear-cache"],"flags":{},"args":[]},"create-geometry-file":{"id":"create-geometry-file","description":"Creates a geojson file that contains the geometries for each road segment in the specified city, as well as both the corresponding OSM identifiers for each road segment.\n    \nThe produced file can help avoid the need to download and manipulate OSM geometries from the web yourself.","pluginName":"movement-data-toolkit","pluginType":"core","aliases":[],"examples":["$ mdt create-geometry-file cincinnati 2018 > my-output-file.geojson"],"flags":{"api-host":{"name":"api-host","type":"option","description":"Which host to use for Movement API requests (only really useful for local testing)","hidden":true},"log-level":{"name":"log-level","type":"option","description":"What types of logs should be emitted?","options":["INFO","DEBUG"],"default":"INFO"},"output":{"name":"output","type":"option","char":"o","description":"File to write output to (writes to stdout by default)"},"bbox":{"name":"bbox","type":"option","description":"Features outside of this bounding box will be removed from output. Should be of the form minX,minY,maxX,maxY like \"-10.0,-10.0,10.0,10.0\" (see https://tools.ietf.org/html/rfc7946#section-5)"},"driving-side":{"name":"driving-side","type":"option","description":"Road geometries are \"twinned\" in the output file to visualize speeds in both directions, to do this accurately you should use --driving-side=\"LEFT\" for places like the UK or Australia.","options":["LEFT","RIGHT"],"default":"RIGHT"},"format":{"name":"format","type":"option","description":"Format to use for the output file","options":["GEOJSON","CSV"],"default":"GEOJSON"},"geom-format":{"name":"geom-format","type":"option","description":"Changes format of geometries in output file (only supported with --format=CSV)","options":["GEOJSON","WKT"],"default":"GEOJSON"},"twin":{"name":"twin","type":"boolean","description":"Whether or not to \"twin\" road geometries in the output file – this duplicates and offset two-way roads so you can visualize data in both directions. Defaults to true.","allowNo":true}},"args":[{"name":"city","description":"Slug of the city to download data for. You can find this value in the URL when accessing data on the Movement website."},{"name":"year","description":"Movement publishes mapping files and road geometries yearly, specify the year you would like to use here"}]},"speeds-to-geojson":{"id":"speeds-to-geojson","description":"Downloads and processes Movement speeds data into a geojson file that can be visualized with Kepler.gl or other geospatial visualization tools.\n\nNote: Becuase our speeds data CSVs have an hourly granularity, the results produced by this command are technically an average of averages and may differ slightly from results shown in the app at movement.uber.com.","pluginName":"movement-data-toolkit","pluginType":"core","aliases":[],"examples":["$ mdt speeds-to-geojson cincinnati 2018-01-01 2018-01-31 > my-output-file.geojson"],"flags":{"api-host":{"name":"api-host","type":"option","description":"Which host to use for Movement API requests (only really useful for local testing)","hidden":true},"log-level":{"name":"log-level","type":"option","description":"What types of logs should be emitted?","options":["INFO","DEBUG"],"default":"INFO"},"output":{"name":"output","type":"option","char":"o","description":"File to write output to (writes to stdout by default)"},"bbox":{"name":"bbox","type":"option","description":"Features outside of this bounding box will be removed from output. Should be of the form minX,minY,maxX,maxY like \"-10.0,-10.0,10.0,10.0\" (see https://tools.ietf.org/html/rfc7946#section-5)"},"driving-side":{"name":"driving-side","type":"option","description":"Road geometries are \"twinned\" in the output file to visualize speeds in both directions, to do this accurately you should use --driving-side=\"LEFT\" for places like the UK or Australia.","options":["LEFT","RIGHT"],"default":"RIGHT"},"twin":{"name":"twin","type":"boolean","description":"Whether or not to \"twin\" road geometries in the output file – this duplicates and offset two-way roads so you can visualize data in both directions. Defaults to true.","allowNo":true}},"args":[{"name":"city","description":"Slug of the city to download data for. You can find this value in the URL when accessing data on the Movement website."},{"name":"startDate","description":"Fetch data starting from this date"},{"name":"endDate","description":"Fetch data up to and including this date"}]},"speeds-transform":{"id":"speeds-transform","description":"Downloads and transforms Movement Speeds data, filtering by date range and optional bounding box and producing a CSV with speed values mapped to OSM identifiers.","pluginName":"movement-data-toolkit","pluginType":"core","aliases":[],"examples":["$ mdt speeds-transform historical cincinnati 2018-01-01 2018-01-31 > filtered.csv"],"flags":{"api-host":{"name":"api-host","type":"option","description":"Which host to use for Movement API requests (only really useful for local testing)","hidden":true},"log-level":{"name":"log-level","type":"option","description":"What types of logs should be emitted?","options":["INFO","DEBUG"],"default":"INFO"},"output":{"name":"output","type":"option","char":"o","description":"File to write output to (writes to stdout by default)"},"bbox":{"name":"bbox","type":"option","description":"Features outside of this bounding box will be removed from output. Should be of the form minX,minY,maxX,maxY like \"-10.0,-10.0,10.0,10.0\" (see https://tools.ietf.org/html/rfc7946#section-5)"}},"args":[{"name":"type","description":"Either \"historical\" for the monthly historical time series or \"stats\" for the quarterly statistics file."},{"name":"city","description":"Slug of the city to download data for. You can find this value in the URL when accessing data on the Movement website."},{"name":"startDate","description":"Fetch data starting from this date"},{"name":"endDate","description":"Fetch data up to and including this date"}]}}}