Hi Thiemo,
Thanks for the background information. I agree with these default choices -- seems useful. Just two comments:
There may be an option to enter the precision as a number, if requested, but I don't think this is necessary at this point.
I think the point is simply that it is not nice to have a wiki system where some (useful) edits can not be made by normal people but only by developers.
...
We currently have null values in the database. I tend to think of them as "not yet entered". I'm not sure if we should "reject" this at any point, I prefer to apply the auto-detection instead (so the answer is, again, neither nor).
The problem is that auto-detection cannot be applied to the JSON data, because the values there are double numbers. Auto-detection would require the user input (decimal number string) to work. Therefore, we now default to 1.0/3600 when seeing "null" precisions in the data.
Cheers,
Markus