[gdal-dev] Ignore geometry_columns table in VRT

[Brent Fraser]

Tyler,

   So using

<GeometryField encoding='WKT' field='myWKT'/>

in the VRT doesn't work when used with Mapserver?

Best Regards,
Brent Fraser

On 12/31/2012 2:04 PM, Tyler Mitchell wrote:
> On 2012-12-31, at 12:17 PM, Stephen Woodbridge wrote:
>>> Just from code looking, I see that the geometry_columns table is queried from
>>> OGRIngresLayer::FetchSRSId(OGRFeatureDefn *poDefn), which is called by
>>> OGRIngresTableLayer::ReadTableDefinition(). There's no way (apart changing the
>>> code of course!) to disable that query. But I'm not clear why a failure of it
>>> would cause MapServer to misbehave if ogrinfo works.
>> I think Mapserver checks this to see if it needs to reproject the data. You might be able to get around it by adding or removing "using srid xxxx" clause from the sql. Basically you want to trick mapserver into thinking that it does not need to do a reprojection then it might not make the check that is failing. Mind you this is only my intuition, I have not looked at the code.
> Thanks guys, I'll give it a whirl.  Obviously I need to tweak our Ingres driver so it can work better too :)
> The weirdest part was having different behaviour between points/lines and the polygons.. but I've found a workaround for now - just used a spatially enabled db instead heh.
>
> Tyler
> _______________________________________________
> gdal-dev mailing list
> gdal-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/gdal-dev
>