tudelft3d / 3dfier

The open-source tool for creating 3D models
http://tudelft3d.github.io/3dfier
GNU General Public License v3.0
526 stars 106 forks source link

Cannot read polygons from postgis in v1.3.0 #129

Open m-gerhold opened 3 years ago

m-gerhold commented 3 years ago

Hello,

I'm new to 3Dfier and really liking it a lot so far. However, I'm having trouble reading input polygons from a postgresql/postgis database with version 1.3.0 of 3Dfier. The software unexpectedly quits right in the beginning when trying to connect to the database, but there is no error message in the log:

E:\3Dfier-1.3.0>3dfier.exe config.yml --PostGIS "PG:dbname='dbname' host='localhost' port='5432' user='user' password='password'"
3dfier Copyright (C) 2015-2020 3D geoinformation research group, TU Delft
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; for details run 3dfier with the '--license' option.

Config file is valid.
==> "E:/3Dfier-1.3.0"

However, I tried using version 1.2.2 of 3Dfier instead and with this version it reads the polygons from the database just fine:

E:\3Dfier-1.2.2>3dfier.exe config.yml --PostGIS "PG:dbname='dbname' host='localhost' port='5432' user='user' password='password'"
3dfier Copyright (C) 2015-2019  3D geoinformation research group, TU Delft
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; for details run 3dfier with the '--license' option.

Config file is valid.
Opening PostgreSQL database connection.
        Layer: gebaeude
        (14,354 features --> Building)
        Split 14,354 MultiPolygon(s) into 14,362 Polygon(s)

Here is the part in the config file:

input_polygons:
  - datasets: 
      - "PG:dbname=daten_2d host=localhost port=5432 user=user password=password tables=gebaeude"
    uniqueid: id
    lifting: Building
    height_field: height_field

I'm assuming that there is a bug in version 1.3.0 that makes reading the input polygons not work correctly for the database. Output to a postgis database works perfectly in both versions, though. I would appreciate if you could take a look at this.