Indian geospatial regulation
High-accuracy spatial data of Indian territory carries rules about who may collect it, what may be labelled on it and where it may be processed. Here is the part that concerns a processing service, in the wording of our own published terms.
The framework
Alons Advanced Technologies Private Limited operates LAZweaver in accordance with the Guidelines for Acquiring and Producing Geospatial Data and Geospatial Data Services Including Maps (Department of Science and Technology, 15 February 2021) and the National Geospatial Policy, 2022 (S.O. 6095(E), notified 28 December 2022, which does not supersede the 2021 Guidelines).
Threshold values of spatial accuracy
The DST Guidelines set threshold values of spatial accuracy, of which the two relevant to terrestrial survey work are one metre horizontal and three metres vertical, at one RMSE. Airborne, terrestrial and mobile LiDAR of the kind LAZweaver processes is ordinarily finer than those values, and a customer should assume that its clouds are.
In practice that means you should assume the rules for finer-than-threshold data apply to your survey, rather than hoping they do not.
Where Indian data is processed and stored
All processing of Indian point-cloud data on LAZweaver takes place, and all such data is stored, exclusively within the India data plane (in-mumbai-1, AWS Mumbai). Point coordinates, classified clouds and derived surfaces do not transit foreign edge proxies, international CDN workers, overseas key-value stores or international log aggregators.
The only edge services in front of this product are authoritative DNS and the sign-in challenge. The API hostname a survey file is uploaded through is answered by DNS and then reached directly, with no proxy in between — a decision recorded in the infrastructure rather than left as an intention.
The negative list
The Guidelines provide for a negative list of sensitive attributes that may not be shown or labelled on a map. Explanation 1 to paragraph 8(iii) states expressly that there will not be any negative list of prohibited areas.
This is the point most often got wrong in summaries of the Guidelines, which is why it is quoted here in the Department's own terms: the restriction is on labelling and depiction of specified attributes, not a prohibition on collecting data within any area.
What remains yours
Verifying that a dataset does not label or depict a sensitive attribute, observing the categories the Guidelines reserve to Indian entities, and holding every permission an acquisition required — including DGCA authorisations for drone flight — remain the customer's own responsibilities.
A processing service can say where it processes and what it does not publish. It cannot hold your permissions for you, and it should not imply that using it settles a question about your acquisition.
If you are outside India
LAZweaver sells to businesses in other countries from an Indian cell, and says so plainly rather than implying a local presence it does not have. A customer processing data elsewhere is responsible for that jurisdiction's own rules on survey, acquisition, mapping and export.
Read the source
Every statement on this page is quoted from our published documents rather than paraphrased from them.