added additional JSON export encoded as GeoJSON #79
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
devbender
pushed a commit
to devbender/dump1090
that referenced
this pull request
Dec 1, 2020
Forward MLAT traffic to Stratux JSON output, marked with IsMlat:true in JSON
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
and outputted to /geodata.json in the internal HTTP server.
http://geojson.org
My slight ulterior motive is that this would allow easier input to my alternative web front end which I'm developing although I believe GeoJSON is a natural fit to this output and may negate the need for the existing data.json output if the javascript was altered to support this.
https://github.com/Surfrdan/GeoJsonScope