Please note that imports are case sensitive, make sure all fields are lower case to ensure correct importing. 


Combination CSV Import

Imports a CSV file with the points in 3D space. The order of the CSV columns will not affect the import, as long as there is a heading row with the following headings to identify the columns:


Heading Row Fields
Required or Optional
Function
x
Required
point coordinates
y
Required
point coordinates
z
Required
point coordinates
type


Required


The following types are allowed (type names must follow the below spelling exactly, see also note 2):
  • ground
  • water
  • road
  • veg
  • building
  • electrical
  • railway
  • pipeline
  • special
  • structure
  • cond
name


Optional


A label for the imported point that will be visible in the workspace. If field is empty, then it will be labelled by the type with a sequence no. The sequence number is the order in which the point is listed in the CSV file.
comment
Optional

Only used for poles and adds a comment to the pole notes field in the pole properties information.

The pole import will also have the following options:
  • Update poles matching by name

If the existing PLP file have poles, the import will try to match the imported pole label with the existing pole labels in the file. If a match is found, the import pole properties will override the existing pole properties


  • Merge poles within 2m
           If the existing PLP file has a pole within 2m of a pole in import file, the import pole properties will override this existing pole.            

  • Create new poles

New poles will be created from import file regardless of what is in the existing PLP file. Nothing will be overwritten, hence user may potentially get duplicate poles or poles very close to each other.


See example attached.


Note:

  1. This terrain import will try to build the terrain by interpolating between the nearest two points in the CSV, where the points are close enough. Otherwise, for points that are too far from other points, it will assume the same ground height within a radius around the ground point.
  2. Should there be a location where it contains more than one type of data, each type of data needs its own line with its own type description. For exmaple, one line for ground, one line for veg, one line for structure, one line for cond.

  

Pole CSV Import

To import poles from CSV data, the CSV file needs to have the following, the order of the CSV columns will not affect the import, as long as there is a heading row with the following headings to identify the columns:


Heading Row Fields
Required or Optional
Function
x
Required
pole position coordinate
y
Required
pole position coordinate
type

Optional
Pole with a name that corresponds with pole names in the Pole Library. Where there is no data, a default pole from the Pole Library will be selected.
label
Optional
Pole identifier labels. Where there is no data, a default ID label will be assigned to each pole.
height
Optional
Height of pole above ground in meters. Where there is no data, the default in the Pole Library will be used.


The pole import will also have the following options:
  • Update poles matching by name
If the existing PLP file have poles, the import will try to match the imported pole label with the existing pole labels in the file. If a match is found, the import pole properties will override the existing pole properties


  • Merge poles within 2m
           If the existing PLP file has a pole within 2m of a pole in import file, the import pole properties will override this existing pole.            

  • Create new poles

New poles will be created from import file regardless of what is in the existing PLP file. Nothing will be overwritten.


See example attached.