I think it's important to have both, they both have use cases IMO it would be good to be able to tell the project how to store each layer, relative or absolute. Use case: say I have a drive with my base maps and a folder structure on a different drive for projects, the base maps server is fixed but the sub projects can be moved within the main projects folder.
Exampe Base maps server == \\mymaps\ Main Project Folder -> BushfireProject ---> FireLayer.shp ---> Tracks.shp ---> Bushfire.qgs In Bushfire.qgs ./FireLayer.shp ./Tracks.shp ./Bushfire.qgs \\mymaps\basemaps\propertybase.shp \\mymaps\basemaps\roads.shp \\mymaps\basemaps\labels.shp etc etc This way I can move BushfireProject inside another folder, say BushfireProject2010 while still maintaining relative paths for some layers and absolute paths for stuff that won't change location. Main Project Folder -> BushfireProject2010 ---> BushfireProject2010 -----> FireLayer.shp -----> Tracks.shp -----> Bushfire.qgs - Nathan On Mon, Dec 19, 2011 at 9:40 PM, Richard Duivenvoorde <[email protected]>wrote: > I see Giovanni mention the change from absolut vs relative paths in qgs > files: http://hub.qgis.org/issues/4665#note-1 > > We (jef and specially me) are responsible for this during Zurich > hackfest... > > My argument was 'why would you have absolute paths, that is not > portable'... But in the issue I see that this COULD be handy when using > maybe the qgs-files voor qgis-server? Or at least: apparently users > where counting on this? > > So: to recap: should we discuss this (and maybe roll back?). Or are > relative paths just better.... Or will this end up in a war between > absolute vs relative-adepts. > > Regards, > > Richard > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer >
_______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
