|
Revision 14
(checked in by graybeal, 3 years ago)
|
Reformatted and edited for clarity.
|
- Property svn:eol-style set to
native
|
| Line | |
|---|
| 1 |
Use Case 1: Discover and plot data from common sensor types automatically |
|---|
| 2 |
-> e.g., via SOS Services |
|---|
| 3 |
|
|---|
| 4 |
1. Portal presents a category "CTD" for a user to get data from a CTD sensor |
|---|
| 5 |
2. Users goes to a portal and searches data from CTD sensors |
|---|
| 6 |
3. Portal asks a registry for Sensor Observation Services which have as a method a CTD sensor |
|---|
| 7 |
[ need a URI to categorize this type ] |
|---|
| 8 |
4. Registry looks for services whose method is a CTD sensor |
|---|
| 9 |
[URI of CTD ] |
|---|
| 10 |
5. Registry returns services that uses a CTD sensor |
|---|
| 11 |
[ that matches the URI of the CTD ] |
|---|
| 12 |
6. Portal uses the service information retrieve from the registry to get the data. |
|---|
| 13 |
7. Portal knows how to plot CTD data and presents a preview to the user |
|---|
| 14 |
|
|---|
| 15 |
The term 'CTD' could be replaced by vertical profiler or any other type of sensor. |
|---|
