On 06/01/2013 15:01, Lennard wrote:
On 6-1-2013 15:51, Dave F. wrote:
On a related topic; if a field has a barrier tag it changes colour
rendering at zoom 16:
That's because having a landuse on it as well pushes it into the
polygon table. It's subsequently rendered as a barrier area, ie.
2013/1/6 Dave F. dave...@madasafish.com:
On 06/01/2013 15:01, Lennard wrote:
On 6-1-2013 15:51, Dave F. wrote:
On a related topic; if a field has a barrier tag it changes colour
rendering at zoom 16:
That's because having a landuse on it as well pushes it into the polygon
table. It's
On Sun, 2013-01-06 at 17:24 +0100, Martin Koppenhoefer wrote:
The problem is with the mapper mixing up linear and polygon features
on the same osm object. You could tag a way with barrier=hedge and
then add this way as outer way to a multipolygon relation tagged with
landuse=farmland.
2013/1/6 Philip Barnes p...@trigpoint.me.uk:
On Sun, 2013-01-06 at 17:24 +0100, Martin Koppenhoefer wrote:
The problem is with the mapper mixing up linear and polygon features
on the same osm object. You could tag a way with barrier=hedge and
then add this way as outer way to a multipolygon
On 06/01/2013 16:24, Martin Koppenhoefer wrote:
The problem is with the mapper mixing up linear and polygon features
on the same osm object.
I completely disagree with this. He mapped it accurately as a field with
a fence around it. The fact the renderer intentionally put in some code
2013/1/6 Dave F. dave...@madasafish.com:
On 06/01/2013 16:24, Martin Koppenhoefer wrote:
The problem is with the mapper mixing up linear and polygon features on
the same osm object.
I completely disagree with this. He mapped it accurately as a field with a
fence around it. The fact the
Martin Koppenhoefer dieterdre...@gmail.com writes:
2013/1/6 Dave F. dave...@madasafish.com:
On 06/01/2013 16:24, Martin Koppenhoefer wrote:
The problem is with the mapper mixing up linear and polygon features on
the same osm object.
I completely disagree with this. He mapped it accurately
7 matches
Mail list logo
