How to download socrata files as csv

When a job fails you can click on it to get more details and see some error messaging on what may have been wrong on upload. The below is a sample error message for a job that had a record that could not be identified as a date type in one of the columns.

If you only have permission to one domain, you will be dropped into the directory for that domain. You should see the directories named with the dataset ID e. If you have permission to multiple domains, you will see them as subdirectories. You can download log. The import blueprint is how you tell the importer how to interpret your data. Note that you must provide a columns array, and both fields inside it are required.

If the file is small enough, the importer will import it, and return to you the metadata of the newly created view just as if you requested the metadata of an already-existing dataset within the same request.

However, if the importer determines that your import could take a while, it will instead return a response with an HTTP status code of , and a body that looks like the following:. To check on the status of your in-flight import, use your ticket value with a GET request to the following API endpoint:.

It provides two methods to solve these problems. Just like with importing above, if the file is small the importer with just process it immediately and return the metadata of the view. As above, if the importer decides that the file is too large and might take some time to fully import, it will respond with an HTTP with a ticket in the body. Trims leading and trailing whitespace before inserting the data into the dataset.

Also trims quoted values e. Trims leading and trailing whitespace that already exists in the dataset. This flag is generally only necessary if data was previously added to the dataset with whitespace due to trimWhitespace being false.

Relevant only to Location columns. If you are not providing the latitude and longitude in the synthetic location e. Socrata will geocode the location , set this to "true" to minimize perceived changes to your data. If you are providing the latitude and longitude in the synthetic location, set this to "false".

For new backend datasets, this will affect how data is imported into text fields. If true, then empty text not whitespace will be treated as NULL. If false, it will be treated as the empty string. Any joda-formated string is acceptable. If you want to allow multiple formats to be accepted, then you can specify a list of values rather than a single value e. A list of accepted names is available at this Joda documentation page. Allows transformation of multiple columns into one or more Location columns during insert.

See See the Location column and geocoding configuration section for an example.