Baxtersweb Maps

Baxtersweb Maps helps WordPress developers and site builders display route maps from structured ACF Pro field data.

Instead of creating a separate map and embedding it manually, you add map markers directly to posts, pages, or custom post types. Baxtersweb Maps then displays those points as an interactive OpenStreetMap route map using Leaflet.

Baxtersweb Maps is useful for:

• Travel itineraries
• Safari routes
• Hiking trails
• Cycling routes
• Road trips
• Delivery routes
• Multi-location guides
• Festival or venue maps

Baxtersweb Maps uses OpenStreetMap and Leaflet. A free openrouteservice API key is optional and is used only for calculating road-following routes. Without a key, route markers are joined with a dashed straight line.

Features

• Interactive route maps
• ACF Pro repeater support for ordered map markers
• ACF OpenStreetMap Field support for visual location picking
• Route lines between ordered points
• Optional points of interest that do not affect the route line
• Built-in Dashicon, theme-class, or plain POI markers
• Individual POI background colours
• Nearby POI grouping with click-to-spread behaviour
• Alphabetical or numbered route markers
• Duplicate map marker handling
• Custom route colour, marker colour, marker text colour, POI colour, map height, border radius, and marker numbering settings
• Works with posts, pages, and custom post types
• One-click ACF field setup
• Leaflet bundled locally with the plugin

Requirements

Baxtersweb Maps currently requires:

• Advanced Custom Fields Pro
• ACF OpenStreetMap Field

The ACF OpenStreetMap field should use Return Format: Raw data and should allow one marker per row.

Demo

Check out the Baxtersweb Maps demo page to see example route maps, points of interest, and styling options.

Documentation

Read the Baxtersweb Maps documentation for setup instructions, shortcode usage, and developer examples.

External Services

Baxtersweb Maps uses external services for map tiles and optional road-route calculation.

• OpenStreetMap Standard tiles are loaded in the visitor’s browser from the OpenStreetMap Foundation tile service whenever a map is displayed. The visitor’s IP address, browser details, referring page, and requested tile coordinates may be sent to OpenStreetMap. Tile usage policy: https://operations.osmfoundation.org/policies/tiles/ Terms of Use: https://osmfoundation.org/wiki/Terms_of_Use Privacy policy: https://osmfoundation.org/wiki/Privacy_Policy

• openrouteservice is used only when the site administrator has supplied a valid API key and road geometry needs to be calculated or recalculated. This may occur after route points are saved or changed, after an API key is successfully verified, or when an unrouted map is first rendered. The route coordinates are sent from the WordPress server to https://api.openrouteservice.org/ solely to calculate a road-following route. Returned route geometry is stored in WordPress and reused, so normal visitor views of an already calculated route do not make routing requests. Service and API information: https://openrouteservice.org/ Terms of Service: https://openrouteservice.org/terms-of-service/ Privacy policy: https://openrouteservice.org/privacy-policy/

• Leaflet JavaScript and CSS, WordPress Dashicons, and all Baxtersweb Maps plugin code are loaded locally. No icon CDN is used.

Baxtersweb Maps does not send WordPress user account data to these services.

Source Code

The plugin source code is included in this plugin package. The JavaScript and CSS files in assets/js and assets/css are human-readable source files and are not generated from a separate build step. No npm, webpack, or other build tooling is required to regenerate the shipped assets.