Re: [gdal-dev] GDALOpenShared: warning about "filename" vs "description"

To my eye this looks like a very old 'warning' from Frank W's era, where he was taming cats (user community) and dsn were, reasonably, file names of a sort. Would overhead of regex comparing terminating characters after final '/' meet the file name versus descriptor still be useful? I imagine he wa

Re: [gdal-dev] CMAKE Report:[ 98%] Linking CXX executable pytest_runner; recompile with -fPIE/-fPIC

GDAL driver and OGR to OFF Updated Netcdf, HDF4 & HDF5 - so stack improved there I got so conditioned to out of tree builds that I tried it on the python reinstall. CMake, it's more than a build, it's an adventure. Chris On Sat, Mar 5, 2022 at 10:50 PM chris english wrote: >

Re: [gdal-dev] crunch lib

and > then managed to build GDAL against it with "cmake .. > -DCMAKE_PREFIX_PATH=/home/even/install-crunch" > > Even > > Le 04/03/2022 à 01:48, chris english a écrit : > > https://github.com/DaemonEngine/crunch > > appears to be a better source to point to for c

Re: [gdal-dev] Attempting a coherent CMAKE problem report from a git clone- steps taken

Sun, Mar 6, 2022 at 1:50 PM Even Rouault wrote: > > Le 05/03/2022 à 06:30, chris english a écrit : > > Kai, > Rebuilt Geos with your insight, and two spaces between all -D entries, > including eliminating MrSid that was complied under gcc 521 or so and might > likely cause p

Re: [gdal-dev] CMAKE poppler c++17

I will follow your lead locally and comment out the GCC version check as MrSid is useful, and perhaps Maintainer to Maintainer would have more effect over at LizardTech. And apologies for inflicting this on your work email threads. I noted a desire to get feedback in anticipation of the CMAKE tran

[gdal-dev] CMAKE Report:[ 98%] Linking CXX executable pytest_runner; recompile with -fPIE/-fPIC

This can't be a novel 'almost got there', but then not. [ 98%] Linking CXX executable pytest_runner /usr/bin/ld: /usr/local/lib/libpython3.6m.a(pylifecycle.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a PIE object; recompile with -fPIE /usr/bin/ld: /usr/local/lib/

Re: [gdal-dev] Attempting a coherent CMAKE problem report from a git clone- steps taken

Kai, Rebuilt Geos with your insight, and two spaces between all -D entries, including eliminating MrSid that was complied under gcc 521 or so and might likely cause problems, using GDAL build hints , and we have success on on *target gcore_mdreader*, and I'll move

Re: [gdal-dev] Attempting a coherent CMAKE problem report from a git clone- steps taken

EOS::geos_c "${_IMPORT_PREFIX}/lib/libgeos_c.so.1.16.0" ) # Commands beyond this point should not need to know the version. set(CMAKE_IMPORT_FILE_VERSION) On Fri, Mar 4, 2022 at 2:02 PM chris english wrote: > Concerning (executed in either git download directory or build): &g

[gdal-dev] Attempting a coherent CMAKE problem report from a git clone- steps taken

Concerning (executed in either git download directory or build): ~/gdal$ git describe v3.3.0-2898-gba4e7c404b Condition: was building and stopped with [ 89%] Built target gcore_mdreader CMakeFiles/GDAL.dir/build.make:2661: *** target pattern contains no '%'. Stop. make[1]: *** [CMakeFiles/Makefile

[gdal-dev] crunch lib

https://github.com/DaemonEngine/crunch appears to be a better source to point to for crunch, as it builds, whereas crunch link in docs doesn't. And builds for the hapless, as I believe I've demonstrated. Chris ___ gdal-dev mailing list gdal-dev@lists.osge

[gdal-dev] CMAKE [ 89%] Built target gcore_mdreader *** target pattern contains no '%'

This subject line is a mash up of this: [ 89%] Built target gcore_mdreader CMakeFiles/GDAL.dir/build.make:2661: *** target pattern contains no '%'. Stop. make[1]: *** [CMakeFiles/Makefile2:4871: CMakeFiles/GDAL.dir/all] Error 2 and hereafter I have no idea of how to proceed. I've previously dispe

Re: [gdal-dev] CMAKE poppler c++17

to patch GDAL 3.4.1 > for this, but in your case you might want to grab GDAL-master from git > as that will be easier to handle the new poppler. > > > -jeff > > > > -- > Jeff McKenna > GatewayGeo: Developers of MS4W, MapServer Consulting and Training > co-founder of

[gdal-dev] CMAKE poppler c++17

Hi, I am a weak link when it comes to CMAKE. Geos-3.10.2 and PROJ-8.2.1 were a breeze nonetheless. A source build of libpoppler.so.119 via ./configure went smoothly. I have consistently failed at ogrpdflayer (well, only four times so far) on 'optional', that is a C++17 thing. <- an example of a

[gdal-dev] building gdal-3.3.0-dev with proj free(): invalid pointer

Hi. Been building and rebuilding gdal-3.3.0-dev and arrive at this output: chris@jacie:~$ gdalinfo --version GDAL 3.3.0dev-96fab634a5, released 2021/03/02 free(): invalid pointer Aborted two version of libproj are involved: chris@jacie:~$ ldd /usr/local/bin/gdalinfo | grep libproj libproj.so.22

Re: [gdal-dev] Fema Flood Maps NAV88 - proj4text

Just to close this out, New York New Jersey FEMA advisory Base Flood Elevations are ESPG:3857 > From: sgl...@hotmail.com > To: g...@ir.bbn.com; gdal-dev@lists.osgeo.org > Date: Sat, 2 Feb 2013 11:39:23 -0500 > Subject: Re: [gdal-dev] Fema Flood Maps NAV88 - proj4text > > > The parcels are, o

Re: [gdal-dev] Fema Flood Maps NAV88 - proj4text

The parcels are, of course, horizontal only datum. from the .prj PROJCS["NAD_1983_StatePlane_New_Jersey_FIPS_2900_Feet", GEOGCS["GCS_North_American_1983", DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]], PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]], PROJE

[gdal-dev] Fema Flood Maps NAV88 - proj4text

t is the elevation of one's particular parcel in relation the the flood maps as against the more generalized representation of the flood zone stops about here. thank you for your advice and consideration, Chris English __

[gdal-dev] SetUTM - how to say how far north Python

Hi, Assuming the following: >>> src_ds = gdal.Open('test_3.ter')>>> dst_ds = >>> driver.CreateCopy('test_6.hf2', src_ds, 0)>>> >>> dst_ds.SetGeoTransform([582495,1,0.5,4512717,0.5,-1])0>>> srs = >>> osr.SpatialReference()>>> srs.SetUTM(18,1)0>>> >>> srs.SetWellKnownGeogCS('WGS84')0>>> dst_ds.S

[gdal-dev] Python syntax for Terragen band::SetUnitType()

Hi, What is the proper Python syntax for SetUnitType("m") for Terragen ? >>> type(dst_ds) The dataset (Terragen) exists, and (I think) in order for the MIN/MAXUSERPIXELVALUESto make sense it seems you'd have to SetUnitType() prior to WritingArrayin the same way you'd establish SetGeoTransform()

[gdal-dev] VPF - Failure fetching requested layer OGDI

I know it is there. C:\gisdata\vdu\software\um\DNC16>ogr2ogr a160_danger_a.shp gltp:/vrf/gisdata/vdu/software/um/DNC16/a160 'dang...@obs(*)_area'FAILURE: Couldn't fetch requested layer ''dang...@obs(*)_area'