Export issue in I3dm.export

[ashitoshp]

I have imported your Sample to PostGIS and tried the command as below
i3dm.export -c "Host=172.16.0.213;Username=postgres;Password=postgres;Database=3Dmodels;Port=5432" -t i3dm.mydata

Getting System.ArgumentOutOfRangeException error

Stacktrace as below

Tool: I3dm.export
Version: 2.4.1.0
Exporting i3dm's from i3dm.mydata...
Bounding box for table (WGS84): 4.6981, 52.4227, 4.722, 52.4823
Heights for bounding volume: [0 m, 50 m]
Maximum instances per tile: 1000
Creating tile: ./output/content/0_0_0.cmpt Writing 1 subtree files...
Unhandled exception. System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter 'index')
at System.Linq.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument)
at System.Linq.Enumerable.ElementAt[TSource](IEnumerable1 source, Int32 index) at i3dm.export.Program.<>c.<Main>b__0_1(Options o) in D:\dev\github.com\geodan\i3dm.export\src\Program.cs:line 82 at CommandLine.ParserResultExtensions.WithParsed[T](ParserResult1 result, Action`1 action)
at i3dm.export.Program.Main(String[] args) in D:\dev\github.com\geodan\i3dm.export\src\Program.cs:line 25

[bertt]

It seems something goes wrong when writing the tiles. Did you follow the getting started?
https://github.com/Geodan/i3dm.export/blob/main/docs/getting_started.md

One thing I noticed the coordinates are different:

Yours:
Bounding box for table (WGS84): 4.6981, 52.4227, 4.722, 52.4823

Sample:
Bounding box for table (WGS84): 4.7591, 52.2785, 4.9999, 52.4301

[sweco-sekrsv]

I get the same error. I used this sample to setup the databse:
https://github.com/Geodan/i3dm.export/blob/main/testdata/create_testdata.sql

And then I use this box renamed to tree.glb:
https://github.com/Geodan/i3dm.export/blob/main/docs/Box.glb

This is the output:
C:\work\3d_tiles\olp_output\i3dm>i3dm.export -c "Host=localhost;Username=postgres;Password=xxxx;Database=test_gis;Port=5432" -t i3dm.mydata -f cesium
Tool: I3dm.export
Version: 2.4.1.0
Exporting i3dm's from i3dm.mydata...
Bounding box for table (WGS84): 4,6981, 52,4227, 4,722, 52,4823
Heights for bounding volume: [0 m, 50 m]
Maximum instances per tile: 1000
Creating tile: ./output/content/0_0_0.cmpt Writing 1 subtree files...
Unhandled exception. System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter 'index')
at System.Linq.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument)
at System.Linq.Enumerable.ElementAt[TSource](IEnumerable1 source, Int32 index) at i3dm.export.Program.<>c.<Main>b__0_1(Options o) in D:\dev\github.com\geodan\i3dm.export\src\Program.cs:line 82 at CommandLine.ParserResultExtensions.WithParsed[T](ParserResult1 result, Action`1 action)
at i3dm.export.Program.Main(String[] args) in D:\dev\github.com\geodan\i3dm.export\src\Program.cs:line 25

[bertt]

if you follow the getting started document there is an input table of 60K features (it should work), when using the sample database setup script (https://github.com/Geodan/i3dm.export/blob/main/testdata/create_testdata.sql) there is something going wrong

[ashitoshp]

It seems something goes wrong when writing the tiles. Did you follow the getting started? https://github.com/Geodan/i3dm.export/blob/main/docs/getting_started.md

One thing I noticed the coordinates are different:

Yours: Bounding box for table (WGS84): 4.6981, 52.4227, 4.722, 52.4823

Sample: Bounding box for table (WGS84): 4.7591, 52.2785, 4.9999, 52.4301

Thanks for your response.
I was able to run your example (mentioned in get started page). However, if I try this on my data, it fails with exact same same issue. The only difference I see in the table is that I have Z values and are negative. Projection is 4326.
Any ideas?

[bertt]

the issue occurs when very few cmpt tiles are generated (like 1 or 5). When working with a small dataset you can decrease max_features_per_tile (default 1000) so more tiles are generated.
This issue will be fixed in next release.

[sweco-sekrsv]

The getting started works for me as well. However I needed to add this to be able to get it to work:
-t_srs EPSG:28992
like this:
$ ogr2ogr -t_srs EPSG:28992 -f "PostgreSQL" PG:"host=localhost user=postgres password=postgres dbname=postgres" current_traffic_signs.geojson -nlt POINT -nln traffic_signs

Sounds great that this will be fixed in an upcoming release!

[ashitoshp]

the issue occurs when very few cmpt tiles are generated (like 1 or 5). When working with a small dataset you can decrease max_features_per_tile (default 1000) so more tiles are generated. This issue will be fixed in next release.

Thanks. Got the code to work. The output however is not creating proper json.
While loading in cesium get this error
"<!DOCTYPE "... is not valid JSON
Cesium.js:8114 A 3D tile failed to load: http://localhost/cesiumtest/data/content/4_7_8.cmpt
Cesium.js:8114 Error: Failed to load i3dm
Failed to load glTF
Failed to load glTF: http://localhost/cesiumtest/data/content/4_7_8.cmpt?compositeIndex=0
Unexpected token '<', "
"
Attached one of cmpt files for your reference.

file
4_7_8.zip

[bertt]

@ashitoshp somehow a ?github? webpage ended up in the 4_7_8.cmpt file... Maybe try again

[bertt]

@sweco-sekrsv that should not be necessary when following the getting started... what error do you get?

[sweco-sekrsv]

@sweco-sekrsv that should not be necessary when following the getting started... what error do you get?

I got this error:
ERROR: ST_Transform: Input geometry has unknown (0) SRID

[bertt]

@sweco-sekrsv that should not be necessary when following the getting started... what error do you get?

I got this error: ERROR: ST_Transform: Input geometry has unknown (0) SRID

You mean in this sql query? https://github.com/Geodan/i3dm.export/blob/main/docs/getting_started.md#create-instances-table. Cannot reproduce that.

[ashitoshp]

@ashitoshp somehow a ?github? webpage ended up in the 4_7_8.cmpt file... Maybe try again

Yes tats my bad! Im able to convert to i3dm now. Just wanted to confirm that the Z value is also taken into consideration while conversion to i3dm.
Will check the results and et back if any issues anyways. Thanks for your support.

[bertt]

Just wanted to confirm that the Z value is also taken into consideration while conversion to i3dm.

yes should be

[bertt]

issue is fixed in 2.4.3