[OSM-talk] waist deep in the tagpile

[Etienne]

On 5/31/06, Jo Walsh <jo at frot.org> wrote:
<snip>
>
> So right now, Etienne's wonderful Osmarender isn't picking up on the many
> segments that were tagged 'class=foo'. For the mapserver-based
> Osmarender knockoff i worked round this by making a duplicate layer for
> each key, that's what is shown in the map link above.

If you want Osmarender to render segments that are tagged with
class=foo then all you have to do is add the appropriate instruction
to the rules file.

Make a copy of osm-map-features.xml called osm-class-tags.xml, change
all k="highway" v="foo" to k="class" v="foo" and there you have it.


>
> What is to be done?
>
> * I leave things as they are, for others to workaround in the same way.
>   [ But this seems super-undesirable - the problem is small now. ]
>
> * I go through all the planet.osm segments that have 'class=' and no
>   'highway=' tags and POST additions to the API. I see no way to
>   delete tags through the API, this probably makes sense.
>   [ But this will lead to unnecessary data duplication + slowdown. ]
>   [ same issue arises with automated correction of obvious typos ]
>
> * I try to persuade someone with direct access to the OSM db to
>   replace all the class= tags with highway= tags.
>   [ But this may break the world of someone who is still annotating
>     with, or rendering with, 'class=foo' tags. ]
>
> * I ignore tagged segments and concentrate on ways
>   * But segments seem to have better metadata + presence than ways do
>   * Someone has to create the ways before they can get key/values,
>     either inherited from the segment's tags (again, do any of the
>     clients support this?) or re-created by hand.
>   * I worry that my understanding of how ways work is partial.
>
> While I'm here:
>
> - Andy's work on the Map_Features vocabulary is spiffing. Is this 'best
> practise' to the extent that it's implemented in one or more of the
> editing clients?
>
> On Tue, May 30, 2006 at 07:59:21PM +0100, Tom Carden wrote:
> > openstreetmap.org - the main site should always have the best possible
> > maps that can be generated from OSM data (it's behind at the moment,
> > but catching up thanks to Nick) because it's really the only place
> > that can drive traffic back to the editors.  Feedback is golden.
>
> - But not a cent for entropy?. The ideal of sensible shared
> classification emerging through demonstrated usage is a nice ideal.
> OSM has got to the stage where this has led to an evolved 'standard'
> which, though English-only, *is* being used in non-UK places in Europe.
> I think that entropy for key/value usage preference is missing now.
> "Most recently used popular tags" in an editing client could be a start.
>
> - Would a 'key foo is semantically equivalent to key bar, and value X
> in the context of key foo is equavalent to etc etc' be overkill? I
> mention it in the context of future i18n.
>
> - One thing the three of us have are planning for, is an AJAX editing
> client intended *only* for creation of metadata, not for drawing of
> shapes. But if something like this didn't run on the OSM systems, then
> we'd have to implement our own user authentication and either maintain
> locally a model of who-tagged-what-how-when and repost everything to
> OSM through one account, or somehow automate OSM account creation for
> everyone who came to use a tag-only client.
>
> The idea of a metadata-only client may sound dull, but i experimented
> with this a lot last year, before 'tagging' was implemented in the OSM
> API, and it had a lot of the same stickiness / 'just one more feature'
> compulsion nature to it as drawing clients do. Honestly ;)
>
> More than enough for now.
>
>
> jo
>
>
>
>
> _______________________________________________
> talk mailing list
> talk at openstreetmap.org
> http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
>


-- 
Etienne