Imports are case sensitive
Make sure all fields in your CSV file are in lower case to avoid issues
Format for importing a combination of assets
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):
|
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. |
Pole import options
Update poles matching by name: If the existing Neara file has 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 Neara 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 Neara file. Nothing will be overwritten, hence user may potentially get duplicate poles or poles very close to each other.
The 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.
If there is a location that contains more than one type of data, each type of data needs its own line with its own type description.
For example: separate lines for ground, veg, structure, and conductor.
Format for importing Pole assets
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 Neara file has 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 Neara 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 Neara file. Nothing will be overwritten.
Setting the pole base as a structure point will auto-add a pole to that defined location.
This will also create a ground point in the process. If you wish to avoid auto-adding a pole, use another point type as your pole base (such as special).
Example import CSV file formats
Download the examples from the attachments at the bottom of this article.