Nabble - geonames

Australian suburb population data

2009-12-21T15:25:52Z

http://www.abs.gov.au/AUSSTATS/abs@.nsf/mf/2033.0.55.001 is available under a CC-BY licence.

You can see what it looks like with http://www.suburbantrends.com.au/

Is this worth looking at to sync up with geonames / freebase?

You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@....
To unsubscribe from this group, send email to geonames+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/geonames?hl=en.

Re: typo in french exports

2009-12-05T00:43:55Z

Thanks. It will be fixed with the next dump.

marc

thogau wrote:

> Hi,
> just to inform you that in current france postal codes export, the
> "Bretagne" region is spelled in english "Brittany".
> HTH
>
> --
>
> You received this message because you are subscribed to the Google Groups "GeoNames" group.
> To post to this group, send email to geonames@....
> To unsubscribe from this group, send email to geonames+unsubscribe@....
> For more options, visit this group at http://groups.google.com/group/geonames?hl=en.
>
>
>

--

You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@....
To unsubscribe from this group, send email to geonames+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/geonames?hl=en.

typo in french exports

2009-12-03T02:25:02Z

Hi,
just to inform you that in current france postal codes export, the
"Bretagne" region is spelled in english "Brittany".
HTH

--

You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@....
To unsubscribe from this group, send email to geonames+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/geonames?hl=en.

Re: Error in geoid 2891541

2009-12-01T11:14:16Z

Hi Dennis

It was a typo. There is a village of this name exactly 1 degree to the
west of the location. I have moved it there.

Best

Marc

Dennis Keßler wrote:

> Hi Dan,
>
> Sorry for my mistake :-) It was indeed in Czechia.
> Personally I have not found any references to this location so far, only
> to a hill, located in Germany.
>
> However, it seems that the data was corrected and now pointing to a
> Bavarian village near the Czech and Austrian border.
>
> - Dennis
>
> --
>
> You received this message because you are subscribed to the Google
> Groups "GeoNames" group.
> To post to this group, send email to geonames@....
> To unsubscribe from this group, send email to
> geonames+unsubscribe@....
> For more options, visit this group at
> http://groups.google.com/group/geonames?hl=en.

Re: Error in geoid 2891541

2009-12-01T10:46:09Z

Hi Dan,

Sorry for my mistake :-) It was indeed in Czechia.

Personally I have not found any references to this location so far, only to a hill, located in Germany.

However, it seems that the data was corrected and now pointing to a Bavarian village near the Czech and Austrian border.

- Dennis

Re: Error in geoid 2891541

2009-12-01T07:47:38Z

Hi Dennis,

How did you came to the conclusion that it is within the Polish borders?
The coordinates you gave are in Czechia. I do not know Kernberg either
but theoretically, a German placename could occur in the area. It is the
border area to Austria where there used to live German minority, and
numerous German villages used to be along the border (but disappeared
after WW2).

Best,
Dan

Dennis napsal(a):

> Hello,
> I´m currently playing around with the geonames db and found a
> inccorect entry:
> 2891541 is the record for a german populated place, called "Kernberg",
> which the geonames db locates at "48.75,14.7333333" within the Polish
> borders. Unfortunately, I don`t know where the correct location is.
>
> - Dennis
>
> --
>
> You received this message because you are subscribed to the Google Groups "GeoNames" group.
> To post to this group, send email to geonames@....
> To unsubscribe from this group, send email to geonames+unsubscribe@....
> For more options, visit this group at http://groups.google.com/group/geonames?hl=en.
>
>

--
RNDr. Daniel Zeman, Ph.D.
ÚFAL MFF, Univerzita Karlova, Praha
http://ufal.mff.cuni.cz/~zeman/

--

You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@....
To unsubscribe from this group, send email to geonames+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/geonames?hl=en.

Error in geoid 2891541

2009-12-01T06:53:36Z

Hello,
I´m currently playing around with the geonames db and found a
inccorect entry:
2891541 is the record for a german populated place, called "Kernberg",
which the geonames db locates at "48.75,14.7333333" within the Polish
borders. Unfortunately, I don`t know where the correct location is.

- Dennis

--

You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@....
To unsubscribe from this group, send email to geonames+unsubscribe@....
For more options, visit this group at http://groups.google.com/group/geonames?hl=en.

Re: Missing METAR codes

2009-11-22T08:23:07Z

Kelly

Please feel free to add them if you think they are missing.
I have checked a couple of them. "Mildura Airport" was already in the
database but was missing the icao code. I have added the code. For some
other I also have the impression the exist but the code is often
different for only one letter and I am not sure whether it is a typo or
whether really both codes exist.

Best

Marc

Kelly Jones wrote:

