Re: major libgweather Locations updates

[Dan Winship <danw gnome org>]

Andre Klapper wrote:
> #: ../data/Locations.xml.in.h:40
> msgid "Abilene Regional Airport"
> #: ../data/Locations.xml.in.h:50
> msgid "Abumusa Island, Abumusa Airport"
> #: ../data/Locations.xml.in.h:769
> msgid "Babelthuap Island, Babelthuap /Koror Airport"
> #: ../data/Locations.xml.in.h:2301
> msgid "Cincinnati Municipal Airport, Lunken Field"
> 
> Is there a concept behind the different versions of listing an airport
> (commas, no commas) that I don't get? ;-)

The closest there is to a rule is that if there's a comma, then
everything on the same side of the comma as the word "Airport" is part
of the airport name, and anything not on the same side probably isn't.

Here's the situation: our primary source of weather station information
is just the most godawful database in the world, with absolutely no
consistency in naming conventions, ridiculous misspellings and typos,
out-of-date names for airports (and even for cities in some places), etc.

You can see my efforts to improve the situation here:
http://svn.gnome.org/viewvc/libgweather/trunk/data/station-fixups.pl?view=markup

In the case of the specific examples you gave, the names of the airports
themselves are "Abilene Regional Airport", "Abumusa Airport",
"Babelthuap/Koror Airport" (the weird spacing around the "/" is a bug),
and "Cincinnati Municipal Airport". The middle two are preceded by the
name of the island where they are, which maybe I should be stripping out
because the information probably isn't that useful. The last one is
suffixed with the name of a specific area within the airport, which I
should *definitely* be stripping out...

(Note that these strings are only used to differentiate different
weather stations within a city. Eg, someone living in Cincinnati can
pick either "Cincinnati Municipal Airport" or "Cincinnati / Northern
Kentucky International Airport" depending on which is closer to them,
and get better weather reports that way.)

-- Dan