Status in source: mandatory.
Names: sampleDataTable
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"sampleDataTable",
"OBJECT-TYPE",
"SYNTAX",
"SEQUENCE",
"OF",
"SampleDataEntry",
"ACCESS",
"not-accessible",
"STATUS",
"mandatory",
"DESCRIPTION",
"\"<Definition> Table containing the historical sample period data. The number of rows in this table is equal to the maxSensorZones data element multiplied by the maxSampleDataEntries data element. Table rows are set by the manufacturer, and row creation/deletion is not supported. To retrieve all historical data entries for a zone, the last (oldest) entry should be retrieved by using numSampleDataEntries and retrieving class one (1) through numSensorZoneClass first. Class 1 is an aggregation of the data from all of the other classes (if any exist). All of the class data for a particular numSampleDataEntries has the same sequenceNumber. Once these entries are retrieved, the other entries sequence numbers denote the correct order of the samples. Sequence number is used rather than end date as the system clock may have been reset between data samples. <TableType> static <Object Identifier> 1.3.6.1.4.1.1206.4.2.4.3.4\"",
"::=",
"{",
"tssDataCollection",
"4",
"}"
],
"syntax_tree": [
[
"conceptualTable",
[
"row",
"SampleDataEntry"
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"mandatory"
],
[
"DESCRIPTION",
"<Definition> Table containing the historical sample period data. The number of rows in this table is equal to the maxSensorZones data element multiplied by the maxSampleDataEntries data element. Table rows are set by the manufacturer, and row creation/deletion is not supported. To retrieve all historical data entries for a zone, the last (oldest) entry should be retrieved by using numSampleDataEntries and retrieving class one (1) through numSensorZoneClass first. Class 1 is an aggregation of the data from all of the other classes (if any exist). All of the class data for a particular numSampleDataEntries has the same sequenceNumber. Once these entries are retrieved, the other entries sequence numbers denote the correct order of the samples. Sequence number is used rather than end date as the system clock may have been reset between data samples. <TableType> static <Object Identifier> 1.3.6.1.4.1.1206.4.2.4.3.4"
],
null,
null,
null,
null
]
}
- ITE public NTCIP working repository MIBs
· Publisher's source file: NTCIP-1209 — ntcip1209-Tss.mib
Module: NTCIP1209v02-MIB1
See published definition above
Module imports
{'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004-2008': ['OwnerString', 'BITMAP8', 'BITMAP16', 'BITMAP32', 'tss']}Source data warning: This original is published in an ITE NTCIP working repository. Repository publication does not establish that this particular revision is an adopted standard. Consult its native revision history and the NTCIP published standards catalog before implementation. Copyright and distribution notices are retained in the downloadable original.
Source data warning: Potentially inaccurate interpretation of historical NTCIP imports: the original references NTCIP8004-2008, which is absent from the public repository snapshot. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP-1209 — ntcip1209-Tss.mib
Related source files and packages:
- NTCIP published standard MIB annexes (reviewed modules)
· Publisher's source file: NTCIP 1209 v02, Object Definitions for Transportation Sensor Systems (TSS) Published May 2014 — original PDF
· Official record
Module: NTCIP1209v02-MIB1
See published definition above
Source data warning: Recovered from a file whose complete MIB does not parse. The original assignment and definition are preserved. Registration and implementation details may be inaccurate; consult the original file. Other damaged or unresolved declarations are not established registrations.
Source data warning: This record is transcribed from a published NTCIP MIB annex. The downloadable text is a derived transcription with page furniture and section headings masked; the unmodified original PDF is authoritative. Native definitions, DESCRIPTION and STATUS are retained. A published object definition does not establish support by any particular device.
Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: missing or unreadable imports of tss. These exact source files require the reviewed bindings shown below. The numeric roots used here are the explicit assignments in normative Annex A.2 of published NTCIP 8004 v02 (2010), physical pages 43–44. This does not establish that every historical module revision is identical. The annex also prints enterprise instead of RFC 1155 enterprises and declares Protocols while referencing protocols; those spelling interpretations are disclosed. The original IMPORTS, numeric suffixes and definitions remain unchanged. Verify both originals before implementation.
· Download NTCIP1209v0218jp.pdf — NTCIP1209v02-MIB1 (MIB transcription)
Related source files and packages: