Opened 16 years ago
Last modified 15 years ago
#34 closed enhancement (fixed)
.prj creation by pgsql2shp — at Initial Version
| Reported by: | dane.springmeyer | Owned by: | robe |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 1.3.6 |
| Component: | postgis | Version: | 1.4 |
| Keywords: | Cc: |
Description
This is a very minor feature request.
It would be great to be able to automatically generate the .prj file needed by many shapefile readers during export from postgis.
I also made a note of this issue on the postgis-users list a while back (http://postgis.refractions.net/pipermail/postgis-users/2007-November/017698.html)
An optional flag for pgsql2shp, say -s 4326, would match the specified srid and pull from cooresponding srtext field.
For any custom projections added that did not have a cooresponding srtext field, a warning could be output by pgsql2shp. The user would then be responsible for filling it in if blank, from spatialrefererence.org or other sources.
I understand that the srtext field was likely not intended to be used this way, so there may be better solutions.
This thread notes (http://postgis.refractions.net/pipermail/postgis-users/2004-October/005958.html) that postgis would benefit from a full fledged WKT parser, but in the case of this feature request, I don't imaging that much parsing would need to be involved to output the srtext during export.
