But there all some limitations.
1) We can deny, but You do anything You want anyway, so we politely ask, don't use this data to make other websites or HTML-based apps. We are open for cooperation, but in that case, we would like to know what You are trying to do. Maybe together we could do something more and share some experience?
2) We expect that Your credit us in Your app/site/whatever. Fullscreen logo would be nice, but it isn't necessary ;-)
At this moment, we provide following formats:
Native XML formatDesigned for our website purposes, described below. This format supports URL paramaters.
RT Systems ADMSCSV file for RT Systems ADMS - tested with ADMS-4B for Yaesu FT-857/897. This format supports URL paramaters.
ExcelPropably most human-readable. Generated on demand, always with fresh data. Unfortunately, available at this moment only in polish language. This format supports URL paramaters.
Garmin-checked GPXGPX file suitable for Garmin (and propably other) devices, tested by Paweł SQ9PPT. Like Excel file, currently only in polish. This format supports URL paramaters.
KML for Google Maps and Google EarthXML file readable both by Google Maps website, and by Google Earth. Like always, polish descriptions inside at this moment. This format supports URL paramaters.
Chirp's CSV fileCSV file compatible with Chirp. This format supports URL paramaters.
XML for Repeater RadarThis is usable by Repeater Radar for Android.
Timestamp of last update in databaseThis is for those, who doesn't want to fetch all data and treat our bandwidth with respect. Optionally, we can add format param to the URL, which is described in PHP manual. Also values "unix" and "mysql" are supported.
Some of files described above accepts parameters in URL:
- setlang - language (pl or en) - for data that can be traslated (like statuses, modes, column headers in Excel, etc.). If You download file by Your browser, You will get data in language that You are using on website. If You are using some other downloading tools, or download data for automatic parse in Your application, You will get english modes, activation types by default.
- source - for RXF and GPX you can set it to all to fetch all data, or empty to fetch only repeaters that we are collect on our own, for other formats skipping this param will cause export data of all repeaters, setting this to "local" will give You only our data.
- country - 2 letter country code to fetch (one of: pl, uk, de, cz, sk, by, lt), skip this param or set it to all to fetch repeaters from all countries.
- band - band (2m, 70cm, and so on).
- mode - repeater mode (fm, dstar, atv, echolink).
- onlyworking - set this to any value You want, to get only working and confirmed repeaters.
- updatedafter - used to incremental data fetch, accepts any format readable by strftime().
- latitude, longitude, range - optional we can search only for repeaters withing specified range from origin point.
For most params You can type more than one search criteria separating values using coma:
http://przemienniki.net/export/rxf.xml?country=cz,sk&source=all - XML file with repeaters from Czech Republic and Slovakia.
http://przemienniki.net/export/chirp.csv?latitude=52.231957&longitude=21.006129&range=20&band=2m,70cm - Chirp-readable CSV with 2m and 70cm band repeaters, located up to 20 km from Warsaw's city center.
Native XML format
Root of XML file is contained in <rxf> ... </rxf>. In addition to fields describing basic data like last update date or geneation date, it contains two sets of data: dictionary and repeaters list. Dictionary contains list of atributes that can be assigned to every repeaters in fields status, band, mode and activation type. Each of attribute value have unique in its type value that contains only single bit set to 1. This allows to describe few attributes in single value. Fore example, repeater that is both FM and DSTAR repeater has value 36 (32+4) in status field. Contrary to appearances, the search through the values from the programmer's point of view is very easy and involves performing operations "logical and" on the values. Of course, in addition to such a complex record, each repeater has also normal descriptive and human-readable value.
Example repeater record from XML file looks like this:
<repeater> <qra>SR5TEST</qra> <id>8996912</id> <hash>fa7929c5bb73997ed0fe252b8c23e3d9</hash> <created>2012-03-15 13:02:42</created> <updated>2012-03-15 13:02:42</updated> <statusInt>1</statusInt> <status>WORKING</status> <licenseExpiryDate>2017-01-01</licenseExpiryDate> <modeInt>4</modeInt> <mode>FM</mode> <bandInt>4096</bandInt> <band>2M</band> <qrg type="rx">145.100000</qrg> <qrg type="tx">145.700000</qrg> <country>pl</country> <qth><![CDATA[Warszawa PKiN]]></qth> <location> <locator>KO02MF</locator> <latitude>52.231716</latitude> <longitude>21.006031</longitude> <altitudeOverSea>117</altitudeOverSea> <altitudeOverGround>80</altitudeOverGround> </location> <activationInt>16672</activationInt> <activation>1750</activation> <activation>CTCSS</activation> <activation>DTMF</activation> <ctcss type="rx">131.8</ctcss> <ctcss type="tx">146.2</ctcss> <dtmf type="rx">*</dtmf> <trxPower>10.00</trxPower> <operator>SP1ABC</operator> <operator>SP5DEF</operator> <echolink>3183277</echolink> <remarks><![CDATA[Przemiennik klubu SP5XYZ]]></remarks> <link>http://przemienniki.net/przemienniki/2m/SR5TEST</link> <link>http://www.sp5xyz.pl/przemiennik_sr5test</link> <source>http://przemienniki.net</source> <feedback>http://przemienniki.net/zglos/8996912</feedback> </repeater>
And here's some legend to that example:
- qra - repeater's QRA.
- id - our database unique ID.
- hash - record hash calculated in a manner known only to us. We are using this field while importing to verify that the imported data has changed. If You don't trust date fields, You can verify whether the record has been changed.
- created, updated - appropriate date and time when the drive has been added to the database and when it was modified.
- statusInt, status - status in integer format and as human-readable text.
- licenseExpiryDate - repeater's license expiry date (if available, this field is optional).
- modeInt, mode - repeater mode as integer format and as human-readable text.
- bandInt, band - repeater band as integer followed by list of those bands as a text.
- qrgs - list of repeater's frequencies, each frequency has attribute "type" which is set to "rx" or "tx". Crossband repeaters that works between two bands has four frequency entries: two for RX for both bands, and two for TX.
- country - two letter country code.
- qth - repeater's QTH.
- location - list of repeater's locations. Each location entry contains QTH locator, latitude and longitude (both optional), altitude over sea level and over ground level (also optional). At this momement, each of repeater has only one location, but multisite repeaters will be implemented on our website in future.
- activationInt, activation - repeater activation mode as integer format and as human-readable list of activation types.
- ctcss, dcs, dtmf (optional) - DCS codes, CTCSS frequencies and DTMF digits used to open repeater (additional atribute "type" equal "rx") or that is transmited by repeater ("type" equal "tx", if course <dtmf type="tx"> never occur).
- trxPower - transmitter power (optional).
- operators - repeater's license keepers/operators (optional).
- echolink - Echolink node ID (optional).
- remarks - remarks and notes (optional).
- link - URLs to sites regarding this repeater, first will always point out to przemienniki.net.
- source - URL to source site of this repeater.
- feedback - URL to report update (optional, available only for our repeaters, not imported).
We strongly advise to verify file version in header and in case of change immediatly visit this site again ;-)