Where RVSpot's park data comes from, how it's verified, what "data quality" means in practice, and how to report errors or update your park's listing.
The foundation of every park record in RVSpot is a verified Google Place ID. This means:
Records imported from Google Places are tagged with data_source = 'google_places_v1' in our database. This is the highest-confidence data tier.
When a park owner claims their listing, they gain full edit access to all park fields. Operator-provided data is considered the most authoritative source for:
All operator edits are logged and reviewed before going live. Operators are responsible for keeping their park's data accurate — RVSpot displays whatever operators submit, and travelers are encouraged to verify critical details directly with the park before booking.
Travelers can submit:
Community data is moderated before it influences a park's public listing. Reviews require verified submission (email or sign-in) and are reviewed for authenticity.
| Data Source | Confidence Level | Notes |
|---|---|---|
| Google Places API (google_places_v1) | Highest | Verified real-world business, GPS coordinates confirmed |
| Operator-claimed listing | High | Owner-provided, reviewed before publication |
| Community speed test | Medium | Measured by traveler, attributed to specific park and date |
| Community review | Medium | Moderated, requires verified submission |
| AI-enriched description (ai_enriched_v1) | Low | Template-generated description for parks without operator content — clearly distinguished from operator-written copy |
When RVSpot displays a verified data point, it means:
What "verified" does not mean:
RVSpot always recommends verifying critical details (especially pricing, rig length limits, and availability) directly with the park before booking.
| Data Field | Update Mechanism | Frequency |
|---|---|---|
| Park rates (nightly/weekly/monthly) | Operator edit | Real time (when operator updates) |
| Amenity details | Operator edit | Real time (when operator updates) |
| Wi-Fi speed tier | Operator edit + community speed tests | Real time for operator; moderated for community |
| Reviews and ratings | Community submission + moderation | Rolling (typically 1–5 business days) |
| Core park identity (from Google Places) | Automated refresh from source | Quarterly |
| FEMA flood zone | FEMA NFHL API enrichment | Annual refresh |
| Nearby service counts | OpenStreetMap Overpass API | Periodic enrichment (planned Sprint 9) |
Found something wrong? There are three ways to report it:
We review all correction requests within 5 business days. For critical errors (wrong contact information, closed parks still showing as active), we prioritize same-day review.
Core park data (name, location, contact, basic amenities) is sourced from Google Places API and verified against public records. Rates, amenities, and Work-Ready data come from operators who claim their listings and from community submissions. All imports require a verified Google Place ID — no synthetic park records are created.
Work-Ready status requires verified speeds of 25+ Mbps or a dedicated coworking space. Speed verification comes from operator-reported data (when a park claims its listing) and community speed tests (submitted by travelers during stays). "Wi-Fi available" alone does not earn the Work-Ready badge.
Claimed parks update in real time as operators make changes. Unclaimed parks refresh from verified sources quarterly. Community corrections are reviewed and applied on a rolling basis. Always verify current rates and conditions directly with the park before booking.
Park operators: claim your listing at rvspot.net/claim for direct edit access. Travelers: use the "Report an error" link on the park page or contact us. We review corrections within 5 business days.
Claim your listing to update rates, amenities, and Work-Ready status — free for park operators.
Claim Your Listing