Hi,
I just wanted to check if there is a suggested approach to more precisely specify the type of a rel: describes link similar to the rel: wms field from STAC web-map-links?
For instance, the following binds to the item's WMS/WFS services but a client that wishes to render these on map will need to guess from the URL what the actual type of the service is and how to request it.
|
{ |
|
"rel": "describes", |
|
"title": "OGC Web Map Service (WMS)", |
|
"href": "https://geo.woudc.org/ows?service=WMS&request=GetCapabilities" |
|
}, |
|
{ |
|
"rel": "describes", |
|
"title": "OGC Web Feature Service (WFS)", |
|
"href": "https://geo.woudc.org/ows?service=WFS&request=GetCapabilities" |
|
}, |
An additional attribute describing the service type would make the binding more predictable. I guess the definition of the type values itself is out-of-scope of Records API but is there a suggested attribute name for the type? Eg protocol: wms. Or does it make sense to use the STAC definition rel: wms?
Cheers
Hi,
I just wanted to check if there is a suggested approach to more precisely specify the type of a
rel: describeslink similar to therel: wmsfield from STAC web-map-links?For instance, the following binds to the item's WMS/WFS services but a client that wishes to render these on map will need to guess from the URL what the actual type of the service is and how to request it.
ogcapi-records/core/examples/json/record.json
Lines 300 to 309 in c06b998
An additional attribute describing the service type would make the binding more predictable. I guess the definition of the type values itself is out-of-scope of Records API but is there a suggested attribute name for the type? Eg
protocol: wms. Or does it make sense to use the STAC definitionrel: wms?Cheers