Rafael Schouten

Yeah, I don't like the possibility of accidentally overwriting files, I think you should always have to type something strongly worded like `force=true` to show you mean it

So, here is a a todo list, assuming the above is generally accepted (edit if not!): - [ ] Shapefile.jl: - [ ] `crs` keyword, - [ ] `geometrycolumn` keyword...

> Adding force=false would be a breaking change right now For sure. Making a very solid agreement here and doing it all at once, or even with a warning first...

I would prefer they were single PRs each package to keep the review overhead a bit lower

Oh yeah randoms can totally do any one of those :)

Yeah, its not really worth being a parameter unless you or some optimiser will want to change it. It's not really a package to define and manage all you models...

Maybe I don't really get what you're trying to do

Oh, if that metadata relates to specific model parameters you can add arbitrary fields to them... Like `Param(x; mymetadata= ["icesat", "icesat2"])` and `:mymetadata` will be a column in the `Model`...

Yes probably we just need that. Maybe `AnyParam`? It should be pretty easy to implement. Maybe it would have been better to never try making Param a Number and just...

I don't totally get it, doesn't this work for you? ```julia @kwdef struct MyStruct a = Param(defaultval; prior=Normal(0, 1), bounds=(1, 2)) b = Param(defaultval; prior=LogNormal(1, 2), bounds=(2, 3)) end ```...