You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 18, 2019. It is now read-only.
Right now if you navigate to an SOS dataset such as this GCOOS dataset, you're only able to reference the service (i.e. SOS GetCaps). This is just personal opinion here, but I've always found it rather onerous to have to manually type out DescribeSensor requests based upon the output of GetCapabilities. Ideally, we should have links so that users don't have to do that. Since we're accessing the DescribeSensor output to get information about the SOS sensors/stations/networks anyway, we ought to link to the DescribeSensor URL.
The text was updated successfully, but these errors were encountered:
+1, add it to the list so we can talk about it at the next release planning session. Actually, you already have added it. Start thinking about ways you might parse and visualize SensorML documents to, for example, address @emiliom comment above.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now if you navigate to an SOS dataset such as this GCOOS dataset, you're only able to reference the service (i.e. SOS GetCaps). This is just personal opinion here, but I've always found it rather onerous to have to manually type out DescribeSensor requests based upon the output of GetCapabilities. Ideally, we should have links so that users don't have to do that. Since we're accessing the DescribeSensor output to get information about the SOS sensors/stations/networks anyway, we ought to link to the DescribeSensor URL.
The text was updated successfully, but these errors were encountered: