DTVF: Troubleshooting

This page offers some solutions for common issues, and answers to common questions, that may arise when using the DTVF. These are listed here (on the GitHub wiki), rather than within committed README files as they may be useful for all uses of the framework, regardless of mapping provider, or pertain to multiple versions of the code.

Potential issues/questions relating to all uses of the framework, regardless of map provider, are listed first; solutions that only pertain to individual map providers are listed in further sections.

Generic

This section is relevant to all uses of the DTVF, regardless of the selected mapping provider.

Issue/Question	Solution/Answer
Visualisation not updating after changes	Try clearing (or disabling) your browser cache before reloading the page.
Visualisation not updating after changes	If running the visualisation within a Docker container, you may need to rebuild the Docker image and run a new container to see recent file changes.
No data is shown	If no data is shown and no layer tree is built then this suggests that one (or more) of the user defined JSON files is invalid. Please use an external validator tool (or website) to ensure that the JSON is valid.
Hovering over a feature does nothing	The framework supports mouse hovering effects if the input data contains certain metadata fields. To show a small description box the geospatial data needs to contain a name and description field.

Mapbox

Cesium JS

This section is relevant to issues/questions that only arise when developing Cesium JS visualisation with the framework.

Issue/Question	Solution/Answer
Do my data files have to be hosted online?	Cesium requires a valid URL to load data files, this does mean that they have to be accessible online. However, data files can be included within the visualisation container (which uses Apache to host a web server) so that they can be accessed via a http://localhost/... URL.
Getting an 401 (Unauthorized) error	If the URL causing the error is an attempt to use a Cesium API key, then this is expected. The desire here is that we want to ensure that we're not using a Cesium Ion key.
3D data is not showing	Depending on the format, some data may specify object locations relative to a position defined outside the data itself. If not set, this can cause the 3D data not to appear. Within the source node of the visualisation configuration, please ensure the position (an array of longitude, latitude, and height) is set.
3D data is in wrong rotation	At the time of writing, specifying a rotation at visualisation time is not supported. Users will need to ensure that their data contains the correct rotation within the files themselves.