| Author |
Message |
|
|
Hallo Christian
Ich verstehe das Problem. Der Ort ist auf der Luxemburgischen Seite des Rheins. Wir haben aber nur die Ortsmittelpunkte gespeichert und in Luftlinie ist der Ort Wellen am nächsten. Zum gegenwärtigen Zeitpunkt kann ich nichts tun, es bräuchte Vektorinformationen mit den Grenzumrissen der Orte um solche Fälle unterscheiden zu können. Diese Daten sind aber nicht frei erhältlich.
Viele Grüsse
Marc
|
 |
|
|
GeoNames is using several servers. I have manually updated the main database and the modification will become visible on the other servers and services when we update the database and webservice index on all servers.
Marc
|
 |
|
|
John
Unfortunately we have many alternate names where we don't know which language the name is in.
Marc
|
 |
|
|
Hi Brook
This is weird. Do you still have any problems?
What I have seen in the logfiles is that you are querying the same lat/lng over and over again. Could there be an endless loop on your end?
Marc
|
 |
|
|
Thanks David. Will do it.
Marc
|
 |
|
|
modifications.txt is a subset of the geonames table generate at the time of creating the dump. It is redundant and only included in the download directory for convenience. All it contains are the records from the geonames table with the given modifcationdate.
Marc
|
 |
|
|
Michael
This is not yet available. What you can do is to calculate the bounding box over the countries in a continent.
Marc
|
 |
|
|
I will put it onto the todo list. The data is currently not included in the search index and in order to be consistent all services should return the same result for style=full. So it needs to be in the search index to make sure all services return the same xml.
Marc
|
 |
|
|
In the FAQ there are a couple of threads to import GeoNames into all major databases :
http://forum.geonames.org/gforum/forums/show/6.page
We believe csv is the simplest form to provide the data. It can easily be loaded into all databases and it can be processed by all application environments. SQL dumps would only be loadable in one database type and would make it unnecessarily difficult for every body else.
Marc
|
 |
|
|
Thanks, ext.
I have run the updates. They are available with todays daily dump.
Marc
|
 |
|
|
Hi John
All you have to do in order to add places it to create an account and follow the instruction : http://www.geonames.org/manual.html
ICAO/IATA codes are in the database for most airports.
Many of our data sources are from US agencies and are using the FIPS codes. We plan to switch to ISO codes where it is possible.
Marc
|
 |
|
|
I have not yet found free polygons with ocean boundaries. Do you know of one?
Marc
|
 |
|
|
Hi Phil
The connection pool problem is fixed. It was a configuration error.
For the second problem there is not much I can do. Unless it is for an enterprise application and you are ready to pay for a NAVTEQ data license.
Marc
|
 |
|
|
Hi
Withouth lat/lng it is difficult. All our other toponyms have lat/lng and it would be a considerable change in the data model when we start including data without lat/lng all of a sudden.
Marc
|
 |
|
|
Hi Giorgio
There is a hierarchy service, though it does not include oceans.
Marc
|
 |
|
|
Do you know which kind of code system for administrative divisions in Japan makes sense? Up to now we don't have any identification codes assigned for the lower administrative divisions in Japan and the edit interface does not work properly in this case. What we could do is assign the geonameId as a code. The downside would be that it will be difficult to change it in the future to a code system more commonly used in the country. GeoNames users might rely on the geonameId as a code and it could confuse them if we change to another coding system.
Marc
|
 |
|
|
Hi Phil
The address API is using data from the US census. The US census is not as fast in collecting information as the commercial providers (NAVTEQ or Tele Atlas). I guess the residential neigbourhood is rather new and the US census has not yet added this street level information into their system.
The findNearbyPlaceName services that works on USGS (US Geological Survey) data does return results for this location :
http://ws.geonames.org/findNearbyPlaceName?lat=39.059269&lng=-77.466728&style=full
Marc
|
 |
|
|
Fred
Tags are not a panacea, I fully agree. I have something in mind like the featureCodes but where multiple codes are allowed. The downside of the featureCodes is that only one code is allowed and a lot of categorizations are orthogonal. They are independent from each other and a toponym can be one or more. The tagging approach allows to express this unrelatedness, I think it is the same concept you describe with bit flags.
Marc
|
 |
