ReCollect Waste Data Guide

This page explains the data format and content that we need from you to provide accurate waste collection schedules. It also outlines options for ongoing data connectors.

If you or your GIS department have any questions, please send us an email!

Schedules For All

We want to provide a great experience for those searching — and finding — their waste collection schedule.

In addition to the people you serve, ReCollect can display collection schedules for a wide range of specific addresses, or customized messages for addresses you don’t service, like:

  • Multi-family units (like apartment buildings)
  • Industrial, Commercial or Institutional addresses (like businesses or schools)
  • Pilot areas (like a food scraps collection pilot area)
  • Addresses in neighboring municipalities, that frequently believe they are served by your organization (but are not).

Detailed data helps provide a great experience for visitors to your website and fewer calls to your help line!

General Data Requirements

If all waste types have weekly collection for all addresses, we only require one address file containing a field for the collection day. If waste collection is variable (weekly Trash, bi-weekly Recycle), we require both an address file and a calendar file that specifies the pattern of collection.

Your data must:

  1. Be in either a tabular format (ex. CSV, Excel, Access), GIS format (Shape, Geodatabase), or open data/rest endpoints.
  2. Use a standard schema (column headers), which won’t change with each update.

Address Data Format and Schema

Full Street Name, House Number, and Unit Number must be listed separately. Your address data cannot include special symbols. Each row must refer to one address, and not a range. All address data for single-family (and optionally, multi-family and/or commercial dwellings) must include the following columns:

  •       Route ID (required, this is the pickup information for each address whether it be a route ID, route number, zone name or day. This must match the Route ID in the Calendar file) 
  •       House Number (required, separate from unit number)
  •       Unit Number (optional, for multi-family)
  •       Full Street Name (include directional prefixes/suffixes, for example: Main St W, or NW Broadway Ave)
  •       Alternate Street Name (optional, this is for addresses that could be typed in more than one way by your end users (ex: Main St W vs W Main St).  Semicolon separated list or separate columns are fine.
  •       City/town name
  •       Latitude (Y) coordinate (optional, but required if you want to issue service alerts to targeted geo-zones; preferably WGS84 format, but if not the coordinate system must be identified to us)
  •       Longitude (X) coordinate (optional, see above)
  •       Unique ID (optional, from your system. Must be a unique and permanent identifier that doesn’t change between updates)

Here is the exact format your address data must appear in and the column headers that need to be included:

Address Data

Calendar Data Format and Schema

Calendar data is only provided initially, when setting up your collection schedules, OR any time you make significant route changes. Calendar data can be emailed directly to ReCollect. Zone changes, such as moving yard waste to organics as a pilot will require new calendar data. For any questions about this, please send us an email!

Your calendar data must include the following required columns:

  •   Route ID (This must match the Route ID in the Address file)
  •   Collection days (Required if Route ID is not a day of the week)
  •   Frequency of each collection type (eg., “every-week”, “first-week”, “second-week”, “A”, or “B”)
  •   Start date of each collection type

 Here is the exact format your calendar data must appear in and the column headers that need to be included:

Calendar Data

Address Data Updates

We want to ensure people can access the most up-to-date address data. Every data update must use the same schema (ie, column headers) as the initial data upload. If the schema changes, there will be errors in your data, as a result.

Option 1

Once or twice a year, send ReCollect GIS or tabular file/s containing all your address data. You must use the same column headers as your initial data upload.

Option 2


Bi-monthly or quarterly, use ReCollect’s “drag-and-drop” feature to upload a CSV file containing all your address data. Use the same column headers as your initial data upload

Option 3

Nightly or weekly, push GIS or tabular file(s) containing all your address data to ReCollect’s SFTP (secure file transfer protocol) site. You’ll need to send ReCollect your public SSH key to access ReCollect’s SFTP.

Option 4

Nightly or weekly, ReCollect can pull GIS, tabular file(s) containing all your address data from your SFTP or FTP site. You’ll need to provide ReCollect with credentials to access these sites.

Option 5

On a specified interval, ReCollect can pull all your address data from an open data portal/rest endpoint. You’ll need to provide ReCollect with credentials to access these sites.


Updating From Your APIs

ReCollect can pull data directly from your APIs and open data portals. Please shoot an email to with the details about how to connect to your API or open data portal, what data to look for, and which fields should be used.

The connector will check your services at a scheduled interval. Let us know the time and frequency that your systems are updated, and we can tailor the connector to match.


Pushing Data To ReCollect’s SFTP

Your systems can push data to ReCollect’s SFTP server whenever it changes.

The SFTP server uses SSH Public Keys for authentication. To get started, create a SSH Keypair and send the public key to

The private key should be securely stored on your servers, and is only needed for connecting to the ReCollect SFTP server. If you ever need to revoke a key, just shoot us an email.

When ReCollect receives your public key, our team will create an SFTP account for your organization and send you details on how to connect. 

Creating SSH Keys

These instructions describe the process on Linux, but you can create SSH keys using OpenSSL or other tools on many platforms.


  1. First, you should have a tool called ssh-keygen installed on your system. If it is not found, you will need to install openssh-client or another such package.
  2. Then, create a new key with: ssh-keygen -t rsa -b 4096 -f recollect-sftp-key.
  3. This will prompt for a passphrase for the key. Hit Enter twice to supply no passphrase. (This key will likely be used by your automated processes, so we do not wish to require a passphrase for every use. The flip side of this is that the private key should be kept private – it essentially becomes your password.)
  4. You should now have two files created:
    • recollect-sftp-key – This is your private key. Keep it private to your organization and processes.
    • – This is the public key. This will be shared with ReCollect.
  5. Send (via copy/paste or as an attachment) to ReCollect Support in an email.

Holiday Schedules

Please provide a list of holidays observed in your region and how they affect your services. Are services delayed by a single or multiple days after a holiday? Are services delayed for the entire week, including after the bumped collection day? If there are bumps that potentially bump into the weekend, are both Saturday and Sunday pickup days or do all end on Saturday?

Common holidays we see observed are as follows but please let us know what your community observes and more importantly how the holiday affects your service schedules:


  • New Year’s Day
  • Family Day (Canada)
  • MLK Jr. Day (US)
  • President’s Day (US)
  • Good Friday (Canada)
  • Easter Monday (Canada)
  • Memorial Day (US)
  • Victoria Day (Canada)
  • Canada Day
  • Independence Day (US)
  • Labor Day (Canada and US)
  • Thanksgiving Day (Canada and US)
  • Day after Thanksgiving Day (US)
  • Christmas Day (Canada and US)
  • Boxing Day (Canada)
  • Various provincial and state holidays (Canada and US)