Hi Dan,<div><br></div><div>It's a bit difficult to recall exactly what was introduced in which version of PostGIS.</div><div><br></div><div>The "smart" function uses the "ST_startpoint" and "ST_endpoint" function, which had some issues in certain versions of PostGIS as far as I remember. </div>
<div>This problem also occurred in the workshop, see: <a href="http://pgrouting.postlbs.org/wiki/WorkshopFOSS4G2008/ch08">http://pgrouting.postlbs.org/wiki/WorkshopFOSS4G2008/ch08</a> (well, it's not a problem of PostgreSQL as written there, but it's a problem of PostGIS. I just can't tell now which version it was).</div>
<div><br></div><div>I agree that the target should be 1.3+. We could think about some compatibility table for wrapper functions, if many of them will make use of new functions.</div><div>If there is a larger interest in publishing new wrappers (hopefully many from the community), we might have to think about a better way to organize them. </div>
<div><br></div><div>Daniel</div><div><br></div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div><br><br><div class="gmail_quote">2010/7/27 Dan Putler <span dir="ltr"><<a href="mailto:putler@yahoo.com">putler@yahoo.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">In adding to the core_sp_smart functions from the sandbox, I want to do things to maintain the level of version compatibility that pgRouting wants to maintain (so I've done in all the calls to functions introduced in version 1.5+). I assume that the target is PostGIS 1.3+, but want to make sure.<br>
<br>
Dan<br>
<br>
<br>
<br>
_______________________________________________<br>
Pgrouting-users mailing list<br>
<a href="mailto:Pgrouting-users@lists.osgeo.org">Pgrouting-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/pgrouting-users</a><br>
</blockquote></div><br></div>