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
the documentation at inasafe.org is out of date (roadmap, governance) and contains inaccurate information (change log 2.1.0)
there are multiple copies of the same information managed, stored and delivered in different places: eg change log, road map (inasafe.org, changelog.linfiniti.com, github wiki
updated information has been provided but has disappeared into the ether (governance)
proposed solution
consolidate all information - one version only
determine the best location for info to be managed (depending on need to translate)
establish and maintain links so that the user experience is seamless
priority
this is really important and should be given a high priority
there is no single point I can direct people to when they make an enquiry that has all the information & in fact the info is so out of date that I have opted to not direct enquiries to the insafe.org web site :(
Some of the other issues above remain. The easiest to fix would be a review of the changelog for 2.1.0 which has some somewhat alarming inaccuracies as per the text below. It would be fantastic if the new functionality list could be corrected before you refresh.
New Functionality in InaSAFE:
Routing
Evacuation routes
Transportation from A to B
Multiple Hazard Analysis
Damage and Loss Assessment (DALA)
Percentage of affected area by aggregation
Polygon flood impact on roads impact function added
Impact merge tool: This tool will allow you to merge the output from two impact assessments covering the same geographic extent and aggregated by the same areas.
OSM Roads downloader: In InaSAFE 1.2 we introduced the new OSM downloader tool for buildings data. Beside a lot of improvements now roads can be downloaded too and at the same time the correct keywords will be assigned to the data.
problem
proposed solution
priority
cc
@timlinux, @mach0 @MariaSolovyeva @iyan31
The text was updated successfully, but these errors were encountered: