dataforgoodfr / dataforgoodfr/Coordonnees

Feat: Support multiple layers / geometries for same source

Open
#75 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

P1
Dominant language
Python
Stars
6
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Objective

As a coordo user, I want to be able to define 2 layers for the same data source in the config.json

Context

In MapLibre, Sources and Layers are separated components that allow a user to render the same data in multiple manners.
https://maplibre.org/maplibre-gl-js/docs/examples/add-multiple-geometries-from-one-geojson-source/

In Data4Trees, what we want to do is the following :

For Seed :
Have one layer that displays icons and when clicked the popup with indicators is displayed. This layer would hide if the zoom become big.
When the zoom becomes big, another layer is made visible : this layer shows polygons filled with color, but the same popup as in the other layer is rendered when a polygon is clicked.

All4Trees:
Have one layer that displays icons and when clicked the popup with indicators is displayed. This layer would hide if the zoom become big.
When the zoom becomes big, another layer is made visible : this layer shows circles, but the same popup as in the other layer is rendered when a polygon is clicked.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with config.json and the MapLibre multiple-geometries example linked in the issue. Trace how Seed and All4Trees sources, layers, zoom visibility, and popups are currently configured. Done means each source supports icon and geometry layers with zoom-based switching and the same indicators popup for both.

Written by the indexing model from the issue text.

Assessment

Domain
frontend, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.