|
|
We have two different tables for the GeoNames main database and the postal codes. For France the postal code data in the main database is now better than the postal codes data in the postal code database.
It would make sense to replace the postal code data in the postal code table with the data from the GeoNames main tables. I wanted to do this yesterday, but found some problems.
1. Some postal codes are missing in the main GeoNames database (like 69003 Lyon)
2. We have a lot more postal code placename combination in the main tables (>60000) wheres we have < 40000 in the postal code table. In this respect I wonder whether we should have a featurecode PPLA4 for seat of a fourth order administration to flag the main place of a postal code. Sometimes the same postal code is used by villages around the main city and I think it would be useful to know which one is the main city.
Marc
Postal codes from the postal code table, missing in the main database :
Code:
zip | placename
-------+----------------------------
13123 | L Albaron
13661 | Salon De Provence Air
13898 | Aix En Provence Armees
13900 | Marseille Cheques
13968 | Carpiagne Armees
13998 | Marseille Armees
16109 | Cognac Air
17135 | Rochefort Fourriers Marine
20223 | Solenzara Air
20900 | Ajaccio Cheques
21900 | Dijon Cheques
29240 | Brest Naval
30998 | Nimes Armees
31900 | Toulouse Cheques
31998 | Toulouse Armees
31999 | Andorre
33164 | Cazaux Air
33970 | Cap Ferret
33998 | Bordeaux Armees
34900 | Montpellier Cheques
35900 | Rennes Cheques
35910 | Rennes Cne
35998 | Rennes Armees
36630 | La Martinerie Terre
38900 | Grenoble Cheques
38998 | Grenoble Varces Armees
40115 | Biscarrosse Air
44900 | Nantes Cheques
50115 | Cherbourg Naval
51900 | Chalons Sur Marne Cheques
54900 | Nancy Cheques
56998 | Lorient Naval
57645 | Montoy Flanville
57998 | Metz Armees
59076 | Retours 3 Suisses
59081 | Retours Redoute
59140 | Dunkerque
59493 | Villeneuve D Ascq
59650 | Villeneuve D Ascq
59900 | Lille Cheques
59998 | Lille Armees
60149 | St Crepin Ibouvillers
63900 | Clermont Ferrand Cheques
67900 | Strasbourg Cheques
68126 | Bennwihr Gare
69001 | Lyon 01
69002 | Lyon 02
69003 | Lyon 03
69004 | Lyon 04
69005 | Lyon 05
69006 | Lyon 06
69007 | Lyon 07
69008 | Lyon 08
69009 | Lyon 09
69125 | Lyon Satolas Aeroport
69125 | Satolas Aeroport
69900 | Lyon Cheques
69998 | Lyon Armees
70301 | Luxeuil Air
74480 | Guebriant
74480 | Plateau D Assy
74730 | Martel De Janville
74780 | Praz Coutant
74790 | Sancellemoz
74810 | Mont Blanc Assy
75055 | Paris Rp
75056 | Paris Rp
75057 | Paris Rp
75058 | Paris Rp
75059 | Paris Rp
75100 | Paris Rp
75195 | Paris Rp
75196 | Paris Rp
75197 | Paris Rp
75198 | Paris Rp
75199 | Paris Rp
75348 | Paris 07 Sp
75349 | Paris 07 Sp
75350 | Paris 07 Sp
75351 | Paris 07 Sp
75352 | Paris 07 Sp
75353 | Paris 07 Sp
75354 | Paris 07 Sp
75355 | Paris 07 Sp
75356 | Paris 07 Sp
75357 | Paris 07 Sp
75358 | Paris 07 Sp
75359 | Paris 07 Sp
75700 | Paris 07 Sp
75800 | Paris
75900 | Paris Cheques
75919 | Paris Concours
76900 | Rouen Cheques
78129 | Velizy Villacoublay Air
80100 | Abbeville
80117 | Bouvaincourt Sur Bresle
83380 | Les Issambres
83800 | Toulon Naval
83898 | Draguignan Armees
83998 | Canjuers Armees
84998 | Apt Armees
86900 | Poitiers Cheques
87900 | Limoges Cheques
93210 | La Plaine Depot Du Landy
93210 | La Plaine St Denis
94390 | Aeroport D Orly
95707 | Roissy Aeroport
95707 | Sagatrans Cooperation
98000 | Monaco
(109 rows)
|
 |
|
|
I have deleted the out-of-date boundary polygons for Poland and replaced them with the new polygons. Enjoy.
Thanks a lot, Pigletto for your help.
Marc
|
 |
|
|