Currently, the Features constructor creates a feature set based on a GOL.
As an alternative, the constructor could accept an iterable that contains arbitrary Feature objects, which can then be further filtered, displayed on a map, or exported in other formats.
Open issues:
What happens if user passes non-Feature objects? Are they simply ignored? Is an exception raised?
Currently, the
Featuresconstructor creates a feature set based on a GOL. As an alternative, the constructor could accept an iterable that contains arbitraryFeatureobjects, which can then be further filtered, displayed on a map, or exported in other formats.Open issues:
Featureobjects? Are they simply ignored? Is an exception raised?