Map settings

Select Map in the App tree for settings that affect the map viewport and source.

SVG source and camera

Map → Settings exposes the current SVG and the supported change/edit actions. Use Draw for shape editing. Choose a calibrated SVG such as geo-calibrated/usa.svg if the project will later use a geographic Google overlay.

Width, height, and initial camera controls determine the map component’s presentation. The App width and Canvas zoom dropdowns below the editor preview are separate preview preferences; they do not save an initial geographic zoom.

Test the initial view after a reload. A map you have panned manually during inspection is not proof that the same camera is saved as its starting view.

Interaction and visual settings

Use the Map’s available panels to control map-level interactions, zoom/panning, and styles. Region fill and borders belong to Region → Styles; marker images belong to Marker → Settings. Keeping these scopes separate prevents an App background change from being mistaken for region coloring.

Map’s fixed internal components remain under Map. Move Map itself through Layout when you want it in a different container.

Google Maps and clustering

Google Maps and Clustering settings appear in the Map inspector when available. Clustering requires its module and a marker-producing Objects source. It groups markers at a given view; it does not turn Region records into markers.

Google Maps requires a configured API key. Enabling it for a calibrated USA source creates an overlay relationship; use a partially transparent region fill when you want the base map to remain visible. See USA over Google Maps.

Pagination

Where a Map pagination control is offered, it shows navigation for the relevant data binding. Query/Page item count and pagination visibility are separate settings. See Queries and bindings.

Before publishing, test map controls in Arrow mode and on an actual WordPress page.