the Community class is a remnant of the earliest versions of geosnap, when we were super concerned about storage efficiency and tried to maintain a single set of geometries for several temporal sets of attributes. We moved away from that design decision for several reasons, but kept the class-based interface. Now that a Community is little more than a long-form geodataframe, the class seems like it's now providing more burden than utility (as a user its easier to work with gdfs anyway, and internally that's what we work with anyway).
so i'd like to reorient (or at least provide an alternative) function-based API that operates on long-form geodataframes instead of Community-based methods.
the
Community
class is a remnant of the earliest versions of geosnap, when we were super concerned about storage efficiency and tried to maintain a single set of geometries for several temporal sets of attributes. We moved away from that design decision for several reasons, but kept the class-based interface. Now that aCommunity
is little more than a long-form geodataframe, the class seems like it's now providing more burden than utility (as a user its easier to work with gdfs anyway, and internally that's what we work with anyway).so i'd like to reorient (or at least provide an alternative) function-based API that operates on long-form geodataframes instead of
Community
-based methods.