Live data from Hacker News

ADS-B Exposed

adsb.exposed

71–80 of 87 posts

Re: ADS-B Exposed

#71
Highlighting an area, I see in the sidebar: Time: 2022-02-01 00:09:20.136 — 2023-12-07 22:46:41.480. Would be nice if it had newer data.

Re: ADS-B Exposed

#72
post #9

Very cool project. Little bit of trivia regarding the "strange hole near Mexico City"[1] from the README. This is a 12-kilometer exclusion zone around the highly active Popocatépetl volcano to prevent incidents stemming from volcanic activity. [1] https://adsb.exposed/?zoom=9&lat=19.1139&lng=261.3813&query=...

I wish there was an Aztec goddess of tea drinking called Pollyputthekettleon.

Not that the Aztecs had tea drinking, if only the Chinese treasure ships had connected up across the Pacific…

Re: ADS-B Exposed

#73
post #19

We have a an ADS-B receiver at Summit Station in Greenland which we use to track airplanes that produce RFI we see in our experiment. I've considered sharing data (since nobody else seems to have data there) but the feeding instructions always scare me (run this script that downloads a bunch of random crap as sudo... no thanks). Please just give me a cURL command I can run... (perhaps some services have that, I haven…

It's good to be careful. A popular ADS-B network used to distribute a raspberry pi image that let the maintainers ssh into your machine whenever they wanted.

Re: ADS-B Exposed

#75
post #9

Very cool project. Little bit of trivia regarding the "strange hole near Mexico City"[1] from the README. This is a 12-kilometer exclusion zone around the highly active Popocatépetl volcano to prevent incidents stemming from volcanic activity. [1] https://adsb.exposed/?zoom=9&lat=19.1139&lng=261.3813&query=...

Can’t tell if it’s the same spot or not

https://www.reddit.com/r/StrangeEarth/comments/1e476ob/weath...

Re: ADS-B Exposed

#76
post #33

Earlier quoted context omitted.

Yeah I definitely don't want to run an opaque container either. We're already collecting and storing the data... I am happy to throw the data over via a udp socket or http request, but I don't want random software that we don't control running...

I had the same concerns awhile back and ending up running a slightly modified version of https://github.com/wiedehopf/mlat-client -- not quite as simple as an http push, but much simpler than a containerized feed client.

That's only MLAT though and won't feed the ADS-B data.

Re: ADS-B Exposed

#77
post #33

Earlier quoted context omitted.

You can get containerized feeders for services like fr24 (e.g. liggy1/fr24feed) but that may not meet your requirements since it's really intended to handle everything from the sdr to the API, not siphon off data you are collecting some other way and then feed it.

Yeah I definitely don't want to run an opaque container either. We're already collecting and storing the data... I am happy to throw the data over via a udp socket or http request, but I don't want random software that we don't control running...

If you're not comfortable running my readsb (fork of dump1090) which is the feed client used by live / lol / fi and some other sites, then you can probably just send them data using socat.

Most of them will have port 30004 open for their ingest domain, usually feed.domain.com. Thus you'd hook up socat to 127.0.0.1:30005 (i assume you run dump1090 or readsb locally as a decoder). And make socat send that to feed.adsb.lol:30004 and/or feed.airplanes.live:30004

If you're in a remote location, you don't need to worry about mlat-client as MLAT requires at least 4 receivers that receive common aircraft.

Re: ADS-B Exposed

#78
post #33

Earlier quoted context omitted.

Yeah I definitely don't want to run an opaque container either. We're already collecting and storing the data... I am happy to throw the data over via a udp socket or http request, but I don't want random software that we don't control running...

If you're not comfortable running my readsb (fork of dump1090) which is the feed client used by live / lol / fi and some other sites, then you can probably just send them data using socat. Most of them will have port 30004 open for their ingest domain, usually feed.domain.com. Thus you'd hook up socat to 127.0.0.1:30005 (i assume you run dump1090 or readsb locally as a decoder). And make socat send that to feed.adsb.…

[deleted]

Re: ADS-B Exposed

#79
post #19

We have a an ADS-B receiver at Summit Station in Greenland which we use to track airplanes that produce RFI we see in our experiment. I've considered sharing data (since nobody else seems to have data there) but the feeding instructions always scare me (run this script that downloads a bunch of random crap as sudo... no thanks). Please just give me a cURL command I can run... (perhaps some services have that, I haven…

It's good to be careful. A popular ADS-B network used to distribute a raspberry pi image that let the maintainers ssh into your machine whenever they wanted.

FlightAware?

Re: ADS-B Exposed

#80
post #33

Earlier quoted context omitted.

Yeah I definitely don't want to run an opaque container either. We're already collecting and storing the data... I am happy to throw the data over via a udp socket or http request, but I don't want random software that we don't control running...

If you're not comfortable running my readsb (fork of dump1090) which is the feed client used by live / lol / fi and some other sites, then you can probably just send them data using socat. Most of them will have port 30004 open for their ingest domain, usually feed.domain.com. Thus you'd hook up socat to 127.0.0.1:30005 (i assume you run dump1090 or readsb locally as a decoder). And make socat send that to feed.adsb.…

Thanks! After doing some more digging I suspected something like this was the simplest solution! Thanks for confirming.
Post reply on HN