> I compared NOAA's METAR list http://weather.noaa.gov/data/nsd_cccc.txt
> to geonames' and the below are missing.
>
> Could someone add them? I'd do it myself, but I have no information of
> these locations above/beyond what's in the nsd_cccc.txt file
>
> EGTH;--;---;Hatfeild Private ;;United Kingdom;6;51-46N;000-15W;;;77;;
> EQYG;--;---;NSA Souda Bay;;Greece;6;35-32N;024-09E;;;146;;
> EQYN;--;---;Naples, Navsuppact;;Italy;6;40-53N;014-17E;;;91;;
> EQYR;--;---;Rota, Naval Station;;Spain;6;36-39N;006-20W;;;26;;
> EQYS;--;---;Sigonella, NAS;;Italy;6;37-24N;014-55E;;;25;;
> FLLC;67;666;Lusaka City
> Airport;;Zambia;1;14-27S;028-28E;15-25S;028-19E;1280;1280;
> KBAN;--;---;MCMWTC BRIDGEPORT, CA;CA;;;38-21N;119-31W;;;2057;;
> KCNB;--;---;Myers Field Airport;MN;United States;4;44-43N;96-16W;;;364;;
> KDLF;--;---;Laughlin, Laughlin Air Force Base Auxiliary
> Airfield;TX;United States;4;29-07-00N;100-28-00W;;;294;294;
> KEUF;--;---;WEEDON FIELD AIRPORT;AL;UNITED STATES;4;31-57-05N;85-07-55W;;;87;;
> KFHU;72;273;Fort Huachuca, Libby AAF Ft Huachuca;AZ;United
> States;4;46-98N;110-20W;;;1438;;
> KGSN;--;---;SAIPAN INTERNATIONAL AIRPORT ;;NORTHERN MARIANA
> ISLAND;;15-07N;145-44E;;;66;;
> KICR;--;---;WINNER REGIONAL AIRPORT ;SD;UNITED STATES;4;43-23N;99-51W;;;619;;
> KNEN;--;---;NOLF WHITEHOUSE FIELD, FL;FL;UNITED STATES;4;30-21N;81-52W;;;30;;
> KPRN;--;---;GREENVILLE AIRPORT;AL;UNITED STATES;4;31-47N;085-57W;;;137;;
> KQTA;--;---;ATSUGI, JAPAN NAVAL AIR;;JAPAN;2;35-27N;139-27E;;;62;;
> KSPS;72;351;WICHITA FALLS SHEPPARD AFB;TX;United
> States;4;33-59N;98-30W;33-58-25N;098-30-07W;309;308;
> KYUK;--;---;YUKON RANGE R-2205;AK;UNITED STATES;4;64-43N;146-31W;;;536;;
> LPFU;08;521;Funchal / S.
> Catarina;;Portugal;1;32-41N;016-46W;32-41N;016-46W;58;49;P
> MMCS;--;---;Ciudad Juarez International ;;Mexico;4;31-38N;106-26W;;;1171;;
> MMML;--;---;Mexicali International Airport ;;Mexico;4;32-38N;117-00W;;;22;;
> PAFW;--;---;Farewell Lake;AK;United States;4;62-32N;153-37W;;;323;;
> PAHS;--;---;Huslia, Huslia Airport;AK;United States;4;65-42N;156-23W;;;55;;
> PHMO;--;---;KAUNAKAKAI MOLOKAI AIRPORT;HI;UNITED STATES;4;21-09N;157-06W;;;138;;
> RPMP;98;444;Legaspi;;Philippines;5;13-08N;123-44E;13-08N;123-44E;16;17;P
> RPMR;98;536;Romblon;;Philippines;5;12-35N;122-16E;;;46;47;P
> RPMS;98;428;Sangley Point;;Philippines;5;14-30N;120-55E;14-30N;120-55E;3;4;
> TTPT;78;962;Crown Point Airport, Tobago;;Trinidad and
> Tobago;4;11-09N;060-50W;11-09N;060-50W;3;6;P
> VBRM;48;042;Mandalay;;Myanmar;2;21-59N;096-06E;21-59N;096-06E;74;76;
> VIUD;42;542;Udaipur Dabok;;India;2;24-37N;073-53E;24-37N;073-53E;509;514;
> WRRR;97;230;Denpasar /
> Ngurah-Rai;;Indonesia;5;08-45S;115-10E;08-45S;115-10E;1;1;P
> YBAM;94;568;Amberley Aerodrome;;Australia;5;27-38S;152-43E;;;27;31;P
> YMMI;94;693;Mildura Airport;;Australia;5;34-13S;142-05E;34-14S;142-05E;50;52;P
> YPLC;94;674;Leigh Creek Airport;;Australia;5;30-35S;138-25E;;;261;259;
>

Missing METAR codes

2009-11-13T19:28:20Z

I compared NOAA's METAR list http://weather.noaa.gov/data/nsd_cccc.txt
to geonames' and the below are missing.

Could someone add them? I'd do it myself, but I have no information of
these locations above/beyond what's in the nsd_cccc.txt file

