Don't complain about JSON. It's miles better than XML. In addition, Python has libraries that can read in that JSON file and convert it to Python data structures with ease. Since CHIRP is written in Python, JSON is a good fit.
On Thu, May 28, 2020 at 12:37 PM Michael Downey N2UN n2un@arrl.net wrote:
Hi Luke,
On Thu, May 28, 2020, at 04:24, Luke Bryan wrote:
Unlike other repeater books, the full database is accessible in a
readily readable format. Even the app is open source.
Thanks for sharing this project. A couple questions:
- I poked around your web site but couldn't find a published open data
license for the database. Can you point us to one? 2. Is the data available in any other formats other than the JSON feed? 3. Are there any plans to document the API endpoints and methods so people will know how to work with the data? (Or if already done, where can it be found?) 4. I also looked for the source code and associated open source license for the webapp but couldn't find it; only found a link to a different desktop-based application. Can you point us to the site's source code?
Very excited to watch the platform develop!
Additionally I hope for this repeater listing to be unlike other
repeater books in that it is newer, does not have old old repeaters that were there once years ago, after all the time you take to plug them in... they are not actually there :(
I note that your JSON feed of repeaters listed at the link above currently contains 2,383 entries. Apparently (taking their word for it) repeaterbook.com has around 40,000 repeaters and processes 18,000 records each year. Do you have a plan yet on getting data into the system?
73, Michael Downey N2UN _______________________________________________ chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to W5NNH at kemkerj3@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@intrepid.danplanet.com