Back to Tideswell community information

Use the data

Last updated 9 October 2026

Everything on tideswell.org.uk comes from one shared database of local information: places, organisations, services, events, notices and bus routes in Tideswell and the villages around it, each checked by local editors. You can use it on your own website, in a calendar, or in your own code. You do not need an account, and you do not need to ask first. The database is available under the Open Database Licence (ODbL); the terms are below.

One set of facts, three ways to use it. The Tideswell community information database feeds blocks for websites (tideswell.org.uk/embed, for site owners), feeds (tideswell.org.uk/whats-on.ics, for anyone, in phones, calendars and readers) and a REST API (for developers, in apps, maps and research). Terms: credit Tideswell community information with a link; share a database built from ours under the ODbL too; photographs keep their own licences; keep each item's last-checked line and its Something changed? link; cache answers; organisations sending their own events in need an account.
One set of facts, three ways to use it. Select the picture to see it full size.

Three ways to use it

On a website: blocks

A block is a finished, styled listing, such as what's on, clubs and groups, places to eat, road works or buses, that your site shows with no programming. Each one carries the "last checked" line and a "Something changed? Tell us" link on every item.

curl "https://tideswell.org.uk/embed/organisations?kinds=club&categories=sport"

In a calendar or feed reader: feeds

What's on is published as three feeds that anyone can subscribe to:

Each takes days (1 to 90, default 60), community (one village, such as litton) and categories (topics, such as music,theatre), for example whats-on.ics?categories=music,theatre. An organisation's own feed, for its website, newsletter or members' calendars, takes organisation (its id), and a venue's takes place; the "What's on" embed takes the same two. One occurrence on its own, as the calendar file behind an "Add to calendar" link, is whats-on.ics?event=<id>&at=<start>, with the start in UTC as 20261109T190000Z (the .ics file only; hub is the one other parameter it takes).

In your own code: the REST API

The REST API gives every published record as JSON. It is PostgREST, which turns the database's public views into web addresses and lets you filter, sort and page them.

Addresshttps://kwiqdfriiuyaqqchgvrr.supabase.co/rest/v1/
KeySend this in an apikey header. It is meant to be public: the page at tideswell.org.uk uses the same key, and it can only read published records.
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6Imt3aXFkZnJpaXV5YXFxY2hndnJyIiwicm9sZSI6ImFub24iLCJpYXQiOjE3OTEwNDAzMDYsImV4cCI6MjEwNjYxNjMwNn0.phFdAeRavxgDUaqw9n4P4V1MqQb3-32fTUqzCyHmQxU
Descriptiontideswell.org.uk/openapi.json (OpenAPI 2.0), for Postman, Insomnia or Swagger UI.
curl -sg "https://kwiqdfriiuyaqqchgvrr.supabase.co/rest/v1/places?select=name,kind,street&kind=in.(pub,cafe,restaurant,takeaway)&order=name" \
  -H "apikey: THE_KEY_ABOVE"

What you can read

ViewWhat it holds
placesVenues, pubs, cafés, restaurants, shops, churches, defibrillators and more, with address, position and opening hours.
organisationsClubs, groups, charities, churches, businesses and public bodies, with their own published contact details. running is running or pausing (a group not meeting at the moment but expected back, with welcomes_members when it said so; its regular events and services are left out while it pauses); a group that has stopped, or that the editors are asking about, is not listed at all, so active is always true.
servicesWhat organisations offer: who it is for, cost, how to get it.
events_upcomingOne row per occurrence over the next 90 days. events has every occurrence; event_series one row per series.
notices_currentRoad works, closures, planning applications and other notices in force. notices has past ones too.
transport_routes, transport_stopsBus routes with their operator and a link to the official timetable, and the stops they serve.
communities, hubsThe villages, and the hubs that show them.
categoriesThe topics records can be tagged with.
media, record_socialPhotographs with their credits and licences; Facebook and Instagram links.
event_postersOrganisers' own posters for events, as a picture or a PDF, with a description. Each file is at https://tideswell.org.uk/poster/<file> while its event is listed (see the licence).
map_layers, map_pointsMaps that local groups keep on their own websites, shown on the hub's map as a choice: so far the Tideswell & District Environment Group's hedgehog sightings, each with its type (seen alive, signs, found dead), position, year and parish. Not open data (see the licence).
sources, record_sourcesWhere each record's facts come from.
recordsEvery published record of every kind, in one list.
record_linksLinks between published records, with both names: a notice affects a place or a bus route, a new shop replaces an old one, an event is part of a festival, two records are related, an article mentions a record. For the records you show, ask with or=(from_record_id.in.(…),to_record_id.in.(…)).
articlesPointers to stories on local news sites (see the licence).

Five functions answer place questions: rpc/lookup_postcode (where a postcode is, its parish and whether it is still in use), rpc/records_near (records within a distance), rpc/nearest_hubs, rpc/resolve_area and rpc/records_in_area. The description gives every field and setting.

Filtering

With curl, add -g so the braces are not read as a pattern. The current types and topics for each kind of record are in tideswell.org.uk/embed/types.

The licence

The Tideswell community information database is made available under the Open Database Licence 1.0. In short, you may copy, share and build on it, for any purpose, if you:

  1. Credit the source: "Contains information from Tideswell community information (tideswell.org.uk), available under the Open Database Licence." with a link to tideswell.org.uk, wherever you show or share it.
  2. Share alike: if you publish a database you have built from ours, make it available under the ODbL too. A website, map or app that simply shows the information is not a database in this sense, but still needs the credit.
  3. Keep it open: if you lock a copy away with technical measures, also offer an unlocked one.

Some things are not covered by the ODbL:

Parts of the location data are from others, under licences that ask for these credits: positions © OpenStreetMap contributors, available under the Open Database Licence; parish boundaries and postcode positions from the Office for National Statistics (Parishes and Non-Civil Parished Areas, May 2026; ONS Postcode Directory, August 2026), licensed under the Open Government Licence v3.0. Contains OS data © Crown copyright and database right 2026. Contains Royal Mail data © Royal Mail copyright and database right 2026.

This summary is not the licence; the full text is what applies.

Please

The addresses and fields on this page are a stable contract. If one ever has to change in a way that would break your use of it, the new version will run alongside the old one for a while, and this page will say so first.

Sending information in

Anyone can tell us about something new or changed, with no account, using the pencil on any item or the tell-us page; an editor checks every note before anything is published. An organisation that wants to send its own events and changes straight from its own system can have an account limited to its own records: ask us.

Questions

Email data at tideswell dot org dot uk. The information itself contains no personal data; how the notes people send are handled is in the privacy notice.