EGTH;--;---;Hatfeild Private ;;United Kingdom;6;51-46N;000-15W;;;77;;
EQYG;--;---;NSA Souda Bay;;Greece;6;35-32N;024-09E;;;146;;
EQYN;--;---;Naples, Navsuppact;;Italy;6;40-53N;014-17E;;;91;;
EQYR;--;---;Rota, Naval Station;;Spain;6;36-39N;006-20W;;;26;;
EQYS;--;---;Sigonella, NAS;;Italy;6;37-24N;014-55E;;;25;;
FLLC;67;666;Lusaka City
Airport;;Zambia;1;14-27S;028-28E;15-25S;028-19E;1280;1280;
KBAN;--;---;MCMWTC BRIDGEPORT, CA;CA;;;38-21N;119-31W;;;2057;;
KCNB;--;---;Myers Field Airport;MN;United States;4;44-43N;96-16W;;;364;;
KDLF;--;---;Laughlin, Laughlin Air Force Base Auxiliary
Airfield;TX;United States;4;29-07-00N;100-28-00W;;;294;294;
KEUF;--;---;WEEDON FIELD AIRPORT;AL;UNITED STATES;4;31-57-05N;85-07-55W;;;87;;
KFHU;72;273;Fort Huachuca, Libby AAF Ft Huachuca;AZ;United
States;4;46-98N;110-20W;;;1438;;
KGSN;--;---;SAIPAN INTERNATIONAL AIRPORT ;;NORTHERN MARIANA
ISLAND;;15-07N;145-44E;;;66;;
KICR;--;---;WINNER REGIONAL AIRPORT ;SD;UNITED STATES;4;43-23N;99-51W;;;619;;
KNEN;--;---;NOLF WHITEHOUSE FIELD, FL;FL;UNITED STATES;4;30-21N;81-52W;;;30;;
KPRN;--;---;GREENVILLE AIRPORT;AL;UNITED STATES;4;31-47N;085-57W;;;137;;
KQTA;--;---;ATSUGI, JAPAN NAVAL AIR;;JAPAN;2;35-27N;139-27E;;;62;;
KSPS;72;351;WICHITA FALLS SHEPPARD AFB;TX;United
States;4;33-59N;98-30W;33-58-25N;098-30-07W;309;308;
KYUK;--;---;YUKON RANGE R-2205;AK;UNITED STATES;4;64-43N;146-31W;;;536;;
LPFU;08;521;Funchal / S.
Catarina;;Portugal;1;32-41N;016-46W;32-41N;016-46W;58;49;P
MMCS;--;---;Ciudad Juarez International ;;Mexico;4;31-38N;106-26W;;;1171;;
MMML;--;---;Mexicali International Airport ;;Mexico;4;32-38N;117-00W;;;22;;
PAFW;--;---;Farewell Lake;AK;United States;4;62-32N;153-37W;;;323;;
PAHS;--;---;Huslia, Huslia Airport;AK;United States;4;65-42N;156-23W;;;55;;
PHMO;--;---;KAUNAKAKAI MOLOKAI AIRPORT;HI;UNITED STATES;4;21-09N;157-06W;;;138;;
RPMP;98;444;Legaspi;;Philippines;5;13-08N;123-44E;13-08N;123-44E;16;17;P
RPMR;98;536;Romblon;;Philippines;5;12-35N;122-16E;;;46;47;P
RPMS;98;428;Sangley Point;;Philippines;5;14-30N;120-55E;14-30N;120-55E;3;4;
TTPT;78;962;Crown Point Airport, Tobago;;Trinidad and
Tobago;4;11-09N;060-50W;11-09N;060-50W;3;6;P
VBRM;48;042;Mandalay;;Myanmar;2;21-59N;096-06E;21-59N;096-06E;74;76;
VIUD;42;542;Udaipur Dabok;;India;2;24-37N;073-53E;24-37N;073-53E;509;514;
WRRR;97;230;Denpasar /
Ngurah-Rai;;Indonesia;5;08-45S;115-10E;08-45S;115-10E;1;1;P
YBAM;94;568;Amberley Aerodrome;;Australia;5;27-38S;152-43E;;;27;31;P
YMMI;94;693;Mildura Airport;;Australia;5;34-13S;142-05E;34-14S;142-05E;50;52;P
YPLC;94;674;Leigh Creek Airport;;Australia;5;30-35S;138-25E;;;261;259;

--
We're just a Bunch Of Regular Guys, a collective group that's trying
to understand and assimilate technology. We feel that resistance to
new ideas and technology is unwise and ultimately futile.

--

You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@....
For more options, visit this group at http://groups.google.com/group/geonames?hl=.

Re: non-asciinames in cities1000.txt

2009-11-12T03:25:35Z

On Nov 11, 10:10 pm, Andrew Dalke <da...@...> wrote:

>
> In any case, the "I have no idea" means that I don't know what goes
> in the ASCII field for that name. The others I could handle by eye,
> picking the closest looking ASCII character or by doing:
> # Get the raw UTF-8 bytes
> name = field[ascii_name_column]
> # Convert to Unicode
> name = unicode(name, "utf8")
> # Normalize in a way that you'll have to consult
> # the Unicode references for, then convert to ASCII.
> # short version: split out diacritics into composed characters
> # then remove the composing characters.
> name = unicodedata.normalize("NFKD", name).encode("ASCII", "ignore")
>

