I’m trying the cesium on premise for 3D tiling city GML or 3D Model files.
Now. I just started using the cesium on premise 3d tilers.
but whenever i tried it, I encounter this error message. I searched in the cesium community and googled it. I couldn’t find proper answer for the trouble.
I need your help.
I don’t know what else I can do.
below I attached the error message I have been seeing.
Those file types are cityGML and Terrain as far as I know of by now.
It doesn’t seem to have any problem with 3D model type (which is ‘.obj’ that I checked).
I checked those cityGML and terrain (.img) files with FME Inspector to look into the coordinate info if there are any suspicious things. Those files have their own EPSG:5186 coordinate system.
I wondered if cesium has something with the ‘EPSG:5186’ coordinate system.
So I downloaded sample cityGML files from the internet which uses the different coordinate system, but I had the same error message ‘Invalid spatial reference system… Spatial Reference System : EPSG:4979.’
I’m so desperate.
I’m still having the same problems with cesium on premise tiler.
This time I’ve tried to tile the terrain files but there were another error with postgreSQL I guess.
beside the spatial reference problem that I used to have.
This is really hard to deal with…
Hello,
Thanks for your patience in waiting on a response, and I hope we can solve this problem for you soon. Is there sample data you can share with us that demonstrates the issue? That would be very helpful as we look into this.
I know that you are using the on-premises tilers, but if you upload your data to ion and share the asset ID with us, we can retrieve it for internal investigation that way.
Thanks,
Matt
Finally I got response from you.
I’ve been working on these problems by now but there is no any sign of progress here.
We are supposed to 3d tile all kinds of Geo Data that are convertible with general geo systems, but I want to start with ‘cityGML’, ‘Terrain’ type of geo data first.
I uploaded parts of files that I want to deal with on cesium ion ‘onppom’ account and those asset ID are 733822, 733824.
Actually about the terrain file. I need to convert way bigger than the asset I uploaded terrain files (ID:733824). I don’t think it’s easy to upload because it’s size is over 82 Gigabytes.
Today I encountered another error. I’ll attach captured image. Please let me know what should I do with it.
Thank you.
Hello,
I took a look at assets 733822 and 733824. If there are other assets that generated some of the errors you posted earlier in this thread, please let me know, and I’ll be happy to examine those as well.
I see that asset 733822 tiled successfully in ion, and I was able to tile it on my local Windows machine using the on-premises 3D Tiling Pipeline 4.5.2 and the following command:
../tilers-win-4.5.2/bin/3d-buildings-tiler -I CityGML -i ../_gml/733822 -o ../_tilesets/733822
You should be able to view the asset in your ion dashboard.
When you received the error Invalid spatial reference system, was that for the source data for asset 733822?
As a test, I would recommend following the instructions under Using the tiler at the top of 3DBuildingsTiler.pdf, which came with the on-premises 3D Tiling Pipeline. Attempting to run the tiler on the included sample data will help us determine if the problem is related to the data or your local environment.
Please be sure to download and install both Visual C++ Redistributables, as noted in the document, if you have not already done so.
It is a similar case with asset 733824: I see that the tiling job completed successfully in ion, and I was able to tile it on my Windows machine using the command below.
../tilers-win-4.5.2/bin/terrain-tiler -i ../_img/733824/*.img -o ../_tilesets/733824
For this one, it would be helpful if you could follow the instructions at the top of TerrainTiler.pdf to download the sample data and attempt to tile it, similar to the above CityGML case. Please let us know the result.
These cases lead me to believe that there is some key difference in your local environment. We will do our best to determine what it may be. As a starting point, please let us know if you are able to successfully tile the sample data.
Thank you,
Matt
Thank you for your prompt response.
Actually, there are no issues when I use cesium-ion uploading my assets. I’ve been using it with another account uploading a lot of cityGML, terrain and imagery files. There are no problems. Sometime when I saw error message on dash board I could easily figure out what went wrong and resolved them.
No. there were no issues with cesium-ion uploading my assets which always make trouble with on-premise.
About the ‘Invalid spatial reference system : EPSG:4979’, we don’t use that coordinate system.
I don’t think our assets have to do with EPSG:4979.
Those are coordinate system we usually use in South Korea.
EPSG : 4326, 4019, 4737, 5181, 5186, etc
And I proceeded the 3d building tiler, terrain tiler with the “sample data” as you mentioned.
The result was the same as when I used my own assets.
I don’t think there were some errors in our assets. I think it would be the local environment.
But, my machine wouldn’t be the only one which go along with the cesium-on-premise.
Actually I’ve tried this on another machine which runs windows server 2019 standard and the result was the same. My PC runs on windows 10 professional, anyway.
For references I will attach the result of the 3d building and terrain tiling with the sample data.
Thank you.
Microsoft Windows [Version 10.0.19042.1415]
(c) Microsoft Corporation. All rights reserved.
C:\Users\conso4>d:
D:\>cd Cesium3DTiling/bin
D:\Cesium3DTiling\bin>3d-buildings-tiler -I CityGML -i d:/Cesium3DTiling/bin/Data/SampleData/Reichstag -o d:/Cesium3DTiling/bin/Data/SampleData/Reichstag_Tiles
Reading CityGML [ ] 0% 0.0 seconds
Error: Invalid spatial reference system
Filepath: d:\Cesium3DTiling\bin\Data\SampleData\Reichstag\Reichstag.gml
Spatial Reference System: EPSG:4979
D:\Cesium3DTiling\bin>
D:\Cesium3DTiling\bin>
D:\Cesium3DTiling\bin>terrain-tiler -i d:/Cesium3DTiling/bin/Data/SampleData/ZionNationalPark.tiff -o ZionNationalPark.terraindb
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_BAG.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_BAG.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_FITS.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_FITS.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_GMT.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_GMT.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_HDF4.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_HDF4.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_HDF4Image.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_HDF4Image.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_HDF5.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_HDF5.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_HDF5Image.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_HDF5Image.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_KEA.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_KEA.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_netCDF.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\gdal_netCDF.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\ogr_MSSQLSpatial.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: Can't load requested DLL: C:\Program Files\GDAL\gdalplugins\ogr_MSSQLSpatial.dlle[0m
e[35mWarning: 126: 지정된 모듈을 찾을 수 없습니다.e[0m
e[35mWarning: ERROR 1: PROJ: proj_create_from_database: C:\Program Files\PostgreSQL\13\share\contrib\postgis-3.1\proj\proj.db lacks DATABASE.LAYOUT.VERSION.MAJOR / DATABASE.LAYOUT.VERSION.MINOR metadata. It comes from another PROJ installation.e[0m
e[35mWarning: ERROR 1: PROJ: proj_create_from_database: C:\Program Files\PostgreSQL\13\share\contrib\postgis-3.1\proj\proj.db lacks DATABASE.LAYOUT.VERSION.MAJOR / DATABASE.LAYOUT.VERSION.MINOR metadata. It comes from another PROJ installation.e[0m
e[0m(1 of 1) Adding ZionNationalPark.tiff to tileset.e[0m
e[35mWarning: ERROR 1: PROJ: proj_create_from_database: C:\Program Files\PostgreSQL\13\share\contrib\postgis-3.1\proj\proj.db lacks DATABASE.LAYOUT.VERSION.MAJOR / DATABASE.LAYOUT.VERSION.MINOR metadata. It comes from another PROJ installation.e[0m
e[0mCould not apply height reference to projectione[0m
e[35mWarning: ERROR 1: PROJ: proj_create_from_database: C:\Program Files\PostgreSQL\13\share\contrib\postgis-3.1\proj\proj.db lacks DATABASE.LAYOUT.VERSION.MAJOR / DATABASE.LAYOUT.VERSION.MINOR metadata. It comes from another PROJ installation.e[0m
Error: Invalid spatial reference system
Spatial Reference System: EPSG:4979
D:\Cesium3DTiling\bin>
Hello,
Thanks for the additional details around this. We’ve been discussing this issue on our end and have some recommendations for how we can troubleshoot it with you.
Problems that are particular to a user’s local environment are often a challenge to investigate, since we can’t always reproduce the problem on our end. Please bear with me as I suggest some steps you can take that will help us better understand what may be happening.
This appears to be a problem with the tilers incorrectly looking for GDAL DLLs in C:\Program Files\GDAL\gdalplugins on your machine, rather than using the DLLs that shipped with the 3D Tiling Pipeline. This may be because the tilers cannot locate the <tilers-directory>/bin/Data/gdal directory. This may be the problem for the buildings tiler as well, despite the error message referencing a particular coordinate system.
The first thing that would be useful is if we could verify the structure of your tilers directory. Based on the logs you provided, this should be D:/Cesium3DTiling on your machine. The most surefire way for me to check it would be if you could send it to me as it is via Google Drive or another file-sharing service. That way, I could verify that the tilers were installed correctly.
If that’s not feasible, an alternative would be if you could please let me know whether the folders and subfolders look like this on your machine:
The most relevant part here is the gdal subfolder. The tilers expect it to have the same relative path that it had in the original .zip, so if it was moved, that would explain why the tilers went searching for GDAL DLLs in another location instead.
Please let me know if you can verify this initial item. If everything seems OK with the installation, we can determine a best next step.
Thanks,
Matt
Actually I totally agree with your thought that the my local environment has to do with all the stuff.
As I read your response I think I got some clue on this.
These 3D tilers are supposed to use it’s own gdal related files under ‘gdal’ directory not the ‘gdal’ located in ‘c:/Program Files/GDAL’.
Then I think I can do check out with the ‘environmental variable’ settings on Windows OS.
Because of that when all the processes call ‘gdal’ that one in ‘c:/Program Files/GDAL’ seem to be run.
I’ll check that out right after this post.
And for your request.
I will send my own 3d tilers folder as it is as a google driver link through message to you.
Thank you.
I’ve tried 3d tilers after removing ‘c:/Program Files/GDAL’.
But the result was the same.
Microsoft Windows [Version 10.0.19042.1415]
(c) Microsoft Corporation. All rights reserved.
C:\Users\conso4>d:
D:\>cd Cesium3DTiling/bin
D:\Cesium3DTiling\bin>3d-buildings-tiler -I CityGML -i d:/Cesium3DTiling/bin/Data/SampleData/Reichstag -o d:/Cesium3DTiling/bin/Data/Reichstag_Tiles
Reading CityGML [ ] 0% 0.0 seconds
Error: Invalid spatial reference system
Filepath: d:\Cesium3DTiling\bin\Data\SampleData\Reichstag\Reichstag.gml
Spatial Reference System: EPSG:4979
D:\Cesium3DTiling\bin>
Hello,
Thank you for trying those steps and for sending your tilers folder. I examined it, and everything with it seems correct. I was able to use it in a fresh (Windows Sandbox) environment to tile the sample data.
Please let us know if you were able to uncover anything about environment variables in your system. Environment variables related to GDAL (e.g., GDAL_DRIVER_PATH) or PROJ may be relevant.
Do you have access to a fresh/virtual environment such as Windows Sandbox? I know you said you’ve already tried this on a different machine. If you have other environments that may have a different IT configuration, please let us know. Trying to use the tilers on those may help us narrow down the possibilities of what could be going wrong.
In the past, the language settings for a machine have not had any impact on whether our tilers can run successfully, but if your computer is configured to use a language other than English, it may be worth trying to change that setting (ideally, in a virtual/Sandbox environment if you have access to one).
Let us know if any of the above yields different results. Again, thanks for your patience—I know that troubleshooting an issue like this is always challenging as it is environment-dependent.
Thanks,
Matt
Hi.
I thought all the problems have been solved when I succeeded to process 3d tiler after working on the windows ‘environmental variables’ related to GDAL, PostgreSQLs. Actually it worked. The sample data, some of my data could be tiled.
But now I encounter another obstacle with coordinate system.
I think I had no idea how many geo codes we use in our country.
It is EPSG 5179.
Those cityGML files with EPSG 5179 are not able to be tiled not only on premise but also on ion.
I guess it would be grateful if you check the asset (ID : 763489)
And I’m also attaching the code I tried with ‘on premise’.
C:\Users\conso4>d:\\Cesium3DTiling\bin\3d-buildings-tiler -I CityGML -i d:\\Cesium3DTiling\bin\Data\SampleData\Reichstag -o d:\\Cesium3DTiling\bin\Data\Reichstag_Tiles
Reading CityGML [====================] 100% 0.0 seconds
Adaptive Quadtree Tile (est. 0 levels) [====================] 1/1(100%) 0.0 seconds
Output Tiles [====================] 2/2(100%) 0.5 seconds
Tileset written to d:\Cesium3DTiling\bin\Data\Reichstag_Tiles
C:\Users\conso4>d:\\Cesium3DTiling\bin\3d-buildings-tiler -I CityGML -i d:\\Temp_FME_Test_Result\KOR_Shp_to_Shp\336\2671033024 -o d:\\Temp\__CesiumData\TestResult
Reading CityGML [ ] 0% 0.0 seconds
Error: Invalid spatial reference system
Filepath: d:\Temp_FME_Test_Result\KOR_Shp_to_Shp\336\2671033024\2671033024.gml
Spatial Reference System: EPSG 5179
Hello.
There was a mistake on converted CityGML files.
It was supposed to be “EPSG:5179” not “EPSG 5179”.
I used 2D shp. files to convert it to CityGML. I set several parameters for the CityGML writer.
When I did that work, I wrote down ‘EPSG 5179’ for the SRS Parameter instead of ‘EPSG:5179’.
It’s embarrassing but it would be helpful for someone like me later.
I won’t remove this post.
Please, don’t bother with this post. All things get cleared. It works well.
And don’t be silly like me!
No problem at all—very glad to hear it now works. Thank you for returning to post your solution. That’s always helpful for future readers, and the community appreciates it.