[postgis-devel] [PostGIS] #227: [wktraster] Add out-db support in gdal2wktraster.py script
PostGIS
trac at osgeo.org
Fri Dec 18 09:34:51 PST 2009
#227: [wktraster] Add out-db support in gdal2wktraster.py script
---------------------------+------------------------------------------------
Reporter: jorgearevalo | Owner: jorgearevalo
Type: task | Status: new
Priority: high | Milestone: WKTRaster 0.1.6
Component: wktraster | Version: trunk
Resolution: | Keywords:
---------------------------+------------------------------------------------
Comment (by jorgearevalo):
I've implemented this (function wkblify_band):
- bandidx (band number) comes from caller method: wkblify_raster_level.
1-based index
- the path to the external file is the same provided with the option "-r
<raster_name>" when calling the loader
After this, I've commented these lines in rtpostgis.sql.in.c:
-- Verify out_db[[BR]]
-- TODO: Waiting for out-db rasters[[BR]]
--IF ( p_out_db = true ) THEN[[BR]]
-- RAISE EXCEPTION 'TODO: Outside database rasters not
implemented yet';[[BR]]
-- RETURN 'fail';[[BR]]
--END IF;[[BR]]
Once re-compiled, I've correctly loaded a raster with outdb support doing
this. Do you think the approximation is correct? If yes, I'll finish the
out-db raster reading support in GDAL, and I'll test it (this is one of my
GDAL tickets: http://trac.osgeo.org/gdal/ticket/3234
--
Ticket URL: <http://trac.osgeo.org/postgis/ticket/227#comment:8>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.
More information about the postgis-devel
mailing list