Hi Laith
I personally have implemented a directory structure and file saving scheme
that keeps this problem down. Here's how it works on my system (with about
750,000 tables and 5,000-7,500 workspaces)
1) Store all your main mapping tables like streets, city boundaries, block
groups, etc in one main folder. I personally break this down a bit for speed
- Major Roads, Highways and Interstates are stored at the US level (in a
folder called USA) and larger files (like streets, streams & rivers, block
group boundaries) are broken down and stored by state. The directory
structure looks something like the following:
\Mapping Data
\Mapping Data\USA
\Mapping Data\USA\Boundaries
\Mapping Data\USA\Highways
\Mapping Data\USA\Water <- Oceans and major lakes only
\Mapping Data\USA\Data <- demographic data files (dbf)
\Mapping Data\States\Texas\Roads <- the streets go here
\Mapping Data\States\Texas\Water <- streams, rivers
For individual projects I create a folder for my client and then subfolders
under them for individual projects. When I make a map the workspace and any
files specific to that workspace (road labels, trade areas, etc) are stored
in the same folder as the workspace. The directory structure looks like
this:
\Clients\Client 1
\Clients\Client 1\Project 1
\Clients\Client 1\Project 1\Workspace 1.wor
\Clients\Client 1\Project 1\Highway Labels.tab
\Clients\Client 1\Project 1\Trade Area Boundary.tab
This system has served me very well over the years - you just have to make
sure people understand that the main mapping files are _not_ to be moved.
Overall, this keeps file sizes down, data duplication to almost nothing and
ensures that workspaces always open. I generally assume that anything I
created several years ago should open just fine today - and it usually does.
You need to plan out your directory structures carefully but, if you do, you
should have very few problems with file locations.
Drop me a note if you want more info.
Regards,
James
James L Marlow
Director, Geographic Information Systems
Channel Marketing Corporation
15032 Beltway Drive
Dallas, Texas 75001
Telephone 1 (972) 858-9600 extension 331
Facsimile 1 (972) 858-9601
email: [EMAIL PROTECTED]
www: http://www.cmcus.com
-----Original Message-----
From: Laith Wark [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 22, 1999 12:26 AM
To: MapInfo List Serve (E-mail)
Subject: MI Housekeeping
A housekeeping question.
Can anybody suggest an orderely and efficient way of storing tables and
workspaces over a network with the aim to:
1. Maintain workspace robustness
2. Reduce the amount of space taken
3. Enable the fastest working speed
With the amount of dud workspaces failing to open due to corrupted paths, I
resorted to making copies of each table, and saved it in the same folder as
the .wor. Needless to say, this uses a LOT of space (ok, I went for the
"fix it with a hammer" approach).
Any advices would be appreciated.
Laith
========================================
Laith Wark
EDAW (Aust) P/L
Design, Planning and
Environments Worldwide
Level 4 Rowes Building
235 Edward Street
Brisbane 4000
Australia
Ph: INT +61 (0)7 3229 6422
Fx: INT +61 (0)7 3229 6422
Email: [EMAIL PROTECTED]
========================================
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]
