[chirp_devel] Support for other sites than RepeaterBook
Hello there all!
First of all - thanks for all developers for this software. Finally I have something free and working to manage my FT-857D. Thanks!
So, why I am here? I'm author and developer of online repeaters database - przemienniki.net. It's primary polish site, but with help of community and moderators we also collect data for repeaters in surrounding countries. With permission of RSGB we have also British repeaters in our site. Access to przemienniki.net is free for everyone and data export is allowed in few more or less usable formats (native XML, Excel file, GPX for Garmin devices, Google's KML and XML for iPhone RPTs).
Since I had lot of requests to allow export data to radio programming software from website I've started to looking what software is available on market and found out about Chirp.
And when I saw that Chirp can do online database query for US repeater sites...
So, is there any, even very slight chance, to get someday version of Chirp that will support my site[1]? :-) Of course, I can provide any kind of interface that will be needed to implement that feature.
Kind regards, Lucas, SQ5LWN.
[1] Without me learning Python ;)
On Tue, Feb 26, 2013 at 3:58 PM, Łukasz Jarosław Mozer baseciq@gmail.com wrote:
So, is there any, even very slight chance, to get someday version of Chirp that will support my site[1]? :-) Of course, I can provide any kind of interface that will be needed to implement that feature.
RepeaterBook supports export of Chirp-compatible CSV files. I recommend you study Chirp's CSV format and add an export option to your site for this format. This will allow users of your site to put the data into Chirp without writing a single line of Python :-)
More info about Chirp CSV here: http://chirp.danplanet.com/projects/chirp/wiki/CSV_HowTo
Tom KD7LXL
That would be easy way for me, and thanks, I'm aware of csv import ability in Chirp and this kind of export will be implemented soon (tomorrow before lunchtime in CEST).
But direct import, query, etc. from Chirp? That would be something easier for end users. Can You imagine finding csv file saved by those evil browser in some random directory among 2TB of other temporary files?
Anyway, python is already on my "to learn" list, just after learning c and learning java ;-)
Cheers
But direct import, query, etc. from Chirp? That would be something easier for end users. Can You imagine finding csv file saved by those evil browser in some random directory among 2TB of other temporary files?
Adding a direct query is not a problem. If you could expose a JSON representation of the query options for dynamically building the UI, perhaps, and then a way to get a CHIRP CSV file based on those query paramters, that'd be perfect. Sound okay?
Witam!
W liście datowanym 27 lutego 2013 (03:30:14) napisano:
But direct import, query, etc. from Chirp? That would be something easier for end users. Can You imagine finding csv file saved by those evil browser in some random directory among 2TB of other temporary files?
Adding a direct query is not a problem. If you could expose a JSON representation of the query options for dynamically building the UI, perhaps, and then a way to get a CHIRP CSV file based on those query paramters, that'd be perfect. Sound okay?
Please, look at this:
http://przemienniki.net/export/chirp.csv
Available URL params:
country (optional) - one of 'by', 'cz', 'de', 'lt', 'pl', 'sk', 'uk', if not set, all available countries will be dumped into file mode (optional) - 'fm' or 'dv', if not set, both dv and fm repeaters will be dumped onlyworking (optional) - if set (no matter to what), only working and confirmed repeaters will be exported
latitude, longitude (optional) - cooridinates of origin point to filter repeaters by distance range - maximum distance from origin point in kilometers
Example:
http://przemienniki.net/export/chirp.csv?country=pl&mode=fm&onlywork...
That's for start. There's no problem to implement more bells and whistles to this URL ;)
http://przemienniki.net/export/chirp.csv
Available URL params:
country (optional) - one of 'by', 'cz', 'de', 'lt', 'pl', 'sk', 'uk', if not set, all available countries will be dumped into file mode (optional) - 'fm' or 'dv', if not set, both dv and fm repeaters will be dumped onlyworking (optional) - if set (no matter to what), only working and confirmed repeaters will be exported
latitude, longitude (optional) - cooridinates of origin point to filter repeaters by distance range - maximum distance from origin point in kilometers
Okay, this seems reasonable, although it would be nice to have the options be discoverable by some web service at some point.
Please open a feature request issue on the site and put this information inside and I'll take a look when I get a chance.
Thanks!
Witam!
W liście datowanym 3 marca 2013 (17:28:39) napisano:
Okay, this seems reasonable, although it would be nice to have the options be discoverable by some web service at some point.
Specs in XML file? That would be nice indeed.
Please open a feature request issue on the site and put this information inside and I'll take a look when I get a chance.
By the way - is CSV is required? I see that .chirp file is XML, so what is easier to parse or easier to implement - XML or CSV?
Issue #645 has been submited. Also support for band filtering has been added to this URL.
Specs in XML file? That would be nice indeed.
JSON would be my preference, but XML would work.
By the way - is CSV is required? I see that .chirp file is XML, so what is easier to parse or easier to implement - XML or CSV?
CSV gets far more use and attention, so yes, CSV please :)
Issue #645 has been submited. Also support for band filtering has been added to this URL.
Thanks!
Witam!
W liście datowanym 3 marca 2013 (21:33:32) napisano:
Specs in XML file? That would be nice indeed.
JSON would be my preference, but XML would work.
Maybe something like... this?
http://przemienniki.net/chirp-discovery.json
;)
Witam!
W liście datowanym 3 marca 2013 (21:33:32) napisano:
Specs in XML file? That would be nice indeed.
JSON would be my preference, but XML would work.
I've sent previous response from wrong e-mail address - sorry.
So - again - http://przemienniki.net/chirp-discovery.json - something like this would be enough? ;)
By the way - is CSV is required? I see that .chirp file is XML, so what is easier to parse or easier to implement - XML or CSV?
CSV gets far more use and attention, so yes, CSV please :)
Issue #645 has been submited. Also support for band filtering has been added to this URL.
Thanks!
Works flawless.
Missing "any band" and "any country". But works flawless!
participants (4)
-
Dan Smith -
Tom Hayward -
Łukasz Jarosław Mozer -
Łukasz Jarosław Mozer