A question about OGRPoint.
There are copy constructor, assignment, and clone. Shouldn't these do
basically the same thing but with a bit different syntax? By the same
thing I mean that the new point or assignee should have the same flags
(is_empty, is_3D, is_measured), same coordinate values,
28.01.2016, 16:46, Even Rouault kirjoitti:
"Currently hacks such as nCoordDimension == -2 are used to denote empty
geometries" --> to be pedantic, this is only true for point. Other geometry
types don't need that since they are containers/vectors and if the
container/vector size is 0, it means em
Thanks for your reply Even. Very helpful!
>I'm not a JS programmer, nevertheless I tried to understand
https://github.com/koopjs/GeoXForm/blob/master/src/lib/vrt.js, and you seem
to
group GeoJSON Feature objects by batch of 5000 (*) , put them in a temp
.json
file, and assemble all the JSon files
Hi,
I'm having a look at the following all related issues :
https://trac.osgeo.org/postgis/ticket/1940
https://trac.osgeo.org/proj/ticket/185
https://trac.osgeo.org/gdal/ticket/4762
related to EPSG:2065 support, ie "S-JTSK (Ferro) / Krovak". There's an issue
about the datum shift used, but that'
Here is a link for the PDF
https://drive.google.com/file/d/0B4shTM1bPS5TaVZ2OWxxR0MtM2s/view?usp=sharing
and the gdalinfo is as follows, Does this projection is supported by the
PDF driver.
Driver: PDF/Geospatial PDF
Files:Plant_GIS_ANSI_D_View4_Treatment_50Scale.pdf
Size is 5100, 3300
Coordinate
Le jeudi 28 janvier 2016 15:09:06, Ari Jolma a écrit :
> Folks, especially the PSC,
>
> I'd like to call for discussion about RFC 61: Adding support for
> measures in geometries.
Thanks for leading the effort.
>
> Measures (M) are a sort of fourth coordinate for points in geometries. A
> typica
Folks, especially the PSC,
I'd like to call for discussion about RFC 61: Adding support for
measures in geometries.
Measures (M) are a sort of fourth coordinate for points in geometries. A
typical use of measures is for distance from origin in line strings that
represent roads but they can b
Le jeudi 28 janvier 2016 10:48:02, Jukka Rahkonen a écrit :
> Even Rouault spatialys.com> writes:
> > I downloaded it and don't see any issue. But it looks like it is the one
> > written by GDAL
>
> Oops, well, it is good to have reference data :) This is from OpenJUMP
> http://latuviitta.org/dow
Even Rouault spatialys.com> writes:
> I downloaded it and don't see any issue. But it looks like it is the one
> written by GDAL
Oops, well, it is good to have reference data :) This is from OpenJUMP
http://latuviitta.org/downloads/KKK.zip
-Jukka-
Le jeudi 28 janvier 2016 10:33:49, Jukka Rahkonen a écrit :
> Even Rouault spatialys.com> writes:
> > Hi Jukka,
> >
> > could you provide the file or the source file used to generate it ? In
>
> theory,
>
> > the driver should be able to process any valid file. The checks are meant
> > to detec
Even Rouault spatialys.com> writes:
> Hi Jukka,
>
> could you provide the file or the source file used to generate it ? In
theory,
> the driver should be able to process any valid file. The checks are meant to
> detect things like
> that could result in denial of service, but there must be s
Even,
agreed. I guess I have become rather too embedded in Oracle these
days: any SQL method that supports blobs should provide the same. The
bigger issue would be for those methods that cannot support blobs, arrays,
etc, where this wkt would be pretty much the only viable alternative.
Bes
Le jeudi 28 janvier 2016 09:58:06, Peter Halls a écrit :
> Ari, Even,
>
> one potential solution where M data are present but not supported by
> the Geometry type would be to add M as a user defined attribute, as is done
> for Z values in some drivers / packages. This preserves both the geo
Ari, Even,
one potential solution where M data are present but not supported by
the Geometry type would be to add M as a user defined attribute, as is done
for Z values in some drivers / packages. This preserves both the geometry
integrity and the data. Should the user wish to 'upgrade' th
Le jeudi 28 janvier 2016 09:07:20, Christian Urich a écrit :
> Hi,
>
> I’m still running an older version of GDAL/OGR (1.11.3) and would like to
> access a binary field in python.
>
> It seems that GetFieldAsBinary is only available in version > 2.0 so I
> tried to access the data using GetFieldA
Le jeudi 28 janvier 2016 09:23:47, Ari Jolma a écrit :
> 28.01.2016, 00:05, Even Rouault kirjoitti:
>
> Thanks for the pointer to the geometry codes in SF Common Architecture,
> somehow I overlooked it.
>
> > my point with adding the new capabilities was that drivers that
> > wouldn't advertize t
28.01.2016, 00:05, Even Rouault kirjoitti:
Thanks for the pointer to the geometry codes in SF Common Architecture,
somehow I overlooked it.
my point with adding the new capabilities was that drivers that
wouldn't advertize the M capabilities would never see a M or ZM
geometry / geometry type
Hi,
I’m still running an older version of GDAL/OGR (1.11.3) and would like to
access a binary field in python.
It seems that GetFieldAsBinary is only available in version > 2.0 so I tried to
access the data using GetFieldAsString. However the returned hex is cut off
after 75 characters. Is th
18 matches
Mail list logo
