[OSM-talk] 1) Messy Overlapping 2) Messy Layers 3) Bridges 4) Trunk/primary 5) Forum
80n80n at gmail.com
Sun Feb 11 09:03:55 GMT 2007
The reason primary and trunk render in dfifferent colours at different zoom
levels is because zoom levels 14 through 17 are not finished yet.
Zoom levels 12 and 13 were fixed up a while back to render more nicely at
those zoom levels. At the same time some other things were also fixed up.
The same process needs to be done for zoom levels 14 through 17.
On 2/11/07, Ben Robbins <ben_robbins_ at hotmail.com> wrote:
> 5 problems I have...please split up into seperate topics for reply. Check
> image for refernces..
> 1) Where different highway types meet at junctions it usually renders
> a messy overlap of the core where 1 of the cores renders later and has a
> rounded end. In just adding an additional tag (for the purpose of the
> example I have added core=yes) you can make selected cores render again
> later and clean up junctions. What would a good tag for this be? or...are
> there better methods of sorting out this asthetical fault?.
> I seem to have had to make loads of different tags just to sort out how
> things rendered. I'm considering just putting them all under
> or extra/other/render etc. Any ideas/suggestions?
> 2) A common problem that I've heard mentioned. When things are on
> different layer there are lines between them. If an additional way is
> over the top tagged the same as in point 1, this goes away for the
> core. Is
> it ok just to add this tag and have a set of layers to sort the problem?
> sounds 'route planner messy' to me.
> 3) Bridges.... I've been adding them for quite some time, and now there
> the bridge=yes rendereding. I stated why I thourght this tag was
> inconsistent before, but I am more concerned with the way the problem of
> bridges has been approuched. I have a bad feeling that there are so many
> different forms and odd and excentric bridges in the world, that just
> a tag and trying to render them correct is not going to always be
> satisfactory. The bridge may in most parts corralate strognly with the
> that passes over it, but there are many exceptions. I would have tried to
> solve the problem from the bottom up. So just have the bridge drawn, as I
> do so, in its elements in josm. Its incredably basic, but therefore can be
> used anywhere, and if JOSM (or any editing program) created them
> automatically or on command then I think this would confront the problem
> from the correct angle. This allows for full freedom of reshaping the
> bridge, as well as allowing the bridge tags to be seperate. A road can
> split into 2, rejoin itself, go threw a slalum and have a river running
> and under it all the way along the bridge, and it would still be quite
> simple to map.
> In the end I think drawing a map with a pencil and paper will have far
> hurdles than osm is having/will face, just becuase it has no rules. The
> data that can be seen in osm datas raw elements the better as it is free
> these rules. Predefined tags are great where they work and I'm all for
> them, but there should always be the safety net allowing data to be added
> its most basic form, and therefore most acurate. If josm could support
> it would be extreamly helpful I think.
> 4) Primary and Trunk render differently at the different zoom levels
> online. I asume this is known about, but I've never heard it
> mentioned. Is
> it not quite an easy thing to fix?
> 5) As disscussed on the wiki main page disccusion, where is the forum?
> been gone for a while now, and it was in a bit of a state, but I, along
> quite a few others it would seem, would far prefer to be using that to
> problems such as these ^^.
> Sorry these emails seem to get kinda long. I easily have a 100
> questions/concerns but these are some at the front of my mind at present
> I throught I would chuck them into the ML and see what comes out.
> MSN Hotmail is evolving – check out the new Windows Live Mail
> talk mailing list
> talk at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the talk