Expose version information through API endpoints
Adds:
- /version.json
- /versions.json
- X-BAG-Version header to /lookup.json
Speedup final view insert with analyse
Sometimes (when track_counts=off maybe?) the query planner takes the
wrong approach when selecting data for the "bag" table and the statement
takes many hours to finish instead of minutes.
Update sanity baseline counts
Clean import failed because number of "standplaats" jumped over 20% from
2023-01-08.
Only accept dataset which are larger than the original/current
To avoid getting downgraded.
Run updater on specific time of the day
Note: the update at startup still happens.
Ignore bad object geometries
Some objects contain geometry values outside of the Netherlands. They
are wrong, but rare and normally get corrected in the next update but
they do mess up the visualization.
Automatic prune old versions
Use RETENTION_SUCCESS and RETENTION_FAILURE environment variables to
configure the amount of versions to retain.
Add build failure email trigger
Track all gebruiksdoel for a given VBO
There can be multiple destination of use for a given residence. The
order doesn't appear to be as meaningful as the combination of the uses
together. This change allows for all `gebruiksdoel` values to be
tracked in `straatnaam`
Add presentation
Presented at "Eerlijke WOZ B.V." on 2022-10-12.
Fix for overlapping nummeraanduiding records
Speedup import
Import the large datasets (NUM, PND, VBO) in parallel with the rest.
Filter out inactive objects
Objects with status denoting it no longer exists will be considered
inactive and thus excluded from the exposed tables and views.
Expose verblijfsobject and pand tables
SELECT
bag.*, vbo.oppervlakte, pnd.oorspronkelijk_bouwjaar
FROM
bag
LEFT JOIN
verblijfsobject vbo
ON
vbo.id = bag.object_id
LEFT JOIN
verblijfsobject_pand vbo_pnd
ON
vbo_pnd.id = bag.object_id
LEFT JOIN
pand pnd
ON
vbo_pnd.pand_id = pnd.id