node-red-contrib-tak-registration 0.7.0 → 0.7.1

package/README.md

@@ -30,29 +30,29 @@ As it registers to the gateway it should be possible for other team members to s
 
 ### Standard COT event
 
-If the `msg.payload` is an XML string it will be passed directly though.
+If the `msg.payload` is an XML string it will be passed directly though. It should be a correctly formatted CoT XML message of course.
 
-### Simple GeoChat messages
+### Sending marker position...
+
+To create or update a simple marker send a msg with the following property
+
+ - **payload** - *object* - a "standard" node-red worldmap format - IE a msg.payload containing `name, lat, lon, SIDC or cottype or aistype, (alt), (speed), (bearing), (layer), (remarks)`, where `SIDC` is the standard mil 2525C code, eg SFGPU, `cottype` is the CoT type, eg a-f-g-u, or `aistype` is the AIS ship type number, eg 80 for a tanker. The `layer` will get turned into a hashtag which can then be selected on/off in the TAK app layers control, and any `remarks` will get added to the CoT remarks field.
+
+ ### Simple GeoChat messages
 
 requires a `msg` containing the following properties
 
-- **sendTo** - *string|array* - can either be an individual TAK callsign, a comma separted list of callsigns, an array of callsigns, or **broadcast** to send to all users.
+- **sendTo** - *string | array* - can either be an individual TAK callsign, a comma separted list of callsigns, an array of callsigns, or **broadcast** to send to all users.
 - **payload** - *string* - the text of the message to send.
 
 ### Sending data packages...
 
 requires a `msg` containing the following properties
 
- - **sendTo** - *string|array* - can either be an individual TAK callsign, an array of callsigns, or **broadcast** to send to all users, or **public** to just upload the package to the TAK server.
+ - **sendTo** - *string | array* - can either be an individual TAK callsign, an array of callsigns, or **broadcast** to send to all users, or **public** to just upload the package to the TAK server.
  - **topic** - *string* - the overall package name - IE what you want it to be called on the TAK device (keep it short).
  - **attachments** - *array of objects* - each object must contain at least a **filename** (string) and **content** a buffer of the file/data, for example `[{filename:"foo.kml", content: <buffer of the file>}]`
 
-### Sending marker position...
-
-To create or update a simple marker send a msg with the following property
-
- - **payload** - *object* - a "standard" node-red worldmap format msg.payload containing `name, lat, lon, SIDC or cottype or aistype, (alt), (speed), (bearing), (layer), (remarks)`, where `SIDC` is the standard mil 2525C code, eg SFGPU, `cottype` is the CoT type, eg a-f-g-u, or `aistype` is the AIS ship type number, eg 80 for a tanker. The `layer` will get turned into a hashtag which can then be selected on/off in the TAK app layers control, and any `remarks` will get added to the CoT remarks field.
-
 ### Sending drawing layer...
 
 The node will also accept drawing type messages incoming from the drawing layer of the
@@ -63,7 +63,7 @@ and convert them to CoT objects for display. To do this configure a *worldmap-in
 
 To update the location of the gateway dynamically the node can accept a payload
 
- - **payload** - *string|object* - Either an NMEA string starting `$GPGGA` (for example from a locally attached serial GPS device) - or an object containing `lat` and `lon` and optional `alt` properties (**but no name** property).
+ - **payload** - *string | object* - Either an NMEA string starting `$GPGGA` (for example from a locally attached serial GPS device) - or an object containing only `lat` and `lon` and optional `alt` properties (**but no name** property).
 
 ### Details
 
@@ -73,6 +73,7 @@ This should work almost directly with messages received from an email-in node fo
 
 This node can accept input direct from a TCP request node, configured to point to the TAK server tcp address and port (usually 8087 or 8089), set to return strings, *keep connection open* mode, and split on "&lt;/event&gt;". This can be same TCP node as used by the TAK-registration node above.
 
-It will produce a well formatted JSON object containing the event.
+It will produce a well formatted JSON object containing the event. It is returned as **msg.payload.event**
 
-It can also accept input from a UDP node configured to listen to *multicast* on address 239.2.3.1. port 6969. The JSON object produced contain similar information but formatted/organised differently.
+It can also accept input from a UDP node configured to listen to *multicast* on address 239.2.3.1. port 6969. The JSON object produced contain similar information but formatted/organised differently.
+It is returned as **msg.payload.cotEvent**

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "node-red-contrib-tak-registration",
-    "version": "0.7.0",
+    "version": "0.7.1",
     "description": "A Node-RED node to register to TAK and to help wrap files as datapackages to send to TAK",
     "dependencies": {
         "@turf/turf": "6.5.0",

package/tak-ingest.js

@@ -9,7 +9,7 @@ module.exports = function(RED) {
     "use strict";
     const fastXmlOptions = {
         attributeNamePrefix: "",
-        attrNodeName: "attr",
+        // attrNodeName: "attr",
         ignoreAttributes: false,
     };