[Feature request] Add invasion history maps

[SanderDevisscher]

Is your feature request related to a problem? Please describe. No, just a new feature as requested by @timadriaens

Describe the solution you'd like A stack of maps comparing the current year of invasion with the 2 prior periodes of 3 years (map current year (2024) + map current year -1 (2023) <-> current year - 4 (2020) + map current year -5 (2019) <-> current year - 9 (2016))

Describe alternatives you've considered not relevant

Additional context example for vespa, note years do not match request.

@SanderDevisscher add code example

[SanderDevisscher]

for all species with management

[mvarewyck]

Some more questions

• Static or interactive maps? Interactive can be slow and how to handle zooming?
• Region levels: choices are municipalities and provinces. If municipalities, need border for provinces?
• Same options as current maps: legend placement, show/hide globe, unit, source

I checked: Oxyura jamaicensis has no info on municipalities and provinces. https://github.com/inbo/aspbo/issues/53#issuecomment-1921085756

Current graphs and filters (already in the app):

[SanderDevisscher]

Some more questions

1. Static or interactive maps? Interactive can be slow and how to handle zooming?
2. Region levels: choices are municipalities and provinces. If municipalities, need border for provinces?
3. Same options as current maps: legend placement, show/hide globe, unit, source

1. static is ok
2. If municipalities, need border for provinces? => yes please
3. Yes

[mvarewyck]

Example output for Vespa Velutina @SanderDevisscher @timadriaens

[SanderDevisscher]

@mvarewyck can you add a region (flanders, wallonia, etc...) filter ?

[SanderDevisscher]

@timadriaens we need to think about usefull "levels"

[mvarewyck]

@mvarewyck can you add a region (flanders, wallonia, etc...) filter ?

We have a region filter now at the top of the page which applies for all graphs.

[SanderDevisscher]

Perfect

[SanderDevisscher]

@mvarewyck which sources did you use for the respective maps ?

[SanderDevisscher]

I'm thinking this might better fit under indicators or observation than management since it should display the number of observations in resp. periods 🤔

@soriadelva what do you think ?

[mvarewyck]

@mvarewyck which sources did you use for the respective maps ?

@SanderDevisscher @soriadelva I use management data.

• For Vespa velutina it is the total sum of points, nesten and beheerde nesten (same as in the map at top of mgt page)
• For Lithobates catesbeianus it is the total count from GBIF (Lithobates_catesbeianus.csv in S3 bucket)

We can change it to any type of source; the data only needs to contain year and region columns (count can be 1 per row).

[SanderDevisscher]

Since we want to display the invasion history of a species I think we need to use the observations instead of management. So the same data source as the observation maps.

• [ ] @mvarewyck highlight changes needed to input files
• [ ] @SanderDevisscher @soriadelva provide modified input files
• [ ] @mvarewyck move maps to indicators subtab

[mvarewyck]

@SanderDevisscher Which spatial regions do you want to show for the invasion maps?

(1) Municipalities & provinces like in the current invasion maps -> need to enrich data file be_alientaxa_cube.csv with columns

• NAAM: municipality name
• provincie: province name

(2) UTM 1x1 and 10x10 squares like in the current observation maps -> no change to the input data needed

[SanderDevisscher]

I think all 4 options should be possible.

[mvarewyck]

[ ] @SanderDevisscher @soriadelva provide modified input files

@soriadelva I saw this PR but it enriches the reporting files instead of observations? For this issue, we need to enrich be_alientaxa_cube.csv

[soriadelva]

[ ] @SanderDevisscher @soriadelva provide modified input files

@soriadelva I saw this PR but it enriches the reporting files instead of observations? For this issue, we need to enrich be_alientaxa_cube.csv

@mvarewyck thanks for noticing, I have now done a left join with the be_alientaxa_cube and the utm1 file and saved this as a .csv. However, this file seems too big to push to Github. How should I best add this file to the repo and is .csv okay (maybe .gpkg would be better?)

[mvarewyck]

[ ] @SanderDevisscher @soriadelva provide modified input files

@soriadelva I saw this PR but it enriches the reporting files instead of observations? For this issue, we need to enrich be_alientaxa_cube.csv

@mvarewyck thanks for noticing, I have now done a left join with the be_alientaxa_cube and the utm1 file and saved this as a .csv. However, this file seems too big to push to Github. How should I best add this file to the repo and is .csv okay (maybe .gpkg would be better?)

@soriadelva I don't think .gpkg will be smaller than .csv. The file you upload will be processed and reduced in size before uploading it to S3 as parquet file. How big is your file now? You could consider using Git LFS

[soriadelva]

[ ] @SanderDevisscher @soriadelva provide modified input files

@soriadelva I saw this PR but it enriches the reporting files instead of observations? For this issue, we need to enrich be_alientaxa_cube.csv

@mvarewyck thanks for noticing, I have now done a left join with the be_alientaxa_cube and the utm1 file and saved this as a .csv. However, this file seems too big to push to Github. How should I best add this file to the repo and is .csv okay (maybe .gpkg would be better?)

@soriadelva I don't think .gpkg will be smaller than .csv. The file you upload will be processed and reduced in size before uploading it to S3 as parquet file. How big is your file now? You could consider using Git LFS

@mvarewyck it's over 316 MB, I tried to use Git LFS but got the following error when pushing: batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.

[SanderDevisscher]

@mvarewyck @soriadelva i think we have to look into storing the file directly on the S3-bucket thus bypassing github

[soriadelva]

@mvarewyck @soriadelva i think we have to look into storing the file directly on the S3-bucket thus bypassing github

@SanderDevisscher, yes that would fix it 👍