Closed ateucher closed 3 years ago
@boshek @stephhazlitt - re the wms/wfs/web service/web map service. WFS (Web Feature Service) and WMS (Web Map Service) are both special cases of OWS (OGC Web Service). I think any catalogue record that has one of WFS of WMS will have both. The catalogue lists all of these records as WMS (which is why bcdc_tidy_resources()
lists them as such and we use that language throughout) though bcdata
pretty much only makes use of the WFS (except in bcdc_preview()
which is only just functional).
So the cadillac fix would be to go through it all and use ows/wms/wfs consitently where they are appropriate, but as a stopgap it might be worth just updating the documentation as Miles suggested. Thoughts?
Could we just use Web Service throughout?
I think "Web Map Service" might be better, since the catalogue is also a web service.
That said, the way you use "Web Feature Service" in #266 is correct, and switching that to "Web Map Service" would be wrong - WMS is the image overlay service, WFS is the actual vector shapes + attributes.
I say keep the article as you have it, and I'll try to align some of the documentation
TTW picking the proper noun was one of the hardest part of the writing.... 🤷♀️
UF3: Should you state explicitly in the documentation that the format of a resource needs to be
wms
to usebcdc_query_geodata
?The help for
bcdc_query_geodata
says:And the closest statement I have found is in the
Querying Spatial Data with bcdata
vignette:I am 95% sure this corresponds to the
wms
format based on the content of theWeb Service
link. If true, this could be made more explicit by changing that para to something like:Originally posted by @MilesMcBain in https://github.com/bcgov/bcdata/issues/239#issuecomment-758614846