[aprssig] Parsing error Stations
Phillip zl2tze at yahoo.com.auSun Jan 20 19:47:08 UTC 2008
- Previous message: [aprssig] APRS - discriminator direct on FT-2800M ?
- Next message: [aprssig] Follow-up to my previous posting re W0APR
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Below is a list of stations taken from FINDU that have Parsing Errors From the top these have the most errors in 6 hours 200 plus to the bottom who 1 or 2 Why does my station's information not show up on findU? If you are a member of the Citizen Weather program, the most common problem is an incorrectly entered latitude and longitude. Some programs do not check the number enetered for validity, but the system has a very specific format it requires, so check that the information is entered correctly. For other problems, you should get support from the person or company that produces the program you are using. The process of reports getting to findU via amateur radio and APRS is complex. First, your station transmits the data, likely it must travel through one or more digipeaters before reaching an internet gateway, which forwards it to a hub in the APRS Internet System, and then finally to findU com. Problems can occur anywhere along this path, though by far the most common are in the early stages...an individual's RF system has a problem, their path is not set correctly to be digipeated by their local RF network, or their local IGate is down or misconfigured. From the internet there is absolutely no way I can diagnose these problems. Your best bet is to seek out a local APRS user that can listen for you on RF, and try to figure out what is wrong. If you are writting your own software, or manually entered an APRS string into a hardware or software configuration file, you may have misformatted the data. findU tends to follow strict interpretation of the APRS standard, and some errors may be displayable in some client programs but not findU, a typical example is an incorrect number of digits in a lat/lon. You can always check findU's parsing error page to see if findU is detecting an error. http://www.findu.com/cgi-bin/errors.cgi G7NFK KD5JNV-15 KP4FAK N2NJH-3 K3BZG-3 CW9393 KNYPLEAS6 C2698 CW3009 CW9622 W9TMW CW9335 KC7GGQ-4 CW9293 CW9333 SV4FHR-2 SV4IKL-2 VE7WBI-10 N2AYK-1 WX3SMD-8 W0APR-3 I3VZB-3 DB0OSN CW8923 aprsdXXX SV1UY-3 KA2QYE-10 F1SZZ-5 N0AYK-10 aprsdTIF W4OT-3 CW6769 W3YNI-1 K7EK-5 WA2UMX-2 CW4083 DK5EC-6 F6BGK-9 N3LZX-9 W7WRO-3 K3ARL-1 KB7PSD DJ9XB PU1WAX-10 AG4KM SBBA2 KQ1L VA2PHL-10 LW4DEM-8 KE4KWR-1 VK8NSB-7 WA0RTO LW1DXP-1 LW1DXP-7 N8IYX-4 STUFFS VK4RMM-3 KB2WYA SR5NWA K41UEB AC0GJ hub-wdx SV2BNL-12 K4SRC-2 KA5GMG-1 F6KKR-2 W3CE-3 APRSDOCKU CW8821 LU4HAW-10 VE3GKS-14 CW9669 KY4K-10 VE7ROM-15 KD6RSQ VY1RHJ K4TQL-7 VE6DDD VR2JJ-0 VY1RMB 5B8BE-11 WX9GRB-3 N5RIG HB9EBV-4 VY1RFH JA1LJF-3 CT0XUL I1YLM-2 K4YWE-2 AC6SZ-10 M0SCI-2 K4OKE-3 EB1D-15 SV2HIS DB0KUN W4LJM SV4BHA-11 DK8IOF-2 SV4BHA-12 W0MXW-1 KF6RAL-9 KC5EZZ-3 N7ZEV-4 SV2DCD-11 N0LWV CW8770 CW8046 VK2RAG-1 KB7DZR WB5WAJ AK5Z VA2HAR-1 KC7DMF-7 PA1PAS VY1RDC OZ4DIG-2 J42VAF KI4GNI N8OND-1 SZ7SER IR3BZ RIMFORSA VE9DKS-9 CW4207 KB8VEE-3 WA0SOP-15 FM1HN K4FI SD7RA-9 SR7WXP KC6URU KC8QNO PY1EU-10 J47VAE VE3OIC AI5TX-1 W7KMV-9 KE1FO-9 SV2BNL-10 IK2RJI -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.tapr.org/pipermail/aprssig/attachments/20080121/23f081ef/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/gif Size: 41190 bytes Desc: not available Url : http://www.tapr.org/pipermail/aprssig/attachments/20080121/23f081ef/attachment.gif
- Previous message: [aprssig] APRS - discriminator direct on FT-2800M ?
- Next message: [aprssig] Follow-up to my previous posting re W0APR
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
