How to load a huge set (about 3.5 gb) of ecw images outside the default install dir for MGE?

[Anonymous]

My default install of MGE(server and Web tier) is on C drive with 3 gb free
space and now I want to set up a layer of orthophotos in ECW with a total
size of 3.5 gb (170 ecw files). I know I can not load the ecw files into the
repository of the default install on my C drive simply because of the space
limit and a max of 2 gb limit for a package file through Studio.

If I don't want to change my default install (to d drive which has 150 gb
space) now, how could I make the ecw files of 3.5 gb as a feature source in
MGE repository but pointing to a file folder having the 3.5 gb ecw files on
my d drive? I read about this workaround for SDF and SHP files:

https://mapguide.osgeo.org/servlets/ReadMsg?listName=users&msgNo=321

I tried the method suggested with this content text file:



xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xsi:noNamespaceSchemaLocation="FeatureSource-1.0.0.xsd">
Autodesk.Raster.3.1

DefaultFileLocation
D:\orthophotos\1-6000-ECW


ReadOnly
TRUE



But it seems this setup via Admin still needs to load the ecw files from d
drive to the c drive repository in order to make them available for a layer,
which means this method does not work for me.

Packaging the 3.5 gb ecw files failed too because of the 2gb limit for this
process even though with Admin I could reconfigure the package dir from c to
d drive.

Do I have any other workarounds than reinstalling the server repository to d
drive in order to overcome the space limit problems for big image files?

Thanks

Meng

[Anonymous]

Hi Meng,
Did you follow the steps in this white paper?

http://images.autodesk.com/adsk/files/linking_to_external_data_autodeskmapguidewhitepaper.pdf

There is also a Request for Change (RFC) currently underway for MapGuide
Open Source that pertains to this topic and that change would then in turn
make it into a future MapGuide Enterprise release.

http://wiki.osgeo.org/index.php/MapGuide_RFC_2_-_Unmanaged_Data_APIs

Andy

"Meng Li" wrote in message
news:5403707@discussion.autodesk.com...
My default install of MGE(server and Web tier) is on C drive with 3 gb free
space and now I want to set up a layer of orthophotos in ECW with a total
size of 3.5 gb (170 ecw files). I know I can not load the ecw files into the
repository of the default install on my C drive simply because of the space
limit and a max of 2 gb limit for a package file through Studio.

If I don't want to change my default install (to d drive which has 150 gb
space) now, how could I make the ecw files of 3.5 gb as a feature source in
MGE repository but pointing to a file folder having the 3.5 gb ecw files on
my d drive? I read about this workaround for SDF and SHP files:

https://mapguide.osgeo.org/servlets/ReadMsg?listName=users&msgNo=321

I tried the method suggested with this content text file:



xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xsi:noNamespaceSchemaLocation="FeatureSource-1.0.0.xsd">
Autodesk.Raster.3.1

DefaultFileLocation
D:\orthophotos\1-6000-ECW


ReadOnly
TRUE



But it seems this setup via Admin still needs to load the ecw files from d
drive to the c drive repository in order to make them available for a layer,
which means this method does not work for me.

Packaging the 3.5 gb ecw files failed too because of the 2gb limit for this
process even though with Admin I could reconfigure the package dir from c to
d drive.

Do I have any other workarounds than reinstalling the server repository to d
drive in order to overcome the space limit problems for big image files?

Thanks

Meng

[Anonymous]

Hi Andy, thanks for the reply. I didn't read the whitepaper before but
believe that the method is similar. Will have a look at the doc. after my
posting I did successfuly repoint my ecw path to the d drive and can display
the 3.5 gb ecw files as a layer (not a base map layer) but the performance
wasn't good enough. The performance for displaying the same ecw orthophotos
layer (using a RIC file) with MG 6.5 is very good, so we expect MGE could
give us a similar performance.

Yes, I read the RFC pertaining to the topic and hope it can be available as
planned.

Thanks again for the help and will meet with you at AU.

Meng

"Andy Morsell" wrote in message
news:5403729@discussion.autodesk.com...
Hi Meng,
Did you follow the steps in this white paper?

http://images.autodesk.com/adsk/files/linking_to_external_data_autodeskmapguidewhitepaper.pdf

There is also a Request for Change (RFC) currently underway for MapGuide
Open Source that pertains to this topic and that change would then in turn
make it into a future MapGuide Enterprise release.

