🎉 Fetching server dates

[mamadOuologuem]

What is done

• Fetching availableDates from the specified servers in src/config/prism.json

Notes

• Access to fetch at 'https://mng-wfp.ovio.org:8443/geoserver/prism/wms?request=GetCapabilities' from origin 'http://localhost:3000' has been blocked by CORS policy
• The layers returned by the server are squared. We may investigate if we can make then fit on the country boundaries.
• More test on dates (server available dates, layers' time argument, date selector)
• Double-check the serversUrls in src/config/prism.json

[ericboucher]

Access to fetch at 'mng-wfp.ovio.org:8443/geoserver/prism/wms?request=GetCapabilities' from origin 'http://localhost:3000' has been blocked by CORS policy

I think that's because the server is down atm... Will check on it

[ericboucher]

The layers returned by the server are squared. We may investigate if we can make then fit on the country boundaries.

This is fine for now and probably part of the how tilling works in the data cube

[ericboucher]

So technically in Mongolia we have 2 servers with base URLS:

geoserver: https://mng-wfp.ovio.org:8443/geoserver/prism/
openDataCube: http://185.30.8.6:5000/

They can both return WMS & WCS layers using /wms?... or /wcs?... . The difference is that they don't return GetCapabilities the same way for WMS, which is why the python function I shared with you was a bit convoluted.

[ericboucher]

We will be using geoserver only for WMS though and openDataCube for both.
I think we should restructure the layers in layers.json to take:

• server_id instead of the server_uri
• server_type
• server_layer
• server_style (optional)

So that we can build URLs like this one programmatically -> http://185.30.8.6:5000/wms?styles=ndvi&layers=ModisIndices

[ericboucher]

Thoughts @bencpeters ?

[ericboucher]

@mamadOuologuem mng-wfp.ovio.org should be back up

[ericboucher]

Let's make sure the top links for About and GitHub look activated:

[bencpeters]

You don't really need to explicitly define any types - that's the default. In general, you should try to do stronger typing than any, but if it's not possible (or worth it), you don't need to actually type them as any

[mamadOuologuem]

Yeah, I think it's not worth giving a type to rawLayers because it comes from the server and it is formatted as soon as we received it.

Should I turn off the strict mode on tsconfig.json?
The strict mode automatically turn on noImplicitAny

I kinda prefer explicit any.

Comments have been addressed