WFS/OWS Path problem?

[warmerdam]

Frank

I'm running MapServer on Windows 2000 Professional. I found out that
msOWSBuildURLFilename() in mapows.c adds a backslash character.

See following snippet:

#ifdef _WIN32
        sprintf(pszBuf, "%s\\", pszPath);
#else
        sprintf(pszBuf, "%s/", pszPath);
#endif

I think this is what's messing things up. My mapfile works fine for WMS and
the GML file mentioned in the error message is being created in the
appropriate directory.

Is this a bug? If so, what's the work around? If not, what am I doing wrong?

Thanks!
JAB

----- Original Message ----- 
From: "Brown, Jeff (C2MS)" <jeffrey.brown@ngc.com>
To: <cropwithdawn@cox.net>
Sent: Friday, May 05, 2006 11:12 AM
Subject: For JAB: FW: [UMN_MAPSERVER-USERS] Why do I get this error message
when trying to access WFS?




-----Original Message-----
From: Frank Warmerdam [mailto:fwarmerdam@gmail.com] On Behalf Of Frank
Warmerdam
Sent: Friday, May 05, 2006 10:59 AM
To: Brown, Jeff (C2MS)
Cc: MAPSERVER-USERS@LISTS.UMN.EDU
Subject: Re: [UMN_MAPSERVER-USERS] Why do I get this error message when
trying to access WFS?

Brown, Jeff (C2MS) wrote:
> > I get the following error message when I try to access my WFS
resource:
> > msOGRFileOpen(): OGR error. Open failed for OGR connection
> > `/ms4w/tmp/ms_tmp/\7bb0d77657833c3f75a5de7149b5572f.tmp.gml'. File not

> > found or unsupported format.

Jeff,

It looks like an extra "\" is getting inserted in the path somehow.
You might want to check your temporary file path in the WEB object.
Perhaps it is in there?  Or perhaps you will need to drop the trailing
forward slash from there (though that might cause other problems).

[assefa]

looking into this

[assefa]

couple of things :

I have changed the string concatenation logic to validate the last character
before appending the slash.
But that does not seem to solve the issue with opening a gml file using a path
like this /tmp/ms_tmp/name_of_the_gml.gml.  If I use for the same file a path
using the drive c:/tmp/ms_tmp/name_of_the_gml.gml, It will work.
 
This is reproducable by using a simple map layer with an ogr connection (
CONNECTION "/tmp/ms_tmp/3b858489ab10fc43f236141857205a64.tmp.gml").  

Looking into the debugger, the 'error' seems to come from function 
GMLFeature *GMLReader::NextFeature() when calling !m_poSAXReader->parseFirst.  I
could not debug further in that code (for soem reason the debgger exits at that
point).

Note that using ogr with  shape files without a drive specified works ok.

Note sure if this is a new or It has always been like this and was just visible
because of the ms4w default map settings.  
 
   

[fwarmerdam]

I'll try and look into this. 

[warmerdam]

I don't have any information to reproduce this nor do I recall anything about this even though it appears I was the original reporter.

Closing.

[jmckenna]

Assefa, this problem still exists. In fact we've been hitting this for a few years with the MapServer workshop at FOSS4G (we would avoid WFS because of this). I get the same results with MS4W 2.2.9 as your comment:2 using a WFS-client layer: - reproducable with simple OGR connection without the drive letter using shp2img and CGI test app (CONNECTION "/tmp/ms_tmp/3b858489ab10fc43f236141857205a64.tmp.gml") - adding the drive letter to IMAGEPATH (in both mapfile and CGI variable) solves it

I think this is a bug.

[jmckenna]

tiny test mapfile for reproducing problem

[jmckenna]

sorry from re-reading bug it seems Assefa confirmed this bug before and passed it to Frank. Frank let me know if you need anything to reproduce. Easiest method: take that small test.map and run it with shp2img.