The obligation
Law 24/2007 requires every Romanian municipality to keep a registry of its green spaces: parks, trees and the furniture between them. Plenty of towns keep it in a spreadsheet, a stack of CAD files or a drawer. That stays a paperwork problem until a tree falls on a car. Courts have treated the city as responsible for trees in its care regardless of fault, and a current, documented registry is the best evidence that someone was looking after them.
The people who keep the registry are municipal staff with a dozen other jobs, not GIS specialists. So we kept the model small. Each tree gets one of three statuses: healthy, needs attention or danger. That is the question a city has to answer, and a resident can read it at a glance on the public map.
We also didn't want anyone to start from zero. Most towns already have plans somewhere, as DWG, DXF, shapefiles or GeoJSON, drawn in Stereo 70 because Romanian cadastral data uses it. The app imports them as they are.
Under the hood it's Laravel with a Filament back end, a stack we know well for data-heavy admin work. A city clerk shouldn't feel like they're inside a developer tool, though, so we built enough custom interface on top that it no longer looks like Filament. The app also got its own brand, designed alongside the build, so it could stand on its own in front of a mayor.
The public side needs no account. Anyone can open the map, see the parks and trees near them and report a problem, and the municipality answers in the same place, in public.
The best admin software is the kind a clerk can run on a Tuesday afternoon without calling anyone.
No lock-in
Public data shouldn't depend on a single vendor. The app runs in EU data centres or on the municipality's own servers, the same application either way, and everything exports in open formats. If a city ever wants to leave, it takes its registry with it.