Here is some changes to the help - options documentation.
If it is OK will someone (I suppose Steve / Mark) please commit it?
It is my first patch, so please advice where necessary
Groete
BennieD
Steve,
Is the zipped forum archives broken, or just avaialable to a select
few?
I know it wa
Felix,
> Forgot to say, using patch v2 even more errors were reported.
Yeah, it's still not right but at least it's becoming clearer to me
what has to be done. I will work on it again tomorrow evening.
Cheers,
Mark
___
mkgmap-dev mailing list
mkgma
svn commit wrote:
> Version 1364 was commited by markb on 2009-11-09 23:52:28 + (Mon, 09 Nov
> 2009)
>
> write() now reports assertions caught when constructing LinePreparer.
>
> If LinePreparer has a problem, report it and then return rather than
> letting the assertion terminate the program
svn commit wrote:
> Version 1364 was commited by markb on 2009-11-09 23:52:28 + (Mon, 09 Nov
> 2009)
>
> write() now reports assertions caught when constructing LinePreparer.
>
> If LinePreparer has a problem, report it and then return rather than
> letting the assertion terminate the program
Clinton Gladstone wrote:
On Nov 9, 2009, at 8:27, Du Plessis, Bennie wrote:
> BTW I found a style file work around to increase routing distance.
>
> Where my map’s max was 1400km before I can now route up to 2200km,
by simply
> upgrading the road-class of the major long distance connector r
On Nov 9, 2009, at 8:27, Du Plessis, Bennie wrote:
> BTW I found a style file work around to increase routing distance.
>
> Where my map’s max was 1400km before I can now route up to 2200km,
by simply
> upgrading the road-class of the major long distance connector roads.
I added the followin
Felix,
> just tried the patch - it got along further but ultimately still crashed
> on producing the tile (I try not to use --keep-going because I would
> then maybe miss big big errors).
My mistake, I have just committed something that I missed the other day.
With r1364 and the patch I poste
Version 1364 was commited by markb on 2009-11-09 23:52:28 + (Mon, 09 Nov
2009)
write() now reports assertions caught when constructing LinePreparer.
If LinePreparer has a problem, report it and then return rather than
letting the assertion terminate the program.
Like r1349 but for write(O
Mark Burton wrote:
Felix,
As last question - what happens if there are more than 4 labels - are
label 5 and onwards simply dropped?
Yes, you do get a message though from the RoadDef class (warning level).
Cheers,
Mark
PS - please ignore the patch I just posted for the recent ass
Felix,
> As last question - what happens if there are more than 4 labels - are
> label 5 and onwards simply dropped?
Yes, you do get a message though from the RoadDef class (warning level).
Cheers,
Mark
PS - please ignore the patch I just posted for the recent assertions
problem, I will iss
Mark Burton wrote:
Hi Felix,
could you explain a bit more how they work?
Simply, the contents of those "ref" like names are all concatenated
together with ";" between them and then the first 4 names in that list
are used as the labels for the way. If the way also has a "name" then
t
> display_name="bah"
Err, my mistake, you can't set display_name by OSM tag, only in the
style file. This doesn't affect the general idea that it goes into one
of the labels for the line.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.uk
http:/
Hi Felix,
Please try the attached new patch on as much map stuff as you can.
Hopefully, this will fix the assertion problems with routable ways.
However, it doesn't fix non-routable lines and polygons so you can
still expect to see assertions for them. I intend to come up with a fix
for those a
Hi Felix,
> could you explain a bit more how they work?
Simply, the contents of those "ref" like names are all concatenated
together with ";" between them and then the first 4 names in that list
are used as the labels for the way. If the way also has a "name" then
that will be the first label an
Mark Burton wrote:
Hi Steve,
There is also the issue that if there is a NET section a road can have
up to four names, which cannot be expressed in the style file currently.
Actually, they can because tags "ref", "int_ref", "nat_ref" and
"reg_ref" will assign to them (and they can al
Steve Ratcliffe wrote:
On 09/11/09 18:04, Felix Hartmann wrote:
I would like to set up display name with lines in my style-file like
highway=tertiary { display_name '${name}' | 'tertiary' } [0x04 ]
however currently this is impossible. Could someone adapt mkgmap to
treat display_na
Hi Steve,
> There is also the issue that if there is a NET section a road can have
> up to four names, which cannot be expressed in the style file currently.
Actually, they can because tags "ref", "int_ref", "nat_ref" and
"reg_ref" will assign to them (and they can all have multiple elements
se
On 09/11/09 18:04, Felix Hartmann wrote:
> I would like to set up display name with lines in my style-file like
> highway=tertiary { display_name '${name}' | 'tertiary' } [0x04 ]
>
> however currently this is impossible. Could someone adapt mkgmap to
> treat display_name processing like "na
On Nov 9, 2009, at 19:04, Felix Hartmann wrote:
> I would like to set up display name with lines in my style-file like
> highway=tertiary { display_name '${name}' | 'tertiary' }
> [0x04 ]
Have you tried it with "add display_name =" ...? Or do you need the
syntax in the line above?
Th
I would like to set up display name with lines in my style-file like
highway=tertiary { display_name '${name}' | 'tertiary' } [0x04 ]
however currently this is impossible. Could someone adapt mkgmap to
treat display_name processing like "name" processing?
The reason for this is that addin
Hi Felix,
I believe I understand what the problem is here. My recent changes have
uncovered a problem that has been around for a long time. I shall work
on a solution this evening.
Cheers,
Mark
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkgmap.org.u
On Sun, Nov 8, 2009 at 9:59 PM, guilhem barbaza wrote:
> I have a problem with routing on garmin nuvi 255 since I have changed my
> version of JOSM (2255) :
This is a bit confusing: JOSM should have no relation to the routing
on your Nuvi. Can you please provide more details?
Regards,
Gordon.
Version 1363 was commited by steve on 2009-11-09 10:42:25 + (Mon, 09 Nov
2009)
Merge the mapset branch back to trunk.
Makes it possible to have maps with different family id's in the same gmapsupp.
___
mkgmap-dev mailing list
mkgmap-dev@lists.mkg
just as an additional note, I compiled the map with the last mkgmap
version before the change to arc length - where it passed without
problems (well maybe routing is broken on the streets that cause mkgmap
to crash in later versions - dunno).
Mark Burton wrote:
Hi Felix,
Please try the attac
On 09/11/09 08:26, Ralf Kleineisel wrote:
>> Version 1320 was commited by steve on 2009-10-26 19:46:01 + (Mon, 26 Oct
>> 2009)
>> BRANCH: mapset
>>
>> Branch for combining several maps into a gmapsupp.
>
> Has this branch been merged back into trunk already? I think it works very
> good.
It
Mark Burton wrote:
Hi Felix,
Please try the attached patch and see if it fixes the problem.
The patch fools with the way splitting code a bit so please check it doesn't
screw anything else.
That's it for tonight!
Cheers,
Mark
I found out more about this error when I tried to compile Asi
On 10/26/2009 08:46 PM, svn commit wrote:
>
> Version 1320 was commited by steve on 2009-10-26 19:46:01 + (Mon, 26 Oct
> 2009)
> BRANCH: mapset
>
> Branch for combining several maps into a gmapsupp.
Has this branch been merged back into trunk already? I think it works very good.
__
27 matches
Mail list logo
