ghini / distancematrixtocoords

QGIS plugin: Calculate point positions in 2D given a network of mutual horizontal distances and some form of geographic reference information

ghini.server

Ghini is a suite of software programs, helping the management and presentation of botanical data. It aims at botanical gardens, plant collectors, nurseries, and their visitors.

This is the central ghini.server, serving data to all other Ghini family members. ghini.server handles data from one garden, or for several.

• in combination with the included ghini.web client, it lets logged in garden conservators plan their work, produce logs, and review their garden history.
• in combination with the ghini.web web client, it provides non logged in visitors a read-only access to portions of the database.
• in combination with ghini.pocket, it lets gardeners streamline their daily activities, and make it visible to the garden conservator.
• in combination with ghini.tour, it lets visitors find their way in the garden.
• ghini.server can cooperate with other instances of itself, contributing selected data to a ghini.server instance running as a garden aggregator. A ghini.web client accessing a garden aggregator server will now show data from several gardens at the same time.

distancematrixtocoords's Issues

when no python-coverage is available, just skip the step

when no python-coverage is available, make test now errors, which is not nice.

write point id to point

when we add point features, we should store the point ID into them, which is the way the reference points are referred to also in the software.

user interface to choose layer

we expect points to be in a layer and we should let the user choose which layer to work on.
in the first working prototype, the layer name is hard coded.

write better unit tests for most_connected_3clique

the function most_connected_3clique has only unit tests based on data which is far too complex to make for a real unit test. please rewrite them. also, I have the impression, given the problems we had with the example grid for issue #5, that the definition of most connected has to be reviewed. I think we don't want to just "reach" the largest amount of points, but we want to consider a point "reached" only if it is reached from all three points in the clique.

parametrize on id field

the two actions related to the plugin assume a key field, while we could also let the user define which field has to be considered the key. not a big deal, but I did not do it yet.

publish the docs on RTFD.io

publishing the docs on readthedocs.io will enable translation, and better visibility of the tool.

add http in metadata.txt homepage

in https://github.com/Ghini/DistanceMatrixToCoords/blob/master/metadata.txt

the homepage tag is not a URI, you have to add http:// otherwise the home page in http://plugins.qgis.org/plugins/DistanceMatrixToCoords/ ponts to: http://plugins.qgis.org/plugins/DistanceMatrixToCoords/ghini.github.io

user interface to choose data file

in the initial working prototype, data is hard coded in the plugin itself.
we need to let the user load the distances from some file in some reasonable format.

complete GPS information with mutual distances

I have the following problem at hand:

• ~1200 plants locations taken by GPS,
• these 1200 plants occupy just ~460 different positions,
• we wish to correctly place their plants on the map,
• I can ask the people who took these locations to construct a network of distances.

without mutual distances, the best we can do is to place plants at the GPS positions, but this will mean that some trees occupy the same spot, and that some spots are occupied by as many as 25 trees.

I can do the following:

• construct a "frame", using the mutual distances information, but lacking correct georeferentiation,
• define as target function the sum of the distances between each plant as in the frame and their corresponding point as from the measured GPS positions.
• find the rigid transformation that will minimise the target function.
• use the now georeferenced "frame" to correct the plant positions.

at a later stage we could also take into account, in the definition of the target function, the error that the GPS machine associated to the reference.