[gdal-dev] (no subject)

2013-10-06 Thread user gdal
Friends, I sent this mail on Friday. Request for a remedy. If someone can send a built-in project (needn't be with a high end code) using MFC in VC++ 2008 in a Win Zip or RAR, it will be even better. The error (pl. see No. 8) I got is f:\sw\GDALexperiment\GDALexperiment\header\cpl_port.h: fatal e

Re: [gdal-dev] Call for discussion for "RFC 42: OGR Layer laundered field lookup"

2013-10-06 Thread Tamas Szekeres
2013/10/6 Even Rouault > > My rationale was that we have already a few methods that take an approx > flag > (e.g. GetFeatureCount(), CreateField() ), but I don't feel very strongly > for > one way or the other one. > > Even, Yes it's not a significant question indeed. I like Jürgen's original ve

Re: [gdal-dev] Call for discussion for "RFC 42: OGR Layer laundered field lookup"

2013-10-06 Thread Tamas Szekeres
2013/10/6 Jürgen E. > > int iDstField = bExactFieldNameMatch? > poDstFDefn->GetFieldIndex(poSrcFieldDefn->GetNameRef()) : > poDstLayer->FindFieldIndex(poSrcFieldDefn->GetNameRef()); > > Ah yes, this is what I wanted to say. No additional method would be required. Tamas __

Re: [gdal-dev] Call for discussion for "RFC 42: OGR Layer laundered field lookup"

2013-10-06 Thread Even Rouault
Le dimanche 06 octobre 2013 22:21:52, Tamas Szekeres a écrit : > Hi Jürgen, > > The commit you're referring to, doesn't seem contain the handling of the > bExactMatch parameter at the driver. At the moment I consider this a bit > redundant if calling OGRLayer::FindFieldIndex with bExactMatch = TRU

Re: [gdal-dev] Call for discussion for "RFC 42: OGR Layer laundered field lookup"

2013-10-06 Thread Jürgen E . Fischer
Hi Tamas, On Sun, 06. Oct 2013 at 22:21:52 +0200, Tamas Szekeres wrote: > The commit you're referring to, doesn't seem contain the handling of the > bExactMatch parameter at the driver. At the moment I consider this a bit > redundant if calling OGRLayer::FindFieldIndex with bExactMatch = TRUE doe

Re: [gdal-dev] Call for discussion for "RFC 42: OGR Layer laundered field lookup"

2013-10-06 Thread Tamas Szekeres
Hi Jürgen, The commit you're referring to, doesn't seem contain the handling of the bExactMatch parameter at the driver. At the moment I consider this a bit redundant if calling OGRLayer::FindFieldIndex with bExactMatch = TRUE does the same as OGRLayer::GetFieldIndex. In this regard I'd be in favo

Re: [gdal-dev] Call for discussion for "RFC 42: OGR Layer laundered field lookup"

2013-10-06 Thread Jürgen E . Fischer
Hi Tamas, On Sun, 06. Oct 2013 at 20:05:18 +0200, Tamas Szekeres wrote: >Looks like a good proposal. >The only thing I'm uncertain about whether the driver should do something >different when calling OGRLayer::FindFieldIndex with bExactMatch = TRUE >than when calling OGRLayer::GetF

Re: [gdal-dev] Call for discussion for "RFC 42: OGR Layer laundered field lookup"

2013-10-06 Thread Tamas Szekeres
Jürgen, Looks like a good proposal. The only thing I'm uncertain about whether the driver should do something different when calling OGRLayer::FindFieldIndex with bExactMatch = TRUE than when calling OGRLayer::GetFieldIndex? I don't see the driver implementation in the pull request which would pro

[gdal-dev] Call for discussion for "RFC 42: OGR Layer laundered field lookup"

2013-10-06 Thread Jürgen E . Fischer
Hi, This is a call for discussion for "RFC 42: OGR Layer laundered field lookup": http://trac.osgeo.org/gdal/wiki/rfc42_find_laundered_fields It proposes a new method in the OGR layer class (and a C API) to lookup indexes of fields, whose names have been altered by drivers (eg. by LAUNDER in OC