Closed cmutel closed 2 years ago
edges_to_dataframe
uses the extraction function from wurst, which has good performance. However, for other reasons, wurst
loads GIS libraries, which is a bit heavy for everyday installs, so this is optional.
After some reflection, I think we should move the extraction functions from wurst
to bw2data
, and leave a shim in wurst
. This would make things a bit simpler, while avoiding duplication of code.
Moved wurst
functions to bw2data
in 55f107177ead8a73cdf88a5b5be56bf6811bf27f.
Closes #106. Doesn't work for IO tables.
Chose not to use caching; if you need this, it is easy to add, and the memory hit for normal users is big enough that the benefits don't outweigh the tradeoffs IMHO.
Pinging @romainsacchi @michaelweinold @BenPortner if you want to give input.