EDDN: approachsettlement/1 - Sometimes Latitude is missing

[Athanasius]

Apparently the Horizons game client might still have a bug where relogging whilst docked at a Planetary Port will sometimes cause an ApproachSettlement event without the Lat/Long co-ordinates.

Certainly the Live EDDN Gateway is now logging things like:

2022-02-17 19:04:34,786 - ERROR - Gateway:274: Failed Validation "[<ValidationError: "'Latitude' is a required property">]" (332, "E:D Market Connector [Windows]", "5.3.0", "https://eddn.edcd.io/schemas/approachsettlement/1", "-")

We should actually check that our outgoing messages have all the required fields.

[Athanasius]

Arrival (in Horizons):

{ "timestamp":"2022-02-18T14:59:25Z", "event":"ApproachSettlement", "Name":"Mallory Settlement", "MarketID":3537520640, "SystemAddress":1109989017963, "BodyID":64, "BodyName":"Ousey Rock", "Latitude":-72.336609, "Longitude":34.379406 }

After a full game client restart, once more into Horizons:

{ "timestamp":"2022-02-18T15:01:41Z", "event":"ApproachSettlement", "Name":"Mallory Settlement", "MarketID":3537520640, "SystemAddress":1109989017963, "BodyID":64, "BodyName":"Ousey Rock" }

[Athanasius]

https://github.com/EDCD/EDMarketConnector/releases/tag/Release%2F5.3.1 has addressed this, auto-updates being enabled Soon[tm].