Releases: Terralego/django-geostore
Releases · Terralego/django-geostore
0.5.4
0.5.3
0.5.2
0.5.1
0.5.0
!! WARNING - BREAKING CHANGES !!
Features with empty geometry will not pass anymore Integrity Error Check
Please, check and fix you geostore_feature table first before making migrations
-
Add constraint empty geometries
-
Add validation of constraints on geometries
-
geostore.routing has been extracted to django-geostore-routing
- add django-geostore-routing to your project dependencies
- add geostore_routing to you INSTALLED_APPS instead of geostore.routing
-
Add relation property to handle relations directly in feature
-
Force geometries 2d
-
Improve tile generation
0.4.3
0.4.2
0.4.1
0.4.0
-
WARNING Breaking Changes !!
- to continue to use PGRouting features, please add geostore.routing to INSTALLED_APPS
- Some changes in routing API response. Now final geometry and full feature segment list are provided by API
- Configurable tolerance for routing topologies (Default value from 0.0001 to 0.00001)
- HOSTNAME setting is deprecated. Default request HOST is now used to generate absolute full urls for vector tiles.
You can set TERRA_TILES_HOSTNAMES = [HOSTNAME, ] to avoid this
-
Improvements :
- Officially support django 3.1
- Set HOSTNAME or TERRA_TILES_HOSTNAMES is not required anymore. Now full absolute urls are prefixed with current host request
- Installing PGRouting is not required anymore.
- source / target routing attributes :
- add indexes
- Hide by default (editable=False)
- Using JSONField from django.db.models
- Updating DjangoModelFactory location