infureal/gis
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: Change geojson properties structure

Browse Source
This commit is contained in:
Bakhtiyar Issakhmetov
2026-07-01 00:48:02 +05:00
parent 8d9e11db0c
commit f74253140f
4 changed files with 87 additions and 45 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
api/openapi.yaml
View File

@@ -22,8 +22,8 @@ info:
name: Proprietary
servers:
- url: http://localhost:8080
description: Local development
- url: https://dssgis.dwh.kz/
description: Production
tags:
- name: Health
@@ -291,12 +291,13 @@ paths:
A `vector_with_kato` dataset is built from its observations. When it has
its own (dissolved) geometry, the observations are taken to describe that
whole geometry: a single Feature wraps it, and its properties hold only
the observations, keyed by KATO code at the top level (each KATO mapping
to its date->value pairs). Otherwise one Feature is emitted per KATO, its
boundary taken from the `districts` table and the per-year values
flattened into the Feature's properties keyed by date; KATO codes with
no matching district are skipped.
whole geometry: a single Feature wraps it, and its properties nest the
observations under a `data` object, keyed by KATO code (each KATO mapping
to its district `name` and its own `data` map of date->value pairs).
Otherwise one Feature is emitted per KATO, its
boundary taken from the `districts` table and the per-year values nested
under a `data` object (keyed by date) alongside `kato` and `name`; KATO
codes with no matching district are skipped.
Only `ready` datasets are served: a dataset still being processed
returns 409. Other file types (e.g. `raster`) return 422.
@@ -321,9 +322,9 @@ paths:
Like `/datasets/{id}.geojson`, but ignores any geometry the dataset
carries and always joins the `districts` table on KATO code: one Feature
is emitted per KATO, its boundary taken from the matching district and
the per-year observation values mapped into the Feature's properties
keyed by date (alongside `kato` and `name`). KATO codes with no matching
district are skipped.
the per-year observation values nested under a `data` object (keyed by
date) in the Feature's properties, alongside `kato` and `name`. KATO
codes with no matching district are skipped.
Only `ready` datasets are served: a dataset still being processed
returns 409. Other file types return 422.