Basic Requirements
Supported Operating Systems
- Microsoft Windows Server 2012
- Microsoft Windows Server 2016
- Windows 10 Pro
Minimum Requirements – Server
- .NET Framework version 4.5 or higher
- Microsoft Internet Information Services (IIS) 7 or newer
- 1GB LAN
- 2 GHz CPUs
*NAS/CIFS storage not supported
Currently the only browsers officially supported by Canary Systems for our MLWeb platform are:
Recommended Server Specifications
Minimal Environment
Intended primarily for testing, demo or backup purposes, or for very small environments with only a 1-2 users and limited data imports, in particular limited 3D data processing.
- Operating System: Windows 10 Pro
- Processor: 1.8 GHz per core, 4 cores
- Memory: 32 GB
- Hard Drive: 1 TB SSD
Small Environment
Single server deployment running all MLSuite components for small projects and 1-4 concurrent users with limited 3D data processing requirements.
- Operating System: Windows Server 2012 or 2016
- Processor: 3 GHz per core, 8 cores
- Memory: 32 GB
- Hard Drive 1: 500 GB SSD with 2 partitions
- Partition 1 – 100 GB: Operating System
- Partition 2 – 400 GB: Program Files, backups, archives
- Hard Drive 2: 250 GB SSD dedicated to Firebird and PostgreSQL databases
- Hard Drive 3: 250 GB SSD for Page file and Temp folder
Medium Environment
Two server deployment, one dedicated to MLWeb, the second for remaining components. This setup will satisfy the most common project requirements for average size projects including medium sized multi-user environments and use of 3D data with infrequent processing.
- Operating Systems (each server): Windows Server 2012 or 2016
- Processors (each server): 3 GHz per core, 8 cores
- Memory (each server): 32 GB
- Server 1 (running MLWeb only)
- Hard Drive 1: 250 GB SSD with 2 partitions
- Partition 1 – 100 GB: Operating System
- Partition 2 – 150 GB: Program Files
- Hard Drive 2: 250 GB SSD for Page file and Temp folder
- Hard Drive 1: 250 GB SSD with 2 partitions
- Server 2 (running all other components)
- Hard Drive 1: 500 GB SSD with 2 partitions
- Partition 1 – 100 GB: Operating System
- Partition 2 – 400 GB: Program Files, backups, archives
- Hard Drive 2: 250 GB SSD dedicated to Firebird and PostgreSQL databases
- Hard Drive 3: 250 GB SSD for Page file and Temp folder
- Hard Drive 1: 500 GB SSD with 2 partitions
Large Environment
Three server deployment for enterprise sized projects including multi-user access and frequent 3D data processing (such as regular radar data imports).
- Operating Systems (each server): Windows Server 2012 or 2016
- Processors (each server): 3.5 GHz per core, 8 cores
- Memory (each server): 32 GB
- Server 1 (running MLWeb only)
- Hard Drive 1: 250 GB SSD with 2 partitions
- Partition 1 – 100 GB: Operating System
- Partition 2 – 150 GB: Program Files
- Hard Drive 2: 250 GB SSD for Page file and Temp folder
- Hard Drive 1: 250 GB SSD with 2 partitions
- Server 2 (running MLServer, MLGateway and Firebird SQL)
- Hard Drive 1: 500 GB SSD with 2 partitions
- Partition 1 – 100 GB: Operating System
- Partition 2 – 400 GB: Program Files, backups, archives
- Hard Drive 2: 250 GB SSD dedicated to Firebird databases
- Hard Drive 3: 250 GB SSD for Page file and Temp folder
- Hard Drive 1: 500 GB SSD with 2 partitions
- Server 3 (running PostgreSQL and MLProcessor for 3D data)
- Hard Drive 1: 500 GB SSD with 2 partitions
- Partition 1 – 100 GB: Operating System
- Partition 2 – 400 GB: Program Files, backups, archives
- Hard Drive 2: 250 GB SSD dedicated to PostgreSQL databases
- Hard Drive 3: 250 GB SSD for Page file and Temp folder
- Hard Drive 1: 500 GB SSD with 2 partitions
Vector Formats
- CSV (Comma separated values text file)
- DLG (Digital Line Graphs)
- DGN
- DXF-ASCII (AutoCad Export format)
- DXF-BINARY (AutoCad Export format)
- DWG 2000
- E00-ASCII (ArcInfo Export Format)
- E00-BINARY (ArcInfo Export Format)
- FME (requires FME installation)
- GDAL / OGR
- GDF 3.0
- GeoMedia MBD
- GML 3.1.1
- GPX (GPS Exchange Format)
- GSHHS (Global Self-consistent Hierarchical High-resolution Shorelines)
- JSON (JavaScript Object Notation)
- KML (OpenGIS/Google Earth Keyhole Markup Language)
- LandXML
- Lidar XYZ
- MIF/MID (MapInfo Import Format)
- OSM (OpenStreetMap)
- SDTS-TCP (TVP-Topological Vector Profile)
- SHP (ArcView Shape Format)
- S-57 (Marine charting format)
- TAB (Map Info Vector format)
- TIGER/Line
- UDF (User Defined Format)
- VPF 3.0 (Vector Product Format)
- WKT (Well-known text)
- WFS (OpenGIS Web Feature Service)
Image/Grid Formats
- ADF (ArcInfo Integer Grid)
- BIL
- BMP
- BT (Binary Terrain Grid)
- CADRG
- DEM (USGS Digital Elevation Models)
- DT0 (Digital Terrain Elevation Data level 0)
- DT1 (Digital Terrain Elevation Data level 1)
- DT2 (Digital Terrain Elevation Data level 2)
- FLT (Arcinfo Float Binary Grid)
- GDAL
- GeoTIFF
- GIF
- GRD (Arcinfo ASCII Grid)
- GRD (Surfer ASCII Grid)
- IMG (ERDAS IMAGINE)
- JPEG
- JPEG2000
- MrSID
- PixelStore2
- PNG
- SDTS-RPE (Raster Profile and Extensions)
- SRTM HGT (grid)
- UDF (User Defined Format)
- WMS (OpenGIS Web Map Service)
- WMTS (OpenGIS Web Map Tile Service)
- TIFF (uncompressed, LZW, packbits, group4)
API Documentation
News & Announcements
See you at SME 2026!February 12, 2026 - 4:43 pm
Advisory Board Press ReleaseFebruary 2, 2026 - 1:04 pm
Slope Stability 2025 Workshop Recap & PresentationDecember 16, 2025 - 4:43 pm
MLSuite 2025 SP2 ReleaseDecember 12, 2025 - 3:28 pm- See us at Slope Stability 2025!October 24, 2025 - 3:06 pm