http://wiki.osgeo.org/index.php/MapGuide_RFC_2_-_Unmanaged_Data_APIs

Andy

"Meng Li" wrote in message
news:5403707@discussion.autodesk.com...
My default install of MGE(server and Web tier) is on C drive with 3 gb free
space and now I want to set up a layer of orthophotos in ECW with a total
size of 3.5 gb (170 ecw files). I know I can not load the ecw files into the
repository of the default install on my C drive simply because of the space
limit and a max of 2 gb limit for a package file through Studio.

If I don't want to change my default install (to d drive which has 150 gb
space) now, how could I make the ecw files of 3.5 gb as a feature source in
MGE repository but pointing to a file folder having the 3.5 gb ecw files on
my d drive? I read about this workaround for SDF and SHP files:

https://mapguide.osgeo.org/servlets/ReadMsg?listName=users&msgNo=321

I tried the method suggested with this content text file:



xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xsi:noNamespaceSchemaLocation="FeatureSource-1.0.0.xsd">
Autodesk.Raster.3.1

DefaultFileLocation
D:\orthophotos\1-6000-ECW


ReadOnly
TRUE



But it seems this setup via Admin still needs to load the ecw files from d
drive to the c drive repository in order to make them available for a layer,
which means this method does not work for me.

Packaging the 3.5 gb ecw files failed too because of the 2gb limit for this
process even though with Admin I could reconfigure the package dir from c to
d drive.

Do I have any other workarounds than reinstalling the server repository to d
drive in order to overcome the space limit problems for big image files?

Thanks

Meng

[Anonymous]

I tried to link my ecw raster data (3.5 gb with 160 files) on d drive with
the method in this whitepaper:

http://images.autodesk.com/adsk/files/linking_to_external_data_autodeskmapguidewhitepaper.pdf

But when testing the connection for the feature source in Studio, I got this
error:

Permission denied to resource:
Session:df377bc2-ffff-ffff-8000-00145e299cd0_en//FeatureSourceEditorsScratch/SessionVersion1.FeatureSource

I found it's difficult to list all my 160 ecw files in the configuration
document with the configuration xml document allows me to use a wild card for names of
features and images from a defined image file dir? Any better tool like
Raster Workshop is available for doing this kind of work?

I am still unable to create a raster layer to display my recent ecw
orthophotos of 160 files for the entire city with MGE.

Any other suggestions?

Thanks

"Meng Li" wrote in message
news:5403742@discussion.autodesk.com...
Hi Andy, thanks for the reply. I didn't read the whitepaper before but
believe that the method is similar. Will have a look at the doc. after my
posting I did successfuly repoint my ecw path to the d drive and can display
the 3.5 gb ecw files as a layer (not a base map layer) but the performance
wasn't good enough. The performance for displaying the same ecw orthophotos
layer (using a RIC file) with MG 6.5 is very good, so we expect MGE could
give us a similar performance.

Yes, I read the RFC pertaining to the topic and hope it can be available as
planned.

Thanks again for the help and will meet with you at AU.

Meng

"Andy Morsell" wrote in message
news:5403729@discussion.autodesk.com...
Hi Meng,
Did you follow the steps in this white paper?

http://images.autodesk.com/adsk/files/linking_to_external_data_autodeskmapguidewhitepaper.pdf

There is also a Request for Change (RFC) currently underway for MapGuide
Open Source that pertains to this topic and that change would then in turn
make it into a future MapGuide Enterprise release.

http://wiki.osgeo.org/index.php/MapGuide_RFC_2_-_Unmanaged_Data_APIs

Andy

"Meng Li" wrote in message
news:5403707@discussion.autodesk.com...
My default install of MGE(server and Web tier) is on C drive with 3 gb free
space and now I want to set up a layer of orthophotos in ECW with a total
size of 3.5 gb (170 ecw files). I know I can not load the ecw files into the
repository of the default install on my C drive simply because of the space
limit and a max of 2 gb limit for a package file through Studio.

If I don't want to change my default install (to d drive which has 150 gb
space) now, how could I make the ecw files of 3.5 gb as a feature source in
MGE repository but pointing to a file folder having the 3.5 gb ecw files on
my d drive? I read about this workaround for SDF and SHP files:

https://mapguide.osgeo.org/servlets/ReadMsg?listName=users&msgNo=321

I tried the method suggested with this content text file:



xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xsi:noNamespaceSchemaLocation="FeatureSource-1.0.0.xsd">
Autodesk.Raster.3.1

