Skip to content

Milestones

List view

  • Layer control, master toggle, GeoJSON export. Cross-cutting map features and the final GeoJSON export.

    No due date
    0/3 issues closed
  • Rule definitions and attaching them to entities. Rules are defined independently and then attached to any entity. When a festival-goer draws their camp on the public map, the rule engine checks their geometry against all entities that carry rules and applies the configured severity response (style override and/or tooltip message).

    No due date
    0/4 issues closed
  • Point-of-interest markers with icon picker. Points of interest are single-point markers with an icon, name, description and an optional website link. This information is shown to festival-goers when they click the marker on the public map.

    No due date
    0/3 issues closed
  • Fire roads and walking paths with Turf buffer visualisation Fire roads and walking paths are drawn as lines, not polygons. A visual buffer is shown around them on the admin map to approximate their real-world width.

    No due date
    0/4 issues closed
  • All polygon entity types (neighbourhoods, plazas, forbidden zones, etc.) Covers all entity types drawn as polygons: neighbourhoods, plazas, forbidden zones, lakes, parking areas, and any custom type the admin creates — everything except fire roads and walking paths.

    No due date
    0/4 issues closed
  • Style-type definitions CRUD — prerequisite for all entity tabs. Style definitions describe how each entity type is rendered on both the admin tool and the final public map. They must exist before any entity can be created with a meaningful type.

    No due date
    1/3 issues closed
  • Auth, layout, base map, API wiring. Prerequisites before any feature work can be tested end-to-end.

    No due date
    4/5 issues closed