[OSM-talk] The Return of the Highway tags and other junk

[guy at graviles-reynolds.org]

Quoting Ben Robbins <ben_robbins_ at hotmail.com>:

> I'm sorry, but I havn't heard 1 point that would make a node seem the 
> logical thing to do.  I have been mapping these feautres for almost a year,
> 
> and this is what Ive come to evaluate as the most succesfful method of 
> recording data.  I would be interested to know the amount of research that 
> has gone into debating the idea of sticking them as nodes.  I will stand 
> corrected if proven wrong, but this really isn't gunna happen at the moment.
> 
>   These points don't seem to stand up to much scrutany. In short If there 
> isnt some rasional agreement, I will just ignore it.
> 
> Guy: For your second post check the 'Ben's bridge reply'.  There is probably
> 
> faults with it that I would currently alter, but correct on finding, but in
> 
> gerneral route finding should be able to find its way threw that combination
> 
> I think.
> 
> Pictorial accuracy in maps is as inportant as the datas posible use for auto
> 
> route finding.  Not everyone uses routefinders and maps togheter all the 
> time.
> 
 Well having looked at the map on the osmarender layer, on JOSM and rendered
using osmarender with the standard tile at home feature files, I find not only 
does it not render pictorially, but the information is not there for the 
navigation software to use i.e. where the various ways go under and over 
bridges, they are not aware of the existance of the bridges.

Again I would point out that features like gates, stiles, and cattle grids are 
nodes at the crossing point which when rendered will at the approprate zoom 
levels be represented by standard symbols. This minimises the data stored, 
allows different symbol sets to be used by users dependant on their need and 
use whilst having the data in the node or on the way to allow navigation to use 
it. Using your method creates a significant amount of data which adds little to 
the to the overall detail of the map, and in this instance fails to give the 
degree of detail that the standard tags give. 

Trying to achieve the pictorial represtation of bridge parapets using nodes and 
segments, is not the way to do it, it is best done by the renderer reading the 
segment on the way for the bridge tag and rendering the parapets accordingly. 
Whilst rendering bridge parapets is something osmarender does not as yet do, 
this not a reason to compensate for it using nodes, segments and non-standard 
tags but more a reason to come up with a rendering solution. Similarly with all 
the nodal features, if you want a gate or a cattle grid rendered, propose a 
symbol don't try and draw it in the base data, and if you need to expand on 
dimensional information add it using standard key/value pairs not by creating 
areas and segments.

Guy