Trimble Business Center

John,

Are you working with data remotely stored?

I recently experienced the same feeling working on a large roadway project and finally figured out what was going on (at least in my case) when our outside IT contractor came in to install a new switch (so he could remote in to perform updated quicker, not for me. LOL) for the office network. Since the network was going to be down for a bit, I copied the files to my desktop to continue working until he got everything hooked back up. WHOOAA all of a suddenly I was flying along like I was working with a single traverse file instead of having over a quarter gig of data in the file.

Our switch was slowing me down because of the fieldwork files and drawing file being on the network. You would think that is where the data is so have the working file there also but the operations are done on the individual computer, so it was taking the time to xfer the data to my desktop and every save to the network plus rechecking the data every time I recomputed, updated, or saved anything. The more data I imported the slower it got because the work folder was on the %#@$$$ network and the speed limitation of the switches and routers was killing me. it was really noticeable when I had imagery involved, even though the imagery was stored locally it was using the data in the network because that was where it was imported to.

I have since started working with files only on my machine and backing up to the network automatically in the evening. I had to fight the IT guy to get setup for an automatic update due to administration privileges, but when I showed the owner the difference IT got overruled. 

John,

Are you working with data remotely stored?

I recently experienced the same feeling working on a large roadway project and finally figured out what was going on (at least in my case) when our outside IT contractor came in to install a new switch (so he could remote in to perform updated quicker, not for me. LOL) for the office network. Since the network was going to be down for a bit, I copied the files to my desktop to continue working until he got everything hooked back up. WHOOAA all of a suddenly I was flying along like I was working with a single traverse file instead of having over a quarter gig of data in the file.

Our switch was slowing me down because of the fieldwork files and drawing file being on the network. You would think that is where the data is so have the working file there also but the operations are done on the individual computer, so it was taking the time to xfer the data to my desktop and every save to the network plus rechecking the data every time I recomputed, updated, or saved anything. The more data I imported the slower it got because the work folder was on the %#@$$$ network and the speed limitation of the switches and routers was killing me. it was really noticeable when I had imagery involved, even though the imagery was stored locally it was using the data in the network because that was where it was imported to.

I have since started working with files only on my machine and backing up to the network automatically in the evening. I had to fight the IT guy to get setup for an automatic update due to administration privileges, but when I showed the owner the difference IT got overruled. 

Yes, we have noticed the same thing: working off the network drive slows down big projects with a lot of data; pretty much, "what John said!" We have one employee who does a large GPS network adjustment with several days of 24-hour files, and it is a lot of work even locally, but trying to do it off the network will just shut it down. Working locally to get around this is not ideal, but in this case it's not a Trimble issue. 

John,

Are you working with data remotely stored?

I recently experienced the same feeling working on a large roadway project and finally figured out what was going on (at least in my case) when our outside IT contractor came in to install a new switch (so he could remote in to perform updated quicker, not for me. LOL) for the office network. Since the network was going to be down for a bit, I copied the files to my desktop to continue working until he got everything hooked back up. WHOOAA all of a suddenly I was flying along like I was working with a single traverse file instead of having over a quarter gig of data in the file.

Our switch was slowing me down because of the fieldwork files and drawing file being on the network. You would think that is where the data is so have the working file there also but the operations are done on the individual computer, so it was taking the time to xfer the data to my desktop and every save to the network plus rechecking the data every time I recomputed, updated, or saved anything. The more data I imported the slower it got because the work folder was on the %#@$$$ network and the speed limitation of the switches and routers was killing me. it was really noticeable when I had imagery involved, even though the imagery was stored locally it was using the data in the network because that was where it was imported to.

I have since started working with files only on my machine and backing up to the network automatically in the evening. I had to fight the IT guy to get setup for an automatic update due to administration privileges, but when I showed the owner the difference IT got overruled. 

Yes, we have noticed the same thing: working off the network drive slows down big projects with a lot of data; pretty much, "what John said!" We have one employee who does a large GPS network adjustment with several days of 24-hour files, and it is a lot of work even locally, but trying to do it off the network will just shut it down. Working locally to get around this is not ideal, but in this case it's not a Trimble issue. 

John,

Are you working with data remotely stored?

I recently experienced the same feeling working on a large roadway project and finally figured out what was going on (at least in my case) when our outside IT contractor came in to install a new switch (so he could remote in to perform updated quicker, not for me. LOL) for the office network. Since the network was going to be down for a bit, I copied the files to my desktop to continue working until he got everything hooked back up. WHOOAA all of a suddenly I was flying along like I was working with a single traverse file instead of having over a quarter gig of data in the file.

Our switch was slowing me down because of the fieldwork files and drawing file being on the network. You would think that is where the data is so have the working file there also but the operations are done on the individual computer, so it was taking the time to xfer the data to my desktop and every save to the network plus rechecking the data every time I recomputed, updated, or saved anything. The more data I imported the slower it got because the work folder was on the %#@$$$ network and the speed limitation of the switches and routers was killing me. it was really noticeable when I had imagery involved, even though the imagery was stored locally it was using the data in the network because that was where it was imported to.

I have since started working with files only on my machine and backing up to the network automatically in the evening. I had to fight the IT guy to get setup for an automatic update due to administration privileges, but when I showed the owner the difference IT got overruled.