Point collection catalog yields warnings

[dopplershift]

The following code:

from siphon.catalog import TDSCatalog
cat = TDSCatalog('http://thredds.ucar.edu/thredds/catalog/nws/metar/ncdecoded/catalog.xml?'
                 'dataset=nws/metar/ncdecoded/Metar_Station_Data_fc.cdmr')

yields:

WARNING:root:controlledVocabulary must have an attribute: vocabulary
WARNING:root:controlledVocabulary must have an attribute: vocabulary

I'm not sure if we're wrong or if thredds is wrong, but since we control it all, we really should make these warning go away somehow. (i.e. fix TDS or fix Siphon).

[JohnLCaron]

where does this message come from? an XML validator i assume. where does it
get the catalog schema?

On Sun, Jun 21, 2015 at 9:49 AM, Ryan May [email protected] wrote:

The following code:

from siphon.catalog import TDSCatalog
cat = TDSCatalog('http://thredds.ucar.edu/thredds/catalog/nws/metar/ncdecoded/'
'catalog.xml?'
'dataset=nws/metar/ncdecoded/Metar_Station_Data_fc.cdmr')

yields:

WARNING:root:controlledVocabulary must have an attribute: vocabulary
WARNING:root:controlledVocabulary must have an attribute: vocabulary

I'm not sure if we're wrong or if thredds is wrong, but since we control
it all, we really should make these warning go away somehow. (i.e. fix TDS
or fix Siphon).

—
Reply to this email directly or view it on GitHub
#28.

[JohnLCaron]

<xsd:complexType name="controlledVocabulary">
xsd:simpleContent
<xsd:extension base="xsd:string">
<xsd:attribute name="vocabulary" type="xsd:string"/>
/xsd:extension
/xsd:simpleContent
/xsd:complexType

Optional and Required Attributes

Attributes are optional by default. To specify that the attribute is
required, use the "use" attribute:
<xs:attribute name="lang" type="xs:string" use="required"/>

On Sun, Jun 21, 2015 at 3:25 PM, John Caron [email protected] wrote:

where does this message come from? an XML validator i assume. where does
it get the catalog schema?

On Sun, Jun 21, 2015 at 9:49 AM, Ryan May [email protected]
wrote:

The following code:

from siphon.catalog import TDSCatalog
cat = TDSCatalog('http://thredds.ucar.edu/thredds/catalog/nws/metar/ncdecoded/'
'catalog.xml?'
'dataset=nws/metar/ncdecoded/Metar_Station_Data_fc.cdmr')

yields:

WARNING:root:controlledVocabulary must have an attribute: vocabulary
WARNING:root:controlledVocabulary must have an attribute: vocabulary

I'm not sure if we're wrong or if thredds is wrong, but since we control
it all, we really should make these warning go away somehow. (i.e. fix TDS
or fix Siphon).

—
Reply to this email directly or view it on GitHub
#28.

[lesserwhirls]

I got it wrong in siphon. I'll get it fixed.

On Sunday, June 21, 2015, John Caron [email protected] wrote:

<xsd:complexType name="controlledVocabulary">
xsd:simpleContent
<xsd:extension base="xsd:string">
<xsd:attribute name="vocabulary" type="xsd:string"/>
/xsd:extension
/xsd:simpleContent
/xsd:complexType

Optional and Required Attributes

Attributes are optional by default. To specify that the attribute is
required, use the "use" attribute:
<xs:attribute name="lang" type="xs:string" use="required"/>

On Sun, Jun 21, 2015 at 3:25 PM, John Caron <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');> wrote:

where does this message come from? an XML validator i assume. where does
it get the catalog schema?

On Sun, Jun 21, 2015 at 9:49 AM, Ryan May <[email protected]
javascript:_e(%7B%7D,'cvml','[email protected]');>
wrote:

The following code:

from siphon.catalog import TDSCatalog
cat = TDSCatalog('
http://thredds.ucar.edu/thredds/catalog/nws/metar/ncdecoded/'
'catalog.xml?'
'dataset=nws/metar/ncdecoded/Metar_Station_Data_fc.cdmr')

yields:

WARNING:root:controlledVocabulary must have an attribute: vocabulary
WARNING:root:controlledVocabulary must have an attribute: vocabulary

I'm not sure if we're wrong or if thredds is wrong, but since we control
it all, we really should make these warning go away somehow. (i.e. fix
TDS
or fix Siphon).

—
Reply to this email directly or view it on GitHub
#28.

—
Reply to this email directly or view it on GitHub
#28 (comment).

[lesserwhirls]

@JohnLCaron - If attributes are optional by default, what is the difference between the optional attributes that minOccurs=0 and some those that do not?

For example:

  <xsd:complexType name="spatialRange">
   <xsd:sequence>
     <xsd:element name="start" type="xsd:double"  />
     <xsd:element name="size" type="xsd:double" />
     <xsd:element name="resolution" type="xsd:double" minOccurs="0" />
     <xsd:element name="units" type="xsd:string" minOccurs="0" />
   </xsd:sequence>
  </xsd:complexType>

What is the difference between, say, start and stop, and resolution and units? Does that indicate that if there is a start and stop, there may be a resolution and units (but start and stop must exist)?

[JohnLCaron]

attributes can only be required or not.

elements (as above) can have 0 to many, default i think is min=1, max=1

On Mon, Jun 22, 2015 at 10:06 AM, Sean Arms [email protected]
wrote:

@JohnLCaron https://github.com/JohnLCaron - If attributes are optional
by default, what is the difference between the optional attributes that
minOccurs=0 and some those that do not?

For example:

<xsd:complexType name="spatialRange">
xsd:sequence
<xsd:element name="start" type="xsd:double" />
<xsd:element name="size" type="xsd:double" />
<xsd:element name="resolution" type="xsd:double" minOccurs="0" />
<xsd:element name="units" type="xsd:string" minOccurs="0" />
/xsd:sequence
/xsd:complexType

What is the difference between, say, start and stop, and resolution and
units? Does that indicate that if there is a start and stop, there may be a
resolution and units (but start and stop must exist)?

—
Reply to this email directly or view it on GitHub
#28 (comment).

[lesserwhirls]

Ah, yes. My bad for mixing up attrs and elements.

Thanks!

On Mon, Jun 22, 2015 at 11:27 AM, John Caron [email protected]
wrote:

attributes can only be required or not.

elements (as above) can have 0 to many, default i think is min=1, max=1

On Mon, Jun 22, 2015 at 10:06 AM, Sean Arms [email protected]
wrote:

@JohnLCaron https://github.com/JohnLCaron - If attributes are optional
by default, what is the difference between the optional attributes that
minOccurs=0 and some those that do not?

For example:

<xsd:complexType name="spatialRange">
xsd:sequence
<xsd:element name="start" type="xsd:double" />
<xsd:element name="size" type="xsd:double" />
<xsd:element name="resolution" type="xsd:double" minOccurs="0" />
<xsd:element name="units" type="xsd:string" minOccurs="0" />
/xsd:sequence
/xsd:complexType

What is the difference between, say, start and stop, and resolution and
units? Does that indicate that if there is a start and stop, there may
be a
resolution and units (but start and stop must exist)?

—
Reply to this email directly or view it on GitHub
#28 (comment).

—
Reply to this email directly or view it on GitHub
#28 (comment).

[dopplershift]

Fixed with 7f07012.