Henning Bredel

@giohappy @mattiagiupponi That is a pity to read. I only played around with it on the CLI, so I cannot tell much more on this. On our `datapackage.json` approach, we...

@mattiagiupponi thanks for the hint, I will by-pass the importer's `resource_manager` and use my own. Yes, we have talked about the limitation regarding non-spatial/tabualr data in GeoNode. However, I was...

@gannebamm we did create PR https://github.com/GeoNode/geonode/pull/10842 which was needed to keep all unpacked files from an uploaded zip-file. However, the actual work to support non-spatial (tabular) data is a bit...

To be honest it is unclear to me why [an object created/set on the resource](https://github.com/52North/IlwisCore/blob/2d025e6b20c4b6d91058b9f7ec4b9912b6293e27/core/ilwisobjects/ilwisobjectconnector.h#L28), [prepared afterwards and its reference is returned](https://github.com/52North/IlwisCore/blob/2d025e6b20c4b6d91058b9f7ec4b9912b6293e27/core/ilwisobjects/ilwisobjectconnector.h#L32-L37). In GDALConnector the reference [is being set explicitly...

This PR [may have become superseded](https://github.com/GeoNode/geonode/issues/11184#issuecomment-1683787208). It seems that the fixture to [change the geoserver password got removed completely](https://github.com/GeoNode/geonode/pull/11308/files#diff-2e746c9eacad6e2c2fdefdc6a665b5ce4607ea384ebf97a729044b79acc778d6L565-L582). This is actually good, as this raised so many issues. @afabiani...

Via configuration an API provider can limit access to data a client may request in one shot. It certainly depends on the actual data and hardware how many data a...

I think also that the `FEATURE_ID` columns is just for internal use. I do not think it should be hidden, but protected against (accidental) changes which would break the integrity...

Here is another helpful link explaining how to switch axis orientation in proj4: https://trac.osgeo.org/proj/wiki/GenParms#Axisorientation

If something goes wrong, it should be good practice to to tell (somewhere) **what** happened, **where** it happened and **under what context** the error occured. Not that I could tell...

What I mean actually is that the way the connectors are being used by the framework does the developer enforce to place functionality for the one data source in a...