How to create an interactive campsite map guests can book from

Decide what job the map has to do

A fire plan, a printed welcome map and a booking map serve different decisions. A booking map must help a guest understand the site while giving the reservation system enough information to reject combinations that will not work. Pitch boundaries, dimensions, access and stable identifiers therefore matter more than decorative detail.

Keep an operational layer and a guest-facing presentation layer, but derive both from the same objects. Roads, pitches and amenities should not be redrawn in three unrelated files. When the site changes, one controlled update should flow to the front desk and the booking journey.

Collect evidence before drawing

Record the source and date of every input. A high-resolution image can still be several seasons out of date. Walk the site before launch and mark uncertain boundaries for verification instead of making the drawing look more precise than the evidence.

• A current aerial or orthophoto with visible boundaries, roads and tree cover.
• The paper map, PDF, CAD plan or reception-board photograph staff currently use.
• OpenStreetMap features for surrounding roads, water, buildings and site context.
• A pitch register containing number, type, length, width, surface, power and restrictions.
• Recent changes that are missing from imagery, including closed roads, new rows and removed pitches.

OpenStreetMap Foundation

Draw from large, stable features to small ones

1. 1

   Site boundary

   Establish the land guests can use and the edges that must not be crossed.

2. 2

   Roads and paths

   Map vehicle access before pitches; bends and direction determine what can reach a row.

3. 3

   Pitch polygons

   Draw real boundaries with consistent pitch numbers rather than placing dots at approximate centres.

4. 4

   Amenities and hazards

   Add reception, sanitation, water, waste, play areas, emergency exits and restricted zones.

5. 5

   Guest styling

   Only then choose colours, icons, labels and the level of visual detail shown during booking.

Attach data that can prevent a bad booking

Filter for fit before inviting preference

Ask for stay dates and equipment before presenting exact pitches. Availability removes occupied pitches; equipment dimensions remove unsafe fits; mandatory requirements remove unsuitable facilities. The guest can then compare location and softer preferences within a set that will actually work.

This order matters. Showing every attractive pitch and rejecting the selection at checkout produces frustration. Accepting an impossible selection creates a phone call and manual move after payment, which defeats the purpose of self-service booking.

Test the map under difficult conditions

The map is ready when guests and staff refer to the same pitch, attributes and status without translation. After launch, measure filters used, exact-pitch selection, booking abandonment, pre-arrival questions and manual relocations. Improve the data before adding more visual ornament.

• Use a busy weekend when only a scattered set of pitches remains.
• Search with a long motorhome, a caravan plus awning and a small tent.
• Try keyboard navigation, touch targets and labels on a narrow phone.
• Move an existing reservation and verify old and new availability immediately.
• Close a pitch temporarily and check the map, calendar and booking page.
• Ask a new seasonal employee to locate an arrival using only the information shown.

Maintain the map as a system of record

Assign an owner for pitch geometry and identifiers. Walk the property before each season and update operational changes as they happen. Keep a short audit trail explaining why a boundary, restriction or pitch type changed.

Respect the licence and attribution requirements of every source. OpenStreetMap requires attribution, while aerial imagery, survey plans and third-party artwork may have separate terms. Keep source provenance with the map instead of relying on somebody remembering it later.

OpenStreetMap Foundation