Download the PHP package afsakar/filament-leaflet-map-picker without Composer

FilamentPHP LeafletJS Map Picker

A Filament Forms component that provides an interactive Leaflet map for selecting and storing geographical coordinates.

Features

• Interactive map for location selection
• Canonical { lat, lng } state with legacy [lat, lng] and JSON string input support
• Adjustable zoom level and map height
• Draggable and clickable markers
• "My Location" button for quick navigation to the user's current position
• Search modal backed by an explicit-submit geocoder request
• OpenStreetMap and Esri tile presets plus custom HTTPS tile layers
• Custom marker configuration
• Read-only display mode and Infolist entry support

Compatibility

Filament 3 support is intentionally not part of the v3.0.0 package line. If you are staying on Filament 3, keep using the v2 releases.

Installation

Install the PHP package in your Filament app:

The package auto-discovers its service provider. Filament assets are registered with FilamentAsset and loaded on demand through the component views' x-load, x-load-src, and x-load-css attributes, so you do not need to copy the compiled JS/CSS into your app for normal usage.

If you want Leaflet's image assets published locally, you can still publish them:

You can publish translations with:

Optionally, you can publish the views with:

Database and model setup

Store the coordinates in a json or text column:

Cast the attribute to array in your model:

Canonical state format and migration notes

The canonical saved state for v3 is:

The package still reads these legacy inputs while you migrate existing data:

• legacy arrays like [41.0082, 28.9784]
• JSON strings like "{\"lat\":41.0082,\"lng\":28.9784}"

New writes should use the canonical object shape. If you already cast the column to array, Laravel will persist the object-shaped array cleanly in a json column.

Usage

Form

To show editable latitude and longitude inputs inside the picker, enable them on the picker and do not add separate sibling inputs for the same location state path:

When enabled, the selected-location summary is hidden. The default is false, which keeps the summary visible.

The simplest canonical default location example is:

State synchronization behavior

• Clicking the map writes { lat, lng } into the field state.
• Dragging the marker writes { lat, lng } into the field state.
• Search result selection writes { lat, lng } into the field state.
• Geolocation writes { lat, lng } into the field state.
• When showCoordinateInputs() is enabled, editing either coordinate updates the map and the canonical field state after the input changes.
• If the Livewire/Alpine state is changed manually to a valid coordinate object, legacy array, or supported JSON string, the marker and map recenter to match it.

Table column

The column renders a compact thumbnail: it marks the location with a small dot instead of a pin and hides the attribution control, which would otherwise cover most of the tile. The default height is 50px.

The column is read-only. It accepts the canonical { lat, lng } object and legacy arrays or JSON strings. Null and invalid values use the configured default only for visual map placement; they are not shown as a selected record location and never change the row state.

Infolist

Search, tile, and geolocation policy

• Built-in tile presets are limited to openstreetmap and esri.
• OpenStreetMap tile usage must stay on HTTPS and keep the provider's attribution visible.
• The default browser geocoder endpoint is https://nominatim.openstreetmap.org/search.
• Public Nominatim usage here is explicit-submit only. The package does not support autocomplete against the public endpoint.
• Keep public Nominatim traffic to roughly 1 request per second.
• Your application is responsible for any required Referer, User-Agent, API key, custom tile contract, attribution, or provider-specific compliance.
• The browser-side package does not spoof a User-Agent, and browser control over Referer is limited by the host app and browser policy.
• If you need higher traffic, backend credentials, bulk/offline tiles, or policy-controlled geocoding, use your own backend proxy or a commercial/provider-managed geocoder instead of the public endpoint.
• Offline/bulk tile distribution is outside this package; if you need it, bring your own compliant tile infrastructure.

Development checks

Run the package checks from the repository root:

Screenshots

Default:

Custom Marker:

Custom Tile:

Changelog

Please see CHANGELOG for more information on what has changed recently.

Contributing

Please see CONTRIBUTING for details.

Security Vulnerabilities

Please review our security policy on how to report security vulnerabilities.

Credits

• Azad Furkan ŞAKAR
• All Contributors

License

The MIT License (MIT). Please see License File for more information.