Here is the patch that I applied to my local //third_party/tiff copy of
libtiff. My local libtiff and gdal are both at upstream head. I'm using
bazel for building, so I don't have any autoconf or cmake patches. In case
folks want, here is what I have. Suggestions welcome if I did anything
wrong or
Hey Jesse,
I *think* I simplified your query a bit. Untested, but it may work.
delete from {label_name}
where gdal_get_pixel_value('{raster_fp}', {ndvi_band_num}, 'georef',
ST_X(st_centroid(geom)), ST_Y(st_centroid(geom))) < 600
Scott
On 1/8/25 12:53, Meyer, Jesse R. (GSFC-618.0)[SCIENCE SYS
Thanks Even, and appreciate pointer to the GeoTIFF 2.0 spec discussion.
> "If you can sacrifice the ellipsoidal height axis to avoid using a Projected
> 3D CRS, which is a bit of a geodetic dubious object (don't ask me more, but
> minds more enlightned than me question the soundness of using an
Hi Patrick,
I’m working with a GeoPackage database file, using the SQLITE dialect, and
submitting the query through the ExecuteSQL interface on the database object in
Python. This makes the art of crafting SQL queries a bit tricky because ontop
of SQL concerns there’s also the abstraction OGR
Hi, Jesse,
I assume you're working in SQLAlchemy or something, so there may be more to
this than I'm thinking, but if the parsing errors are actually coming from the
Postgres server(?), there should be plenty of ways around your issue, one way
or another. Before you try to get especially fancy,
BTW If this question is too specific to SQL and I should seek aid elsewhere,
please let me know.
I am able to return a layer of rowids associated with features whose geotiff
band value at the centroid location is above a particular threshold. I then
turn back around and delete all such feature
Jesse,
I seem to be able to remove features from a GPKG datasource using
ExecuteSQL and “delete from layer_name where cond” style query with
the SQLITE dialect. For some of our use cases, this is quite a bit
nicer than a manual loop in Python.
Are there restrictions or other concerns that I
All,
On Robert C.'s advice I am currently investigating using vcpkg to fulfill
my company's build requirements. I haven't successfully managed to build
GDAL to our specifications yet. But if I do, I will make sure to post
details to this thread,
On Mon, Jan 6, 2025 at 6:52 PM Greg Troxel wrote:
I seem to be able to remove features from a GPKG datasource using ExecuteSQL
and “delete from layer_name where cond” style query with the SQLITE dialect.
For some of our use cases, this is quite a bit nicer than a manual loop in
Python.
Are there restrictions or other concerns that I should ke
Scott,
I’d like to be able to store a custom WKT *inside GeoTiff metadata* rather
than in an external PAM file.
GeoTIFF CRS encoding is a custom one, and doesn't support WKT (there's
some hypothetical idea of allowing/mandating WKT2 for an hypothetical
GeoTIFF 2.0 spec : https://github.co
Hello gdal-dev,
I’ve looked around for an answer to this one to no avail and would appreciate
any insight from those more familiar with the GeoTiff format. I’d like to be
able to store a custom WKT *inside GeoTiff metadata* rather than in an external
PAM file. I’ve seen some solutions to add cu
Hi,
Changes since RC1:
- revert "CMake: Export -DGDAL_DEBUG as PUBLIC for debug builds (#11311)"
- gml:CircleByCenterPoint: correctly take into account radius.uom for
projected CRS
- swig/python/setup.py.in: fix exception when building a RC git tag
Pick up an archive among the following ones (
12 matches
Mail list logo
