First to Site
Release 1.4

Address & Mapping

Address & Mapping - 6 items delivered in v1.4

What Was Delivered

  • Localise Parcel and Property Join table.
  • Experimentation is underway to download a source file of the Parcel and Property Join table found via: https://discover.data.vic.gov.au/dataset/vicmap-property-parcel-and-property-join-table and create local copies of it which gets updated on a daily basis. Technical Specification:
  • Define Configuration:
  • Set the path to the Shapefile.
  • Specify CSV output file name.
  • Define MySQL database name, user, password, and table name.
  • Convert Shapefile to CSV:
  • Use ogr2ogr to convert the Shapefile into a CSV.
  • Ensure geometry data is excluded or included as required.
  • Prepare MySQL Table:
  • Drop the existing table (if it exists) to avoid conflicts.
  • Create a new table with the following fields:
  1. id (Primary Key).
  2. property_id.
  3. parcel_id.
  4. address.
  5. lot.
  6. spi_number.
  • Import CSV into MySQL:

  • Use mysqlimport to load the CSV into the MySQL table.

  • Map CSV columns to MySQL table fields.

  • Ignore the header row in the CSV

  • Flag records that cannot be found from Vicmaps

  • Specify a flag for Processing records whcih have not been processed by VICMAPs then create a cronjob.

  • User led Address Selector

  • When a parcel is found via SPI, there are times when they are matched with multiple properties.

  • FTS Lense Tech’s current behaviour arbitrarily selects a property based off an algorithm of source, dates and maturity of listing.

  • This has resulted in a 95% accuracy rate and a manual workaround.

  • We instead propose that the property is selected specifically by the user instead.

  • For this to happen, a localised lookup of the following is required:

  • parcel v property and;

  • property v address

  • RE: Downloading Original PDF in Chrome and Edge. when we go to download the original checklist on a job in Chrome my mac downloads to PDF, but when the guys download in Edge and or Chrome (not on a mac device) they get the above snip and can’t naturally download via a PDF unless they right click. Can we address this at some point please.

  • Buggy Look up on SPI number Implementation Notes:

  • When a record is saved:

  • Remove any trailing letters after the numeric value of the SPI field value.

  • Create a project note that stipulates the follwing: Subject: SPI Value Updated by System Message: The value was changed from {ORIGINAL_SPI} to {CURRENT_SPI} by the system.

  • This value will be saved as the new value.


The SPI has a number in the Project details page preventing the correct Address details to be generated from VicMAP. See the look up I did in the VicMAP lens. This image below however may be the actual address as provided to us by our customer

Impact

Enhanced address validation and mapping accuracy, reducing data entry errors and improving location data quality.