Weave Code
Filament Map Picker Laravel Package
humaidem/filament-map-picker
Filament Map Picker provides an interactive map form field for Laravel Filament apps. Users can search, drop a pin, and save latitude/longitude coordinates, making location selection simple in resources and forms.
Filament Map Picker adds an interactive map field to Filament forms for selecting geographic coordinates. Click or drag a marker to choose a location, then save the resulting latitude and longitude directly through your form schema.
It integrates cleanly with Filament’s form builder, making it useful for address, store, event, or delivery-location inputs.
- Interactive marker selection by click or drag
- Stores latitude and longitude values
- Configurable default center and zoom
- Seamless Filament form integration
Frequently asked questions about Filament Map Picker
- How do I install humaidem/filament-map-picker in a Laravel Filament panel?
- Install it with Composer using composer require humaidem/filament-map-picker, then register the plugin or field with your Filament panel provider and add the field class to a form schema. Setup is a single Composer dependency plus panel registration, with no migrations, models, or background processes. Check the README for the exact namespace and registration syntax for your Filament version.
- Does humaidem/filament-map-picker support Filament v4?
- As of its last release in November 2023, humaidem/filament-map-picker targets the Filament v3 line. A Filament v4 panel is therefore a likely incompatibility and should be spiked before you commit. Test the field class against your exact Filament major version early, because this can eliminate the package as an option.
- What value does the Filament map picker save to my model?
- The field is a UI layer that lets an editor pick a location and returns a coordinate value for persistence, but the README and evaluation flag the exact save contract as something to verify. Inspect the field class to confirm whether it emits one serialized string such as lat,lng, an array, or separate attributes. Design your database column around that answer before building the form.
- Can I store latitude and longitude in separate database columns with Filament Map Picker?
- It may be possible, but do not assume it. If the field emits a single lat,lng string, store that string or split it with an accessor and cast; if it emits two attributes, bind two fields. Read the package source and test the saved payload in a Filament form before choosing separate latitude and longitude columns.
- How do I change the map tile provider in humaidem/filament-map-picker?
- The picker is Leaflet-based, so tiles come from a Leaflet tile layer URL, but you must confirm whether humaidem/filament-map-picker exposes that URL as configuration or hard-codes a public endpoint. Free public tile services such as OpenStreetMap have usage policies and rate limits, so production panels should use a self-hosted, MapTiler, or Mapbox endpoint with an owned key. If the package does not expose the tile URL, a small fork may be the cleanest fix.
- Does the package validate coordinates server-side?
- The package is a form-field UI component and the evaluation found no server-side coordinate validation, so treat submitted values as untrusted. Add Laravel validation rules for required or nullable state and latitude/longitude bounds, for example between -90 and 90 and -180 and 180. Validate on the server even if the map UI restricts the picker.
- Is humaidem/filament-map-picker maintained and safe for production?
- The project has modest signals: about 59 stars, zero dependents, a single maintainer, and a last release in November 2023, so it is effectively dormant rather than a de facto standard. The code surface is small, which limits blast radius, but there is no vendor SLA or demonstrated Filament v4 path. For production, consider pinning the version, reviewing the source, and being prepared to fork or vendor it.
- What are alternatives to a Filament map picker field?
- Because the package is a small Leaflet-based Filament field, credible alternatives are to build a custom Filament Field with Leaflet yourself, use another maintained Filament map package, or keep plain latitude and longitude inputs with a separate geocoder. If the package is only a few hundred lines, forking it may be cheaper than depending on an unmaintained utility. Evaluate alternatives against your Filament version and coordinate storage convention.
- Does the map picker support place search and geocoding?
- The package blurb advertises place search, but geocoding usually depends on an external geocoder and may have usage limits or costs. Confirm which search endpoint the field calls, whether it is configurable, and whether search is required for your workflow. If pin-drop is sufficient, you may avoid a paid geocoder and a different build.
- What are the GDPR, CSP, and offline concerns with this Filament Leaflet map field?
- The map loads Leaflet assets and tile images in the browser, and public tile endpoints can create GDPR or data-protection questions plus CSP and air-gapped network issues. If your panel has a strict Content Security Policy or runs offline, verify asset loading and use self-hosted tiles where possible. Review the tile provider policy and your legal and security requirements before production use.
Weaver
How can I help you explore Laravel packages today?