django-teryt
django-teryt is a Django app that implements TERYT database. TERYT (Polish: “Krajowy Rejestr Urzędowy Podziału Terytorialnego Kraju”, English: “National Official Register of Territorial Division of the Country”) is a register maintained by Polish Central Statistical Office (Polish: Główny Urząd Statystyczny; GUS). Among other things it contains:
identifiers and names of units of territorial division,
identifiers and names of localities,
identifiers and names of streets
This app parses XML files from GUS and it imports them to the database. It is meant to be used as a part of a larger system.
Documentation
The full documentation is at https://django-teryt.readthedocs.org.
Quickstart
Install django-teryt:
pip install django-teryt
If you are using Django 1.6 or lower you have to install South:
pip install 'south>=1.0'
Add teryt to INSTALLED_APPS in your settings.py and run:
./manage.py migrate teryt
Then download TERYT data from GUS website, unpack it and then import it:
./manage.py teryt_parse /path/to/WMRODZ.xml /path/to/TERC.xml /path/to/SIMC.xml /path/to/ULIC.xml
Features
It can import all data from all TERYT files
It deals with updates (just run ./manage.py teryt_parse –update TERC.xml)
It keeps flag (aktywny) telling you if some record is still present in TERYT (there are some minor changes in territorial division from time to time)
Support
All bug reports and pull requests are welcome. You can report them at https://github.com/scibi/django-teryt/issues. It can be in English or in Polish ;)
History
0.1.0 (2013-12-31)
First release on PyPI.
0.2.0 (2015-01-08)
Added support for Django 1.7 migrations
Moved common data to abstract base class
Added common flag filed (aktywny)
Added 3 model managers to JednostkaAdministracyjna
Fixed PEP 8 compliance in main source files
0.3.0 (2015-01-06)
Added support for Django 1.8 and 1.9
Added support for SQLite and MySQL/MariaDB
Python 3.4 compatibility
Improved test coverage
This is last version to support Django 1.6 and South
1 maintainer
Metadata
1 maintainer
Release files for django-teryt 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| django-teryt-0.3.0.tar.gz | 15.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| django_teryt-0.3.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details |
Total release size: 39.7 kB
Release files / django-teryt-0.3.0.tar.gz
| Download URL | django-teryt-0.3.0.tar.gz |
|---|---|
| Size | 15.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
394e8fd5c9270bd68e2dc4bd965265b11ab07501dfd9a3436f751dc7f50ce428
|
|
BLAKE2b-256 checksum How to use checksums |
4dbbdc2c4dab77f188b98b5d73ed1f2145ce5a076db6e6742ecc5ebb23ab6128
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / django_teryt-0.3.0-py2.py3-none-any.whl
| Download URL | django_teryt-0.3.0-py2.py3-none-any.whl |
|---|---|
| Size | 24.4 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
54cf52f8351a45e10a94541d1600ade8e32be7898382937b1931ab03b8501581
|
|
BLAKE2b-256 checksum How to use checksums |
5e2c604ec276df3b9593656ca111855eb4b7db998ee2c307f525e346f7db6338
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for django-teryt 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
