Hi all,
When I execute an SQL query on a SQLite source, I am observing that the
feature identifiers are changing. This was observed using 1.11.1.
ogrinfo -geom=NO -fid 1227 test2.sqlite
OGRFeature(roads):1227
gml_id (String) = Roads.371c00110746
arc_flag (String) = T
On 2015-11-23 12:00, Even Rouault wrote:
Le lundi 23 novembre 2015 16:48:48, Andre Vautour a écrit :
Right, thanks, I wasn't thinking of that when I wrote my reply.
Guess it makes sense for a closed format such as DWG. Might not make as
much sense to use it for DGN which is more open
DGN v8
on that: In order to build the DWG driver, you or your company,
need to be part of some kind of alliance to be able to download a full version
of the Teigha SDK. AFAIK
From: gdal-dev <gdal-dev-boun...@lists.osgeo.org> on behalf of Andre Vautour
<a
Hi all,
We are using OGRSFDriver::CopyDataSource() to copy a GML data source to a
memory data source on v1.11.x.
We have encountered a problem where one of the feature tags of a particular GML
file we are trying to read is malformed. What we are seeing is that an error
occurs in
previously as the pixel-space window
would have changed.
If you could explain what you meant, I'd be very grateful. Thanks,
carl
Sorry for the confusion and do let me know if you want more clarification,
André
On Tue, Jul 7, 2015 at 7:22 AM, Andre Vautour andre.vaut...@caris.com
The way I see it, the new spec does clear up some big holes like:
1. Being able to specify an unambiguous operation/projection method (by
identifier) for projections instead of loosely relying on the
projection's name (9.3.3)
2. Knowing the units of projection parameters (9.3.4)
On
On 2015-04-28 11:19, Federico wrote:
Hi guys, i'm trying to get a wmts layer but i'm getting an error. I think
that i'm doing something wrong but i don't what's wrong.
URL: http://opencache.statkart.no/gatekeeper/gk/gk.open_wmts
GetCapabilities:
On 2015-04-16 12:07, Even Rouault wrote:
- All formulations that try to expand the definition with
ProjCoordTransGeoKey = CT_Mercator, its projection parameters and GCS
parameters aren't really appropriate, since there's no way of capturing
that its a spherical mercator that must be used.
On 2015-04-16 07:08, Even Rouault wrote:
Le mercredi 15 avril 2015 22:48:45, Even Rouault a écrit :
The way I see it, there are two different ways to model Google Mercator:
1. As a WGS84 datum/ellipsoid with a custom Mercator-based projection
which uses only the semi-major axis, as seems to be
On 2015-04-15 14:59, Even Rouault wrote:
Le mercredi 15 avril 2015 18:21:51, xavier lhomme a écrit :
Dis you try with 102113 or 102100 instead of 3857 ? I had once to use
those code in order to be discovered as 3857 in arcgis. when i created
geotiff with gdal warp/transform.
Xavier,
thanks
On 2015-04-12 19:51, Even Rouault wrote:
Le samedi 11 avril 2015 15:19:48, Brad Hards a écrit :
On Tue, 7 Apr 2015 07:12:20 AM Jukka Rahkonen wrote:
I felt that document somehow heavy to read but it appears in many places
that Mercator variant A is the primary name since October 2010. This
On 2015-04-13 10:42, Even Rouault wrote:
André,
I am not sure I follow what this has to do with the projection name in
WKT. The newer WKT specification (ISO 19162) relies solely on the
identifier to determine which operation method to use to project
coordinates,
Do you know if there's a
On 2015-04-13 11:01, Pepijn Van Eeckhoudt wrote:
I am not sure I follow what this has to do with the projection name
in WKT. The newer WKT specification (ISO 19162) relies solely on the
identifier to determine which operation method to use to project
coordinates, but the older WKT tends to
Did you happen to look at the date on your calendar this morning?
:p
On 2015-04-01 11:17, Daniel Morissette wrote:
Good morning Even,
That sounds like an ambitious world (universe?) domination plan, but
before going too deep into the implementation details, can you comment
on the potential
Hi all,
I was wondering if there is a way to get at the original feature id when
executing an SQL query for the SQLite dialect. Something similar to what
is described in http://www.gdal.org/ogr_sql.html for FID for the OGR
dialect.
That is, is there something equivalent to the following for
On 2014-09-30 17:08, Even Rouault wrote:
Le mardi 30 septembre 2014 20:20:14, Andre Vautour a écrit :
Hi all,
I am trying to use a geometry binary predicate (ST_Intersects) in
ExecuteSQL() with the SQLite dialect and keep getting back an
ST_Intersect function does not exist error back from
Hi all,
I am trying to use a geometry binary predicate (ST_Intersects) in
ExecuteSQL() with the SQLite dialect and keep getting back an
ST_Intersect function does not exist error back from SQLite.
GDAL is built with SpatiaLite (HAVE_SPATIALITE is defined), but I
believe the problem is that
I ran into a problem where a quoted text string in a OGR Style String
gets lost while interacting with it via an OGRStyleTool. Using the same
style string afterwords causes OGRStyleTool::Parse() to fail because the
quote string contained parentheses which would have typically been
ignored
I want to start off by saying a big thanks to Blake for taking his time
to tackle what can only be a very difficult problem.
From what I can observe, the current discussion seems to be around the
boundary of who should be responsible for ensuring thread safety around
the block cache. The core
Hi all,
Is there a way to configure the proxy for opening data through the ECW
protocol with the ECW driver. For WCS/WMS, I know you can use the
GDAL_HTTP_PROXY configuration option, but that doesn't seem to work for ECW.
Would it make sense to have something like the following in the ECW
Is the DataWindow just ignored here?
I am pretty sure the data window is actually interpreted as the tile
extents of the service for the TMS mini driver. You'll notice that
nothing else in the parameters could be used to georeference the tiles.
I agree that window in this case is misleading
Hi all,
I recently updated to GDAL 1.10.1 and I am looking into possibly using
the VRT data source to have a data source with S57 thematic layers (e.g.
skin of the earth, obstructions, etc.) instead of one layer per object
acronym (feature). I have a collection of ENC files, so my current
Hi all,
I am trying to open a coverage from a 1.1x WCS server that has multiple
fields in its range subset. The WCS XML file is at its most basic form:
WCS_GDAL
ServiceURLhttp://www.example.com/wcs/mywcs?/ServiceURL
CoverageNamesomeCoverageIdentifier/CoverageName
Version1.1.1/Version
I am trying to interpret font sizes coming from OGR feature style strings.
I would expect a font size in ground units to be scale-dependent
inasmuch as a label would get smaller when you zoom out and bigger when
you zoom in. I would expect a font size in pts, mm, inches, pixels, etc.
to be
24 matches
Mail list logo
