“Software troubleshooting is the process of scanning, identifying, diagnosing and resolving problems, errors and bugs in software”
It is a systematic process that aims to filter out and resolve problems, and restore the software to normal operation.
In this module we will explore how to investigate issues encountered during the analysis workflow.
Goal: To learn how to troubleshoot in GeoSAFE
Check your results
After uploading a layer with InaSAFE keywords the
Name | Expectation |
---|---|
❗ | |
GeoSAFE ❗ |
http://geonode.kartoza.com/ |
Layer type ❗ |
Exposure / Hazard |
❗ | |
❗ | |
❗ | |
❗ | |
❗ | |
❗ |
GeoSAFE is an open source project. GeoSAFE consist of GeoNode (Django,PostGIS),QGIS Server and InaSAFE. Most of the components that make up GeoSAFE are constantly being updated to bring in new changes which help optimise the software and make it run efficiently. GeoSAFE always uses the latest stable version of software from the various component parts. GeoSAFE has been tested extensively with sample data which in some cases is not real data and there exist a possibility of other data sets breaking the code and thus rendering some other functions unusable.
The problems users encountered with using GeoSAFE can be categorised as .
1) User error. This is the inability of a user to follow the correct procedures from preparing the data to running and analysis.
2) Data Issues. This results from data that has different encoding or a user failing to generate metadata properly before uploading it.
3) Software problems – This occurs when the software does not do what it is expected to do or produce erroneous results on doing calculations.
A user is encouraged to identify a problem and categorize it. This will ensure that the problem is reported in the right channels or the user corrects himself.
What is the most likely reason an analysis fails:❗
Which of the following statement is not true:❗
Metadata without InaSAFE keywords renders the layers inaccessible to GeoSAFE:❗