altitude operations

[mgross]

Now it is possible to create altitude/elevation maps (data comes from package elevatr):

.

Also custom maps are now possible (user must provide longitude (x), latitude (y) and value (x) data; note that each possible x-y combination must exist, i.e. full data matrix):

Weighting inside LocatoR with said altitude map (or any other map) is possible. We have the option to set negative weighting values to 0 and to apply inverse exponential decay weighting. In the latter case, we can apply a halftime. This can make sense when we weight with altitude for example: For a half-time of 1000m, locations with 1000 altitude get half the probability, with 2000m 1/4 of the probability and so forth.

Using Lives 13C data with 13C -18/1 as point gives this without weighting: However with weighting, higher altitudes are downweighted: With negative values set to zero weight oceans and areas below sealevel get 0 weight:

[mgross]

@arunge : Could you check this?

[arunge]

@mgross Unfortunately, this feature requires a higher version of elevatr than we have currently running, that is why the checks fail:

Possibly, you need exactly version 0.99.0 of elevatr, correct?

I need to discuss with @jan-abel-inwt what way is best for our system to get the higher version into our docker container. I will update you when we found a solution!

[mgross]

@arunge, I can try with 0.4.2

[mgross]

@arunge ok, it also works for older version

[mgross]

@arunge: should be working now

[arunge]

@mgross I merged some fixes from the beta into this feature branch. It is just open to remove the comments mentioned above. I could also do this and merge afterwards. Just let me know if you need something. :blush: