[postgis-devel] Postgis issue suggestions for OSGeo sprint?

[Jeff Adams]

Let me be a little more specific.  I was browsing the trac tickets and
noticed there are several old (1-2 years) ones around shp2pgsql. Like these:

https://trac.osgeo.org/postgis/ticket/67
https://trac.osgeo.org/postgis/ticket/110
https://trac.osgeo.org/postgis/ticket/123
https://trac.osgeo.org/postgis/ticket/229
https://trac.osgeo.org/postgis/ticket/357
https://trac.osgeo.org/postgis/ticket/358
https://trac.osgeo.org/postgis/ticket/393
https://trac.osgeo.org/postgis/ticket/398

Does shp2pgsql just not get a lot of love?  Or is there a high level plan or
architectural reason not to do these tickets?  It seems like the kind of
thing I could sit down with and knock out a few patches next week.

Thanks,
Jeff

On Mon, Mar 7, 2011 at 1:28 PM, Jeff Adams <jadams at azavea.com> wrote:

> I'm planning on attending the OSGeo code sprint next week and hopefully
> contributing to PostGIS again this year.  I was wondering if anyone had
> particular suggestions for issues that would be good to address during the
> sprint?  The bug I was thinking of working on has already been fixed ;-).
>
> Thanks,
> Jeff
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20110308/15d25953/attachment.html>