v8.0.0
GeoRegions v8.0.0
Release Notes:
- Bump to v8 because of many breaking changes (see below)
- Now there is only one GeoRegion type that is used
- All information is now stored in
.json
files instead of.txt
files to speed up saving when a project has many GeoRegions - All GeoRegions now have a rotation component
- A lot of reduction in the methods for functions because there is now only one GeoRegion type instead of three
- Improved leniency for
in()
andon()
functions - Export centroid of geometry in structure
- Added a "derotation" functionality that can, based on the assumed rotation of the GeoRegion in
geo.θ
, derotate a given set of coordinates around the GeoRegion centroid into an x-y cartesian domain
Breaking Changes
- Breaking changes to types, no more
RectRegion
,PolyRegion
andTiltRegion
types, all have been consolidated into a singleGeoRegion
type - Breaking change to define custom GeoRegions, now
ID
,pID
andname
are keyword arguments, only longitude and latitude vectors are non-keyword arguments - Breaking changes to project handling and functions
- Storing all information in
.json
files, so all previously defined GeoRegions will need to be redefined into this new file format