Opened 13 years ago

Last modified 13 years ago

#4009 new defect

inconsistency in the relative paths to files in a tileindex between raster and vector layers

Reported by: winkey Owned by: sdlime
Priority: normal Milestone:
Component: MapServer C Library Version: unspecified
Severity: normal Keywords:
Cc:

Description

I found an inconsistency in the relative paths to files in a tileindex between raster and vector layers

vector - the current path is the location of the top-level map file

raster - the current path is the location of the included map file

I believe the desired behavior should be the relative to the included map file

MapServer version 5.7-dev OUTPUT=GIF OUTPUT=PNG OUTPUT=JPEG OUTPUT=WBMP OUTPUT=SVG SUPPORTS=PROJ SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=ICONV SUPPORTS=WMS_SERVER SUPPORTS=GEOS INPUT=POSTGIS INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE

Change History (2)

comment:1 by sdlime, 13 years ago

Hmmm... This one should probably be run by mapserver-dev just in case. The raster case is far more common so that's the one I'd fear breaking. I'd propose only fixing 6.0+...

Steve

comment:2 by winkey, 13 years ago

The raster case is the way I would expect it to work, relative to the included mapfile, otherwise you cant shuffle things around without rebuilding the tileindex.

Brian

Note: See TracTickets for help on using tickets.