grid approach for ch.bfe.solarenergie-eignung-daecher tooltips

[ltclm]

With the introduction of the new grid layer type we could change the ch.bfe.solarenergie-eignung-daecher tooltips now. The raster part of the tooltip information could be accessed from s3.

This would mean that we can replace the tables:

• bfe.solarenergie_raster
• bfe.solarenergie_raster_files_sisdir
• bfe.solarenergie_raster_files_sis
• bfe.solarenergie_raster_values_sisdir
• bfe.solarenergie_raster_values_sis with static json files in s3.

The total size of these tables is 1GB now but.

• Actually these tables contain 10 years of monthly data for 1/3 of the final perimeter
• they are updated each month and will constantly increase.
• Since the tooltip only needs the last 12 months we could change the automatic data integration and keep only the last 12 months in these tables, so the total size would be around 100MB and the size would be stable then..

Do you think this is worth the effort to move this data from db to s3 and introduce a new hybrid tooltip solution for this layer with one part coming from database and the other part coming from s3 (grid)?

@gjn @AFoletti @loicgasser your thoughts please.

[gjn]

In general yes, but I have one question.

We keep 10 years but only need 12 months? Why?

[ltclm]

raster data in the filesystem is for the last 10 years, in the tooltip we just need 12 months. That's why we should remove this data from the database and adapt the import scripts. @AFoletti can you confirm?

[gjn]

+1 from me then.

[loicgasser]

+1, but does it mean we have to update grid cells automatically on S3 when new raster arrive? I didn't get if those layers were shipped automatically sorry. And what would still some from the DB? (Expect the metadata of course)