On 03/07/11 19:49, Tomas Straupis wrote:
2011-03-07 Steve Ratcliffe:
Is that using code-page or charset?
I would not expect --charset to work.
Yep. Changing to
--code-page=1257
fixes Lithuanian letters!
hmm. i might be doing something wrong... but --code-page=1257 with
mkgmap
2011-03-09 WanMil:
* The mkgmap:country, addr:country and is_in:country tag is now always
assigned with the three letter country code. This makes it possible to
define country specific rules in the style files.
Three letter not two?
Most (all) addresses in Lithuania have addr:country=LT...
Am 09.03.2011 12:51, schrieb Tomas Straupis:
2011-03-09 WanMil:
* The mkgmap:country, addr:country and is_in:country tag is now always
assigned with the three letter country code. This makes it possible to
define country specific rules in the style files.
Three letter not two?
Most
On Wed, Mar 09, 2011 at 01:45:02PM +0200, Rich wrote:
Yep. Changing to
--code-page=1257
fixes Lithuanian letters!
hmm. i might be doing something wrong... but --code-page=1257 with
mkgmap 1867 still results in garbled latvian characters.
Do you have an example? Can you check the file
Hi,
Here is an updated version with the following fixes/improvements:
* correctly set registry key for TYP file
* set registry key for index files only when present
* possibility to use own template for installer script (details below)
* installer localization (English and French at the moment)
On 03/09/11 14:26, Marko Mäkelä wrote:
On Wed, Mar 09, 2011 at 01:45:02PM +0200, Rich wrote:
Yep. Changing to
--code-page=1257
fixes Lithuanian letters!
hmm. i might be doing something wrong... but --code-page=1257 with
mkgmap 1867 still results in garbled latvian characters.
On Wed, Mar 09, 2011 at 04:02:38PM +0200, Rich wrote:
so it might be that the file has properly encoded characters, but the
device does not properly display them ?
That is a possibility. Do the older Garmins (such as GPSMap 60 and Edge
605/705) support anything else than the ISO 8859-1 like
On 03/09/11 17:00, Marko Mäkelä wrote:
On Wed, Mar 09, 2011 at 04:02:38PM +0200, Rich wrote:
so it might be that the file has properly encoded characters, but the
device does not properly display them ?
That is a possibility. Do the older Garmins (such as GPSMap 60 and Edge
605/705) support
Splitter keys:
java -Xmx1200m -jar splitter170.jar ^
--cache=.\splitterCache\ ^
--geonames-file=cities1000.zip ^
--overlap=2 ^
--max-nodes=100 ^
--no-trim ^
full.osm
(full.osm - http://gis-lab.info/data/osm/full.osm.bz2)
mkgmap keys:
java
I've tried downloading Latvian extract from geofabrik and creating a map.
I then browsed through Riga and haven't noticed any problems (using
Colorado). I do see Latvian letters properly...
P.S. Note that Lithuanian letters (and the same should apply to
Latvian ones) does NOT work on GPSMAP
On 03/09/11 18:31, Tomas Straupis wrote:
I've tried downloading Latvian extract from geofabrik and creating a map.
I then browsed through Riga and haven't noticed any problems (using
Colorado). I do see Latvian letters properly...
P.S. Note that Lithuanian letters (and the same should apply
2011-03-09 Rich:
i... don't like vista hcx being mentioned in that list :)
do you have any source for this info ?
I've placed a map on the internet and asked people to send me an
e-mail telling if they see Lithuanian letters or not. That is the
source of above-mentioned information...
--
It's the default style file and my changes are contained in the patch.
WanMil
Can you provide your style-file?
Thx
Am 08.03.2011 um 23:07 schrieb WanMilwmgc...@web.de:
Next round of the location improvements:
* The algorithm that searched which elements were contained within a
boundary
Am 09.03.2011 13:22, schrieb Chris66:
Am 09.03.2011 12:51, schrieb Tomas Straupis:
2011-03-09 WanMil:
* The mkgmap:country, addr:country and is_in:country tag is now always
assigned with the three letter country code. This makes it possible to
define country specific rules in the style files.
Splitter keys:
java -Xmx1200m -jar splitter170.jar ^
--cache=.\splitterCache\ ^
--geonames-file=cities1000.zip ^
--overlap=2 ^
--max-nodes=100 ^
--no-trim ^
full.osm
(full.osm - http://gis-lab.info/data/osm/full.osm.bz2)
mkgmap keys:
java
I have created a new branch for the automatic locator changes.
It can be downloaded from http://www.mkgmap.org.uk/snapshots/
WanMil
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Am 09.03.2011 16:10, schrieb Rich:
On 03/09/11 17:00, Marko Mäkelä wrote:
On Wed, Mar 09, 2011 at 04:02:38PM +0200, Rich wrote:
so it might be that the file has properly encoded characters, but the
device does not properly display them ?
That is a possibility. Do the older Garmins (such as
Hi,
I'd like to see it commited because I want the old layout of the map back.
I don't like the 'a quick and dirty approach', the map looks very ugly now at
lower zoom
levels, shapes look very distorted and forests are completely gone.
Am 08.03.2011 14:57, schrieb Minko:
Hi Johann,
Is this
El 08/03/11 23:07, WanMil escribió:
Next round of the location improvements:
* The algorithm that searched which elements were contained within a
boundary was (is) wrong. I updated some parameters in the Quadtree so
I the probability is very much lower that an element is not assigned
Could this patch be included?
I really think maps in Western Europe (where most mkgmap users are) look
much better on a) old GPS like etrex b) street units like Nuvi 255W or
c) Mapsource/Basecamp/Qlandkarte GT.
About 2 month ago the resolutions for POI got lowered to sensible
defaults (they
charset:cp1251
make-poi-index
block-size=1024
I did a test without those keys. Mapsource error is still here.
Prior to version 1879 I used 1866, in which this problem does not occur.
--
View this message in context:
I found the cause of the problem. This is a --lower-case key! Without it,
Mapsource creates gmapsupp.img file correctly.
--
View this message in context:
http://gis.638310.n2.nabble.com/Commit-r1879-Handle-relations-with-type-boundary-as-multipolygons-tp6086268p6155965.html
Sent from the Mkgmap
Thanks for jar file. Now to report my test results:
I uploaded the map via Garmin MapInstall search for Address and
Intersections. I get a No Data Available
Using: mkgmap-locator-r1892.jar
Args.list:
ode-page=1252
tdbfile
latin1
country-abbr=PHL
country-name=PHILIPPINES
remove-short-arcs=5
23 matches
Mail list logo
