Ed Woodrick wrote: > As far as I know, there's only one basic convention where > you don't end up with a bunch of exceptions. > > CALLSIGN
Given that callsigns are unique ... but often they don't even give you a hint of anything to do with geographical location. W1 D-STAR repeater in Florida - or an area as expanse as some of the US callsign districts. > Even Pete's modified CLLI code has issues, CA is both a > state and a country. Every country has a Universal Postal Union two letter country code: http://www.upu.int/post_code/en/list_of_sites_by_country.html AR = Arkansas and Argentina AZ = Arizona and Azerbijan DE = Delaware and Germany o o o > ZIP Codes can come close, except that no one knows what 23324 is. Right. And not very useful for someone traveling ... as you may know something about a nearby large city but no idea what the ZIP (or even SCF, first three digits of the ZIP code) is. > Airport codes can sometime work, but we've got a couple > of repeaters whose closest airport is the same one. > And LZU or 1AB aren't necessarily readily recognizable as well. As someone who has traveled extensively for 30+ years ... I have a good handle on airport codes. But I agree: what good is some regional airport that has a code but is not recognizable or known? I do like a scheme that has some sort construct to it. And I think it should consider a wide scope, e.g., work in / for multiple countries. Of what's been posted so far ... I like the modified CLLI idea ... country, state, additional info. In the US - one of the things that I have always been frustrated with is the repeater directory. Repeaters are organised by regions ... but again - many times a visitor wouldn't know anything about what those areas are. Even worse - a lot of times repeaters in the same general area are listed in two separate places. Bob W1QA
