Comments (8)
User tag is statically assigned to an airframe in the basestation.sqb database. It is not read off air, hence there is no field in the Basestation format feed that could allow passing its value from dumphfdl to VRS.
from dumphfdl.
Is there any other field in VRS that could be used? Altitude or speed maybe?
from dumphfdl.
from dumphfdl.
Oh well, the numeric ground station ID would be better than nothing. I suppose I could print the systable.conf file and refer to it until I'd memorized the ID numbers and station names, or make a symlink to it on the desktop and open it in a text editor for reference.
from dumphfdl.
Ground station ID would be better than nothing, but freq-as-squawk is even better than ground station ID because it conveys more information, ground station ID included (indirectly). Once you print the systable, you'll have frequencies in front of your eyes as well. And when you reformat and sort it by frequency, looking up GS ID will be equally straightforward.
from dumphfdl.
That's not always true though. 8912 is used by Molokai, Hawaii and Riverhead, New York. 13276 is used by both of those plus San Fransisco California. 17919 is used by San Fransisco, Molokai, Riverhead, Barrow in Alaska and Agana in Guam. Knowing which ground stations I'm receiving messages from would give me an idea of how well my SDR and antenna setup are performing on any given day and time. Currently, I have no idea (in VRS) of knowing if I'm only receiving messages on 17919 from Guam which is relatively near to the Philippines or from New York or Alaska which is DX for me. The only way to find out is to stop dumphfdl then run it again without porting its output to VRS then watch the actual messages to see what ground stations they're coming from. Knowing both the frequency and the ground station would give me the clearest idea of how my station's performing and what the propagation's like from within the VRS web interface.
from dumphfdl.
Currently, I have no idea (in VRS) of knowing if I'm only receiving messages on 17919 from Guam which is relatively near to the Philippines or from New York or Alaska which is DX for me.
VRS won't tell you that. VRS plots plane positions - and these are carried in messages that are sent TO Guam, New York or Alaska, not received FROM them. If you want to know which stations' uplinks you receive, you have to log data to files constantly and inspect their contents - by eyeballing or crafting a script which summarizes them and reports the results.
Knowing both the frequency and the ground station would give me the clearest idea of how my station's performing and what the propagation's like from within the VRS web interface.
You can judge station performance from VRS GUI already - just by look at the distribution of the planes on the map. If it shows you an aircraft that is 15 thousand km away from your location, then it's a good DX regardless of which station that plane is currently talking to.
In short, what you want to do is already possible using existing feature set. The feature you are asking for won't help you in any way in this.
from dumphfdl.
"these are carried in messages that are sent TO Guam, New York or Alaska, not received FROM them."
Oh, I see. I was under the impression for some reason that the messages from aircraft were being relayed or rebroadcast by the ground stations, and it was those relayed GS messages that I was receiving. I didn't realize that I'm receiving messages directly from the aircraft themselves.
That being the case, I agree that my request makes no sense for helping me to glean the information that I was hoping for because the ground stations don't really matter when using dumphfdl along with VRS to track planes on a map, only for monitoring actual message content (i.e. seeing conversations between aircraft and ground stations if that's your interest.)
from dumphfdl.
Related Issues (17)
- freq offset for upconverter HOT 1
- feature - pse add grafana json HOT 1
- Pipe Input? HOT 5
- (Question) Grafana usage
- I/Q stream by TCP connection? HOT 2
- Macos - sudo make install linker error HOT 7
- Request: JSON output HOT 19
- The devel "force AGC to disabled" for SDRPlay breaks --gain-elements for Airspy Mini HOT 4
- Add --station-id option like dumpvdl2 HOT 2
- readStream failed: OVERFLOW, driver is uhd HOT 1
- output to readb ? HOT 2
- (Question) ZMQ input HOT 2
- Feature Request - BaseStation msgs without position option
- Problem compiling dumphfdl HOT 12
- fastddc_init function error while compiling HOT 1
- Incompatible with liquid-dsp 1.6.0 HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dumphfdl.