DogPolicies

Which places match a common question, as a ready-made list: California national parks that allow dogs, off-leash dog beaches in California, state parks that allow dogs? Covers broad "list the ..." questions that are not about one town. Each list is fixed; it takes no county, type or off-leash filter. Without a slug it lists every question with its slug and result count; with a slug it returns that question's places (for example "off-leash-dog-beaches-california"), each with the dog rule, verified date and URL.

Has anything changed around where I am going since my last trip or since a date: a fee, a leash rule, a closure? Re-checks a saved itinerary or a destination: one area, one place or one stretch of highway. Inputs: place (city, county, neighborhood, area or region: "Tahoe", "Alameda", "Monterey") or near={lat, lon}, with radius_miles; or place_id for one place; or route (i-5, us-101, highway-1 ...) with from_mile and to_mile for the listed stops on that stretch. since as YYYY-MM-DD; optional outcome (confirmed, changed, source_gone, blocked, disputed). Returns verification events for places in scope, newest first, each with the place, outcome, date and record link, the rule-change log entries for them, and on the hosted server a separate corrections list (corrections filed for those places or decided since the date, by ticket id and status). An empty list means nothing was re-checked or changed in that window; an unknown name is an answer with did_you_mean. Example: "What changed near Monterey since September?" -> place="Monterey", since="2026-09-01"

What changed in the dog rules anywhere since a date: which fees, leash rules or closures were updated or found gone? A cheap poll for new changes across all the data, without re-reading records. Input: since as YYYY-MM-DD; optional outcome (confirmed, changed, source_gone, blocked, disputed), for example "changed" for only real rule changes. Returns events newest first, each naming the place, what happened, who checked, the date and a link to the record. On the hosted server a separate corrections list shows corrections people filed or whose status changed since the date: ticket id, place, kind of fact, status (filed, verified, rejected), dates and a status_url; what the reporter wrote is never included.

Which of these places is better for my dog: Carmel Beach or Asilomar, two parks, three hotels? Sets two to six known places side by side, fact by fact. Input: ids from search results ("carmel-beach", "asilomar-state-beach"); an exact name or a near miss resolves to the one clear match. Returns one row per fact (dogs allowed, leash rule, where dogs may go, pet fee, weight limit, pets per room, restrictions) and one column per place, with confidence, freshness, who confirmed it, and a citation for each. An id that matches nothing is listed under missing with close matches while the rest are still compared (outcome partial); fewer than two found is no_match with suggestions.

Will a hotel take my dog, and what will the pet fee come to: a 70 lb Lab under $50, two dogs for three nights near Palm Springs, the Motel 6 in Fresno? Does the weight, dog-count and fee arithmetic for the stay, hotel by hotel, against each hotel's published pet policy. Inputs: query (hotel name, city or brand), brand, county without "County", state "CA" or "NV", area (lake-tahoe, big-sur, east-bay), region, or near={lat, lon}; dog_weight_lb, dogs, nights, max_total_fee. Each hotel is a match, a possible (needs a call: case by case, weight unstated, "up to" fee) or excluded, with the arithmetic spelled out, the source URL and verified date. Amounts are pet fees, never room rates: there are no room prices here. Examples: - "Will a Monterey hotel take my 70 lb Lab for under $50?" -> county="Monterey", dog_weight_lb=70, max_total_fee=50 - "Two dogs, three nights near Palm Springs" -> near={lat:33.83, lon:-116.55}, dogs=2, nights=3 - "Is the Motel 6 in Fresno dog friendly?" -> query="Motel 6 Fresno" - "A hotel near LAX for my dog" -> query="LAX" (an airport code or name searches 5 miles around the airport) - "A Las Vegas hotel for my 60 lb dog" -> county="Clark", state="NV", dog_weight_lb=60

What is this hotel chain's pet policy: how many pets, weight limit, fee, exceptions? Answers chain-wide questions such as "What is Motel 6's pet policy?" or "Does Kimpton charge a pet fee?"; it does not work out one hotel's fee for a stay or say whether that hotel confirmed the chain policy. Brands covered: Best Western (best-western), Extended Stay America (extended-stay-america), Kimpton Hotels (kimpton), La Quinta by Wyndham (la-quinta), Motel 6 (motel-6), Red Roof Inn (red-roof). Input: brand id or name, e.g. "red-roof" or "Kimpton". Any other chain is not covered. Returns the published policy with the source URL, quote and verified date, and how many California and Nevada properties carry it.

