Sergio Rey

As far I can see, this would be a change in the specification, not the code, as I don't see where in the code we use "resource" as a keyword...

> Just to make the plug here too, I've added [a comment](https://github.com/pysal/mgwr/issues/77#issuecomment-586648102) over at [`mgwr#77`](https://github.com/pysal/mgwr/issues/77) that affects this discussion too. To @darribas point, if the patsy approach would be used...

Thanks for reporting this. Can you provide a bit more info regarding your os and version of geopandas?

> I am not convinced by either of these changes (but surely won't block them if you want to go ahead). > > area_buffer: > - why it is called...

@darribas how about a new argument called `auto_resolution` that can take the following values: `mean`: sets resolution to give h3 hexagons approximating the mean source area `median`: sets resolution h3...

Great idea. This is similar in spirit to Dasymetric interpolation. A PR to flesh out the specifics of what you have in mind would be welcomed.

Coming up with new use cases is helpful :-> One thought on what you are suggesting is that if population is a column in the source dataframe, then I'm not...

I see what you are getting at. But, the estimated density for the target geometry (in this approach you suggest) would imply a total population of 200 million = 1000...

In terms of the explorer graphic renan shared, i think that should stay in mapclassify as the intention originally, was to provide a simple interface to explore the classifiers visually...

Thanks for raising this. I think it is more appropriate to continue this thread over in splot, so I'm relocating the issue there.