Open mdye opened 8 years ago
keiserk
commented
8 years ago Has the generation of SensorML definitions for the sensors ever been implemented? Might be something to consider as tools for creating instruments are added. Would go a long way towards demonstration interoperability with other EC processes, catalogs, etc.
mdye
commented
8 years ago Hi Ken,
Yes, a SensorML description of each sensor is available for portal instruments/sensors. For example, the T6 instrument http://storm.chordsrt.com/instruments/11 is described by this SensorML http://storm.chordsrt.com/instruments/11.sensorml.
On Mon, Jun 13, 2016 at 1:04 PM, keiserk notifications@github.com wrote:
Has the generation of SensorML definitions for the sensors ever been implemented? Might be something to consider as tools for creating instruments are added. Would go a long way towards demonstration interoperability with other EC processes, catalogs, etc.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NCAR/chords_portal/issues/89#issuecomment-225676850, or mute the thread https://github.com/notifications/unsubscribe/AAQg18FtFbZzsotNDZTUAAg1gpAwJWXpks5qLampgaJpZM4I0i_h .
keiserk
commented
8 years ago Great - this is a good start. Looks to be some things missing (e.g. location), but definitely headed the right direction. We'll look at it more closely.
Ken
On Mon, Jun 13, 2016 at 3:46 PM, Mike Dye notifications@github.com wrote:
Hi Ken,
Yes, a SensorML description of each sensor is available for portal instruments/sensors. For example, the T6 instrument http://storm.chordsrt.com/instruments/11 is described by this SensorML http://storm.chordsrt.com/instruments/11.sensorml.
On Mon, Jun 13, 2016 at 1:04 PM, keiserk notifications@github.com wrote:
Has the generation of SensorML definitions for the sensors ever been implemented? Might be something to consider as tools for creating instruments are added. Would go a long way towards demonstration interoperability with other EC processes, catalogs, etc.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/NCAR/chords_portal/issues/89#issuecomment-225676850 , or mute the thread < https://github.com/notifications/unsubscribe/AAQg18FtFbZzsotNDZTUAAg1gpAwJWXpks5qLampgaJpZM4I0i_h
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NCAR/chords_portal/issues/89#issuecomment-225703341, or mute the thread https://github.com/notifications/unsubscribe/AHOullRAoBiTZhPE08UPnXoxMqJe_nKLks5qLcHDgaJpZM4I0i_h .
mdye
commented
8 years ago Location is included towards the bottom on the XML. Let me know if there is a better way to express the location!
On Mon, Jun 13, 2016 at 2:56 PM, keiserk notifications@github.com wrote:
Great - this is a good start. Looks to be some things missing (e.g. location), but definitely headed the right direction. We'll look at it more closely.
Ken
On Mon, Jun 13, 2016 at 3:46 PM, Mike Dye notifications@github.com wrote:
Hi Ken,
Yes, a SensorML description of each sensor is available for portal instruments/sensors. For example, the T6 instrument http://storm.chordsrt.com/instruments/11 is described by this SensorML http://storm.chordsrt.com/instruments/11.sensorml.
On Mon, Jun 13, 2016 at 1:04 PM, keiserk notifications@github.com wrote:
Has the generation of SensorML definitions for the sensors ever been implemented? Might be something to consider as tools for creating instruments are added. Would go a long way towards demonstration interoperability with other EC processes, catalogs, etc.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/NCAR/chords_portal/issues/89#issuecomment-225676850 , or mute the thread <
https://github.com/notifications/unsubscribe/AAQg18FtFbZzsotNDZTUAAg1gpAwJWXpks5qLampgaJpZM4I0i_h
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/NCAR/chords_portal/issues/89#issuecomment-225703341 , or mute the thread < https://github.com/notifications/unsubscribe/AHOullRAoBiTZhPE08UPnXoxMqJe_nKLks5qLcHDgaJpZM4I0i_h
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NCAR/chords_portal/issues/89#issuecomment-225705937, or mute the thread https://github.com/notifications/unsubscribe/AAQg19SuyYONNJrgtUKkny6h5UA5UKAWks5qLcQIgaJpZM4I0i_h .
keiserk
commented
8 years ago Right saw the field, but its not populated - unless that sensor is in the Atlantic at the equator. :-)
On Mon, Jun 13, 2016 at 4:02 PM, Mike Dye notifications@github.com wrote:
Location is included towards the bottom on the XML. Let me know if there is a better way to express the location!
On Mon, Jun 13, 2016 at 2:56 PM, keiserk notifications@github.com wrote:
Great - this is a good start. Looks to be some things missing (e.g. location), but definitely headed the right direction. We'll look at it more closely.
Ken
On Mon, Jun 13, 2016 at 3:46 PM, Mike Dye notifications@github.com wrote:
Hi Ken,
Yes, a SensorML description of each sensor is available for portal instruments/sensors. For example, the T6 instrument http://storm.chordsrt.com/instruments/11 is described by this SensorML http://storm.chordsrt.com/instruments/11.sensorml.
On Mon, Jun 13, 2016 at 1:04 PM, keiserk notifications@github.com wrote:
Has the generation of SensorML definitions for the sensors ever been implemented? Might be something to consider as tools for creating instruments are added. Would go a long way towards demonstration interoperability with other EC processes, catalogs, etc.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/NCAR/chords_portal/issues/89#issuecomment-225676850 , or mute the thread <
https://github.com/notifications/unsubscribe/AAQg18FtFbZzsotNDZTUAAg1gpAwJWXpks5qLampgaJpZM4I0i_h
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/NCAR/chords_portal/issues/89#issuecomment-225703341 , or mute the thread <
https://github.com/notifications/unsubscribe/AHOullRAoBiTZhPE08UPnXoxMqJe_nKLks5qLcHDgaJpZM4I0i_h
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/NCAR/chords_portal/issues/89#issuecomment-225705937 , or mute the thread < https://github.com/notifications/unsubscribe/AAQg19SuyYONNJrgtUKkny6h5UA5UKAWks5qLcQIgaJpZM4I0i_h
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NCAR/chords_portal/issues/89#issuecomment-225707596, or mute the thread https://github.com/notifications/unsubscribe/AHOulvSAYWdZe9rKG5KbayaEF4GwvYaIks5qLcV_gaJpZM4I0i_h .
mdye
commented
8 years ago Ha! Submarines could be a good CHORDS use case. :-)
It looks like the lat/lon was not configured for the site http://storm.chordsrt.com/sites at which that instrument is located. In retrospect, this was a poor example to provide. Here's a better one http://storm.chordsrt.com/instruments/1.sensorml.
On Tue, Jun 14, 2016 at 6:09 AM, keiserk notifications@github.com wrote:
Right saw the field, but its not populated - unless that sensor is in the Atlantic at the equator. :-)
On Mon, Jun 13, 2016 at 4:02 PM, Mike Dye notifications@github.com wrote:
Location is included towards the bottom on the XML. Let me know if there is a better way to express the location!
On Mon, Jun 13, 2016 at 2:56 PM, keiserk notifications@github.com wrote:
Great - this is a good start. Looks to be some things missing (e.g. location), but definitely headed the right direction. We'll look at it more closely.
Ken
On Mon, Jun 13, 2016 at 3:46 PM, Mike Dye notifications@github.com wrote:
Hi Ken,
Yes, a SensorML description of each sensor is available for portal instruments/sensors. For example, the T6 instrument http://storm.chordsrt.com/instruments/11 is described by this SensorML http://storm.chordsrt.com/instruments/11.sensorml.
On Mon, Jun 13, 2016 at 1:04 PM, keiserk notifications@github.com wrote:
Has the generation of SensorML definitions for the sensors ever been implemented? Might be something to consider as tools for creating instruments are added. Would go a long way towards demonstration interoperability with other EC processes, catalogs, etc.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/NCAR/chords_portal/issues/89#issuecomment-225676850 , or mute the thread <
https://github.com/notifications/unsubscribe/AAQg18FtFbZzsotNDZTUAAg1gpAwJWXpks5qLampgaJpZM4I0i_h
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/NCAR/chords_portal/issues/89#issuecomment-225703341 , or mute the thread <
https://github.com/notifications/unsubscribe/AHOullRAoBiTZhPE08UPnXoxMqJe_nKLks5qLcHDgaJpZM4I0i_h
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/NCAR/chords_portal/issues/89#issuecomment-225705937 , or mute the thread <
https://github.com/notifications/unsubscribe/AAQg19SuyYONNJrgtUKkny6h5UA5UKAWks5qLcQIgaJpZM4I0i_h
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/NCAR/chords_portal/issues/89#issuecomment-225707596 , or mute the thread < https://github.com/notifications/unsubscribe/AHOulvSAYWdZe9rKG5KbayaEF4GwvYaIks5qLcV_gaJpZM4I0i_h
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NCAR/chords_portal/issues/89#issuecomment-225861721, or mute the thread https://github.com/notifications/unsubscribe/AAQg10RBS6XZyu74h890y_RpOYZZ4ISkks5qLpnwgaJpZM4I0i_h .
keiserk
commented
8 years ago Yes agree that this one looks much better. Nice example that we can work with.
thanks
On Tue, Jun 14, 2016 at 11:14 AM, Mike Dye notifications@github.com wrote:
Ha! Submarines could be a good CHORDS use case. :-)
It looks like the lat/lon was not configured for the site http://storm.chordsrt.com/sites at which that instrument is located. In retrospect, this was a poor example to provide. Here's a better one http://storm.chordsrt.com/instruments/1.sensorml.
On Tue, Jun 14, 2016 at 6:09 AM, keiserk notifications@github.com wrote:
Right saw the field, but its not populated - unless that sensor is in the Atlantic at the equator. :-)
On Mon, Jun 13, 2016 at 4:02 PM, Mike Dye notifications@github.com wrote:
Location is included towards the bottom on the XML. Let me know if there is a better way to express the location!
On Mon, Jun 13, 2016 at 2:56 PM, keiserk notifications@github.com wrote:
Great - this is a good start. Looks to be some things missing (e.g. location), but definitely headed the right direction. We'll look at it more closely.
Ken
On Mon, Jun 13, 2016 at 3:46 PM, Mike Dye notifications@github.com wrote:
Hi Ken,
Yes, a SensorML description of each sensor is available for portal instruments/sensors. For example, the T6 instrument http://storm.chordsrt.com/instruments/11 is described by this SensorML http://storm.chordsrt.com/instruments/11.sensorml.
On Mon, Jun 13, 2016 at 1:04 PM, keiserk <notifications@github.com
wrote:
Has the generation of SensorML definitions for the sensors ever been implemented? Might be something to consider as tools for creating instruments are added. Would go a long way towards demonstration interoperability with other EC processes, catalogs, etc.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <
https://github.com/NCAR/chords_portal/issues/89#issuecomment-225676850
, or mute the thread <
https://github.com/notifications/unsubscribe/AAQg18FtFbZzsotNDZTUAAg1gpAwJWXpks5qLampgaJpZM4I0i_h
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/NCAR/chords_portal/issues/89#issuecomment-225703341 , or mute the thread <
https://github.com/notifications/unsubscribe/AHOullRAoBiTZhPE08UPnXoxMqJe_nKLks5qLcHDgaJpZM4I0i_h
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/NCAR/chords_portal/issues/89#issuecomment-225705937 , or mute the thread <
https://github.com/notifications/unsubscribe/AAQg19SuyYONNJrgtUKkny6h5UA5UKAWks5qLcQIgaJpZM4I0i_h
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/NCAR/chords_portal/issues/89#issuecomment-225707596 , or mute the thread <
https://github.com/notifications/unsubscribe/AHOulvSAYWdZe9rKG5KbayaEF4GwvYaIks5qLcV_gaJpZM4I0i_h
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <https://github.com/NCAR/chords_portal/issues/89#issuecomment-225861721 , or mute the thread < https://github.com/notifications/unsubscribe/AAQg10RBS6XZyu74h890y_RpOYZZ4ISkks5qLpnwgaJpZM4I0i_h
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/NCAR/chords_portal/issues/89#issuecomment-225933437, or mute the thread https://github.com/notifications/unsubscribe/AHOulo7xaVU9x1TKMLs7tFeipVXkxKE_ks5qLtNIgaJpZM4I0i_h .
mdye
commented
8 years ago Great! Let me know if you find other things that need modification.
On Tue, Jun 14, 2016 at 12:04 PM, keiserk notifications@github.com wrote:
Yes agree that this one looks much better. Nice example that we can work with.
thanks
On Tue, Jun 14, 2016 at 11:14 AM, Mike Dye notifications@github.com wrote:
Ha! Submarines could be a good CHORDS use case. :-)
It looks like the lat/lon was not configured for the site http://storm.chordsrt.com/sites at which that instrument is located. In retrospect, this was a poor example to provide. Here's a better one http://storm.chordsrt.com/instruments/1.sensorml.
On Tue, Jun 14, 2016 at 6:09 AM, keiserk notifications@github.com wrote:
Right saw the field, but its not populated - unless that sensor is in the Atlantic at the equator. :-)
On Mon, Jun 13, 2016 at 4:02 PM, Mike Dye notifications@github.com wrote:
Location is included towards the bottom on the XML. Let me know if there is a better way to express the location!
On Mon, Jun 13, 2016 at 2:56 PM, keiserk notifications@github.com wrote:
Great - this is a good start. Looks to be some things missing (e.g. location), but definitely headed the right direction. We'll look at it more closely.
Ken
On Mon, Jun 13, 2016 at 3:46 PM, Mike Dye < notifications@github.com> wrote:
Hi Ken,
Yes, a SensorML description of each sensor is available for portal instruments/sensors. For example, the T6 instrument http://storm.chordsrt.com/instruments/11 is described by this SensorML http://storm.chordsrt.com/instruments/11.sensorml.
On Mon, Jun 13, 2016 at 1:04 PM, keiserk < notifications@github.com
wrote:
Has the generation of SensorML definitions for the sensors ever been implemented? Might be something to consider as tools for creating instruments are added. Would go a long way towards demonstration interoperability with other EC processes, catalogs, etc.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <
https://github.com/NCAR/chords_portal/issues/89#issuecomment-225676850
, or mute the thread <
https://github.com/notifications/unsubscribe/AAQg18FtFbZzsotNDZTUAAg1gpAwJWXpks5qLampgaJpZM4I0i_h
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub <
https://github.com/NCAR/chords_portal/issues/89#issuecomment-225703341
, or mute the thread <
https://github.com/notifications/unsubscribe/AHOullRAoBiTZhPE08UPnXoxMqJe_nKLks5qLcHDgaJpZM4I0i_h
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/NCAR/chords_portal/issues/89#issuecomment-225705937 , or mute the thread <
https://github.com/notifications/unsubscribe/AAQg19SuyYONNJrgtUKkny6h5UA5UKAWks5qLcQIgaJpZM4I0i_h
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/NCAR/chords_portal/issues/89#issuecomment-225707596 , or mute the thread <
https://github.com/notifications/unsubscribe/AHOulvSAYWdZe9rKG5KbayaEF4GwvYaIks5qLcV_gaJpZM4I0i_h
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub < https://github.com/NCAR/chords_portal/issues/89#issuecomment-225861721 , or mute the thread <
https://github.com/notifications/unsubscribe/AAQg10RBS6XZyu74h890y_RpOYZZ4ISkks5qLpnwgaJpZM4I0i_h
.
— You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://github.com/NCAR/chords_portal/issues/89#issuecomment-225933437 , or mute the thread < https://github.com/notifications/unsubscribe/AHOulo7xaVU9x1TKMLs7tFeipVXkxKE_ks5qLtNIgaJpZM4I0i_h
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NCAR/chords_portal/issues/89#issuecomment-225965389, or mute the thread https://github.com/notifications/unsubscribe/AAQg14DIfDXGsVJjEIFgssHcYVDqM-Iiks5qLu0cgaJpZM4I0i_h .
from Matt Bartos:
"For setups with large numbers of sensors, manually adding instruments could become somewhat tedious. Having some sort of RESTful framework for instrument creation (similar to how measurements are updated now) could help automate that process."