The import of data has been standardised for NET Design and NET Engineering. The import procedure is described directly in the following sections or linked to the description of the import in NET Engineering.
From version NET Design 14.2.1, the import can both import and update data.
Starting the import process
To import data for structural planning, open the corresponding NET Design project or a NET Design template file. You can find out how to do this here.
Switch to the ‘NET Design’ tab. You will find the ‘Import’ button for starting the import dialogue on the far left.
The import settings dialogue opens
The pull-down menu for the source type opens the list of supported data formats.
Import of an atesio workspace
If an atesio workspace is available, it can be imported.
- Selection of the folder in which the workspace to be imported is located
- Selection of the import profile
- Should the optimisation data model be emptied?
- Selection of the source coordinate system
Import of an Comsof Fiber Designer Workspace
The import dialogue also supports the import of an entire Comsof Fiber Designer workspace.
- Selection of the folder in which both the input data and the result data of the calculation are located
- This is where the POP units from the source workspace are assigned to: Residential unit, Business unit. School, Hospital, Public facilities, Discard
- This is where the P2PP units from the source workspace are assigned to: Residential unit, Business unit. School, hospital, public facilities, discard
- Here you can select whether only the input data or also the result data should be imported
The checkbox activates the transfer of additional attributes
Import from a CSV-file
The procedure for importing a CSV file into a NET Design project works in the same way as the CSV import into a NET Engineering project. The description can be found here.
Import from a Excel-file
The procedure for importing an Excel file into a NET Design project works in the same way as importing Excel into a NET Engineering project. The description can be found here Excel import.
Import of a GeoJSON-file
The procedure for importing a GeoJSON file into a NET Design project is the same as for importing GeoJSON into a NET Engineering project. The description can be found here GeoJSON.
Import of the Geopackage-format
The procedure for importing data in Geopackage format into a NET Design project works in the same way as the Geopackage format import into a NET Engineering project. The description can be found here Geopackage.
Import GIS-NB UUIDs
The GIS-NB UUIDs - Universally Unique Identifier - are used to uniquely identify addresses in the subsidised expansion. The UUIDs are specified by the funding organisation.
The UUIDs can be assigned to connection points via the import.
Select the CSV file to be imported that contains the UUIDs.
The UUID import assigns the following during import
- assigns the UUID from the CSV to an existing connection point with identical attributes in the city, postcode, address and house number or
- creates a connection point without geometry including UUID if no connection point exists as described in 1
Import Infas 360 geodata
NET Design supports the direct import of Infas360 address data.
The target object class of the import is the "connection point". The "Cluster" object class (TC_PL_CLUSTER) acts as a geographical filter.
The following attributes are imported. The mapping takes place automatically:
- infas360 address points incl. telecoms overhang (x/y coordinates)
- infas360 address master incl. telecoms overhang (city, postcode, street, house number with addition)
- Number of households or residential units
- Number of businesses
- Institutions differentiated according to the following types (with activated GIS NB module):
- Schools, vocational schools, universities, other educational institutions → Schools
- Administration, care, railway station, court, police → Public institutions
- Hospital → Hospital
The address data is imported into NET Design via the familiar ‘Import’ dialogue. You can find the steps in detail here.
Note
If the same addresses are imported several times, the costs per address point are incurred anew for each import.
Costs and licensing
The use of the Infas360 import is subject to a charge. The number of address points in the cluster and thus to be imported is decisive for the costs. The address credits must be ordered in advance from TKI. Address credit packages are available in the sizes 2,000, 5,000, 10,000, 50,000, 100,000 and 200,000. These are made available via a licence key. The acquired address credits do not expire.
The address credits required for the current import are displayed before the import.
For a quotation, simply contact our sales department by e-mail at sales@tki-chemnitz.de or by telephone on 0371/52 333 500.
Import of data in KML format
NET Design also supports the import of data in kml format. How the import works is described here.
Importing data from the NET Field Survey basic data model
Fill in the required fields as described below.
- Select the NET Field Survey source document. This is the project with the Field Survey data model on PostgreSQL, which must be open.
- Select the spatial filter for the import. The spatial filter must be available in the source project. The spatial filter must exist in the object class ‘Cluster’ with ‘Cluster type’ Planned area.
- Select which object classes are to be imported: All / Connection points
- If the checkbox is activated, unmapped attributes are also transferred
- If the checkbox is activated, features that are not included are also transferred
Import of OSM road centre lines
Using the OpenStreetMap overpass api (Geofabrik), NET Design provides a direct import of OpenStreetMap street centrelines into a NET Design project.
The import takes place within a defined cluster, so there is no need to download and cut the data beforehand.
Manual mapping of the source and target attributes is not supported with this import format. Explanations on standard mapping can be found in the following text.
To make the road categories clearer, they have been summarised and provided with start standard widths. The widths can be adjusted as required before the import.
The import template can also be saved and used repeatedly.
| NR | Theme / Attribute | Settings or actions to be made |
| 1 | Source Type | Here you select the data type of the source data from a pull-down menu |
| 2 | Cluster | The cluster acts as a geometric filter and can be selected both from the graphic and from the pull-down menu |
| 3 | Import-template load | Saved import templates can be reloaded at this point |
| 4 | Import-template save path | If the checkbox is activated, the import templates are saved. The location and name of the file must be specified under Storage location |
| 5 | OSM Overpass Endpoint | Here the import expects the URL for reading the data. The screenshot shows an example endpoint definition. These servers/endpoints are operated by different organisations or persons, the respective usage instructions apply (requests/data volume per day, etc.) |
| 6 | Oneway limiter | If this option is activated, the road width is halved for data records with oneway=1 |
| 7 | Road width (in m) according to type The road width defines the distance between the “possible trenches” after pre-processing. The value 0 means that the “possible trenches” are not mirrored but are created congruently on the road centerlines. | If the checkbox is activated, data is imported with the selected type and the specified road width. The start default values are empirical values that you can change at any time. |
| 8 | Import Button | Starts the import with the selected options |
Standard mapping of OSM attributes - to attributes of the "street-center-line" object class
| street-center-line (TC_PL_STREET_CL) | Attributes from OSM roads-layer |
| IS_INCLUDE | static → 1 (Yes) |
| WIDTH | Width from import form by type |
| IS_PRIVATE | static → 0 (No) |
| STREET | name, if empty, the value from "ref" is used if available |
| LENGTH | CAD length of the line |
| CREATE_CROSSINGS | static → 1 (Yes) |
An overview of the internal summarisation of the "type" attribute from the roads-OSM data to the "road type" in the import can be found here.
| Type aus OSM | becomes road type during import |
| footway,cycleway,pedestrian, | footway |
| track,path,bridleway, | Track/Path |
| service | Service |
| unclassified | Unclassified |
| living_street,residential, | Living / Residential |
| tertiary,tertiary_link, | Tertiary |
| secondary,secondary_link, | Secondary |
| primary,primary_link, | Primary |
| trunk,trunk_link | trunk |
| motorway,motorway_link, | Motorway |
Import of Shape-Data
NET Design also supports the import of shape data. You can find out how to proceed with the import here.