Messages

I agree that it would be great to have some variables together with the map but also an own customizable screen with all the other informations...

I just tested the new 1.6.1 and noticed something strange...
I have a part of a map saved for offline use. When I move this map now, it's a bit choppy. But moving the same part online is very smooth (except when loading missing tiles of course). Is in the new version something different?

Quick switch is cool... and I'm sure that there are soon several more things which can be added to the quick switch...

Where can I see at once whether I'm in online mode or not? Maybe there could be added a small dot red/green for offline/online?

I just want to start the discussion for a customizable screen in Locus. There is an app called TrekBuddy and there is this screen called CMS. The app provides all the GPS variables and the user can decide in what way this data should be displayed on the screen. Here is a sample (//http://wiki.trekbuddy.net/index.php/CMS) how it looks like... The first picture in blue colors is an old version of my cms...

Such a screen would be great to see in Locus.
What do you think about it???

Here we go... this is the last cms which I created for TrekBuddy. I had TrekBuddy running on an old NOKIA 6300 mobilephone... Meanwhile many of the cms are using my graphics and ideas. I had no problem with this but some used almost my whole artwork and "sold" it as their artwort and this is not ok...

//http://www.trekbuddy.net/forum/viewtopic.php?t=2923

Hi Menion!

I have one BIG wish and I think that there is not much coding necessary because it's just a "search function"...    Can you PLEEEEEAAAASE add support for GeoNames??? At //http://www.geonames.org/ you can download the placenames of all countries free of charge! For each country there exist an own file with the data. It's a simple txt-file... For every cityname there are several fields and also the latitude and longitude (in decimal degrees (wgs84)). So it would be easy to search for a city and place the map to the desired coordinates  . And this search could be done OFFLINE...

Menion, please think about it... this feature would push Locus again one step ahead of all other (offline) map apps!  8-)

@all Locus users
If you find this idea of an offline search  using GeoNames data usefull, then post it here to show Menion that this would be great and he gets an encouragement to add this soon...  

Locus is a funtastic app and therefore I bought the pro version. Thanks!!!


----------------------------------------------------------------------------
Here ist the readme from GeoNames...
----------------------------------------------------------------------------



Readme for Geonames.org :
=========================

This work is licensed under a Creative Commons Attribution 3.0 License,
see http://creativecommons.org/licenses/by/3.0/
The Data is provided "as is" without warranty or any representation of accuracy, timeliness or completeness.

The data format is tab-delimited text in utf8 encoding.


Files :
-------
XX.zip                   : features for country with iso code XX, see 'geoname' table for columns
allCountries.zip         : all countries combined in one file, see 'geoname' table for columns
cities1000.zip           : all cities with a population > 1000 (ca 80.000), see 'geoname' table for columns
cities5000.zip           : all cities with a population > 5000 (ca 40.000), see 'geoname' table for columns
cities15000.zip          : all cities with a population > 15000 (ca 20.000), see 'geoname' table for columns
alternateNames.zip       : two files, alternate names with language codes and geonameId, file with iso language codes
admin1Codes.txt          : names for administrative subdivision 'admin1 code' (UTF8), the code '00' stands for 'unkown code', includes obsolete codes
admin1CodesASCII.txt     : ascii names of admin divisions. (beta > http://forum.geonames.org/gforum/posts/ ... .page#1143)
admin2Codes.txt          : names for administrative subdivision 'admin2 code' (UTF8), Format : concatenated codes <tab>name <tab> asciiname <tab> geonameId
iso-languagecodes.txt    : iso 639 language codes, as used for alternate names in file alternateNames.zip
featureCodes.txt         : name and description for feature classes and feature codes
timeZones.txt            : timezoneId, gmt offset on 1st of January, dst offset to gmt on 1st of July (of the current year)
countryInfo.txt          : country information : iso codes, fips codes, languages, capital ,...
                           see the geonames webservices for additional country information,
                                bounding box                         : http://ws.geonames.org/countryInfo?
                                country names in different languages : http://ws.geonames.org/countryInfoCSV?lang=it
modifications-<date>.txt : all records modified on the previous day, the date is in yyyy-MM-dd format. You can use this file to daily synchronize your own geonames database.
deletes-<date>.txt       : all records deleted on the previous day, format : geonameId <tab> name <tab> comment.

alternateNamesModifications-<date>.txt : all alternate names modified on the previous day,
alternateNamesDeletes-<date>.txt       : all alternate names deleted on the previous day, format : alternateNameId <tab> geonameId <tab> name <tab> comment.
userTags.zip      : user tags , format : geonameId <tab> tag.
hierarchy.zip      : parentId, childId, type. The type 'ADM' stands for the admin hierarchy modeled by the admin1-4 codes. The other entries are entered with the user interface. The relation toponym-adm hierarchy is not included in the file, it can instead be built from the admincodes of the toponym.


The main 'geoname' table has the following fields :
---------------------------------------------------
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(5000)
latitude          : latitude in decimal degrees (wgs84)
longitude         : longitude in decimal degrees (wgs84)
feature class     : see http://www.geonames.org/export/codes.html, char(1)
feature code      : see http://www.geonames.org/export/codes.html, 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), see exceptions below, 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        : bigint (8 byte int)
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


AdminCodes:
Most adm1 are FIPS codes. ISO codes are used for US, CH, BE and ME. UK and Greece are using an additional level between country and fips code.



The table 'alternate names' :
-----------------------------
alternateNameId   : the id of this alternate name, int
geonameid         : geonameId referring to id in table 'geoname', int
isolanguage       : iso 639 language code 2- or 3-characters; 4-characters 'post' for postal codes and 'iata','icao' and faac for airport codes, fr_1793 for French Revolution names,  abbr for abbreviation, link for a website, varchar(7)
alternate name    : alternate name or name variant, varchar(200)
isPreferredName   : '1', if this alternate name is an official/preferred name
isShortName       : '1', if this is a short name like 'California' for 'State of California'


Remark : the field 'alternatenames' in the table 'geoname' is a short version of the 'alternatenames' table without links and postal codes but with ascii transliterations. You probably don't need both.
If you don't need to know the language of a name variant, the field 'alternatenames' will be sufficient. If you need to know the language
of a name variant, then you will need to load the table 'alternatenames' and you can drop the column in the geoname table.



Statistics on the number of features per country and the feature class and code distributions : http://www.geonames.org/statistics/


Continent codes :
AF : Africa         geonameId=6255146
AS : Asia         geonameId=6255147
EU : Europe      geonameId=6255148
NA : North America      geonameId=6255149
OC : Oceania      geonameId=6255151
SA : South America      geonameId=6255150
AN : Antarctica      geonameId=6255152


If you find errors or miss important places, please do use the wiki-style edit interface on our website
http://www.geonames.org to correct inaccuacies and to add new records.
Thanks in the name of the geonames community for your valuable contribution.

Data Sources:
http://www.geonames.org/data-sources.html


More Information is also available in the geonames faq :

http://forum.geonames.org/gforum/forums/show/6.page

The forum : http://forum.geonames.org

or the google group : http://groups.google.com/group/geonames

hmm I was think about it and I think this leads to little bit "too complicated app" and I don't want this. I have one old plan to create customizable screen where you should place some stats to view on display, do ... I hope I'll do it one time

Hi Menion!  A customizable screen would be great, like the CMS in TrekBuddy. I did a lot of artwork there   . Such a screen in Locus would be funtastic. Also some variables like speed, average speed, distance and travelled time would be very, very good to have it together with the displayed map. It should be like a menue which could be optionally displayed.

I think many users would like to see these two features...