Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Filament Locationpickr Field

Filament Locationpickr Field Laravel Package

lara-zeus/filament-locationpickr-field

A Filament form field that lets users pick a location on an interactive map. Search for an address, drop a pin, and save latitude and longitude coordinates straight to your model—simple, lightweight map integration for Laravel admin panels.

View on GitHub
Deep Wiki
Context7

Location picker field for Filament Php using Google Maps

Frequently asked questions about Filament Locationpickr Field
What is lara-zeus/filament-locationpickr-field?
It is a Filament form field for Laravel admin panels that renders an interactive map, lets users search for an address or drop a pin, and returns latitude and longitude for the host model to save. It is a presentation-layer widget with no domain logic, schema, queues, or scheduled work. Think of it as a thin adapter between Filament and a map provider.
How do I install the location picker field in Laravel?
Require the package with Composer using lara-zeus/filament-locationpickr-field, then add the field to a Filament form schema and optionally publish config or views if the package exposes them. You will also need nullable latitude and longitude columns on the model. Check the repository for the exact namespace and registration steps because the provided README excerpt does not include them.
Which Laravel and Filament versions does this package support?
The available context points to Filament 5 support, but the exact PHP, Laravel, and Filament constraints should be read from composer.json. Do not assume Laravel or Filament versions from the README alone. Verify the Composer floors before adding it to an existing application.
Does this package require a Google Maps API key?
The package description says it uses Google Maps, so expect a Google Maps JavaScript API key and likely Places API for address search. The technical review notes that the documentation also references Leaflet, so confirm from the code which provider is actually initialized before provisioning credentials. If Google is used, restrict the browser key by HTTP referrer and API, and set quotas.
How do I save latitude and longitude to my model with this field?
The field is designed to hand back a latitude and longitude pair, so add nullable decimal(10,7) columns or equivalent and cast them appropriately on the model. Persist only coordinates unless you have reviewed Google's caching and storage terms for place IDs, formatted addresses, or place names. Then assign the field value in the Filament form schema and validate the coordinate range.
Is this package free, or will Google Maps cost money?
The package itself is likely MIT-licensed and free to install, but Google Maps JavaScript loads and Places requests are metered. A small admin team may see negligible usage, while a large operations team doing frequent lookups creates a recurring bill. Set quota caps and budget alerts before rollout.
Can I use Leaflet or OpenStreetMap instead of Google Maps?
The description calls it a Google Maps field while also referencing Leaflet, and LocationPickr is historically Leaflet-oriented, so provider ambiguity is real. Read the package source to see whether it initializes Google Maps, Leaflet with open tiles, or a hybrid using Google Places for search. Do not assume the provider is configurable until the code or docs confirm it.
Is this Filament location picker production-ready and actively maintained?
Public adoption signals are very low: one star, zero dependents, a single maintainer, and no documented production users. For a small form field that may be acceptable, but record that you would be an early meaningful adopter. Pin the version and review the code, because there is no SLA and upstream Filament or Google changes may require the maintainer to catch up.
How should I test the location picker in a Laravel application?
Feature tests can submit form data with latitude and longitude and assert that the model persists the expected values, avoiding the map UI entirely. Browser-level tests should mock or block external map and Places calls so CI does not depend on a live key or quota. Also test behavior when the API key is missing, quota is exhausted, or the map script fails, because the package does not document a fallback contract.
What are alternatives to this Filament location picker field?
Alternatives include building a small custom Filament field around Leaflet, Mapbox, or Google Maps, using another Filament map-picker package, or starting with plain latitude and longitude inputs plus a map preview. Choose based on which map provider you can legally and financially support, not just the field UI. For a low-volume admin panel, simple coordinate inputs may be enough.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
robertmarney/lara-hierarchial-collections
simonschaufi/rule-doc-generator
emissaoja/emissaoja
blackbricksoftware/gravityforms-civicrm-form-processor
al-rahabi/fancy-crud
jinas/dhivatar-component
mltstephane/laravel-quality
bernskiold/laravel-talentlms
bernskioldmedia/laravel-form-architect
youbar/easy-crud
c-point-labs/laravel-hostyourai
dbravoan/dbcms-admin-theme-dbcms
dbravoan/dbcms-theme-db-cyber
dbravoan/dbcms-blocks-basic
dbravoan/dbcms-module-content-audit
dbravoan/dbcms-module-ai-assistant
paygate-to/paygate-php
padosoft/askmydocs-connector-base
defstudio/supercharged-carbon
bernskioldmedia/laravel-matomo