Classic geometry file formats as .obj, .off, .ply, .stl or .dae do not support the utilization of coordinate systems besides from a local system, that can not be defined more precisely. This feature is a major requirement for global applications, exchanging geo-referenced models e.g. in the context of outdoor augmented reality applications.

For this reason, the present project evaluates different possibilities of geo-referenced geometry files.

Next to wide-spread standards as GeoVRML, X3D, CityJSON, GeoJSON, GML or KML, we introduce four geo-referenced extensions called .geoobj, .geooff, .geoply and .geostl. While, the named standard formats allow defining objects with multiple additional features, they also come with an overhead according to the file size and an increased structural complexity with disadvantages to the read performance. This overhead has to be minimized in many use cases and for this reason, some file formats are more suitable than others. For completeness: the overhead can be further reduced using binary representations (like binary obj or stl) instead of textual ones, but since not all named formats support a binary mode, this is ignored in favor of human-readability within this project and comparison.

In this chapter you can find multiple extensions of classic geometry file formats. All of these extensions support two major features:

1. Defining the coordinate reference system (CRS) of the used vertices' coordinates
2. Defining an optional origin, which represents an absolute geo-referenced location and an implicit local Cartesian coordinate frame for the models with a metric unit.

Some proposed file formats support additional features such as:

• Geographical extent
• Transformation information (local per object or global for all vertices)
  • Scaling factor
  • Translation
  • Rotation