What are the exact dog rules for this one place, and what is the official source: the quote, the publisher, the date checked? The leash rule, where dogs may go, fees and limits in full, with the official source and its quote, for one place known by id or name. Input: id as returned in any result (for example "carmel-beach"); an exact name works, and a near miss resolves to the one clear match, labeled resolved_from. An id nothing matches is an answer with did_you_mean, not an error. Returns every rule with display text and rule ids, each source with URL, publisher, capture date and quote, and facts the source does not state listed as not_stated. A place on I-5 in California also carries its position on the road (Caltrans mile, side, distance off the freeway) and any paired exit.

Where does this specific rule come from (a fee, a leash rule, a weight limit): what is the exact quote, the source and the date it was verified? Takes one rule id and returns the evidence behind that single fact. Rule ids look like "rul_<place uid>_<kind>" and appear in every place result as rule_records. Returns the rule's value, the source it cites with the quote, confidence, verified date, freshness and the place's citation line.

Is I-5 open right now: lane closures, chain controls, road weather and sign messages on the freeway in California, and the nearest dog stop to each? Live state, not rules: Caltrans feeds fetched within the last 15 minutes (fetched_at in the result), not verified rules. Covers the Grapevine and every other stretch of I-5 in California. Other highways are not covered. Inputs: from_mile and to_mile, or near={lat, lon} with direction and ahead_miles; with none, all of I-5 in California. Each condition is placed on the I-5 centerline (mile, s meters from San Ysidro) and matched to the nearest dog stop. If the feeds cannot be read the answer has outcome unavailable and the address of the live Caltrans page. A result older than two hours is marked stale. Examples: - "Is there a closure or chains on the Grapevine right now?" -> from_mile=170, to_mile=222 - "Weather and closures in the next 60 miles northbound from Redding" -> near={lat:40.59, lon:-122.39}, direction="north", ahead_miles=60

