[OSM-dev] segment discussion - fork of mysql partitioning

[Etienne]

On 8/31/06, Nigel Magnay <nigel.magnay at gmail.com> wrote:
>
> This gets my vote - sounds very sensible to me.
>
> The only thing in segments / ways that I'd like to find a way of
> duplicating is the mental note that I have when using JOSM that 'blue =
> completed, green = needs more work', but that could be done by examining the
> tags.
>

Except that nothing is ever really completed.  A road may be tagged with
highway, name and ref, but there are plenty of other tags that may or may
not be needed: lanes, oneway, width, speed limit, etc.


> While we're at it, could we make some changes to the tags? Whilst I'm all
> in favour of being able to add any arbitary tag value, it would be nice to
> be able to namespace them in some way.
>

There's been a lot of discussion about namespaces and some cases of actual
use (see http://wiki.openstreetmap.org/index.php/Proposed_features/Sourcefor
an example)  It really needs someone to re-draft the Map Features
scheme
to take advantage of namespaces.

Etienne


On 31/08/06, Nicola Ranaldo <ranaldo at unina.it> wrote:
> >
> >
> > > i understand this, but segments are useful for sub-informations like
> > > bridge=yes, tunnel=yes, etc. which do not apply to the whole way - a
> > > possibility around this would be to make ways groupable (arrays of
> > > ways), which is technically not very different to having segments
> > > grouped..
> >
> > A hierarchycal way model could resolve every problem, properties should
> > be
> > propagated from parents to childrens, and these can override their
> > specific
> > properties.In the actual model, on a long tunnel, composed by several
> > segments, you have to replicate the "tunnel=yes" for every of them,
> > wasting
> > resources. Another example could be a long way where half is two lane
> > and
> > half tre lane. This approach is usefull for other things, for example,
> > if you
> > have a motorways with to lanes, you can group and tag them as owned by
> > the
> > same "father" way. Rendering softwares so may decide to not draw the way
> > name
> > twice :) and so on. Adopting this model could let us apply some
> > enforcing on
> > data, for examples subways can be simple connected path and so on.
> >
> >         Niko
> >
> > _______________________________________________
> > dev mailing list
> > dev at openstreetmap.org
> > http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev
> >
>
>
> _______________________________________________
> dev mailing list
> dev at openstreetmap.org
> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/dev
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20060831/b09bcfdf/attachment.html>