Perfect! The double project fits my needs exactly.
Robb
On 11/18/13 7:49 PM, Even Rouault wrote:
Le lundi 18 novembre 2013 20:29:07, Robb K. Wright a écrit :
I haven't been able to get either -wrapdateline or -datelineoffset to
alter the coords. As far as I can figure out, the
Frank,
From what I read, this wouldnt solve our problem since GDAL is using the
same huge static library that we do.
In fact, it would be worst since we add GDAL memory requirement on the top
of ODA.
Any other solution you may think of ?
Thank you.
MARTIN PINEAULT
Vice-President,
All,
Dan Little and myself would like to put forward an RFC proposing -xml and -json
output support for both ogrinfo and gdalinfo. No changes are proposed to the
current text format (which would continue to be the default output format), but
having JSON and XML available would greatly ease the
On 19 November 2013 16:42, Howard Butler how...@hobu.co wrote:
All,
Dan Little and myself would like to put forward an RFC proposing -xml and
-json output support for both ogrinfo and gdalinfo. No changes are proposed
to the current text format (which would continue to be the default output
On Nov 19, 2013, at 10:49 AM, Mateusz Loskot mate...@loskot.net wrote:
On 19 November 2013 16:42, Howard Butler how...@hobu.co wrote:
All,
Dan Little and myself would like to put forward an RFC proposing -xml and
-json output support for both ogrinfo and gdalinfo. No changes are proposed
On 19 November 2013 17:00, Howard Butler how...@hobu.co wrote:
On Nov 19, 2013, at 10:49 AM, Mateusz Loskot mate...@loskot.net wrote:
On 19 November 2013 16:42, Howard Butler how...@hobu.co wrote:
All,
Dan Little and myself would like to put forward an RFC proposing -xml and
-json output
On Nov 19, 2013, at 11:03 AM, Mateusz Loskot mate...@loskot.net wrote:
You don't parse the output of gdalinfo --format, do you? :P
[1] http://lists.osgeo.org/pipermail/gdal-dev/2013-January/035117.html
I don't, but I fully expect that are there are folks who have, simply due to
not
This would be a handy addition. It would be helpful, to add to the RFC, sample
XML output.
From: gdal-dev-boun...@lists.osgeo.org on behalf of Mateusz Loskot
Sent: Tue 19-Nov-13 12:03
To: Howard Butler
Cc: gdal-dev@lists.osgeo.org dev
Subject: Re: [gdal-dev]
You might think of adding json/xml output also to gdalsrsinfo, it should
not be much work.
For example, if you have a srs node output by gdalsrsinfo, you could have
the same (and only) node in gdalsrsinfo. Also consider that there are
various output formats for srs (mostly in gdalsrsinfo, but
I suggest loading it into Postgis use the ST_ShiftLongitude() function - this
was written specifically to enable 0-360 +-180 conversions.
It may be that your data with longitudes -180 fails with this too, but it is
the closest I know of...
Otherwise you could perhaps script something up with
Howard,
I was a bit surprised that the RFC doesn't actually define the format. I
gather we are supposed to deduce it from the modified ogrinfo code?
On the GDAL side, rather than have gdalinfo support some secondary
reporting format, I *feel* it would be better to just have a method on a
FWIW I like the idea, but as others have pointed out some thinking needs
to be put into the json xml output formats.
Daniel
On 13-11-19 11:42 AM, Howard Butler wrote:
All,
Dan Little and myself would like to put forward an RFC proposing -xml and -json
output support for both ogrinfo and
I'm not sure as to the purposed utility of the gdalinfo -vrt conversion
approach. It may very well be valid, I spend most of my time with vector data
and can't take a position one way or the other. Even so, I think having a
script friendly output format for ogrinfo is very useful. When
Le mardi 19 novembre 2013 17:42:32, Howard Butler a écrit :
All,
Dan Little and myself would like to put forward an RFC proposing -xml and
-json output support for both ogrinfo and gdalinfo. No changes are
proposed to the current text format (which would continue to be the
default output
Antii,
Thank you for the testing. It looks like Arc/GIS works while FME and
Intergraph don't.
That file had both StdParallel1 and ScaleAtNatOrigin defined.
I've uploaded two new files. This one has only StdParallel1 defined with
no ScaleAtNatOrigin.
On Nov 19, 2013, at 2:01 PM, Even Rouault even.roua...@mines-paris.org wrote:
Certainly a proposal that would please people that don't want to study GDAL
or
OGR API ;-)
Hehe, yeah. Hipster enablement.
- I saw on IRC that you didn't anticipate to make that capability as an API
call but
16 matches
Mail list logo
