3D ULPIN Generation and vertical Property Mapping SYstem

The receipts 🧾

Every red flag on this statement, in full. These are the four places it bites.

1. Exhibit A

   Indian apartment floor plans do not exist as machine-readable data, so the step from a segmented floor to individual flat boundaries — the actual ownership unit — has to be hand-digitised and that limitation must be stated rather than hidden

2. It gets worse

   The description never defines what a 3D ULPIN is, so you are inventing the central artifact and must justify your encoding against the existing ULPIN scheme when a DoLR judge asks

3. Still reading?

   High-density Indian LiDAR coverage is scarce; teams often end up using a foreign city's open point cloud, which weakens the India-specific claim considerably

4. And the finisher

   3D web visualisation is a genuine time sink and a team that underestimates CesiumJS ends up with working segmentation and nothing to show it in

The damage report 📉

Every score this statement earned, and what each one actually costs you.

• Feasibility

  3/5

  Buildable. Not comfortably. There is a week in here you have not planned for yet.

  Open point cloud data, DSMs and mature libraries like PDAL and Open3D make automated building extraction and floor segmentation genuinely achievable, and the LADM 3D cadastre standard gives you a model to conform to, but Indian building floor plans are not available as data anywhere, so the sub-parcel delineation inside each floor has to be drawn by hand or synthesised.

• Innovation scope

  4/5

  There is something genuinely new here. Do not bury it under another dashboard.

  The description names inputs and desired capabilities but never specifies the ULPIN encoding scheme, the segmentation method or the data model, and 3D cadastre in India is genuinely unsettled ground, so the core design decision — what a 3D ULPIN actually is — is entirely yours.

• Clarity

  3/5

  Clear enough to start, vague enough to drift. Write the scope down and stop reinterpreting it weekly.

  The inputs and AI capabilities are listed cleanly, but the central deliverable is left undefined: it never says what a 3D ULPIN looks like, how it relates to the existing 14-character ULPIN, or how ownership rights attach to a volume, which is the whole substance of the problem.

• Acceptance potential

  4/5

  Strong footing before you have written a line. Try not to waste it.

  This is a genuinely unsolved problem in Indian land administration rather than a rebuild of something deployed, the international standards work exists to anchor it, the demo is distinctive, and the Space Technology mislabel keeps land-records teams from finding it.

• Effort

  Heavy

  Heavy. Somebody on this team is not sleeping in week three. Pick who, on purpose.

  Point cloud processing, automated building extraction, floor segmentation, volumetric parcel construction, an identifier scheme, topology validation and a 3D web viewer is seven pieces, and the 3D viewer alone consumes far more time than teams expect.

• Demo-ability

  Medium

  Demoable, if you rehearse it. Nobody rehearses it.

  A rotating 3D building where clicking a floor returns an ownership record is visually memorable and instantly legible to a non-technical judge, though the segmentation quality only holds up on the building you tuned it against.

• Data

  None supplied

  No dataset comes with this one, so every accuracy figure you quote is a number about labels you invented.

  Nothing is provided with the statement. You are sourcing, cleaning and labelling it yourself, and that work is invisible in the demo but very visible in the questions.

The demo they will have already seen 🪞

Somewhere around 95–220 teams are heading here, and the description is doing the choosing for most of them. They will read the same brief, reach the same architecture, and build a version of the same demo you are planning. Being correct is the floor. If your five minutes could be swapped with the team before you and nobody in the room would notice, you have not picked badly — you have built predictably, which costs exactly the same and hurts more.

What survives 🛡️

The ground worth standing on when the questions start.

• 3D cadastre is genuinely unsolved in India — you are not competing against an existing national system the way most land-record statements are
• The ISO 19152 LADM and CityGML standards already define volumetric parcel modelling, so you can conform to published work instead of defending an invented data model
• The theme is filed under Space Technology, so teams browsing Smart Cities or land governance will not surface it, and the title's typography suggests casual browsers will skip past it too