Change parcels from LDS schema to the BDE schema

[billgeo]

Switch the map back to getting all it's data from BDE schema.

TWG will decide this on Friday.

[palmerj]

Can you please specify what the map requirements are in QGIS? Does it need the LDS primary parcels layers because it has title references and the appellation string?

[billgeo]

Just spoke with Simon about this. He has a few map layers which he is going to investigate switching to the BDE schema or LDS WFS.

1. primary parcel spatial extents
2. pending parcel spatial extents
3. parcel labels showing title numbers

[palmerj]

Is there a requirement to have the data in sync with the AIMS database parcels (e.g crs_parcel)

[billgeo]

This is the filter that you need to use to get primary current and primary pending

Current

    SELECT *
    FROM bde.crs_parcel ap
    WHERE ST_GeometryType(ap.shape) IN ('ST_MultiPolygon', 'ST_Polygon')
    AND ap.status = 'CURR'
    AND ap.toc_code = 'PRIM';

Pending

    SELECT *
    FROM bde.crs_parcel ap
    WHERE ST_GeometryType(ap.shape) IN ('ST_MultiPolygon', 'ST_Polygon')
    AND ap.status = 'PEND'
    AND ap.toc_code = 'PRIM';

[linzbjones]

TWG @palmerj is there anything that you are expecting changed in the UI as a consequence of your changes?

[palmerj]

Note completely sure on the UI within the plugin because I've never seen it!

But one issue could be the context parcels layer in QGIS. Simon tried to swap this out for a derived query to retain the appellation but had performance and correctness issues. See my comment here: #184

[billgeo]

In answer to @linzbjones question. No. This is all backend stuff and AIMS API and UI should work exactly the same.

[billgeo]

@SPlanzer to close once he's swapped the UI over to "bde" schema tables.

[billgeo]

@SPlanzer, as discussed. Look at all options to get the appellation for the map display, including temporary workarounds and put here so we can decide on acitosn

[billgeo]

HI @SPlanzer, we are having a TWG at 3pm today. Are you able to add this info before then please?

[SPlanzer]

The spatial parcels have been migrated from the LDS data to BDE.

However, the addressing team have a requirement to have these parcels labelled with there corresponding appellation - THIS IS STILL OUTSTANDING

Several options have been explored to label these parcels.

• utilising the LDS WFS feed has been considered
  • However, data would be up to a week out of date. It is my understanding this does not suffice
• The UI selecting a database view
  • This triggers a view to be compiled when the plugin loads. It causes the plugin to take > 10 min to load.
  • It is possible this could be optimised but would still mean the plugin will not load in an acceptable time
• A materialised view has been compiled and a trigger created to refresh the materialised view when the bde.crs_parcels table is altered.
  • This porives the AIMS UI users with the up to date labels they require without causing any latency.
  • This has been tested and shown to work, however, testing still needs to be undertaken with the overnight bde_loader running to ensure the triggering of the materialised view refresh does not conflict with the bde_loader.
  • The addressing team has expressed they can go live with the proviso that this solution would be further tested over the coming weeks and rolled out shortly after go live
  • this solution is branched

[palmerj]

I would say another option is to rewrite the appelation pl/pgsql function to sql. That would allow good performance on a non-materialised view.

[billgeo]

TWG: Addressing team has workarounds for this and can live without this function for 3 weeks.