Thanks,
This is a very interesting development. I am trying to do a PhD using only open source software (Windows will soon go out the window!). I will take a good look at this post.
Nicolas Cadieux M.Sc.
Les Entreprises Archéotec inc.
8548, rue Saint-Denis Montréal H2P 2H2
Téléphone: 514.381.511
Thanks Even,
My programing skills are very limited (to mapbasic and thankfully python).
Restructuring the code is beyond me but I will try to change the variables and
recompile. What to you recommend the new value be?
I have never done recompiling in anything but MapBasic so any link towa
Sounds like you have a version mismatch. For example, you'll get that message
if you have numpy 1.7x installed and you installed the gdal binaries and
bindings from Christoph Gohlke
(http://www.lfd.uci.edu/~gohlke/pythonlibs/#gdal) which are built against
numpy 1.9x
If you have numpy 1.7x installe
Hi Nicolas,
You might also be interested in a new development discussed over the past
couple of
days on the PDAL list.
See http://lists.osgeo.org/pipermail/pdal/2015-June/000590.html
Hope it helps,
carl
On Fri, Jun 5, 2015 at 4:13 PM, Even Rouault
wrote:
> Le samedi 06 juin 2015 00:18:45, N
Le samedi 06 juin 2015 00:18:45, Nicolas Cadieux a écrit :
> Hi,
> I have been using gdal_grid to interpolate LiDAR data for some time now.
> This would be a typical command:
>
> gdal_grid -l P0344_sol2004_XYZI_MTM8_CGVD28_150529 -txe 348733.0 401135.0
> -tye 5568587.0 5773796.0 -a
> nearest:radi
Hi,
I have been using gdal_grid to interpolate LiDAR data for some time now. This
would be a typical command:
gdal_grid -l P0344_sol2004_XYZI_MTM8_CGVD28_150529 -txe 348733.0 401135.0 -tye
5568587.0 5773796.0 -a nearest:radius1=3.0:radius2=3.0:angle=0.0:nodata=0.0
-outsize 52402.0 205209.0 -o
Even,
That works, thanks.
Roger
On Fri, Jun 5, 2015 at 12:52 AM, Even Rouault
wrote:
> Le vendredi 05 juin 2015 02:19:06, Roger André a écrit :
> > Hi All,
> >
> > I'm having some trouble using ogr2ogr to do batch uploads to a Postgis
> DB.
> > It appears that on tables which don't contain geo
Le mercredi 03 juin 2015 11:13:51, Even Rouault a écrit :
> Hi,
>
> As no points have been raised on the RFC itself (peripheral discussions on
> how to address out-of-range nodata values) :
>
> Motion : I move to adopt RFC 58: Removing Dataset Nodata Value
>
> https://trac.osgeo.org/gdal/wiki/rf
Simon,
> Looking at the code of GDAL 2.0 (but also 1.x), I noticed that the
> OGRGeometry class (and the derived classes) do not respects the Rule of 3
> : there is a destructor and no copy constructor or assignment operator.
Indeed, the Rule of 3 is not currently really implemented in the C++ AP
Hi,
Looking at the code of GDAL 2.0 (but also 1.x), I noticed that the OGRGeometry
class (and the derived classes) do not respects the Rule of 3 : there is a
destructor and no copy constructor or assignment operator. It seems to me that
this may lead to memory leaks on OGRSpatialReference (for
Hi,
As announced, I have prepared a GDAL/OGR 2.0.0 release candidate. This is your
last chance to test before the official release.
Peek up an archive among the following ones (by ascending size):
http://download.osgeo.org/gdal/2.0.0/gdal-2.0.0RC1.tar.xz
http://download.osgeo.org/gdal/2.0.0
Le vendredi 05 juin 2015 02:19:06, Roger André a écrit :
> Hi All,
>
> I'm having some trouble using ogr2ogr to do batch uploads to a Postgis DB.
> It appears that on tables which don't contain geometry, CreateLayer is
> failing and not allowing data to be appended to an existing table. Here is
>
Hi Stefan,
>
> We've finished the GeoCSV spec. and we're almost ready to publish the
> Editable GeoCSV plugin fpr QGIS.
>
> So, I have following enhancement requests for the OGR CSV reader,
> regarding CSVT:
> 1. Accept "WKT" (case insensitive) indicating WKT geometry field.
> 2. Accept "CoordX"
13 matches
Mail list logo
