DIGIT Docs
Microplanning 0.1
  • DIGIT Knowledge Base
  • Local Governance
Microplanning 0.1
  • Introducing Microplanning
    • Release Notes
      • v0.1 Release Notes
        • Release Checklist
        • Technical Release Summary
        • Master Data Management Service (MDMS) and Configuration updates
        • Service Builds
        • UI/UX Audit
  • PRODUCT SPECIFICATION
    • User Manual
    • Product Requirement Document
      • SOPs
        • Guidelines
  • TECHNOLOGY
    • Architecture
      • High Level Design
      • Low Level Design
        • Plan Management
        • Census Management
        • Microplanning UI
          • System Admin Flow
          • Population Data Approval
          • Facility Catchment Mapping
          • Microplan Estimation Approval
      • Services
        • HCM Microplan Web
          • User Interface Design
          • Set Up Microplan
            • Microplan Details
            • Boundary Selection
            • Data Management
            • Microplan Assumptions
            • Formula Configuration
            • User Tagging
            • Summary Screen
          • User Management
            • Bulk User Create
            • Download Users Credentials
          • Supervisor Flows
            • User Interface Design
            • My Microplan
            • Select Activity
            • Validate And Approve Population Data
              • Village Details
            • Assign Facility To Villages
              • Village Assignment And Unassignment to Facility
            • Validate And Approve Microplan Estimation
          • Open Microplans: System Admin
    • Specification
      • Plan Service
      • Resource Generator Service
      • Census Service
  • SETUP
    • Installation
    • Configuration
      • Advanced Configurations
    • QA Test Cases
Powered by GitBook

All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.

On this page
  • Input File Validation
  • GeoJSON
  • Shapefile
  • Excel

Was this helpful?

Export as PDF
  1. PRODUCT SPECIFICATION
  2. Product Requirement Document
  3. SOPs

Guidelines

PreviousSOPsNextArchitecture

Last updated 5 months ago

Was this helpful?

Input File Validation

GeoJSON

  • The GeoJSON file should meet the specification

  • The top-level element should be of type “FeatureCollection”

  • All the Features within the FeatureCollection should have geometries of the same type (i.e. All should be points, or all should be MultiPolygons, and so on).

  • The coordinates should be in the valid range of Latitude & Longitude. (Valid range for Latitude is -90 to +90; Valid range of Longitude is -180 to +180)

  • If the third coordinate (i.e. the height value) is present, then it will be ignored.

  • All the features should have properties with the same set of keys.

  • In the Properties object, the values for fields that represent a Numeric Value, should not be quoted with double quotes, (i.e. population of 10,000 should be represented as “population” : 10000 and not “population” : “10,0000”

Shapefile

  • A shapefile consists of multiple files with the same name and different extensions. Mandatory ones are .shp, .shx & .dbf. You could also have .prj, .sbx & .sbn.

  • The shapefile should be in the WGS 84 lat-long coordinate system. (i.e. EPSG:4326). If the .prj file is missing, then the data is assumed to be in the WGS 84 lat-long coordinate system.

  • Data in any other coordinate system, even if indicated so in the .prj file will not be considered valid.

  • The coordinates should be in the valid range of Latitude & Longitude. (Valid range for Latitude is -90 to +90; Valid range for Longitude is -180 to +180).

  • Field Names are limited to 10 Characters as per the Shapefile Specification.

  • The Various fields in the attribute table should have the appropriate data types. (i.e. Numeric Values should be in fields of the type Short Integer, Long Integer, Float, or Double)

  • The User should zip up all the files in Zip format, and upload them into the system. At a minimum, the system needs .shp, .shx & .dbf files

  • The total size of all files together should not exceed 2GB

Excel

  • The Latitude & Longitude fields should have data in Degree Decimal and Degree Minute Seconds ( Value should be 12.3455 & not 12° 20' 43.7994")

  • Any leading & trailing whitespace characters (Spaces, Tabs, Carriage Return, new line etc) will be stripped out from all fields

RFC 7946 GeoJSON