| Author |
Message |
|
|
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)
|
|
|
|
More generally, the connection between city or village name and position can be flawed. Spatial image browsers such as Google Earth make use of several databases that link place names with latitude and longitude, and unfortunately all such databases suffer from inaccuracies, such as placing Islamabad 100 miles from its true location. All mapping efforts, whether community based or UN supported, would benefit from a stronger feedback mechanism, such as a community filtering system that enables authenticated individuals to update shared geographical data online. For example, we hope that database providers will support initiatives, such as the Geonames Forum (http://www.geonames.org/about.html).
http://www.nature.com/news/2006/060213/full/439787a.html
|
|
|
|
We have just added a couple of new countries for the postalcode based geocoding service :
# Canada, FSA only (CA)
# Czech Republic (CZ)
# Finland (FI)
# India (IN)
# Croatia (HR)
# Hungary (HU)
# Liechtenstein (LI)
# The Netherlands (NL)
# Pakistan (PK)
# Slovenia (SI)
# Slovakia (SK)
# Thailand (TH)
# South Africa (ZA)
|
|
|
|
Ich habe heute wiedereinmal den Wikipedia Export runtergeladen und damit rumgespielt.
Die 23'000 (Stand 5 Februar) georeferenzierten Einträge in der Deutschen Wikipedia sehen auf googlemaps so aus :
http://www.geonames.org/maps/wikipedia.html
Die drei Fehler (!) auf der Einstiegsseite habe ich im Wikipedia soeben korrigiert. soviel zum Thema Wikipediaqualität ...
Falls jemand noch weitere Fehler findet, hier die Erläuterungen zur Wikipedia Georeferenzierung :
http://de.wikipedia.org/wiki/Wikipedia:WikiProjekt_Georeferenzierung
Beim nächsten Wikipedia-Export werden diese Fehler dann auch bei geonames korrigiert sein.
Eine Volltext-Suche über die georeferenzierten Wikipediaeinträge ist hier :
http://www.geonames.org/wikipedia-search.html?
Aufgefallen ist mir, dass die Georeferenzierung im Deutschen Export viel homogener und damit einfacher zu parsen ist, als im Englischen Export. Im Englischen Export gibt es unzählige Formatvorlagen die man beim parsen berücksichtigen müsste.
PS, Hier die erwähnten Fehler :
- Einwohnerzahl von "Amiens" stimmt nicht, bzw ist doppelt im wikipedia (einmal richtig und einmal falsch).
- Einwohnerzahl von "Beaucaire (Gard)" stimmt nicht.
- Das "Metropolis-Haus" in Madrid ist keine Stadt und hat schon gar nicht 3 Millionen Einwohner.
Mit dem Update vom 5 Feb. sind die Fehler korrigiert. Es sind nun 24'000 Einträge. (editiert am 7 Feb 2006)
|
|
|
|
Hallo Sascha
Die Daten von geonames sind in WGS84 gespeichert. Sowohl der Datenbank-Export wie auch die Webservices verwenden dieses Format.
Für die Webservices ist natürlich grundsätzlich auch ein anderes Format denkbar. Beispielsweise, könnte über einen Parameter beim Aufruf festgelegt werden, in welchem Format die Ausgabe erfolgen soll. Wobei die meisten Formate nur lokal beschränkt sinnvoll sind, CH1903 würde nur für Koordinaten innherhalb der Schweiz Sinn machen.
Welches Format wäre dir am liebsten?
Marc
|
|
|
|
Oooops. Sorry.
Die Koordinaten für diesen Service waren für Deutschland und Belgien vertauscht. Ich habe den Fehler soeben korrigiert, die Koordinaten sollten nun korrekt sein.
Danke für den Hinweis.
Marc
|
|
|
|
The downloadable country files are a simplyfied version of the database. In particular Alternatenames are normalized.
|
|
|
|
Hi Marius
First of all: great service!
thanks.
When I use the search option on this page, I get results in a hierarchy like 1. adminstrative division -> 2. adm. div. -> location. (For Norway). When I download the db dump I cannot figure out how to recreate such an hierarchy. I suppose it is not possible...
How do you build this hierarchy and why isn't there a linking field (table self reference) supplied in the db dump?
Cheers!
Marius,
Norway
You find the first administrative dision in the column 'admin1 code' in the dump. It currrently contains the fips code, but we are working on replacing it with the more meaningful iso 3166-2 code. For the time being you find fips and iso codes here :
http://www.geonames.org/NO/administrative-division-norway.html
For Norway the feature distribution is :
geonames_db=> select count(*),admincode1 from geoname where countrycode = 'NO' group by 2;
count | admincode1
-------+------------
613 |
560 | 13
951 | 00
2357 | 06
3168 | 08
7448 | 09
3053 | 15
2961 | 16
131 | 12
741 | 20
2329 | 11
1362 | 02
870 | 01
2038 | 14
5291 | 07
6929 | 18
3329 | 10
2995 | 17
5205 | 05
1647 | 04
1027 | 19
(21 rows)
Hope this helps
Marc
|
|
|
|
Hallo Daniel
- wer betreibt GeoNames? Vielen Dank an die Betreffenden!
Geonames wir von mir als Hobby betrieben. Ich war für ein anderes Projekt auf der Suche nach 'freien' Webservices. Und weil ich nichts gefunden habe, habe ich selbst damit angefangen.
- welche Technik steckt dahinter? Die Anfragen werden wirklich extrem schnell beantwortet. Habe mir vorhin die komplette Datenbank gezogen und muss schwer arbeiten, um "lokal" überhaupt Vergleichbares hinzubekommen!
Als Datenbank wird Postgres 8 verwendet. Auf Postgis habe ich bislang verzichtet.
Die Volltextsuche wird mit Lucene erledigt. (http://lucene.apache.org/).
Auf der Client-Seite hat es viel Ajax und Googlemaps.
- seit wann gibt's GeoNames -- und wie stehen die Chancen, dass es GeoNames auch in 1 Jahr noch gibt, wenn 10.000x so viele Anfragen am Tag kommen wie jetzt?
Geonames gibt es seit Ende 2005. Wie lange es bestehen wird, ist wie bei allen Projekten, schwer zu sagen. Dies gilt natürlich nicht nur für kostenlose Projekte, auch kommerzielle Projekte kommen und gehen.
Marc
|
|
|
|
Canadian Geographical Names are available on www.geobase.ca, unfortunately the download is only available in 13'500 files. Theses files are generated on the fly and you will receive an email containing the link to these files (no more than 50 for one download order).
We have gone through this painful process and have downloaded all files in xml format.
All files in a single tar ball are here : http://download.geonames.org/export/geobase.tar.gz (30MB)
The tar-file has a size of 30M and contains around 13'500 files with a total of 300'000 distinct names (around 70'000 are duplicates). The datum used in these files is NAD27.
What is the difference to the normal geonames download for Canada ?
* The datum in the normal download is wgs84. (geobase.ca is nad27).
* duplicates are eliminated
* the feature codes have been converted. (http://forum.geonames.org/gforum/posts/list/9.page)
* the geonames download is a cvs file (geobase.ca is xml)
If you are working with wgs84 the normal geonames download might be better for you.
|
|
|
|
O' Reilly has an example on how to use amazon's REST webservices with php.
http://www.onlamp.com/pub/a/php/2003/10/30/amazon_rest.html
Let us know if this helps you.
|
|
|
|
![[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
