gdalindex question

[Gerry Creager n5jxs]

Ed,

What you're describing is the normal||aberent behavior of webservers
with regard to relative paths vice fully qualified paths.  It's also why
I've evolved to using fully qualified paths everywhere I need paths...
realizing I'm still finding some in odd spaces in old mapfiles!

Regards,
Gerry

Ed McNierney wrote:
> Frank -
>
> It's entirely possible that I haven't been looking, but I'm not aware of a clear specification on how relative paths are SUPPOSED to work.  I am under the impression that relative paths are somewhat vulerable to how the Web server is configured and how the MapServer CGI is referenced relative to that Web server.
>
> In the absence of a SHAPEPATH and/or IMAGEPATH statement, it's been my impression that the behavior of relative paths is not specified.  There have been recent changes to MapServer that have changed this behavior (at least in some cases I've observed) but I can't say that I thought either the earlier or the newer behavior was "wrong".
>
> If we intend to have relative paths behave in some consistent, predictable way (e.g. always relative to the directory containing the mapfile) we should be sure that's well-specified before trying to fix the code.  I apologize if that's already been done and I've overlooked it, but I'm not aware of it.
>
>      - Ed
>
> ----- Original Message -----
> From: Frank Warmerdam <warmerdam at POBOX.COM>
> To: MAPSERVER-USERS at LISTS.UMN.EDU
> Sent: Tue,  5 Oct 2004 10:16:06 -0400
> Subject: Re: [UMN_MAPSERVER-USERS] gdalindex question
>
>
>
>>Dylan Keon wrote:
>>
>>>Hi Dylan :-)
>>>
>>>After upgrading to 4.2.x or so, I found I had to use absolute paths for
>>>tileindexes.  That is, SHAPEPATH wouldn't work with my TILEINDEX
>>>declaration.  So, try:
>>>
>>>  TILEINDEX "/full/path/to/imagery/doqq/tiled/doqq_index.shp"
>>>
>>>and see if that makes a difference.  Also, are you sure it's TILEITEM
>>>"Location" instead of "location"?  It may be case sensitive, I can't
>>>remember.
>>
>>Dylan (or Dylan),
>>
>>I would appreciate confirmation if this is the issue.  There seem to have
>>been alot of problems with paths and tileindexes in 4.2 and later but I am
>>not aware of these issues being confirmed as bugs and filed as such.  In
>>particular, I would like to ensure none of these problems exist in 4.4
>>when we release it.  We might also be able to roll fixes into 4.2.4 or later.
--
Gerry Creager -- gerry.creager at tamu.edu
Texas Mesonet -- AATLT, Texas A&M University
Cell: 979.229.5301 Office: 979.458.4020
FAX:  979.847.8578 Pager:  979.228.0173
Office: 903A Eller Bldg, TAMU, College Station, TX 77843