Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Andrew Bell
@abellgithub
@dbcesar : Let me know exactly what you're doing and I can try to help.
Diego Cesar
@dbcesar
Thanks @abellgithub. After your comment I insisted a bit more and could link it with a static library after recompiling the static library with -fPIC flag. Now I can use my filter again ;)
Andrew Bell
@abellgithub
@dbcesar : Glad you got it figured out.
Weston Renoud
@wrenoud
@abellgithub thanks for the comments on my pull request. Still learning pdal. Thought I had a good contribution there. The failing test illustrated the issues you mentioned.
Howard Butler
@hobu
I was excited you sped LAS up 30% ;)
Weston Renoud
@wrenoud
What is the difference between PointTable::metadata() and PointTable::privateMetadata(...) ? Private appears to be a secondary metadata tree, why should I use one or the other?
Andrew Bell
@abellgithub
You should use PointTable::metadata(), generally speaking. privateMetadata() is used to shuttle some internal data between stage processing. I can answer better if you explain your specific use case.
Weston Renoud
@wrenoud
My use for metadata is to communicate between my reader and writer. I'm making a list of files and putting an originId on the files to map them back to their source.
Diego Cesar
@dbcesar

Hello all, I'm having problems to instantiate PDAL on my code, it always goes to segmentation fault. Investigating further, I tried to run it from a json file and I found out a interesting behavior: my filter is only visible to pdal --drivers when I'm at the installation folder. For instance:

<base_dir>$ pdal --drivers - pdal doesn't see my filder
<base_dir>/install/$ pdal --drivers my filter appears
<base_dir>/install/test$ pdal --drivers my filter appears

My filter is located in <base_dir>/install/lib/libpdal_plugin_filter_myfilter.so

Starting my program from the install folder seems to skip the segfault

Is there any environment variable that I should set and I'm missing? Thanks

Andrew Bell
@abellgithub
@dbcesar : You're probably looking for PDAL_DRIVER_PATH. See question 2 here: https://pdal.io/faq.html
Diego Cesar
@dbcesar
@abellgithub, this was exactly what I was looking for. Many thanks, I completely overlooked the "faq" area.
Guilhem
@gui2dev
Hello everyone, I was wondering if there was a particular reason why Dimension::EdgeOfFlightLine was not part of the dimensions outputed by the readers.rxp as it seems possible to get the info by using the virtual void on_line_start_up(const line_start_up< iterator_type > & arg); function from class basic_packets. This could be useful to isolate scan lines.
In the mean time, there also could be some sort of splitting filter that could separate the scan lines.
Howard Butler
@hobu
@gui2dev we would merge a pull request that implemented.
the RXP driver was a quick attempt, not a full-featured implementation
Guilhem
@gui2dev
@hobu thanks for you answer. I'll work on a PR then.
Guilhem
@gui2dev

@gui2dev we would merge a pull request that implemented.

#2724

Andrew Bell
@abellgithub
Thanks for these.
Guilhem
@gui2dev
You're welcome. I'm using PDAL since a while now, it was time to make a contribution
Patrick Sapinski
@drkow_gitlab
Hi all, I am using pdal info --metadata on a las file and getting the following error: "(pdal info readers.las Error) GDAL failure (4) Unable to open EPSG support file gcs.csv. Try setting the GDAL_DATA environment variable to point to the directory containing EPSG csv files.", I'm using the latest pdal from conda which requires gdal 3.0.1, which no longer ships the gcs.csv. Is this a known issue?
Howard Butler
@hobu
can you post the file?
Patrick Sapinski
@drkow_gitlab
sure
Howard Butler
@hobu
try printing your GDAL_DATA environment variable.
maybe the conda environment is hosed up somehow
Patrick Sapinski
@drkow_gitlab
GDAL_DATA is set correctly, gdal 3.0.1 does not ship with gcs.csv
it works if I sub in GDAL_DATA from an older version
Howard Butler
@hobu
hmm...
which platform? windows?
Patrick Sapinski
@drkow_gitlab
yes
Howard Butler
@hobu
conda update --all brings in PROJ 6.2, GDAL 3, and PDAL 2.0.1?
Patrick Sapinski
@drkow_gitlab
I've uploaded the file here: https://filebin.net/3vqodsn3t65uldd2
pdal 2.0.1 py37h12372d9_5 conda-forge
libgdal 3.0.1 h938bd8b_8 conda-forge
proj4 6.1.1 hc2d0af5_1 conda-forge
hobu @hobu grumbles
Howard Butler
@hobu
looks right
Patrick Sapinski
@drkow_gitlab
from the GDAL release notes:
Removed installed files
Removal of resource files related to EPSG and ESRI CRS databases: compdcs.csv, coordinate_axis.csv, datum_shift.csv, ellipsoid.csv, esri_epsg.wkt, esri_extra.wkt, esri_Wisconsin_extra.wkt, gcs.csv, gcs.override.csv, gdal_datum.csv, geoccs.csv, pcs.csv, pcs.override.csv, prime_meridian.csv, projop_wparm.csv, unit_of_measure.csv, vertcs.csv, vertcs.override.csv
Howard Butler
@hobu
yeah, I don't know what's spitting out that error
pdal info --metadata c:\Users\hobu\Downloads\1km173300465402017LLAKEERIE.laz works for me with a clean environment on windows
Patrick Sapinski
@drkow_gitlab
cool thanks, I will rebuild my windows env, something must be interfering with the conda env
Howard Butler
@hobu
try a fresh environment, and if you still have problems let us know
Patrick Sapinski
@drkow_gitlab
oh, it was entirely my fault, I hardcoded an older PDAL binary and was calling that. With the correct PDAL binary I still receive an error: (pdal info readers.las Error) GDAL failure (1) PROJ: proj_create_from_database: crs not found
not sure what it means, it doesn't interfere with what I'm doing
Patrick Sapinski
@drkow_gitlab
(probably related to the vertical crs in that file, I think they used the wrong EPSG code)
Howard Butler
@hobu

PROJ: proj_create_from_database: crs not found

yes, we need to clean some of that up by binding PROJ's logs I think

vvmruder
@vvmruder
Hi together, I have little problem while building EPT and maybe someone here can help me:
Using pdal 2.0.1 and entwine 2.1.0 to produce EPT out of LAZ file I run into the problem that my offset is not recognized by the entwine build.
I can see the offset correctly set and delivered by pdal info
Should I file an Issue to provide full outputs?
vvmruder
@vvmruder
Ok... I opened an issue to provide complete information.