To export the camera post data about your containers as a .csv file, click on the "Insights" tab, then "Data Download":
Enter the date range of the posts you would like to export and click download (note that all timestamps are stored in UTC, and the date range you select correlates to dates based on the UTC timezone):
The download will initiate from your browser. Note that depending on the size of your date range and the number of containers in your organization, the file size could be quite large and slow to download.
Once the download is complete you will have a .csv file that can be opened in your spreadsheet application of choice. The file will include the following columns:
organization: Your organization's identifier (example: compologyinc)
occurredAt: The UTC timestamp of when this event occurred and date it was captured (example: 2017-11-01T01:58:59.615z)
customerId: If the container was assigned to a customer when this event occurred, the unique identifier for the customer (typically an internal reference or billing id, example: 30003)
customerName: If the container was assigned to a customer when this event occurred, the name of the customer (example: Blue Bottle Coffee)
serviceLocationId: If the container was assigned to a service location when this event occurred, the unique identifier for the service location (typically an internal reference or billing id, example: 461)
serviceLocationDescription: If the container was assigned to a service location when this event occurred, the name of the service location (example: Ferry Building)
containerId: The unique Compology identifier for the container. This identifier uniquely identifies the physical box (example: AA4M1L41R9TD)
containerDescription: The current name of the container (typically painted on the container). While duplicates are rare, this is not guaranteed to be unique (example: 3-5201)
containerContentType: The designated content type of the container (example: refuse)
containerCubicYards: The branded size of the container, in cubic yards (example: 3)
level: If present, the level of content within the container at this event as a percentage, inclusive, between 0 and 100. This value may update for recent events as Compology has more time to classify data but should be relatively static 6 hours after the occurredAt timestamp (example: 35)
wasEmptied: If present, indicates whether the container was emptied prior to this event. This value may update for recent events as Compology has more time to classify data but should be relatively static 12 hours after the occurredAt timestamp (example: t)
emptyOccurredAt: If present (when wasEmptied is t), the UTC timestamp representing Compology's best guess at when the bin was emptied. This value may update for recent events as Compology has more time to classify data but should be relatively static 12 hours after the occurredAt timestamp (example: 2017-11-01T01:31:42.982z)
levelAtEmpty: If present (when wasEmptied is t), indicates the last level detected prior to the empty event. This column will only be populated for posts that occured after October 31st, 2019 (example: 35)
latitude: If present, the latitude of the container at this event in decimal degrees (example: 37.771777)
longitude: If present, the longitude of the container at this event in decimal degrees (example: -122.407368)
positionAccuracy: If present, the expected margin of error of the latitude/longitude values in meters (example: 9.3)