GeoNames Forum

It should be great to have Altitude in city info.

I know that it's possible to get altitude by location using another request, but it will be nice to avoid muching up =)

Time zone is also an extremely useful info.

Hi Denis

The 'cities' file include the full information we have in the other dumps, including elevation and time zone :
Code:

 geonameid         : integer id of record in geonames database
 name              : name of geographical point (utf8) varchar(200)
 asciiname         : name of geographical point in plain ascii characters, varchar(200)
 alternatenames    : alternatenames, comma separated varchar(4000)
 latitude          : latitude in decimal degrees (wgs84)
 longitude         : longitude in decimal degrees (wgs84)
 feature class     : see <a href="http://www.geonames.org/export/codes.html," target="_blank" rel="nofollow">http://www.geonames.org/export/codes.html,</a> char(1)
 feature code      : see <a href="http://www.geonames.org/export/codes.html," target="_blank" rel="nofollow">http://www.geonames.org/export/codes.html,</a> varchar(10)
 country code      : ISO-3166 2-letter country code, 2 characters
 cc2               : alternate country codes, comma separated, ISO-3166 2-letter country code, 60 characters
 admin1 code       : fipscode (subject to change to iso code), isocode for the us and ch, see file admin1Codes.txt for display names of this code; varchar(20)
 admin2 code       : code for the second administrative division, a county in the US, see file admin2Codes.txt; varchar(80) 
 admin3 code       : code for third level administrative division, varchar(20)
 admin4 code       : code for fourth level administrative division, varchar(20)
 population        : integer 
 elevation         : in meters, integer
 gtopo30           : average elevation of 30'x30' (ca 900mx900m) area in meters, integer
 timezone          : the timezone id (see file timeZone.txt)
 modification date : date of last modification in yyyy-MM-dd format

Cheers

Marc

Hi Marc,

Thank you for the quick replay.

Actually I was playing with search web services and didn't get that data with style=long. Now I realized that it's possible to get everything with style=full. Thanks!

One more note about time zones.
It could be useful to have DST transition dates rules in database as well.
I think we could help with it.

In our database we keep it in Microsoft style and it's ok for almost all time zones. But some countries use special rules to define DST transition dates so it's possible to define the rule for one year only (surely it's possible to keep history as well).

It looks like seach and searchJSON return little bit different data.

For example searhJSON doesn't include information about time zone and elevation, but gives more detailed information about alternateNames (name + language).

This is true, I will add the missing data to the JSON service timezone, adminname3 and adminname4. Elevation is already included (if we have elevation information).

As for the alternate names in XML, I will only add them if people ask for it. As long as nobody is asking for it I prefer not to unnecessarily blow up the size of the data transfered.

What is missing in both is gtopo30 elevation and srtm3 elevation. This too will only be added if users are asking for it.

Cheers

Marc

What if it to add an ability exactly specify fields instead of using predefined style. Hmmm =) it's sounds like something close to SQL.

That's very flexible way and it's very good from legacy point of view because it covers any future changes.

You are right Denis. This is a good idea.

Are you or anyone else interested in this functionality?

Cheers

Marc

To be honest this option is not extremally critical for me at the moment, but I just was thinking that it may cover almost all possible needs.