Importing Georeferenced Data

How does CityEngine handle georeferenced data on import.

Vector Data

All georeferenced vector data is reprojected to the Scene Coordinate System during import.

  1. Georeferenced vector data requires a coordinate system on import, if no such data is found, the Select data coordinate system Dialog pops up during import which lets the user choose the coordinate system for the data.
  2. If no Scene Coordinate System is defined for the scene previous to the data import, the Select Scene Coordinate System Dialog pops up and lets the user set the Scene Coordinate System.

Shapefiles (.shp)

CityEngine looks for a .prj file with the same name in the same folder.

File Geodatabase (.gdb)

The coordinate system is read per layer of the gdb dataset.

KML/KMZ

KML/KMZ lat/lon data is always interpreted as WGS 1984. When KML/KMZ dat is imported into a scene with no coordinate system set, UTM with matching zone is suggested as Scene Coordinate System.

OpenStreetMap (.osm)

OSM lat/lon data is always interpreted as WGS 1984. When OSM data is imported into a scene with no coordinate system set, UTM with matching zone is suggested as Scene Coordinate System.

Georeferenced Image Data

Image data is considered to be georeferenced if

No reprojection nor rotation is applied to image data on import. The image's coordinate system is used only as reference system for location, extent and unit (translate and scale transformation) for the image data during import. It is therefore important to have image data ready in the target coordinate system before importing into CityEngine. (See behaviour for GeoTiffs below.)

Reference Coordinate System

CityEngine looks for a .prj file with the same name in the same folder to use as coordinate system for the data. If no .prj file is found, the Select data coordinate system Dialog pops up and lets the user choose the coordinate system for the data.

Map Extent

CityEngine looks for a world file (e.g. .jgw, tfw) in the same folder to read the extent of the data. The world file data is interpreted in the unit found in the coordinate system of the data, and calculated accordingly if required. If no world file is found, size and position of the map can be entered manually in the Map Layer Dialog.

Elevation range

CityEngine looks for minimum and maximum range values in the metadata embedded in the image. The range data is interpreted in the unit found in the coordinate system of the data, and calculated accordingly if required. If no elevation range is found, the elevation range of the map can be entered manually in the Map Layer Dialog.

Elevation range data is only used when the image is used as height map.

GeoTiff (.tif, .tiff with embedded metadata)

GeoTiff data is handled the same way as other georeferenced image data with the following differences:

Parameters for location, extent and elevation range can still be entered manually for non-georeferenced images in the Map Layer Dialog

Copyright ©2008-2017 Esri R&D Center Zurich. All rights reserved.