I would moreover transliterate the string:
http://cldr.unicode.org/index/cldr-spec/transliteration-guidelines
[There are also some demos on the ICU project site. For instance, for
the transliteration: http://demo.icu-project.org/icu-bin/translit (and
to check the language identifier: http://unicode.org/cldr/utility/languageid.jsp)]

When using the "Any->Latin" transliterator, it yields: "kạf ạljạʿ" .
You can then go on normalising the string.

Hope it helps

Denis

--

You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@....
For more options, visit this group at http://groups.google.com/group/geonames?hl=.

Re: non-asciinames in cities1000.txt

2009-11-11T13:10:23Z

Hi Denis!

On Nov 11, 2009, at 9:31 PM, Denis Arnaud wrote:
> On Nov 8, 10:36 pm, Andrew Dalke <andrewda...@...> wrote:
>> Those should be
>> 6943439 ... I have no idea ...
>
> I guess that record 6943439 is encoded in UTF8. If so, it would
> correspond to:
> كاف الجاع

Since I have a terminal with UTF-8 encoding, and since that output
comes direct from my Python program, this also works.

>>> print '\xd9\x83\xd8\xa7\xd9\x81 \xd8\xa7\xd9\x84\xd8\xac\xd8\xa7
\xd8\xb9'
كاف الجاع
>>>

I was about to do

unicode('\xd9\x83\xd8\xa7\xd9\x81 \xd8\xa7\xd9\x84\xd8\xac\xd8\xa7\xd8
\xb9', "utf").encode("utf8")

when I realized that was rather pointless.

In any case, the "I have no idea" means that I don't know what goes
in the ASCII field for that name. The others I could handle by eye,
picking the closest looking ASCII character or by doing:
# Get the raw UTF-8 bytes
name = field[ascii_name_column]
# Convert to Unicode
name = unicode(name, "utf8")
# Normalize in a way that you'll have to consult
# the Unicode references for, then convert to ASCII.
# short version: split out diacritics into composed characters
# then remove the composing characters.
name = unicodedata.normalize("NFKD", name).encode("ASCII",
"ignore")

but with pure Arabic this ended up as " ", which is the space in the
middle.

Andrew
dalke@...

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: non-asciinames in cities1000.txt

2009-11-11T12:31:18Z

Hello,

On Nov 8, 10:36 pm, Andrew Dalke <andrewda...@...> wrote:
> Scanning through cities1000.txt I found 5 cities which contained non-
> ASCII characters in that field:
>
> 6943439 '\xd9\x83\xd8\xa7\xd9\x81 \xd8\xa7\xd9\x84\xd8\xac\xd8\xa7\xd8\xb9'
>
> Those should be
> 6943439 ... I have no idea ...

I guess that record 6943439 is encoded in UTF8. If so, it would
correspond to:
كاف الجاع

In case you want to decode it yourself, you can use the following
small Python program: http://codepad.org/QZGa9xan
(for those interested, the C++ is also easy to write)

Best Regards

Denis

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Earth, TX, TX

2009-11-10T17:08:09Z

I think commas in names should be avoided. It causes trouble when trying
to identify the different parts of a string like "Earth, Texas, United
States". Each of the parts separated by comma should have a separate entry
in the database. And in the case of "Earth, TX", when automatically adding
the admin1 name, you get "Earth, TX, Texas". Texas is the admininistrative
division, so it doesn't belong in the name field.

In the database there are 18,604 names containing a comma, and most of
these (if not all) should have been rewritten in my opinion. Take for
instance "Armstrong, Mount", "Argyle, City of", "Annaburg, Stadt" and
"Barkell, Lake". These should be "Mount Armstrong", "City of Argyle",
"Annaburg" and "Lake Barkell". Sometimes it is also a good solution to put
what is behind the comma in parenthesis instead.

In my implementation of Geonames, I simply filter out all names that
contain a comma. :)

--
Best regards,
Even Scharning
Netburn Web Solutions
Time.is - exact time for any time zone and any location in the world
(except those with a comma in their name)

On Sat, 31 Oct 2009 04:44:09 -0700 (PDT), Andrew Dalke
<andrewdalke@...> wrote:

> On Oct 31, 10:35 am, Marc Wick <m...@...> wrote:
>> If I understand you correctly then you take umbrage at the 'TX' that
>> somebody has added to indicate it is a city in Texas and not to be
>> confused with the planet.
>
> Yes. The name of the place is "Earth" and not "Earth, TX". And I think
> the logic is suspect because "Mars", in Pennsylvania , is not written
> as "Mars, PA" and "Jupiter" in Florida is not written as "Jupiter,
> FL".
>
>> I have added an alternate name 'Earth', with the flags 'preferred' and
>> 'short'. I hope this makes everybody happy.
>
> I don't yet have enough experience with this data set to know enough
> to be be happy or sad, but I'm not going to complain. ;)
>
> Cheers!
>
> -- Andrew Dalke <dalke@...>
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

non-asciinames in cities1000.txt

2009-11-08T13:36:17Z

The documentation at
http://download.geonames.org/export/dump/readme.txt

says
> The main 'geoname' table has the following fields :
...
> asciiname : name of geographical point in plain ascii characters, varchar(200)

I need the ASCII name because I want to match the official name of
"Doña Ana, NM" and the often-used name of "Dona Ana, NM" and figured
that using this field was best, because "Dona Ana" does not exist as
an alternate name.

(I could be wrong. The geonames server lets me search for "Dona Ana"
in the US and it finds Doña Ana, so I figured using asciiname was part
of the correct search strategy.)

Scanning through cities1000.txt I found 5 cities which contained non-
ASCII characters in that field:

106909 '\xe1\xb8\x90uba'
6943439 '\xd9\x83\xd8\xa7\xd9\x81 \xd8\xa7\xd9\x84\xd8\xac
\xd8\xa7\xd8\xb9'
1567723 'Song C\xe1\xba\xa7u'
1586288 'C\xe1\xba\xa7n Gi\xe1\xbb\x9d'
1586296 'C\xe1\xba\xa7n Duoc'

Those should be

106909 likely Duba (see http://en.wikipedia.org/wiki/Duba )
6943439 ... I have no idea ...
1567723 Song Cau
1586288 Can Gio
1586296 Can Giuoc

I tried to edit the asciiname field by going to a record, but I saw no
way to do that. I assume it is a derived field and not something which
is externally editable.

Best regards,

-- Andrew Dalke <dalke@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: unexpected aliases in alternateNames.txt

2009-11-08T12:52:01Z

On Nov 8, 7:32 am, Marc Wick <m...@...> wrote:
> please feel free to correct it.

Plus, I can't change the "Beijin - Pekin" entry, which is two
different transliterations of the same name, because

The record you want to edit is locked for updates for userlevel1

Cheers,

-- Andrew Dalke <dalke@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: unexpected aliases in alternateNames.txt

2009-11-08T11:40:06Z

On Nov 8, 5:13 pm, Marc Wick <m...@...> wrote:
> It will need someone who speaks Galego to determine which one of the two
> names is Galego and which one an other language.

That is of course your prerogative. I will point out that the relevant
Wikipedia site (which is where I assume the names came from, since
they are also hyphenated) imply that the first name is Galician and
the second name is the 'foreign' name. For a clear example:

http://gl.wikipedia.org/wiki/Agrixento
> Agrixento - Agrigento
> Agrixento, Agrigento en italiano. Cidade capital da provincia de
> Agrixento, Sicilia, Italia.. 55.000 habitantes.

Which is quite easily interpreted, from its similarities to Spanish
and other Romance languages, as "Agrixento, Agrigento in Italian.
Capital city of the province of Argixento, Sicily, Italy. 55,000
inhabitants."

Similarly, http://gl.wikipedia.org/wiki/Bélxica
> Bélxica - België
> O Reino de Bélxica (Koninkrijk België en neerlandés, Royaume de
> Belgique en francés e Königreich Belgien en alemán) é un país
> da Europa Noroccidental

Which would be "The Kingdom of Bélxica (Koninkrijk België in Dutch,
Royaume de Belgique in French and Königreich Belgien in German) is a
country in Northwest Europe."

http://gl.wikipedia.org/wiki/Tur%C3%ADn
> Turín - Torino
> Turín é unha comuna italiana, capital da rexión de Piemonte cunha poboación de 900.608 persoas

Translated: "Turín is a Italian municipality, capital of the Piemote
region with a population of 900,608 people."

I had looked over the 300+ name pairs and everyone one of them looks
like it has Galacian first and the foreign name second.

I assumed this was an import error from whatever the primary data
source was, and I also assumed that that conversion was not done by
someone who knows the language.

Again, feel free to defer this transformation until someone who knows
Galacian spots the error and is willing to report it, or that someone
like me doesn't mind changing 300+ values by hand.. I did not know
that that was a requirement.

Best regards,

-- Andrew Dalke <dalke@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: comma in name in alternatenames

2009-11-08T11:17:18Z

On Nov 8, 5:03 pm, Marc Wick <m...@...> wrote:
> You shouldn't parse anything that is not designed to be parsed. (or
> parse it at your own risk).

