These would make great inclusions for example.gramps in the 5.2 version. Thanks!
Although there is no animation support for KML polygons yet (as @Nick-Hall suggest below), perhaps we should include a sequence of dated KMLs in anticipation?
But before we trip over our enthusiasm, we need a place to collate suggested inclusions.
And a way so that multiple contributor don’t swamp the system with too many files where the extraneous change hide the desired update. (For instance, importing can update every record with a tag & a source by default. It would be unworkable trying to wade through all that “change” background noise.)
The Import Merge Tool by @prculley creates a short-lived worklist of mergeable changes. Maybe the list objects could be routed to the export as workable delta file? (Are imported .gramps object handles persistent enough across trees to allow backlinks to an object that wouldn’t be included in the delta file?) Then the Delta file could just be imported directly to populate that merge Tool.