No, the problem is baked into PostGIS. http://trac.osgeo.org/postgis/ticket/269
Which invalidates my earlier "it just works!" finding for mapserver+geography. Great. http://blog.cleverelephant.ca/2009/11/geography-and-mapserver.html Or perhaps there's something about the earlier version of Mapserver you have that is interacting in a different way than the version I tested, since my blog post is from after the change was committed. Anyhow, you can work around it by defining explicitly casted versions of the functions you are missing: create function force_2d(geography) returns geometry as 'select force_2d(geometry($1))' language 'sql' immutable strict; P. On Tue, Mar 23, 2010 at 10:56 AM, Paul Ramsey <[email protected]> wrote: > I wonder if you upgraded from an older PostGIS and the upgrade did not > include the geog->geom casts. What should happen (and what did happen > when I tested Mapserver/geog support) was that where geog functions > weren't defined, the casting behavior made things "work right". > > P. > > On Tue, Mar 23, 2010 at 12:37 AM, BrainDrain <[email protected]> wrote: >> >> force_2d(GEOGRAPHY)? >> -- >> View this message in context: >> http://n2.nabble.com/Cannot-get-a-PostGIS-layer-to-render-in-Mapserver-tp4776199p4782840.html >> Sent from the Mapserver - User mailing list archive at Nabble.com. >> _______________________________________________ >> mapserver-users mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/mapserver-users >> > _______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
