osmway:node/osmway:node redundancy

[1ec5]

With the --add-way-node-order flag, osm2rdf includes osmway:node triples that in turn include osmway:node triples, but these are two distinct uses of the osmway:node predicate that have objects of different types. The osmway:node of a way isn’t really a node per se. If you write something like ?way osmway:node ?node . ?node osmway:node, the UI suggests ?node as the next token, which is guaranteed to return zero results.

Should ways have osmway:member triples for consistency with osmrel:member, since the objects in both cases are structured similarly? Or maybe the predicate could be osmway:vertex, based on the terminology occasionally used by OSM editors?

[patrickbr]

I agree, the current situation is (for historical reasons) very confusing and inconsistent.

We have created a PR to fix this, please feel free to test it and give some feedback :)