OID reference

zoneLocationProfile

1.3.6.1.4.1.1206.4.2.13.5.1.1.2

Description

Indicates the format of the zoneLocation object by referencing the location referencing standard SAE J2374. <DescriptiveName>zoneTable.locationProfile:code <Valid Value Rule> value - description geometry - zoneLocation is formatted in LRMS geometry format geographic - zoneLocation is formatted in LRMS geographic forma…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1206.4.2.13.5.1.1 (zoneEntry)
Node code
2
Node name
zoneLocationProfile
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1206.4.2.13.5.1.1.2
URN notation
urn:oid:1.3.6.1.4.1.1206.4.2.13.5.1.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1206 4 2 13 5 1 1 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nema(1206) transportation(4) devices(2) elms(13) elmsZone(5) zoneTable(1) zoneEntry(1) zoneLocationProfile(2)}
OID-IRI notation
  • /1/3/6/1/4/1/1206/4/2/13/5/1/1/2
  • /ISO/Identified-Organization/6/1/4/1/1206/4/2/13/5/1/1/2
  • /ISO/3/6/1/4/1/1206/4/2/13/5/1/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1206/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/identified-organization/dod/internet/private/enterprise/nema/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/identified-organization/dod/internet/private/enterprises/1206/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/identified-organization/dod/internet/private/enterprises/nema/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1206/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nema/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/identified-organization/dod/internet/private/vendor-objects/1206/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/identified-organization/dod/internet/private/vendor-objects/nema/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/org/dod/internet/private/enterprise/1206/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/org/dod/internet/private/enterprise/nema/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/org/dod/internet/private/enterprises/1206/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/org/dod/internet/private/enterprises/nema/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/org/dod/internet/private/ldap-enterprise/1206/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/org/dod/internet/private/ldap-enterprise/nema/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/org/dod/internet/private/vendor-objects/1206/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • /iso/org/dod/internet/private/vendor-objects/nema/transportation/devices/elms/elmsZone/zoneTable/zoneEntry/zoneLocationProfile
  • Additional combinations skipped.

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
mandatory, optional

Definitions may combine these properties differently.

Compare 2 source variants

Variant 1 — NTCIP published standard MIB annexes (reviewed modules)

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
mandatory

Variant 2 — NTCIP published standard MIB annexes (reviewed modules)

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
optional

Enumerated values

Numbers refer to source variants above. Each value is shown only for variants that define it.

ValueNameSource variants
1geometry1, 2
2geographic1, 2
3grid1, 2
4address1, 2

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In NTCIP1213v03, the row index zoneIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.1206.4.2.13.5.1.1.2.<zoneIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1206.4.2.13.5.1.1.2

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

zoneLocationProfile · mandatory

zoneLocationProfile OBJECT-TYPE
SYNTAX      INTEGER {
        geometry (1),
        geographic (2),
        grid (3),
        address (4)}
ACCESS      read-write
STATUS      mandatory
DESCRIPTION "Indicates the format of the zoneLocation object by referencing
the location referencing standard SAE J2374.
<DescriptiveName>zoneTable.locationProfile:code
<Valid Value Rule>
value - description
geometry - zoneLocation is formatted in LRMS geometry format
geographic - zoneLocation is formatted in LRMS geographic format
grid - zoneLocation is formatted in LRMS grid format
address - zoneLocation is formatted in LRMS address format
<Data Concept Type>
ENUMERATION {
        geometry (1),
        geographic (2),
        grid (3),
        text (4)}"
::= {zoneEntry 2}

zoneLocationProfile · optional

zoneLocationProfile OBJECT-TYPE
SYNTAX       INTEGER {
         geometry (1),
         geographic (2),
         grid (3),
         address (4)}


                                                                                      

                                                                                   
                                                                                  

ACCESS      read-write
STATUS      optional
DESCRIPTION "Indicates the format of the zoneLocation object by referencing
the location referencing standard SAE J2374.
<DescriptiveName>zoneTable.locationProfile:code
<Valid Value Rule>
value - description
geometry - zoneLocation is formatted in LRMS geometry format
geographic - zoneLocation is formatted in LRMS geographic format
grid - zoneLocation is formatted in LRMS grid format
address - zoneLocation is formatted in LRMS address format
<Data Concept Type>
ENUMERATION {
        geometry (1),
        geographic (2),
        grid (3),
        text (4)}"
