<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Yea no worries. I don’t know of a way but wanted to share what I just went through. Hopefully someone can chime in if they know. </div> <div id="bloop_sign_1397772043598201088" class="bloop_sign"><div style="font-family:helvetica,arial;font-size:13px"><br></div></div> <br><p style="color:#000;">On April 17, 2014 at 3:52:51 PM, georgew (<a href="mailto:gws293@hotmail.com">gws293@hotmail.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>Thank you Jason but what you suggest, e.g. using a number of steps external
<br>to postgis is exactly what I want to avoid. In any case I have no problem
<br>creating the rasters in SAGA then using using raster2pgsql to import them.
<br>But since postgis has an st_asraster function that creates rasters natively
<br>within postgis from geometries, and since I have already imported the shape
<br>files as postgis vector, all I am looking for is a good tutorial to explain
<br>how to use st_asraster to achieve what raster2pgsql does.
<br>
<br>
<br>
<br>--
<br>View this message in context: http://postgis.17.x6.nabble.com/Postgis-raster-tutorial-tp5006124p5006137.html
<br>Sent from the PostGIS - User mailing list archive at Nabble.com.
<br>_______________________________________________
<br>postgis-users mailing list
<br>postgis-users@lists.osgeo.org
<br>http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
<br></div></div></span></blockquote></body></html>
<br>
<p><font face="Arial" size="2">This transmission contains confidential and privileged
information intended solely for the party identified above. If you receive this message in error, you must not use
it or convey it to others. Please destroy it immediately and contact the sender at
(303) 386-3955 or by return e-mail to the sender.</font></p>