Import geodata
import_geodataWrites what a reference of the room holds into the model: into terrain creates (created names the new elements), into site writes values at the named IfcSite, into alignment an IfcAlignment from LandXML; dry_run previews. Never asks a service; the reference is the kept answer (reference_id from get_geodata, or a terrain the person uploaded; read_reference lists them). into terrain: an IfcGeographicElement in the IfcSite from its heights, built as create_terrain builds one: thinned (delatin/1) up to epsilon_m or the mesh limit per body, cells without a height masked and never filled, map metres into project m through the model georeference (another EPSG point by point over a bridge, named in the report). base_z is required, never assumed. Moddl_TerrainLayers keeps the origin: Dgm* (file, window, CRS, bridge) and from a service Geodata* (service, fetch, licence, links, credit); a credit goes with whatever is built from it. Without OrthogonalHeight in the georeference it is refused: map heights would put the ground metres away from the building. Ask the person for the height of 0.00 above the vertical datum (building permit, survey) and write it with set_project_origin, source user. The report's terrain_created.dgm: service and fetch, cells, masked cells, epsilon reached, each number with its source, and ground: the terrain under the building against the storey nearest z 0, warned past 3 m (a datum error, or a slope). into site: one parcel (feature: its id from the get_geodata rows) of a parcels reference at the IfcSite named by GlobalId: Pset_LandRegistration.LandID the official identifier (none: refused); Moddl_Geodaten the service, fetch, licence, links, credit, reference id, ParcelArea from the outline (m2; assumed over a projection) and ParcelOfficialArea only where the row carries one. The report names each value with source and the value it replaced. New revision, effect report. A call that succeeds is not a job that's done. Double-check the ground against the building: render_view from two sides.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"reference_id": "<reference_id>",
"into": "<into>"
},
"name": "import_geodata"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| into | Yes | terrain: a terrain from the heights of a GeoTIFF or XYZ reference; site: a parcel of a parcels reference as values of the site; alignment: an Alignment of a LandXML reference | |
| name | No | into terrain: name of the container or the single element | |
| note | No | Your note, stored with the new revision | |
| site | No | into terrain: the IfcSite by GlobalId or Name, needed where the file has several; into site, required: the GlobalId of the IfcSite written | |
| base_z | No | into terrain, required: bottom of the terrain body, world z in m; never assumed | |
| layers | No | into terrain: top to bottom; the last reaches down to base_z. None or one: one terrain element | |
| window | No | into terrain: [min_e, min_n, max_e, max_n] in metres of the raster EPSG (not project m, not the model EPSG); the heights inside it. Left out: the whole raster | |
| dry_run | No | Preview: the planned effect, nothing written | |
| feature | No | into site, required: the parcel, by its id in the get_geodata rows (not its feature index) or its official identifier | |
| stations | No | into alignment: stations run with project metres where the map factor of the georeference moves them by more than 1 mm over the length (assumption stations_follow_project_distance, deviation_m, equations shifted in the report); left out, such a file is refused | |
| alignment | No | into alignment: one Alignment of a LandXML reference placed in the viewer, by its name or #index; left out where the file holds one. Written as create_alignment writes it (line, clothoid, arc, PVI with ParaCurve and CircCurve, StaEquation). Each segment is closed against the end the file states (alignment_import.closure, 1 mm); over it the whole alignment is refused with index and type (spiType other than clothoid, UnsymParaCurve). A Cant of the file is written only with rail_head_distance_m; without it the report (alignment_import.cant) says the cant is there and not written, and cant.call is edit_alignment at the alignment written, with the rows of the file and the field to fill (never a second import) The layouts read back with get_element include alignment; edit_alignment takes the layout keys of create_alignment (positive radii, kind, turn) | |
| epsilon_m | No | into terrain: largest deviation from the raster heights, m; left out: thinned to the mesh limit, the value reached an assumption | |
| request_id | No | Your id for this call: a repeat answers the first result and writes nothing | |
| reference_id | Yes | The reference to write from: get_geodata reference_id, or an upload read_reference lists | |
| station_tolerance_m | No | into alignment: how far in plan, in m, the end of the chain written may lie from the end of the file (the segments close against their own ends, each within 1 mm; the written chain only follows them, so it drifts where a joint kinks). At least 0.001, the default; it only widens. Above it the whole alignment is refused with the drift in the detail and the call with this field in detail.call (the value yours). Reported per segment (closure_m, chain_drift_m), as written_end_gap_m and as assumption chain_drift_tolerance_user | |
| confirm_height_check | No | into terrain: an upload is held against catalogue terrain of the room (dgm.height_check); a cm/mm, ellipsoidal or gross reading is refused REFERENCE_HEIGHT_CHECK. true writes it anyway, only after the person confirmed the heights | |
| rail_head_distance_m | No | into alignment: takes the Cant of the file (CantStation, appliedCant, rotationPoint, clothoid ramps) as the cant layout. The distance of the rail heads the roll is formed with (about 1.5 m on standard gauge): yours to name, never the gauge of the file (about 1.435 m); the report shows both. Source user, between the gauge of the file and twice it (rail_head_distance_implausible: a value in mm or another unit is refused with both values). Refused if the Cant cannot be taken whole (index and type), reaches the distance, or the alignment has no profile; a clothoid ramp is read as linear (assumption cant_clothoid_linear with its deviation_m) |