Hi Marco, thanks for the answer and the explanation.
> I guess you are missing an understanding for OSMs data model. OSM is > very flexible in adding attributes to a feature by adding key/value > pairs. If this is to be represented in a GIS data away (table) you have > to convert the data importing just relevant keys (each becoming a > column), which results in loss of some attributes, or you can use > something like hstore in postgresql [1] meaning you store the set of > key/value pairs (or dictionary in python-terms) in one column. This is > lossless and seems to be what is used here. well I think that even if lossless the information are pretty much useless also. What I'm saying is that the old OSM core provider of QGIS 2 (download osm and convert osm to SpatiaLite) and the current QuickOSM plugin (both QGIS 2 and QGIS 3) stores all the information as well, having maybe a lot of columns empty, but still usable. Cheers Matteo _______________________________________________ QGIS-Developer mailing list [email protected] List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
