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
Form Spatial

Form Spatial Laravel Package

looptribe/form-spatial

Laravel package that adds spatial form fields to Looptribe Form, making it easy to capture and edit geographic data such as points, coordinates, and geometries in your forms. Includes field rendering, validation, and model integration for geospatial inputs.

View on GitHub
Deep Wiki
Context7

FormSpatialBundle - Spatial support for Symfony2 forms

Frequently asked questions about Form Spatial
Is looptribe/form-spatial a Laravel package?
No. It is a Symfony2 bundle built around Symfony's Form component and typically Doctrine spatial types, not Laravel, Eloquent, Blade, or Backpack. Despite any Laravel-oriented description, it is not natively compatible with a Laravel application. Treat it as a design reference rather than a Composer dependency.
Can I install looptribe/form-spatial in a Laravel application?
Not realistically. Modern Laravel runs PHP 8.2-8.4, while a Symfony2-era bundle almost certainly constrains PHP and Symfony component versions, so Composer resolution will likely conflict. Even if forced, it would require pulling Symfony Form into Laravel as a parallel form and validation stack. There is no drop-in install path.
What Laravel and PHP versions does looptribe/form-spatial support?
It does not publish Laravel version support because it is not a Laravel package. As a Symfony2-era bundle last released in 2018, it almost certainly targets PHP 5.6/7.x and Symfony 2.x/3.x, far below current Laravel runtimes. Do not expect compatibility with PHP 8.2-8.4 or current Laravel releases.
Does looptribe/form-spatial support points, lines, and polygons?
Conceptually yes; the spatial form field idea covers POINT, LINESTRING, and POLYGON geometry types, not just a single marker. In this package those types are tied to Symfony Form and Doctrine spatial abstractions, not Eloquent. For Laravel you would need to rebuild the field with a map widget, a GeoJSON or WKT hidden input, and an Eloquent cast.
How do I save spatial data to MySQL POINT, LINESTRING, or POLYGON columns with Laravel?
Use native MySQL spatial columns and handle serialization explicitly in Laravel. A practical pattern is a map component such as Leaflet or MapLibre that writes GeoJSON or WKT into a hidden input, a FormRequest rule that validates the geometry, and an Eloquent cast or mutator that converts to and from the database spatial value. This package's Symfony and Doctrine integration does not provide that Laravel persistence layer.
What are the alternatives for map-based geometry fields in Laravel?
Build a small native field using Leaflet or MapLibre for the map, Alpine.js or Livewire for interactivity, a hidden GeoJSON or WKT input, FormRequest validation, and an Eloquent cast for the spatial column. If you need broader geospatial querying, evaluate maintained Laravel or PostGIS packages and custom query scopes rather than an archived Symfony bundle. The functional gap is small enough that a native build is usually shorter than porting.
Is looptribe/form-spatial maintained or safe for production?
No. The repository is archived, last released on 2018-04-19, with 7 stars and 0 dependents, so there is no maintainer, security response channel, or production evidence. Any vulnerability in its PHP glue or embedded map JavaScript becomes permanently yours. It should fail intake for production Laravel work.
What license does looptribe/form-spatial use, and can I use it in a commercial Laravel app?
It is GPL-2.0, which is strong copyleft. Linking GPL code into a proprietary Laravel SaaS creates a strong argument that the combined work must be GPL, and a fork inherits that obligation. This usually fails legal review, so avoid code reuse unless legal has explicitly approved the exposure.
How would I test a spatial form field in Laravel?
Test at three layers: the front-end map component emits valid GeoJSON or WKT, the FormRequest accepts valid geometries and rejects malformed or out-of-range coordinates, and the Eloquent cast round-trips the value to the database spatial column. Use feature tests for the CRUD endpoint and unit tests for geometry serialization. Do not rely on the Symfony bundle's test suite for Laravel behavior.
What should I check before choosing a Laravel spatial form package?
Confirm the actual need, whether it is point capture, arbitrary lines and polygons, or read-only display, along with the spatial backend such as MySQL spatial, PostGIS, or plain latitude/longitude columns. Then verify Laravel and PHP version support, maintenance status, license, and production evidence such as dependents and recent releases. For this package, the archived status, GPL-2.0 license, and Symfony2 architecture are disqualifying for Laravel adoption.
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.
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console