Geospatial survey delivery, from the surveyor to the client
Upload survey files to a GISweaver project, review the draft if needed, then publish a fixed release and deliver it to a client organisation or by expiring link. Clients inspect and download the files in a browser. Delivery records do not verify survey accuracy or fitness for purpose.
The sequence
Prepare the survey
Upload the survey files to a project. GISweaver checks what each file really is (not just its name). Programs, scripts, disk images, macro-enabled Office files and web pages are refused. Other files are checked at intake. Handoff normally requires a malware scan reporting no threats; oversized validated and converted spatial originals have a labelled exception. Type validation is not malware clearance. See Security and data residency for the handoff rules.
Publish a versioned release
A release is a numbered, fixed copy of the survey. Once published it never changes. A correction becomes a new release.
Deliver to a client organisation, or send a link
Name the receiving organisation by the code it gives you, or create an expiring link that opens without an account. You choose how long access lasts and write a short message.
The client reviews and downloads
They open the release in a browser and download the files. An organisation takes the files as one archive or one at a time, and a receipt is written once every file has finished downloading; a link recipient downloads them one at a time, and each opening and download is recorded for the sender. Check the files you saved against the release’s file list.
Optional delivery control
Withdraw or end a delivery
A delivery to an organisation may wait for a set time (the delivery hold) before it can be downloaded. You can withdraw it during the hold. A link can be ended at any time.
What files work
GeoJSON and ASCII DXF become map layers a client can open and measure. LAS and LAZ point clouds open in the 3D view, for you in your own project and for anyone you send a link to. A delivery to another organisation opens as its 2D layers. Every other file a survey firm uses, DWG drawings, PDFs, ZIP archives and photos included, is kept with the release and reaches another organisation only once its malware scan is clean.
A PDF, and a TIFF that is not an elevation model, is also given a preview of its pages when the release is published: kept with the release, not counted towards your storage, and readable in your organisation on a phone or a desktop without downloading the file. The original stays in your project; a PDF reaches another organisation only once its malware scan is clean.
What does the receiving organisation need?
- To receive a delivery into their own organisation: a GISweaver organisation of their own, on any plan including the free one. To open a link: nothing, no account at all.
- No installation and no desktop software. They sign in to the same web application you do, in an ordinary browser.
- Their organisation code, which they read off their own settings page and give to you. You name them by that code, and their organisation name is shown to you before anything is sent.
Who pays
- The surveyor. The delivered files stay on the sending organisation and count against its storage until it deletes them permanently, and sending is available on every published plan.
- Receiving is free. It uses none of the receiving organisation’s storage, and nothing on the receiving side is refused. Copying the release into an account of their own is not available today.
- Extending an access period is free, and can be done as often as the surveyor needs.
Old versions never change
A published release cannot be changed. A correction is issued as a new release that marks the previous one superseded, so the version a client reviewed in March is still exactly what they reviewed in March.
How the files are downloaded
- An organisation downloads one archive with a file list showing every file and its checksum, or one file at a time by name. A link recipient downloads one file at a time.
- Files are downloaded through GISweaver only: an organisation under its own sign-in, a link recipient under the expiring link the sender chose. They are never downloaded from a public storage address.
- A download is refused, with the reason, if the surveyor has deleted the files, the delivery hold has not passed, the sending organisation is frozen, the delivery has been withdrawn, the link has been ended or has expired, or the access period has ended. Files blocked by the malware handoff rules are withheld and named, and the others are still sent. Oversized spatial originals that qualify for the validated-and-converted exception carry a too-large-to-scan label.
What the receipt records
A receipt is stored on both sides once every file in the delivery has finished downloading. An interrupted download does not count. The receipt does not confirm that the browser saved usable files; check the files you saved against the release’s file list.
It names:
- the two organisations, by identifier and legal name, and no individual person
- the project label, and the release with the date it was published and its checksum
- every file handed over, with its size and its SHA-256 checksum, and whether it left as an archive or on its own
- the time the last file finished downloading, and whether the download came from inside or outside India, where GISweaver stores data (never the address)
GISweaver signs it, so either organisation can show it to someone else as proof without asking us to confirm anything.
A receipt is a record of delivery and download activity. It is not a certification of the survey itself: whether the survey is correct, complete and fit for its purpose remains the responsibility of the organisation that published it.
When access ends
The surveyor sets the access period. It defaults to one year, may be up to two years when the delivery is made, and can be extended free of charge at any time, each extension setting a new end no more than a year ahead.
When the access period ends the client stops being able to download. The receipt is kept on both sides for as long as Alonstech operates the Platform, and a client who wants to keep the files downloads them before then.
Support, exports and continuity
For help using GISweaver or arranging beta access, contact support. Download the release files and keep your own copy for your records. The Terms describe retained-data export rights, service-discontinuation arrangements and availability limits; beta availability is not guaranteed.
Ready to look at the product?
See plans and prices, or ask a person.