Vector Data Specifications

vector data represents real world features as shapes on your project map — lines, polygons, and points common examples include polygons – buildings, forests, protected areas lines – roads, waterways, utility networks points – substations, pumps, or other discrete locations note points must be buffered (converted into polygons) before they can be used in analysis in optioneer supported file types format extension notes geojson geojson open source, widely supported geopackage gpkg open source, widely supported shapefile shp esri format — usually supplied as a zip containing multiple files kml kml used in google earth kmz kmz compressed kml, used in google earth ❌ not supported geodatabase ( gdb) is not currently accepted if you need support for a specific format, contact your customer success representative uploading vector data open project layers from the left hand panel select vector as the data type (shown by default) select add data choose upload dataset to import a file from your computer limits up to 50,000,000 features per layer up to 5gb per file up to 64 layers per dataset each dataset must contain a single geometry type (lines only or polygons only — no mixed geometries) before you upload a few things to check before uploading your data use a single file covering the full project area where possible, rather than many smaller files avoid special characters in file and layer names make sure your file opens cleanly before uploading — if you have access to a gis tool such as qgis, use it to verify the file first gis users use wgs84 (epsg 4326) as your coordinate reference system, provide attribute values in si units, and use open source formats such as geojson or geopackage over proprietary alternatives troubleshooting if your data fails to upload or process correctly, try the following if you are unsure about any of these steps, contact your customer success representative and they can assist clip to the required extent — avoid uploading large regional or global datasets start with the smallest area needed for your project run fix geometries — repair invalid geometries before export to remove self intersections and topology errors remove legacy id fields — fields such as fid can conflict with geopackage's internal id management remove them before export sanitize names and text fields — replace symbols such as & with plain text equivalents like and, and remove brackets or special characters from layer names, file names, and key attribute fields round trip through geojson — export to geojson and rebuild the geopackage from scratch this strips problematic metadata and resets the schema rebuild a fresh geopackage — do not merge cleaned layers into an existing package always create a new one if problems persist, contact your customer success representative with a description of the error and the steps already attempted