Map view

A map view places each record on a map at its location. Use it when the work is geographic: customer sites, deliveries, assets in the field, service areas.

What a map needs#

A map view needs a Location column on the table. That column stores a latitude and longitude for each record, and can also store a label and an address. Records without a location don't appear on the map.

A map view also has:

• An optional title field that labels each pin. Without one, the pin shows the location itself.
• Clustering, on by default, which groups nearby pins into one marker when you zoom out.
• A default center and zoom, so the map opens on the area your team works in.

Work with the map#

• Pan and zoom to the area you need. The map loads the records inside the visible area, up to 2,000 at a time, so zoom in to see every pin in a busy area.
• Open a record. Click a pin to open its record page.
• Search and filter work the same way as in other views. The count in the corner shows how many points are on the map.

Filter by distance#

A Location column supports location filters, in any view and in access filters:

• is within radius of a point, given as a latitude, a longitude, and a radius in meters. For example, within 25,000 meters of the depot. is not within radius does the opposite.
• is within bounds, a rectangle such as the area around a city.

Use these in an access filter when a role should only see records near them, for example a regional team that only sees sites in its region.

When to use something else#

A map view shows where records are. If a process needs to decide based on distance, such as finding the nearest technician or checking whether a stop is inside the service area, use the location steps in a workflow.