On Mon, Nov 1, 2010 at 8:44 AM, Andrea Aime
wrote:
> On Mon, Nov 1, 2010 at 3:30 AM, Justin Deoliveira
> wrote:
>> Makes sense. So I guess just a check that if a response returns no supported
>> output formats it should simply be skipped and removed to the candidate
>> response list?
>
> Indeed,
On Mon, Nov 1, 2010 at 3:30 AM, Justin Deoliveira wrote:
> Makes sense. So I guess just a check that if a response returns no supported
> output formats it should simply be skipped and removed to the candidate
> response list?
Indeed, that would be the plan
Cheers
Andrea
---
Makes sense. So I guess just a check that if a response returns no supported
output formats it should simply be skipped and removed to the candidate
response list?
On Fri, Oct 29, 2010 at 11:36 AM, Andrea Aime
wrote:
> Hi,
> I was looking into an odd failure that was happening when the
> ogr form
Hi,
I was looking into an odd failure that was happening when the
ogr format was around, but misconfigured (wrong ogr2ogr location).
In that case the ogr format reports no output formats, and that oddly
results in the dispatcher assuming ogr2ogr can handle every and any
output format!
The culprit
