- What is wm/map-point used for in Laravel?
- wm/map-point is a Laravel Nova 4 field for editing and displaying geographic Point values stored in PostgreSQL/PostGIS geometry or geography columns. It is aimed at admin forms, detail views, and index views where an editor needs to set a marker's latitude and longitude. It is not a full GIS toolkit; migrations, read-side casting, and spatial queries remain your responsibility.
- Does wm/map-point work with MySQL, MariaDB, or SQLite?
- No. The package is built around PostgreSQL with the PostGIS extension and a geometry or geography column typed as Point, so it is inert on MySQL, MariaDB, or SQLite. If your Laravel application does not run PostGIS, this package is not a fit.
- How do I install wm/map-point in a Laravel Nova project?
- Install it with Composer using composer require wm/map-point, then add the field to a Nova resource. The package is described as auto-discovered, so no service provider wiring is required. You still need a PostGIS-backed Point column and a Nova 4 installation before the field can be used.
- Which Laravel and Nova versions does wm/map-point support?
- The provided evaluation lists PHP 8.0+, Laravel 9/10, and Nova 4 as the effective requirements. No Nova 5 path or formal support matrix is stated, so check composer.json and pin Nova to a tested minor. Treat a Nova major upgrade as a migration project rather than a routine update.
- Do I need PostGIS to use wm/map-point?
- Yes. You need PostgreSQL with the PostGIS extension enabled and a geometry or geography column typed as Point. Laravel's schema builder has no first-class geometry type, so the column usually has to be created with raw SQL such as ST_SetSRID(ST_MakePoint(lng, lat), 4326).
- How do I create the Point column required by wm/map-point?
- Create it with raw SQL in a migration, for example ST_SetSRID(ST_MakePoint(lng, lat), 4326), and add a GiST index on the new column. The evaluation recommends keeping existing latitude/longitude numeric columns and dual-writing until the field is validated. Backfill existing rows with a single UPDATE rather than replacing legacy columns immediately.
- Is wm/map-point a value object, Eloquent cast, or Nova field?
- The marketing overview calls it a lightweight latitude/longitude value object, but the technical evaluation identifies it as a Laravel Nova 4 field package. It lives in the presentation/admin layer and handles form, detail, and index rendering for PostGIS Point values. No Eloquent cast or application-domain value object is documented, so do not assume those capabilities.
- Can I use wm/map-point outside Laravel Nova or for proximity queries?
- No. The package is a Nova 4 field and has no relevance if your application does not use Nova. The technical evaluation says it handles admin rendering and persistence only; no model accessor or proximity query API is documented. You will need to implement read-side casting and spatial queries yourself.
- What SRID and longitude/latitude order does wm/map-point assume?
- The supplied material does not document the field's read/write SRID or axis-order assumptions, which is a known silent-corruption risk. The integration example uses SRID 4326 with ST_MakePoint(lng, lat), meaning longitude first and latitude second. Test a save-and-read round trip and confirm behavior for null or invalid geometry before relying on it.
- Is wm/map-point actively maintained and production-ready?
- The evaluation flags provenance as the dominant risk: zero stars, zero dependents, no community validation, no third-party security review, and a bus factor of one. It appears to be an internal utility published by a GIS-focused agency, with no stated test coverage or CI pipeline. Treat adoption as a timeboxed, stack-gated pilot and pin your Nova and Laravel versions.