| Author |
Message |
|
|
Thanks for the error report. It is now fixed.
Marc
|
 |
|
|
Deine Fragen haben durchaus ihre Berechtigung. Wenn du fündig geworden bist, lass es uns bitte wissen, vor allem der erste Punkt ist auch für uns interessant und wir arbeiten daran.
Die Ländernamen (oder meinst du Bundesländer) sollten bei uns ziemlich vollständig abgedeckt sein. Im Moment noch gut versteckt aber am Wochenende installieren wir eine neuere Version von geonames.org und dann sollte dies besser sein. Bis dann muss man auf der Googlemap das Land anklicken und dann im 'Ballon' auf 'alternate names' klicken.
[update : 'Deutschland in anderen Sprachen findest du hier : http://www.geonames.org/countries/DE/other-names-for-germany.html ]
Andere (aber leider nicht public domain) Datenbanken sind :
Getty :
http://www.getty.edu/research/conducting_research/vocabularies/tgn/
Verein für Computergenealogie :
http://gov.genealogy.net/
Hier noch einige Namen für München :
München German (de)
Munich English (en)
Múnich Spanish (es)
München Afrikaans (af)
ميونخ Arabic (ar)
Munich Asturian; Bable (ast)
Мюнхен Bulgarian (bg)
Munic Catalan (ca)
Mnichov Czech (cs)
München Danish (da)
Μόναχο Greek, Modern (1453-) (el)
Munkeno Esperanto (eo)
München Estonian (et)
مونیخ Persian (fa)
München Finnish (fi)
Munich French (fr)
Múnic - München Gallegan (gl)
מינכן Hebrew (he)
München Croatian (hr)
München Hungarian (hu)
München Indonesian (id)
Monaco di Baviera Italian (it)
ミュンヘン Japanese (ja)
მიუნხენი Georgian (ka)
뮌헨 Korean (ko)
München Kurdish (ku)
Monachium Latin (la)
Miunchenas Lithuanian (lt)
Minhene Latvian (lv)
Monaco 'e Baviera Neapolitan (nap)
München Low German; Low Saxon (nds)
München Dutch (nl)
München Norwegian Nynorsk (nn)
München Norwegian (no)
Monachium Polish (pl)
Munique Portuguese (pt)
München Romanian (ro)
Мюнхен Russian (ru)
Mníchov Slovak (sk)
München Slovenian (sl)
München Swedish (sv)
மியூனிக் Tamil (ta)
มิวนิก Thai (th)
Münih Turkish (tr)
Мюнхен Ukrainian (uk)
München Vietnamese (vi)
慕尼黑 Chinese (zh)
|
|
|
|
This would certainly help. You can send the file to info@geonames.org.
I will then run it against our place name database and add lat/lng to all records.
Marc
|
|
|
|
Hi Ryle
The name of the state of California was 'California, State of'. We have now removed the part ', State of' from all names of US states. Your query now returns the state of California at the top position.
Do you think we should also change the following :
19982 | , Township of
3791 | , Town of
The number is the the number of records.
Marc
|
|
|
|
Hi Paul
There are a lot of things not included in the download as they are available elsewhere. We focus on offering webservice around the data to save our users the trouble to download and install this data.
The lat/lng -> country reverse geocoding is using country border shape files. The algorithm is just a simple database lookup with postgres.
We are actually working to improve this geocoding service. We have far better shape files than the ones we currently use, but unfortunately without any country information.
Marc
|
|
|
|
Postal codes and geocoding are now available for Poland (thanks to Kay for his help), Sri Lanka and Iceland.
Postal codes for Mexico and the Netherlands have been improved and corrected.
http://www.geonames.org/postal-codes/
http://www.geonames.org/export/free-geocoding.html
|
|
|
|
Ich habe einen Fehler im Javascript Code gefunden und geflickt. Ich hoffe es funktioniert jetzt.
Hier noch die Liste der Hauptstädte mit fehlenden Einwohnerangaben :
geonames_db=> select geonameid,name,countrycode from geoname where population is null and featureclass = 'P' and featurecode = 'PPLC';
geonameid | name | countrycode
-----------+---------------------------+-------------
1252416 | Thimphu | BT
1528675 | Bishkek | KG
1559446 | Koror | PW
1821274 | Macau | MO
1899461 | Koror | PW
2078127 | Flying Fish Cove | CX
2110079 | Tarawa | KI
2198148 | Suva | FJ
3042091 | Saint Helier | UK
3042287 | Saint Peter Port | UK
3576022 | Saint John's | AG
3576812 | Castries | LC
3577887 | Kingstown | VC
3579925 | Saint George's | GD
4030723 | Adamstown | PN
4032402 | Nuku`alofa | TO
3578069 | Plymouth | MS
Ich werde die Liste manuell updaten, falls jemand Lust hat dabei zu helfen : nur zu.
Hier die letzten 50 updates :
http://www.geonames.org/recent-changes.html
Update :
0 U 2006 03 12 09:51:11 Hong Kong (historical) HK marc add pop 7012738
0 U 2006 03 12 09:50:08 Krung Thep TH marc add pop 8538610
0 U 2006 03 12 09:49:10 Sri Jayewardenepura Kotte LK marc add pop 115826
0 U 2006 03 12 09:48:16 Mexico MX marc add pop 11285654
0 U 2006 03 12 09:45:19 Belgrade CS marc add pop 1273651,movement 0 km
|
|
|
|
Hallo Kolossos
Vielen Dank für dein 'Mashup'. Ich habe auch schon daran gedacht ein kmz file zu machen, aber jetzt erübrigt es sich ja.
Ich vermute du verwendest die pop Zahlen für die Sortierung? Dann könntest du die Haupstädte ohne pop Angaben in der Sortierung auch noch berücksichtigen.
Schön wäre es, wenn Du beim Infowindow eine Link zurück zu www.geonames.org legen könntest, damit Fehler gleich bei Geonames korrigiert werden können. Der Link sieht so aus :
http://www.geonames.org/maps/geonameId=3123709
Marc
|
|
|
|
The full text search should have response times of not more than a couple of milliseconds. On the online (html) interface there is also a spell checker which kicks in if no results are found. The current implementation of the spell checker ("did you mean ... ") is not really fast (up to one second). Depending on the query term 'no rows found' may also result in a call to the yahoo geocoder web service.
If you use the full text search xml web service no other services are involved and you should get response times of maximal a couple of milliseconds.
Do you have an example of a slow search? I would like to investigate further.
Of course it would be possible for us to run it on a faster server as a commercial version. But as explained above, I am confident to get fast response time with the free version of the service.
Marc
|
|
|
|
Oops, it was a bug in the javascript code. Thanks for letting us know.
The bug is fixed now, you may have to press 'shift reload' to make sure your browser is loading the newest javascript code.
Thanks for using geonames.org and for bearing this bug.
Marc
|
|
|
|
For the decoding of the METAR (MÉTéorologique ("Weather") Aviation Régulière) weather data we use the following text items. If you want to use the webservice in a new language just translate the texts below and send the translation to info@geonames.org. We will then include the language in the webservice.
http://www.geonames.org/export/JSON-webservices.html#weather
Languages currently supported : English, Bulgarian, Russian, German, Spanish, Portuguese, Italian, Dutch,Finnish, French, Hebrew, Arabic, Czech, Chinese (zh), Norwegian Nynorsk (nn), Norwegian Bokmål (nb)
clouds.null = n/a
clouds.SKC = clear sky
clouds.CLR = clear sky
clouds.FEW = few clouds
clouds.SCT = scattered clouds
clouds.BKN = broken clouds
clouds.OVC = overcast
clouds.CAVOK = clouds and visibility OK
clouds.NCD = no clouds detected
clouds.NSC = nil significant cloud
clouds.VV = vertical visibility
condition.null=n/a
condition.DZ=drizzle
condition.RA=rain
condition.SN=snow
condition.SG=snow grains
condition.IC=ice crystals
condition.PL=ice pellets
condition.GR=hail
condition.GS=small hail/snow pellets
condition.UP=unknown precipitation
condition.BR=mist
condition.FG=fog
condition.FU=smoke
condition.VA=volcanic ash
condition.SA=sand
condition.HZ=haze
condition.PY=spray
condition.DU=widespread dust
condition.SQ=squall
condition.SS=sandstorm
condition.DS=duststorm
condition.PO=well developed dust/sand whirls
condition.FC=funnel cloud
condition.+FC=tornado/waterspout
condition.-=light
condition.+=heavy
condition.VC=in vicinity:
condition.MI=shallow
condition.BC=patches
condition.SH=showers
condition.PR=partial
condition.TS=thunderstorm
condition.BL=blowing
condition.DR=drifting
condition.FZ=freezing
|
|
|
|
Thanks Stan.
Let us know once you have integrated the search. We would like to add your application to the 'geonames users' list.
Regards
Marc
|
|
|
|
Geonames has now included the place name dataset from "Land Information New Zealand (LINZ)".
If you plan to use the new zealand data from geonames, don't forget to give credit to LINZ.
LINZ writes :
In circumstances where this data or derivatives of this data have been used to generate information dissemination products such as maps, digital database products, internet databases, gazetteer books or similar, a clear and prominent reference should be made to Land Information New Zealand as the source of the data. If the data has been downloaded and translated or imported into another format or computer program Land Information New Zealand will not be responsible for any problems arising from the use of the data. The spelling or composition of the place names must not be altered unless the change is made to keep the name in line with a New Zealand Geographic Board Nga Pou Taunaha Aotearoa decision or to correct a known error as detailed by Land Information New Zealand. This data may be freely distributed provided that these conditions are distributed with the data and adhered to by all recipients.
http://www.linz.govt.nz/rcs/linz/pub/web/root/core/Placenames/SearchPlaceNames/downloaddataset/index.jsp
Despite of coming from an offical source the data is far from perfect. LINZ writes : The co-ordinates were digitised at the bottom left corner of the text labels that appear on the printed map. The co-ordinates are not a GPS position for the geographic location of the feature.
We have used the following table to convert LINZ features to geonames featue classes and feature codes :
Code:
AIR = S.AIRP
BAY = H.BAY
BCH = T.BCH
BDGE = S.BDG
BLDG = S.BLDG
BNK = H.BNK
BSN = T.PAN
CAVE = S.CAVE
CEM = S.CMTY
CGND = S.CMP
CLIF = T.CLF
CRTR = T.CRTR
DAM = s.DAM
ESTY = H.ESTY
FALL = H.FLLS
FARM = S.FRM
FLAT = T.PLN
FORD = T.FORD
FRST = V.FRST
GLCR = H.GLCR
GLKS = S.RECG
GORG = T.GRGE
HILL = T.HLL
HIST = S.HSTS
HOSP = S.HSP
HSTD = S.FRMT
HUT = S.HUT
ISLD = T.ISL
ISTH = T.ISTH
LAKE = H.LK
LOC= L.LCTY
LTH = S.LTHSE
METR = P.PPL
MINE = S.MN
NAVB = S.BCN
NLR = L.RESV
PA = L.RESV
PARK = L.PRK
PASS = T.PASS
PEN = T.PEN
PNT = T.PT
POPL = P.PPL
RC = S.RECR
RDGE = T.RDGE
RDRF = R.RD
RLYF = R.RR
RNGE = T.MTS
ROCK = T.RK
RSTN = S.RSTN
SBRB = P.PPLX
SCH = S.SCH
SEA = H.SEA
SKI = S.RSRT
SPR = H.SPNG
STRA = H.STRT
STRM = H.STM
SWMP = H.SWMP
TOWN = P.PPL
TRCK = R.TRL
TREE = V.TREE
TRIG = S.BLDG
TUNL = R.TNL
TWAY = R.RR
UNIV = s.SCH
USAT = P.PPL
WELL = H.WLL
WHF = S.WHRF
WILD = L.RESN
WRCK = s.WRCK
WWAY = H.CNL
No conversion :
GEO`GEOTHERMAL AREA: Area of geothermal activity
MNAT`MISCELLANEOUS NATURAL FEATURE:
MPLA`MISCELLANEOUS PLACE:Misc named place or area
MRFM`MARINE ROCK FORMATION
PPLN`PIPELINE: Conduit for carriage of liquids or gas
SLIP`SLIP: Area of unstable hillside
We have inserted around 50'000 new records, and matched ca 6'000 records to existings nga records. For the conversion of the NZGD49 datum we have used the GD2000it utility.
|
|
|
|
Question :
How can I help geonames? What can I contribute?
Answer :
We need help in various areas :
You can also support the project with a donation and help pay for the servers : http://www.geonames.org/donations.html
If you want to help just get in touch with us : info@geonames.org
Thank you.
|
|
|
|
Hi Anonymous
What you are referring to are "collations" used for sorting.
http://dev.mysql.com/doc/refman/5.0/en/charset-unicode.html
According to this page :
http://dev.mysql.com/doc/refman/5.0/en/charset-charsets.html
you could use the collation : "utf8_general_ci" for the character set "utf8".
Hope this helps.
Marc
|
|
|
|
How long is your column 'name' ?
The dump files are in utf8 format, this may explain why you see strange names like the ones you mention.
You have to configure your database to use utf8. In the NL file there are only dutch names and therefore no exotic characters.
Marc
|
|
|
|
Question :
I have edited and corrected a place name on geonames.org. What happens with my update if a new nga release is loaded? Will my update be overwritten and disappear?
Answer :
Your update will stay untouched.
First we only update nga records if they have a timestamp newer than our last update, and second even if it has a newer timestamp we compare the change history for both update branches and the two branches are merged whenever possible. If it is not possible to reconcile the two conflicting branches the modification by the geonames user takes precedence.
The concept is similar to the 'progressive fork' concept of the wikipedia fork Citizendium.
We are also in touch with nga and send them periodically our updates. It is therefore possible that your change on www.geonames.org makes it into the official nga release.
|
|
|
|
Question :
We are using geonames data on our website and we would like to have a backlink to a geonames record where our users can move and update a wrong entry. Is this possible?
Answer :
Sure. Geonames is supporting links of the following pattern :
http://www.geonames.org/<geonameId>/<name>.html
where <geonameId> is the integer id of the geonames database entry. You find the id in the database download and in the webservice.
There is also an optional parameter "zoom" if you want the google map to be displayed in an other zoom level (default is 3).
Example : http://www.geonames.org/3123709/eibar.html
If you don't know the name a default page name like '/geonameId/index.html' will also work.
The previous link is deprecated but still supported :
www.geonames.org/maps/geonameId=<geonameid>
http://www.geonames.org/maps/geonameId=3123709
|
|
|
|
We have updated the geonames database with the latest nga release 2006-02-22.
3355 records have been modified
7584 new records
With this release nga has changed its language codes and is now using 3-letter iso language code instead of using its own codes. Geonames.org has already been using iso 2-letters iso language code. Geonames.org will continue using 2-letters iso language code if available and only use 3-letter language code where no 2-letter code is available.
Code:
countries updated with this data load :
count | countrycode
-------+-------------
1295 | CO
762 | KP
263 | KR
212 | RU
182 | AF
131 | YE
63 | IQ
50 | ID
43 | PE
43 | MN
27 | HT
15 | CN
12 | UA
8 | OM
4 | NG
3 | TN
2 | SL
2 | IR
2 | LR
2 | LB
2 | MA
2 | DO
1 | BG
1 | QA
1 | GE
1 | BZ
1 | DZ
1 | RE
1 | GR
1 | TW
1 | MR
1 | BF
countries with new records :
count | countrycode
-------+-------------
3697 | CO
2379 | ID
756 | KR
391 | RU
133 | CN
58 | IQ
45 | PE
35 | AF
28 | HT
21 | KP
17 |
7 | YE
3 | UA
3 | IR
3 | TW
2 | LB
2 | DO
2 | CF
1 | QA
1 | TN
(20 rows)
|
|
|
|
We have parsed and extracted geo location from the wikipedia dumps in english and german.
We have thus been able to extract the geolocation of 155'000 Wikipedia entries in 189 languages:
http://www.geonames.org/wikipedia.html
A google maps mashup is here :
http://www.geonames.org/maps/wikipedia.html
Fulltext search over geo referenced wikipedia articles :
http://www.geonames.org/wikipedia-search.html?
The data is also available as webservice : http://www.geonames.org/export/wikipedia-webservice.html
For more information about geo location in wikipedia :
http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Geographical_coordinates
Or in German :
http://de.wikipedia.org/wiki/Wikipedia:WikiProjekt_Georeferenzierung
(edit 2006 March 5)
|
|
|
|
![[Search]](/gforum/templates/default/images/icon_mini_search.gif){kind=icon}
![[Recent Topics]](/gforum/templates/default/images/icon_mini_recentTopics.gif){kind=icon}
![[Groups]](/gforum/templates/default/images/icon_mini_groups.gif){kind=icon}
![[Register]](/gforum/templates/default/images/icon_mini_register.gif){kind=icon}
Register![[Login]](/gforum/templates/default/images/icon_mini_login.gif){kind=icon}
Login
