dataforgoodfr / dataforgoodfr/14_Data4Trees

Chore: Improve default layers of config.json

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

Nobody has claimed this yet.

D4T_Backend P3
Dominant language
TypeScript
Stars
9
Forks
0
Avg merge
10d 11h
Merged PRs (30d)
4

Description

Currently we use basic layers with merkator projection :

  {"layers": [
    {
      "id": "satellite",
      "type": "xyzservices",
      "provider": "Esri.WorldImagery"
    },
    {
      "id": "villages",
      "type": "openmaptiles",
      "layer": "place",
      "filters": {
        "class": "village"
      }
    },
    {
      "id": "towns",
      "type": "openmaptiles",
      "layer": "place",
      "filters": {
        "class": "town"
      }
    },
    {
      "id": "boundaries",
      "type": "openmaptiles",
      "layer": "boundary",
      "filters": {
        "admin_level": 2
      },
      "style": {
        "paint": {
          "line-color": "hsl(248,7%,66%)"
        }
      }
    }]}

The idea of this PR is to use a non-merkator projection rto represent Africa with its real size. Also the goal would be to show a more detailed map with road and big cities, as it seems now only villages / regions are shown.

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 trace how the default layers and projection are loaded. Review the current layer definitions for the satellite, place, and boundary entries, then determine which supported non-Mercator projection and map sources can provide roads and major cities. Done means Africa is displayed with a non-Mercator projection and the default map includes the requested detail.

Written by the indexing model from the issue text.

Assessment

Domain
data-visualization, frontend
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.