Import Geo data: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
Maxim@tygron.com (talk | contribs)
No edit summary
No edit summary
 
Line 2: Line 2:


==Vector data==
==Vector data==
With the [[Geo_Data_Wizard|Geo data wizard]] you can easily import vector data. The wizard also helps you to transform your data to the proper format for importing.  
Use the [[Geo_Data_Wizard|Geo data wizard]] to import vector data. The wizard also helps you to transform your data to the proper format for importing.  
There are five different import methods:
There are five different import methods:
# with a [[GeoJSON]], [[GeoPackage]] or [[DXF]] file for 2D data
# with a [[GeoJSON]], [[GeoPackage]] or [[DXF]] file for 2D data
Line 9: Line 9:
# through a [[CSW|Catalogue Service for the Web (CSW)]].
# through a [[CSW|Catalogue Service for the Web (CSW)]].
# through [[ArcGIS Online]]: with this option you can also log in to your [[How to log in an ArcGIS Online account in the Tygron Client Application|ArcGIS Online organization]] or [[How to log in an ArcGIS Enterprise account in the Tygron Client Application|ArcGIS Enterprise portal]] to add [[Map service]] data to your project.   
# through [[ArcGIS Online]]: with this option you can also log in to your [[How to log in an ArcGIS Online account in the Tygron Client Application|ArcGIS Online organization]] or [[How to log in an ArcGIS Enterprise account in the Tygron Client Application|ArcGIS Enterprise portal]] to add [[Map service]] data to your project.   
Choose a method based on how and where you have your data available.


Shapefiles are not directly supported; these can be converted to a [[GeoPackage]] or [[GeoJSON]] using [[QGIS]].
Shapefiles are not directly supported; these can be converted to a [[GeoPackage]] or [[GeoJSON]] using [[QGIS]].
Line 17: Line 16:
# through a [[WCS|Web Coverage Service (WCS)]] or [[WMS|Web Map Service (WMS)]].
# through a [[WCS|Web Coverage Service (WCS)]] or [[WMS|Web Map Service (WMS)]].
# as a [[GeoTIFF Overlay]] with optional [[QML]]
# as a [[GeoTIFF Overlay]] with optional [[QML]]
Choose a method based on how you have your data available.


==Plan==
==Plan==
It is possible to import a spatial plan into the {{software}}, either for visualization or to calculate the effects on the surroundings.  
It is possible to import a spatial plan into the {{software}}, either for visualization or to calculate the effects on the surroundings.  
When importing a 2D plan, the {{software}} models corresponding with the chosen [[Function]]s will be used to visualize the plan.
For 2D plans, the software uses models that correspond to the selected [[Function]]s for visualization.
When importing 3D models, the actual model, including textures, will be imported.
When importing 3D models, the actual model, including textures, will be imported.
*[[Spatial plan]]
*[[Spatial plan]]
Line 27: Line 25:
{{article end
{{article end
|notes=
|notes=
* The Geo dataset should have a CRS (Coordinate Reference System) defined, for the {{software}} to properly translate the coordinates to the right location.  
* The Geo dataset should have a CRS (Coordinate Reference System) defined, for the {{software}} to properly translate the coordinates to the right location.
* Vector data: {{software}} only supports polygons; the data wizard automatically buffers any line or point features into polygons.
* Vector data: {{software}} only supports polygons; the data wizard automatically buffers any line or point features into polygons.
* Vector data: all desired attributes must be numerical, so that they can be loaded as valid [[attribute]] values. Non-numeric attributes are ignored when attempting to load them as attributes.
* Vector data: all desired attributes must be numerical, so that they can be loaded as valid [[attribute]] values. Non-numeric attributes are ignored when attempting to load them as attributes.
Line 47: Line 45:
* [[ArcGIS Online]]
* [[ArcGIS Online]]
* [[Map service]]
* [[Map service]]
|api=
* [[Api session items sources]]
* [[Api session event editor source]]
}}
}}


{{Template:GeoDataOverview}}
{{Template:GeoDataOverview}}

Latest revision as of 14:59, 10 July 2026

Almost any Geo data (data that refers to specific locations and contains geometry) can be imported into Tygron Platform. There are different methods for importing Geo data. The method to choose is based on how you have your data available, as vector or raster data and/or what the data represents.

Vector data

Use the Geo data wizard to import vector data. The wizard also helps you to transform your data to the proper format for importing. There are five different import methods:

  1. with a GeoJSON, GeoPackage or DXF file for 2D data
  2. with a IFC, CityGML or SLPK file for 3D data
  3. through a Web Feature Service (WFS)
  4. through a Catalogue Service for the Web (CSW).
  5. through ArcGIS Online: with this option you can also log in to your ArcGIS Online organization or ArcGIS Enterprise portal to add Map service data to your project.

Shapefiles are not directly supported; these can be converted to a GeoPackage or GeoJSON using QGIS.

Raster data

There are two different import methods:

  1. through a Web Coverage Service (WCS) or Web Map Service (WMS).
  2. as a GeoTIFF Overlay with optional QML

Plan

It is possible to import a spatial plan into the Tygron Platform, either for visualization or to calculate the effects on the surroundings. For 2D plans, the software uses models that correspond to the selected Functions for visualization. When importing 3D models, the actual model, including textures, will be imported.

Notes

  • The Geo dataset should have a CRS (Coordinate Reference System) defined, for the Tygron Platform to properly translate the coordinates to the right location.
  • Vector data: Tygron Platform only supports polygons; the data wizard automatically buffers any line or point features into polygons.
  • Vector data: all desired attributes must be numerical, so that they can be loaded as valid attribute values. Non-numeric attributes are ignored when attempting to load them as attributes.

See also

API Endpoints