Data quality

This page reports, from the live database, how much the Paws of London venue directory actually knows. Every number is an aggregate over the current records and is recomputed as the data changes — nothing here is hand-typed.

The rule behind every count: missing is not negative. A venue with no dog-policy evidence is unknown, not unwelcoming; a missing amenity flag means “not recorded”, not “does not have”; missing opening hours are shown as unknown, never as open 24 hours. We publish these figures so that you can judge how much weight a listing deserves.

Live data-quality metrics for the Paws of London venue directory
MetricValueDefinition
Corpus
Live venues 890 Venue records with archived = false. Every other count on this page is over this set unless it says otherwise.
Boroughs covered 33 Distinct non-empty borough values among live venues. London has 33 boroughs; a higher number means at least one borough value is not an official borough name.
Most recent venue update 2 September 2026 The newest updated_at among live venues — the last time any venue record changed. This is a data-updated stamp, not an editorial review date.
Dog-policy evidence
Live venues with a website 835 (93.8%) Live venues whose website field is non-empty. A website is a place we can look for a policy; it is not itself evidence of one.
Live venues with a description 805 (90.4%) Live venues whose description field is non-empty. Most descriptions are AI-generated from imported facts and are not a dog-policy source.
Live venues with dog-policy notes 372 (41.8%) Live venues whose dog_policy_notes is non-empty after trimming whitespace. Many notes are absence statements such as “no information about dogs was found on the website”, so this is evidence text, not a count of dog-friendly venues.
Live venues with a website-extraction row 450 (50.6%) Live venues with at least one row in venue_website_extractions — the machine-read summary of the venue's own website. Roughly half of live venues have one; most of the rest have a website whose crawl failed.
Extractions where dogs_allowed is true 236 (52.4%) Extraction rows for live venues whose dogs_allowed.value is exactly true. This includes vets treating dogs as patients and pet shops selling dog food, so it is a lead for review, not a confirmed policy.
Extractions where dogs_allowed is false 116 (25.8%) Extraction rows for live venues whose dogs_allowed.value is exactly false. The evidence is usually “no information found”, i.e. absence rather than prohibition — it never becomes a not-dog-friendly label on its own.
Extractions with no dogs_allowed verdict 98 (21.8%) Extraction rows for live venues where dogs_allowed.value is null or the value key is missing (an empty extraction). Unknown is recorded as unknown.
Live venues with zero policy evidence 55 (6.2%) Live venues with no website, no dog-policy notes and no website-extraction row. Nothing on file either way; these are shown as unconfirmed, never as dog-friendly.
Venue confirmation
Venue-confirmed listings (active) 0 (0.0%) Live venues where verified_at is set and verification_expires_at is in the future — the venue itself confirmed its listing and the confirmation has not expired. Confirmation is only ever written by the venue's own reply; nothing infers it.
Venue-confirmed in the last 90 days 0 (0.0%) Active venue-confirmed listings whose verified_at is within the last 90 days.
Opening hours
Live venues with opening hours 815 (91.6%) Live venues whose opening_hours is not null. A null is an honest unknown and is displayed as “Hours unknown”, never as open.
Opening hours in the 24/7 shape 6 (0.7%) Live venues whose opening_hours has all seven days not marked closed, opening at 00:00 or 00:01 and closing at 23:59 or 00:00 — the shape the editor's “Open 24/7” button writes. For a pub, café or shop this is almost certainly a default rather than a fact, so it is tracked toward zero.
Amenities
Live venues with an amenity row 603 (67.8%) Live venues with a row in venue_amenities.
Amenity rows with nothing recorded 277 (45.9%) Amenity rows for live venues with no flag true and no false we can trust. Until migration 20260902130000 every flag is stored as false by default, so an all-false row is read as “nothing recorded”, not as “has none of these”; after it, unrecorded flags are null and a false counts as a recorded negative only on a row that says who recorded it (recorded_via) or has at least one true flag. Same population as the baseline's 277 all-false rows; the key stays amenity_rows_all_false for comparability.
Live venues with no amenity row 287 (32.2%) Live venues with no row in venue_amenities at all — pure unknown.

How to read these figures

Read next