Le mercredi 28 septembre 2011 21:28:26, Even Rouault a écrit :
> Le jeudi 22 septembre 2011 17:48:29, Andy Colson a écrit :
> > Hi List,
> >
> > I'm using ogr2ogr to convert (and reproject) data from shapefile to PG,
> > if I use insert statements the null dates are not a problem, but if I
> > set
Oops, sorry sent message accidentally without last bit of text output,
pls see below ...
On Thu, Sep 29, 2011 at 11:38 AM, Patrick Sunter wrote:
> Hi,
>
> As part of testing GDAL's NetCDF drivers projections, I've been trying
> to gdalwarp a Geotiff file from a UTM projection to Mercator-2SP
> (h
Hi,
As part of testing GDAL's NetCDF drivers projections, I've been trying
to gdalwarp a Geotiff file from a UTM projection to Mercator-2SP
(http://geotiff.maptools.org/proj_list/mercator_2sp.html).
Thinking I should file this as a ticket? But thought I'd post here first.
I've tried 2 approaches
On 9/28/2011 2:28 PM, Even Rouault wrote:
>
> On another layer, regardless of insert/copy, I'm getting:
>
> ERROR: numeric field overflow
> DETAIL: A field with precision 19, scale 11 must round to an absolute
> value less than 10^8.
> CONTEXT: COPY poltwppoly, line 1, column shape_area:
Le mercredi 28 septembre 2011 23:09:01, Andy Colson a écrit :
> Would a 16Meg .zip file, that extracts to 157Meg, be acceptable in Trac?
> I attempted to copy some records out, but it created the new shapefile
> with a type of ftString instead of ftDate.
I'm afraid 16 MB will be too big. Perhaps
Would a 16Meg .zip file, that extracts to 157Meg, be acceptable in Trac?
I attempted to copy some records out, but it created the new shapefile
with a type of ftString instead of ftDate.
-Andy
On 9/28/2011 2:28 PM, Even Rouault wrote:
Le jeudi 22 septembre 2011 17:48:29, Andy Colson a écrit
Le jeudi 22 septembre 2011 17:48:29, Andy Colson a écrit :
> Hi List,
>
> I'm using ogr2ogr to convert (and reproject) data from shapefile to PG,
> if I use insert statements the null dates are not a problem, but if I
> set PG_USE_COPY=YES, then I get errors:
>
> ERROR 1: COPY statement failed.
>
ah ok. well i reckon if the data's a bit unpredictable its gonna be better to
write something that steps through the possible gotchyas.. once its in place
you'l be glad for it.. and it'l likely be quicker than code fixes in gdal. good
luck
-i
-Message d'origine-
De : Andy Colson [mail
Not simply. I am receiving data from many different places, some places
send nice clean data, other's, not so much (all in different projections
which is why I'm trying to find a common ground). I have hundreds of
shapefiles, with many times that of columns, any one of which may have
nulls in
and you don't want to set the nulls to blank text before uploading ? (you could
set them back once they'r up there, as well as perform the reprojection). i've
never tried to use nulls in shapes before. can sqllite be used as an
intermediatry instead ?
-i
-Message d'origine-
De : Andy
They use a slightly older version of shapelib that doesnt quite work
with null's. If I ogr2ogr shapefile -> shapefile (to get it in the
projection I want), then shp2pgsql will fail with fields that are null.
Which, I could to ask them to update, yes. It was a 50/50. Ask gdal or
ask postgis.
is there a reason you don't want to use shp2pgsql ?
not sure if its better for everything but i've used it on occasion when i had a
prob in ogr2ogr
-i
-Message d'origine-
De : gdal-dev-boun...@lists.osgeo.org [mailto:gdal-dev-boun...@lists.osgeo.org]
De la part de Andy Colson
Envoyé
Sorry to keep pestering. Is there a better place I should be seeking
help? Would a $bounty$ help?
-Andy
On 9/22/2011 10:48 AM, Andy Colson wrote:
Hi List,
I'm using ogr2ogr to convert (and reproject) data from shapefile to PG,
if I use insert statements the null dates are not a problem, but
Thanks Matt
my problem is that this operation needs to be performed over a very wide area,
comprised of many images with many water bodies, so it needs to be automatic.
My plan is to write something in python that:
- generates vector polys from original NODATA pixel areas (greater than a given
Hi Matt,
in a bizare coincidence of the world i just asked this yesterday. The tool you
want is gdal_fillnodata, you need gdal with python bindings.
as long as you don't try to use the -si option it works great.. for one pixel
holes it'l be perfect.
-i
De : gdal-dev-boun...@lists.osgeo.org
Hi
I am wanting to fill (interpolate) nodata values in a Geotiff. (derived
from SRTM data). They are small holes, usually just one pixel.
I tried variations on this
gdal_grid -a invdist -of GTiff S34E151.tif S34E151_grid.tif
But it did not work, no error message - just returned the help page.
Hi all again,
I've forgot to ask one thing;
Is there possible to set values of attributes in block?
I've googled a little bit, and some are saying that it works, other ones
that it doesn't.
I've tried to make it work with attribute in layer (same name as the one in
block) but I'm recieving the fo
Hi, I'm re-posting my colleague post because it was not accepted by the
mailing list yet, and it's a kind of urgent. So here it is:
Hi,
I'm working with rawcofe and thank you all for your answers.
We've temporary stoped working on that issue, but it is now again active and
would need some ext
18 matches
Mail list logo
