Round results about finch HOT 2 CLOSED

I'll need to be convinced there is value doing this server-side vs by the end-user. There is a click-button for this in Excel.

Question: Are we able to determine the actual precision automatically? If not, then this is left as a user parameter. I'm concerned we'll get multiple requests for the same computations, with only the precision changing once people realize they've asked for too much or not enough precision.

from finch.

I think it depends on who you call "end-user". If the end-user is climatedata.ca, then the problem is their current way of using finch does not allow modification of the data. If the end-user is the person visiting climatedata.ca, then yes this is a simple one-click problem, but the issue is that this person could be unaware of this notion of precision vs exactitude.

No we will not be able to determine the actual precision automatically. There's already a divide between "significant digits" (which is actually what climatedata.ca wants) and "decimal precision" (which is what I propose to implement).
The way this is going to be used is that climatedata.ca will hardcode the requested format for each indicator, finch will not be responsible for finding a best one. This also answers your issue about multiple requests: the real users won't have access to this option.

After discussion with Travis, I think I'll go forward with a csv_float_format input argument.

from finch.