I understand that. I wrote the above to point out that there's nothing
which describes which fields are designed to be parsed and which are
not.

Specifically, http://download.geonames.org/export/dump/readme.txt
says:

Remark : the field 'alternatenames' in the table 'geoname' is a
short version of the 'alternatenames' table. You probably don't
need both. If you don't need to know the language of a name
variant,
the field 'alternatenames' will be sufficient. If you need to know
the language of a name variant, then you will need to load the
table
'alternatenames' and you can drop the column in the geoname table.

I did not need to know the language of the name variant, so I thought
I could use this field.

I also did not realize that some of the names are machine generated
transliterations from other languages. I do not see that documented
anywhere, so I assumes there was some other data source involved.

Cheers,

-- Andrew Dalke <dalke@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: escaped unicode characters as aliases

2009-11-08T11:10:40Z

On Nov 8, 4:51 pm, Marc Wick <m...@...> wrote:
> It is an html encoding and it will therefore display correctly on an
> html page.

But it shouldn't, unless the source data is supposed to be HTML
encoded - which it isn't.

Take for example geonameid 6619831, which is for the Victoria & Albert
Museum. Go to that page and view source and you'll see an error in the
HTML:

<meta name="description" content="Victoria & Albert Museum England
Kensington and Chelsea, United Kingdom, museum" />

This is a bug. The '&' should be & and you can see that the title
field is properly escaped:

<title>Victoria & Albert Museum, United Kingdom</title>

Potentially this opens the geonames server up to various sorts of well-
known attacks.

I tried to test this by adding a place named '"> testing' at the
stadium in Boden. That gives me the error message

error while saving:
Cannot parse ' country:SE names:" names:testing fcode:STDM( fc:S )':
Lexical error at line 1, column 54. Encountered: after : "\"
names:testing fcode:STDM( fc:S )"

That implies that special characters aren't properly being escaped
before doing into the database. If I use two double quotes, it worked,
that is

""> testing

I'm disconcerted about that. Perhaps there is also a possible
injection attack on the database? I also can't figure out where the
record went so I can delete it. (Or more properly, use the correct
name.) Please feel free to delete the record if it was created, or for
that matter wipe my account if this was too improper.

> All that needed to be done was to click on the edit link and save again.
> I did it for you.

Thanks. But that shouldn't have been the right solution if data
conversion is correctly done all the way through, which is why I
didn't consider doing it.

-- Andrew Dalke <dalke@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: unexpected aliases in alternateNames.txt

2009-11-08T08:13:08Z

It will need someone who speaks Galego to determine which one of the two
names is Galego and which one an other language.

Marc

Andrew Dalke wrote:

> On Nov 8, 7:32 am, Marc Wick <m...@...> wrote:
>> please feel free to correct it.
>
> There are 305 such names which are obviously wrong for the Galician
> language and can be fixed with something like
>
> perl -pe 's/(^\d+\t\d+\tgl\t)([^-]+ - )(.*$)/$1$3/'
>
> plus another three which I spotted by hand when scanning for a "-" in
> the alternate name.
>
> Shall I send in a diff against alternateNames.txt? While I now know
> about the web based interface to make corrections manually, I don't
> really want to do 300+ edits by hand. If each takes 30 seconds that's
> over 2.5 hours of work.
>
> -- Andrew Dalke <dalke@...>
>
> >
>

Re: comma in name in alternatenames

2009-11-08T08:03:05Z

The field is present because users have asked for it, to search on I
suppose. It is redundantly build from the alternate names info. The name
"G'oteborg" is an ascii transliteration of the bulgarian name.

You shouldn't parse anything that is not designed to be parsed. (or
parse it at your own risk).

Best

Best

Marc

Andrew Dalke wrote:

> On Nov 8, 7:31 am, Marc Wick <m...@...> wrote:
>> The alteratenames field is not meant to be parsed.
>
> Then out of curiosity, why is that field present? And
> may I ask that the documentation somewhere mention that?
>
> Are there other fields which should not be parsed?
>
>> If you want to know the individual alternate names
>> then you should use the alteratename file.
>
> I don't understand why those two sources are different.
> Here are the alternatenames for Gothenburg, Sweden
>
> G'oteborg,GOT,Gautaborg,Geteborga,Gjoteborg,Goeteborg,Goteborg,Goteburg,Gotemburgo,Gotenburg,Gothembourg,Gothenburg,Gothoburgum,Gottenborg,Göteborg,Gøteborg,Gēteborga,Γκέτεμποργκ,Гьотеборг,Гётеборг,גוטנבורג,
> イェーテボリ,哥德堡
>
> There are 23 unique names in that list.
>
> Gothenburg is geonameid 2711537 and it has 33 entries in
> alternateName.txt .
>
> 1235974 2711537 Goeteborg
> 1235975 2711537 Goteburg
> 1235976 2711537 Gothenburg
> 1235977 2711537 Gottenborg
> 1600989 2711537 da Göteborg
> 1600991 2711537 eo Göteborg
> 1600995 2711537 hu Göteborg
> 1600999 2711537 la Gothoburgum
> 1601003 2711537 nl Gotenburg
> 1601007 2711537 pt Gotemburgo
> 1601009 2711537 sv Göteborg
> 1600984 2711537 de Göteborg
> 1600986 2711537 es Gotemburgo
> 1600988 2711537 ca Göteborg
> 1600992 2711537 fi Göteborg
> 1600996 2711537 ia Göteborg
> 1601002 2711537 nds Göteborg
> 1601006 2711537 pl Göteborg
> 1634095 2711537 it Göteborg
> 2256568 2711537 no Gøteborg
> 1970271 2711537 is Gautaborg
> 2181201 2711537 iata GOT
> 1600987 2711537 bg Гьотеборг
> 1600990 2711537 el Γκέτεμποργκ
> 1600994 2711537 he גוטנבורג
> 1600998 2711537 ja イェーテボリ
> 1601000 2711537 lv Gēteborga
> 1601008 2711537 ru Гётеборг
> 1621129 2711537 zh 哥德堡
> 1600993 2711537 fr Gothembourg
> 1601005 2711537 no Göteborg 1 1
> 1600985 2711537 en Gothenburg 1 1
> 1600997 2711537 id Göteborg
>
>
> of which 19 are unique. I see that "G'oteborg", which is
> the first name of the alternatenames field of cities1000.txt,
> is not in the alternateNames.txt file.
>
> Knowing no better, I decided to use the alternatenames
> from cities1000.txt because that one record (which is
> where I live) had more alternate names, and for the
> project I'm working on I wanted to maximize the
> likelihood of getting a match.
>
> Cheers,
>
> -- Andrew Dalke <dalke@...>
>
> >
>

Re: escaped unicode characters as aliases

2009-11-08T07:51:35Z

It is an html encoding and it will therefore display correctly on an
html page.
All that needed to be done was to click on the edit link and save again.
I did it for you.

Best

Marc

Andrew Dalke wrote:

> On Nov 8, 7:34 am, Marc Wick <m...@...> wrote:
>> Please don't hesitate to correct it:http://www.geonames.org/manual.html
>
> I had not actually known that as an option, as I've been working with
> the data files directly.
>
> I tried to do that and found the first difficulty was finding the
> records those fields referred to. All I had was:
>
> 2296413 788578 mk Lubaništa 1
> 58902 113646 fa Tabrīz 1
> 2181093 2540850 ar Warzāzāt
> 2181103 6533373 fa Meydān-e Emām Khomeinī
>
> Neither the main geonames.org page nor the advanced search page allow
> lookup by geonameid 788578. They think it's some sort of postal code.
> I could not find a match in cities1000.txt for that geonameid (though
> I could have searched in allCountries.txt), and searching for
> "Lubaništa" pointed out some place in Mexico which made no sense.
> (The language code is mk for Macedonian.)
>
> I used Google and found out that records are accessible through URLs
> like
> http://www.geonames.org/6533373
>
> I used that to go to each record, and in every case the alternate name
> string is displayed correctly.
>
> This suggests some sort of import/export Unicode encoding problem.
> Likely one which has been fixed, but with remnants of it still in the
> system somewhere.
>
> I do not think I am able to edit and fix these four cases.
>
> Best regards,
>
> -- Andrew Dalke <dalke@...>
>
> >
>

Re: escaped unicode characters as aliases

2009-11-08T07:40:50Z

On Nov 8, 7:34 am, Marc Wick <m...@...> wrote:
> Please don't hesitate to correct it:http://www.geonames.org/manual.html

I had not actually known that as an option, as I've been working with
the data files directly.

I tried to do that and found the first difficulty was finding the
records those fields referred to. All I had was:

2296413 788578 mk Lubaništa 1
58902 113646 fa Tabrīz 1
2181093 2540850 ar Warzāzāt
2181103 6533373 fa Meydān-e Emām Khomeinī

Neither the main geonames.org page nor the advanced search page allow
lookup by geonameid 788578. They think it's some sort of postal code.
I could not find a match in cities1000.txt for that geonameid (though
I could have searched in allCountries.txt), and searching for
"Lubaništa" pointed out some place in Mexico which made no sense.
(The language code is mk for Macedonian.)

I used Google and found out that records are accessible through URLs
like
http://www.geonames.org/6533373

I used that to go to each record, and in every case the alternate name
string is displayed correctly.

