Supported formats
Which survey files GISweaver accepts, which become map layers or open in 3D, and which are kept for download.
Which files you can deliver
Every accepted file can be downloaded with the required access.
| Format | Extensions | On upload |
|---|---|---|
| GeoJSON | .geojson | Viewed as map layers. |
| DXF | .dxf | Viewed as map layers.ASCII DXF is drawn on the map. A binary DXF is kept as a file and not drawn. |
| KML/KMZ | .kml, .kmz | Viewed as map layers. |
| GeoPackage | .gpkg | Viewed as map layers.A table that names no coordinate system is not drawn, and a GeoPackage with no feature table is kept as a file. |
| Shapefile (zipped) | .zip holding the .shp, .dbf and .prj | Viewed as map layers.Send the set in one ZIP with nothing else in it: a lone .shp is kept and not drawn. It is drawn only with its .prj; the project’s coordinate system is never assumed. |
| GeoTIFF | .tif, .tiff | A single-band elevation raster builds terrain; any other raster gets a preview.Which treatment applies depends on the raster’s own bands, not its name. |
| LAS | .las, .laz | Viewed as a point cloud in the 3D view.A LAZ is read as it is. If its declared coordinate system differs from the project’s it is drawn from its own, with a note. |
| Photos | .jpg, .jpeg, .png, .heic, .webp | Kept with the project with a thumbnail, plus when and where it was taken. |
| Videos | .mp4, .mov | Kept with the project. Plays in the viewer with the browser’s own controls. |
| Kept with the project with a page-by-page preview. | ||
| ZIP | .zip | Kept with the project as the archive it is, unless it is a Shapefile. |
| Other files | .dwg, .e57, .csv, .txt and any other file | Kept with the project. Not drawn on the map. |
- File size limits depend on the plan: see Plan capacity.
- Programs, scripts, disk images, macro-enabled Office files and web pages are refused. A binary DXF or any other file is kept as it is, and not drawn.
How does GISweaver identify a file?
GISweaver checks what a file is from its content, not only its name. A program, script, disk image, macro-enabled Office file or web page is refused; every other file is kept with the project.
This is why the table says ASCII DXF. A binary DXF has no marker that GISweaver reads, so a drawing exported as binary from a CAD package is kept as a file and not drawn.
Coordinate reference systems
- GeoJSON that names no coordinate reference system is read as WGS84, as the format’s specification requires, and its coordinates are checked against that range — projected metres offered as degrees are refused rather than published in the wrong place. A named system must be CRS84 or an EPSG code.
- DXF carries no reliable projection metadata, so the project’s own coordinate reference system is used and never inferred from the file. Every vertex converted on this path is checked against the area that system is defined for: an entity with a vertex outside it, such as one left at an unset origin, is left out and counted on the file, and a drawing with nothing inside it is refused.
- On publication every feature is stored twice: once in the project’s own system, which is the authoritative geometry, and once in WGS84 for display.
- A LAS or LAZ point cloud that declares a coordinate system different from the project’s is drawn reprojected, from the system it declares, and the file carries a note saying so. Measurements stay in the system the file came in.
Sizes
Each plan sets the largest file you can upload: see Plan capacity on the Pricing page. A GeoJSON file is read up to 512 MB and 500,000 features, and a single feature up to 64 MB. MB here are the binary units the Pricing page explains.
A LAS or LAZ point cloud of up to about 15 GB of point data once unpacked is the size we expect to convert and draw in 3D; how long it takes depends on the data. A larger cloud may be too big to draw, and is then kept as its original for download, so split it into tiles if you need it drawn.
A plan also sets the organisation’s total storage. That figure is on the Pricing page rather than here.
Scanned before it reaches anyone else
Every file the scanner can take is scanned for malware in the storage itself, in the same region. A file crosses to another organisation, or opens through a link, only once its scan has found no threats; one that is still being scanned or carries a threat is held back and named, and the rest of the delivery is still sent. A very large point cloud, raster or drawing that is too big for the scanner is passed on only after it has been checked as a valid file of its type, and it is labelled so.
What the analysis tools need
Distance, area and point measurement work on any published vector layer, and that is what analysis of a delivery means today. A single-band elevation GeoTIFF does build an elevation grid, but the tools that would read one are not on any published plan.
A measurement read off the map is a measurement, not a certified quantity survey. GISweaver does not make contours; it shows contours you deliver.
Ready to look at the product?
See plans and prices, or ask a person.