Network, Cloud, and Long File Path Support

CivilGEO software supports projects stored on local drives, network drives, cloud storage platforms, and deeply nested folder structures. This allows users to work from shared company folders, remote project directories, cloud-synced locations, and long organizational folder paths without requiring special Windows configuration.

This support is especially useful for engineering teams that manage project files across LAN/WAN environments, cloud storage platforms, and standardized project folder structures. Users can open, edit, and save projects while avoiding many of the file-locking errors, incomplete results, path-length issues, and workflow interruptions that commonly occur when project files are accessed directly from remote storage locations.

To support these workflows, the software uses a local project caching system. When a project is opened from a remote location, the software automatically copies the project data to the user's local machine, works from that local copy during the modeling session, and synchronizes updated files back to the original storage location when the project is saved. This reduces file-locking errors, network latency issues, and workflow interruptions that can occur when project files are accessed directly from remote storage locations during active modeling.

Supported Storage Environments

CivilGEO software supports projects stored in the following environments:

• Local hard drives and SSDs
• Network drives in LAN and WAN environments
• Cloud storage platforms — Google Drive, Dropbox, Microsoft OneDrive, SharePoint, ShareFile, and similar platforms
• Deeply nested folder structures with long cumulative directory path lengths

For cloud storage workflows, the project folder should be available through the local file system, such as a synced cloud folder, mapped drive, or network-accessible location. This allows the software to open and save project files through standard file access workflows.

For example, the following image shows a project file stored on OneDrive being opened directly from the Open Project dialog box.

Why Remote Storage Support Matters

Civil engineering projects often contain many related files, including project databases, terrain files, GIS layers, background map data, model results, reports, and supporting documents. When these files are stored in shared folders or cloud-synced locations, direct read/write activity against the source files can be affected by network latency, cloud synchronization delays, file permissions, or file-locking behavior from other applications.

These issues can interrupt modeling workflows, slow down project performance, or prevent results from being saved correctly. CivilGEO software reduces these risks by working from a local cached copy during the active modeling session and synchronizing changes back to the original project location when the project is saved.

How CivilGEO Handles Remote Project Files

When a project is opened from a network or cloud storage location, the software automatically copies the project data to a local cache on the user's machine. All read and write operations during the modeling session are performed against this local copy rather than directly against the remote storage location. This approach avoids the performance slowdowns, file-access conflicts, and file-locking errors that commonly occur when project files are accessed over a network or cloud connection during active modeling.

When the user saves the project, the software writes the updated data from the local cache back to the original source location. Because all changes are accumulated locally during the session, the save operation does not require continuous network access throughout the modeling workflow.

The local cache is stored on a local drive on the user's machine and is managed automatically by the software. The software selects an appropriate local drive for the cache rather than defaulting to the operating system drive. This is useful for computers where the C: drive is reserved for the operating system and application executables, while another drive, such as the D: drive, is used as the user’s working hard drive.

If required, the user can override the default local cache location using the Default local file location entry in the General Preferences section under Application Options on the Options backstage page, as shown below.

To learn more about the Options backstage page, refer to this article in our knowledge base.

Long File Path Support

Traditional Windows file handling has historically limited file paths to a maximum of 260 characters. Starting with Windows 10 version 1607, Microsoft introduced support for longer file paths; however, this support requires both a Windows system configuration change and explicit application opt-in, meaning it is not automatically available to every application or analysis engine.

This creates issues for engineering modeling software because the underlying analysis engines used by CivilGEO software — including HEC-RAS, HEC-HMS, and EPA SWMM — do not natively support long file paths. HEC-RAS can further compound this issue by generating temporary or output files, including DSS-related files, with already-lengthy file names. Even a moderately nested folder structure can push these file names past the traditional 260-character limit, causing errors during computation.

This becomes a practical problem when organizations store projects in deeply nested folder structures that reflect long project names, client names, review stages, or standardized directory hierarchies commonly used across engineering firms.

CivilGEO software supports long file paths by managing path-length constraints internally, so that the underlying analysis engines receive valid file paths regardless of how deeply the project is nested on disk. This allows the user to organize projects in folder structures that align with the organization's file management standards without encountering path-length errors during normal project operations.

Long file path support is useful when project files are stored in locations such as:

• Standardized company project directories
• Client-specific folder structures
• Cloud-synced project folders
• Nested design, review, submittal, and archive folders
• Shared engineering folders with long project or phase names

Unicode and International File Name Support

CivilGEO software supports Unicode file names and folder names that include international character sets. Project files, directories, and associated data files can use characters from Unicode-supported languages and scripts, including accented Latin characters, Cyrillic, Arabic, Chinese, Japanese, Korean, and other writing systems.

The software handles Unicode file paths transparently throughout supported project workflows, including opening and saving projects, importing GIS and terrain data, exporting results, and generating reports. The user does not need to rename files to ASCII-compatible formats or adjust system encoding settings.

Recommended Best Practices

When working with projects stored on network drives, cloud storage platforms, or deeply nested folder structures, the following best practices can help maintain a reliable workflow:

• Confirm that the user has read and write authorization for the source project folder.
• Allow cloud storage clients to complete synchronization before opening or sharing updated project files.
• Avoid moving, renaming, or deleting source project folders while a project is open.
• Keep project folders organized so related model files, terrain files, GIS data, and results remain together.
• Avoid using Windows-reserved characters in file and folder names.
• Verify that third-party tools used in the workflow support long file paths and Unicode file names.

Conclusion

CivilGEO software's support for network storage, cloud storage, long file paths, and Unicode file names allows engineering teams to work in modern shared storage environments without restructuring their file management practices. By caching project data locally during active modeling sessions, the software reduces file-access conflicts, improves performance, and maintains reliable synchronization with the original project location. This allows engineering teams to follow their organization's preferred file management standards while keeping the modeling workflow stable and efficient.