Google Code Exporter
Google Code Exporter
``` The API to access the various indices object properties is in need of a cleanup. Much of the API is not fully logical. The simplest solution is to rebuild...
``` The spatial conditions are getting complex when there is caching involved. It would be much simpler to generalise the approach used for Biodiverse::Indices, where pre_calc methods are specified for...
``` A useful addition to the GUI would be to allow shapefiles to determine the shape of the spatial plots. This will be particularly useful for text groups. Issues that...
``` It would be convenient for users to get a list of available arguments and examples for spatial conditions. Currently it just lists valid and invalid args, giving no hints...
``` It's often much easier to fix a user's problems if the program's output log is available. It even includes details about exceptions. Currently I think it's only written to...
``` Most of the Biodiverse modules do not have POD documentation. Those that do are often out of date. This needs to be fixed. ``` Original issue reported on code.google.com...
``` The calculations, e.g. calc_endemism, calc_sorenson, calc_richness, are currently listed under only one category in the calculation lists. In many cases they could easily fall under several categories. For example,...
``` The pntd indices currently consider all labels across both neighbour sets. It would be handy to generalise this to develop a dissimilarity index, where the labels in neighbour set...
``` The system currently checks the validity of the spatial conditions. This makes it easier to debug conditions. However, the checks are imperfect (and actually quite basic). At times it...
``` Matrices with a basedata_ref, such as are generated in Cluster and RegionGrower analyses, should support export to spatial formats. This can involve a to_basestruct method, followed by export of...