dataforgoodfr / dataforgoodfr/12_bloom

[FEATURE] Interaction avec zone

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

Nobody has claimed this yet.

P3
Dominant language
Python
Stars
30
Forks
10
Avg merge
1m
Merged PRs (30d)
9

Description

Sur la carte, on veut pouvoir interagir avec les zones via un clic (contexte à définir).
On peut donc déjà créer ou compléter une route qui sert les données :

/zones/{zone_id}/details par exemple => Return the list of vessels that either visited the zone or fished in the zone with the activity duration
(parameters : start_at, end_at, type = VISIT | FISHING)
{
   id: Union[int, None] = None
   category: str
   sub_category: Union[str, None] = None
   name: str
   json_data: Union[dict, None] = None
   reglementation_start_at: datetime (date de début de mise en place de la zone)
   reglementation_end_at: datetime (date de  fin de mise en place de la zone)
   activities : 
        [
            {
              vessel : {
                  id: Union[int, None] = None
                  mmsi: Union[int, None]
                  ship_name: str
                  country_iso3: str
                  type: str
                  imo: Union[int, None]
                  ircs: Union[str, None]
                  length: Union[float, None] = None
                  
              }
             duration: Optional[timedelta]
            }
        ]
}

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 by locating the existing zone routes and the entry point for vessel activity data, then compare their models with the proposed /zones/{zone_id}/details response. Clarify the click interaction, VISIT/FISHING behavior, date filters, and duration definition before implementing; done means the agreed endpoint returns the specified zone, vessel, and activity fields.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.