Data & quality
Make the uncertainty
part of the answer.
A useful geospatial result explains its origin, method and limits. The actual quality and data-handling commitments are agreed for each engagement.
A practical quality framework
Identify the source
Record acquisition dates, source resolution, licences and whether observations are measured or estimated.
Define the reference
Specify the coordinate reference system, horizontal and vertical datum, epoch and transformations where relevant.
Validate the result
Agree acceptance criteria, distinguish precision estimates from measured accuracy and report gaps or outliers.
Position quality is contextual
GNSS quality depends on geometry, receiver capability, obstruction, multipath, corrections and processing. Fix type and HDOP alone do not establish a guaranteed position error.
Use horizontal/vertical precision estimates only where the source supplies them. Record the statistic and units, timestamp and correction context. Validation against independent control is a separate step.
GPS.gov: accuracy factorsData handling and interoperability
Agree the controls
Before sharing project data, agree its classification, authorised users, hosting and processing locations, retention, backups and permitted use. Do not send sensitive datasets through an initial enquiry.
No blanket security certification or hosting-location guarantee is made by this website.
Indian geospatial context
Applicable data, mapping, field-access and hosting requirements must be considered for the specific engagement. DST’s geospatial guidelines include conditions for certain data and activities. This website does not certify project compliance.
Read the official DST guidelines