## [2.5.1] - 2026-08-02

- Take a layer's symbol from its tabaka, never from its name. A layer
holding
  one tabaka fell through to matching its own layer name, which only
ever
  worked while layers were named after a category whose name happened
to
  contain the tabaka's keyword. Once layers took the official upper
group
  names, that stopped being true: 15 of the 24 official group names
identify
  nothing at all, so `PL_DERE` — sitting in a layer named after group
  `SU - ATIKSU VE ATIK SİSTEMLERİ` — came out plain grey instead of
water
  blue, and `SNR_YAPIYAK` and `HAT_KADEME` lost their official styling
the
  same way. Worse, a group name can identify the *wrong* thing: read
as a
  tabaka, `İDARİ SINIRLAR` lands on İdari Hizmet Alanı, an area rather
than a
  boundary. Single-tabaka layers are now categorised on the tabaka
like every
  other layer.
- Draw plan areas with a 0.7 mm outline. The official style set leaves
the
  outline off most polygon rules, since the fill or the tarama carries
the
  meaning, but a plan sheet still needs its function boundaries to
read.
  Rules that state their own outline keep it.

## [2.5.0] - 2026-08-02

- Group layers by the Ministry's own upper groups. PlanGML mode
grouped tabaka
  into seven categories that read like the regulation's but were not
from it;
  it now uses the upper groups of the official UİP tabaka catalog, so
a plan
  opens organised the way the regulation organises it — `KONUT
ALANLARI /
  YERLEŞİM ALANLARI`, `KENTSEL ÇALIŞMA ALANLARI`, `EĞİTİM TESİSLERİ
ALANI`,
  `PLANLAMA SINIRLARI`, `ÖZEL ÇİZGİLER` and the rest. **Layer names
change
  accordingly.**
- Tabaka the catalog does not define — CAD symbol and text layers, and
local
  names with no unambiguous official counterpart — go to a single
  `DİĞER PLAN ALANLARI` layer. It is deliberately the only group name
in the
  tree that is not the Ministry's own: mixing official names with
invented ones
  that look almost identical would make the tree harder to read, not
easier.
- The layer tree and the PlanGML schema columns now agree, since both
are
  resolved from the same official catalog.

## [2.4.0] - 2026-08-02

- Fill the PlanGML schema columns with the Ministry's own codes. They
were
  derived from the symbology engine's keyword lists, which hold no
codes at
  all, so every feature came out claiming upper group `100` — a value
that
  means nothing and that survives into an exported GeoPackage looking
  authoritative. `PL_KONUT` now comes out as upper group `112000`
"KONUT
  ALANLARI / YERLEŞİM ALANLARI", function `112002` "YERLEŞİK KONUT
ALANI".
- The 256 tabaka and 25 upper groups of the official UİP tabaka
catalog are
  compiled into the plugin from the Mekânsal Planlar Yapım Yönetmeliği
UİP
  database. A short, documented alias list resolves local spellings a
  municipality actually uses onto the official tabaka they are the
same
  function as, so `PL_BELEDIYE` reads as `110004` Belediye Hizmet
Alanı and
  `PL_SAGLIK_OCAGI` as `115001` Aile Sağlığı Merkezi.
- A tabaka the catalog does not define gets **empty code cells**, not
invented
  ones. That covers CAD helper layers — symbol, text-anchor, rölöve —
which
  have no planning identity to claim, and the handful of local names
with no
  unambiguous official counterpart. A plausible-looking code in a
column
  reserved for the Ministry's codes is worse than an empty cell.
- The drawing's own tabaka name is still kept in `uip_tabaka`, so
layer
  grouping, the categorised symbology and what you recognise on screen
are
  unchanged.
- `THIRD_PARTY_NOTICES.md` records the catalog's source and what is
reproduced
  from it, alongside the plan gösterimleri already noted there.

## [2.3.2] - 2026-08-02

- Draw `PL_KONUT` as yerleşik konut. The Ministry's own UİP tabaka
catalog
  settles the reading under upper group 112000 "KONUT ALANLARI /
YERLEŞİM
  ALANLARI": 112001 GELİŞME KONUT ALANI is the tabaka
`PL_GELISME_KONUT`, and
  112002 YERLEŞİK KONUT ALANI is the tabaka `PL_KONUT`. A bare
`PL_KONUT` is
  therefore not a generic konut needing a default, and it was being
given the
  gelişme colour. Gelişme konut keeps its own reading and its own
colour.
- Draw kaldırım, refüj and yaya yolu as 0.3 mm hairlines. Their widths
are
  declared in the official style set in **metres of ground** —
kaldırım and
  refüj are 1 m wide, some watercourses 2.83 m — and were being copied
into a
  paper width, which drew them several times too heavy. Widths under a
metre
  unit are now recognised as ground widths and given the drawing
convention
  for plan line objects instead.
- Clear the two findings the QGIS Hub reported on the previous
version: an
  unused `dataclasses.field` import that shadowed a local name (Flake8
F811),
  and five unscoped Qt enum members
(`QgsSimpleMarkerSymbolLayer.Square` and
  friends, `QgsUnitTypes.RenderPixels`). The scoped spellings were
verified to
  work on both QGIS 3.44 LTR and QGIS 4.2 before being adopted.

None