| Author |
Message |
|
|
Thanks, you are right. I will correct it.
Marc
|
 |
|
|
As long as this is a purely theoretical discussion I don't see a need to change anything. We can discuss about other data models when we really have a real life problem and have solved all other problems. At the moment if would be no improvement and would only cause confusion.
Marc
|
 |
|
|
Just because a name occurs many time in a country does not necessarily mean the places don't exist or are duplicates, in the first place it means it is a very popular place name in a country.
Marc
|
 |
|
|
A new sw version has been deployed that allows to enter FAA codes with the pseudo code 'FAAC'.
Best
Marc
|
 |
|
|
The geonames coordinates are in WGS84 (=googlemaps format). There is something wrong with your import script. Did you process it with excel or something similar?
Best
Marc
|
 |
|
|
Thanks. The automatic adm1 assignment had a wrong admin code. It has been fixed.
Best
Marc
|
 |
|
|
Where possible we relate the postal code entries to the places in the main geoname table.
For instance Coogee: http://www.geonames.org/2170697/coogee.html
It is very simple to move a place to its proper location. It is also possible to add postal codes as alternate names using the pseudo language code 'post': http://www.geonames.org/manual.html
From time to time we will update the coordinates in the postal code table with the corrected/improved coordinates from the place table.
The centroids have been used to update those postal code lat/lng that do not have a match in the place name table or where the distance is more than just some 100m. For Coogee and many others the distance is less than some 100m and the coordinates from the geoname table are used.
Marc
|
 |
|
|
It is not one way or the other, it depends on the data available for a postal code. The column 'accuracy' gives an indication of how accurate the lat/lng for a postal code is.
For lack of other data in most cases it derived from the lat/lng of the corresponding city.
postal code - city name co-occurence is only used to determine the sort order. Combinations that have more hits on searches rank higher than combinations with lesser hits.
Marc
|
 |
|
|
There are a lot of services on the geonames site. If you don't specify which service you are speaking of it is difficult to help. In any case, for most services there are already discussions on this forum about implementation and performance issues.
Best
Marc
|
 |
|
|
Hi Marlies
I think I have found and fixed a potential cause for this failure. Let's hope it really was it and it does not occur again.
Best
Marc
|
 |
|
|
Thanks Jerome. It is fixed. ('Tokyo' was missing the 'preferred' flag)
Marc
|
 |
|
|
I cannot see any reference to 661485 in the country file.
The geonameId mentionend in the country file 6697173 is correct (feature class A = country/territory).
It could be discussed whether 6632699 is required as feature class L or whether it could be deleted.
There is also an entry for the continent with geonameId 6255152
Best
Marc
|
 |
|
|
Hi Marlies
The indexer stopped working at ca 11:34, I don't know yet what is causing this interruption every now and then.
I have manually recreated the search index from scratch.
Best
Marc
|
 |
|
|
"Monte Alegre" was a duplication in the middle of the ocean. I have deleted it.
"Aoraki - Mount Cook Airport" had a timezone in the database, but for some reasons it was not included in the search index and not returned by the web service. I have recreated the search index from scratch.
Marc
|
 |
|
|
Thanks.
We have updated the postal code database with the missing postal codes.
Marc
|
 |
|
|
Thanks, the configuration of this service on one of the servers was not correct.
Marc
|
 |
|
|
Thanks, the names have been corrected.
Marc
|
 |
|
|
You are not hitting a limit. There must be something else causing the problem. The server does not seem to be too busy lately (after the offline period earlier this week this means), so I doubt it is a server problem.
Best
Marc
|
 |
|
|
The fastest and simplest way is to just fix it:
http://www.geonames.org/manual.html
Marc
|
 |
|
|
For 01150 - Sainte-Julie I get this response by both free and commercial service:
http://ws.geonames.org/postalCodeSearch?placename=01150+Sainte-Julie&maxRows=10&style=full
For 78111 I am getting "Dammartin En Serve":
http://ws.geonames.org/postalCodeSearch?placename=78111&maxRows=10&style=full&country=FR
The same result is returned by the French Postal code service:
http://www.laposte.fr/Particulier/Utilisez-nos-outils-pratiques/Outils-et-documents/Trouvez-un-code-postal
|
 |
|
|