• Arbitrary meta information, with three fixed keys:
  • Global per file such as:
    • Translation unit (tu): any unit can be used. The present project only supports transformations with metres ( m)
    • Rotation unit (ru: any unit can be used. The present project only supports transformations with degrees ( deg)
  • Local per object
    • Type (type): Type of the geo-object such as Building, Car, etc.

The .geoobj file format extends the classic .obj file format with two line-types:

1. The crs line type is used to define the coordinate system which is used within the file
2. The or line type is used to define the optional origin of the vertices

Example:

crs urn:ogc:def:crs:EPSG::4326
or 48.3028533074941 14.2842865755919 279.307006835938

Next to the geo-referencing features, the .geoobj extension also supports exchanging scale, rotation, as well as translation information using the following line prefixes:

1. sc for adding scale information (s is already defined in .obj for smoothing groups)
2. t for translation information
3. r for rotation angular information

Example:

sc 1.5 2 5
t 10 -5 4
r 90 45 10

Note that: if either a scaling, a translation or a rotation information is stated after an object definition with the prefix o, the transformation is not interpreted globally, but locally for the specific object.

Next to that it also supports the optional geographical extent meta information, containing the minimal (first three values) and maximal (remaining three values) coordinate value expressions using the line prefix e. This information can be useful for filtering geo-referenced files without any need to iterate all vertices.

e -0.5 -0.5 -0.5 0.5 0.5 0.5

GeoObj also supports meta information on file or on object level:

4. m for arbitrary object based meta information. Every meta entry contains a key as first element followed by one or more values. Reserved keys:
   • type for object type information
5. mf for arbitrary file based meta information. Every meta entry contains a key as first element followed by one or more values. Reserved keys:
   • tu for defining the translation unit (default is metres m)
   • ru for defining the rotation unit (default is degrees deg)

mf tu inch
mf ru rad
m axis_ordering x y z

And finally GeoObj contains an extension to map object hierarchy:

6. h can be used before an object definition to change the hierarchy level. Like this an object tree can be created
   • Uses the absolute index of the used hierarchy level (e.g. 2 represents a grandchildren-object root->children-> grandchildren)
   • Use 0 for root level
   • Parents are set to the last object of the specified level

crs urn:ogc:def:crs:OGC:2:84
or 14.2842798233032 48.30284881591775 279.807006835938
v -0.5009357136907019 -0.4994462475020125 0.5
v -0.5009357136907019 -0.4994462475020125 -0.5
v -0.5009356247086404 0.4994462914230726 -0.5
g cubes
h 1
o child1
f 1 2 3
o child2
f 1 2 3
h 2
o child3
f 1 2 3

The .geooff file format extends the classic .off file. For this we introduce a new file header using GeoOFF instead of OFF. The next non-empty line after this header is used to define the crs.

Example:

GeoOFF
urn:ogc:def:crs:EPSG::4326

GeoOFF supports alternative headers, using different postfix values. The pattern of the header is based on the OFF header definition and is defined like [ST][C][N][4][n]GeoOFF[o][e][s][t][r][f*][m*]. Like this GeoOFF is able to support:

• An absolute origin using the o header postfix symbol
• Extent information using the e header postfix symbol
• Global scaling information using the s header postfix symbol
• Global translation information using the t header postfix symbol
• Global rotation information using the r header postfix symbol
• Arbitrary meta information using the m header postfix symbol for object information or f for file information ( which can occur multiple times)
  • Defined as blank-separated list of key/value pairs like key value
  • Values may be again a list of values that are separated with a whitespace like key value1 value2 value3
  • Reserved keys for file meta information (f):
    • tu for defining the translation unit (default is metres m)
    • ru for defining the rotation unit (default is degrees deg)
  • Reserved keys for object meta information (m):
    • type for object type information

Example:

GeoOFFostrffm
urn:ogc:def:crs:OGC:2:84
14.2842798233032 48.30284881591775 279.807006835938
2 2 2
10 50 100
90 0 0
tu inch 
axis_ordering x y z
type genericobject 

Note: The .off prefixes are currently not supported in the implementations.

The .geoply file format extends the classic .ply file format with two header-line-types:

1. The crs line type is used to define the coordinate system which is used within the file
2. The origin line type is used to define the optional origin of the vertices

In addition to those types it also changes the header from ply to geoply.

geoply
crs urn:ogc:def:crs:EPSG::4326
o 48.3028533074941 14.2842865755919 279.307006835938
...
end_header

Next to the geo-referencing features, the .geply extension also supports exchanging global scale, rotation, as well as translation information using the following line prefixes:

1. scale for adding scale information
2. translate for translation information
3. rotate for rotation angular information
4. meta for arbitrary object based meta information. Every meta entry contains a key as first element followed by one or more values. Reserved keys:
   • type for object type information
5. metaf for arbitrary file based meta information. Every meta entry contains a key as first element followed by one or more values. Reserved keys:
   • tu for defining the translation unit (default is metres m)
   • ru for defining the rotation unit (default is degrees deg)

Example:

geoply
...
scale 1.5 2 5
translate 10 -5 4
rotate 90 45 10
metaf tu m
metaf ru deg
meta type genericobject
metaf axis_ordering x y z
...
end_header

Next to that it also supports the optional geographical extent meta information, containing the minimal (first three values) and maximal (remaining three values) coordinate value expressions using the extent header. This information can be useful for filtering geo-referenced files without any need to iterate all vertices.

geoply
...
extent -0.5 -0.5 -0.5 0.5 0.5 0.5
...
end_header

The .geostl file format extends the classic .stl file using the geosolid root element. Followed by the geosolid prefix of the file format a meta-data tuple is introduced. This tuple consists of the crs at the first position, followed by the optional origin coordinates and finally the optional stl name.

geosolid urn:ogc:def:crs:OGC:2:84 48.3028533074941 14.2842865755919 279.307006835938 fileName

The different named file formats come with a variable amount of features according to e.g. the supported CRS, an origin for specifying a local coordinate system, the meta information of the minimal and maximal coordinates (geographical extent), multi-object support or also differ in the representation of vertices. To take up the last point, some formats use e.g. central vertex lists with referencing indices in the face definition and others re-define the vertices within every indiviudal face. Next to that there are many different other features (e.g. smoothing groups in .obj , geographicalExtent in CityJSON or exact property definitions in .ply), which vary between the file formats and lead to a diverse semantic expressiveness.

† Some file formats do not explicitly support an origin representation, but this feature can be approximated using translations.

* Currently, only text support, but the base format would support binary, so a binary extension would be possible.

The following file comparison uses the minimal required sub-set of the specific file formats to represent geo-referenced 3D models. Additional features (e.g. GeographicalExtent in CityJSON) are not considered as far as possible, to avoid a negative bias of the comparison. Next to that also the used reader does not support all features of the input files ( e.g. .mtb material information) and may use different line-ending symbols (Windows vs Linux). This would lead to the situation that in some cases the input file size is greater than the geo-referenced version. For this reason we have decided to do a normalization first by reading the input files with our custom reader and exporting the normalized representation using our custom obj writer. The exported and normalized files are used as basis of comparison.

You can find most of the used obj files here. The only exceptions are the Amsterdam (find it here) and Berlin (find it here) city model files. Also note that, X3D is currently not explicitly supported by the present framework since it can be encoded using XML or VRML. Next to that it is the successor of VRML and supports many features of GeoVRML within the geospatial extension with only minor differences. For this reason it would result in a comparable size when using the VRML encoding and is left out in the following comparison.

Note: Sizes are in KiloByte (KB)

Note 2: Some results are below the baseline. GeoOFF and GeoPLY are for example smaller compared to the input OBJ file's, because of the missing line prefix. While vertices and faces are marked with v and f in OBJ, this prefix is implicitly given by the ordering and the number of elements in the two mentioned file formats (and their base formats OFF and PLY). The line prefix results in a comparable high overhead, when it comes to files with thousands of lines.

An interactive visualization of the size comparison can be found here.

To set up and use the project have a look at the detailed description here

You can install the framework via pip:

pip install geofiles

The present project supports multiple reader implementations for importing (geo-referenced) geometry files (.obj , .geoobj, .ply, .geoply, .off, .geooff, .stl, .geostl, CityJSON, GeoJSON, KML, GML, CityGML , Collada (.dae)). Using one of these readers is the entrypoint to the framework and allows to create an in-memory geometry model using the GeoObjectFile class. Note that only a subset of the features of the named files are currently supported. So reading files with non-supported features may result in a loss of information (e.g. smoothing groups in .obj, exact property definitions of .ply or classes of CityObjects in CityJSON, etc.)

reader = GeoObjReader()
path = "mygreatfile.geoobj"
with open(path) as file:
    geoObjFile: GeoObjectFile = reader.read(file)

Next to file imports, the framework also supports to read geometric objects from strings:

geoobj = """
         crs urn:ogc:def:crs:OGC:2:84
         v 14.2842865755919 48.3028533074941 279.307006835938
         v 14.2842865755919 48.3028533074941 280.307006835938
         v 14.2842865755907 48.3028443243414 280.307006835938
         o triangle
         f 1 2 3
         """
geoObjFile: GeoObjectFile = reader.read_string(file)

The present framework supports different conversion methodologies as converting from one to another coordinate reference system. Next to the CRS-conversion the framework also supports to transform between origin and non-origin based representations, as well as between geo-referenced and local representations. Finally, there is also basic support for transforming (scale, rotation, translation) a model's vertices.

# 1. Change coordinate system
converter = CrsConverter()
converted = converter.convert(geoObjFile, "urn:ogc:def:crs:OGC:2:84")

# 2. Change to origin-based representation
originconverter = OriginConverter()
origin_based = originconverter.to_origin(converted)

# 3. Apply transformation
transformer = Transformer()
origin_based.scaling = [2, 2, 2]
origin_based.translation = [5, 10, -5]
origin_based.rotation = [45, 30, 90]
transformed = transformer.transform(origin_based)

The geographical extent of a file can be determined in two ways:

1. Only searching for the min and max coordinates of the values (not considering transformation or origin information)
2. Determining the geographical extent considering all available meta information

Depending on the use case one variant is more suitable than the other. If you are going to ignore transformation information in your application, the additional overhead of the second method is not required, otherwise if you want to know the extents considering this meta information you have to use the ExtentCalculator class.

# 1. Classic geographical extent 
geoObjFile: GeoObjectFile = ...
geoObjFile.update_extent()

# 2. Using the ExtentCalculator
objFileWithExtents = ExtentCalculator.update_extent(geoObjFile, True, True)

Finally, the in-memory model representations can be re-written to your hard drive using one of the writer implementations. Note:

1. That some file formats presuppose a specific CRS (e.g. .kml requires vertices in Wgs84 representation)
2. Most file formats do not support transformation (scale, rotation, translation) meta-information. A model's vertices have to be transformed first before exported to such a file format.
3. The writers will automatically append the specific file type (unless you set append_file_type to False)

writer = GeoPlyWriter()
writer.write("mygreatfile.geoply", transformed, append_file_type=False)

Alternatively, the writers can also be used to create file format specific output like JSON (for GeoJSON, CityJSON, ...) , XML (for GML, KML, ...) or just string:

writer = GeoPlyWriter()
string_output = writer.write_to_string(transformed)

writer = GeoJsonWriter()
json_output = writer.create_json(transformed)

writer = GmlWriter()
xml_output = writer.create_xml(transformed)

• Why yet another 3D geometry file format like .geoobj?
  • During our research in the context of outdoor augmented reality applications, we were looking for a possibility for exchanging geo-referenced geometry models. In this context, the other named file formats come with a too high overhead (e.g. XML tags or not required meta information as object types like in CityJson) in our opinion and are for this reason not ideal.
• You describe multiple geo-referenced file formats. Which one should I use for geo-referenced 3D models?
  • This depends on the use case. If you have to exchange the models with as little overhead as possible we recommend using the proposed .geoply, .geoobj or .geooff format extensions. If you require semantic expressiveness, you should prefer other formats like CityJson or GML.
• How are vertices defined, if I use the origin-based approach of .geoobj, .geoply, .geooff or .geostl?
  • In the origin-based version, vertices are represented within a local Cartesian coordinate system with the defined origin as coordinate system origin (0, 0, 0).
  • The local coordinate system is intended as a left handed system.
  • The local coordinate system uses the x-axis as abscissa axis (width information), y-axis as ordinate axis (length information) and z-axis as applicate axis (height information).
  • The units used in this type of coordinate system are assumed to be in meters.
• How is the transformation information defined?
  • The proposed transformation information is separated into tuples (one value per axis) for translation, rotation and scale.
  • Per default: For the translation, meter based offsets are intended to be used, the rotation is based on degrees and the scale tuple is represented using numeric factors.
  • GeoOBJ, GeoOFF and GeoPLY support to change the used unit for translation/rotation information

First make sure to read our general contribution guidelines.

Copyright (c) 2021 the original author or authors. DO NOT ALTER OR REMOVE COPYRIGHT NOTICES.

This Source Code Form is subject to the terms of the Mozilla Public License, v. 2.0. If a copy of the MPL was not distributed with this file, You can obtain one at https://mozilla.org/MPL/2.0/.

If you are going to use this project as part of a research paper, we would ask you to reference this project by citing it.

@article{Praschl2023,
  title = {Extending 3D geometric file formats for geospatial applications},
  volume = {16},
  ISSN = {1866-928X},
  url = {http://dx.doi.org/10.1007/s12518-023-00543-6},
  DOI = {10.1007/s12518-023-00543-6},
  number = {1},
  journal = {Applied Geomatics},
  publisher = {Springer Science and Business Media LLC},
  author = {Praschl,  Christoph and Krauss,  Oliver},
  year = {2023},
  month = dec,
  pages = {161–180}
}