dma-ais / aistrack Goto Github PK

The AisTrack server is currently not persisting the AIS overview, which it provides. The result is, that it will take several hours after a server restart to rebuild the AIS overview in areas (e.g. Arctic) where AIS messages are primarily received from satellites. Some sort of persistence is needed in order to reload the AIS overview after a server restart.

If a vessel or basestation provides a timestamp in the future when reporting position. That message will remain as 'most recent' position. Example

"target" : {
"mmsi" : 999167000,
"country" : "NL",
"lastReport" : "2016-08-06T17:01:49.568Z",
"created" : "2016-06-19T00:00:03.282Z",
"vesselStatic" : {
"mmsi" : 999167000,
"received" : "2016-06-19T00:00:03.282Z",
"sourceTimestamp" : "2016-08-06T17:01:49.568Z",
"created" : "2016-06-19T00:00:03.282Z",
"name" : "OOOOOODAM",

The list of returned AIS tracks currently contains tracks/targets with incorrect MMSI numbers consisting of only 5-6 digits. This could be caused by buggy AIS messages. We should investigate if this is the case and if so filter out these messages. If problem lies somewhere else, then correct the problem there.

A request to /ais-track/tracks/ will return a number of AisTargets, which seems to consist of wrong data. Some of them are specifically positioned in the middle og Greenland. Most of them are positioned close to a horizontal line a long 69 50.000N and comes from AIS sources 811 (HELCOM) and 812 (NorthSea). It seems that more and more a pilling up along 69 50.000N.

If requesting details by /ais-track/tracks?mmsi=, then it seems that lastReport (timestamp) is often more than 10 days old.

These AIS erroneous data should some be evicted from the cache.