Hi Gerd I think this is about ready for release. There is a slight problem with the layout in the Style Manual in that the width of "is_in(tag,value,method)" causes it to run into the Node/Way/Relation flags. If there was a way to put the function args down the first column it would fix it, but I have no idea of the rules of the formatting language. What are the tools used to transform doc/styles/*.txt to the style-manual.pdf? I'm not going to be able to do any complex line->polygon in/on/out debugging in the next few days and it seems to work well for most cases. Ticker On Mon, 2020-02-24 at 12:50 +0000, Ticker Berkin wrote:
Hi Gerd
Patch attached that:
- rewords the sentence is the Style Manual and changes the highlighting; I need to check the next build/download to see if this is clearer.
- fixes polygon 'any' method to also return true if exactly ON.
- merge polygons for 'any' so that line on shared boundary is "in" rather than "on".
- change the test driver to try all methods relevant to the element, checking they return true/false as appropriate. I decided that, rather than introducing a new tag saying which methods should match, it was clearer to use the 'expected' tag value as a description of how the element interacted with the polygons and generate the methods that should match from this and the non-matching from a list if all methods.
Ticker