Introduction
Types of data that Optioneer can work with:
DTM - elevation, slope
Geology - soil types, geohazards
Constraints - soft constraints, hard constraints
Linear features - existing infrastructure, watercourses, utilities
For all datasets:
ensure no corrupt data entries (like NaN) are present
inspect visually if the data is aligned correctly with source data
merge sources into a single file for the entire project area i.e. we prefer 30 large coverage files with one layer each than more smaller coverage files with 30 layers each
where possible, provide values in SI units
do NOT use special characters in file name or layer names
verify that your file can be opened without warnings with open source software like QGIS (version 3+)
provide the data in WGS84, rather than local systems
minimise the amount of metadata attached to features / layers, focus on geometries and types
please avoid using file formats specific to a software provider and use open-source formats instead
if more than 24 layers are present, please split the file into smaller files by common type. For example, split linear features into roads, rivers & streams, utilities files, rather than alphabetically or by feature count
DTM layer
Description: this is the dataset that gives Optioneer information about terrain elevation which is used in vertical profile and pumping costs calculation. Floating point values are preferred to give as precise definition of elevation at point as possible.
Specification:
Raster dataset, 1/3600 degree (1 arcsecond) resolution in lat/lon
In case of more granular datasets, provide average value when downsampling
Projection: WGS84 (EPSG:4326)
File format: .tif, .tiff, .geotiff
Datatype: Int32, Float32
No skew
Positive values correspond to elevations above sea level.
One band per file
No data value specified (in general, please avoid no-data but if present, set it to an arbitrarily high number like 32767)
File name should not contain special characters and use underscore (i.e. '_') to denote spaces
File size: up to 1GB
Geology
Description: this is the dataset that gives the optimiser information about geology/seabed conditions along the horizontal profile.
NB: Optioneer doesn’t yet support data which varies with depth.
Specification:
Vector file with up to 24 layers
Projection: WGS84 (EPSG:4326)
File format: shp (+shx, prj, dbf), geojson, gpkg, kml, kmz
Feature count: up to 100,000
Feature size: up to 100,000 km2
No empty layers
Allowed geometry types: polygon, multipolygon
Layer names should not contain special characters and use underscore (i.e. '_') to denote spaces
File name should not contain special characters and use underscore (i.e. '_') to denote spaces
File size: up to 200MB
Constraints
Description: this is the dataset that gives the optimiser information about constraints along the horizontal profile.
Specification:
Vector file with up to 24 layers
Projection: WGS84 (EPSG:4326)
File format: shp (+shx, prj, dbf), geojson, gpkg, kml, kmz
Feature count: up to 100,000
Polygon size: up to 100,000 km2
No empty layers
Allowed geometry types: polygon, multipolygon
Layer names should not contain special characters and use underscore (i.e. '_') to denote spaces
File name should not contain special characters and use underscore (i.e. '_') to denote spaces
File size: up to 200MB
Linear features
Description: this is the dataset that gives the optimiser information about linear features and will inform crossing counts and engineering decisions.
Specification:
Vector file with up to 24 layers
Projection: WGS84 (EPSG:4326)
File format: shp (+shx, prj, dbf), geojson, gpkg, kml, kmz
Feature count: up to 100,000
No empty layers
Allowed geometry types: LineString, MultiLineString
Layer names should not contain special characters and use underscore (i.e. '_') to denote spaces
File name should not contain special characters and use underscore (i.e. '_') to denote spaces
File size: up to 200MB
Other data
Description: any other data deemed relevant for the project, such as administrative boundaries, Points of Interest, socio-economic / population data etc.
Do get in touch with Continuum Industries team to discuss the specifics - use Intercom or email geodata@continuum.industries
For vector datasets:
Vector file with up to 24 layers
Projection: WGS84 (EPSG:4326)
File format: shp (+shx, prj, dbf), geojson, gpkg, kml, kmz
Feature count: up to 100,000
Polygon size: up to 100,000 km2
No empty layers
Allowed geometry types: polygon, multipolygon, LineString, MultiLineString
Layer names should not contain special characters and use underscore (i.e. '_') to denote spaces
File name should not contain special characters and use underscore (i.e. '_') to denote spaces
File size: up to 200MB
For raster datasets:
1/3600 degree (1 arcsecond) resolution in lat/lon
In case of more granular datasets, provide average value when downsampling
Projection: WGS84 (EPSG:4326)
File format: .tif, .tiff, .geotiff
Datatype: Int32, Float32
No skew
Positive values correspond to elevations above sea level.
One band per file
No data value specified
File name should not contain special characters and use underscore (i.e. '_') to denote spaces
File size: up to 1GB
Project features - points, lines and polygons
These features are different to general geospatial data and are uploaded as 'project features' rather than data layers that can be used within design rules.
These features can be uploaded as .geojson and contain individual or multiple features of each kind. More info to follow!