Axel Lehmann

ad-freiburg/osm2rdf#70 put data into both `osm:` and `ohm:` depending on the selected base dataset even though the original values were always stored with `osmkey:`. With ad-freiburg/osm2rdf#79 we moved the typed...

> It would be very use full for indexing and to attach further meaning to have a URI instead the OSM value for keys, e.g. ` "country" .` Just to...

I think we can now collapse some of them. `osm2rdfgeom` will be removed with #89 and `osm2rdfmember` is currently used for [member relations](https://github.com/ad-freiburg/osm2rdf/blob/50455995b4d69e6a1a9c1ea6cab1df40697815e0/tests/issues/Issue24.cpp#L262-L269). We would need to find good names...

Partial example output for Lichtenstein: ``` ... osmnode:26863444 rdf:type osm:node . osmnode:26863444 osmmeta:changeset "141388466"^^xsd:integer . osmnode:26863444 osmmeta:timestamp "2023-09-17T16:00:53"^^xsd:dateTime . osmnode:26863444 osmmeta:user "tg4567" . osmnode:26863444 osmmeta:version "7"^^xsd:integer . osmnode:26863444 osmmeta:visible "yes"...

Can/Shall we replace the current `geo:hasGeometry` with `geo:hasDefaultGeometry ` as we only provide a single geometry? If both are needed we would have provide the same information with two predicated:...

1. Yes, currently `intersects_area` is a subset of all intersection. This should be changed, thanks for highlighting the issue. 2. The `intersects_area` and `intersects_nonarea` predicates are used to split the...

One of the targets @patrickbr and I formulated when we started the work on osm2rdf was to have access to the raw data/every information provided by the OSM where ever...

Another suggestion for the format name would be "LKB" (little-known binary), this would keep the name smaller :wink:

I'm not good at naming things, as we only have a global meta prefix I thought that mentioning multipolygons could help the understanding of what this value is about without...