GIS Import JSON Schema Documentation
Use the json schema files to validate your geojson files you intend to import into an AND project file.
Version
V 0.8 - 10.4.2025
File Names
The file names to be processed by import are mandatory. They should be within one folder or zip file.
file name | geometry type | must relate to schema |
---|---|---|
ducts.geojson | LineString | importDuctsSchema.json |
trenches.geojson | LineString | importTrenchesSchema.json |
sites.geojson | Point | importSitesSchema.json |
GeoJSON File Description
For a description of the possible content of the GeoJSON files, see the detailed descriptions, which can be accessed via the links on the left.
Subtitles within Description
Component-mapping
the value of this property can be taken to map a AND library component
This must then be set up in the Mapping UI.
Value-mapping
Allowing you to use your own enums the value of this property can be translated to a AND value
Target
Information how the imported value will be stored within AND data
Recommended minimal content
- files must follow the GeoJSON standard
- sites must have geometry type “Point”
- trenches and ducts must have geometry type “LineString”
Apart from that, there are no really mandatory data in input. However, to get better results, it is recommended that you set the following properties in input:
-
duct.properties.type If that property isn’t set the duct will be imported as a trenchduct inside a trenchline. Microducts are only imported correctly, if the type of the legs is “sub_duct” and the type of the parents is “duct_package”.
-
duct.properties.parent_id If microduct legs have “parent_id” not set, the owning ductpackage is found by position. If several Microduct packages lie over each other the parent found by position is arbitrary. In that case “parent_id” must be set to ensure that the legs are connected to the right microduct package.
-
site.properties.logical_type Creating a routable network requires “logical_type” to be set for sites. If the “logical_type” is not set in the input, it is recommended to switch off “Create Pins” in the dialog for GisImport.
Coordinate System
Must be WGS84
optional you may use the non standard crs property for other coordinate systems/projections
Units
All lengths units are in meters
enums used in AND SITES GIS-Import FeatureCollection
properties.logical_type
enum int | enum string | description | WebSolution Value |
---|---|---|---|
0 | n/a | n/a, | 0 |
80 | TI | technical Infrastructure | |
100 | RS | Receiving Station | 1000 |
105 | HE | Headend | |
110 | POP | Point of Presence | 1100 |
120 | CO | Central Office | 1200 |
200 | MPOP | Mini POP, | 2000 |
300 | DP | Distribution Point, | 3000 |
310 | FSP | Fiber Splicing Point, | 3100 |
320 | FDP | Fiber Distribution Point, | 3200 |
330 | FSDP | Fiber Distribution and Splicing Point | |
500 | POI | Point of Interest | 5000 |
510 | RDP | Radio Distribution point / Cell Tower | 5100 |
550 | BTP | Building Termination Point | 5500 |
560 | BEP | Building Entry Point | |
600 | FN | Fiber-Node | |
610 | AP | Amplifier-Point | |
620 | PS | PS Power-Source |
properties.site_type
enum int | enum string | description | WebSolution Value |
---|---|---|---|
0 | ANY | “site any” | 10000 |
1 | RES | “residential any” | 10010 |
2 | COM | “commercial any” | 10020 |
3 | PUB | “administrative any” | 10030 |
4 | TEC | “technical any” | 10040 |
5 | IFSTRUCT | “infrastructure any” | 10050 |
6 | TOWER | “Tower” | 10060 |
7 | TRANST | “Transformer tower” | 10070 |
13 | SRES | “Single-family house (residential)” | 10130 |
14 | DRES | “Duplex house (residential)” | 10140 |
15 | TRES | “Terraced house (residential)” | 10150 |
23 | MDRES | “Multiple dwelling house (residential)” | 10230 |
24 | ARES | “Apartment house (residential)” | 10240 |
25 | HRES | “High-rise house (residential)” | 10250 |
32 | OFB | “Office building” | 10320 |
33 | SCOM | “Commercial single” | 10330 |
34 | MCOM | “Commercial multi” | 10340 |
35 | MALL | “Commercial mall” | 10350 |
36 | MARKET | “Market” | 10351 |
37 | KIOSK | “Kiosk” | 10352 |
38 | WAREH | “Warehouse” | 10360 |
39 | FACTORY | “Factory building” | 10370 |
40 | INDUSTRY | “Industrial building” | 10375 |
48 | FARM | “Farm” | 10380 |
49 | HOTEL | “Hotel” | 10390 |
50 | GOV | “Government building” | 10500 |
51 | ADMIN | “Administrative building” | 10501 |
52 | SCHOOL | “School” | 10510 |
53 | UNI | “University” | 10512 |
54 | KGN | “Kindergarten” | 10515 |
55 | CHURCH | “Church” | 10520 |
56 | HOSPITAL | “Hospital” | 10530 |
57 | TRAINST | “Train station” | 10540 |
58 | TRANSPORT | “Transportation” | 10545 |
59 | GARAGE | “Parking garage” | 10547 |
60 | AIRPORT | “Airport” | 10550 |
61 | SPORTS | “Sports building” | 10560 |
62 | STADIUM | “Stadium” | 10570 |
100 | INFRA_B | “Building (infrastructure)” | 11000 |
101 | INFRA_T | “Tower (infrastructure)” | 11010 |
102 | INFRA_TR | “Transformer tower (infrastructure)” | 11020 |
103 | INFRA_TS | “Transformer station (infrastructure)” | 11030 |
150 | CABINET | “Cabinet” | 11500 |
152 | MANHOLE | “Manhole” | 11520 |
153 | HANDHOLE | “Handhole” | 11530 |
154 | EARTHHOLE | “Earthhole” | 11540 |
155 | TRENCHDIV | “Trench Divider” | 11550 |
160 | CLOSURE | “Closure” | 11600 |
180 | MAST | “Mast” | 11800 |
182 | POLE | “Pole” | 11820 |
190 | WALLBOX | “Wallbox (outside)” | 11900 |
200 | FLOOR | “Floor” | 12000 |
210 | ROOM | “Room” | 12100 |
220 | FLAT | “Appartment” | 12200 |
250 | O_OFFICE | “Office (open-plan)” | 12500 |
252 | R_OFFICE | “Office (room)” | 12520 |
260 | WALLBOX_IS | “Wallbox (inside)” | 12600 |
270 | CABINET_IS | “Cabinet (inside)” 12700 | |
300 | FRAME | “Distribution Frame” | 13000 |
350 | CONST | “Construction” | 13500 |
400 | RACK | “Rack” | 14000 |
410 | SHELF | “Shelf” | 14100 |
420 | CASS | “Cassette” | 14200 |