On Jul 28, 2009, at 8:44 PM, Frank Warmerdam wrote:
Brian Hamlin wrote:
its SegFaulting atgcore/mask.py mask_5
http://paste.debian.net/42924/
Brian,
I'm not seeing that problem here. This this just happen to you
recently
after things were working? Are you using an external system li
agnes123 wrote:
Dear all,
i have one question on the default pixel size in gdalwarp.
In gdalwarp, we can use -tr to determine output pixel size in x and y
direction, however, if i omit the argument -tr , gdal will have a default
pixel size value which is in target projection units.
For ex
patsv wrote:
Hi, I am having some problems with finding information about the size of
the map without the borders in the BSB dataset.
Is this information available or should I use the GCP points.
Patrik,
I am not sure of a way to identify what is the map collar in a BSB file.
It may be that
Jorge Arévalo wrote:
Hello,
Here, the report:
http://www.gis4free.org/blog/2009/07/26/gsoc-09-weekly-report-9-1707-2407/
And here, the project page: http://trac.osgeo.org/gdal/wiki/WKTRasterDriver
Jorge,
The progress looks good. You mentioned adding overviews tables as
subdatasets of the gen
Brian Hamlin wrote:
its SegFaulting atgcore/mask.py mask_5
http://paste.debian.net/42924/
Brian,
I'm not seeing that problem here. This this just happen to you recently
after things were working? Are you using an external system libtiff? If
so, the problem may be that the test expose
its SegFaulting atgcore/mask.py mask_5
http://paste.debian.net/42924/
==
Brian Hamlin
ISDE5 Steering Committee
Planetwork.net
OSGeo California Chapter
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/g
>> In future a person or program using data defined as NAD83(CSRS) will
>> reasonably expect sub-meter datum accuracy, for that is the purpose of
>> the datum. if this is not the case, it should not call itself such.
>
> The accuracy of any data is irrelevant to the projection it's in though. I
> c
On Wed, Jul 29, 2009 at 9:48 AM, Matt Wilkie wrote:
> Hi Robert, thank you for contributing your insight, it helps!
>
> > cs2cs -v is quite clear about what it's doing, OGR not so much.
> >
> > Using the "straight" Proj EPSG defs on my system:
> > $ cs2cs -v +init=epsg:3579 +to +init=epsg:4617
>
Hi Robert, thank you for contributing your insight, it helps!
> cs2cs -v is quite clear about what it's doing, OGR not so much.
>
> Using the "straight" Proj EPSG defs on my system:
> $ cs2cs -v +init=epsg:3579 +to +init=epsg:4617
...
> No datum transform will happen (ellipses match, and +towgs8
On Wed, Jul 29, 2009 at 5:25 AM, Matt Wilkie wrote:
>
> Let's see if I have this straight then: if I specify -t_srs epsg:4617 and
> not
> +nadgrid, no datum transformation occurs, even though the output .prj file
> says it has?
If your projection definition in Proj4/OGR has a datum defined it w
Let's see if I have this straight then: if I specify -t_srs epsg:4617 and not
+nadgrid, no datum transformation occurs, even though the output .prj file
says it has?
-matt
Francesco P. Lovergine wrote:
>
> On Fri, Jul 24, 2009 at 09:09:27AM -0700, Matt Wilkie wrote:
>>
>> Now back to GDAL and
Hi,
Can google earth skin format be converted by GDAL to be used within
MapServer?
Thanks,
John J. Mitchell
--
John J. Mitchell
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
Markus Reinhold wrote:
Hej again,
thank you for the suggestions.
Normally this is accomplished as a side effect of running gdal16.bat to
switch to the GDAL 1.6 environment. If you look at
osgeo4w\bin\gdal16.bat
you will see it does:
SET PYTHONPATH=%OSGEO4W_ROOT%\apps\gdal-16\pymod;%PYTHON
Hi, I am having some problems with finding information about the size of the
map without the borders in the BSB dataset.
Is this information available or should I use the GCP points.
Regards
Patrik Svensson
___
gdal-dev mailing list
gdal-d
Dear all,
i have one question on the default pixel size in gdalwarp.
In gdalwarp, we can use -tr to determine output pixel size in x and y
direction, however, if i omit the argument -tr , gdal will have a default
pixel size value which is in target projection units.
For example, if the orgin
Hej again,
thank you for the suggestions.
Normally this is accomplished as a side effect of running gdal16.bat to
switch to the GDAL 1.6 environment. If you look at osgeo4w\bin\gdal16.bat
you will see it does:
SET PYTHONPATH=%OSGEO4W_ROOT%\apps\gdal-16\pymod;%PYTHONPATH%
As a matter of fa
16 matches
Mail list logo
