Map My Block

The description states that Map My Block allows census enumerators to:

• Upload government-provided HLB maps.
• Align these with OpenStreetMap.
• Draw block boundaries and mark houses, roads, public institutions, and landmarks.
• Work offline using local storage (IndexedDB, localForage, service workers).
• Export completed maps for submission.

It is described as a mobile-first Progressive Web App built with Next.js, React, and TypeScript. The tool integrates OpenStreetMap data, OpenAI Codex (for development), and Open Buildings dataset to reduce manual effort.

Inference The product appears to be an offline-capable mapping interface tailored for field-based census work in India.

The author positions Map My Block as a solution to inefficiencies in the current Indian census mapping process. The description claims:

• Government tools exist for data collection but not for final map creation.
• Manual sketching leads to inconsistency and time delays.
• The tool aims to digitize and improve accuracy of block-level mapping.

It is framed as a practical, user-centric solution developed directly from feedback with enumerators.

Inference The positioning reflects an attempt to address real-world workflow pain points rather than a generic or hypothetical use case.

The description states that the primary users are census enumerators in India, particularly those working with HLB maps. These individuals reportedly:

• Visit hundreds of houses.
• Note landmarks and sketch block boundaries manually.
• Face challenges due to inconsistent drawing skills and lack of digital tools.

Inference The ICP is likely field-based, non-technical users who require offline-capable tools for mapping tasks in rural or low-connectivity environments.

Not evidenced. The description does not mention any pricing model, monetization strategy, or business model. It is presented as a hackathon project with no indication of commercial intent or revenue streams.

The tool is built using:

• Frontend: Next.js, React, TypeScript
• Mapping: Leaflet, OpenStreetMap, OpenAI Codex (development aid)
• Offline support: IndexedDB, localForage, service workers
• Data sources: OpenStreetMap, Open Buildings dataset, HLB maps
• Features: Drag/rotate/scale alignment, automatic fetching of reference layers, export capabilities

The author notes that the team had to iterate on product understanding and technical challenges like touch interaction management and map alignment.

Inference Technical delivery shows a focus on usability and offline functionality. The use of PWA technologies suggests an intent to support field deployment in low-connectivity areas.

Not evidenced. There is no mention of:

• Customers or users
• Revenue or funding
• Product adoption or usage metrics
• Deployment beyond the hackathon context

The description states that this was a hackathon submission and does not indicate any follow-up or real-world implementation.

Not evidenced. The description does not reference existing tools, competitors, or market landscape for census mapping software in India or globally.

• No traction evidence: The project is described as a hackathon submission with no indication of real-world usage.
• Unverified claims: All stated benefits and features are self-reported without independent validation.
• Limited scope: No mention of integration with official census systems or scalability beyond prototype-level functionality.
• Founder team size: Only one member listed (archana_prabhat T K), which may limit execution capacity.

1. Has the tool been tested in real field conditions with enumerators?
2. Are there any partnerships or pilot programs with government agencies or census departments?
3. What is the current status of the product — prototype, alpha, beta, or production-ready?
4. How does it integrate with existing census data collection systems?
5. Is there a plan for ongoing maintenance or updates post-hackathon?