rsmp_schemer 0.3.2 → 0.4.2

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0020.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Control mode\n\nCan be used for the management system to check the current control mode (startup, normal, standby, failure, test).",
+      "description" : "Control mode.\nCan be used for the management system to check the current control mode (startup, normal, standby, failure, test).",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0021.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Manually set detector logic\n\nProvides status of detector logic (1-255) regarding if they are either forced to true or false.\n\nCan be used to connect RSMP compatible detection equipment to the traffic light controller. Can also be used for prioritization.",
+      "description" : "Manually set detector logic.\nProvides status of detector logic (1-255) regarding if they are either forced to true or false.\nCan be used to connect RSMP compatible detection equipment to the traffic light controller. Can also be used for prioritization.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0022.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "List of time plans\n\nProvides a list of the configured time plans which is possible to use. This status was added due to status S0018 only provides the total number of time plans and not which were possible to use with M0002.\n\nCan be used for the management system to check the number of time plans configured in the controller.",
+      "description" : "List of time plans.\nProvides a list of the configured time plans which is possible to use. This status was added due to status S0018 only provides the total number of time plans and not which were possible to use with M0002.\nCan be used for the management system to check the number of time plans configured in the controller.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0023.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Dynamic bands\n\nProvides a list of all defined dynamic bands. Dynamic bands moves start of signal groups in the cycle and changes the signal timings.\n\nA typical usage of dynamic bands is scenario based control where changing of signal timings is used for optimal traffic flow.",
+      "description" : "Dynamic bands.\nProvides a list of all defined dynamic bands. Dynamic bands moves start of signal groups in the cycle and changes the signal timings.\nA typical usage of dynamic bands is scenario based control where changing of signal timings is used for optimal traffic flow.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0024.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Offset time\n\nOffset time is used to define an offset between intersections in coordinated control. It is based on the expected travel time between intersections.\n\nCan be used by the management system to check to fine tune the coordination for optimal traffic flow.",
+      "description" : "Offset time.\nOffset time is used to define an offset between intersections in coordinated control. It is based on the expected travel time between intersections.\nCan be used by the management system to check to fine tune the coordination for optimal traffic flow.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0025.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Time-of-Green / Time-of-Red\n\nProvides predicted signal timings of green and red for each signal group. Max, min and likely time to green and red.",
+      "description" : "Time-of-Green / Time-of-Red.\nProvides predicted signal timings of green and red for each signal group. Max, min and likely time to green and red.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0026.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Week time table\n\nWeek time table for signal programs (time plan) to use for each day during a week.\n\nThe week time table determine which predefined signal timings (time plan) to use during the week for optimal traffic flow.",
+      "description" : "Week time table.\nWeek time table for signal programs (time plan) to use for each day during a week.\nThe week time table determine which predefined signal timings (time plan) to use during the week for optimal traffic flow.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0027.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Time tables\n\nTime of day for when to switch signal program (time plan).\n\nThe signal timings (time plan) to use during time of day for optimal traffic flow.",
+      "description" : "Time tables.\nTime of day for when to switch signal program (time plan).\nThe signal timings (time plan) to use during time of day for optimal traffic flow.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0028.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Cycle time\n\nCycle time (or cycle length) is the sum of all phases in a time plan (traffic program). This time is fixed when using fixed time control or coordination (except \"local coordination\"). When the cycle counter reaches this length it is reset back to zero.\n\nChanging the cycle time can be used as part of scenario based control.",
+      "description" : "Cycle time.\nCycle time (or cycle length) is the sum of all phases in a time plan (traffic program). This time is fixed when using fixed time control or coordination (except \"local coordination\"). When the cycle counter reaches this length it is reset back to zero.\nChanging the cycle time can be used as part of scenario based control.",
       "properties" : {
         "n" : {
           "enum" : [
@@ -24,7 +24,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Cycle time table\nEach cycle time is written as pp-tt where:\npp=time plan\ntt=cycle time in seconds\n\nEach cycle time is separated with a comma\n\n\nE.g.\npp-tt,pp-tt",
+            "description" : "Cycle time table\nEach cycle time is written as pp-tt where:\npp=time plan\ntt=cycle time in seconds\n\nEach cycle time is separated with a comma\n\nE.g.\npp-tt,pp-tt",
             "type" : "string"
           }
         }

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0029.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Forced input status\n\nProvide status of input (1-255) regarding if they are forced or not. Can be used for all types of input where the traffic light controller must react to external control.\n\nCan be used for bus priority, coordination between traffic controllers, external control systems, and much more.",
+      "description" : "Forced input status.\nProvide status of input (1-255) regarding if they are forced or not. Can be used for all types of input where the traffic light controller must react to external control.\nCan be used for bus priority, coordination between traffic controllers, external control systems, and much more.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0030.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Forced output status\n\nProvide status of output (1-255) regarding if they are forced or not. Can be used for all types of output where the traffic light controller needs to control other equipment.\n\nCan be used for bus priority, coordination between traffic controllers, external control systems, and much more.",
+      "description" : "Forced output status.\nProvide status of output (1-255) regarding if they are forced or not. Can be used for all types of output where the traffic light controller needs to control other equipment.\nCan be used for bus priority, coordination between traffic controllers, external control systems, and much more.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0031.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Trigger level sensitivity for loop detector\n\nThe trigger level sensitivity determines at what level the loop detector should trigger. If it set too low then then traffic will not be detected as intended. If it is set too high the detector might give false positives.\n\nCan be used to make sure that the detectors detect traffic as intended.",
+      "description" : "Trigger level sensitivity for loop detector.\nThe trigger level sensitivity determines at what level the loop detector should trigger. If it set too low then then traffic will not be detected as intended. If it is set too high the detector might give false positives.\nCan be used to make sure that the detectors detect traffic as intended.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0091.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Operator logged in/out OP-panel\n\nProvides information if maintenance personnel is currently working on site.",
+      "description" : "Operator logged in/out OP-panel.\nProvides information if maintenance personnel is currently working on site.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0092.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Operator logged in/out web-interface\n\nProvides information if maintenance personnel is currently working with the controller.",
+      "description" : "Operator logged in/out web-interface.\nProvides information if maintenance personnel is currently working with the controller.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0095.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Version of Traffic Light Controller\n\nProvides diagnostic version information.",
+      "description" : "Version of Traffic Light Controller.\nProvides diagnostic version information.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0096.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Current date and time\n\nProvides diagnostic information about the current date and time set in the controller.",
+      "description" : "Current date and time\nProvides diagnostic information about the current date and time set in the controller.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0097.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Checksum of traffic parameters\n\nCan be used to check if any traffic parameter has been changed.\n\nFor instance, depending on controller, maintenance personnel can modify traffic parameters on site to optimize traffic flow. This status provides the ability to monitor if any traffic parameter has been changed. The traffic parameters may be downloaded with S0098.",
+      "description" : "Checksum of traffic parameters.\nCan be used to check if any traffic parameter has been changed.\nFor instance, depending on controller, maintenance personnel can modify traffic parameters on site to optimize traffic flow. This status provides the ability to monitor if any traffic parameter has been changed. The traffic parameters may be downloaded with S0098.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0098.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Configuration of traffic parameters\n\nCan be used to download all traffic parameters from the controller.\n\nFor instance, depending on controller, maintenance personnel can modify traffic parameters on site to optimize traffic flow. This status provides the ability to downloaded them.",
+      "description" : "Configuration of traffic parameters.\nCan be used to download all traffic parameters from the controller.\nFor instance, depending on controller, maintenance personnel can modify traffic parameters on site to optimize traffic flow. This status provides the ability to downloaded them.",
       "properties" : {
         "n" : {
           "enum" : [
@@ -26,7 +26,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Traffic parameters\nIncludes\n- all signal programs, including program versions\n- signal group settings\n- time plans\n- safety matrix\n- intergreen times\n- detector setting\n\nIt should NOT include:\n- network settings\n- log files\n- software\n- other device settings that are not part of the signal program\n\nNote:\n- There is no way to upload this binary file to the TLC using RSMP\n- The format of the binary file is not specified and is not expected to be compatible between suppliers",
+            "description" : "Traffic parameters.\nIncludes\n- all signal programs, including program versions\n- signal group settings\n- time plans\n- safety matrix\n- intergreen times\n- detector setting\n\nIt should NOT include:\n- network settings\n- log files\n- software\n- other device settings that are not part of the signal program\n\nNote:\n- There is no way to upload this binary file to the TLC using RSMP\n- The format of the binary file is not specified and is not expected to be compatible between suppliers",
             "type" : "string"
           }
         }

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0201.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Traffic Counting: Number of vehicles\n\nUsed for Traffic counting.",
+      "description" : "Traffic Counting: Number of vehicles.\nUsed for Traffic counting.",
       "properties" : {
         "n" : {
           "enum" : [

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0202.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Traffic Counting: Vehicle speed\n\nUsed for Traffic counting.",
+      "description" : "Traffic Counting: Vehicle speed.\nUsed for Traffic counting.",
       "properties" : {
         "n" : {
           "enum" : [
@@ -25,7 +25,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Time stamp for start of measuring. Format according to W3C XML dateTime with a resolution of 3 decimal places. All time stamps in UTC. E.g. 2009-10-02T14:34:34.341Z",
+            "description" : "Time stamp for start of measuring. Format according to W3C\nXML dateTime with a resolution of 3 decimal places. All time stamps\nin UTC. E.g. 2009-10-02T14:34:34.341Z",
             "$ref" : "../../core/definitions.json#/timestamp"
           }
         }

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0203.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Traffic Counting: Occupancy\n\nUsed for Traffic counting.",
+      "description" : "Traffic Counting: Occupancy.\nUsed for Traffic counting.",
       "properties" : {
         "n" : {
           "enum" : [
@@ -25,7 +25,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Time stamp for start of measuring. Format according to W3C XML dateTime with a resolution of 3 decimal places. All time stamps in UTC. E.g. 2009-10-02T14:34:34.341Z",
+            "description" : "Time stamp for start of measuring. Format according to W3C\nXML dateTime with a resolution of 3 decimal places. All time stamps\nin UTC. E.g. 2009-10-02T14:34:34.341Z",
             "$ref" : "../../core/definitions.json#/timestamp"
           }
         }

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0204.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Traffic Counting: Number of vehicles of given classification\n\nUsed for Traffic counting.",
+      "description" : "Traffic Counting: Number of vehicles of given classification.\nUsed for Traffic counting.",
       "properties" : {
         "n" : {
           "enum" : [
@@ -33,7 +33,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Time stamp for start of measuring. Format according to W3C XML dateTime with a resolution of 3 decimal places. All time stamps in UTC. E.g. 2009-10-02T14:34:34.341Z",
+            "description" : "Time stamp for start of measuring. Format according to W3C\nXML dateTime with a resolution of 3 decimal places. All time stamps\nin UTC. E.g. 2009-10-02T14:34:34.341Z",
             "$ref" : "../../core/definitions.json#/timestamp"
           }
         }

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0205.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Traffic Counting: Number of vehicles\n\nThis status was introduced to improve performance in case traffic counting is done on all all detectors.",
+      "description" : "Traffic Counting: Number of vehicles.\nThis status was introduced to improve performance in case traffic counting is done on all all detectors.",
       "properties" : {
         "n" : {
           "enum" : [
@@ -25,7 +25,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Time stamp for start of measuring. Format according to W3C XML dateTime with a resolution of 3 decimal places. All time stamps in UTC. E.g. 2009-10-02T14:34:34.341Z",
+            "description" : "Time stamp for start of measuring. Format according to W3C.\nXML dateTime with a resolution of 3 decimal places. All time stamps\nin UTC. E.g. 2009-10-02T14:34:34.341Z",
             "$ref" : "../../core/definitions.json#/timestamp"
           }
         }
@@ -45,7 +45,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Number of vehicles\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)\n",
+            "description" : "Number of vehicles.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
             "type" : "string"
           }
         }

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0206.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Traffic Counting: Vehicle speed\n\nThis status was introduced to improve performance in case traffic counting is done on all all detectors.",
+      "description" : "Traffic Counting: Vehicle speed\nThis status was introduced to improve performance in case traffic counting is done on all all detectors.",
       "properties" : {
         "n" : {
           "enum" : [
@@ -25,7 +25,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Time stamp for start of measuring. Format according to W3C XML dateTime with a resolution of 3 decimal places. All time stamps in UTC. E.g. 2009-10-02T14:34:34.341Z",
+            "description" : "Time stamp for start of measuring. Format according to W3C\nXML dateTime with a resolution of 3 decimal places. All time stamps\nin UTC. E.g. 2009-10-02T14:34:34.341Z",
             "$ref" : "../../core/definitions.json#/timestamp"
           }
         }
@@ -45,7 +45,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Average speed in km/h (integer)\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)\n",
+            "description" : "Average speed in km/h (integer).\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
             "type" : "string"
           }
         }

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0207.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Traffic Counting: Occupancy\n\nThis status was introduced to improve performance in case traffic counting is done on all all detectors.",
+      "description" : "Traffic Counting: Occupancy.\nThis status was introduced to improve performance in case traffic counting is done on all all detectors.",
       "properties" : {
         "n" : {
           "enum" : [
@@ -25,7 +25,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Time stamp for start of measuring. Format according to W3C XML dateTime with a resolution of 3 decimal places. All time stamps in UTC. E.g. 2009-10-02T14:34:34.341Z",
+            "description" : "Time stamp for start of measuring. Format according to W3C\nXML dateTime with a resolution of 3 decimal places. All time stamps\nin UTC. E.g. 2009-10-02T14:34:34.341Z",
             "$ref" : "../../core/definitions.json#/timestamp"
           }
         }
@@ -45,7 +45,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Occupancy in percent (%) (0-100)\n- Value expressed as an integer with a range of 0-100.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)\n",
+            "description" : "Occupancy in percent (%) (0-100)\n- Value expressed as an integer with a range of 0-100.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
             "type" : "string"
           }
         }

data/schemas/tlc_1.0.15/schema/tlc/statuses/S0208.json

@@ -1,7 +1,7 @@
 {
   "allOf" : [
     {
-      "description" : "Traffic Counting: Number of vehicles of given classification\n\nThis status was introduced to improve performance in case traffic counting is done on all all detectors.",
+      "description" : "Traffic Counting: Number of vehicles of given classification.\nThis status was introduced to improve performance in case traffic counting is done on all all detectors.",
       "properties" : {
         "n" : {
           "enum" : [
@@ -33,7 +33,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Time stamp for start of measuring. Format according to W3C XML dateTime with a resolution of 3 decimal places. All time stamps in UTC. E.g. 2009-10-02T14:34:34.341Z",
+            "description" : "Time stamp for start of measuring. Format according to W3C\nXML dateTime with a resolution of 3 decimal places. All time stamps\nin UTC. E.g. 2009-10-02T14:34:34.341Z",
             "$ref" : "../../core/definitions.json#/timestamp"
           }
         }
@@ -53,7 +53,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Number of cars\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)\n",
+            "description" : "Number of cars.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
             "type" : "string"
           }
         }
@@ -73,7 +73,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Number of cars with trailers\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)\n",
+            "description" : "Number of cars with trailers.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
             "type" : "string"
           }
         }
@@ -93,7 +93,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Number of trucks\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)\n",
+            "description" : "Number of trucks.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
             "type" : "string"
           }
         }
@@ -113,7 +113,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Number of trucks with trailers\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)\n",
+            "description" : "Number of trucks with trailers.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
             "type" : "string"
           }
         }
@@ -133,7 +133,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Number of busses\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)\n",
+            "description" : "Number of busses.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
             "type" : "string"
           }
         }
@@ -153,7 +153,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Number of trams\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)\n",
+            "description" : "Number of trams.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
             "type" : "string"
           }
         }
@@ -173,7 +173,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Number of motor cycles\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)\n",
+            "description" : "Number of motor cycles.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
             "type" : "string"
           }
         }
@@ -193,7 +193,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Number of bicycles\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)\n",
+            "description" : "Number of bicycles.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
             "type" : "string"
           }
         }
@@ -213,7 +213,7 @@
       "then" : {
         "properties" : {
           "s" : {
-            "description" : "Number of pedestrians\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)\n",
+            "description" : "Number of pedestrians.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
             "type" : "string"
           }
         }