Skip to content

DiGi.GIS.PostgreSQL.Enums

github-actions[bot] edited this page Sep 23, 2026 · 6 revisions

DiGi.GIS.PostgreSQL.Enums Namespace

Enums

AdministrativeArealType Enum

Represents the type of administrative area.

The value is the type_id column of administrative_areal_2d and travels the wire as an integer. One row is stored per polygon part of a unit, so a level holds more rows than there are real units - counties are 406 rows for 380 codes, and both country and voivodeship are 406 rows because every county part carries its own ancestor chain.

public enum AdministrativeArealType

Fields

Undefined -1

Undefined administrative area type.

Country 0

Country level administrative area.

Voivodeship 1

Voivodeship (province) level administrative area.

County 2

County (powiat) level administrative area.

Municipality 3

Municipality (gmina) level administrative area.

Subdivision 4

Subdivision level administrative area.

Renamed from the misspelled Subdivison (missing the second i), which was the accepted wire token until this build. Subdivison is now rejected with HTTP 400 - send Subdivision or the integer 4. The value is unchanged, so nothing stored under type_id is affected.

BuildingDataUpdateType Enum

Specifies the building data update type.

public enum BuildingDataUpdateType

Fields

General 0

General data update type, which mostly includes Building2D.

Database 1

Database data update type.

Occupancy 2

Occupancy data update.

RadialRatios 3

Radial ratios (Radial Building Coverage Ratio, Radial Floor Area Ratio) update.

Statistical 4

Statistical demographic data update.

YearBuilt 5

Year built data update: writes the predicted, user and calculated year-built columns.

UpdateRejectionReason Enum

Names why a row handed to an update never reached the database.

A row that cannot be filed under a county part is dropped rather than written, which used to leave no trace at all: the caller received only the identifiers of the rows that were stored, so a batch that stored one of five thousand looked exactly like a batch that stored all of them. The reason is carried alongside the reference because it decides what the caller should do next - a payload defect is worth correcting and reposting, a footprint that falls outside every candidate part is not.

public enum UpdateRejectionReason

Fields

Undefined 0

The element itself was null, so there is nothing to name.

MissingGeometry 1

The row carries no bounding box, so no county could even be attempted. A defect in the posted payload.

CountyUnresolved 2

County resolution ran and named no part. Not necessarily the caller's fault - the last tier decides by geometry, and a footprint falling outside every candidate part lands here.

PartitionUnavailable 3

The county resolved, but its partition could not be created, so every row filed under it was dropped. Server-side.

MissingCounty 4

The caller did not state a county identifier, and the row carries no geometry from which one could be inferred. A defect in the posted payload.

Clone this wiki locally