|
rpm-build |
ca2b01 |
The format of Locations.xml[.in] is something like this:
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
<gweather format="1.0">
|
|
rpm-build |
ca2b01 |
<region>
|
|
rpm-build |
ca2b01 |
<_name>North America</_name>
|
|
rpm-build |
ca2b01 |
<country>
|
|
rpm-build |
ca2b01 |
<_name>United States</_name>
|
|
rpm-build |
ca2b01 |
<iso-code>US</iso-code>
|
|
rpm-build |
ca2b01 |
<state>
|
|
rpm-build |
ca2b01 |
<_name>Alabama</_name>
|
|
rpm-build |
ca2b01 |
<tz-hint>America/Chicago</tz-hint>
|
|
rpm-build |
ca2b01 |
<location>
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
<_name>Alabaster</_name>
|
|
rpm-build |
ca2b01 |
KEET
|
|
rpm-build |
ca2b01 |
<zone>ALZ019</zone>
|
|
rpm-build |
ca2b01 |
<radar>bhm</radar>
|
|
rpm-build |
ca2b01 |
<coordinates>33-10-42N 086-46-54W</coordinates>
|
|
rpm-build |
ca2b01 |
</location>
|
|
rpm-build |
ca2b01 |
<city>
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
<_name>Mobile</_name>
|
|
rpm-build |
ca2b01 |
<location>
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
<_name>Mobile Downtown Airport</_name>
|
|
rpm-build |
ca2b01 |
KBFM
|
|
rpm-build |
ca2b01 |
<zone>ALZ061</zone>
|
|
rpm-build |
ca2b01 |
<radar>bix</radar>
|
|
rpm-build |
ca2b01 |
<coordinates>30-36-50N 088-03-48W</coordinates>
|
|
rpm-build |
ca2b01 |
</location>
|
|
rpm-build |
ca2b01 |
</city>
|
|
rpm-build |
ca2b01 |
...
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
Most of the data in the file appears inside <location> entries.
|
|
rpm-build |
ca2b01 |
However, various larger geographic divisions exist to make things
|
|
rpm-build |
ca2b01 |
easier for both users and maintainers.
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
At the top level are <region>s. These mostly correspond to continents,
|
|
rpm-build |
ca2b01 |
but not entirely. They are arbitrary, and could be changed in the
|
|
rpm-build |
ca2b01 |
future if we wanted.
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
Each <region> is divided into <country>s. Every internationally-
|
|
rpm-build |
ca2b01 |
recognized country for which at least one <location> is defined should
|
|
rpm-build |
ca2b01 |
have its own <country>. For the most part, "dependencies",
|
|
rpm-build |
ca2b01 |
"territories", "protectorates" and the like are listed as <location>s
|
|
rpm-build |
ca2b01 |
within their ruling country if they are in the same <region>, but
|
|
rpm-build |
ca2b01 |
separately if they are in a different <region>. This is not followed
|
|
rpm-build |
ca2b01 |
100% consistently.
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
Every <country> must have an <iso-code> tag giving its ISO 3166-1
|
|
rpm-build |
ca2b01 |
alpha-2 code. Sub-country <location>s can also specify their own
|
|
rpm-build |
ca2b01 |
<iso-code> if they have one.
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
A <country> MAY specify a <tz-hint>, giving the default time zone name
|
|
rpm-build |
ca2b01 |
for the country. Countries that only have one timezone (or where the
|
|
rpm-build |
ca2b01 |
majority of the country is covered by a single timezone) should list
|
|
rpm-build |
ca2b01 |
it at the <country> level. Countries with multiple timezones and no
|
|
rpm-build |
ca2b01 |
obvious "default" should not list anything here. (See README.timezones
|
|
rpm-build |
ca2b01 |
for more information about timezones in Locations.xml.)
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
A <country> can contain <city>s and <location>s directly, or can be
|
|
rpm-build |
ca2b01 |
split into <state>s which contain <city>s and <location>s. The name
|
|
rpm-build |
ca2b01 |
"state" comes from the US states, but it can be used to represent any
|
|
rpm-build |
ca2b01 |
sort of well-defined sub-country region that has a name which will be
|
|
rpm-build |
ca2b01 |
familiar to local users. A <state> may specify a <tz-hint> which will
|
|
rpm-build |
ca2b01 |
override the <country>'s <tz-hint> for <location>s within the state.
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
<city> is an optional element used to group together multiple
|
|
rpm-build |
ca2b01 |
<location>s within the same city.
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
Finally, a <location> represents a location for which weather data can
|
|
rpm-build |
ca2b01 |
be retrieved. Its fields are:
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
<_name> - required, the name of the location
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
<iso-code> - optional, the ISO 3166 code of the location, if not
|
|
rpm-build |
ca2b01 |
the same as its parent <country>
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
<tz-hint> - optional, the timezone of the location, if not the
|
|
rpm-build |
ca2b01 |
same as its parent <state> or <country>
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
- required, the METAR code identifying this location
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
<zone> - optional, secondary weather source information:
|
|
rpm-build |
ca2b01 |
US: the NOAA IWIN zone
|
|
rpm-build |
ca2b01 |
UK: the Met Office region name, prefixed with ":"
|
|
rpm-build |
ca2b01 |
AU: the BOM forecast name, prefixed with "@"
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
<radar> - optional, the Weather.com radar map name for the
|
|
rpm-build |
ca2b01 |
location (North America only)
|
|
rpm-build |
ca2b01 |
|
|
rpm-build |
ca2b01 |
<coordinates> - optional, the latitude and longitude of the
|
|
rpm-build |
ca2b01 |
location, as "[-]ddd.dddddd [-]ddd.dddddd"
|
|
rpm-build |
ca2b01 |
Positive values are North and East respectively,
|
|
rpm-build |
ca2b01 |
negative values are South and West.
|