::= {zoneEntry 2}

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Indicates the format of the zoneLocation object by referencing the location referencing standard SAE J2374. <DescriptiveName>zoneTable.locationProfile:code <Valid Value Rule> value - description geometry - zoneLocation is formatted in LRMS geometry format geographic - zoneLocation is formatted in LRMS geographic format grid - zoneLocation is formatted in LRMS grid format address - zoneLocation is formatted in LRMS address format <Data Concept Type> ENUMERATION { geometry (1), geographic (2), grid (3), text (4)}

Sources for this description

NTCIP published standard MIB annexes (reviewed modules)

See 2 matching source records

Evidence

Source records

2 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1NTCIP published standard MIB annexes (reviewed modules)2 records · 2 sources

Description 1

zoneLocationProfile · mandatoryNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: mandatory.

Names: zoneLocationProfile

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "zoneLocationProfile",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "geometry",
    "(",
    "1",
    ")",
    ",",
    "geographic",
    "(",
    "2",
    ")",
    ",",
    "grid",
    "(",
    "3",
    ")",
    ",",
    "address",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "mandatory",
    "DESCRIPTION",
    "\"Indicates the format of the zoneLocation object by referencing the location referencing standard SAE J2374. <DescriptiveName>zoneTable.locationProfile:code <Valid Value Rule> value - description geometry - zoneLocation is formatted in LRMS geometry format geographic - zoneLocation is formatted in LRMS geographic format grid - zoneLocation is formatted in LRMS grid format address - zoneLocation is formatted in LRMS address format <Data Concept Type> ENUMERATION { geometry (1), geographic (2), grid (3), text (4)}\"",
    "::=",
    "{",
    "zoneEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "geometry",
            1
          ],
          [
            "geographic",
            2
          ],
          [
            "grid",
            3
          ],
          [
            "address",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "mandatory"
    ],
    [
      "DESCRIPTION",
      "Indicates the format of the zoneLocation object by referencing the location referencing standard SAE J2374. <DescriptiveName>zoneTable.locationProfile:code <Valid Value Rule> value - description geometry - zoneLocation is formatted in LRMS geometry format geographic - zoneLocation is formatted in LRMS geographic format grid - zoneLocation is formatted in LRMS grid format address - zoneLocation is formatted in LRMS address format <Data Concept Type> ENUMERATION { geometry (1), geographic (2), grid (3), text (4)}"
    ],
    null,
    null,
    null,
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1213 v03 Object Definitions for Electrical and Lighting Management Systems (ELMS) Published January 2023 — original PDF · Official record

    Module: NTCIP1213v03

    See published definition above

    Module imports
    {'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['IpAddress', 'Counter', 'Gauge', 'Opaque'], 'NTCIP8004-v2': ['profiles', 'devices']}

    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: Publication-status ambiguity: the official catalog presents this NTCIP 1213 v03 PDF as published, while its physical page headers still say Draft NTCIP 1213 v03.37c. This entry reports the definitions printed in that public document, not independent confirmation of final approval or registration. Verify the exact edition before implementation.

    Source data warning: The luminaireCommProtocol DESCRIPTION omits its closing quote immediately before its explicit assignment 38. Close the parser string in one whitespace character; retain the literal source and unchanged numeric suffix.

    Source data warning: The luminaireLightSourceType DESCRIPTION is missing its closing quote immediately before its own explicit assignment 34. Close it in a whitespace character of the derived transcription; retain the exact original definition and numeric suffix.

    Source data warning: The luminaireWattage DESCRIPTION closes prematurely after its first sentence and also has a final closing quote after its metadata. Mask only the early delimiter so the complete native description and its own assignment 35 remain together; original text is retained.

    Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: NTCIP8004-v2. 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 1213-v0337c-aspublished.pdf — NTCIP1213v03 (MIB transcription)

    Related source files and packages:

    Show more related files and packages
zoneLocationProfile · optionalNTCIP published standard MIB annexes (reviewed modules)1 source

Status in source: optional.

Names: zoneLocationProfile

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "zoneLocationProfile",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "geometry",
    "(",
    "1",
    ")",
    ",",
    "geographic",
    "(",
    "2",
    ")",
    ",",
    "grid",
    "(",
    "3",
    ")",
    ",",
    "address",
    "(",
    "4",
    ")",
    "}",
    "ACCESS",
    "read-write",
    "STATUS",
    "optional",
    "DESCRIPTION",
    "\"Indicates the format of the zoneLocation object by referencing the location referencing standard SAE J2374. <DescriptiveName>zoneTable.locationProfile:code <Valid Value Rule> value - description geometry - zoneLocation is formatted in LRMS geometry format geographic - zoneLocation is formatted in LRMS geographic format grid - zoneLocation is formatted in LRMS grid format address - zoneLocation is formatted in LRMS address format <Data Concept Type> ENUMERATION { geometry (1), geographic (2), grid (3), text (4)}\"",
    "::=",
    "{",
    "zoneEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "geometry",
            1
          ],
          [
            "geographic",
            2
          ],
          [
            "grid",
            3
          ],
          [
            "address",
            4
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "optional"
    ],
    [
      "DESCRIPTION",
      "Indicates the format of the zoneLocation object by referencing the location referencing standard SAE J2374. <DescriptiveName>zoneTable.locationProfile:code <Valid Value Rule> value - description geometry - zoneLocation is formatted in LRMS geometry format geographic - zoneLocation is formatted in LRMS geographic format grid - zoneLocation is formatted in LRMS grid format address - zoneLocation is formatted in LRMS address format <Data Concept Type> ENUMERATION { geometry (1), geographic (2), grid (3), text (4)}"
    ],
    null,
    null,
    null,
    null
  ]
}
  • NTCIP published standard MIB annexes (reviewed modules) · Publisher's source file: NTCIP 1213 v02, Object Definitions for Electrical and Lighting Management Systems (ELMS) Published March 2011 — original PDF · Official record

    Module: NTCIP-1213v02-20

    See published definition above

    Module imports
    {'GLOBAL': ['globalSetIDParameter', 'globalMaxModules', 'moduleNumber', 'moduleDeviceNode', 'moduleMake', 'moduleModel', 'moduleVersion', 'moduleType', 'globalTime', 'globalDaylightSaving', 'globalLocalTimeDifferential'], 'RFC-1212': ['OBJECT-TYPE'], 'RFC1155-SMI': ['Counter'], 'RFC1213-MIB': ['DisplayString'], 'NTCIP8004v02': ['elms', 'OerString']}

    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: The PDF prints an invalid ASN.1 module label (NTCIP 1213v02.20). The derived transcription uses an equal-length internal parsing label; this is not an OID registration or an alteration of any numeric assignment. The original label and full PDF are retained.

    Source data warning: Potentially inaccurate interpretation of historical NTCIP namespace references: missing or unreadable imports of devices. 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 NTCIP1213v02.pdf — NTCIP-1213v02-20 (MIB transcription)

    Related source files and packages:

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1206)

