search

kartoza / least-cost-electrification-somalia

Global Electrification Platform for Global
1 stars 0 forks source link

[EPIC] Add csv export feature #35

Open AndreasSahlberg opened 3 years ago

AndreasSahlberg commented 3 years ago

Add the possibility to export the list of sites that have been filtered in a tabular format (e.g. csv), so that the user doesn’t have to zoom in and out of the entire country to find the locations manually.

meomancer commented 3 years ago

There are 2 ways:

  1. Just provide the static csv and we can just read the csv and make filters based on it (it will take 2-4 hours)
  2. Create uploader, put the sites to database and make filters based on it (about >4 hours, because i haven't learned the database system)

Is it ok for way #1? so just give the csv everytime csv is updated, and update the server.

meomancer commented 3 years ago

could you provide the csv @AndreasSahlberg ?

AndreasSahlberg commented 3 years ago

It should use the csv-files from the results that are ingested to the platform if possible: https://drive.google.com/drive/u/0/folders/15quQoRmSAf46Duo_DUEevRO6KXffChW3

AndreasSahlberg commented 3 years ago

image

AndreasSahlberg commented 3 years ago

What we would like, if possible, is that when the user has applied a filter on the visualization platform (see the right part of the picture above), he/she could download a csv file with the results only for the clusters that are displayed after filtering. This csv should include either the data that is attached to the clusters after they have been ingested (including x- and y-coordinates at the very least) or the full data that was provided for those clusters in the result file for those clusters before ingestion.

As mentioned, this is an enhancement that would be very useful if possible, but other issues are prioritized.

meomancer commented 3 years ago

ah, i understand now @AndreasSahlberg

This is going to be complex and hard to be implemented for my current knowledge of gep for now @AndreasSahlberg as per we don't have worker architecture for the gep that can execute a process in background so, if the data is big, user needs to wait csv to be constructed, but if it is too long the request can be Request Time Out (if we don't process it in background)

This ticket will take a lot of time for my current knowledge

AndreasSahlberg commented 3 years ago

Ok, if it's not possible to do this one now the focus should be on the other tickets instead.