This suggests some sort of import/export Unicode encoding problem.
Likely one which has been fixed, but with remnants of it still in the
system somewhere.

I do not think I am able to edit and fix these four cases.

Best regards,

-- Andrew Dalke <dalke@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: unexpected aliases in alternateNames.txt

2009-11-08T07:20:33Z

On Nov 8, 7:32 am, Marc Wick <m...@...> wrote:
> please feel free to correct it.

There are 305 such names which are obviously wrong for the Galician
language and can be fixed with something like

perl -pe 's/(^\d+\t\d+\tgl\t)([^-]+ - )(.*$)/$1$3/'

plus another three which I spotted by hand when scanning for a "-" in
the alternate name.

Shall I send in a diff against alternateNames.txt? While I now know
about the web based interface to make corrections manually, I don't
really want to do 300+ edits by hand. If each takes 30 seconds that's
over 2.5 hours of work.

-- Andrew Dalke <dalke@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: comma in name in alternatenames

2009-11-08T07:03:23Z

On Nov 8, 7:31 am, Marc Wick <m...@...> wrote:
> The alteratenames field is not meant to be parsed.

Then out of curiosity, why is that field present? And
may I ask that the documentation somewhere mention that?

Are there other fields which should not be parsed?

> If you want to know the individual alternate names
> then you should use the alteratename file.

I don't understand why those two sources are different.
Here are the alternatenames for Gothenburg, Sweden

G'oteborg,GOT,Gautaborg,Geteborga,Gjoteborg,Goeteborg,Goteborg,Goteburg,Gotemburgo,Gotenburg,Gothembourg,Gothenburg,Gothoburgum,Gottenborg,Göteborg,Gøteborg,Gēteborga,Γκέτεμποργκ,Гьотеборг,Гётеборг,גוטנבורג,
イェーテボリ,哥德堡

There are 23 unique names in that list.

Gothenburg is geonameid 2711537 and it has 33 entries in
alternateName.txt .

1235974 2711537 Goeteborg
1235975 2711537 Goteburg
1235976 2711537 Gothenburg
1235977 2711537 Gottenborg
1600989 2711537 da Göteborg
1600991 2711537 eo Göteborg
1600995 2711537 hu Göteborg
1600999 2711537 la Gothoburgum
1601003 2711537 nl Gotenburg
1601007 2711537 pt Gotemburgo
1601009 2711537 sv Göteborg
1600984 2711537 de Göteborg
1600986 2711537 es Gotemburgo
1600988 2711537 ca Göteborg
1600992 2711537 fi Göteborg
1600996 2711537 ia Göteborg
1601002 2711537 nds Göteborg
1601006 2711537 pl Göteborg
1634095 2711537 it Göteborg
2256568 2711537 no Gøteborg
1970271 2711537 is Gautaborg
2181201 2711537 iata GOT
1600987 2711537 bg Гьотеборг
1600990 2711537 el Γκέτεμποργκ
1600994 2711537 he גוטנבורג
1600998 2711537 ja イェーテボリ
1601000 2711537 lv Gēteborga
1601008 2711537 ru Гётеборг
1621129 2711537 zh 哥德堡
1600993 2711537 fr Gothembourg
1601005 2711537 no Göteborg 1 1
1600985 2711537 en Gothenburg 1 1
1600997 2711537 id Göteborg

of which 19 are unique. I see that "G'oteborg", which is
the first name of the alternatenames field of cities1000.txt,
is not in the alternateNames.txt file.

Knowing no better, I decided to use the alternatenames
from cities1000.txt because that one record (which is
where I live) had more alternate names, and for the
project I'm working on I wanted to maximize the
likelihood of getting a match.

Cheers,

-- Andrew Dalke <dalke@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: escaped unicode characters as aliases

2009-11-07T22:34:44Z

Please don't hesitate to correct it:
http://www.geonames.org/manual.html

Marc

Andrew Dalke wrote:

> The following from alternateNames.txt contain escaped Unicode
> characters in
>
> 2296413 788578 mk Lubaništa 1
> 58902 113646 fa Tabrīz 1
> 2181093 2540850 ar Warzāzāt
> 2181103 6533373 fa Meydān-e Emām Khomeinī
>
> of which these
>
> Tabrīz
> Warzazāt
> Warzāzāt
>
> are also listed in cities1000.txt as alternatenames.
>
> -- Andrew Dalke <dalke@...>
>
> >
>

Re: is geonameid 2556150 correct?

2009-11-07T22:33:58Z

It is obviously wrong. I have corrected it.

Marc

Andrew Dalke wrote:

> This is suspicious:
>
> 2556150 mohammed boulaich el habate ksar sghir mohammed boulaich el
> habate ksar sghir 35.7 -5.7 P PPLR
> MA 51 50000 209 Africa/Casablanca
> 2007-06-26
>
> The name is "mohammed boulaich el habate ksar sghir". The
> capitalization isn't right, it's a rather long name, and if you go to
>
> http://www.geonames.org/2556150/boulaichich-mohammed-boulaich.html
>
> it doesn't look like a place with 50,000 people. Which is a rather
> round number.
>
> -- Andrew Dalke <dalke@...>
>
> >
>

Re: unexpected aliases in alternateNames.txt

2009-11-07T22:32:51Z

please feel free to correct it.

Marc

Andrew Dalke wrote:

