[mapguide-users] ALIAS keeping old path in Package
chris.claydon at autodesk.com
Tue Jun 2 12:23:53 EDT 2009
I ran into this when trying to run raster performance tests. I copied over the feature sources as packages, but had to painstakingly open and re-save them all to get them to work. The reason for this is that the configuration document for the feature source uses the real file paths, and not the aliased paths. This is necessary because FDO (which creates and uses the config doc) doesn't know anything about the aliases, since they belong to the MG code.
I think it should be possible to unzip the package, batch update the config docs to use the new paths, and then zip it back up before importing it into the second server. A little ugly, but probably much easier than manually updating each feature source.
From: mapguide-users-bounces at lists.osgeo.org [mailto:mapguide-users-bounces at lists.osgeo.org] On Behalf Of GordonL
Sent: Tuesday, June 02, 2009 9:07 AM
To: mapguide-users at lists.osgeo.org
Subject: [mapguide-users] ALIAS keeping old path in Package
I was wondering if anyone has come across this one:
I have a MGP that has some data sources that point to some TIF files that
use an ALIAS (i.e. "GIS_DATA" points to E:\GIS )
My other server the same GIS_DATA points to C:\GIS, but for some reason, my
data sources all still point to the old location even though I am using
File 'C:\GIS\airphoto.tif' does not exist - if you look at the datastore, it
My workaround was by re-browsing to the folder, and saving the data store,
but I have hundreds of data stores. Restarting has no effect. Why is the
ALIAS translating to the full path permanently?
Shouldn't the new Alias direct the paths correctly? Where is this stored?
View this message in context: http://n2.nabble.com/ALIAS-keeping-old-path-in-Package-tp3012647p3012647.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
mapguide-users mailing list
mapguide-users at lists.osgeo.org
More information about the mapguide-users