Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot access Terrain Server for Cesium. Port issue? #16

Open
jose-sanchez-morales opened this issue Feb 1, 2019 · 1 comment
Open

Comments

@jose-sanchez-morales
Copy link

I have a Node.js server running Cesium Apps in port 8080: http://localhost:8080/Apps/own_terrain.html

Path for the html file is:

C:/Users/username/Downloads/software/Cesium-1.53/Apps/own_terrain.html
The terrain files have been generated by using: cesium-terrain-builder-docker

I just took as input a sample DEM in format tif (EPSG:4326) covering a small area in Europe.

Then, I want to run my terrain tiles using cesium-terrain-server in docker.

This is how I built it:

docker run -p 9000:8080 -v C:/Users/username/Downloads/software/Cesium-1.53/Apps/terrain:/data/tilesets/terrain
geodata/cesium-terrain-server
So, Cesium running in 8080 and terrain server in 9000,

I also added CORS functionality to my node server at 8080, but nothing has improved.

When I try to access the terrain tiles, i.e:

http://localhost:9000/tilesets/tiles/0/0/0.terrain
Nothing happens, Chrome says:

localhost didn’t send any data. ERR_EMPTY_RESPONSE
And the same when integrating that into the own_terrain.html:

Cesium.js:445 GET http://localhost:9000/tilesets/tiles/layer.json net::ERR_EMPTY_RESPONSE

What am I doing wrong?

@hadirsa
Copy link

hadirsa commented Apr 11, 2019

same

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants