Chris,
Christopher Barker wrote:
Hi folks,
I have a dataset that is a 4-dimensional array of values: time,x,y,z
We're currently using netcdf to store it, which is well suited to this
kind of data.
However, we also need to get it into a GIS (Arc in this case), and I'm
trying to find a good
Don't know if this is what you are looking for but if those netCDF files
are of a similar type that one can get from the poet site
(http://poet.jpl.nasa.gov/), Mirone has a tool called "Aquamoto" (a tool
original developed to show time stamps of a tsunami propagation models)
that loads those fi
I don't think there is a GIS that does this in a natural way - all you
can do is read in multiple slices. If the order of your axes really is
time, x, y, z then you will have y.n * z.n (time, x) slices (as
bands) when read by GDAL - NetCDF will tend to store dimensions in
reverse order to the natu
>
> From: Duarte Carreira
> Subject: RE: [gdal-dev] Re: ESRI file geodatabase support
> To: Eric Wolf , Peter J Halls
> Cc: "gdal-dev@lists.osgeo.org" , Matt
> Wilkie
>
>
> Well, if SpatiaLite offers some "proper" benefits and disseminates through
> all of the FOSS world, then it may
Well, if SpatiaLite offers some "proper" benefits and disseminates through all
of the FOSS world, then it may get a strong enough push even for ESRI to pick
it up. It happened before... (kml?)
If SL would:
1) Be as fast as shapefile in production settings, desktop and webgis
2) Offe
Hi folks,
I have a dataset that is a 4-dimensional array of values: time,x,y,z
We're currently using netcdf to store it, which is well suited to this
kind of data.
However, we also need to get it into a GIS (Arc in this case), and I'm
trying to find a good way to do that.
Both Arc and gdal
On Thu, Jun 17, 2010 at 1:40 PM, Alexander Bruy
wrote:
> Hi,
>
> I use next code to translate real coordinates (lat/lon) to the pixel/line
> coordinates
>
> def mapToPixel( mX, mY, geoTransform ):
> if geoTransform[ 2 ] + geoTransform[ 4 ] == 0:
> pX = ( mX - geoTransform[ 0 ] ) / geoTransform
Hi,
I use next code to translate real coordinates (lat/lon) to the pixel/line
coordinates
def mapToPixel( mX, mY, geoTransform ):
if geoTransform[ 2 ] + geoTransform[ 4 ] == 0:
pX = ( mX - geoTransform[ 0 ] ) / geoTransform[ 1 ]
pY = ( mY - geoTransform[ 3 ] ) / geoTransform[ 5 ]
else
Matt's chicken-and-egg point seems dead-on. Except that Jack Dangermond
abhors a vacuum and ESRI has been focused on higher-order issues than file
formats. They are trying to provide topological constraints in the database
(or file) and things like geometric networks (which are really just a set of
Frank,
I have increased the cache as you suggested using GDALSetCacheMax
and it produced a performance gain. Thanks.
I think I can improve more acting on the virtual datataset that I use to
adapt the image to the paper size.
I have to look into the tms driver in order to understand how it
On Thu, Jun 17, 2010 at 11:03 AM, Zermeno, Robert J CIV NAVAIR,
472100D wrote:
>
> GDALBeginAsyncReader(fileDataset,
> 0, 0, //Start at top-left position
> ImageWidth, ImageHeight, //Note, I am requesting whole image.
> JPIP_Buffer,
> Bu
Hi Peter,
Thank you very much!
With your help,I fixed this problem!
The reason is that my GDAL_DATA environment variable is not true.
I set it first by the GDAL
FAQ(http://trac.osgeo.org/gdal/wiki/FAQInstallationAndBuilding#HowtosetGDAL_DATAvariable)
which tells me :$ export GDAL_DATA=/usr/local/s
Thanks Frank!
It made a lot of sense. My last comment concerning this function is how would
you be able to
Acquire a smaller image size of a larger image using GDALBeginAsyncReader() for
RGB images?
I can get it to work for Grayscale, but using the same parameters for RGB gives
me an AccessV
On Thu, Jun 17, 2010 at 5:39 AM, canduc17 wrote:
>
> I saw that this thread is quite old...it is anything changed with the last
> version of GDAL?
>
> Is the triangulation not implemented yet?
Hi,
The situation is still the same. There is no transformer based
on a triangulated mesh from GCPs.
Hi Peter,
Thank you so so much for your response!
I still believe there is something wrong with my GDAL compiling or environment
variable.
I use ogrinfo(one of GDAL/OGR utilities) in GDAL on my Linux & Windows OS, the
result is the same(wrong):
->Ogrinfo -ro -al -q US5TX51M.000 |more
ERROR 1:Inva
Hi,
it is possible to set the tile's dimension in gdal2tiles.py?
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/gdal-dev
This is a problem which regards all the gdal versions and is about the Python
GDAL bindings.
It seems to be impossible to setup PixelFunctionType and SourceTransferType
in VRTDerivedRasterBand from Python Gdal.
This is an example using IPython:
In [20]: vrtdriver = gdal.GetDriverByName('VRT')
In
I saw that this thread is quite old...it is anything changed with the last
version of GDAL?
Is the triangulation not implemented yet?
Thanks in advance.
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/Warp-info-tp2031316p5190183.html
Sent from the GDAL - Dev mailing lis
I have implemented in C++ an example of color table applied to a band, taking
as reference the python script reported in this thread:
Ludwig wrote:
>
> colorTable = gdal.ColorTable()
> greentransparent = (0, 255, 0, 0)
> blue = (0,0, 255,255)
> colorTable.SetColorEntry(0, greentransparent)
> col
Randy,
I think you need to fiddle with the preprocessor definition
S57_BUILTIN_CLASSES during compilation. (
http://trac.osgeo.org/gdal/browser/trunk/gdal/ogr/ogrsf_frmts/s57/s57classregistrar.cpp
).
I didn't work with S-57 format, so I don't know any more than you.
On Thu, Jun 17, 2010 at 1:51
Hi Peter,
Thanks for your response!
>
> I do not use s57 data, however I have written a number of programs which
> use
> OGR_FD_GetName ... and it has always returned the feature name, if set, or
> null
> for me. Feature, as opposed to Layer, names seem quite uncommon, however;
> althoug
Randy,
I do not use s57 data, however I have written a number of programs which use
OGR_FD_GetName ... and it has always returned the feature name, if set, or null
for me. Feature, as opposed to Layer, names seem quite uncommon, however;
although I generally set feature names when creating
Hi Chaitanya,
Thanks for your quick response!
I use this function in parse a s57 file(*.000). In this format file,I
think the layer-name in OGR should be like this:
berths,bridge,canals...
which to some extend,is as same as a feature-name. But now I'm not sure
whether I understand this concept righ
Another way to achieve interoperability is via a DBMS for which there is an SDE
implementation, although this may not be appropriate for Matt Wilkie's
requirements. It may not be always as easy as with shapefiles but it does not
have the limitations. Having said that, in our Oracle environment
24 matches
Mail list logo