> There are some alternate names I did not expect both in cities1000.txt
> and in alternateNames.txt, easily found by grepping for " - " (space
> hyphen space):
>
>
> 1894665 3165524 gl Turín - Torino
> 1972921 2802361 gl Bélxica - België
> 1986656 2525764 gl Agrixento - Agrigento
> 1977253 223816 gl Xibutí - Djibouti
>
> It looks like there was a bad import of a set of Galician names.
>
> There are a few problems with other languages, like
>
> 2014633 2787387 id Saint-Josse-ten-Noode - Sint-Joost-ten-Node
> 2013778 2783474 id Woluwe-Saint-Pierre - Sint-Pieters-Woluwe
>
> and some anonymous ones, like
>
> 2181169 1816670 Beijing - Pekin
>
> -- Andrew Dalke <dalke@...>
>
> >
>

Re: comma in name in alternatenames

2009-11-07T22:31:10Z

The alteratenames field is not meant to be parsed. If you want to know
the individual alternate names then you should use the alteratename file.

Marc

Andrew Dalke wrote:

> The geoname schema which describes cities1000.dat is at
>
> http://download.geonames.org/export/dump/readme.txt
>
> It says
>
> alternatenames : alternatenames, comma separated varchar(4000)
> (varchar(5000) for SQL Server)
>
> The entry for geonameid 6292397 is for the city
>
> Rüti / Dorfzentrum, Südl. Teil
>
> That appears to be the same place as
>
> http://en.wikipedia.org/wiki/Rüti,_Zürich
>
> The entry contains a ",", which means my parser, which splits on ",",
> gets messed up. I'm going to change it to be "," not followed by
> space.
>
> I don't know if this is a problem with the name (that it contains a
> ","), with the documentation (that it doesn't say how names which
> contains commas are handled), or if it's that I shouldn't be using
> that field and should instead use the alternateNames.txt file to get
> these.
>
> -- Andrew Dalke <dalke@...>
>
> >
>

escaped unicode characters as aliases

2009-11-07T15:09:29Z

The following from alternateNames.txt contain escaped Unicode
characters in

2296413 788578 mk Lubaništa 1
58902 113646 fa Tabrīz 1
2181093 2540850 ar Warzāzāt
2181103 6533373 fa Meydān-e Emām Khomeinī

of which these

Tabrīz
Warzazāt
Warzāzāt

are also listed in cities1000.txt as alternatenames.

-- Andrew Dalke <dalke@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

is geonameid 2556150 correct?

2009-11-07T15:03:26Z

This is suspicious:

2556150 mohammed boulaich el habate ksar sghir mohammed boulaich el
habate ksar sghir 35.7 -5.7 P PPLR
MA 51 50000 209 Africa/Casablanca
2007-06-26

The name is "mohammed boulaich el habate ksar sghir". The
capitalization isn't right, it's a rather long name, and if you go to

http://www.geonames.org/2556150/boulaichich-mohammed-boulaich.html

it doesn't look like a place with 50,000 people. Which is a rather
round number.

-- Andrew Dalke <dalke@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

unexpected aliases in alternateNames.txt

2009-11-07T14:56:26Z

There are some alternate names I did not expect both in cities1000.txt
and in alternateNames.txt, easily found by grepping for " - " (space
hyphen space):

1894665 3165524 gl Turín - Torino
1972921 2802361 gl Bélxica - België
1986656 2525764 gl Agrixento - Agrigento
1977253 223816 gl Xibutí - Djibouti

It looks like there was a bad import of a set of Galician names.

There are a few problems with other languages, like

2014633 2787387 id Saint-Josse-ten-Noode - Sint-Joost-ten-Node
2013778 2783474 id Woluwe-Saint-Pierre - Sint-Pieters-Woluwe

and some anonymous ones, like

2181169 1816670 Beijing - Pekin

-- Andrew Dalke <dalke@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

comma in name in alternatenames

2009-11-07T13:50:54Z

The geoname schema which describes cities1000.dat is at

http://download.geonames.org/export/dump/readme.txt

It says

alternatenames : alternatenames, comma separated varchar(4000)
(varchar(5000) for SQL Server)

The entry for geonameid 6292397 is for the city

Rüti / Dorfzentrum, Südl. Teil

That appears to be the same place as

http://en.wikipedia.org/wiki/Rüti,_Zürich

The entry contains a ",", which means my parser, which splits on ",",
gets messed up. I'm going to change it to be "," not followed by
space.

I don't know if this is a problem with the name (that it contains a
","), with the documentation (that it doesn't say how names which
contains commas are handled), or if it's that I shouldn't be using
that field and should instead use the alternateNames.txt file to get
these.

-- Andrew Dalke <dalke@...>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: Every findNearbyPostalCodes request returning Canillo, AD?

2009-11-05T21:06:33Z

there was an issue with a new sw release, I have restored the previous
version.

Marc

angelod101 wrote:
> I've been having this problem for hours today. Does anyone know if
> ws.geonames.org is having issues at the moment?
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

Every findNearbyPostalCodes request returning Canillo, AD?

2009-11-05T16:33:49Z

I've been having this problem for hours today. Does anyone know if
ws.geonames.org is having issues at the moment?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "GeoNames" group.
To post to this group, send email to geonames@...
To unsubscribe from this group, send email to geonames+unsubscribe@...
For more options, visit this group at http://groups.google.com/group/geonames?hl=en
-~----------~----~----~----~------~----~------~--~---

Re: comment in alternateNames.txt

2009-11-05T11:28:00Z

It is really weird. I have deleted those names.

Best

Marc

Andrew Dalke wrote:

> This is in alternateNames.txt
>
> 2729452 6949363 fa It is a village of nahavand in Hamadan
> Province West Iran 1 1
>
>
> Looking at http://www.geonames.org/recent-changes/country/IR/
> it appears to derive from the comment field.
>
> -- Andrew Dalke <dalke@...>
>
> >
>