GitHub user dosubot[bot] added a comment to the discussion: Deck.gl map change style directly on dashboard
<!-- Answer --> If your TileLayer is not rendering, here are the most common causes and how to debug them: 1. **Layer Visibility**: In your code, the `IntensityLayer` has `visible: false`. Only layers with `visible: true` will render. Make sure the layer you want to see has `visible: true`. 2. **Data URL Issues**: The `data` property for your TileLayer points to URLs like `http://storage.cockpit.hell.ee.loc/intensity/{z}/{x}/{y}.png`. If these URLs are not accessible from your browser (due to network issues, CORS, or the server not running), the tiles will not load. Open your browser's developer tools (F12), go to the Network tab, and check if tile requests return 200 OK or errors. 3. **JavaScript Errors**: Open the browser console (F12, Console tab) and look for any errors or warnings related to deck.gl, TileLayer, or failed resource loads. These messages often point directly to the problem. 4. **Superset Logs**: For backend errors, enable detailed logging in Superset by editing your `superset/config.py`: ```python import logging, os LOG_LEVEL = logging.DEBUG ENABLE_TIME_ROTATE = True TIME_ROTATE_LOG_LEVEL = logging.DEBUG FILENAME = os.path.join(DATA_DIR, "superset.log") ROLLOVER = "midnight" INTERVAL = 1 BACKUP_COUNT = 30 ``` This will create a `superset.log` file with detailed error messages you can review for issues during local development. [Reference](https://github.com/apache/superset/discussions/32998) 5. **Layer Array**: Ensure you are actually passing your `updatedLayers` (or the correct array of layers) to the `layers` prop of the DeckGL component. If you want to render both your dynamic layers and the TileLayer, combine them: `layers={[...updatedLayers, ...currentLayer]}`. If you follow these steps—checking visibility, network access, browser console, and Superset logs—you should be able to pinpoint why the TileLayer is not rendering. If you see specific errors in the browser console or Superset logs, those will give you the next clue to fix the issue. <!-- Dosu Comment Footer --> *To reply, just mention my name [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/90ab3007-4631-43f8-8bbc-6738a3a4d7b5?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/90ab3007-4631-43f8-8bbc-6738a3a4d7b5?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/90ab3007-4631-43f8-8bbc-6738a3a4d7b5?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/90ab3007-4631-43f8-8bbc-6738a3a4d7b5?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/90ab3007-4631-43f8-8bbc-6738a3a4d7b5?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/90ab3007-4631-43f8-8bbc-6738a3a4d7b5?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/90ab3007-4631-43f8-8bbc-6738a3a4d7b5?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/32149) GitHub link: https://github.com/apache/superset/discussions/32149#discussioncomment-13297435 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
