Hi,
I translated a HDF image:
$ gdalinfo asi-n6250-20020619-v5i.hdf
Driver: HDF4Image/HDF4 Dataset
Files: asi-n6250-20020619-v5i.hdf
Size is 1216, 1792
Coordinate System is `'
Metadata:
valid_range=0, 1
long_name=ASI Ice Concentration, 20020619, res: 6.25000, AMSR-E, ASI Version:
5.5i, miss
I found a work around to the problem - posting here in case someone else
runs into the problem
I changed the initial select * to separate the attributes and cast them
as real
Example: Select cast(LAT2 as real), cast(lon2 as real), cast(confidence
as real), cast(intensity as real), date_time
Greetings,
I’m new to ogr/gdal, so perhaps this is a silly question-regardless:
Using the C/C++ APIs for OGR, is there a way to use either text in a string
(char*, std::string, etc) or a C++ stream object as a data source for OGR?
I have GML documents in string format, and need to store the info
hi,
i wanted to ask qhull to give me the TINs (Triangulated Irregular Networks) of
3D points from Lidar LAS files... can anyone show me the command how to get
this done (by any chance if you have used the qhull tool)?
thanks!
___
gdal-dev mailing li
Ray Joslyn wrote:
Hello,
I have noticed tile artifacts that corespond to the tile sizes when
compressing color images with the PHOTOMETRIC=YCBCR option for JPEG compressed
Tiff images. I do not see this if I use PHOTOMETRIC=RGB. Are there any
options that may prevent this?
Folks,
I follow
Selon Ivan :
I realize I hadn't yet tested with multibyte data types.
I've improved the javadoc of the ReadRaster_Direct and WriteRaster_Direct
methods to mention the byte ordering issue.
> Thanks Daniele. That takes care of the problem.
>
>
> > ---Original Message---
> > From: Daniele
Thanks Daniele. That takes care of the problem.
> ---Original Message---
> From: Daniele Romagnoli
> Subject: Re: [gdal-dev] GDAL-Java: How to write Flot32, Int16?
> Sent: Nov 04 '09 12:36
>
> Hi Ivan,
>
> Try adding this:
> byteBuffer.order(ByteOrder.nativeOrder());
>
> af
Hi Ivan,
Try adding this:
byteBuffer.order(ByteOrder.nativeOrder());
after the allocateDirect and before the asFloatBuffer calls.
That is:
---
ByteBuffer byteBuffer = ByteBuffer.allocateDirect(4 * xsize);
byteBuffer.order(ByteOrder.nativeOrder());
FloatBuffer floatBuf
It seems like I encountered this problem before but I can not find any
information about it now.
If I run a SQ script like the following
Select * from
(Select MIN_LAT - (round((MIN_LAT - LATITUDE) / (MAX_LAT - MIN_LAT) *
1728.497600)) * 0.000579 LAT2,
MAX_LON - (round((LONGITUDE
Hi,
I'm trying to use gdal_rasterize to draw polygons, then draw their borders
in a different color, and can't figure out how to do it. Drawing a polyline
produces no output - and I don't see a way to specify the pixel width.
Drawing a polygon with a hole inside produces a black instead of a
trans
Even,
Thanks for you reply.
I wrote this piece of code to demonstrate what is happening:
{{{
public static void main(String[] args) {
Dataset dataset = null;
Driver driver = null;
Band band = null;
int xsize = 4;
int ysize = 4;
gdal.AllR
Ray Joslyn wrote:
Hello,
I have noticed tile artifacts that corespond to the tile sizes when
compressing color images with the PHOTOMETRIC=YCBCR option for JPEG compressed
Tiff images. I do not see this if I use PHOTOMETRIC=RGB. Are there any
options that may prevent this?
Ray,
What is yo
Hello,
I have noticed tile artifacts that corespond to the tile sizes when
compressing color images with the PHOTOMETRIC=YCBCR option for JPEG compressed
Tiff images. I do not see this if I use PHOTOMETRIC=RGB. Are there any
options that may prevent this?
Thanks
Ray
___
13 matches
Mail list logo