What is on I-5 between here and there for a dog: the next restroom stops with a pet area, the stops on the Grapevine, between Sacramento and Redding? For the freeway in California only, by one of eleven named stretches (sandiego, orange-la, grapevine, kern-westside, westside, delta, sacramento, valley, tehama, shasta, siskiyou), a mile range, or a window ahead of a point. It covers I-5 only, with no hotel fee arithmetic and no closures or chain controls. Inputs: strip, or from_mile and to_mile (Caltrans odometer), or near={lat, lon} with direction (north or south) and ahead_miles; family=true keeps stops whose official source states restrooms and a pet area or dog park; paired=true adds exits with places for people nearby (counted from OpenStreetMap, never named, not verified for restrooms) matched to the nearest dog-legal place. With none of these it lists the stretches. Each stop carries its mile, s in meters from San Ysidro, the side of the road, distance off the freeway, and restrooms, water, pet area and hours as the source states them, with source URL and verified date. A rest area Caltrans reports fully closed right now carries closed_now (Caltrans' reason and end time); it stays in the list and the text names the first open stop instead. Examples: - "What is between the Grapevine and Kettleman?" -> strip="grapevine" and strip="kern-westside" - "The next 5 family stops northbound from Stockton" -> near={lat:37.95, lon:-121.29}, direction="north", family=true, limit=5 - "Every stop between mile 300 and 340" -> from_mile=300, to_mile=340

What can my dog do in or around this town, neighborhood or region: beaches, parks, trails, hotels, campgrounds, cabins, patios and rest areas, nearest first? Answers "dog-friendly things in X" questions, grouped by kind. It does not check hotels against a dog's weight or a fee budget. Input: place as people say it: a city, county, neighborhood or alias ("Van Nuys", "Koreatown", "Venice Beach", "the Mission", "DTLA"), an area or region ("Lake Tahoe", "East Bay", "Central Valley"), or near={lat, lon}. Small spelling slips ("Montery") are corrected and labeled. If nothing is inside the radius it widens to 30, 60, then 100 miles and says so. Each result carries the dog rule, verified date and source URL. An unknown name comes back as an answer with did_you_mean, the nearest towns and next (a larger town or county that is covered). Examples: - "What can my dog do in Carmel?" -> place="Carmel" - "Dog beaches and parks around South Lake Tahoe" -> place="South Lake Tahoe", types=["beach","park"] - "Anything dog-friendly in Van Nuys?" -> place="Van Nuys" - "Anything dog-friendly within 5 miles of here" -> near={lat:36.6, lon:-121.9}, radius_miles=5

Plan a dog trip to a town: where can we stay with this dog, what is the pet fee for all the nights, what can we do each day, where can we eat? One answer covers a whole stay, such as "three nights in Monterey with our 70 lb Lab, pet fees under $150" or "camping near Mammoth Lakes". Inputs: place (a city, county, neighborhood, area or region, with small spelling slips corrected) or near={lat, lon}; dog_weight_lb, dogs, nights, max_total_fee, stay_types. Optional: start_date (dates each day), stay_id (build the plan on that stay), save=true (adds trip_url, a dogpolicies.com page showing the plan; the plan travels inside the link, nothing is stored). Returns stays that fit with the whole-stay pet fee worked out (a pet fee, never a room rate), stays that need a call to confirm, and "days": for each night the stay, a morning beach, trail or off-leash area, an afternoon park and a dinner patio, each a real record with source URL and verified date; a slot the data cannot fill is null with the reason (dinner often is). "plan_stay" shows the fee arithmetic and whether the dog's weight and number fit. Within 10 miles of I-5 in California it adds the drive leg: the town's mile and the next family stops each way. An unknown town is an answer with did_you_mean. The markdown answer is laid out as a trip document for the traveler. Examples: - "Three nights in Monterey with our 70 lb Lab, pet fees under $100" -> place="Monterey", dog_weight_lb=70, nights=3, max_total_fee=100 - "A weekend in South Lake Tahoe with two small dogs" -> place="South Lake Tahoe", dogs=2, nights=2 - "Camping near Mammoth Lakes with a dog" -> place="Mono County", stay_types=["campground","cabins"] - "Plan 4 nights in Carmel with two dogs and give me a link" -> place="Carmel-by-the-Sea", dogs=2, nights=4, save=true

Tell us a rule is wrong: the fee went up, a beach closed to dogs, a hotel now takes two pets. For a record the traveler says is wrong or out of date; this is the one tool that writes. The report goes to a person who re-reads the official source, and the record does not change until it is verified: a report is filed, not a fix. Inputs: place_id from a result, message (what is wrong, in the traveler's words), optional fact (which kind of fact is wrong), optional source_url of the official page, optional contact if the traveler offers one. No other personal detail is accepted. The answer carries a ticket id and a status_url. The ticket's status (filed, then verified or rejected) is public there; what they wrote is not.

Do I need chains on I-80 to Tahoe right now? Is US-50 open over Echo Summit? Caltrans chain controls, lane and ramp closures, road-weather stations and message-sign text on I-80 (San Francisco to the Nevada line), US-50 (West Sacramento to Stateline), I-15 (San Diego to Primm) and I-5 in California, each at its route mile with the nearest dog stop. Live state, not rules: Caltrans feed data fetched every 15 minutes (fetched_at in the result), never a verified fact. For the day of a mountain or desert drive: Donner Summit, Echo Summit, Cajon Pass, the Grapevine. It reports conditions, not places to stop: each condition carries only the nearest dog stop. Nevada roads and other highways are not covered. Inputs: route ("I-80", "80", "US 50", "Highway 50", "I-15", "I-5"); a window as from_mile and to_mile, or town (a town or named stretch on the route: Truckee, Donner Pass, South Lake Tahoe, Placerville, Cajon Pass, Barstow) with direction and ahead_miles; direction alone keeps that direction's closures, signs and chain controls. With no window, the whole route in California. chain_controls_in_effect is true when a Caltrans chain-control point in the window reports a control (any status but R-0), with Caltrans' own wording; a sign that mentions chains is listed under signs with its text. Each weather station says whether its reading is current (the feeds sometimes carry readings months old; those numbers are left out of the text). A document older than two hours is marked stale; when no document can be read the answer has outcome unavailable and the address of Caltrans QuickMap, the live map. Examples: - "Do I need chains on I-80 to Tahoe right now?" -> route="I-80", direction="east" - "Is Highway 50 open over Echo Summit?" -> route="Highway 50", town="Echo Summit" - "Closures on I-15 from Barstow to the Nevada line" -> route="I-15", town="Barstow", direction="north", ahead_miles=120

Where can we stop with the dog along this highway, in driving order: rest areas, travel stops with dog parks, hotels, campgrounds, parks and beaches, each with its mile and distance off the road? For a drive on I-5, US-101, Highway 1, I-15, I-80 or US-50 in California, or I-15, I-80, US-50, US-95 or US-93 in Nevada (each route stops at the state line). It lists stops, not closures or chain controls. Inputs: route (default i-5), a start as near={lat, lon} or from_mile, direction (north, south, east, west), ahead_miles or to_mile, dog_weight_lb and max_total_fee for stays. On I-5 add family=true (restrooms and a pet area stated by the source) or paired=true (an exit with places for people, plus the nearest dog-legal place). Each stop has its mile, side, distance off the road, dog rule, source URL and verified date; stays carry the whole-stay pet fee. On I-5 a rest area Caltrans reports fully closed right now carries closed_now (Caltrans' reason and end time), is left out of the "first open stop" in the text, and stays in the list. Examples: - "Driving north on I-5 from Los Angeles with a 70 lb dog, where can we stop?" -> near={lat:34.05, lon:-118.24}, direction="north", dog_weight_lb=70 - "Pet areas on the Grapevine" -> from_mile=170, to_mile=222, kinds=["rest_area","park"] - "Next restroom stop for the whole family, dog included, 40 miles north of Harris Ranch" -> near={lat:36.25, lon:-120.25}, direction="north", ahead_miles=40, family=true - "Heading south on 101 from San Francisco, where can the dog run?" -> route="us-101", near={lat:37.77, lon:-122.42}, direction="south" - "Driving I-80 east from Reno with a dog" -> route="i-80-nevada", near={lat:39.53, lon:-119.81}, direction="east"

Can my dog go to this place, or which parks, beaches, trails, campgrounds or patios allow dogs: "Can I bring my dog to Point Lobos?", "state parks in Marin that allow dogs", "off-leash beaches near San Diego"? Answers for one named place or a filtered list of one kind; each result's id names the place's full record, with every rule and source. Inputs: query (name, city or brand; words like "cabins", "hikes", "wineries" or "dog friendly hotels in Carmel" are read as the kind and the place), type (lodging, campground incl. RV parks, cabins, beach, park, trail, restaurant, rest_area, stop; "hotel", "dog park" or "hike" are read as these), dogs_allowed, off_leash, state "CA" or "NV", county without "County", area (lake-tahoe, big-sur, east-bay), or near={lat, lon}. Each result: yes, yes_restricted, no or varies, the rule in a sentence, verified date, URL and id. No match is an answer (outcome no_match) with did_you_mean, nearest and next. Nevada coverage is thin. Examples: - "Off-leash beaches near San Diego" -> type="beach", off_leash=true, near={lat:32.72, lon:-117.16} - "Can I bring my dog to Point Lobos?" -> query="Point Lobos" - "State parks in Marin County that allow dogs" -> type="park", county="Marin", dogs_allowed=true - "Lake Tahoe beaches in Nevada that allow dogs" -> type="beach", state="NV", dogs_allowed=true - "Off-leash dog parks in Las Vegas" -> type="park", off_leash=true, county="Clark", state="NV" - "RV parks in Fresno County that take dogs" -> type="campground", county="Fresno", dogs_allowed=true - "Dog-friendly cabins in June Lake" -> type="cabins", query="June Lake", dogs_allowed=true (query="June Lake cabins" works too) - "Restaurants with a dog-friendly patio in Alameda" -> type="restaurant", query="Alameda"

Can you tell me if the dog rules change at Carmel Beach before our trip? Can I follow changes near Lake Tahoe, or along I-5? For hearing about changes later, without asking again: it answers with a feed link (Atom and JSON Feed) for one place, a town, county, area or neighborhood with a radius, or a highway's stops, which any feed reader can follow. It computes the links and counts only; it signs nobody up, stores nothing and sends no email. Inputs: one of place (a place id from any answer, e.g. "carmel-beach"), near (a town, county, area, region or neighborhood, e.g. "Lake Tahoe", "Monterey", "Van Nuys") with radius_miles, or route (i-5, us-101, highway-1, i-15, i-80, us-50, or a Nevada route ending in -nevada) with from_mile and to_mile. Returns atom_url and json_url, how many verification events, rule changes and corrections the scope had in the last 90 days, the page for the scope, and share_text: a sentence with the link, written for the traveler. An unknown name is an answer with did_you_mean. Examples: - "Tell me if the rules change at Carmel Beach" -> place="carmel-beach" - "Can I get alerts for dog rule changes around Lake Tahoe?" -> near="Lake Tahoe" - "Follow changes on the Grapevine stretch of I-5" -> route="i-5", from_mile=170, to_mile=222