{"name": "02CadGis Universal CAD/GIS Importer", "package_name": "zero2cadgis", "version": "2.5.1", "experimental": false, "qgis_min": "3.22.0", "qgis_max": "4.99.0", "downloads": 552, "uploaded_by": "geo140195philo", "upload_datetime": "2026-08-01T18:34:27.699861", "changelog": "## [2.5.1] - 2026-08-02\r\n\r\n- Take a layer's symbol from its tabaka, never from its name. A layer holding\r\n  one tabaka fell through to matching its own layer name, which only ever\r\n  worked while layers were named after a category whose name happened to\r\n  contain the tabaka's keyword. Once layers took the official upper group\r\n  names, that stopped being true: 15 of the 24 official group names identify\r\n  nothing at all, so `PL_DERE` \u2014 sitting in a layer named after group\r\n  `SU - ATIKSU VE ATIK S\u0130STEMLER\u0130` \u2014 came out plain grey instead of water\r\n  blue, and `SNR_YAPIYAK` and `HAT_KADEME` lost their official styling the\r\n  same way. Worse, a group name can identify the *wrong* thing: read as a\r\n  tabaka, `\u0130DAR\u0130 SINIRLAR` lands on \u0130dari Hizmet Alan\u0131, an area rather than a\r\n  boundary. Single-tabaka layers are now categorised on the tabaka like every\r\n  other layer.\r\n- Draw plan areas with a 0.7 mm outline. The official style set leaves the\r\n  outline off most polygon rules, since the fill or the tarama carries the\r\n  meaning, but a plan sheet still needs its function boundaries to read.\r\n  Rules that state their own outline keep it.\r\n\r\n## [2.5.0] - 2026-08-02\r\n\r\n- Group layers by the Ministry's own upper groups. PlanGML mode grouped tabaka\r\n  into seven categories that read like the regulation's but were not from it;\r\n  it now uses the upper groups of the official U\u0130P tabaka catalog, so a plan\r\n  opens organised the way the regulation organises it \u2014 `KONUT ALANLARI /\r\n  YERLE\u015e\u0130M ALANLARI`, `KENTSEL \u00c7ALI\u015eMA ALANLARI`, `E\u011e\u0130T\u0130M TES\u0130SLER\u0130 ALANI`,\r\n  `PLANLAMA SINIRLARI`, `\u00d6ZEL \u00c7\u0130ZG\u0130LER` and the rest. **Layer names change\r\n  accordingly.**\r\n- Tabaka the catalog does not define \u2014 CAD symbol and text layers, and local\r\n  names with no unambiguous official counterpart \u2014 go to a single\r\n  `D\u0130\u011eER PLAN ALANLARI` layer. It is deliberately the only group name in the\r\n  tree that is not the Ministry's own: mixing official names with invented ones\r\n  that look almost identical would make the tree harder to read, not easier.\r\n- The layer tree and the PlanGML schema columns now agree, since both are\r\n  resolved from the same official catalog.\r\n\r\n## [2.4.0] - 2026-08-02\r\n\r\n- Fill the PlanGML schema columns with the Ministry's own codes. They were\r\n  derived from the symbology engine's keyword lists, which hold no codes at\r\n  all, so every feature came out claiming upper group `100` \u2014 a value that\r\n  means nothing and that survives into an exported GeoPackage looking\r\n  authoritative. `PL_KONUT` now comes out as upper group `112000` \"KONUT\r\n  ALANLARI / YERLE\u015e\u0130M ALANLARI\", function `112002` \"YERLE\u015e\u0130K KONUT ALANI\".\r\n- The 256 tabaka and 25 upper groups of the official U\u0130P tabaka catalog are\r\n  compiled into the plugin from the Mek\u00e2nsal Planlar Yap\u0131m Y\u00f6netmeli\u011fi U\u0130P\r\n  database. A short, documented alias list resolves local spellings a\r\n  municipality actually uses onto the official tabaka they are the same\r\n  function as, so `PL_BELEDIYE` reads as `110004` Belediye Hizmet Alan\u0131 and\r\n  `PL_SAGLIK_OCAGI` as `115001` Aile Sa\u011fl\u0131\u011f\u0131 Merkezi.\r\n- A tabaka the catalog does not define gets **empty code cells**, not invented\r\n  ones. That covers CAD helper layers \u2014 symbol, text-anchor, r\u00f6l\u00f6ve \u2014 which\r\n  have no planning identity to claim, and the handful of local names with no\r\n  unambiguous official counterpart. A plausible-looking code in a column\r\n  reserved for the Ministry's codes is worse than an empty cell.\r\n- The drawing's own tabaka name is still kept in `uip_tabaka`, so layer\r\n  grouping, the categorised symbology and what you recognise on screen are\r\n  unchanged.\r\n- `THIRD_PARTY_NOTICES.md` records the catalog's source and what is reproduced\r\n  from it, alongside the plan g\u00f6sterimleri already noted there.\r\n\r\n## [2.3.2] - 2026-08-02\r\n\r\n- Draw `PL_KONUT` as yerle\u015fik konut. The Ministry's own U\u0130P tabaka catalog\r\n  settles the reading under upper group 112000 \"KONUT ALANLARI / YERLE\u015e\u0130M\r\n  ALANLARI\": 112001 GEL\u0130\u015eME KONUT ALANI is the tabaka `PL_GELISME_KONUT`, and\r\n  112002 YERLE\u015e\u0130K KONUT ALANI is the tabaka `PL_KONUT`. A bare `PL_KONUT` is\r\n  therefore not a generic konut needing a default, and it was being given the\r\n  geli\u015fme colour. Geli\u015fme konut keeps its own reading and its own colour.\r\n- Draw kald\u0131r\u0131m, ref\u00fcj and yaya yolu as 0.3 mm hairlines. Their widths are\r\n  declared in the official style set in **metres of ground** \u2014 kald\u0131r\u0131m and\r\n  ref\u00fcj are 1 m wide, some watercourses 2.83 m \u2014 and were being copied into a\r\n  paper width, which drew them several times too heavy. Widths under a metre\r\n  unit are now recognised as ground widths and given the drawing convention\r\n  for plan line objects instead.\r\n- Clear the two findings the QGIS Hub reported on the previous version: an\r\n  unused `dataclasses.field` import that shadowed a local name (Flake8 F811),\r\n  and five unscoped Qt enum members (`QgsSimpleMarkerSymbolLayer.Square` and\r\n  friends, `QgsUnitTypes.RenderPixels`). The scoped spellings were verified to\r\n  work on both QGIS 3.44 LTR and QGIS 4.2 before being adopted.", "external_deps": null, "download_url": "https://plugins.qgis.org/plugins/zero2cadgis/version/2.5.1/download/"}