Hi Ticker,
reg. result:
Please find a better explanation for this:
"This is useful for the negative - is_in(...,any_in_or_on)=false - for
processing a line that is outside the polgon(s) but might touch an edge."
For me this sounds plain wrong. It would be okay without "but might touch an
edge".
Hi Gerd
The new meaning of any_in_or_on is for handing a line where some is
OUT, none is IN and touching the edge is irrelevant and is tested as
()=false, with the +ve logic being "some-IN or all-ON". Can't stop on
ON because need to have IN component.
This was the the meaning I had originally
Hi Mike,
Ticker is right. Please don't add mkgmap special tags to the OSM database.
Those tags should be used in the style.
Gerd
Von: mkgmap-dev im Auftrag von Mike
Baggaley
Gesendet: Montag, 17. Februar 2020 20:17
An: 'Development list for mkgmap'
Hi
It is standard mkgmap behaviour to not load OSM tags that it doesn't
see the need for. It detects tags referenced in the style and has a
list of other tags known to be processed by the java code
(resources/styles/builtin-tag-list).
Add extra ones to your style options file:
...
Hi Gerd
A simpler way of expressing it in the Style Manual would be:
+any_in_or_on+ - if is_in(...,any_in_or_on)=false, part is outside,
none is inside.
What do you think? An alternative would be to re-phrase the keyword as
something like 'some-out-none-in', testing for =true instead. But,
Hi Ticker,
I would except
+any_in_or_on+ - if is_in(...,any_in_or_on)=false, all is outside, none is in
or on the edge.
Or name it
+all_out+ - if is_in(...,all_out)=true, all is outside, none is in or on the
edge.
A method that returns true when all is either out or on the edge could be
Hi all,
I have set logging to enable warnings in StyledConverter, and have been
getting a few unexpected results from the dead end check. It seems that
using the default style and latest mkgmap release, if a way has
mkgmap:dead-end-check=no set in OSM, this information is not loaded, so when
the
Ticker Berkin wrote
> I suggest replacing ANY_IN_OR_ON with SOME_OUT_NONE_IN, giving it the
> method string "none", like SOME_IN_NONE_OUT is referenced as "all".
Yes, much better.
Gerd
--
Sent from: http://gis.19327.n8.nabble.com/Mkgmap-Development-f5324443.html
Hi Gerd
The two most common cases that I imagine users will want to match are
lines inside the polygon(s) and lines outside.
Inside lines will frequently meet the edge, and I don't think these
should fail the inside test.
Outside lines will, less frequently, meet the edge, and I don't think
Gerd Petermann wrote
> Ticker Berkin wrote
>> I suggest replacing ANY_IN_OR_ON with SOME_OUT_NONE_IN, giving it the
>> method string "none", like SOME_IN_NONE_OUT is referenced as "all".
>
> Yes, much better.
Thinking again about it. What would be the difference between
is_in(..all)=true and
Hi Arndt
There should be no need to delete äöü if you use the --latin1 or
--code-page=1252 option to mkgmap
Ticker
On Sat, 2020-02-15 at 14:31 +0100, Arndt Röhrig wrote:
> Hi Ticker,
>
> now all is OK. I delete äöü in the typ/txt files and give mkgmap the
> option --latin1.
>
> Thank you!
>
Hi Ticker,
I don't understand the new meaning of any_in_or_on. Why can't you stop early
when ON was found?
I still think that the "stop early" code is just adding complexity. Do you have
a sample that shows how this improves performance?
Reg. unexpected results when joining shapes: Welcome to
Hi Gerd
Here is patch with:
- IsInUtilTest driver using the is_in function with methods.
- a slight re-formulation to the 'any_in_or_in' method.
- updates to style manual for above.
- some fixes and improvements relating to holes, ON etc.
There is one more bit of logic that is needed for
13 matches
Mail list logo
