Closed Bluesmile82 closed 8 months ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
orcasa-client | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Feb 14, 2024 11:25am |
I haven't tested the code yet. Could you tell me first:
interaction_config
objects. On the staging environment?I haven't tested the code yet. Could you tell me first:
- Where you have updated the
interaction_config
objects. On the staging environment?- Which layers can't have this feature?
label
and missing the unit
Land use group
and the Clay Content
and World reference Base layers
(These two last ones return 'Search returned no results.')Clay content and World Reference Base (2006) Soil Groups layers have working interaction now. This is ready for review again!
Updated text and units in Strapi. For no data we have "At coordinates ... there is no data". We can review this later if needed.
I think I rebased and they were added. I don't think they are needed so Ill clean them
It's clean now. Thanks for noticing
Show interactive data on click on the layers through a popup.
Check the interaction config on staging. There are more complex configuration on the layers with tabs or select like "Historic change"
https://vizzuality.atlassian.net/browse/ORC-226?atlOrigin=eyJpIjoiM2RlNmUwYTUwZGVhNGQ5YWFiYWY0MmE2NjczZjdlMTAiLCJwIjoiaiJ9
For some layers (Clay content and World Reference Base (2006) Soil Groups) we needed to specify the correct Bbox API format (overpass, nominatim, default). This is a new parameter on the CMS. If not specified the default will be the normal bbox format (WSEN)
Attention: We need to pass as an argument JSON_CONFIGURATION to the parseConfig method. This is not ideal but is because we are using it to get the default value for the layers interaction on complex layers and the deck.gl library is having problems when is server side rendered. At least in the version we are using. Here is the issue for more info: https://vizzuality.slack.com/archives/D5REHE38E/p1706610946819099 The solution is to import dynamically the Decode Layer which is part of the JSON_CONFIGURATION and was causing the app to crash if we were on SSR. The map will always render on the client anyways.
Example of interaction_config on Global Soil Organic Carbon Map v1.5 (GSOC) layer (already on staging):
There are some layers where the interaction will not work and science is aware of it. E.g. Land Cover group