geonetwork / geonetwork/core-geonetwork
Layers added to map not visible in 3D map mode
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 521
- Forks
- 515
- Avg merge
- 6d 13h
- Merged PRs (30d)
- 19
Description
Layers added to the map from a WMS service are not visible on the map when switching the map to 3D mode. The service requests are converted to proxy requests by adding http://localhost:8080/geonetwork/proxy?url= in front of it and get a 500 error status result. In 2D mode the services work without problem but switching the map to 3D mode makes them invisible as the layers can not be loaded through the proxy url.
Steps to reproduce the behavior:
- In User interface settings turn on the option 'Allow 3D mode'
- Go to the map and add a layer through Add Layer > Services, for example: https://geodata.zuid-holland.nl/geoserver/landelijk_gebied/wms
- The layer is visible in 2D mode. Then switch to 3D mode by clicking on the button 'Switch from 2D to 3D'
- Now the layer is not visible anymore. The F12-menu shows the proxy requests with 500 errors.
Test environments:
- GeoNetwork 3.12.11 server installation opened with Chrome on Windows
- GeoNetwork 3.12.10 Docker installation opened with Safari on Mac OSX
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by enabling 3D mode, adding the example WMS service, and switching from 2D to 3D. Start by inspecting the proxy requests shown in the browser's F12 menu; done means the WMS layer remains visible in 3D mode without 500 errors.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100