You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am experiencing an issue while working with raster time series in GeoNode. The process involved the following steps:
I optimized the raster layer using GDAL, including the creation of the necessary .properties file ,the optimized raster layer was successfully uploaded and published in GeoServer, following the instructions provided in the documentation attached.
Issue Encountered:
After uploading the optimized mosaic to GeoServer, I am unable to publish it on GeoNode. The layer fails to sync properly and does not appear or update in GeoNode.
As a result, the raster layer cannot be accessed or visualized in GeoNode.
I am experiencing an issue while working with raster time series in GeoNode. The process involved the following steps:
I optimized the raster layer using GDAL, including the creation of the necessary .properties file ,the optimized raster layer was successfully uploaded and published in GeoServer, following the instructions provided in the documentation attached.
Issue Encountered:
After uploading the optimized mosaic to GeoServer, I am unable to publish it on GeoNode. The layer fails to sync properly and does not appear or update in GeoNode.
As a result, the raster layer cannot be accessed or visualized in GeoNode.
Environment:
GeoNode Version: [4.4.1]
Additional Information:
I followed the instructions in the GeoNode documentation and GeoServer tutorial but the layer doesn't show up in GeoNode after uploading to GeoServer.
(https://training.geonode.geosolutionsgroup.com/master/GN2/ADV_LAYERS_PUB/OPTIMIZE_RASTER.html) (https://docs.geoserver.org/main/en/user/tutorials/imagemosaic_timeseries/imagemosaic_timeseries.html),
Please suggest any alternative methods for generating raster time series in GeoNode or how I can resolve the issue I'm encountering.
The text was updated successfully, but these errors were encountered: