Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WMS parsing of THREDDS service #234

Closed
fmigneault opened this issue Nov 13, 2019 · 7 comments · Fixed by #363
Closed

WMS parsing of THREDDS service #234

fmigneault opened this issue Nov 13, 2019 · 7 comments · Fixed by #363
Assignees
Labels
feature New feature to be developed plugin Service plugin

Comments

@fmigneault
Copy link
Collaborator

Support the new functionality of integrated WMS in Thredds.

@fmigneault fmigneault added feature New feature to be developed plugin Service plugin labels Nov 13, 2019
@fmigneault
Copy link
Collaborator Author

@huard @dbyrns
Please provide more details about the exact use case, not sure I understood everything.

@huard
Copy link
Contributor

huard commented Nov 13, 2019

THREDDS provides for each file/dataset a list of services: HTTP, Opendap, NCML, UDDC, ISO, WCS, WMS.

https://pavics.ouranos.ca/twitcher/ows/proxy/thredds/catalog/birdhouse/testdata/flyingpigeon/cmip5/catalog.html?dataset=birdhouse/testdata/flyingpigeon/cmip5/tasmax_Amon_MPI-ESM-MR_rcp45_r2i1p1_200601-200612.nc

A potential use case is to allow anonymous access to the ISO and UDDC services, but private access to all other services.

@dbyrns
Copy link
Contributor

dbyrns commented Nov 13, 2019

Right now, when we access the twitcher/ows/proxy/thredds the read permissions is check to allow access to the /catalog/{resource} /fileServer/{resource} and /dodsC/{resource} sub-services. We need to ensure that every other sub-services which are now active (see https://pavics.ouranos.ca/twitcher/ows/proxy/thredds/catalog/birdhouse/cmip5/NASA-GISS/GISS-E2-R-CC/rcp85/mon/seaIce/r1i1p1/sic/catalog.html?dataset=birdhouse/cmip5/NASA-GISS/GISS-E2-R-CC/rcp85/mon/seaIce/r1i1p1/sic/sic_OImon_GISS-E2-R-CC_rcp85_r1i1p1_207601-210012.nc) iso, wcs, wms can be accessed the same way.

For now let's use the "read" permission also and @huard will tell us if we need a read_wms, read_wcs, read_opendap, etc. permissions.

@dbyrns
Copy link
Contributor

dbyrns commented Nov 13, 2019

Ok well, @huard beat me with his post, so at least we will require the read_iso and read_uddc permissions for these two services. read could still be used for the others sub-services unless other needs arise.

@huard
Copy link
Contributor

huard commented Nov 13, 2019

I don't know if it's useful, but I think we could split services into two categories: metadata access and data access.

Metadata-only access: NCML, ISO, UDDC
Data access: HTTP, Opendap, WCS, WMS

@dbyrns
Copy link
Contributor

dbyrns commented Nov 14, 2019

Very useful.
I propose 3 permissions then : write, read_metadata, read_data with the subservices mapping provided by @huard .

@fmigneault
Copy link
Collaborator Author

3 permissions for BROWSE metadata and READ/WRITE data are implemented by #361 via PRs #353 and #363

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature to be developed plugin Service plugin
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants