Skip to content

Conversation

@brianhelba
Copy link
Member

No description provided.

Comment on lines +128 to +129
GDAL_LIBRARY_PATH = osgeo.GDAL_LIBRARY_PATH
GEOS_LIBRARY_PATH = osgeo.GEOS_LIBRARY_PATH
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment on lines +115 to +121
[[tool.uv.index]]
name = "large_image_wheels"
url = "https://girder.github.io/large_image_wheels/"
explicit = true

[tool.uv.sources]
gdal = { index = "large_image_wheels" }
Copy link
Member Author

@brianhelba brianhelba Jan 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"opencv-python-headless",
"tqdm",
# guano metadata
"gdal",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wanted to put this under the correct comment mini-block, but I'm not sure where that would be.

It also seems like geopandas below should go with it?

g++ \
libgdal36 \
libc6-dev \
libpq-dev \
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

libpq-dev is no longer needed regardless. It supports Psycopg, which is now available purely via the Python wheel.

@brianhelba
Copy link
Member Author

I think this is an improvement, as I'd like to get towards a place where system libraries aren't required, as this makes deployment much easier and more portable. It also aligns with 12 Factor: Dependencies, as we want all of our application dependencies to be defined within our Python lockfile, rather than implicitly depending on system versions that we may not always have full control over.

I need help testing this and need help understanding exactly where GDAL is being required from (so we can make sure that the installed wheel satisfies the usage).

@BryonLewis
Copy link
Collaborator

I need help testing this and need help understanding exactly where GDAL is being required from (so we can make sure that the installed wheel satisfies the usage).

So we used to have a tile server for the spectrograms until we converted to using side-by-side JPEGS.

The other case is in the creation of the GRTS Cell Ids. This is a 10x10km grid across the North America that is used by USGS with their NABat project to identify locations of bats. They originally provided this to us as a large CSV with a tons of rows to be ingested. It's quicker to utilize the shapefiles and process them for ingestion (like 2 minutes vs the 15-20 for the CSV they gave us)
./core/managment/commands/loadGRTS.py or docker compose run --rm django ./manage.py loadGRTS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants