Add area indicators and country code

[vgeorge]

Contributes to: #65, #43, #20

Changes:

• Reverted the upgrade of npm-run-path from v5.3.0 to v6.0.0 introduced in chore: Migrate to MapboxGL #62, as it was breaking the ingest script
• Pinned Prisma to v5.20.0.
• Added a new meta JSON property to the Area model to store indicators, country codes, and other metadata
• Updated the seed script to populate the meta property
• Connected the indicator data to the area panel
• Added country codes to the area label on the area panel

How to Test:

• Set up the local server to use the database global-food-twin-dev-db
• Navigate to an area page; indicators should be displayed correctly in the side panel

Known Issues:

• I performed a new ingestion with a reduced number of flows to speed up the process, but unfortunately, most areas don’t have flow data. Here are some example areas that do:

  • http://localhost:3000/area/DEU.10_1
  • http://localhost:3000/area/CRI.3_1
  • http://localhost:3000/area/CHN.19_1

• The country codes use 3-letter abbreviations because this is the only format available in the provided data

Screen capture

@oliverroick this is ready for review.

cc @wrynearson @faustoperez

[oliverroick]

This looks good for the most part.

I noticed, the total population number is a bit odd, with the .0288 humans. For can round the number, if feels like this should be done at data ingest.

[vgeorge]

@oliverroick I made some updates following your feedback, this is ready for another review.

The indicators section should look like this:

The changes introduced are:

• Styles: indicator label is fixed at the top of the row and the indicator value is aligned vertically
• Formatting: I borrowed a number formatting function we used in GEP to help us handle rounding and the diffence in scale of the indicators of an area. We are deviating a little from the designs but with this approach we can handle better indicators that can be counted in thousand, millions or billions
• Types: I added a interface in the seed script for the area indicator to enhance type declarations and make it consistent with the component. It doesn't look like the ideal place to put it, we can move it elsewhere later

cc @faustoperez @wrynearson

[oliverroick]

These changes are looking good!