UTRANS Tools
utrans-tools provides command-line tools for working with UTRANS data.
Install for users
conda create --name utrans-tools --clone arcgispro-py3
conda activate utrans-tools
pip install ugrc-utrans-tools
Show help:
utrans --help
Upgrade to a new version:
pip install --upgrade ugrc-utrans-tools
Install for development
From this directory:
conda create --name utrans-tools --clone arcgispro-py3
pip install -e ".[dev]"
Upgrade these packages if you have troubles installing the dev version:
pip install --upgrade pathspec hatchling
Usage
Get Recent Edits
utrans get-recent-edits --county Carbon --update-features "Z:\Documents\gdb\Carbon20231019.gdb\Roads" --base-features "Z:\Documents\gdb\Carbon20230208.gdb\CC_Roads"
The output is written to the geodatabase containing --update-features.
Run utrans get-recent-edits --help for the complete option reference and supported county profiles.
ETL
Convert county roads to the UTRANS schema with explicit inputs:
utrans etl --county saltlake --source-features "Z:\Documents\gdb\SaltLake.gdb\RoadCenterline_Recents" --utrans-roads "Z:\schemas\UtahRoadsNGSchema.gdb\Roads_Edit" --county-boundaries "Database Connections\internal.sde\SGID.BOUNDARIES.Counties"
The output is written to the geodatabase containing --source-features. It contains complete road features that intersect the selected county boundary; it does not clip features at the boundary. Run utrans etl --help for all options.
Detect Changes
Process ETL output against a previous UTRANS road feature class:
utrans detect-changes --county Carbon --update-features "Z:\Documents\gdb\Carbon.gdb\county_etl" --utrans-features "Z:\Documents\gdb\UTRANS.gdb\Roads" --append-target "Database Connections\internal.sde\UTRANS.DFC_RESULT"
The command writes outputs to the geodatabase containing --update-features. It uses the NAME matching and comparison fields, adds DFC editor metadata, creates TEST_DFC_RESULT with NC and D changes excluded, and appends the filtered result to --append-target.
Run utrans detect-changes --help for the remaining options.
Metadata
Release files for ugrc-utrans-tools 1.1.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 | |
|---|---|---|---|
| ugrc_utrans_tools-1.1.0.tar.gz | 46.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| ugrc_utrans_tools-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 74.2 kB
Release files / ugrc_utrans_tools-1.1.0.tar.gz
| Download URL | ugrc_utrans_tools-1.1.0.tar.gz |
|---|---|
| Size | 46.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3b52fae207844d7bc6cc7babdf5eed55d331158920a5e0fe8e8c97f6dff9b7ff
|
|
BLAKE2b-256 checksum How to use checksums |
05ed769deaa33a295f61d942fca36a51ae04419aa613fb7554140cc09832ffd9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 28, 2026.
Transparency logRelease files / ugrc_utrans_tools-1.1.0-py3-none-any.whl
| Download URL | ugrc_utrans_tools-1.1.0-py3-none-any.whl |
|---|---|
| Size | 28.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
38580cbad440ec45fd8337081d0e07a676ffed9c864ea7c8847a5e9300aaae1f
|
|
BLAKE2b-256 checksum How to use checksums |
82624f237f57e33094ed9656e9cb29b00aa55e1544f18f759d374f701baf8d8c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 28, 2026.
Transparency log