Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new regions #47

Open
Flunzmas opened this issue Nov 14, 2020 · 3 comments
Open

Add new regions #47

Flunzmas opened this issue Nov 14, 2020 · 3 comments
Labels
bg: permanent Issues indicating things that can always be improved, extended etc. topic: data / assets Things related to the data the app accesses and uses.

Comments

@Flunzmas
Copy link
Collaborator

Flunzmas commented Nov 14, 2020

We are currently working on an updated description/mechanism for adding new regions to the app.

For now you can:

  1. point us to websites/organizations with fruit and vegetable availability data for the region
  2. ask for permission to reuse said data
  3. integrate the data into the database and give proper credit / or "Non-Database-fiddling Alternative"

Outdated description

From v1.5.0, adding a new region XX corresponds to adding new availability info for each food:

  1. Creating a new table foods_av_XX in the SQLite database file assets/db/foods.db, with XX being a two-letter code for the region. The easiest way to do this is by copying the table foods_av_ce with the SQL statement below:

CREATE TABLE foods_av_xx AS SELECT * FROM foods_av_ce

  1. Replace the availability data (including the column isCommon): each column holds a number per month, separated by commas. 0.0 indicates no availability, e.g. 0.5 indicates partial availability and 1.0 abundant availability in that month.
  2. Specify in the column isCommon whether the food is common or a rarity in your region.

Non-Database-fiddling Alternative

Send me a spreadsheet with the data of your region, containing the availability numbers for each food (1 number per month) and whether the food is common or a rarity in your region.

@Flunzmas Flunzmas added topic: data / assets Things related to the data the app accesses and uses. bg: permanent Issues indicating things that can always be improved, extended etc. labels Nov 14, 2020
@seasoncalendar seasoncalendar locked and limited conversation to collaborators Nov 14, 2020
@Flunzmas Flunzmas pinned this issue Nov 14, 2020
@matzebond
Copy link
Collaborator

@matzebond
Copy link
Collaborator

I have contacted both cuesa.org and eufic.org #104 and asked for permission to reuse their data.

@matzebond
Copy link
Collaborator

We did not get permission from cuesa :(

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bg: permanent Issues indicating things that can always be improved, extended etc. topic: data / assets Things related to the data the app accesses and uses.
Projects
None yet
Development

No branches or pull requests

2 participants