Originally posted by Mike
View Post
and on-request hold / release for analysis purposes should be implemented by all ADS-B monitoring device / software manufcturers. Hobbyist ADS-B monitoring
is a bit gray area in many countries. This kind of accident analysis support could help making hobbyist ADS-B monitoring activity more accepted to the authorities.
Some development ideas:
-support development of the receiver base (other than already supperted FR24/Radarcape) to provide GPS-timestamped data
-encourage local buffering of the full feed to the internal memory maximum of the receiver platform
-mechanism for FR24 to request a hold and dump of all stored data frames of a spesific HEX (this might be a type of request that would require an OK by the
receiver owner for the data to be delivered, the release request could contain a reasoning for the request)
Spesifically related to Radarcape..as the hardware base is very similar / identical to the FR24 receiver, this type of full feed buffering and HEX-based release request
should be quite easy to implement. Maybe something to consider together with FR24 and Radarcape?
I really would like to see crowdsourced ADS-B monitoring to be universally accepted from legislation point of view. Internet aviation enthusiast community has already proven to provide valuable data. There are also other areas where crowdsourced sensor networks could provide added value: weather monitoring and thunderstorm detection are good examples.
Comment