Levi John Wolf
Levi John Wolf
@knaaptime any updates on this? I'd say yes, either import it from segregation & expose it here, or contribute the source here as `weights.Proportional_Contiguity` or something & import that into...
Hi @knaaptime, this is implemented in Segregation, correct? That implementation needs to be kicked up here, not remain in segregation.
Hey, yes the "extra" polygons are holes:  This results in some confusing behavior if you assemble a multipolygon using all the alpha shapes as regular polygons... some of the...
> to remove holes that involves... Great! Yes, the test-case I've just cooked up for this is: ```python numpy.random.seed(100) inner_r = numpy.random.uniform(low=1, high=2, size=1000) outer_r = numpy.random.uniform(low=4, high=5, size=1000) inner_theta...
For the instance you discuss, @prusswan, we might want to consider a pygeos-based implementation that only records the `touches` matrix.
Would really like that!!
I guess this is significant because the sparse weights actually supports constructing bishop weights. A refactor/contribution of this would: 1. make the sparse constructor `lat2SW` *the* constructor, while supporting all...
Sure! So, my recommendation is to 1. use the `lat2SW()` code as the only code to make lattice weights. 2. make sure that both `lat2W` and `lat2SW` take the same...
Good eye! Order in that list shouldn't be important. We should be using a set for this, but due to historical reasons, we use lists. Check for equality using the...