Add lat/long and other corrections

This commit is contained in:
Jeremy Rimpo 2025-04-19 21:50:23 -05:00
parent 651add8a4c
commit a3724363c8
No known key found for this signature in database
GPG Key ID: D72B900810CF2AD6
2 changed files with 17 additions and 2 deletions

View File

@ -82,3 +82,9 @@ release, Update 7, plus one patch).
It will disappear again when they fly back above that altitude, or jump
away.
5. If Status.json does **not** have `BodyName` then clear `status_body_name`.
#### Latitude / Longitude
While latitude and longitude are not reported with the event data, this event
necessitates being on a planet surface. Pulling the current coordinates from
the `Status.json` should be sufficient to populate the data. The `Status.json`
granularity is quite accurate when on-foot.

View File

@ -33,7 +33,7 @@
"type" : "object",
"description" : "Contains all properties from the listed events in the client's journal minus the Localised strings and the properties marked below as 'disallowed'",
"additionalProperties" : false,
"required" : [ "timestamp", "event", "ScanType", "Genus", "Species", "SystemAddress", "BodyID", "BodyName"],
"required" : [ "timestamp", "event", "ScanType", "Genus", "Species", "Latitude", "Longitude", "SystemAddress", "BodyID", "BodyName"],
"properties" : {
"timestamp": {
"type" : "string",
@ -88,7 +88,16 @@
"type" : "integer"
},
"BodyName": {
"type" : "string"
"type" : "string",
"description" : "Must be added by the sender to corroborate BodyID"
},
"Latitude": {
"type" : "number",
"description" : "Must be added by the sender, generally from Status.json"
},
"Longitude": {
"type" : "number",
"description" : "Must be added by the sender, generally from Status.json"
}
},
"patternProperties": {