From e969f477e3271200a96028c65ced31851c7ba637 Mon Sep 17 00:00:00 2001 From: Simon O'Keefe Date: Mon, 12 Jun 2023 15:14:43 +1000 Subject: [PATCH] Remove docs All documentation is now maintained in PoziWebsite repo/website --- app/PoziConnect/version.py | 2 +- build.bat | 1 - docs/build.md | 32 -- docs/configuration.md | 535 ----------------------------- docs/index.md | 3 - docs/installation.md | 67 ---- docs/m1s.md | 128 ------- docs/m1s/advanced-configuration.md | 70 ---- docs/m1s/audits.md | 143 -------- docs/m1s/configuration.md | 48 --- docs/m1s/history.md | 304 ---------------- docs/m1s/load-reports.md | 19 - docs/m1s/m1-output.md | 9 - docs/m1s/precise-addressing.md | 96 ------ docs/m1s/spatial.md | 7 - docs/m1s/statistics.md | 93 ----- docs/piqa.md | 47 --- docs/template.html | 113 ------ 18 files changed, 1 insertion(+), 1716 deletions(-) delete mode 100644 docs/build.md delete mode 100644 docs/configuration.md delete mode 100644 docs/index.md delete mode 100644 docs/installation.md delete mode 100644 docs/m1s.md delete mode 100644 docs/m1s/advanced-configuration.md delete mode 100644 docs/m1s/audits.md delete mode 100644 docs/m1s/configuration.md delete mode 100644 docs/m1s/history.md delete mode 100644 docs/m1s/load-reports.md delete mode 100644 docs/m1s/m1-output.md delete mode 100644 docs/m1s/precise-addressing.md delete mode 100644 docs/m1s/spatial.md delete mode 100644 docs/m1s/statistics.md delete mode 100644 docs/piqa.md delete mode 100644 docs/template.html diff --git a/app/PoziConnect/version.py b/app/PoziConnect/version.py index 91e2855..dc0b02f 100644 --- a/app/PoziConnect/version.py +++ b/app/PoziConnect/version.py @@ -1 +1 @@ -version = '2.10.0' +version = '2.10.1' diff --git a/build.bat b/build.bat index 155d5d0..48d2880 100644 --- a/build.bat +++ b/build.bat @@ -23,7 +23,6 @@ copy "dist\vendor\%GDAL_NAME%\bin\libeay32.dll" "dist\vendor\%GDAL_NAME%\bin\gda copy PoziConnect.ini dist\ xcopy /E tasks dist\tasks\ xcopy /E recipes dist\recipes\ -xcopy /E docs dist\docs\ mkdir dist\output copy post-install.bat dist\ diff --git a/docs/build.md b/docs/build.md deleted file mode 100644 index 440c5f2..0000000 --- a/docs/build.md +++ /dev/null @@ -1,32 +0,0 @@ -resolve the "Errno -1073741512" error by copying the libeay32.dll file from `PoziConnect\vendor\release-xxxx-gdal-x-xx-mapserver-x-x\bin\` to `PoziConnect\vendor\release-xxxx-gdal-x-xx-mapserver-x-x\bin\gdal\apps\` - -## New Release - -A Pozi Connect 'release' consists of files from multiple sources, including - -* PoziConnect GitHub repo -* PoziConnectConfig GitHub repo - -To create a new release: - -* commit and sync changes in PoziConnectConfig -* make at least one edit in PoziConnect repo (eg, update `docs\m1\history.md`), then commit and sync (this forces GitHub Releases to recognise that something has changed since the last release) -* update PoziConnectConfig (`PoziConnect\tasks`) - * open C:\Temp\PoziConnect\PoziConnect.exe (this is a separate installation of the application, and not linked to the development version) - * click on dot to download latest PoziConnectConfig zip - * close PoziConnect, reopen PoziConnect, proceed with update - * close PoziConnect - * delete `PoziConnect\backup` folder - * delete `PoziConnect\output\PoziConnect.log` file -* update `PoziConnect\docs` by copying files from development version of Pozi Connect -* launch Advanced Installer -* update version number (eg update 1.32.14 to 1.32.15) (and when prompted about the product code, choose 'Generate new', not 'Keep existing') -* build new version - new msi file is created in C:\Temp\ -* go to https://github.com/pozi/PoziConnect/releases, and create new release -* update - * tag (eg v1.32.14) - * release name (eg Release 1.32.14) - * upload new msi - * notes (use previous releases as examples of what to write) -* publish -* notify relevant users to download from https://github.com/pozi/PoziConnect/releases/latest \ No newline at end of file diff --git a/docs/configuration.md b/docs/configuration.md deleted file mode 100644 index 22262ae..0000000 --- a/docs/configuration.md +++ /dev/null @@ -1,535 +0,0 @@ -# Pozi Connect Configuration - -PoziConnect provides a simple interface for accessing, processing, analysing and exporting spatial and non-spatial data. - -It uses the power of the popular open source [GDAL/OGR translator library](http://www.gdal.org/index.html), with these important enhancements: - -* it provides a simple interface that exposes typical translation functions that administrators can preconfigure using INI files and enable users to select and adjust according to specific tasks -* it uses the bare minimum information required to complete a task; for example: - * it doesn't care if a destination file or table already exists - it has the intelligence to create or overwrite as necessary - * it uses the specified source and destination file extensions to determine the required translation settings -* it provides access to Python and database functions within the configuration for operations like indexing and file operations - ---- - -## Running as a batch task - -To run multiple Pozi Connect tasks sequentially and avoid having to open up Pozi Connect and pick and run individual tasks, you can configure a 'recipe' for Pozi Connect to follow. This is useful if you have a series of tasks you regularly need to run (for example, M1s) or for setting up as a scheduled task. - -Here we will use the Melton M1 tasks as an example. - -Create a text file... - -`PoziConnect\recipes\Melton M1.txt` - -…with the following text… - - Melton\Melton M1 - 1 - Import Authority.ini - Melton\Melton M1 - 2 - Import Vicmap.ini - Melton\Melton M1 - 3 - Generate M1.ini - -Then create a batch file or scheduled task with the following target: - -`PoziConnect.exe --recipe="recipes\Melton M1.txt"` - -(You may need to specify the full path to the exe file instead of just `PoziConnect.exe`.) - -This will launch Pozi Connect and run all the tasks specified in the recipe. - ---- - -## Configuration - -Pozi Connect is controlled using INI files. You can edit these files in a text editor. - -If using Windows Notepad, the line returns in existing files may not display correctly. Notepad++ is recommended for editing these files. - -### User Settings - -Notes: - -* If key name ends with 'folder', the interface offers the user a button to launch an Open Folder dialog. -* If key name ends with 'file', the interface offers the user a button to launch an Open File dialog -* If key name ends with 'password', the interface displays dummy characters in place of the populated or typed characters - -Examples: - - [User Settings] - Vicmap_Address_Folder: - Vicmap_Property_Folder: - LGA_Code: 302 - Database_File: Output\Ballarat.sqlite - - [User Settings] - Pathway_DSN: pthprod - Pathway_User_ID: - Pathway_Password: - Pathway_Table_Prefix: pthdbo. - -### General Settings - -Example: - - [General Settings] - Description: - Extract Pathway address and parcel - information into Pozi Connect database - Pathway_Connection: ODBC:DSN={Pathway_DSN};UID={Pathway_User_ID};PWD={Pathway_Password} - Database_File: Output\Ballarat.sqlite - ---- - -## Parameters - -### Source/Destination - -#### Files - -* SHP -* TAB -* CSV -* DXF -* DGN -* GML -* KML -* GPX -* VRT -* XLS, XLSX -* JSON, GeoJSON -* DBF -* MIF -* XML (GeoRSS) - -#### Databases - -*Note: specify file path or connection, then comma, then table name* - -* SQLite (.sqlite, .db) -* PostGIS -* Oracle -* ODBC - -A reference guide for the SQL functions in SQLite and Spatialite is [here](http://www.gaia-gis.it/spatialite-2.3.1/spatialite-sql-2.3.1.html). A tutorial with examples is [here](http://www.gaia-gis.it/gaia-sins/spatialite-tutorial-2.3.1.html). - -#### Web Service - -* WFS - -#### Examples: - - Source: C:\Temp\Road.tab - Source: C:\Temp\Vicmap.sqlite,Road - Destination: PG:host='server.pozi.com' port='5432' dbname='councilgis' user='opengeo' password='abc123',Road - Destination: OCI:gisadmin/abc123@127.0.0.1,Road - -## If - -Notes: - -* the execution of any section can be made conditional -* use a Python expression to return true or false - -Example - - If: os.path.exists('{Input_Folder}/ConquestRoads.TAB') - -### Select - -Notes: - -* Comma-delimited list of fields from input layer to copy to the new layer. A field is skipped if mentioned previously in the list even if the input layer has duplicate field names. (Defaults to all; any field is skipped if a subsequent field with same name is found.) Starting with OGR 2.0, geometry fields can also be specified in the list. -* equates to `-select` parameter in ogr2ogr - -Example: - - Select: ogc_fid as fid, prop_propnum as propnum, ezi_address as address, transform(ST_SimplifyPreserveTopology(transform(the_geom, 28355), 1),4326) as the_geom - -### Where - -Notes: - -* Attribute query (like SQL WHERE) -* equates to `-where` parameter in ogr2ogr - -Examples: - - Where: prop_propnum is not null and prop_propnum <> '' - Where: OGR_GEOMETRY='POINT' - -### SQL - -Notes: - -* SQL statement to execute. The resulting table/layer will be saved to the output. -* equates to `-sql` parameter in ogr2ogr - -Examples: - - SQL: SELECT * FROM pthdbo.cnacomp (NOLOCK) - SQL: select RURAL_NO, RDNAME, RDTYPE, PROPNUM, COMMENTS, PRIMARY as IS_PRIMARY, HOUSE, ID, RA_Complete, XCOORD, YCOORD, PROPERTYNA, DATE from Rural_Address_Original_GJ - SQL: select * from ADDRESS where lga_code = '{LGA_Code}' - -### SQLFile - -Example: - - SQLFile: {Shared_SQL_Folder}\M1 R Edits.sql - -### Native SQLite Processing - -When performing operations where the source and destination are the same SQLite database, you can take advantage of SQLite's native query processing rather than OGR's. This may help for some complex queries. - -Example: - - SQLProcessing: SQLite - - -### TransformCoordSys - -Notes: - -* reproject/transform to this SRS on output -* equates to `-t_srs` parameter in ogr2ogr - -Example: - - TransformCoordSys: EPSG:4326 - -### AssignCoordSys - -Notes: - -* assign an output SRS -* equates to `-a_srs` parameter in ogr2ogr - -Example: - - AssignCoordSys: EPSG:28355 - -### OverrideCoordSys - -Notes: - -* override source SRS -* equates to `-s_srs` parameter in ogr2ogr - -Example: - - OverrideCoordSys: EPSG:28355 - -### GeometryType - -Notes: - -* Define the geometry type for the created layer. One of NONE, GEOMETRY, POINT, LINESTRING, POLYGON, GEOMETRYCOLLECTION, MULTIPOINT, MULTIPOLYGON or MULTILINESTRING. -* equates to `-nlt` parameter in ogr2ogr - -Example: - - GeometryType: None - -### Index - -Example: - - Index: status,tpklpatitl - -### SpatialIndex - -Example: - - SpatialIndex: No - -### Commands - -Examples: - - Command: startfile('{Output_Folder}\\') - Command: DSNList() - PostCommand: system('ogrinfo {Pathway_Connection}') - Command: startfile('output\PoziConnect.log') - -### SkipInfo - -By default, Pozi Connect obtains information about a table and writes it to the log before importing the table's contents. In some circumstatnces, this adds a significant load to the source server. Use `SkipInfo` to prevent Pozi Connect from obtaining the table info. - -Example: - - SkipInfo: true - -### OGRInfoOnly - -Special case used where usual source-destination is not relevant. For example, if updating an existing table. - -Example: - - OGRInfoOnly: true - ---- - -## Advanced - -A number of other OGR commands are available for advanced use within POZI Connect. These operate as per the ogr2ogr cli. Currently, the following commands are supported. For advanced usage, see the [ogr2ogr](http://www.gdal.org/ogr2ogr.html) documentation. - -### Dim - -Defines the dimentions of the output layer. Supported values are XY, XYZ, XYM, and XYZM. layer_dim can also be specified to copy the dimention of the output layer. - -Example: - - Dim: XY - -### SPAT - -Defines the spatial query extents for the source layer. Allows spatial filtering of the source features prior to processing. - -Example: - - SPAT: 0 0 1000 1000 - -### SPAT_SRS - -Defines the SRS of the spatial query extent, provided in SPAT - -Example: - - SPAT_SRS: EPSG:3111 - -### GT - -Defines the number of features grouped per transaction. Defaults to 20000. Changing this value may provide performance improvements for some data sources. - -Example: - - GT: 2000 - -### ZFIELD - -Defines the field of the source layer which will be written to the Z dimention of XYZ or XYZM layers. - -Example: - - ZFIELD: alt - -### CLIPSRC - -Defines a layer/feature used to clip the source layer before processing. A bounding box, WKT Geomerty or a datasource can be provided to the tool. - -Example: - - CLIPSRC: d:\test.shp - -### CLIPSRCSQL - -Defines the SQL to run against CLIPSRC to use in the clip. - -Example: - - CLIPSRCSQL: SELECT * FROM test where group = 1 - -### CLIPSRCLAYER - -Defines the named layer of the CLIPSRC to use in the clip. - -Example: - - CLIPSRCLAYER: Test - -### CLIPSRCWHERE - -Defines an attribute query on the CLIPSRC to use in the clip. - -Example: - - CLIPSRCLAYER: Test - - -### CLIPDST - -As per CLIPSRC, except the clip operation is completed after data has been processed. - -Example: - - CLIPDST: d:\test.shp - -### CLIPDSTSQL - -As per CLIPDSTSQL. - -Example: - - CLIPDSTSQL: SELECT * FROM test where group = 1 - -### CLIPDSTLAYER - -As per CLIPDSTLAYER. - -Example: - - CLIPDSTLAYER: Test - -### CLIPDSTWHERE - -As per CLIPDSTWHERE. - -Example: - - CLIPDSTLAYER: Test - -### SIMPLIFY - -Simplifies a complex layer, using an algorithm which preserves topology per feature, but not the layer. This option accepts a tollerance value. - -Example: - - SIMPLIFY: 5 - -### SEGMENTIZE - -Segmentizes a layer by adding nodes. This option accepts a maximum node distance value. - -Example: - - SEGMENTIZE: 10 - -### EXPLODECOLLECTIONS - -Exploding collections takes a multipart feature and breaks it into its single part components. - -Example: - - EXPLODECOLLECTIONS: True - -### MAPFIELDTYPE - -Similar to SQL's CAST, this function allows the change of field type. All={type} can be used to change all values to a particular type. Accepts Integer, Integer64, Real, String, Date, Time, DateTime and Binary. - -Example: - - MAPFIELDTYPE: ALL|String - -### ADDFIELDS - -Similar to append, this function also add any new field in the source to the destination. - -Example: - - ADDFIELDS: True - -### RELAXEDFIELDNAMEMATCH - -Relaxes the matching of field names between source and destination - -Example: - - RELAXEDFIELDNAMEMATCH: True - -### FORCENULLABLE - -Do not propogate NOT NULL constraints between source and destination - -Example: - - FORCENULLABLE: True - -### UNSETDEFAULT - -Do not propogate DEFAULT constraints between source and destination - -Example: - - UNSETDEFAULT: True - -### MO - -Adds metadata to the destintion, if the layers supports it. - -Example: - - MO: True - -### Open & Creation Options - -The following commands can have multiple options specified, separated by a pipe '|' character - -* dsco -* lco -* doo -* oo - -Example: - - LCO: SHPT=POLYGONZ|RESIZE=YES - ---- - -## Usage - -### Import MapInfo TAB file into SQLite database - - [Vicmap Address] - Source: {Vicmap_Address_Folder}\ADDRESS.tab - SQL: select * from ADDRESS where lga_code = '{LGA_Code}' - Destination: {Database_File},VMADD_ADDRESS - Index: property_pfi - -### Specify destination coordsys and geometry type - - [Vicmap Features of Interest - Polygon] - Source: {Vicmap_Features_of_Interest_Folder}\FOI_POLYGON.tab - Destination: {Database_File},vmfeat_foi_polygon - GeometryType: MULTIPOLYGON - TransformCoordSys: EPSG:4326 - -### Filter by geometry type during import - - [Vicmap Features of Interest - Point] - Source: {Vicmap_Features_of_Interest_Folder}\FOI_POINT.tab - Where: OGR_GEOMETRY='POINT' - Destination: {Database_File},vmfeat_foi_point - -### Translate MapInfo table to CSV - - [Vicmap Reference Table - VMADD_ACCESS_TYPE] - Source: {Vicmap_Reference_Folder}\ADDRESS_ACCESS_TYPE.tab - Destination: {Output_CSV_Folder}\VMADD_ACCESS_TYPE.csv - -### Import non-spatial MapInfo TAB file into SQLite database - - [Vicmap Parcel-Property] - Source: {Vicmap_Property_Folder}\PARCEL_PROPERTY.tab - Destination: {Database_File},VMPROP_PARCEL_PROPERTY - GeometryType: NONE - SpatialIndex: NO - Index: parcel_pfi,property_pfi - -### Update an existing SQLite table - - [Update PC_Council_Property_Address] - OGRInfoOnly: true - Destination: {Database_File},dummy - SQLFile: Tasks\Swan Hill\SQL\Swan Hill PC Council Rural Address.sql - -### Delete a table from a SQLite file - - [Vicmap Vegetation - Remove Tree Density] - OGRInfoOnly: true - SQL: drop table vmveg_tree_density - Destination: {Database_File},dummy - -### Zip up output - - [General Settings] - ZipFilePath: {Output_Folder}/PIQA Export.zip - ZipSession: ZipFile('{ZipFilePath}', 'a', ZIP_DEFLATED) - - [PIQA Parcel Export] - Source: {PlaceLabDB} - SQLFile: {ParcelSQLFile} - Destination: {Output_Folder}/PIQA Parcel Export.CSV - PostCommand: {ZipSession}.write('{Destination}') - - [PIQA Zip Finalisation] - Command: {ZipSession}.close() - [Display in Windows Explorer] - Command: startfile('{Output_Folder}\\') diff --git a/docs/index.md b/docs/index.md deleted file mode 100644 index 8f230ee..0000000 --- a/docs/index.md +++ /dev/null @@ -1,3 +0,0 @@ -# Pozi Connect: Documentation - -## *You can now find help for Pozi Connect at [https://docs.pozi.com/pozi-connect/](https://docs.pozi.com/pozi-connect/)* diff --git a/docs/installation.md b/docs/installation.md deleted file mode 100644 index db1d108..0000000 --- a/docs/installation.md +++ /dev/null @@ -1,67 +0,0 @@ -# Pozi Connect Installation - -## Instructions - -1. go to [https://github.com/pozi/PoziConnect/releases/latest](https://github.com/pozi/PoziConnect/releases/latest) -2. click on the link to the .msi file to download the installer -3. run the installer -4. change the default path to the desired PoziConnect location on your network (pick the location of the existing installation if you have previously installed it) -5. follow the prompts to complete the installation - -Pozi Connect Setup - -### Customise Configuration - -You can customise the Pozi Connect drop-down task list to display only the tasks that you're interested in. - -The `PoziConnect\PoziConnect.site.ini` file contains filters to specifically include or exclude tasks. Open the file in a text editor, and specify the filter. For example, if you only want to display tasks that relate to 'Glen Eira', update the file as follows: - -``` -[Settings] -Include: Glen Eira -Exclude: -``` - -You can enter multiple filter terms, separated by commas. Save the file and exit. - -This file should persist in your Pozi Connect application folder, so you need only do this step once, not every time you update the application or configuration. - -## FAQ - -### How does Pozi Connect connect to my corporate database? - -Pozi Connect uses your PC's existing ODBC connection settings. It does not require any additional network or firewall configuration. It requires only that the user's PC has the appropriate DSN configured to access (read-only) the council's property database. Authentication can be based on a username/password or trusted connection (using Windows login name). - -## Troubleshooting - -### Pozi Connect fails to start - -Download and install the [Microsoft Visual C++ 2008 Redistributable Package (x86)](http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en), and try running Pozi Connect again. - -### Pozi Connect returns an 'Incorrect padding' error - -If you encounter an error saying 'Incorrect padding', it may be because your database password contains a special character (such as '&') that interferes with the database connection string. - -Reset your password so that it doesn't contain any special characters. (If your password needs to use at least one special character, use '#'.) - -### Cannot connect to data source - -_In this example, we'll assume that we're trying to connect to a DSN called 'pthprod'._ - -Run the 32 bit ODBC setup wizard (instead of the standard DSN wizard in the Control Panel). At the Windows Start menu, type in cmd, then at the command-line prompt, type or paste in the following, then hit 'Enter': - -`C:\Windows\SysWOW64\odbcad32.exe` - -In the System DSN tab, check if there is a data source for 'pthprod'. If not, add a new DSN, using the same settings as your existing 64 bit one. It is recommended to use a different name for the new 32 bit DSN. For example, name it 'pthprod32' or similar so it can be distinguished from the existing DSN. - -Open the relevant Pozi Connect config file (eg `PoziConnect\tasks\~Shared\M1 Shared - Import Pathway.ini` or equivalent client-specific task) in a text editor and update the DSN name: - -``` -Pathway_DSN: pthprod32 -``` - -### Pozi Connect returns an error number 1073741512 - -Go into your `C:\Windows\System32` folder and see if there is a file called `libeay32.dll`. If so, rename it to `libeay32.bak`. Then try running Pozi Connect again. - -(Rename the file back again when you've finished so that any other programs that may rely on it can use it.) diff --git a/docs/m1s.md b/docs/m1s.md deleted file mode 100644 index 2ef6943..0000000 --- a/docs/m1s.md +++ /dev/null @@ -1,128 +0,0 @@ -# Pozi Connect for M1s - -Pozi Connect generates council 'M1' reports that are critical link for updating the Victorian state map base. - -![M1 Form](http://i.imgur.com/rlp9JKS.jpg "M1 Form") - -Pozi Connect compares the council's property data with the latest Vicmap data and determines what updates are required in Vicmap to accurately reflect the council's property and address information. - -After Pozi configures and implements Pozi Connect for your council, you can generate M1s at any time by launching Pozi Connect and running the three or four M1 tasks from the picklist. Your M1 report will be generated to a pre-defined location, and it is ready to be submitted via the [NES](http://nes.land.vic.gov.au/WebSite/Login.aspx) system. - -(See Pozi Connect's [history](/poziconnect/m1s/history) to see the our most recent changes.) - -## Vicmap Maintenance Cycle - -Vicmap data is maintained by DELWP. Councils obtain updates of 'Vicmap Address' and 'Vicmap Property Simplified 1' by downloading it weekly (recommended) or fortnightly from the Spatial Datamart. - -Pozi Connect uses this downloaded Vicmap data (as well as the council's current rates data) to automatically generate the required M1s. When the M1 is submitted, it feeds into the Vicmap maintenance cycle. The changes will not be immediate because of the DELWP/Jacobs maintenance schedules and occasional backlogs. Allow at least two weeks before you can expect to see the changes in Vicmap. - -Manual M1s (or using software like Common Ground) are no longer required for routine data maintenance. Pozi Connect takes care of most property number and address updates when you run it on a regular basis. It will even use any rural address point locations that you specify in a point table (if Pozi Connect is configured for it). - -## Preparation - -Download and unzip the following MapInfo or SHP datasets to the predefined location on your network: - -* Vicmap Address -* Vicmap Property Simplified v1 - -(If you do not know the predefined locations on your network for these datasets, launch Pozi Connect and pick the M1 task that relates to importing Vicmap. The network location is shown there.) - -If you have not already done so, set up a weekly repeat order for both datasets at the [Spatial Datamart]( http://services.land.vic.gov.au/SpatialDatamart/). - -### Unzipping Spatial Datamart Files - -Zip files generated by the Spatial Datamart contain folders within folders within folders. It is important to unzip this file correctly. - -The behaviour of unzipping a file can vary depending on the setup of your PC. Winzip has an option to ignore folders within the zip file, while other applications (such as the built-in Windows unzip function) extracts all the files AND folders. - -The important thing is that you are aiming to overwrite the files in the main Vicmap Address and Vicmap Property Simplified folder(s). - -If you find that unzipping the zip file puts the new files into another location (eg, into series of subfolders like `mga94_55\mapinfo\lga_polygon\bayside\VMPROP\`), then you can see that it's gone wrong. All the individual table files need to be moved into the main folder(s) for Vicmap Address and Vicmap Property Simplified. - -Confirm that the dates of the files in these main folder(s) correspond to the date of the zip file to ensure that you've extracted the files to the correct location. - -## Generating M1s - -Launch Pozi Connect. From the picklist, select the first M1 task that relates to your council name: - -![Pozi Connect for M1s](http://i.imgur.com/Yx9RH81.png "Pozi Connect for M1s") - -For each of the three to four M1 tasks in the picklist: - -* select respective M1 item from list -* enter any credentials if prompted (if a username/password is required, enter the *database* credentials, as opposed to any *application* credentials you may use for accessing your property system) -* click 'Start' (each task will take between half a minute and ten minutes) - -There are three or four tasks, depending on whether your council has been configured for importing any custom address locations. - -Upon completion of the 'Generate M1' M1 task, you can find the completed M1 report in the `PoziConnect\output\M1` folder. - -## Submitting M1 - -### Preview - -Open up the M1 report in Excel to preview the updates that Pozi Connect has generated. Scroll all the way to the right, and review the Comments (column AX) field. - -![M1 Comments](http://i.imgur.com/bZz3m1Z.png "M1 Comments") - -For the first few times you run Pozi Connect, you may find you want to hold back some updates if you're not sure that you want to submit them. For example, if an update's comments show that a property is going to be added as a multi-assessment and you're not sure that it should be a multi-assessment, you may delete the row before you submit the M1. This gives you the opportunity to check your property system to see if you're happy with affected properties' parcel description (if two properties share the same parcel description, Pozi Connect will assume they are meant to be a multi-assessment). - -Any rows you delete will simply appear on the next M1 if there are no changes made to the council's property data. - -Other items to look out for: - -* warnings (WARNING: conflicting localities): check that you're happy for a property to be allocated to a parcel whose locality differs in Vicmap and Council -* new roads (column AL): if a Council road name doesn't exist in Vicmap, it will assume that the Council road name is correct, and it will be flagged as a 'new road' in Vicmap, and the new road name will be accepted as the official road name; check that it's not a typo - -After you've removed any records you don't want to submit, save the spreadsheet with a different name to differentiate it from the original output. You can even save it to a different folder of 'submitted' M1s to keep a record of M1s you've actually submitted (as opposed ones that have been generated but not submitted, say for data cleansing purposes). - -### Submit - -Log on to [NES](http://nes.land.vic.gov.au/WebSite/Login.aspx) and upload the spreadsheet file as per the [M1 Form Load Guide](http://nes.land.vic.gov.au/WebSite/help/NES_Quick_Guides_-_M1_Form_Load_V1.8.pdf) [pdf]. - -## M1 Edit Codes - -Pozi Connect generates separate edits for property number, crefno and address changes. Instead of analysing a property in its entirety to see all the things that need to be updated, it checks the eligibility of each property to be included in an update based on the edit code. - -In the first pass, it works out if a multi-assessment needs to be added (A). In the next pass, it works out if a crefno needs to be updated (C). Then it works out if a property needs to be removed (E). And so on. - -This is why Pozi Connect generates separate edits for property number updates and address updates. - -If you were filling out an M1 manually, you would typically update property number and address at the same time with an 'E' edit. Because of the way Pozi Connect systematically evaluates every property's suitability for updating, it processes property number updates (P) separately from the address updates (S). - -In the case of a new property, there would be a P edit to allocate the new property number, followed by an S edit further down the spreadsheet. - -For more details about how Pozi Connect determines which records are included in which scenarios, see the dedicated explanations of the logic for each edit code: - -* [Edit Code A](https://github.com/pozi/PoziConnectConfig/blob/master/~Shared/SQL/M1%20A%20Edits.md/) -* [Edit Code C](https://github.com/pozi/PoziConnectConfig/blob/master/~Shared/SQL/M1%20C%20Edits.md/) -* [Edit Code E](https://github.com/pozi/PoziConnectConfig/blob/master/~Shared/SQL/M1%20E%20Edits.md/) -* [Edit Code P](https://github.com/pozi/PoziConnectConfig/blob/master/~Shared/SQL/M1%20P%20Edits.md/) -* [Edit Code R](https://github.com/pozi/PoziConnectConfig/blob/master/~Shared/SQL/M1%20R%20Edits.md/) -* [Edit Code S](https://github.com/pozi/PoziConnectConfig/blob/master/~Shared/SQL/M1%20S%20Edits.md/) -* [Edit Code S (proposed)](https://github.com/pozi/PoziConnectConfig/blob/master/~Shared/SQL/M1%20S%20Proposed%20Edits.md/) - -After the M1 is submitted in NES, Jacobs will process the edits in the following order: - -``` -Z, R, P, S, E, C, A -``` - -## Data Audits - -[Audits](/poziconnect/m1s/audits) - -## Troubleshooting - -### Edits that are not yet handled by Pozi Connect - -* secondary addresses -* multi-assessment properties where all existing propnums in Vicmap are incorrectly matched (typical multi-assessments are OK) -* transfers of parcels that contain a primary address -* address position update (ie, addresses that have *moved* from their original position) - -## Support - -Pozi offers consulting services to improve councils' property data maintenance processes. - -[Read more](https://pozi.com/pozi-connect/), or [contact](https://pozi.com/contact/) Pozi. diff --git a/docs/m1s/advanced-configuration.md b/docs/m1s/advanced-configuration.md deleted file mode 100644 index 5845b23..0000000 --- a/docs/m1s/advanced-configuration.md +++ /dev/null @@ -1,70 +0,0 @@ -# Pozi Connect: Advanced Configuration - -### 'Gridlocked' Matches - -There are certain match combinations in Vicmap that are not easily corrected. In these cases, a multi-assessment record must first be removed prior to the property being re-matched correctly. - -The following are the query samples being developed to identifiy these issues. These are not yet implemented in the Pozi Connect application. - -``` -select property_pfi, '' as spi, propnum, 'R' as edit_code -from -( -select property_pfi, spi, propnum, count(*) num_parcels -from pc_vicmap_parcel vp -where - multi_assessment = 'Y' and - propnum in ( select propnum from pc_vicmap_property_parcel_count where num_parcels > 1 ) and - propnum in ( select propnum from pc_council_property_address ) and - spi in ( select spi from pc_council_parcel ) and - propnum not in ( select propnum from pc_council_property_parcel_count where num_parcels > 1 ) and - spi not in ( select spi from pc_council_parcel_property_count where num_props > 1 ) -group by spi -) -where num_parcels = 2 -group by property_pfi - -union - -select '' as property_pfi, spi, propnum, 'P' as edit_code -from -( -select property_pfi, spi, propnum -from -( -select property_pfi, spi, propnum, count(*) num_parcels -from pc_vicmap_parcel vp -where - multi_assessment = 'Y' and - propnum in ( select propnum from pc_vicmap_property_parcel_count where num_parcels > 1 ) and - propnum in ( select propnum from pc_council_property_address ) and - spi in ( select spi from pc_council_parcel ) and - propnum not in ( select propnum from pc_council_property_parcel_count where num_parcels > 1 ) and - spi not in ( select spi from pc_council_parcel_property_count where num_props > 1 ) -group by spi -) -where num_parcels = 2 -group by property_pfi -) -order by propnum, edit_code desc -``` ---- - -``` -select property_pfi, '' as spi, 'R' as edit_code, 'parcel ' || spi || ': removing propnum ' || propnum || ' from multi-assessment to match properly later' as comments -from -( -select property_pfi, spi, propnum, count(*) num_parcels -from pc_vicmap_parcel vp -where - multi_assessment = 'Y' and - propnum in ( select propnum from pc_vicmap_property_parcel_count where num_parcels > 1 ) and - propnum in ( select propnum from pc_council_property_address ) and - spi in ( select spi from pc_council_parcel ) and - propnum not in ( select propnum from pc_council_property_parcel_count where num_parcels > 1 ) and - spi not in ( select spi from pc_council_parcel_property_count where num_props > 1 ) -group by spi -) -where num_parcels = 2 -group by property_pfi -``` \ No newline at end of file diff --git a/docs/m1s/audits.md b/docs/m1s/audits.md deleted file mode 100644 index 8b85b2c..0000000 --- a/docs/m1s/audits.md +++ /dev/null @@ -1,143 +0,0 @@ -# Pozi Connect: Victorian Council Data Audits - -Pozi Connect generates parcel and property/address audits when it creates an M1. Use these audit reports to uncover anomalies in your council's data. - -Described below are techniques for filtering the audits to narrow down the records to show only the ones that require further attention. - -### Opening Audit - -When opening a spreadsheet: - -##### split window to freeze column headings - -* place cursor in A2 cell, then `ALT` + `W` + `S` (doesn't work on all versions of Excel) - or -* manually drag split pane control down past the first row - -##### set autofilter on/off - -* keyboard shortcut `ALT` + `D` + `F` + `F` - -##### expand columns - -* click top left corner to highlight all rows, then double-click on any column divider) - -### Filtering Audit - -*Example filter to select only `0` values* - -![](http://i.imgur.com/rjvYdGt.png) - - -## Council Parcel - -Audit file: `Audit - Council Parcels.csv` - -### Structure - -Column|Description|Usage -:--|:--|:-- -`spi`|council parcel description (in SPI format) constructed from council parcel attributes| -`crefno`|council parcel id| -`propnum`|council property number| -`summary`|council-maintained combined address (council reference only) -`status`|council parcel status -`spi_validity`|description of any detected instances of SPI not meeting Vicmap rules|filter on `NOT (Blank)` to list non-compliant parcel descriptions -`spi_in_council`|number of properties in Council that share this SPI -`council_propnums`|list of property numbers in Council that share this SPI -`spi_in_vicmap`|number of parcels in Vicmap that match this SPI|filter on `0` to list Council parcel descriptions that don't exist in Vicmap -`spi_propnum_in_vicmap`|number of parcels in Vicmap that match this SPI and property number -`vicmap_propnums`|list of property numbers in Vicmap that share this SPI -`partial_spi_in_vicmap`|number of parcels in Vicmap that match on `plan_numeral` but not `plan_prefix`|filter on `NOT 0` to list parcels with potentially incorrect plan prefix -`alt_spi_in_vicmap`|number of parcels in Vicmap that match on `further_description` field instead of `spi`|filter by `NOT 0` to list parcels with potentially incorrect plan prefix -`suggested_spi`|Vicmap SPI that matches closely to Council parcel based on existing `crefno` or partial SPI match|filter on `NOT (Blank)` to list potential easy fixes for invalid parcel descriptions -`propnum_in_council`|number of Council parcel records that share this `propnum` -`propnum_in_vicmap`|number of Vicmap parcel records that matched to this `propnum`|**filter on `0` to list unmatched properties, ie, CRITICAL** -`crefno_in_vicmap`|number of Vicmap parcel records that matched to this `crefno`|**filter on `0` to list unmatched parcels, ie, CRITICAL** -`m1_edit_code`|update pending for this parcel|filter on `(Blank)` to list records not already flagged for update in current M1 -`m1_comments`|comments for pending update - -### Examples - -#### Unmatched parcels, with suggested parcel description fixes (critical, easy) - -The most valuable records to target, as they will result in new matches and are likely to be easily solved. - -* `propnum_in_vicmap`: 0 -* `spi_in_vicmap`: 0 -* `suggested_spi`: NOT (Blank) - -#### Plan Prefix Anomalies - -Likely to be easily solved by updating a plan prefix. See `suggested_spi` field for a hint of the correct plan prefix. - -* `spi_in_vicmap`: 0 -* `partial_spi_in_vicmap`: NOT 0 - -#### Gridlocked Records - -These are parcels that should be matched to Vicmap, but Pozi Connect cannot match them due to conflicting associations on the target Vicmap parcel. - -It's possible these will clear up in subsequent M1s after Pozi Connect removes any redundant records. Alternatively, if these remain unresolved, they should be manually inspected to determine if changes in the council property system are required to break the deadlock. - -* `m1_edit_code`: (Blank) -* `propnum_in_vicmap`: 0 -* `spi_in_vicmap`: NOT 0 - -#### Parish and Township Codes - -The `suggested_spi` field will often contain a parish/township code. To find the parish/township names that correspond with the codes, use the following lists. - -Parish codes (PP2..., PP3..., PP4...): -https://github.com/pozi/PoziConnectConfig/blob/master/~Shared/Reference/VMADMIN_PARISH.csv - -Township codes (PP5...): -https://github.com/pozi/PoziConnectConfig/blob/master/~Shared/Reference/VMADMIN_TOWNSHIP.csv - -You can type the code (without the 'PP') into the 'Search this file...' section to quickly find the parish or township name. - -## Council Property Address - -Audit file: `Audit - Council Property Address.csv` - -### Structure - -Column|Description|Usage -:--|:--|:-- -`propnum`|council property number -`status`|council property status -`address`|combined council address constructed from council address attributes -`locality`|council locality -`summary`|council-maintained combined address (council reference only) -`address_validity`|description of any detected instances of address not meeting Vicmap rules|filter on `NOT (Blank)` to list non-compliant addresses -`parcels_in_council`|number of parcels in Council that share this propnum -`council_parcels`|list of parcels in Council that share this propnum -`parcels_in_vicmap`|number of parcels in Vicmap that match this propnum -`vicmap_parcels`|list of parcels in Vicmap that match this propnum -`vicmap_address`|address of property in Vicmap that matches this propnum -`vicmap_locality`|locality of property in Vicmap that matches this propnum|filter on `N` to list wrong locality in Council -`propnum_in_vicmap`|Council property number exists in Vicmap (Y/N) -`address_match_in_vicmap`|Council address matches Vicmap address (Y/N) -`locality_match_in_vicmap`|Council locality matches Vicmap locality (Y/N) -`road_locality_in_vicmap`|Council road name/locality combination exists in Vicmap (Y/N) -`current_m1_edit_code`|update pending for this parcel|filter on `(Blank)` to list records not already flagged for update in current M1 -`current_m1_comments`|comments for pending update - -### Examples - -#### Locality Anomalies - -Filter - -* `locality_match_in_vicmap`: N -* `is_primary`: not N -* `house_number_1`: not blank - -## Vicmap Property address - -### Examples - -#### Fragmented Properties - -* `cohesion`: < 0.001 -* `propnum`: not blank diff --git a/docs/m1s/configuration.md b/docs/m1s/configuration.md deleted file mode 100644 index 405a8db..0000000 --- a/docs/m1s/configuration.md +++ /dev/null @@ -1,48 +0,0 @@ -# Configuration for Pozi Connect for M1s - -Obtain from Council - -* any status codes for filtering properties? -* number of properties at date of extract -* example retired/cancelled/historic/dummy property numbers -* assign 'NCPR' to all common properties? -* SHP or TAB? -* rural addressing (separate table and/or flag in property system) -* for Authority sites, obtain Type Type table (eg, as supplied from Murrindindi in Feb 2015) -* maintaining own SPI? (eg Mount Alexander Title.Title_SPI_Reference; Baw Baw nucLand.TEXT5; West Wimmera auprparc.ttl_nme; Campaspe pr_parcel.SPI_REF) - -Start Configuration - -* obtain council data -* order and download Vicmap data -* create new folder _Council Name_ based on client name -* copy INI and SQL files from similar site (based on an existing site using the same property system) into new folder -* replace references to previous council SQLite file name with new council name -* look up [LGA code](https://github.com/pozi/PoziConnectConfig/blob/master/~Shared/Reference/VMADMIN_LGA.csv) and update INI settings in Process Vicmap task and both SQL files - -For each of Parcel and Property/Address SQL: - -* if using council's existing PIQA SQL as starting point: - * replace tabs with spaces (4) - * convert upper case SQL syntax to lower case (edit manually or try [Instant SQL Formatter](http://www.dpriver.com/pp/sqlformat.htm)) - * replace old field names - * add expression for num_road_address/ezi_address or spi/simple_spi -* include any necessary expression in road name standardise with Vicmap - * replace (apostrophe) with (blank) - * replace & with AND - * replace ' - ' with '-' - * etc -* ensure propnum and crefno fields are character fields -* remove any unneeded fields -* eliminate null values (replace with blanks if appropriate), *especially spi, propnum* -* test query against council's data -* check that address values comply with: - * [BLG_UNIT_TYPE](https://github.com/pozi/PoziConnectConfig/blob/master/~Shared/Reference/VMADD_BLG_UNIT_TYPE.csv) - * [FLOOR_TYPE](https://github.com/pozi/PoziConnectConfig/blob/master/~Shared/Reference/VMADD_FLOOR_TYPE.csv) - * [LOCATION_DESCRIPTOR](https://github.com/pozi/PoziConnectConfig/blob/master/~Shared/Reference/VMADD_LOCATION_DESCRIPTOR.csv) -* test if the Parcel and Property/Address queries return the same set of property numbers - * check for parcels without properties: `select * from pc_council_parcel where propnum not in ( select propnum from pc_council_property_address )` - * check for properties without parcels: `select * from pc_council_property_address where propnum not in ( select propnum from pc_council_parcel )` -* check for blank values in road_type field: `select * from pc_council_property_address where road_type = ''` -* generate 'sampler' query (10 records from each edit code) -* copy/paste results into audit template and email to council \ No newline at end of file diff --git a/docs/m1s/history.md b/docs/m1s/history.md deleted file mode 100644 index ff784e0..0000000 --- a/docs/m1s/history.md +++ /dev/null @@ -1,304 +0,0 @@ -# Pozi Connect Release History - -## Highlights - -Here are some of the improvements and bug fixes. (For a complete history of all changes, see [here]( -https://github.com/pozi/PoziConnectConfig/commits/master/~Shared/)) - -### Version 2.9 (Sep 2021) - -* support for new Datashare data supplies -* prevent property number updates where existing address is a complex site -* include parcel pfi for proposed parcels -* populate floor type only if floor number exists -* don't trigger update for unit type if unit number doesn't exist -* improve handling of building/complex name changes -* ensure property_pfi is not empty for A edits -* remove distance_related_flag when house number is blank -* don't populate building names greater than 45 characters -* populate road name with existing road name from Vicmap if council road name is a close match but not an exact match -* remove rural address when house number is blank -* prevent Comments being null when address isn't perfectly formed -* update all references from Groundtruth to Pozi -* upgrade GDAL library to v3.1.4 -* various bug fixes -* configuration updates for Frankston, Strathbogie, Wangaratta, Maribyrnong, West Wimmera, Campaspe, Melton, Warrnambool, Surf Coast, Murrindindi, Glen Eira, Manningham, Hobsons Bay, Kingston, Indigo, Latrobe, Hepburn, Swan Hill, Monash, Baw Baw, Mitchell, Mildura, Maroondah and Ballarat - -### Version 2.8 (Feb 2020) - -* improve performance of P edit query -* detect new distance-based addresses -* detect new floor and building details -* populate property_pfi for multi-property parcels -* enable Township parcels to be recognised in multi-assessments -* allow NCPRs to be replaced if address is the same -* allow invalid property numbers to be replaced with NCPR -* improve formatting of Pozi map links to better enable Excel to recognise them as links -* prevent locality conflict warning if name contains a bracket -* remove note about parcel linking to multiple properties -* enable user editing of database connection -* upgrade to GDAL 3.0.0 -* various bug-fixes -* change branding from Groundtruth to Pozi -* configuration updates for Maribyrnong, Loddon, Mitchell, Moorabool, Murrindindi, Moira, Bass Coast, Northern Grampians, South Gippsland, Moonee Valley, Alpine, Colac Otway, Latrobe, Frankston, Hindmarsh, Bendigo, Mornington Peninsula, Ballarat, Melton, Towong, Swan Hill, Casey, Mount Alexander, Indigo, Baw Baw, Pyrenees - -### Version 2.7 (Jun 2018) - -* prevent overwriting addresses if there are multiple unique addresses already associated with that property number in Vicmap -* exclude from A edits any properties associated with current R edits -* improve detection of most appropriate pfi to use when updating multi-property parcels -* detect new hotel style addresses -* improve performance of Vicmap Property Address audit -* update M1 R edit comments to include all parcels that property will be later matched to -* add support for CP and PC plans in SPEAR report -* move Parcel Audit address field closer to front to improve readability -* update VMREFTAB look-up tables -* upgrade GDAL library to `release-1911-gdal-2-2-3-mapserver-7-0-7` -* switch application version numbering to Semantic Versioning standards -* configuration updates for Ballarat, Bass Coast, Buloke, Cardinia, Glen Eira, Golden Plains, Latrobe, Maribyrnong, Maroondah, Mitchell, Monash, Moonee Valley, Moreland, Nillumbik, Northern Grampians, South Gippsland, Stonnington, Swan Hill - -### Version 2.06 (Oct 2017) - -* prevent unneeded house number removal warning -* populate dist_rel field with Vicmap value if no Council vlaue found -* revert to old-style map link format to resolve incompatibility with older versions of Excel -* configuration updates for Monash, Hepburn - -### Version 2.05 (Oct 2017) - -* populate most suitable property_pfi for multi-property parcels -* enforce geometry types for output layers -* update Pozi web links to new format -* update Exception table generation -* upgrade GDAL library to `release-1800-gdal-2-1-3-mapserver-7-0-6` -* configuration updates for Hepburn, Glen Eira, Hindmarsh, Wangaratta, Moorabool - -### Version 2.04 (Jun 2017) - -* add support for M1 exception list -* prevent replacement of NCPR properties that contain addresses -* enable R edits on some previously excluded properties -* prevent Mt/Mount road name discrepancy triggering S edit -* improve parcel matching for Valuer General report -* update Valuer General report output format to CSV to avoid formatting issues -* upgrade GDAL library to `release-1800-gdal-2-1-3-mapserver-7-0-4` - -### Version 2.02 (Feb 2017) - -* prevent retirement of NCPR properties -* prevent retirement of properties for which the council doesn't have any parcel records -* re-add SPI attribute for all P edits -* fix audit message pointing to wrong field -* add crown status to Vicmap Parcel audit - -### Jan 2017 - -* add Valuer General Reports for all councils -* upgrade GDAL library from `release-1600-gdal-1-11-1-mapserver-6-4-1` to `release-1800-gdal-2-1-2-mapserver-7-0-2` - -### Dec 2016 - -* prompt user to confirm property_pfi for parcels that relate to multiple properties -* eliminate duplicate multi-assessment edits - -### Nov 2016 - -* generate address updates only for valid road names -* improve readability of M1 by removing redundant attributes (plan_number and lot_number) - -### Oct 2016 - -* warn user if building name exceeds valid length -* improve audit performance by removing `alt_spi_in_council` calculation -* improve comments for R edits involving NCPR properties -* update audit map links - -### Aug 2016 - -* add parcel area output to Valuer General report - -### Jun 2016 - -* fix SPI formula - cater for parcels with section but no allotment -* change default projection for distance-based addresses to VicGrid (because Jacobs can't handle lon/lat) -* support for multi-status addresses (to avoid reject "Property Identifier has multiple matches") -* prevent attempting to match to non-existent road properties - -### May 2016 - -* update map links -* add generic Property.Gov extract task - -### Apr 2016 - -* improve address validity check to detect invalid house suffix values - -### Mar 2016 - -* improve performance of audit queries - -### Feb 2016 - -* improve edit rules: - * prevent "Property PFI is superseded" error - * when updating distance-related addresses, populate with existing coordinates - * ensure every invalid multi-assessment is retired - -### Jan 2016 - -* improve edit rules: - * prevent multi-assessments being added where property already exists in overlapping multi-lot parcel -* make task names easier to understand: rename 'VG Report' to 'Valuer General Report' -* improve comments - * warn of house number being removed - * warn of adding multi-assessment with different road name - * warn of replacing distance-based address with non-distance-based address - -### Dec 2015 - -* fix bug in generating map links -* fix bug that generated retirements when a spi value was blank -* fix bug that caused incorrect address to be displayed in comments on rare occasions - -### Nov 2015 - -* reduce time taken for council parcel audit by up to two thirds -* reduce time taken for council property audit by up to one third -* re-enable retiring of invalid multi-assessments so they can be matched properly in subsequent M1 (bug fix) -* improve parcel audit results by checking for invalid section values - -### Oct 2015 - -* improve edit rules: - * prevent retiring properties created via SPEAR -* improve comments - * warn of transfer of parcel that includes existing primary distance-based address - -### Sep 2015 - -* improve edit rules: - * exclude any address updates for proposed parcels if the address belongs to a property that is already being updated in another address edit - -### Jul 2015 - -* improve edit rules: - * exclude properties being matched to an approved parcel if the number is already matched to a proposed parcel - -### Jun 2015 - -* improve edit rules: - * resolution of 'gridlocked' properties - now P edits can replace a property if that property can be matched elsewhere - * limit address updates for proposed parcels to one per property number - * better detect overlapping parcels when dealing with muti-assessment retirements - * better determining of when to use new_road flag - * prevent retiring multi-assessment properties that can't be matched later to another valid parcel -* improve comments: - * show if multi-assessments relate to proposed parcels - * show if property updates involve new properties - * explain why valid properties are being removed from multi-assessments (so they can be later matched to the correct parcel) - -### May 2015 - -* improve address validity check to detect invalid ranges for unit and house numbers -* improve parcel validity check to detect missing parish -* improve speed of address update query -* improve support for hotel-style addressing -* improve comments to show original source of properties being removed - -### Apr 2015 - -* fix bug in address match statistics -* improve accuracy of audits and statistics by excluding hyphens and apostrophes from road name comparisons - -### Mar 2015 - -* improve QGIS integration by forcing refresh of spatial index -* upgrade to latest GDAL library `release-1600-gdal-1-11-1-mapserver-6-4-1` (up from `1-10-1`) -* improve comments on M1s to clarify which propnums and crefnos being replaced do not exist in council -* improve readability of documentation with new webpage template (`viewdocs-yeti`) -* add parcel area to Vicmap audit -* provide central location for latest releases: https://github.com/pozi/PoziConnect/releases/latest - -### Feb 2015 - -* massively improve performance of council parcel audit for councils who don't maintain crefno (from 14 minutes down to 16 seconds) -* improve commenting to show if propnum being removed from parcel exists in council records, and also if property being matchecd is a proposed one -* clean up PIQA output by excluding non-primary address records - -### Jan 2015 - -* improve warning on potentially conflicting locality -* include more address updates (eg, change in building name) -* improve reporting for discrepancies between Council addresses and Vicmap addresses - -### Dec 2014 - -* package Pozi Connect into Windows installer -* prevent populating address attributes that violate M1 rules -* add Vicmap Property Address audit, including 'cohesion' setting to help find fragmented properties -* cater for Vicmap parcels without parcel-prop link - -### Nov 2014 - -* improve processing logic to prevent rejects at SKM - -### Oct 2014 - -* create separate subfolders for various output files -* fix spatial output by separately processing approved and proposed address updates - -### Sep 2014 - -* document how to use audit spreadsheets -* commence tracking history of M1 edits -* improve comments, including adding address details and warning for conflicting localities -* improve logic for populating pfi values only when required - -### Aug 2014 - -* add property statistics reporting -* add new retirement scenario -* eliminate duplicate records -* add Vicmap parcel audit - -### Jul 2014 - -* check for invalid plan prefixes, invalid characters in address fields, SPI length -* improve comments - -### Jun 2014 - -* standardise audit processes -* create Valuer General report - -### May 2014 - -* spatialise M1 and Audit output - visualise audits and M1s as map layers -* add check for missing plan prefix, unit number, floor type -* cater for base property numbers - -### Apr 2014 - -* detect invalid characters in parcel descriptions -* improve comments and address checking -* add addresses to multi-assessment updates - -### Mar 2014 - -* check for valid road name and type - -### Feb 2014 - -* introduce council property address audit -* check for out-of-range plan numbers -* check for invalid characters in parcel descriptions - -### Jan 2014 - -* introduce council parcel audit -* check for valid property numbers - -## Complete History - -For a complete history of all changes, see: -https://github.com/pozi/PoziConnectConfig/commits/master/~Shared/ diff --git a/docs/m1s/load-reports.md b/docs/m1s/load-reports.md deleted file mode 100644 index 3b40694..0000000 --- a/docs/m1s/load-reports.md +++ /dev/null @@ -1,19 +0,0 @@ -# Load Reports - -## Report Messages - -### `Cannot Determine Property Pfi >1 Property Found for Parcel Identifier` - -### `Cannot Determine Parcel Pfi SPI Not Found` - -### `Invalid Datum Provided` - -### `M1 Road-Locality combination does not exit and not a new road` - -### `Original rural address would fall outside property` - -### `Parcel has no property link M2 required for fix` - -### `Property Identifier has multiple matches` - - diff --git a/docs/m1s/m1-output.md b/docs/m1s/m1-output.md deleted file mode 100644 index 3bcef6c..0000000 --- a/docs/m1s/m1-output.md +++ /dev/null @@ -1,9 +0,0 @@ -# Pozi Connect: M1 Output - -### History File - -The history file maintains every record generated by Pozi Connect, whether you've submitted them or not. - -It is not imperative that you submit every M1. If a discrepancy remains unresolved, Pozi Connect will just regenerate the same edit every time, so it doesn't matter if you don't submit an M1. - -Pozi Connect does have the ability to remember if a particular edit has been generated before, but it only uses this to display the date in the last column of the M1. It will always include all potential edits on the M1, even if they have been generated before. \ No newline at end of file diff --git a/docs/m1s/precise-addressing.md b/docs/m1s/precise-addressing.md deleted file mode 100644 index 6bb3176..0000000 --- a/docs/m1s/precise-addressing.md +++ /dev/null @@ -1,96 +0,0 @@ -# Precise Addressing - -By default, property addresses positions are determined by DELWP. Based on information provided by the council (such as what parcels are occupied by the property, and the address attributes), address points are placed automatically inside the property boundary, typically at eight metres inside the centre of the property frontage. - -Councils have the option of specifying the exact location in their M1s. This is the basis of rural (distance-based) addressing, but it can also be used within urban areas to make addresses more usable. It is especially useful to specify separate address locations for multi-assessment properties, where each property can have its own separate entrance. - -Pozi Connect can be configured to obtain address coordinates from a data source maintained by the council. The location information can be stored within the property system itself, or in an external file like a CSV, TAB or SHP file. The coordinates are read or derived from the source, and appended to the existing address attributes already obtained from the property system. Address locations are optional, so a council needs only to maintain address location information for the addresses it wants to change from the default or existing location in Vicmap. - -## Prerequisites - -Acceptable formats: - -* MapInfo TAB -* Esri SHP -* CSV -* Property System (eg, Pathway, Authority) - -Spatial tables must contain point geometries. Non-point geometries will be ignored. - -The following fields are used by Pozi Connect. The names of the fields in the point table can be different to the names specified here. - -#### Required field: - -* `propnum` - -#### Optional fields: - -* `house_number_1` (if not specified, Pozi Connect will assume it's the council's primary address) -* `is_primary` (if not specified, Pozi Connect will assume it's a primary address) -* `outside_property` (if not specified, Pozi Connect will assume it's inside the property) -* `distance_related_flag` (if not specified, Pozi Connect will populate the value based on the council's preferred default) - -#### For non-spatial sources (eg, property system, CSV): - -* `easting` -* `northing` -* `datum_proj` (if not specified, Pozi Connect will populate the value based on the council's preferred default) - -#### For spatial sources (eg, TAB, SHP): - -Pozi Connect will obtain the coordinates from the spatial point object itself. Councils do not have to populate coordinates manually. The coordinates will be extracted in the pre-determined coordinate system, and rounded to the nearest metre along each axis. - -## Pozi Connect Configuration - -If your council has a support and software maintenance arrangement for Pozi Connect, Groundtruth will configure the Precise Addressing functionality for you. Send your address point table to Groundtruth to get started. - -What to provide to Groundtruth: - -* zipped address point table (TAB, SHP or CSV) -* exact file path of the address point table on your network -* preferred value for `distance_related_flag` -* preferred value for `datum_proj` (if using non-spatial source) - -The new configuration will returned to you. - -#### Before - -``` -Swan Hill M1 - 1 - Import Authority -Swan Hill M1 - 2 - Import Vicmap -Swan Hill M1 - 3 - Generate M1 -``` - -#### After - -``` -Swan Hill M1 - 1 - Import Authority -Swan Hill M1 - 2 - Import Rural Addresses -Swan Hill M1 - 3 - Import Vicmap -Swan Hill M1 - 4 - Generate M1 -``` - -## Use Cases - -* **Rural address**: place point at property entrance, eight metres inside the boundary, and populate the property number -* **Differentiate property entrance locations for multi-assessments**: place point at each entrance, and populate each with the respective property number -* **Shared rural driveways**: as above, and maintain a field for `outside_property` and populate it with 'N' in any of the records where the address point is not within its own property boundary - -## Limitations - -There are some limitations of support for precise addressing in Pozi Connect. - -Councils can choose to fund development of Pozi Connect to provide the functionality they require. Contact Groundtruth for a quote. - -##### Updating Address Locations - -Pozi Connect bases its updates on non-spatial criteria. It doesn't compare coordinates of Vicmap vs coordinates in the council's point table. Therefore, differences in address point locations are not currently detected by Pozi Connect. - -##### Secondary Adresses - -Pozi Connect currently supports updating of only one address per property. There is no support for updating secondary addresses. - -Any addresses in the point table that are specified as non-primary will be filtered out and ignored by Pozi Connect. - -If you require secondary addresses to be added, updated or removed in Vicmap, it is recommended to add this information manually to your next M1. - diff --git a/docs/m1s/spatial.md b/docs/m1s/spatial.md deleted file mode 100644 index 0898169..0000000 --- a/docs/m1s/spatial.md +++ /dev/null @@ -1,7 +0,0 @@ -# Spatial Output - -## Find non-contiguous/fragmented properties. - -The new layer, called `Audit - Vicmap Property Address.TAB` contains a field called `cohesion`. Properties that are nice and rectangular have a cohesion value that is close to 1. Properties with a value close to 0 are likely to be fragmented and may require further attention. - -Open up the table in MapInfo, and sort by the cohesion field. Select the first record, and click Ctrl-A to locate it on the map. If a property is really fragmented, you may not even see it, because MapInfo will zoom to the middle where they may not be anything to see. You may have to zoom out or add the selection to the map window as its own layer and give it a really thick colourful border so you can find it. diff --git a/docs/m1s/statistics.md b/docs/m1s/statistics.md deleted file mode 100644 index 80744a6..0000000 --- a/docs/m1s/statistics.md +++ /dev/null @@ -1,93 +0,0 @@ -# Pozi Connect: M1 Statistics - -## Usage - -After generating your M1 in Pozi Connect, visit the [Pozi Connect Property Health Dashboard](http://dashboard.pozi.com/property/). - -![Pozi Connect Property Health Dashboard](http://i.imgur.com/kOlywWO.png) - -In Windows Explorer, navigate to your `PoziConnect\output\Statistics\` folder, and drag your property statistics .json file from the folder and drop it into the Property Health Dashboard web page. - -View your statistics. - -Optionally download a PDF report by clicking the red button. - -## Statistics Items - -Item|Description -:--|:-- -`lga_code`| -`vicmap_properties`| -`vicmap_parcels`| -`vicmap_parcel_properties`| -`council_properties`| -`council_parcels`| -`council_parcel_properties`| -`council_properties_in_vicmap`| -`council_properties_not_in_vicmap`| -`vicmap_parcels_no_propnum`| -`vicmap_parcels_no_propnum_ps600000+`| -`vicmap_parcels_no_propnum_tp`| -`vicmap_parcels_no_propnum_other_plan`| -`vicmap_parcels_no_propnum_cm`| -`vicmap_parcels_no_propnum_res`| -`vicmap_parcels_no_propnum_crown_parcel`| -`vicmap_parcels_no_propnum_plan_related`| -`vicmap_parcels_no_propnum_crown_desc`| -`vicmap_propnum_not_in_council`| -`vicmap_propnum_not_in_council_approved`| -`vicmap_propnum_not_in_council_proposed`| -`vicmap_address_in_council`| -`vicmap_address_not_in_council`| -`vicmap_properties_cm_address`| -`vicmap_parcels_ncpr`| -`council_address_in_vicmap`| -`council_address_in_vicmap`| - -## Data Health Indicators - -The three main statistics displayed at the top of the report will give you a good idea of the health of the council's data. We expect these statistics to improve as the council submits its M1s. The tips below will enable you to proactively target the issues behind the remaining issues to further improve the statistics. - -### Council properties not in Vicmap - -Open your `Audit - Council Parcel.csv` spreadsheet, and filter by: - -* propnum_in_vicmap = 0 -* m1_edit_code = (blank) - -This will give you all the properties that aren't in Vicmap and aren't being matched by Pozi Connect. You'll probably need to fix the parcel descriptions in your property system in order for Pozi Connect to find a match. - -### Vicmap parcels without propnum - -Open your `Audit - Vicmap Parcel.csv` spreadsheet, and filter by: - -* propnum_in_council = 0 - -This will give you all the parcels that don't have a property number. You'll need to allocate the parcel descriptions to the appropriate properties in your property system in order for Pozi Connect to find a match. - -### Vicmap propnum not in Council - -There is no need to do anything about these. They will be removed on the -next M1. - -## FAQ - -#### Why are there items like `vicmap_parcels_no_propnum`, and not `vicmap_properties_no_propnum`? - -Pozi Connect treats properties as council-defined entities. In a council-centric view, a 'property' is created when the council assigns a property number to one or more parcels. (Although Vicmap does create property records with null property numbers, Pozi Connect doesn't see these as having any real meaning to the council.) - -Statistics items like `vicmap_parcels_no_propnum` are measures of the number of parcels to which the council should assign a property number. - -#### I've just updated Vicmap, and now I want to see my latest stats. - -To generate updated statistics, Pozi Connect needs to import the council's latest property data and the latest version of Vicmap. It re-calculates the statistics when it generates the M1. - -Follow the usual three (or four) steps that you do for doing an M1. At the end of the step 3, Pozi Connect automatically launches the [webpage](http://dashboard.pozi.com/property/) in your browser and you can drag the `PoziConnect\output\Statistics\[your council] Property Statistics.json` file into the webpage. - -Whether you choose to submit the M1 that gets created is optional. - -#### Troubleshooting - -If you experience problems with seeing the result in Internet Explorer, try using a different web browser. - - diff --git a/docs/piqa.md b/docs/piqa.md deleted file mode 100644 index fd22765..0000000 --- a/docs/piqa.md +++ /dev/null @@ -1,47 +0,0 @@ -# PIQA - -Each year, Victoria's [Department of Environment, Land, Water & Planning](http://www.delwp.vic.gov.au/) (DELWP) requires councils to supply it with an extract of property and address information from their internal property systems to be used for an annual Property Information Quality Audit (PIQA). - -The process of extracting, filtering and formatting this data is time consuming and often overwhelming for councils, and can require the participation and co-operation of council staff members across GIS, Rates and IT departments. - -[Pozi Connect](https://www.pozi.com/pozi-connect/) (formerly known as PlaceLab) is a tool developed by Pozi, with financial support of DELWP, that enables councils to quickly and accurately compile their property and address information into the required PIQA format. - -## Instructions For PIQA Participants - -When DELWP requests you to submit a PIQA extract for your council, follow these five easy steps: - -1. Download the [Pozi Connect installer](https://github.com/pozi/PoziConnect/releases/latest). (If you have a previous installation of Pozi Connect, please remove it before proceeding by deleting your existing `PoziConnect` or `PlaceLab` folder.) -2. Run the installer, and when it prompts you, specify a folder location. You can choose anywhere; somewhere like `C:\Temp\` or the desktop will be sufficient. -3. Navigate to the newly-created PoziConnect folder location, and run PoziConnect.exe by double-clicking it. -4. From the Task drop-down list, select the item that relates to your council (eg, Alpine Shire Council would choose 'Alpine PIQA'). If you are prompted for a database username and/or password, enter them. You may have your own credentials that you can use, or you may use the database administrator credentials. Then click OK and wait for the application to run (it can take several minutes). -5. Check the `PoziConnect\output` folder (or you may have specified your own location in the settings) for a newly created 'PIQA Export.zip' file. This file contains two CSV spreadsheets that have been generated from the council’s property and address data. Email the zip file to your DELWP contact. - -If you experience any difficulties such as the Pozi Connect failing to start, please download and install the [Microsoft Visual C++ 2008 Redistributable Package (x86)](http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en), and try running Pozi Connect again. - -For any issues that are not solved by installing this patch, please contact Groundtruth. - -## FAQ - -### How does Pozi Connect connect to the property system? - -Pozi Connect uses your PC’s existing ODBC connection settings. It does not require any additional network or firewall configuration. - -### Does Pozi Connect extract any confidential information? - -Pozi Connect only extracts the tables and fields from your property system that contains information relevant to the PIQA. You can check for yourself what information will be sent to DEPI by opening up the CSV files located in the “Output” folder in Excel. - -### Does Pozi Connect make any changes to the property system? - -Pozi Connect does not perform any update on your property database. It simply reads data from the database tables via the PC’s ODBC connection, similar to the Import function in Access, Excel or Crystal Reports. - -### How does Pozi Connect work? - -Pozi Connect extracts tables from your council’s property database and imports them into a temporary SQLite database file. It then performs a series of queries (customised for each council) on this file to generate PIQA-compliant CSV files that contain the council’s address and parcel information required for the PIQA audits. These two CSV files are automatically zipped up for you, ready for emailing to DEPI. - -### What else is Pozi Connect capable of? - -Pozi Connect has other tricks up its sleeve. It generates map layers from corporate databases (spatial and non-spatial), performs spatial data analysis, converts between data formats (Esri SHP, MapInfo TAB, DXF, KML, and others), loads data into spatial databases (SQL Server 2008, PostGIS, Oracle Spatial), and generally automates many of the tasks that GIS Administrators find themselves doing on a regular basis. - -Most importantly, it can [automate your M1 workflow](https://www.pozi.com/pozi-connect-for-m1s). - -Contact Pozi to find out how you can put Pozi Connect to work in your council’s GIS. diff --git a/docs/template.html b/docs/template.html deleted file mode 100644 index bb0659d..0000000 --- a/docs/template.html +++ /dev/null @@ -1,113 +0,0 @@ - - - - Pozi Connect Docs - - - - - - - - - - - - -
-
-
-
- Pozi Connect Docs - -
- -
-
- -
- {{CONTENT}} -
-
- - - - - - - - \ No newline at end of file