Peels can now mirror official public drop-off datasets into stub listings. NYC is the first feed (nyc-dsny-food-scrap).
NYC mirrored listings use the Stubs USA account. Do not CSV-edit mirrored rows unless you intend the next sync to overwrite them. Claimed listings stop syncing.
See Open Data Listings and docs/open-data-listings.md.
Boston, Brisbane, and open-data feeds should share one avatar file per city or feed, not one file per site.
listing_avatars bucket in Studio.listings.avatar for every stub in the batch. For open data, also store it on open_data_feeds.default_avatar, for example open_data/nyc-dsny-food-scrap.png.listing_avatars. Many rows may point at the same path. That is intentional.Local, staging, and production Storage are separate. Upload the file in each environment you care about.
Do not put these marks in the static bucket. That would need extra app code. Stay on listing_avatars, same as existing council stubs.
Stubs are listings created by the Peels team on behalf of (usually) local government food scrap drop-off points. Here’s an example of one.
They differ from normal listings in the following ways:
Think of them like stubs on Wikipedia; they’re placeholders until someone else (hopefully an owner or authority) takes over. That’s why the language around stubs on Peels is about encouraging the owner of the place to take over the listing.
Stubs are designed to be helpful, not to simply populate the Peels map. So only add a stub if the location is permanent, the information is correct, there are external links, and you feel strongly that the owner or manager of the space would endorse the public coming over to drop scraps off uninvited. Think city-run food scrap drop-off points with an official website to link to.