.
Ticker
On Fri, 2024-04-05 at 16:08 +0100, Ticker Berkin wrote:
> Hi Gerd
>
> Looking at the svn log it seems that the man page splitter.1 which is in groff
> format can be generated from splitter.1.xml which is in DocBook XML format. I
> can't be bothered to install and try this so I
> I've committed r654 for now. Not sure what to do with your version of
> splitter.txt.
>
> Gerd
>
>
>
> ____
> Von: mkgmap-dev im Auftrag von Ticker
> Berkin
> Gesendet: Freitag, 5. April 2024 12:09
> An: Develop
Hi Gerd
The unix man entry looks fine
$ man -l ${splitterSvn}/trunk/doc/splitter.1
but I don't know how anyone would be expected to find and use it unless it gets
installed with the other man pages
dist/doc/splitter.txt and .html generated with mwconf from doc/splitter.txt are
attached; I
Hi Joao
The default style has logic at the end of the "lines" file to use road numbers
(ref) in various highway-symbol shields and also to use the multiple name
facility to then allow specification of the name and other references for
searching.
If you don't want this then the logic could be
nd my own typ file,
> when does garmin do something differently than what I expect?
>
>
> On 1/30/24 02:39, Ticker Berkin wrote:
> > Hi Brad
> >
> > Lines like this follow the type code and, as a comment, describe the
> > standard
> > Garmin usage, eg:
Hi Brad
Lines like this follow the type code and, as a comment, describe the standard
Garmin usage, eg:
...
[_polygon]
type=0x02
;GRMN_TYPE: Urban Areas/SMALL_CITY/Small urb...nts/Non NT
String=Suburb
String1=0x01,Résidentiel
...
Ticker
On Mon, 2024-01-29 at 17:43 -0700, brad wrote:
> I was
Hi
The disadvantage of using extended points is that none are findable.
I've had trouble with 0x2b (Lodgings) points showing or not on different devices
(eTrex HCx & eTrex 30x) and software and some subtype# not being findable on
different devices.
HCx has Lodgings (0x2b) "Find" categories:
Hi Karl
You could simply not match it in "polygons" but render the lines that define it.
Alternatively, what I do, is catch it early in "polygons" to render it but with
[... continue] and render it striped/transparent with a high _drawOrder.
[_polygon]
Type=0x16
String=Nature Reserve
Xpm="32 32
Sorry - should say ... {tag|subst: ...
Ticker
On Wed, 2023-12-13 at 10:18 +, Ticker Berkin wrote:
> Hi Diego
>
> On the issue of case, your build is probably running without --lower-case, so
> everything in the .img file is UPPER. The Garmin device then initcaps stuff in
>
Hi Diego
On the issue of case, your build is probably running without --lower-case, so
everything in the .img file is UPPER. The Garmin device then initcaps stuff in a
way of its own choosing.
Use of --lower-case can cause problems and unknowns with the index system where
there are different
wrote:
> > Hi Ticker,
> >
> > please can you provide a unit test for this?
> >
> > Gerd
> >
> > ____
> > Von: mkgmap-dev im Auftrag von
> > Ticker
> > Berkin
> > Gesendet: Donnerstag, 12. Okto
Ticker,
> >
> > if you don't mind I'd like to postpone this patch until the active branches
> > are merged into
> > trunk.
> >
> > Gerd
> >
> >
> > ________
> > Von: mkgmap-dev im Auftrag von
&g
Hi Gerd
Looking at the code, there shouldn't be any crash from mkgmap if a contour line
doesn't have an
"ele" tag. I assume the Garmin device will just draw the appropriate line
without a label. This
might be common where alternate contours are not given heights.
So, no; I don't think you
Hi Diego
If you use the --gmapi mkgmap option it will make the folder (named with
--family_name option)
and contents, including Info.xml
Ticker
On Tue, 2023-10-10 at 15:15 +, helter skelter wrote:
> Hello guys
> When I create the map for Basecamp, I get a folder under
>
Hi Gerd
I've looked through all the places I could find that took [highPrec]coord vals,
manipulated them
and then converted back and they all seem safe with my patch.
There might be slight differences where, using Java2DConverter or similar, a
calculated value
converts to a different/adjacent
Hi Gerd
Sorry - bit hasty in my reply
I need to look at the other places that use DELTA_SHIFT and check their
arithmetic/rounding etc
is consistent with the corrected highPrecCoord and uniform in rounding
behaviour.
Ticker
On Fri, 2023-10-06 at 16:15 +0100, Ticker Berkin wrote:
> Hi G
Hi Gerd
My change to toMapUnit should be almost undetectable. Imagining mapUnits [x] as
degrees over the
real range -2.5 .. +2.5, the original implementation resulted in:
-2.5 < [-2] <= -1.5 < [-1] <= -0.5 < [0] < -0.5 <= [1] < +1.5 <= [2] <
+2.5
I've changed it to give:
-2.5 <= [-2] <
at 16:37 +0100, Ticker Berkin wrote:
> Hi Gerd
>
> I've changed the way mapUnit and highPrec Coords are calculated slightly so
> that the exact 1/2
> unit boundary values are consistent between negative and positive. This gets
> rid of my couple
> of
> abnormalities with a -
hich
> makes use of the
> coord pool.
> No idea which one has more effects on performance.
>
> Gerd
>
>
>
>
>
> Von: mkgmap-dev im Auftrag von
> Ticker Berkin
>
> Gesendet: Mittwoch, 4. Oktober 2023 15:
rd is
> converted back but
> get's the other extreme. In the end, only the 24 bit value is written to the
> map, and that
> causes the gap.
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag von
> Ticker Berkin
>
> Gesendet: Mon
Hi Gerd
Considering no_hp-overflow_alpha.patch:
It seems wrong to change a 24bit coordinate. Utils.toMapUnit() is well defined
to do the
expected rounding with the conversion.
The actual deltas are local to Coord.java and, apart from their use by
getAlternativePositions,
are just used to get
Hi
I was thinking that gaps like this could often happen when adjacent polygons
share the points
along the common boundary, but, during the various point-removal optimisations,
esp. Douglas
Peucker, different points along this boundary are chosen to represent the 2
polygons.
Regarding
Hi Joao
There isn't a way to change the type of the background polygon/area of map
coverage.
Can you disable the night-mode switching in your device?
Can you define the rendering for the 0x4b polygon in your typ-file, with both a
day and night
mode?
Transparent maps don't set the background.
Hi
You need to have ... --input-file=otm-hungary.img ... to fix the file
doesn't exist errors.
I have no idea if the rest of what you are asking for will work.
Ticker
On Thu, 2023-07-13 at 16:35 +0200, Tamas Gal wrote:
> Hi all,
>
> maybe I got that wrong but I thought I can merge multiple
Hi Diego
It is probably better to have something like this in "lines":
natural=valley & is_closed()=false [0x12005 resolution 21]
then the rule won't be triggered for closed ways and will be passed on
to "polygons" processing:
natural=valley [0x10f09 resolution 21]
If you wanted both line and
Hi Carlos
The first message is related to forming subdivisions that obey all
required restrictions:
(area.getNumLines() > MAX_NUM_LINES
|| area.getNumPoints() > MAX_NUM_POINTS
|| (sizes[MapArea.POINT_KIND] + sizes[MapArea.LINE_KIND]) >
MAX_RGN_OFFSET_SIZE
Hi Gerd
The added comments are helpful but overall I think the readability is
worse; it takes careful reading to see where the dp filter is placed.
If other tweaks to different orderings between normal and parallel
chains are necessary it will become even more confusing.
Ticker
On Mon,
ter?
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Sonntag, 4. Juni 2023 10:15
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] Error processing tile
>
> Hi Gerd
>
> Reali
cker
Forwarded Message
From: Ticker Berkin
To: Development list for mkgmap
Subject: Re: [mkgmap-dev] Problems with sea in overview map
Date: Fri, 21 May 2021 17:10:07 +0100
Hi Gerd
I'd been doing some investigation of filters ordering (based on trunk).
I'd also done the pre-filte
nit tests need changes. Please check if
> my changes are plausible. Something might be wrong on my system
> because SimpleRouteTest failed also without your patch.
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> G
Hi
Sorry - this isn't the correct explanation.
Reducing MapSplitter.MAX_NUM_LINES fixes the problem but there must be
something else going on that adds 1 more line. I'll investigate a bit
more.
Ticker
On Fri, 2023-06-02 at 16:47 +0100, Ticker Berkin wrote:
> Hi Gerd & Carlos
>
&g
Hi Gerd & Carlos
I've found the problem and attach a patch which reduces the Subdivision
line limit to 254.
Subdivisions/areas have a set of limits, one of which was <= 255 lines.
These lines can be of any type including roads. When --route, a
reference to each line/road part is created, but
Forgot to mention access=customers or similar, which might cause
mkgmap:throughroute=no
Ticker
On Thu, 2023-06-01 at 10:50 +0100, Ticker Berkin wrote:
> Hi
>
> Things to check:
>
> Have you set 'allow tolls' on your routing options - most ferries
> cost.
>
> Ferry po
Hi
Things to check:
Have you set 'allow tolls' on your routing options - most ferries cost.
Ferry ports can have complicated road systems with barriers, gates,
one-way systems, service roads, parking/holding lots etc; it can
require very careful checking to see that there is a valid route
Hi Carlos
I've tried this on my latest build which is r4907 + quite a few other
changes and I don't get the problem, but using an older, downloaded,
version I can reproduce it.
My changes don't look relevant to this issue; mainly character set
issues and some line/polygon filter reordering.
Hi Frank
Some quick comments:
1/ Whatever you need to do to make it run on old versions of Java.
2/ I've always used the pre-build bounds-latest.zip file from
https://www.mkgmap.org.uk/download/mkgmap.html
which redirects to the site you mention.
This global file is designed to avoid
Hi Thomas
Have you looked at the code and output from the mkgmap display tool? It
was available for svn at
https://svn.mkgmap.org.uk/mkgmap/display
but I can't access it at the moment
Ticker
On Wed, 2023-03-15 at 19:57 +0100, tho...@ankarsvik.nu wrote:
> Hi,
>
> Sorry if this is slightly of
Hi Diego
If you get 'incomplete multipolygon relation' errors from the splitter,
for significant areas to be rendered, it is quite likely that you get
the effects you see. I don't know if the splitter makes any attempt to
complete the polygon along the edge of input area, but I suspect not as
Hi Felix
Your syntax looks correct, but, given that the example WAY you quote is
a private driveway, I'd suspect the settings of hgh:*, being set to
meet these conditions for the way in question and the road and wall
Ticker
On Sun, 2023-03-05 at 22:35 +0100, Felix Herwegh wrote:
> Hi,
> I seem
tour/Non NT
> 0x02400=Contour Lines/INT_BATHY_CONTOUR/Intermediate bathymetric, or
> depth, contour (should be used for about every 5th contour line)/Non
> NT
> 0x02500=Contour Lines/MAJOR_BATHY_CONTOUR/Major bathymetric, or
> depth, contour (should be used for about every 10th contou
Hi
My understanding of the default Garmin usage is that
0x20..0x22 are land/height contours (Minor to Major)
0x23..0x25 are sea/depth ""
Ticker
On Thu, 2023-03-02 at 08:52 +, Gerd Petermann wrote:
> Hi Vadim,
>
> I see code in mkgmap to handle the statement with Elevation=m or
Hi
0x11 is rendered as a thin black line on my eTrex HCx and a white line
on my eTrex 30x
Ticker
On Sun, 2022-11-27 at 17:35 +, ael wrote:
> On Sun, Nov 27, 2022 at 04:13:44PM +, Gerd Petermann wrote:
> > Hi ael,
> >
> > the "default typ" is the one that comes with the firmware of the
Hi
Looking at common values for this, I'm going to have:
tourism=information & (
information=office | information=visitor_centre |
information=board | information=map
) {add name='${information}'} [0x4c00 resolution 24]
I think it is bad that "points" does include 'inc/name' so
Hi Steve
Assuming you haven't overridden the default style, these boundary lines
are triggered by:
boundary=administrative {name '${mkgmap:boundary_name}'}
boundary=administrative & admin_level<3 [0x1e resolution 12]
boundary=administrative & admin_level<5 [0x1d resolution 19]
Hi John
Adding to what Thorsten has written:
It can be impossible to reliably deduce what should be sea when just
using the coastline data from within an OSM area extract. The extract
area is expanded to be within a set of rectangular tiles and, as a
result of this, coastline data might just
Hello Raphael
I'm not quite sure what you mean but the variable mkgmap:label:1 put
the label information into the map. This can be set directly and the
name command also sets it
The default style has, in the section of
points/lines/polygons, the command:
name=* {name '${name}'}
Ticker
On
Hi Andrez
On Tue, 2022-05-31 at 00:23 +0200, Andrzej Popowski wrote:
> Hi Ticker!
>
> > I don't get a crash
>
> Maybe there are other factors? I'm using AMD Ryzen, Windows 10,
> OpejJDK
> 18.0.1 (just have updated, 17.02 worked the same). I can create a set
> which cause crash, if you are
Hi
Firstly:
I don't get a crash from:
if (mkgmap:style-option:test=true) then
() echo {"test"}
end
with or without --style-option=test.
Also, don't you mean "... mkgmap:option:test ..."
Next:
The "test" part of a rule must contain at least 1 "positive" limiting
clause, as per the
ble the partitioning in class MultiPolygonRelation.
> I've not yet understood why, but I fear your patch simply works
> around this problem.
> The partitioning seems to produce parts where an inner and an outer
> rectangle both seem to cover the same area.
> I think I have to fix that as
Petermann wrote:
> Hi Ticker,
>
> thanks, I'll take a look at it. My understanding was that
> SeaGenerator should produce an outer way which is slightly larger
> than the tile.
> Did I change that?
>
> Gerd
>
>
> Von: mk
Hi Gerd
I've just rebuilt britain-and-ireland-latest.osm.pbf with the current
trunk and find that many tiles on the coast have flooded rectangles.
The coastline is all correct and these flooded area are normally well
inland and unrelated to where the coastline crosses the tile boundary.
I use
Hi
The * needs to be quoted in the param list:
boundary=* & ... & is_in(boundary, '*', ...
Ticker
On Wed, 2022-04-06 at 13:02 +, lig fietser wrote:
> I also want to use it for all boundaries but this line is not
> working:
> boundary=* & mkgmap:area2poi=true &
Hi
I don't see a way to control the placement of the POI for a
multipolygon; it sets it to the centre point of the biggest area.
You could suppress the POI if it isn't within the area by using the
is_in() function, something like:
tag=value & mkgmap:area2poi=true & is_in(tag, value,
re less important I guess.
>
> Kind regards,
> Joris
>
>
>
>
> -Oorspronkelijk bericht-
> Van: mkgmap-dev Namens
> Ticker Berkin
> Verzonden: vrijdag 18 maart 2022 18:59
> Aan: Development list for mkgmap
> Onderwerp: Re: [mkgmap-dev] Update o
Hi Joris
My opinion is that using TYPViewer to edit the the mkgmap held typ-
files is too dangerous; it deletes language strings it can't cope with
and makes textual changes that make it very difficult to see the actual
difference between versions.
Unless TYPViewer supports and generates a
Hi Gerd
Fantastic work.
I've never see any effect of having a Mdr6 section (where the zips end
up) either from mkgmap or any zip searching ability from a GARMIN NT
map; both of which had MDR 6 sections.
Ticker
On Wed, 2022-03-16 at 15:55 +, Gerd Petermann wrote:
> Hi devs,
>
> one of the
derstanding is that you had some mistagged OSM ways which happened
> to have
> a barrier node which probably also missed proper access tags.
> Adding a special rule for those is likely to cause trouble somewhere
> else.
>
> Gerd
>
>
f the way and I don't see how this is related.
>
> Let's see if anybody else wants this.
>
> Gerd
>
>
>
>
>
>
>
>
> ________
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Donnerstag, 17. Februa
else wants this.
>
> Gerd
>
>
>
>
>
>
>
>
> ________
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Donnerstag, 17. Februar 2022 13:39
> An: Development list for mkgmap
> Betreff: Re: [mkgmap-dev] option link-pois-
:11 +, Gerd Petermann wrote:
> Hi Ticker,
>
> with examples I meant links to OSM ways.
>
> My current understanding is that these OSM ways may need different
> tagging.
>
> Gerd
>
>
> Von: mkgmap-dev im Auftra
ker,
>
> I don't see a problem with the patch, but I also don't see how it
> solves a problem
> with wrong routing.
>
> Please give me some examples for highways where this would help.
>
> Gerd
>
>
>
> ____
> Von: mkgmap-dev
Ticker
On Tue, 2022-02-15 at 16:41 +, Ticker Berkin wrote:
> Hi Gerd
>
> highway=street_lamp was just an example of a POI that can get linked
> to
> a WAY that can be ignored. There are others that are valid OSM
> tagging
> that are irrelevant to the highway behaviou
:25 +, Gerd Petermann wrote:
> Hi Ticker,
>
> reg. routing problems in Basecamp: Maybe you hit the problem
> described for --max-routing-island-len?
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Ges
error in the map data produced by mkgmap
> or maybe you used wrong routing settings. Please let me know how to
> reproduce.
>
> No idea if your proposed change would improve routing, but feel free
> to experiment with that.
>
> Gerd
>
> _____
Hi all
To improve routing, I'd like to get information about the POIS that are
being linked to a WAY that can be used as part of the style/lines
processing.
The problem I'm trying to solve is to restrict car routing through some
types of very low level roads (eg service) when there is a barrier.
ield instead of
> ignoring them.
> I am not aware of any code in mkgmap that reads or fills those
> bits,yet.
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Samstag, 12. Februar 2022 15:19
>
Hi Gerd
Reading it more carefully, probably the basic flag set is 16 bits, with
0x0100 indicating more bytes to read/write
Ticker
On Sat, 2022-02-12 at 12:36 +, Ticker Berkin wrote:
> Hi Gerd
>
> Although the comment might have inaccuracies and be ambiguous, it
> con
Hi Gerd
Although the comment might have inaccuracies and be ambiguous, it
contains useful information about how the extra flags for POI might be
represented, which could be different from just reading 4 bytes.
One way of interpret it is if (first byte & 0x80), then read/write
extra bytes; the 3
Hi Gerd
I feel there are too many disparate and significant changes in mdr2 to
merge it into trunk in 1 go. Is it possible do a topic at a time,
starting with the least likely to cause problems, leaving time between
for any problem to emerge?
Ticker
On Thu, 2022-02-10 at 11:35 +, Gerd
Hi Gerd
Patch attached to fix MdrSummary readHeaderLen, cope with different hdr
lengths more clearly and improve output.
I've found I can now split my old "City Navigator Europe NT" map and
look at the MDR, which includes sections 30/31, 32/33, 34, 37 & 38
codePage=1252 id1=18 id2=1 unk=0x0011
Hi Gerd
Subdivision.write needs adjusting to merge startRgnPointer and
getType()
MAX_RGN_OFFSET_SIZE limits to 16 bits rather than 24 so probably not be
directly related.
The 24 to 28 bit increase presumably covers all the subdivisions in the
tile and so should allow larger maps. I didn't
Hi Gerd
I looked more carefully after your last post and I agree; except "p"
increases when the partialString is at the end and "s" when at the
start.
There were some cases that confused, but I think these were mostly
where there was a 0x1f (zoomSuffix) in the string; p & s > 1.
I notice that
changes, so please double check.
>
> Gerd
>
>
>
>
>
> Von: mkgmap-dev im Auftrag von
> Ticker Berkin
> Gesendet: Mittwoch, 26. Januar 2022 18:12
> An: mkgmap development
> Betreff: [mkgmap-dev] Style Manual correctio
Hi Jose
GPSMapEdit from
https://www.geopainting.com/
can tell you some of this. The free version should do; install it and
open gmapsupp.img or an individual tile. Then look at Map Properties >
Statistics tab.
Ticker
On Thu, 2022-01-27 at 15:31 +0100, jose1711 wrote:
> Hello,
> can someone
Hi Gerd
Attached is patch for Style Manual:
1/ Keep |not-contained filter example within the page.
2/ Fix the highway-symbol documentation to agree with the code.
3/ Describe road_class more accurately; consistent with default style.
4/ Adjust various table widths to stop some long, unbreakable
ut have now realised that the example has been truncated.
Regards,
Mike
-Original Message-
From: Ticker Berkin [mailto:rwb-mkg...@jagit.co.uk]
Sent: 25 January 2022 15:03
To: Development list for mkgmap
Subject: Re: [mkgmap-dev] tag value within regular expression
Hi Mike
Would the tag filter
Hi Mike
Would the tag filter not-contained (4.4.1) do the job?
Ticker
On Tue, 2022-01-25 at 13:51 +, Mike Baggaley wrote:
> Hi,
>
> Section 4.2.3 of the style manual shows how to compare the values of
> two
> tags, but does not indicate whether it is possible to use tag values
> within
> a
I don't know any
> site which still offers a download.
> Can't you just write code to fill 32/33 or and see if it has the
> effect that you expect?
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: S
Hi Gerd
When I looked at this (not very closely) a couple of weeks ago, it
seemed as if LBL could be huffman encoded, with ENCODING_FORMAT set to
11, and the decoding table somewhere in RGN
Ticker
On Tue, 2022-01-25 at 08:10 +, Gerd Petermann wrote:
> Hi Steve,
>
> if I got that right
Hi Gerd
Looking at the mask logic in MdrDisplay printSect30/32 I'd guess that
the pointer size is always governed by the size of Mdr31/33 and any
extra bytes are something else, probably the length of the string.
I've haven't managed to find any maps with these sections so I can't be
sure. How
| |
> | | | Record 842
> 001a1d3a | 002423 | 13 | 19 map number
> 001a1d3b | 002424 | 79 18 80 | Pointer back into LBL:
> 001879
> 001a1d3e | 002427 | 76 01 0f |
| | | mdr33 string: SOLDEN
> | | | mdr33 string:
> TIMMELSJOCHSTRAßE
>
> No idea how the data is used. My Oregon cannot find any address
> and shows garbage for the region name when I install the
> gmapsupp.img.
Hi Gerd
I got confused between Mdr15 (full string for gmapi) and Mdr17 (partial
string for device), so what I wrote here makes little sense.
I need to think about it more. Sorry for wasting your time.
Ticker
On Thu, 2022-01-20 at 20:42 +, Ticker Berkin wrote:
> Hi Gerd
>
>
t(maxSuffixCount))
> + 1;
>
> The two counters are never increased in the current code. In r3968
> there's some commented code which used them.
>
> Gerd
>
> ____
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Ges
Hi Gerd
I'm struggling to understand the possibilities of Mdr7 (ordering,
partialInfo, nameOffset, string different to label, etc etc)
My initial thought about nameOffset was that it was for skipping over
the shield prefix or text before the 0x1b marker.
partialInfo is very strange; it seems
Hi Gerd
I'm trying understand all this, so maybe what I'm trying to say here is
rubbish.
How is it that --split-name-index didn't also break Find > Street
select list.
If it is required that Mdr7 index entries refer to a label, then,
maybe, can have multiple index entries to the same label with
A quick and dirty method is just to edit the .osm file to move the
... to after the last ...
Ticker
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
https://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
Hi Gerd
Patch attached to fix offsetSize in check16 and have readVarLength()
return the size.
Ticker
Index: src/test/display/MdrCheck.java
===
--- src/test/display/MdrCheck.java (revision 593)
+++ src/test/display/MdrCheck.java
Hi
I was noticing MdrCheck problems in Mdr7 with unicode and string
compression - not using mdr7-del so probably because of the
shield/prefix/sep/suffix markers. Looks like a slightly related
problem.
Ticker
On Mon, 2022-01-17 at 16:20 +, Gerd Petermann wrote:
> Hi Mike,
>
> I fear it is
Hi Gerd
I'm looking at GPXSee at the moment.
Significant to the problem lots of symbols:
The size of the tab1 offset into the symbol list is the same as the
size of the size (the 1+ bytes after the 8/symbol width), so, if more
than 127, it needs an extra byte.
Ticker
On Mon, 2022-01-17 at
oder must understand what a codepoint
> is?
> I don't think so. The only important thing is that utf-8 still can
> use a single 0
> to terminate strings.
>
> Gerd
>
>
>
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
Hi Gerd
More unicode problems: The data structures for the frequency analysis
and then the list of chars to encode will all need attention.
Ticker
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
Struct and rowsIn1stTable is still
troubling, as I'd have expected it to be associated with the
prefixTable
Ticker
On Sun, 2022-01-16 at 12:37 +, Ticker Berkin wrote:
> Hi Gerd
>
> I'm just starting to look at this, but won't be able to do much
> today,
> but some initial f
Hi Gerd
I'm just starting to look at this, but won't be able to do much today,
but some initial findings:
If just making gmapi from .img, unless --code-page is given it doesn't
do compression, however the Mdr generated with the expected charset.
MdrCheck and MdrDisplay, including string dump,
Hi Jose
I don't see from your display which you mean, but, from the OSM area, I
think I understand.
You could consider adding something like this to
highway=footway {
existing stuff;
set mkgmap:set_unconnected_type=none;
set mkgmap:set_semi_connected_type=none;
} [existing stuff]
lain when building an indexed
> gmapi/gmapsupp
> where some tiles where freshly compiled with the new version and
> others with
> an older (like Felix and Carlos do)?
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag
> von Ticker Berk
.
>
> I plan to recode MdrDisplay now that I undestand almost all data.
> I also want to implement this in MdrCheck during the next days.
>
> Gerd
>
>
>
> Von: mkgmap-dev im Auftrag
> von Ticker Berkin
> Gesendet: Mont
Hi Gerd
More minor stuff - Still haven't understood the mincode parts
mdr/Mdr16.java:
loopupBits/lookupBits is very confusing.
Can you have lookupBits for table2 size and something else for table1
size
If maxDepth < initial size (5 or 6), can't you just set table1 size to
maxDepth and set
It looks like the LBL file could be Huffman compressed with an ENCODING
value of 11.
Is there scope for having the new Huffman logic with
app/labelenc/CharacterEncoder /CharacterDecoder interface?
Ticker
___
mkgmap-dev mailing list
r these characters in MapSource and I think
> MapSource uses MDR12
> when you type only a few characters for the name of a POI and don't
> pick up an entry from the list.
>
> Gerd
>
>
> Von: mkgmap-dev im Auftrag von
> Ticker B
1 - 100 of 1100 matches
Mail list logo
