New answers tagged

0

As MariaDB is a fork of MySQL, I believe it has al the same spatial functionality, which is considerably less than Postgis, but sufficient for your query. You can't GROUP BY a bounding box as such, but you can summarize attributes where the geometries bounding boxes intersect some input geometry. In MySQL/MariaDB, functions that operate on bounding boxes ...


2

I'm afraid this is more of a personal preference than a best practices issue. You have many choices: Create the spatial table in database A with SQL tools, and access it though Query Layers Create the spatial table in database B with SQL tools, and access it through Query Layers Create the spatial table in database B with SQL tools, and register it with ...


0

If your organization is able to run a server with postgresql + postgis as database it will be your best option. If is not possible for you maintain your own server maybe you can check any of the cloud services out there.


0

With GRASS GIS, you can create 3D geometries with: a 3D shapefile a 2D shapefile with z as an attribute 3D polygon(s) (shapefile 3D) and points (shapefile 2D with z as attribute)



Top 50 recent answers are included