RV loading clocks: data dictionary and reuse notes Can I Park My RV? | Study and source-read date: November 11, 2026 Study: https://caniparkmyrv.com/rv-loading-time-limits-study/ CSV: https://caniparkmyrv.com/data/rv-loading-clocks-nov11.csv JSON: https://caniparkmyrv.com/data/rv-loading-clocks-nov11.json WHAT A ROW MEANS One row is one selected private-property RV loading or service provision in one municipality. The ten examples cover six states. Nine rows use published municipal code; Glendale, Arizona, uses official municipal guidance. This is a purposive teaching sample drawn from existing site guides and readable municipal sources, not a random or nationally representative survey. No row is an address-specific parking approval. Other vehicle, zoning, ownership, location and activity requirements still apply. Published sources may omit later amendments. The source-read date is not a guarantee that every later ordinance or parcel-specific condition has been checked. Public-street permits, abandoned-vehicle or towing thresholds, general storage limits and guest-occupancy windows are outside this comparison. The data do not establish permission to sleep in an RV. FILE FORMAT The UTF-8 CSV contains a header followed by ten rows. Fields containing commas are quoted. The JSON contains study-level context and the same ten records in the "rows" array. In JSON, "hours" is a number; the other row fields are text. The final two CSV columns, "row_id" and "row_url", identify individual examples. Do not depend on row position. Use "row_id" when matching the CSV to the JSON. FIELD DICTIONARY city: Municipality name. Pair with "state" to distinguish namesakes. state: Two-letter U.S. state abbreviation. A city row is not a statewide rule. hours: Numeric boundary in hours. Read with "operator", "clock_type", "period" and "occurrences". It is not a standalone parking allowance or a common measure that can be averaged across these different provisions. operator: "at most" includes the numeric boundary; "strictly less than" excludes it. Tontitown's value of 8 is an excluded boundary, not an eight-hour allowance. clock_type: An editorial category for the source's time-accounting structure: - "rolling total": qualifying time is counted within the consecutive-day window in "period"; arrival does not by itself reset the allowance. - "per occurrence with monthly cap": the duration applies to a stay or occurrence, with a separate monthly count in "occurrences". - "calendar-week total": the total is attached to a calendar week, not a moving seven-day window. - "single period; recurrence not stated": the selected clause supplies a duration but does not specify a repeat-use rule. Do not infer unlimited use. These labels summarize accounting language; they are not quoted legal terms. period: The source-based accounting window or event to which "hours" applies. Preserve it when quoting or charting a row. A calendar week, a rolling window and one stay are not interchangeable. The field is a summary, not a quotation. occurrences: A separate visit or occurrence cap, when encoded. An empty string means no separate occurrence-count value was encoded for that total-time row; it does not mean zero, unlimited visits or that every other rule was cleared. "Not specified in cited clause" explicitly records an unresolved recurrence rule. "At most 2 per month" must remain attached to the per-occurrence limit. scope: The property, zoning, placement and vehicle scope of the selected rule. Do not apply a driveway provision to the street or a size-specific exception to every vehicle. This summary is not an exhaustive parcel-eligibility check. activities: The activities named in the selected provision. Loading, routine maintenance and repairs are not assumed equivalent. An activity missing from this clause may be addressed in a different local provision. conditions: Material qualifications and unresolved overlaps retained in the comparison. Keep these with reused rows. A caveat is not permission, and this field is not a complete statement of every applicable local requirement. section: The municipal-code section or guidance-page locator for this row. For amended model-code provisions, the locator includes the local amendment. source: URL of the published municipal source used for the row. Read it with "section". These are links to the publisher, not archived copies; the content at a "latest" URL or another live source URL may change. edition: The edition, supplement or publication label recorded for the source. Labels are not uniform. A posted chapter or brochure label is not an ordinance effective date or proof that all later amendments have been incorporated. source_type: "Published municipal code" or "Official municipal guidance". Guidance is labeled separately and must not be described as enacted code. source_read_date: Date the linked provision was read, in YYYY-MM-DD format. It is not a new legal-review date for the full city guide or an effective date. guide_url: Related Can I Park My RV? jurisdiction guide for wider context. The guide is not the primary municipal source. study_url: Canonical URL of the full comparison, including method and limits. row_id: Stable identifier within this comparison, using "rule-city-state". It identifies the selected example, not every parking rule in that city. row_url: Canonical study URL plus a fragment linking to that example's table row. Use this for an individual citation and retain the municipal-source link. REPRODUCING THE MAIN FINDING Select records where hours = 72 and operator = "at most": six of ten records. Group rolling-total rows by period. Combine rows with clock_type = "per occurrence with monthly cap" and occurrences = "At most 2 per month" into one model, while retaining their different period wording. This gives counts of 2, 1, 1 and 2: - Any 7 consecutive days: Bloomington, MN; Glendale, AZ (2 rows). - Every 10 consecutive calendar days: Brunswick, OH (1 row). - Any 30-day period: Centerburg, OH (1 row). - Each occurrence/stay, at most 2 per month: Lakeshire, MO; Ellisville, MO (2 rows). Ellisville specifies first driveway arrival. These groups describe the accounting structure of selected examples, not which city is more permissive. Do not convert them into an average allowed stay, a national percentage, a ranking, or a prediction of enforcement. CITING AND CHECKING AN EXAMPLE Study citation: Can I Park My RV? (November 11, 2026), "RV Loading Time Limits: 10 Local Rules Compared." https://caniparkmyrv.com/rv-loading-time-limits-study/ Individual example: Link to its row_url. Include the city and state, hours and operator, accounting period, occurrence cap, property/vehicle scope, activity and material conditions. Identify the source_type, section, edition and source_read_date. Link to the municipal source as well as this comparison, and check the source before using the rule for a current decision. Preserve unresolved caveats. A description that preserves the sample limit: "Among ten selected municipal examples, six use a 72-hour private-property loading or service limit, but those six use four different accounting models. The comparison is not a representative survey of U.S. parking rules." Attribution guidance does not grant a license to third-party publications. For source wording, refer to the linked municipal publisher.