v6.0.0 (2023-12-14)
See v5 to v6 migration guide
π₯ Breaking Changes
explodeMulti
property is now explicitly required for internal datasources in your projects datasources.json. When true
(default), all multipolygons are broken up into polygons, with properties persisted. This reduces the number of polygons to be fetched when you just need the features within the bounding box of your sketch. When set to false
, it will use PROMOTE_TO_MULTI
option to make everything a multipolygon. So an imported datasources will never be a mixture of polygons and multipolygons. This is required by the flatgeobuf driver, among others.
π New Feature / Improvement
- Split vector datasources on import using ogr2ogr wrapdateline option.
- Increase raster import performance - add lzw compression, multithreaded, and increase cache size.
- Drop creation of extra xml metadata file on raster import.
- Add
splitSketchAntimeridian
and splitFeatureAntimeridian
functions to split polygons crossing 180 degree antimeridian into multipolygon pieces on either side of it.
- Add
cleanCoords
function to adjust Polygon coordinates within -180 to 180 degrees prior to splitting.
- Refactor code generated by
create:function
to include geography and antimeridian handling, as well as demonstrating fetching data from global vector and raster datasources.
- Refactor code generated by
create:client
to include a more robust top-level report with Translator
, and a lower-level card component. Allow the user to specify the name of the geoprocessing function that gets called.
- Add BioOracle and TNC Marine Ecosystems of the World global datasources to default.
π Bug Fix
- Fix
create:client
and create:function
CLI commands.
- overlapFeatures - fix bug when multipolygon both params, clarify precalc question on data import
π Internal
- Reproject multi_class_variability test dataset to proper 4326
- Upgradee to Geoblaze 2.5.0 with better support for antimeridian use cases.
- Upgrade to Georaster 1.6.0
- Refactor template-blank-project and template-ocean-eez functions and clients to support antimeridian.
π Documentation
- Add antimeridian sections to Concepts page
- Rewrite Tutorials for creating a geoprocessing function and report client.