rm-hull / maps / 22325277816

24%

push

github

feat: add street-level crime map layer (#1048)

* feat: add street-level crime map layer

Introduces a new overlay layer that fetches and displays street-level
crime data from the UK Police API (`data.police.uk`).

-   Markers are grouped by street and colored based on the highest
    severity incident at that location.
-   Includes a legend and detailed popups featuring incident tables
    showing category, outcome, and context.
-   Uses `useQuery` for efficient caching of API responses based on
    map bounding boxes.

```mermaid
sequenceDiagram
    participant M as StreetLevelCrimeLayer
    participant H as useStreetLevelCrimes
    participant S as fetchStreetLevelCrimes
    participant A as Police API

    M->>H: bounds
    H->>S: bounds, category
    S->>A: GET /crimes-street (poly=...)
    A-->>S: JSON StreetLevelCrime[]
    S-->>H: data
    H-->>M: incidents
    M->>M: group by street & render markers
```

* feat: add month selection to crime map layer

Introduces a month selector in the map legend to filter crime data
by date. This change updates the data fetching hook and API service
to handle the `date` parameter.

Additionally, the crime incident popups now use specialized **Table**
and **List** views depending on the incident count to improve
information density and readability.

```mermaid
sequenceDiagram
    participant U as User
    participant L as Legend (Select)
    participant S as StreetLevelCrimeLayer
    participant H as useStreetLevelCrimes
    participant A as API Service

    U->>L: Select Month
    L->>S: onMonthChange(month)
    S->>H: Update query with new month
    H->>A: fetchStreetLevelCrimes(month, bounds)
    A-->>H: Return crime data
    H-->>S: Update data
    S-->>U: Render updated markers
```

* Update src/config/layer.tsx

Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

* perf: optimize map bounds caching and UI cleanup

* Stabilize query keys by rounding map c... (continued)

462 of 1146 branches covered (40.31%)

Branch coverage included in aggregate %.

0 of 40 new or added lines in 3 files covered. (0.0%)

445 of 1237 relevant lines covered (35.97%)

4.17 hits per line