ePlan Victoria - Project Attributes

Description

A list of the project attributes required to generate a submission to ePlan Victoria.

Access

Home / Tools / Attributes / Project

Requirements
  • Xchange-ePlan module
  • An open project based on the LISTECH - ePlan Victoria template
Attributes

The following table lists the project attributes used in the Survey Header for the ePlan Victoria submission.

Project Attribute Description Format
Plan Number Enter the Plan Number. Enter "LV-To-Supply", if a plan number has not been allocated. Include the checksum and exclude spaces.
Surveyor Reference Firms internal reference (Surveyors Reference and Surveyors Version are concatenated in the exported file).  
Surveyor Version Firms internal version (Surveyors Reference and Surveyors Version are concatenated in the exported file).  
Survey Classification (optional) Select the survey classification from the list.
Survey Type Select the survey type from the list.
Legislation Select the Legislation the plan is based on. Multiple legislations are allowed.
Purpose of Survey Select the sections of the act that apply to the survey plan. An additional secondary purpose can be added using the 'Additional Purpose of Plan' annotation.
Surveyor Enter the full name of the surveyor as registered.
Surveyor Registration Number Enter the surveyor's registration board member number.
Local Government Area Select the Local Government Area from the list.
Parish Select the Parish from the list.
Survey Date Enter the Date of the Survey.
Annotation Add an Annotation attribute group then add the following attributes:
  • Type- Select the type of annotation from the list. The required annotation types are dependent on the type of Legislation and the Purpose of Survey.
  • Text- Enter the annotation. This may be any information that could benefit future surveyors, examiners or auditors.
Annotations can be added to:
  • Project Attributes - Add an annotation that refers to the entire plan as a project attribute. For example: Annotation[@Type= 'Report on Datum'] should be created as a project attribute.
  • Project Attribute Groups - Add an annotation that refers to a specific group in the Project attributes. For example: Annotation[@Type= 'The Basis For Allocation Of Lot Entitlement And Liability'] should be created as an attribute of the Owners Corporation group.
  • Polygon Attributes - Add an annotation that refers to a particular polygon as a polygon attribute. For example: Annotation[@Type='Restriction Expiry Date'] should be created as an attribute of the restriction polygon it refers to.
Enter Text as a continuous string without formatting.

The following table lists the project attributes related to Easements.

Project Attribute Description Format
Name Enter a unique name of the easement. This name is used to link the easement to the easement polygon. EAS#
Plan Number For an existing easement, enter the plan number. For a created easement the plan number is sourced from the projects plan number. Exclude spaces and checksum.
State Select 'existing', 'created', 'affected' or 'extinguished' from the list.
Purpose Select the purpose of the easement from the list.
Beneficiary Enter the authority or land parcel that benefits from the easement. If the beneficiary is both an authority and a land parcel then add an Easement Beneficiary Annotation instead.
Annotation Add an Annotation attribute group then add the following attributes:
  • Type- Select the type of easement annotation from the list.
  • Text- Enter the annotation. This may be a more detailed description of the easements purpose, the origin of the easement or a beneficiary.
Enter Text as a continuous string without formatting.

The following table lists the project attributes related to Restrictions.

Project Attribute Description Format
Name Enter a unique name for the restriction. This name is used to link the restriction to the restriction polygon. RST#
Plan Number For an existing restriction, enter the plan number. For a created restriction the plan number is sourced from the projects plan number. Exclude spaces and checksum.
State Select 'created', 'affected' or 'extinguished' from the list.
Description Click Browse and enter the details of the restriction. Benefits and burdens are added to individual lots.

The following table lists the project attributes related to Owners Corporation.

Project Attribute Description Format
Name Enter a unique name for the Owners Corporation. OC#
Plan Number For an existing owners corporation, enter the plan number. For a created owners corporation the plan number is sourced from the projects plan number. Exclude spaces and checksum.
State Select 'created', 'affected' or 'extinguished' from the list.
Limitation Select the limitation from the list.
Address Add an Address attribute group, then add the following address attributes:
  • Type- Select if the address is a primary or secondary address. This address is for serving notices regarding the Owners Corporation.
  • House Number | Flat Number | Level Number - Enter the appropriate attributes for the house, flat or level number.
  • Road - Add a Road group.
    • Name - Enter the name of the road as it appears in Vicmap Address.
    • Type - Select the type of road from the list as it appears in Vicmap Address.
    • Ownership- Select the ownership type from the list.
  • Locality- Select a locality from the list.
  • Postcode- Enter a postcode.
Annotation Add an Annotation attribute group then add the following attributes:
  • Type- Select the type of annotation from the list. An Owners Corporation group must include the annotation types "Purpose Of The Owners Corporation" and "The Basis For Allocation Of Lot Entitlement And Liability".
  • Text- Enter the annotation.
Enter Text as a continuous string without formatting.

The following table lists the project attributes related to Depth Limitation.

Project Attribute Description Format
Name Enter a unique name for the depth limitation. DL#
Description Enter the depth limitation and the lots affected by the limitation.
Notes
  • Easements and Owners Corporations must have their geometric extents defined by a polygon.
  • Restrictions can have their geometric extents defined by a polygon but this is not essential.
  • If a project is in two Administrative Areas, add multiple Administrative Areas (Local Government Area or Parish) to the Project Attributes.
Related topics

Top of page TOP OF PAGE