Schopp Bruce J.

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1206.4.2.13.5.1.1.1 zoneIndex00
1.3.6.1.4.1.1206.4.2.13.5.1.1.3 zoneLocation00
1.3.6.1.4.1.1206.4.2.13.5.1.1.4 zoneMode00
1.3.6.1.4.1.1206.4.2.13.5.1.1.5 zoneSwitchMode00
1.3.6.1.4.1.1206.4.2.13.5.1.1.6 zoneSwitchModeTime00
1.3.6.1.4.1.1206.4.2.13.5.1.1.7 zoneLightThreshold00
1.3.6.1.4.1.1206.4.2.13.5.1.1.8 zoneHoldInterval00
1.3.6.1.4.1.1206.4.2.13.5.1.1.9 zoneLightHysteresis00
1.3.6.1.4.1.1206.4.2.13.5.1.1.10 zoneDelayInterval00
1.3.6.1.4.1.1206.4.2.13.5.1.1.11 zoneDimLevel00
1.3.6.1.4.1.1206.4.2.13.5.1.1.12 zoneDimWarmUpInterval00
1.3.6.1.4.1.1206.4.2.13.5.1.1.13 zoneFunctionalProfile00
1.3.6.1.4.1.1206.4.2.13.5.1.1.14 zonePhotocellIndex00
1.3.6.1.4.1.1206.4.2.13.5.1.1.15 zoneUnitsOfReading00