Goal

Choose where your map opens — its center point and how zoomed in it starts — the moment a map view first appears in your app. This matters because the map can’t always read the device’s real GPS location: location permission may be denied, a GeoIP lookup (estimating location from the visitor’s IP address) may fail, or the very first frame may render before any location comes back. When that happens, the app falls back to a default region you define. This article walks you through setting that fallback center and its starting zoom level.

A note on “bounds.” MAM Suite doesn’t currently offer a configurable bounding box (a south-west / north-east rectangle that would constrain panning), so that’s not something we cover here. What you can set today is the default center point and default zoom, which together decide the region the map opens to. If you need a hard pan/zoom boundary, treat that as a feature request rather than a setting you can flip. See Limitations below.

Before you start

• You should be comfortable in Mobile App Manager → App Setup and the app settings screen.
• Have the latitude and longitude of the point you want the map to center on. You can get these from any maps service (right-click a location in most desktop map apps to copy its coordinates).
• This is a global setting: it applies to every map in the app, not just one map button. If you have several map screens, they all share this same default region.

The settings you’ll use

You’ll find all four on the app settings screen, split across two sections. Because they’re global settings (environment all), one value applies across the whole app.

The first three live in the GeoFilters section of the settings screen. That section — and those three settings — is added by the mam-geofilters plugin, so it needs to be active before they’ll show up. “Initial Map Zoom” lives in the Misc section instead, and ships as part of mam-main.

How the fallback actually works

It helps to know the order the app and server work through on the way to deciding where the map opens — your default only kicks in at the very end of that chain:

1. Real device location. If the app has a usable device location, it uses that. The map centers on the user.
2. GeoIP estimate. If no device location comes through, the server takes a guess by estimating a location from the request’s IP address. When that guess succeeds, it uses the estimated latitude/longitude/city.
3. Your default region. If neither of the above produces a location, the server falls back to GeoFilter Default Latitude and GeoFilter Default Longitude (and the city name) you set here.

So the default region really is just a fallback. Someone standing in your target area will almost always see their own location, not yours. Your default matters most for three kinds of visitors: those with location turned off, those far outside your service area, and everyone during the brief moment before a location resolves.

Zoom is applied independently. “Initial Map Zoom” controls how tightly the map is zoomed the moment it appears, no matter which of the three center points above ends up being used. The documented default is 14 (roughly neighborhood / town level) — lower numbers zoom out (city, region, country), higher numbers zoom in (streets, individual blocks).

Steps

1. Choose your center point

Start by picking the spot the map should open to when nothing better is known — usually the heart of your service area: a downtown, a venue, the middle of a city, or the centroid of whatever region you cover.

Get its coordinates as decimal degrees. For example:

• Latitude 40.7128
• Longitude -74.0060

One thing to watch: longitude is negative for locations west of the prime meridian (that’s most of the Americas), and latitude is negative south of the equator. Drop that minus sign by mistake and your map lands on the wrong side of the planet.

2. Enter the default latitude and longitude

1. Go to Mobile App Manager → App Setup and open the app settings screen.
2. Find GeoFilter Default Latitude and enter your latitude (e.g. 40.7128).
3. Find GeoFilter Default Longitude and enter your longitude (e.g. -74.0060).
4. Enter the coordinates as plain decimal numbers — no degree symbols, no N/S/E/W letters.

3. Set the default city name

Set GeoFilter Default City Name to a readable label for that point (e.g. New York). This label shows up alongside the default location in geofilter-style UI — it won’t move the map on its own, but it keeps the displayed place name consistent with the coordinates you entered.

4. Set the starting zoom

1. Find Initial Map Zoom (Default is 14).
2. Leave it blank (or set 14) to keep the standard neighborhood-level view.
3. To open more zoomed out — showing a whole metro area or region — lower the number (try 11–12).
4. To open more zoomed in — focused on a single block or address — raise the number (try 15–17).

Zoom is really something you tune by feel — change it, save, reload the map in the app, and keep adjusting until the opening view frames your area just the way you want.

5. Save and verify

1. Save the app settings.
2. Open the app (or rebuild/refresh the app content so the new settings are picked up).
3. Open a map screen with device location turned off, so you can watch the fallback do its job. The map should open centered on the coordinates you entered, at the zoom you set.
4. Then turn location back on and confirm the map recenters on the device — that’s expected, and it confirms the fallback is behaving like a fallback, not a hard override.

Tips

• Pick a center that reads well at your chosen zoom. A coordinate that’s technically inside your area but visually off-center can still make the opening view feel wrong. If the framing is off, adjust the coordinate itself, not just the zoom.
• One default for the whole app. Since these are global settings, every map in the app uses the same fallback region. If your map screens really need different defaults, the current settings can’t do that — worth noting for your team.
• Coordinates are stored as text. Stick to clean decimal values. Stray spaces, commas used as decimal separators, or formatting carried over from a paste can all keep the value from parsing.

Limitations

• No configurable bounding box. There’s no admin setting today that locks the map to a south-west / north-east rectangle or caps how far users can pan or zoom out. If you need a hard boundary, raise it as a feature request.
• Default region is a fallback, not a lock. It won’t stop the map from centering on a real device or GeoIP location — it only fills in when no location is available at all.
• Map rendering is the mobile client’s job. The server supplies the center, zoom, and markers; the native map view (Apple Maps / Google Maps, depending on platform and configuration) does the actual drawing. A few related map options — marker clustering, for instance — live behind separate toggles in the miscellaneous settings.

Related settings and articles

• Turn Off Map Clustering? (tsl-map_turn_off_google_map_clustering) — controls whether nearby markers are grouped on the map.
• Content class: Map — how map markers are sourced and what the marker JSON looks like.
• Geofilter configuration — how the default city, latitude, and longitude tie into the geofilter “near me” experience.

Verification

Grounded against:

• mam-geofilters/includes/admin-settings.php — setting definitions for geofilter_default_lat, geofilter_default_lon, geofilter_default_name (category geofilters, which registers the “GeoFilters” settings section).
• mam-main/includes/app-settings/admin-settings-page.php — setting definition for default_map_zoom (category misc).
• mam-main/includes/app-connect/main-json-manager.php — device location → GeoIP → geofilter_default_lat/_lon fallback chain.
• mam-main/includes/content-classes/local-app-map-class.php — the Map content class (no per-button region settings).
• mam-main/user_docs/03d-content-class-map.md — existing Map reference (global default coords, strings, client-side rendering).