From a857bc1fae2171679d22c440ca672a876c23f6ae Mon Sep 17 00:00:00 2001 From: Athanasius Date: Mon, 31 Oct 2022 08:49:33 +0000 Subject: [PATCH 1/2] docs/Developers: Compression needs `Content-Encoding` header ... not `Content-Type`. --- docs/Developers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/Developers.md b/docs/Developers.md index b77499e..c9ff0b2 100644 --- a/docs/Developers.md +++ b/docs/Developers.md @@ -128,8 +128,8 @@ compress this body then you MUST set a `Content-Type` header of `applicaton/json`. You *MAY* use gzip compression on the body of the message, but it is not -required. If you do compress the body then you **MUST* send a `Content-Type` -header of `gzip` instead of `application/json`. +required. If you do compress the body then you **MUST* send a +`Content-Encoding` header of `gzip`. **Due to issues when messages are compressed, form-encoded data is NO LONGER SUPPORTED as of 2022-06-16.** From 41f9713f096fa77dd546d502cfb6f1a2047a0767 Mon Sep 17 00:00:00 2001 From: clonedArtie <37144216+clonedArtie@users.noreply.github.com> Date: Thu, 19 Oct 2023 12:21:30 +0200 Subject: [PATCH 2/2] Adding latest changes to live branch. (#216) * "Typo" in headline Since this is the Readme for FSSBodySignals the Headline wrongly contains FSSAllBodiesFound. * Update README.md to remove mention of EDDB EDDB is now defunct and its links are dead. * added update 17 schema changes, also protected from additional properties approachsettlement gets station data fsssignaldiscovered gets signaltype * additionalproperties in correct place --------- Co-authored-by: Lord Asrothear Co-authored-by: Rob Co-authored-by: Avraham Adler Co-authored-by: Gareth Harper --- README.md | 11 ++------ schemas/approachsettlement-v1.0.json | 37 +++++++++++++++++++++++++++ schemas/fssbodysignals-README.md | 2 +- schemas/fsssignaldiscovered-v1.0.json | 2 ++ 4 files changed, 42 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index 02c97df..3e88a40 100644 --- a/README.md +++ b/README.md @@ -65,14 +65,11 @@ then you're probably looking for one of the sites listed below. NB: These are listed in name-alphabetical order and no particular ranking or endorsement is intended. -- [EDDB](https://eddb.io/) - a website which tries to act as a database of all - the data available in the game. In general EDDB tries to help finding - stuff which players are looking for. - [EDSM](https://www.edsm.net/) - originally focused on being a 'Star Map', but has since expanded its functionality. Of particular interest to in-game explorers. -- [Inara](https://inara.cz/) - a popular alternative to EDDB, with a lot of - its own unique functionality. +- [Inara](https://inara.cz/) - a popular alternative to the now defunct EDDB, + with a lot of its own unique functionality. - [Spansh](https://www.spansh.co.uk/plotter) - originally this had one tool, a 'Neutron Star' route plotter, but has since expanded into offering many other route plotting tools and general data searching. @@ -91,10 +88,6 @@ use: large, but is currently the only source of an "all known bodies" dump. Pay attention to the 'Generated' "time ago" column. -- [EDDB dumps](https://eddb.io/api) represent a snapshot of the data EDDB uses. - NB: There has been no "bodies" data for years now, EDDB itself stopped - updating or adding to this. - - [EDSM nightly dumps](https://www.edsm.net/en/nightly-dumps) represent a snapshot of the data EDSM uses. NB: there's only a "last 7 days" bodies dump as the full data proved too large to dump in a timely manner. diff --git a/schemas/approachsettlement-v1.0.json b/schemas/approachsettlement-v1.0.json index 1af5052..81007d5 100644 --- a/schemas/approachsettlement-v1.0.json +++ b/schemas/approachsettlement-v1.0.json @@ -70,6 +70,43 @@ "maxItems" : 3, "description" : "Must be added by the sender" }, + "StationGovernment": { + "type" : "string" + }, + "StationEconomies": { + "type" : "array", + "items" : { + "type" : "object", + "additionalProperties" : false, + "properties": { + "Name": { + "type" : "string" + }, + "Proportion": { + "type" : "number" + } + }, + "patternProperties" : { + "_Localised$" : { "$ref" : "#/definitions/disallowed" } + } + } + }, + "StationFaction": { + "type" : "object", + "additionalProperties" : false, + "properties": { + "Name": { + "type" : "string" + } + } + }, + "StationServices": { + "type" : "array", + "items" : { "type": "string" } + }, + "StationEconomy": { + "type" : "string" + }, "SystemAddress": { "type" : "integer" }, diff --git a/schemas/fssbodysignals-README.md b/schemas/fssbodysignals-README.md index 7582514..422355b 100644 --- a/schemas/fssbodysignals-README.md +++ b/schemas/fssbodysignals-README.md @@ -1,4 +1,4 @@ -# EDDN FSSAllBodiesFound Schema +# EDDN FSSBodySignals Schema ## Introduction Here we document how to take data from an ED `FSSBodySignals` Journal diff --git a/schemas/fsssignaldiscovered-v1.0.json b/schemas/fsssignaldiscovered-v1.0.json index 3f7b171..d551031 100644 --- a/schemas/fsssignaldiscovered-v1.0.json +++ b/schemas/fsssignaldiscovered-v1.0.json @@ -69,6 +69,7 @@ "minItems": 1, "items": { "type": "object", + "additionalProperties" : false, "required": ["timestamp", "SignalName"], "description": "Single FSSSignalDiscovered event", "properties": { @@ -77,6 +78,7 @@ "format" : "date-time" }, "SignalName": { "type": "string" }, + "SignalType": { "type": "string" }, "IsStation": { "type": "boolean" }, "USSType": { "type": "string",