Supported files and limits¶
Every file reaches a project through the strip at the top of its Files list (see Add files to a project). This page lists what that strip accepts, what GISweaver does with each kind, and the limits that apply.
The files a project accepts¶
| File | Extensions | What it becomes |
|---|---|---|
| GeoJSON | .geojson, .json | Map layers within the reading limits below; other JSON is kept as text. With no coordinate system named, it is read as WGS 84, as the GeoJSON specification requires; a named system must be CRS84 or an EPSG code. Projected metres offered as degrees are refused rather than drawn in the wrong place. |
| DXF | .dxf | Map layers. ASCII DXF only: a binary DXF is kept as a file and not drawn. A DXF has no reliable coordinate system, so it is read in the project's own; a drawing entity with a point outside the area that system covers is left out and counted on the file. |
| KML/KMZ | .kml, .kmz | Map layers, one for each folder of the KML. A KMZ is read as the KML inside it; a KMZ with no KML inside is kept as an archive. A KML is in WGS 84 by its specification. |
| GeoPackage | .gpkg | Map layers, one for each feature table. A table must name its coordinate system, or it is refused rather than guessed and the file is still kept. A GeoPackage with no feature table is kept as a file and not drawn. |
| Shapefile (zipped) | .zip holding the .shp, .shx, .dbf and .prj | Map layers, one for each Shapefile in the ZIP. A ZIP is a Shapefile only if it holds a .shp and every other file in it is a part of a Shapefile (.shx, .dbf, .prj, .cpg); a ZIP with anything else in it is kept as an archive. Without the .prj, or with a lone .shp, it is kept and not drawn. |
| GeoTIFF | .tif, .tiff | A single-band elevation raster becomes an elevation grid; any other raster, such as a drone orthomosaic, gets a preview. The raster's bands decide which, not its name. |
| LAS, LAZ | .las, .laz | A point cloud, viewed in 3D. A LAZ (compressed) file, and a COPC file, which is a LAZ, are read as they are. A cloud that declares a coordinate system different from the project's is drawn from its own and marked Source CRS EPSG:n; shown reprojected; measurements stay in its own system. One that declares none is read in the project's; one whose stated system does not match where its points lie is refused. |
| Photo | .jpg, .jpeg, .png, .heic, .webp | A kept file with a thumbnail, and when and where it was taken. A HEIC or WebP photo is stored as a JPEG or PNG. |
| Video | .mp4, .mov | A kept file that plays in the viewer. |
| A kept file with a page-by-page preview. | ||
| Word and Excel | .docx, .xlsx | A kept file, kept as it came. It is checked for its type and that it is whole. |
| Archives | .zip, .7z, .rar, .tar, .gz, .tgz | A kept file, handed over as received: it is scanned for known malware, and its contents are not opened or refused, so a program inside a clean archive reaches the person you send it to. Send only archives you trust. An archive is not unpacked into map layers, except a ZIP that is a Shapefile. |
| DWG | .dwg | A kept file: AutoCAD drawings are kept as they came, scanned for malware and delivered. Export an ASCII DXF for a map layer. |
| Other files | .e57, .xml, .csv, .txt and any other extension | A kept file, kept as it came and never drawn. |
GISweaver identifies a file by its content, not by its name, so renaming a file does not make it an accepted format. A kept file is not drawn on the map, and it enters a release only when someone includes it.
Files that are refused¶
| File | Why | What to do |
|---|---|---|
| A program, script, disk image or web page (for example .exe, .sh, .bat, .msi, .html, .svg) | These can run code. | Send the data they carry in an ordinary format. |
| A macro-enabled Office file (.docm, .xlsm, .pptm, or a .doc, .xls or .ppt that carries a macro project) | The macro can run code. | Save it without the macro. |
| A file whose name does not match its content, such as a DWG drawing named .url | A file's name must carry the extension of what it contains. | Give it the right extension. |
| A text, XML or KML file in an encoding the check cannot read | The check reads UTF-8, UTF-16, US-ASCII, ISO-8859 and Windows-125x. | Save it as UTF-8. |
| A file over a size limit | See the limits below. | Split it into smaller files. |
A text, CSV, XML or KML file is read end to end for scripts and links that run code. A file that cannot be fully read in the time allowed is held with a sentence saying so, not refused. A very large XML or KML file may be held because checking it takes longer than allowed.
Malware scans and downloads¶
Files are checked for their type and that they are whole, and scanned for malware before they reach another organisation. A file crosses only once its malware scan has found no threats. A clean scan is not a certificate that a file is free of malware, so add only files you have checked yourself.
Download original works while the release, your permission and the access period allow it. A checksum helps detect a changed file; it does not certify the survey's legal status, coordinate system or accuracy.
If a file is left out of a download¶
| Reason | What you get |
|---|---|
| The scan flagged the file, could not check it, or is still checking it | The download carries the other files and a note that names each file left out and why. It is refused only when no file may be sent. |
| The file is outside the permitted selection | The file is left out and recorded in the list of files. |
| A client reviewer from another organisation added the file, and the scan flagged it | The file is refused to your organisation too. |
Convert a file for the map¶
GISweaver draws a KML, KMZ, GeoPackage or zipped Shapefile as it is. To prepare a GeoJSON or ASCII DXF copy instead, confirm the source file's coordinate system with the person who produced it: a conversion cannot repair a missing or wrong one. Keep the original with the converted copy, and compare the two before you upload.
| From | To | The software maker explains it |
|---|---|---|
| Shapefile | GeoJSON in EPSG:4326 (WGS 84) | QGIS: creating a new layer from an existing layer |
| ArcGIS feature layer | GeoJSON | ArcGIS Pro: Features To JSON |
| DWG | ASCII DXF, not binary | AutoCAD: SAVEAS and DXF Options |
A conversion can alter curves, fields, precision or elevation values. If the original is part of the handover, upload it too: a DWG or a zipped Shapefile is kept and delivered like any other file.
Fixed limits, for every organisation¶
These do not change with your plan.
| What | Limit |
|---|---|
| One file, kept or drawn | 12 GiB |
| One LAS or LAZ point cloud, expected to convert | About 15 GB of point data once unpacked. A larger cloud is kept as its original for download and not drawn; split it into smaller files to draw it. |
| One GeoJSON file | 512 MiB and 500,000 features |
| One feature in a GeoJSON file | 64 MiB |
| One DXF file | 512 MiB |
| One KML, KMZ, GeoPackage or zipped Shapefile | 512 MiB (a larger one is kept as a file and not drawn) |
| Survey exports an organisation may issue | 2,000 exports or 2 GiB |
- A GeoJSON or DXF file above its reading limit is kept for download and not drawn.
- JSON that is not a FeatureCollection is kept as text.
- A BigTIFF raster is kept without a preview or map view.
- The release states why an original was not drawn.
Other limits on a file¶
Your plan sets the limit for one file, the uploads each month and your storage, and those apply first. The Files strip states your plan's limit for one file to Owners, Admins, Billing managers and Auditors, and refuses a larger file before it is sent: see What your plan allows per file.
| Limit | What it caps | Past it |
|---|---|---|
| One file | The size of each file, kept or drawn | The file is refused before it is sent |
| Uploads a month | How many uploads your organisation may make | Your plan is full for uploads this month. It refills on the first day of the next calendar month. |
| Storage | How much your organisation holds | A sentence about storage |
A kept file (a PDF, a photo, a video or an archive) is held to the same limit for one file as every other file, and its size is set aside from your storage when the upload starts. Publish adds no stored copy, so it is never refused for storage.
Where to look:
| What you need to check | Where to look |
|---|---|
| Your plan's limits and what you have used | Console → Organisation → Billing → Plan and usage |
| The plans on sale | Pricing and Plans |
| What an upload is doing, and why it was refused | The project's Files list or Console → Uploads; see the file statuses |
| Why an export is incomplete | The Export panel and its preview or warning |
| A delivery's access period and download state | Console → Deliveries |
File statuses¶
The Uploads page and a project's Files list give each file one of these statuses: see Follow an upload.
| Status | What it means |
|---|---|
| Waiting | Being read, waiting for a free upload slot, paused, being sent from another tab, or already uploaded and waiting for other files to finish processing. The line under the name explains which. Keep the tab open. Closing the tab now leaves it unfinished. |
| Uploading | On its way. The line under the name says Finishing the upload once every part is in. |
| Stalled | The transfer stopped part-way and nothing has arrived for a while. Resume it from the same device, or cancel it. |
| Not confirmed | You cancelled it and GISweaver did not confirm the cancellation; see Cancel an upload. |
| Checking | Arrived; its checks are running. Closing the tab does not stop this. |
| Processing | Being made ready for the map. The line under the name says which step, such as Converting the file. |
| Ready | Done. A kept file (a photo, a PDF, a video or an archive) reads Internal only beside it. |
| Partial | On the map, with some drawing entities left out: see Understand a drawing converted in part. |
| Original only | Kept as the original; there is nothing in it to draw on the map. The line under the name says why, from the moment it is filed in the draft. |
| Failed | Processing stopped, or the transfer ran out before the whole file arrived. The line under the name says why. |
| Refused | Turned away by its checks, or by your plan before it was sent. |
| Deleted | Somebody deleted it from its project. A deleted file can be restored while its stored copy is kept: see Restore or permanently delete a file. |
A point cloud too large to draw is kept as Original only. Split it into smaller files to draw it on the map. Other conversion errors, such as malformed point data or running out of memory, still fail.
A file read as Original only is not lost: it is stored exactly as you sent it and can be downloaded. In the project's Files list the reason sits under its name and, again, in its details, so you can decide what to do before you publish: a file too large to draw can be split, and a format the converter does not read can be exported again.
Why a file stopped¶
What a file's reason says in the common cases, and what helps: see Fix a file that stopped.
| The reason says | What to do |
|---|---|
| This DXF is binary; save it as ASCII DXF and upload again. | Save it as ASCII DXF in your CAD software, then Replace file. |
| Nothing in this file lies inside the project's coordinate zone … | The file is in another coordinate system. Check it, then Replace file, or add it to a project whose zone covers that ground. |
| The coordinate system in this file is not one the converter recognises … | Export it with a standard EPSG coordinate system, then Replace file. |
| This point cloud is compressed in a way the converter could not read … | Export it again as a standard LAZ or as an uncompressed LAS, then Replace file. |
| This file took longer to process than the time allowed for a file of its size … | Split it into smaller files and send those, or Retry. |
| This file needs more memory to process than one conversion is given … | Split it into smaller files and send those. |
| The coordinate system this point cloud declares does not match where its points are … | The header names a coordinate system its points do not lie in. Check the coordinate system it was exported with, then Replace file, or add it to a project whose zone covers that ground. |
| This file is larger than one conversion accepts … | Split it into smaller files and send those. |
| Processing stopped because of a fault on our side … | Retry. |
| Processing stopped because the worker running it was restarted … | Retry. |
| Processing was interrupted by a fault on our side and will be retried automatically. Nothing is needed from you. | Nothing. GISweaver tries again by itself; the file is not stopped. This one fixed sentence is all a retry shows, whatever went wrong inside. |
| Processing stopped because the converter tried an operation it is never allowed to make … | Report a problem and name the file; support has the details. Retry is not offered, because the same file would stop the same way. |
| Processing stopped; support has the details. | Report a problem, and quote the reference the sentence names. |
Retry is never offered for a file refused for its format, its coordinate system or its size, because the same bytes would be refused the same way. A file in a published release does not offer it either.
A file over your plan's limit for one file, or over the most one file may be, is refused before it is sent and never becomes a row: see Add files to a project.
Upload states¶
A transfer that is not Stalled has its own control: see Resume an interrupted upload.
| The row reads | Select |
|---|---|
| Waiting, Paused: you signed out or switched organisation while it was sending | Resume upload on the row or in its details |
| Waiting, In another tab: another tab of this browser is sending it | Upload from this tab, after you close the other tab, or let that tab finish |
For someone without a GISweaver account¶
To tell a surveyor or a client what to send you, share the public page Supported formats. It lists the same formats for anyone to read.