Replacing the mv_geojson_geoms view in stable/5.2.x

[chi...@fargeo.com]

Hi Everyone,

Just a heads up - later today or (maybe early tomorrow) we are going to merge into stable/5.2.x some work that Rob Gaston did to move the management of geometries from the mv_geojson_geoms materialized view to a table called geojson_geometries. This will allow geometry records to be updated in place rather than having to refresh the materialized view. Refreshing the materialized view can be a long running task for large projects, so this change will lift a substantial burden from postgres.

This change will not delete the mv_geojson_geoms materialized view, but Arches will no longer update that view, so if you are referencing mv_geojson_geoms in any custom code, or if you are connecting directly to it in a client such as QGIS, you may want to point to the geojson_geometries table instead once you have pulled from 5.2.x and run migrations.

With the exception of an added id column, the schema between mv_geojson_geoms and geojson_geometries is the same, so the transition should be very easy. Once you pull from stable/5.2.x you will need to run migrations. This will load your tile geometries into geojson_geometries. This will take about as long as it would take to refresh the materialized view. That means if you have a really large project, the migration may take a while.

Thanks,

Cyrus