Sean,
Very cool. One follow up question, do you really need the "with" for
open? Does this not work (and MemoryFile can drop the file descriptor as
soon as it wants to)?
with MemoryFile(open(path_zip_file, 'rb')) as memfile:
with memfile.open('white-gemini-iv.vrt') as dataset:
Thanks for confirming that I was on the right trail, Even! I got it figured
out: I was naively trying to open the /vsizip/vsimem/ file in update mode.
In case you're interested, my new Python usage is like this:
with open(path_zip_file, 'rb') as f:
with MemoryFile(f) as memfile:
with
> On Jan 31, 2017, at 7:46 AM,
> niels.vonfestenberg-packisch@rohde-schwarz.com wrote:
>
> Hi all,
> I would like to transform local cartesian coordinates into longitude and
> latitude. According to all the documentation I could find, I tried doing this
> (in C++, specifying a center fo
On mardi 31 janvier 2017 18:29:48 CET Daniele Romagnoli wrote:
> Hi Even,
> I'm back to this topic and I have a couple of questions.
> - Is it there any libtiff specific version involvement on that?
> - Are all these improvements self contained in GDAL code itself or do them
> require some specific
Hi Even,
I'm back to this topic and I have a couple of questions.
- Is it there any libtiff specific version involvement on that?
- Are all these improvements self contained in GDAL code itself or do them
require some specific libtiff version?
Cheers,
Daniele
On Fri, Dec 16, 2016 at 2:56 PM, Dani
Hi all,
I would like to transform local cartesian coordinates into longitude and
latitude. According to all the documentation I could find, I tried doing
this (in C++, specifying a center for the orthographic projection at 56 N
15 E):
projPJ cSourceProjection = pj_init_plus("+proj=ortho +ellp
On mardi 31 janvier 2017 17:33:23 CET Sean Gillies wrote:
> Hey all,
>
> The tests in
> https://svn.osgeo.org/gdal/branches/1.9/autotest/gcore/vsizip.py show how
> to create a zip archive in memory and create directories and files within
> it. I'm looking for a shortcut.
>
> Given a sequence of b
Hey all,
The tests in
https://svn.osgeo.org/gdal/branches/1.9/autotest/gcore/vsizip.py show how
to create a zip archive in memory and create directories and files within
it. I'm looking for a shortcut.
Given a sequence of bytes representing an existing zip file that contains a
TIFF and a VRT (ref
On mardi 31 janvier 2017 15:29:53 CET Ahmed Tolba wrote:
> Hi Evan,
>
> I have tried to debug,
>poFeatureDefn->GetFieldIndex("gml_id") == 0;
> This returns -1
>
> What does this mean ?
That there's no gml_id field found. Which is expected if you indeed use JSON
ouput.
Only GML
Hi Evan,
I have tried to debug,
poFeatureDefn->GetFieldIndex("gml_id") == 0;
This returns -1
What does this mean ?
From: Even Rouault [mailto:even.roua...@spatialys.com]
Sent: Tuesday, January 31, 2017 3:45 PM
To: Ahmed Tolba
Cc: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] W
On mardi 31 janvier 2017 14:15:38 CET Ahmed Tolba wrote:
> Can you please try with that server ?
> WFS:http://192.168.139.128/cgi-bin/tinyows.exe?SERVICE=WFS&VERSION=1.1.0&out
> putFormat=JSON
This is a non public URL. And outputFormat=JSON could actually be the cause for
issues. You
should try
Thank you, should have looked a bit further...
Benjamin
-Original Message-
From: gdal-dev [mailto:gdal-dev-boun...@lists.osgeo.org] On Behalf Of Rutger
Sent: January-31-17 6:01 AM
To: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] gdal.Rasterize select output type different than Float64
Can you please try with that server ?
WFS:http://192.168.139.128/cgi-bin/tinyows.exe?SERVICE=WFS&VERSION=1.1.0&outputFormat=JSON
From: Even Rouault [mailto:even.roua...@spatialys.com]
Sent: Friday, January 27, 2017 12:22 PM
To: Ahmed Tolba
Cc: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] WFS-T
Related to the attribute index: when using SQL WHERE clauses like
WHERE myfield IN (1, 2, 3) on the integer field, it reports on the last
one only, like if the query was
WHERE myfield = 3
(while there are rows with myfield = 1 and 2 as well...)
This is happening only if usin
> Even,
>
> I tried ogr2ogr -lco RESIZE=YES and indeed the Integer64 field becomes
> Integer, but that changes the original shapefile, I was hoping to use
> the existing shapefile without touching it.
If there are no holes in feature numbering, you could normally reuse the
existing .shp and
.sh
Even Rouault-2 wrote
> Another option is to not use shapefiles and use more powerful alternatives
> like GeoPackage
> or Spatialite.
>
> Even
I wonder how usable and reliable this peculiar attribute index is. Would it
be a big loss to stop supporting it?
-Jukka Rahkonen-
--
View this messag
What is the proper way to use new GDAL on the old shapefile without
modifying it?
Is there a way to explicitly tell GDAL to use that field as Integer and
to make the field indexing work?
I'm not sure if MapInfo indexes support 64 bit integers (probably not),
but the code does not
On mardi 31 janvier 2017 04:01:28 CET andreahmed wrote:
> I get a SQL Expression parsing error
>
> OE_DEBUG << LC << "SQL: " << expr << std::endl;
> _resultSetHandle = OGR_DS_ExecuteSQL( _dsHandle, expr.c_str(),
> _spatialFilter, 0L );
>
> the expr is expr = "SELECT * FROM tows:poi_ais"
I get a SQL Expression parsing error
OE_DEBUG << LC << "SQL: " << expr << std::endl;
_resultSetHandle = OGR_DS_ExecuteSQL( _dsHandle, expr.c_str(),
_spatialFilter, 0L );
the expr is expr = "SELECT * FROM tows:poi_ais"
In the database the table name is poi_ais. The layer is tows. Is
Hey Benjamin,
This is fixed with 2.1.3, see (at the bottom):
https://trac.osgeo.org/gdal/wiki/Release/2.1.3-News
A workaround is shown at:
http://osgeo-org.1560.x6.nabble.com/gdal-RasterizeOptions-output-type-tp5293573p5293575.html
Regards,
Rutger
--
View this message in context:
http://os
20 matches
Mail list logo
