On Monday, December 17, 2012, Clay Smalley wrote:
(Of course, some of these lines run through tunnels where they are tagged
layer=-1, and on bridges where they are tagged layer=1 correctly. The layer
tag on these bits of track would remain untouched.)
Though this layer tag is unnecessary if
2012/12/17 Paul Johnson ba...@ursamundi.org:
On Monday, December 17, 2012, Clay Smalley wrote:
(Of course, some of these lines run through tunnels where they are tagged
layer=-1, and on bridges where they are tagged layer=1 correctly. The layer
tag on these bits of track would remain
Well, I say this because I've yet to come across any renderer that doesn't
automatically assume layer=-1 for tunnel or layer=1 for bridge when it's
omitted.
On Mon, Dec 17, 2012 at 9:24 AM, Martin Koppenhoefer dieterdre...@gmail.com
wrote:
2012/12/17 Paul Johnson ba...@ursamundi.org:
On
On Mon, Dec 17, 2012 at 12:50 AM, Clay Smalley claysmal...@gmail.comwrote:
I noticed the majority of the trackage of the San Francisco Muni lines are
tagged as layer=1, while the streets along which they run have no layer tag
(an implied layer=0).
If the Muni lines are layer=1, it is my
On 2012-12-17 07:50, Clay Smalley wrote
:
I noticed the majority of the trackage of the San
Francisco Muni lines are tagged as layer=1, while the streets
along which they run have no layer tag (an implied layer=0).
If the Muni lines are layer=1, it is my
On Monday 17 December 2012 18:13:37 Clay Smalley wrote:
On Mon, Dec 17, 2012 at 12:50 AM, Clay Smalley claysmal...@gmail.comwrote:
I noticed the majority of the trackage of the San Francisco Muni lines
are tagged as layer=1, while the streets along which they run have no
layer tag (an
On 17/12/12 06:50, Clay Smalley wrote:
I noticed the majority of the trackage of the San Francisco Muni lines
are tagged as layer=1, while the streets along which they run have no
layer tag (an implied layer=0).
If the Muni lines are layer=1, it is my understanding that the Muni
lines should
On Mon, Dec 17, 2012 at 11:40 AM, A.Pirard.Papou
a.pirard.pa...@gmail.comwrote:
A level is an altitude. A layer is a drawing opacity. Although OSM does
not tag for the renderer, it uses the tag *layer=**. It defines *layer*as the
relative position (is that altitude?). In fact, the only
On Mon, Dec 17, 2012 at 12:23 PM, Chris Hill o...@raggedred.net wrote:
The layer tag is only a hint to renderers. If you remove the tag the road
way may render over the rail way and hide it.
Yes, that's been my understanding. It's also been my understanding that we
have a separate renderer for
Though in this case, the rail way should be on the track centerline, which
probably doesn't overlap the road centerline.
On Dec 17, 2012 12:25 PM, Chris Hill o...@raggedred.net wrote:
On 17/12/12 06:50, Clay Smalley wrote:
I noticed the majority of the trackage of the San Francisco Muni lines
2012/12/17 Chris Hill o...@raggedred.net:
The layer tag is only a hint to renderers. If you remove the tag the road
way may render over the rail way and hide it.
no it is not (only, IMHO), it is an attribute to get some depth into a
2D-model (our database). It is a tag that indicates which
2012/12/17 A.Pirard.Papou a.pirard.pa...@gmail.com
A level is an altitude. A layer is a drawing opacity. Although OSM
does not tag for the renderer, it uses the tag *layer=**. It defines *
layer* as the relative position (is that altitude?)
no, it is not altitude (height over ground), it
On 2012-12-17 22:16, Martin Koppenhoefer wrote :
2012/12/17 A.Pirard.Papou a.pirard.pa...@gmail.com
mailto:a.pirard.pa...@gmail.com
A level is an altitude. A layer is a drawing opacity. Although
OSM does not tag for the renderer, it uses the tag *layer=**. It
defines *layer* as
Am 18.12.2012 07:31, schrieb A.Pirard.Papou:
On 2012-12-17 22:16, Martin Koppenhoefer wrote :
2012/12/17 A.Pirard.Papou a.pirard.pa...@gmail.com
mailto:a.pirard.pa...@gmail.com
We badly need precision.
. In fact, the only effect of assigning a layer is that upper
layer objects hide
14 matches
Mail list logo
