wget https://services.arcgis.com/xOi1kZaI0eWDREZv/arcgis/rest/services/NTAD_North_American_Roads/FeatureServer/replicafilescache/NTAD_North_American_Roads_3862439624850511818.geodatabase
Connection to NTAD_North_American_Roads_3862439624850511818.geodatabase failed check: no such module: VSRS
I based my work on this, maybe the link is out, thx for testing. The dataset has already been consumed and collapsed into a smaller graph representation.
I assume you mean non-LLM.
--------------
Question for those familiar with uv. US Routing apparently requires a very specific Python version (3.11 and nothing else), but my system has Python 3.10.9 installed at the moment and I'd rather not upgrade the global version just now. My understanding from reading a lot of uv evangelism on HN and elsewhere is that uv fixes this type of dilemma. But, having just tried to use it to install this package, it's just giving me the same old Python version errors:
C:\devel\us-routing-master\us_routing>uv venv
Using CPython 3.10.9 interpreter at: c:\WinPython-31090
\python-3.10.9.amd64\python.exe
Creating virtual environment at: .venv
Activate with: .venv\Scripts\activate
C:\devel\us-routing-master\us_routing>.venv\Scripts\activate
(us_routing) C:\devel\us-routing-master\us_routing>uv pip
install us-routing
x No solution found when resolving dependencies:
`-> Because the current Python version (3.10.9) does not
satisfy Python>=3.11,<3.12 and us-routing==0.1.0
depends on Python>=3.11,<3.12, we can conclude that us-
routing==0.1.0 cannot be used.
And because only us-routing==0.1.0 is available and you
require us-routing, we can conclude that your
requirements are unsatisfiable.
I imagine you'd want:
uv venv --python 3.11
What you want is `uv venv —python 3.11` to create a virtual environment with Python 3.11 without messing up your global system env. This should also install a portable version of Python 3.11 if needed (which it will be since you don’t have it).
https://docs.astral.sh/uv/pip/environments/#creating-a-virtu...
``` :: Step 1: Install pyenv-win (make sure Git is installed) git clone https://github.com/pyenv-win/pyenv-win.git "$env:USERPROFILE\.pyenv"
:: Step 2: Add pyenv to PATH (run or add to your profile) $env:PYENV = "$env:USERPROFILE\.pyenv\pyenv-win" $env:PATH += ";$env:PYENV\bin;$env:PYENV\shims"
:: Step 3: Restart your terminal or reload environment if needed :: (you can paste the above $env:... lines again after restart)
:: Step 4: Install Python 3.11 pyenv install 3.11.9
:: Step 5: Set the local Python version for your project folder cd C:\devel\us-routing-master\us_routing pyenv local 3.11.9
:: Step 6: Verify correct Python is selected pyenv which python # should point to 3.11.x
:: Step 7: Create uv environment using Python 3.11 uv venv .venv --python "$(pyenv which python)"
:: Step 8: Activate the environment .venv\Scripts\activate
:: Step 9: Install your package uv pip install us-routing ```
pyenv is a great way to have many versions of Python installed, whether or not your global is mapped to the latest. You don't even need to set the local .python_version.. you could just do `uv venv .venv --python=python3.11`
Glad to see this is for roads.
FREEWAY = 1 # Freeway (Multi-lane, controlled access)
PP_TH = 2 # Primary Provincial/Territorial highway
SP_TH_MA = 3 # Secondary Provincial/territorial highway/ municipal arterial
MC_USP_TH = 4 # Municipal collector/Unpaved secondary provincial/territorial highway
LS_WR = 5 # Local street/ winter road
3 was the sweetspot. The dataset can be explored here in case you want to get an intuition on detail level. https://geodata.bts.gov/datasets/usdot::north-american-roads...
dmitrygr•11h ago
ivanbelenky•11h ago