element <StopMonitoringFIlter> (local)
Namespace:
http://www.siri.org.uk/siri
Type:
StopMonitoringFilterStructure
Content:
complex, 18 elements
Defined:
locally within StopMonitoringMultipleRequestStructure complexType in siri_stopMonitoring_service.xsd; see XML source
XML Representation Summary
<StopMonitoringFIlter>
   
Content: 
</StopMonitoringFIlter>
Content model elements (18):
DestinationRef (type DestinationRefStructure), DirectionRef (type DirectionRefStructure), Extensions, IncludeSituations (type xsd:boolean), IncludeTranslations, Language (type xsd:boolean), LineRef (type LineRefStructure), MaximumNumberOfCalls (defined in StopMonitoringRequestPolicyGroup group), MaximumStopVisits (type xsd:nonNegativeInteger), MaximumTextLength (type xsd:positiveInteger), MinimumStopVisitsPerLine (type xsd:nonNegativeInteger), MinimumStopVisitsPerLineVia (type xsd:nonNegativeInteger), MonitoringRef (type MonitoringRefStructure), OperatorRef (type OperatorRefStructure), PreviewInterval (type PositiveDurationType), StartTime (type xsd:dateTime), StopMonitoringDetailLevel (type StopMonitoringDetailEnumeration), StopVisitTypes (type StopVisitTypeEnumeration)
Included in content model of elements (1):
StopMonitoringMultipleRequest
Annotation
Request particulars for an individual stop as part of a list of multiple= requests.
XML Source (see within schema source)
<xsd:element maxOccurs="unbounded" name="StopMonitoringFIlter" type="StopMonitoringFilterStructure">
<xsd:annotation>
<xsd:documentation>
Request particulars for an individual stop as part of a list of multiple= requests.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
Content Element Detail (all declarations; 18/18)
DestinationRef
Type:
DestinationRefStructure, simple content
Defined:
locally within StopMonitoringTopicGroup group
Filter the results to include only journeys to the DESTINATION of the journey.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="DestinationRef" type="DestinationRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only journeys to the DESTINATION of the journey.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
DirectionRef
Type:
DirectionRefStructure, simple content
Defined:
locally within StopMonitoringTopicGroup group
Filter the results to include only Stop Visits for vehicles running in a specific relative DIRECTION, for example, "inbound" or "outbound". (Direction does not specify a destination.)
XML Source (see within schema source)
<xsd:element minOccurs="0" name="DirectionRef" type="DirectionRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only Stop Visits for vehicles running in a specific relative DIRECTION, for example, "inbound" or "outbound". (Direction does not specify a destination.)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
Extensions
Type:
ExtensionsStructure, complex content
Defined:
by reference within StopMonitoringFilterStructure complexType
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="Extensions"/>
IncludeSituations
Type:
xsd:boolean, predefined, simple content
Defined:
locally within StopMonitoringRequestPolicyGroup group
Whether any related SITUATIONs should be included in the ServiceDelivery. Default is 'false'. +SIRI v2.0
XML Source (see within schema source)
<xsd:element minOccurs="0" name="IncludeSituations" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Whether any related SITUATIONs should be included in the ServiceDelivery. Default is 'false'. +SIRI v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
IncludeTranslations
Type:
xsd:boolean, predefined, simple content
Defined:
by reference within StopMonitoringRequestPolicyGroup group
XML Source (see within schema source)
<xsd:element minOccurs="0" ref="IncludeTranslations"/>
Language
Type:
xsd:boolean, predefined, simple content
Default:
"false"
Defined:
locally within StopMonitoringRequestPolicyGroup group
Preferred language in which to return text values.
XML Source (see within schema source)
<xsd:element default="false" minOccurs="0" name="Language" type="xsd:boolean">
<xsd:annotation>
<xsd:documentation>
Preferred language in which to return text values.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
LineRef
Type:
LineRefStructure, simple content
Defined:
locally within StopMonitoringTopicGroup group
Filter the results to include only Stop Visits for VEHICLEs for the given LINE.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="LineRef" type="LineRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only Stop Visits for VEHICLEs for the given LINE.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
MaximumNumberOfCalls
Type:
anonymous complexType, complex content
Defined:
locally within StopMonitoringRequestPolicyGroup group
If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="MaximumNumberOfCalls">
<xsd:annotation>
<xsd:documentation>
If calls are to be returned, maximum number of calls to include in response. If absent, exclude all calls.
</xsd:documentation>
</xsd:annotation>
<xsd:complexType>
<xsd:sequence>
<xsd:element minOccurs="0" name="Previous" type="xsd:nonNegativeInteger">
<xsd:annotation>
<xsd:documentation>
Maximum number of ONWARDS CALLs to include in results. Only applies if StopMonitoringDetailLevel of 'calls' specified. Zero for none. If StopMonitoringDetailLevel of 'calls' specified but MaximumNumberOfCalls.Previous absent, include all ONWARDS CALLs.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element minOccurs="0" name="Onwards" type="xsd:nonNegativeInteger">
<xsd:annotation>
<xsd:documentation>
Maximum number of ONWARDS CALLs to include in results. Zero for none. Only applies if StopMonitoringDetailLevel of 'calls'specified. Zero for none. If StopMonitoringDetailLevel of 'calls' specified but MaximumNumberOfCalls.Onwards absent, include all ONWARDS CALLs.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
MaximumStopVisits
Type:
xsd:nonNegativeInteger, predefined, simple content
Defined:
locally within StopMonitoringRequestPolicyGroup group
The maximum number of Stop Visits to include in a given delivery. The first n Stop Visits within the look ahead window are included. Only Visits within the Lookahead Interval are returned. The MinimumStopVisits parameter can be used to reduce the the number of entries for each LINE within the total returned.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="MaximumStopVisits" type="xsd:nonNegativeInteger">
<xsd:annotation>
<xsd:documentation>
The maximum number of Stop Visits to include in a given delivery. The first n Stop Visits within the look ahead window are included. Only Visits within the Lookahead Interval are returned. The MinimumStopVisits parameter can be used to reduce the the number of entries for each LINE within the total returned.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
MaximumTextLength
Type:
xsd:positiveInteger, predefined, simple content
Default:
"30"
Defined:
locally within StopMonitoringRequestPolicyGroup group
Maximum length of text to return for text elements. Default is 30.
XML Source (see within schema source)
<xsd:element default="30" minOccurs="0" name="MaximumTextLength" type="xsd:positiveInteger">
<xsd:annotation>
<xsd:documentation>
Maximum length of text to return for text elements. Default is 30.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
MinimumStopVisitsPerLine
Type:
xsd:nonNegativeInteger, predefined, simple content
Defined:
locally within StopMonitoringRequestPolicyGroup group
The minimum number of Stop Visits for a given LINE to include in a given delivery. If there are more Visits within the LookAheadInterval than allowed by MaximumStopVisits and a MinimumStopVisits value is specified, then at least the minimum number will be delivered for each LINE. I.e Stop Visits will be included even if the Stop Visits are later than those for some other LINE for which the minimum number of Stop Visits has already been supplied. This allows the Consumer to obtain at least one entry for every available LINE with vehicles approaching the stop. Only STOP Visits within the Look ahead Interval are returned.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="MinimumStopVisitsPerLine" type="xsd:nonNegativeInteger">
<xsd:annotation>
<xsd:documentation>
The minimum number of Stop Visits for a given LINE to include in a given delivery. If there are more Visits within the LookAheadInterval than allowed by MaximumStopVisits and a MinimumStopVisits value is specified, then at least the minimum number will be delivered for each LINE. I.e Stop Visits will be included even if the Stop Visits are later than those for some other LINE for which the minimum number of Stop Visits has already been supplied. This allows the Consumer to obtain at least one entry for every available LINE with vehicles approaching the stop. Only STOP Visits within the Look ahead Interval are returned.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
MinimumStopVisitsPerLineVia
Type:
xsd:nonNegativeInteger, predefined, simple content
Defined:
locally within StopMonitoringRequestPolicyGroup group
The minimum number of Stop Visits for a given LINE and VIA combination to include in a given delivery. As for MinimumStopVisitsPerLine but with Via also taken into account. SIRI+v2.0
XML Source (see within schema source)
<xsd:element minOccurs="0" name="MinimumStopVisitsPerLineVia" type="xsd:nonNegativeInteger">
<xsd:annotation>
<xsd:documentation>
The minimum number of Stop Visits for a given LINE and VIA combination to include in a given delivery. As for MinimumStopVisitsPerLine but with Via also taken into account. SIRI+v2.0
</xsd:documentation>
</xsd:annotation>
</xsd:element>
MonitoringRef
Type:
MonitoringRefStructure, simple content
Defined:
locally within StopMonitoringTopicGroup group
Reference to Monitoring Point(s) about which data is requested. May be a STOP POINT, timing point, or a group of points under a single reference.
XML Source (see within schema source)
<xsd:element name="MonitoringRef" type="MonitoringRefStructure">
<xsd:annotation>
<xsd:documentation>
Reference to Monitoring Point(s) about which data is requested. May be a STOP POINT, timing point, or a group of points under a single reference.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
OperatorRef
Type:
OperatorRefStructure, simple content
Defined:
locally within StopMonitoringTopicGroup group
Filter the results to include only Stop Visits for VEHICLEs run by the specified OPERATOR.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="OperatorRef" type="OperatorRefStructure">
<xsd:annotation>
<xsd:documentation>
Filter the results to include only Stop Visits for VEHICLEs run by the specified OPERATOR.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
PreviewInterval
Type:
PositiveDurationType, simple content
Defined:
locally within StopMonitoringTopicGroup group
Forward duration for which Visits should be included, that is, interval before predicted arrival at the stop for which to include Visits: only journeys which will arrive or depart within this time span will be returned.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="PreviewInterval" type="PositiveDurationType">
<xsd:annotation>
<xsd:documentation>
Forward duration for which Visits should be included, that is, interval before predicted arrival at the stop for which to include Visits: only journeys which will arrive or depart within this time span will be returned.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
StartTime
Type:
xsd:dateTime, predefined, simple content
Defined:
locally within StopMonitoringTopicGroup group
Start time for PreviewInterval. If absent, then current time is assumed.
XML Source (see within schema source)
<xsd:element minOccurs="0" name="StartTime" type="xsd:dateTime">
<xsd:annotation>
<xsd:documentation>
Start time for PreviewInterval. If absent, then current time is assumed.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
StopMonitoringDetailLevel
Type:
StopMonitoringDetailEnumeration, simple content
Default:
"normal"
Defined:
locally within StopMonitoringRequestPolicyGroup group
Level of detail to include in response. Default is 'normal'.
XML Source (see within schema source)
<xsd:element default="normal" minOccurs="0" name="StopMonitoringDetailLevel" type="StopMonitoringDetailEnumeration">
<xsd:annotation>
<xsd:documentation>
Level of detail to include in response. Default is 'normal'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
StopVisitTypes
Type:
StopVisitTypeEnumeration, simple content
Default:
"all"
Defined:
locally within StopMonitoringTopicGroup group
Whether to include arrival Visits, departure Visits, or all. Default is 'all'.
XML Source (see within schema source)
<xsd:element default="all" minOccurs="0" name="StopVisitTypes" type="StopVisitTypeEnumeration">
<xsd:annotation>
<xsd:documentation>
Whether to include arrival Visits, departure Visits, or all. Default is 'all'.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
This XML schema documentation has been generated with DocFlex/XML 1.9.5 using DocFlex/XML XSDDoc 2.8.1 template set.
DocFlex/XML is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high-quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.
DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-quality XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).
A commercial license for "DocFlex/XML XSDDoc" will allow you:
  • To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support > 400 template parameters, which work the same as "options" of ordinary doc-generators. The parameters are organized in nested groups, which form a parameter tree. Most of them have their default values calculated dynamically from a few primary parameters. So, you'll never need to specify all of them. That will give you swift and effective control over the generated content!
  • To use certain features disabled in the free mode (such as the full documenting of substitution groups).
  • To select only the initial, imported, included, redefined XML schemas to be documented or only those directly specified by name.
  • To include only XML schema components specified by name.
  • To document local element components both globally and locally (similar to attributes).
  • To allow/suppress unification of local elements by type.
  • To enable/disable reproducing of namespace prefixes.
  • To use PlainDoc.tpl main template to generate all the XML schema documentation in a signle-file form as both HTML and incredible quality RTF output.
  • To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
  • To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
  • To remove this very advertisement text!
Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML (Full Edition) and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!
But this is not all. In addition to it, a commercial license for "DocFlex/XML SDK" will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!
Please note that by purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the results of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!
To purchase a license, please follow this link: http://www.filigris.com/shop/