Supported formats
Which files GISweaver accepts as a delivery, which of them become map layers, which are kept for download, and what the elevation tools need before they will run.
Which files a delivery may be
Map layers from GeoJSON and ASCII DXF. Other accepted files can be retained as source artefacts.
| Format | Becomes map layers | Kept for download | Analysis supported |
|---|---|---|---|
| GeoJSON | Yes | Yes | Distance, area and point tools on the published layers |
| DXFASCII DXF only. A binary DXF is not accepted. | Yes | Yes | Distance, area and point tools on the published layers |
| ZIP | No | Yes | Nothing on the map: the file is kept for download |
| LAS | No | Yes | Nothing on the map: the file is kept for download |
| No | Yes | Nothing on the map: the file is kept for download |
- Elevation profiles, profile comparison and cut-and-fill volumes need a release that already carries a compatible elevation surface. No format above produces one — DEM, DSM, GeoTIFF and COG intake is not implemented — and the volumes those tools report are planning-grade, not a survey certification.
- Not accepted as a delivery: Shapefile on its own, LAZ (supply the uncompressed LAS), GeoTIFF, COG, DEM, DSM and 3D Tiles. A Shapefile inside a ZIP is accepted as part of that archive and kept for download, but it does not become map layers. Site photographs and documents can be kept on a project as attachments.
How a file is identified
By its leading bytes, never by its name or extension. Renaming a file changes nothing: a document that is not one of the accepted formats is refused at intake, and the two text formats are recognised by the shape their grammar forces on the first lines rather than by a signature.
This is why the table says ASCII DXF. A binary DXF announces itself with a sentinel the validator does not read, so a delivery exported as binary from a CAD package is refused.
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, which is what catches a drawing whose origin was left at zero.
- 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.
Sizes
A single delivery upload is accepted up to 100 GB, and a project attachment up to 1 GiB. A GeoJSON document is read up to 512 MiB and 500,000 features, and a single feature up to 64 MiB.
A plan may also set a smaller limit on one file and on the organisation’s total storage. Those figures are published per deployment and are on the plans page rather than here.
What the analysis tools need
Distance, area and point measurement work on any published vector layer. Elevation profiles, profile comparison and cut-and-fill volumes need a release that already carries a compatible elevation surface, and no accepted format produces one — intake for DEM, DSM, GeoTIFF and COG is not implemented. Where a release has no surface those three tools are drawn disabled with the reason beside them, rather than failing when pressed.
Where a surface is present, a volume or a profile is a planning estimate derived from that elevation model. It is not a certified quantity survey, and GISweaver does not generate contours from a surface.
Ready to look at the product?
The plans page lists what each plan includes and what it costs. If you would rather ask a person first, the support page is the way to reach one.