DefaultFileLocation
D:\orthophotos\1-6000-ECW


ReadOnly
TRUE



But it seems this setup via Admin still needs to load the ecw files from d
drive to the c drive repository in order to make them available for a layer,
which means this method does not work for me.

Packaging the 3.5 gb ecw files failed too because of the 2gb limit for this
process even though with Admin I could reconfigure the package dir from c to
d drive.

Do I have any other workarounds than reinstalling the server repository to d
drive in order to overcome the space limit problems for big image files?

Thanks

Meng

[Anonymous]

I got it working and the error was related to some incorrect formats in the
xml doc. I found that using the Migration Tool migrating the MLF file can
allow me to create the xml configuration document (config.xml) with the
config template and all image file names populated, with this config.xml
file, I successfully created a raster feature source pointing to the ecw
files directory on D drive of my MGE server.

Thanks

"Meng Li" wrote in message
news:5404683@discussion.autodesk.com...
I tried to link my ecw raster data (3.5 gb with 160 files) on d drive with
the method in this whitepaper:

http://images.autodesk.com/adsk/files/linking_to_external_data_autodeskmapguidewhitepaper.pdf

But when testing the connection for the feature source in Studio, I got this
error:

Permission denied to resource:
Session:df377bc2-ffff-ffff-8000-00145e299cd0_en//FeatureSourceEditorsScratch/SessionVersion1.FeatureSource

I found it's difficult to list all my 160 ecw files in the configuration
document with the configuration xml document allows me to use a wild card for names of
features and images from a defined image file dir? Any better tool like
Raster Workshop is available for doing this kind of work?

I am still unable to create a raster layer to display my recent ecw
orthophotos of 160 files for the entire city with MGE.

Any other suggestions?

Thanks

"Meng Li" wrote in message
news:5403742@discussion.autodesk.com...
Hi Andy, thanks for the reply. I didn't read the whitepaper before but
believe that the method is similar. Will have a look at the doc. after my
posting I did successfuly repoint my ecw path to the d drive and can display
the 3.5 gb ecw files as a layer (not a base map layer) but the performance
wasn't good enough. The performance for displaying the same ecw orthophotos
layer (using a RIC file) with MG 6.5 is very good, so we expect MGE could
give us a similar performance.

Yes, I read the RFC pertaining to the topic and hope it can be available as
planned.

Thanks again for the help and will meet with you at AU.

Meng

"Andy Morsell" wrote in message
news:5403729@discussion.autodesk.com...
Hi Meng,
Did you follow the steps in this white paper?

http://images.autodesk.com/adsk/files/linking_to_external_data_autodeskmapguidewhitepaper.pdf

There is also a Request for Change (RFC) currently underway for MapGuide
Open Source that pertains to this topic and that change would then in turn
make it into a future MapGuide Enterprise release.

http://wiki.osgeo.org/index.php/MapGuide_RFC_2_-_Unmanaged_Data_APIs

Andy

"Meng Li" wrote in message
news:5403707@discussion.autodesk.com...
My default install of MGE(server and Web tier) is on C drive with 3 gb free
space and now I want to set up a layer of orthophotos in ECW with a total
size of 3.5 gb (170 ecw files). I know I can not load the ecw files into the
repository of the default install on my C drive simply because of the space
limit and a max of 2 gb limit for a package file through Studio.

If I don't want to change my default install (to d drive which has 150 gb
space) now, how could I make the ecw files of 3.5 gb as a feature source in
MGE repository but pointing to a file folder having the 3.5 gb ecw files on
my d drive? I read about this workaround for SDF and SHP files:

https://mapguide.osgeo.org/servlets/ReadMsg?listName=users&msgNo=321

I tried the method suggested with this content text file:



xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xsi:noNamespaceSchemaLocation="FeatureSource-1.0.0.xsd">
Autodesk.Raster.3.1

DefaultFileLocation
D:\orthophotos\1-6000-ECW


ReadOnly
TRUE



But it seems this setup via Admin still needs to load the ecw files from d
drive to the c drive repository in order to make them available for a layer,
which means this method does not work for me.

Packaging the 3.5 gb ecw files failed too because of the 2gb limit for this
process even though with Admin I could reconfigure the package dir from c to
d drive.

Do I have any other workarounds than reinstalling the server repository to d
drive in order to overcome the space limit problems for big image files?

Thanks

Meng