8080.AI
DesignReqsTasksUser FlowArchitecture
Log inSign up for free

peta3d-landu-leko

byJoshua Purba

https://peta-3-d-landu-leko--juansapangallo8.replit.app/ Tolong perbaiki bentuk geometri 3D pulau Landu Leko agar 100% presisi dan akurat sesuai batas wilayah spasial resminya. buatlah sesuai dengan peta pulau rote di file pdf yang saya kasih, bentuknya harus sama persis tidak boleh beda. Harus sama dan bentukya 3d Saat ini bentuknya masih terlalu sederhana dan berbentuk blok. Mohon perbarui kodenya dengan ketentuan berikut: Gunakan data batas wilayah (GeoJSON) atau data vektor ketinggian presisi untuk wilayah Kecamatan Landu Leko, Kabupaten Rote Ndao (koordinat sekitar WGS 1984 Zone 51S). Bentuk garis pantai, teluk, semenanjung, serta danau-danau di bagian dalam pulau (seperti Danau Usamu/Danau Landu) harus persis mengikuti peta topografi resmi. Lakukan kalkulasi extrusion/3D terrain mesh berdasarkan kontur ketinggian sebenarnya dari data topografi (KJP = Tidal Mudflat, KPG = Karst Plateau, NNE = Estuarine, serta danau-danau). Pastikan label zona (KJP, KPG, NNE, Danau) diletakkan secara akurat pada koordinat spasial masing-masing zona. Berikan kontrol rotasi, zoom, dan kemiringan (tilt) 3D yang mulus menggunakan Three.js / Deck.gl."

No preview

Comments (0)

No comments yet. Be the first!

System Requirements

Proposed change+52−41on v2
Page 1 of 16

System Requirements Document

Page 2 of 16

1. Introduction

This System Requirements Document (SRD) defines the requirements for an interactive, web-based 3D visualization of Kecamatan Landu Leko, Kabupaten Rote Ndao, East Nusa Tenggara, Indonesia. The system reconstructs the district's island geometry and terrain from official spatial boundary and topographic source data so that the rendered 3D form matches the district's authorized administrative and topographic map.

The reference source is the Topographic Map of Landu Leko District, Rote Ndao Regency, East Nusa Tenggara, produced by the Department of Geography Education, Faculty of Teacher Training and Education, Universitas Nusa Cendana, at a map scale of 1:30000, with a base map scale of 1:25,000 sourced from the Indonesian Topographic Base Map and the Ministry of Energy and Mineral Resources (ESDM).

The purpose of this rewrite is to replace the current simplified, block-like island model with a precise, topography-driven 3D model whose coastline, bays, peninsulas, inland lakes, elevation relief, landform-zone types, scale reference, and labels are spatially faithful to the official map.

The user's explicit requirement is that the 3D island geometry of Landu Leko be 100% precise and accurate to its official spatial boundary, that the island shape be exactly the same as the Rote island map in the uploaded PDF with no deviation whatsoever, and that the result be a true 3D form rather than the current simple block shape. The current deployed Replit application (https://peta-3-d-landu-leko--juansapangallo8.replit.app/) renders a simplified, block-like island geometry; that geometry is obsolete and must be fully replaced by the topography-driven model defined in this document.

Page 3 of 16

2. System Overview

The system is a single interactive geospatial web application that:

  • Loads district boundary and elevation data for Kecamatan Landu Leko in the coordinate reference system WGS 1984 – Zone 51S (Transverse Mercator projection, Grid Geografi grid system).
  • Builds an extrusion-derived 3D terrain mesh from real topographic contour and elevation-point data.
  • Renders the coastline, bays, peninsulas, and inland lakes (including Danau Usamu / Danau Landu) as regionally accurate geometry.
  • Renders each landform type as a distinct spatial region using the source map's landform classification.
  • Displays the landform legend, scale reference, and zone labels.
  • Places categorical landform-zone labels at their true spatial coordinates.
  • Provides smooth rotation, zoom, and tilt (camera controls) in a live 3D scene.
  • Replaces the existing simplified, block-like island geometry with a precise, topography-driven 3D model that matches the official topographic map shape exactly.

The landform and feature categories that must be represented are defined by the source legend:

  • KJP — Tidal Mudflat Plain (Flat)
  • KPG — Karst Plateau (Undulating to Hilly)
  • NNE — Estuarine and Merged River Plain (Flat to Gently Sloping)
  • Lake — inland water bodies (e.g., Danau Usamu / Danau Landu)
  • Elevation Point, Contour Line, and District Administrative Boundary as supporting feature classes.

3. Functional Requirements

Page 4 of 16

3.1 Geographic Accuracy and Boundary Reconstruction

  1. As a cartographer, I want the 3D island geometry to be derived from official district administrative boundary data (GeoJSON) so that the rendered island matches the authorized spatial boundary of Kecamatan Landu Leko exactly.
  2. As a cartographer, I want the 3D model to use the horizontal datum WGS 1984 – Zone 51S with Transverse Mercator projection and the Grid Geografi grid system so that all geometry is positioned in the correct coordinate reference.
  3. As a cartographer, I want the coastline to precisely follow the official topographic map so that no artificial or simplified boundary is introduced.
  4. As a cartographer, I want bays to be reproduced exactly as they appear on the official map so that the coastal indentation pattern is faithful.
  5. As a cartographer, I want peninsulas to be reproduced exactly as they appear on the official map so that protruding landforms are spatially correct.
  6. As a cartographer, I want the island outline to be identical to the shape of the Rote map provided in the uploaded PDF so that no shape deviation exists between the model and the official map.
  7. As a cartographer, I want the previous block-like, oversimplified geometry fully replaced so that the model is no longer a coarse block approximation.
  8. As a cartographer, I want the District Administrative Boundary to be rendered as a distinct boundary feature so that the legal spatial extent of the district is visible in the 3D scene.
  1. As a cartographer, I want the 3D island geometry to be 100% precise and accurate to the official spatial boundary of Kecamatan Landu Leko so that the model is a faithful representation of the district's legal extent.
  2. As a cartographer, I want the island shape to be exactly the same as the Rote island map in the uploaded PDF, with no shape difference permitted, so that the model is a direct 3D counterpart of the official map.
  3. As a cartographer, I want the model delivered as a true 3D form (not a flat or block approximation) so that the island reads as a spatial object in three dimensions.
Page 5 of 16

3.2 Terrain and Elevation Modeling

  1. As a cartographer, I want an extrusion / 3D terrain mesh calculated from real topographic elevation contours so that terrain relief reflects actual surveyed elevation.
  2. As a cartographer, I want the model to incorporate precise vector elevation data for Kecamatan Landu Leko so that vertical relief is accurate.
  3. As a cartographer, I want high-elevation areas within the KPG (Karst Plateau) zone rendered as undulating-to-hilly relief so that the plateau's character is visible in 3D.
  4. As a cartographer, I want the KJP (Tidal Mudflat Plain) zone rendered as flat terrain so that the mudflat plain's low-relief character is represented.
  5. As a cartographer, I want the NNE (Estuarine and Merged River Plain) zone rendered as flat-to-gently-sloping terrain so that the estuarine plain's slope character is represented.
  6. As a cartographer, I want contour lines and elevation points to drive the terrain surface so that the vertical geometry corresponds to the map's elevation values.
  7. As a cartographer, I want inland water bodies to be modeled as surface depressions / flat lake surfaces within the terrain mesh so that lakes appear as distinct flat features rather than terrain.
  1. As a cartographer, I want an extrusion / 3D terrain mesh calculated from real topographic elevation contours so that terrain relief reflects actual surveyed elevation.
  2. As a cartographer, I want the model to incorporate precise vector elevation data for Kecamatan Landu Leko so that vertical relief is accurate.
  3. As a cartographer, I want high-elevation areas within the KPG (Karst Plateau) zone rendered as undulating-to-hilly relief so that the plateau's character is visible in 3D.
  4. As a cartographer, I want the KJP (Tidal Mudflat Plain) zone rendered as flat terrain so that the mudflat plain's low-relief character is represented.
  5. As a cartographer, I want the NNE (Estuarine and Merged River Plain) zone rendered as flat-to-gently-sloping terrain so that the estuarine plain's slope character is represented.
  6. As a cartographer, I want contour lines and elevation points to drive the terrain surface so that the vertical geometry corresponds to the map's elevation values.
  7. As a cartographer, I want inland water bodies to be modeled as surface depressions / flat lake surfaces within the terrain mesh so that lakes appear as distinct flat features rather than terrain.
  8. As a cartographer, I want the extrusion / 3D terrain mesh to be computed from the actual elevation contours of the topographic data for the KJP (Tidal Mudflat), KPG (Karst Plateau), NNE (Estuarine), and the inland lakes so that each landform's real relief is reproduced.
Page 6 of 16

3.3 Landform Types and Classification

  1. As a cartographer, I want the KJP (Tidal Mudflat Plain, Flat) landform type rendered as its own distinct spatial region so that the mudflat plain is classified and displayed separately from other landforms.
  2. As a cartographer, I want the KPG (Karst Plateau, Undulating to Hilly) landform type rendered as its own distinct spatial region so that the karst plateau is classified and displayed separately from other landforms.
  3. As a cartographer, I want the NNE (Estuarine and Merged River Plain, Flat to Gently Sloping) landform type rendered as its own distinct spatial region so that the estuarine plain is classified and displayed separately from other landforms.
  4. As a cartographer, I want the Lake landform type rendered as its own distinct spatial region so that inland water bodies are classified and displayed separately from land landforms.
  5. As a viewer, I want a Landform Types legend displayed alongside the 3D scene listing KJP, KPG, NNE, and Lake with their full descriptive names and slope/relief character so that I can interpret each rendered landform region correctly.
  6. As a viewer, I want the landform legend entries to correspond visually to the colors/fills used for each landform type in the 3D scene so that I can map legend entries to terrain regions at a glance.
  7. As a cartographer, I want each distinct occurrence of the KPG zone to be rendered and labeled independently so that separate karst plateau patches are each spatially correct.
  8. As a cartographer, I want each distinct occurrence of the KJP, NNE, and Lake zones to be rendered and labeled independently so that multiple patches of the same landform type are each spatially correct.
  1. As a cartographer, I want the KJP (Tidal Mudflat Plain, Flat) landform type rendered as its own distinct spatial region so that the mudflat plain is classified and displayed separately from other landforms.
  2. As a cartographer, I want the KPG (Karst Plateau, Undulating to Hilly) landform type rendered as its own distinct spatial region so that the karst plateau is classified and displayed separately from other landforms.
  3. As a cartographer, I want the NNE (Estuarine and Merged River Plain, Flat to Gently Sloping) landform type rendered as its own distinct spatial region so that the estuarine plain is classified and displayed separately from other landforms.
  4. As a cartographer, I want the Lake landform type rendered as its own distinct spatial region so that inland water bodies are classified and displayed separately from land landforms.
  5. As a viewer, I want a Landform Types legend displayed alongside the 3D scene listing KJP, KPG, NNE, and Lake with their full descriptive names and slope/relief character so that I can interpret each rendered landform region correctly.
  6. As a viewer, I want the landform legend entries to correspond visually to the colors/fills used for each landform type in the 3D scene so that I can map legend entries to terrain regions at a glance.
  7. As a cartographer, I want each distinct occurrence of the KPG zone to be rendered and labeled independently so that separate karst plateau patches are each spatially correct.
  8. As a cartographer, I want each distinct occurrence of the KJP, NNE, and Lake zones to be rendered and labeled independently so that multiple patches of the same landform type are each spatially correct.

3.4 Inland Lakes

  1. As a cartographer, I want the inland lakes, including Danau Usamu / Danau Landu, to be rendered with boundaries that follow the official topographic map exactly so that lake extents are accurate.
  2. As a cartographer, I want lake shorelines to be represented as true spatial polygons within the 3D scene so that lakes are distinguishable from land zones.
  1. As a cartographer, I want the inland lakes, including Danau Usamu / Danau Landu, to be rendered with boundaries that follow the official topographic map exactly so that lake extents are accurate.
  2. As a cartographer, I want lake shorelines to be represented as true spatial polygons within the 3D scene so that lakes are distinguishable from land zones.
  3. As a cartographer, I want the inland lakes in the interior of the island (such as Danau Usamu / Danau Landu) to follow the official topographic map exactly so that no lake boundary is approximated.
Page 7 of 16

3.5 Zone Labeling

  1. As a cartographer, I want the KJP zone label placed at the accurate spatial coordinates of the KJP zone so that the label is geographically correct.
  2. As a cartographer, I want the KPG zone label placed at the accurate spatial coordinates of the KPG zone so that the label is geographically correct.
  3. As a cartographer, I want each distinct KPG zone label placed at the accurate spatial coordinates of its own KPG zone so that every karst plateau patch is labeled correctly.
  4. As a cartographer, I want the NNE zone label placed at the accurate spatial coordinates of the NNE zone so that the label is geographically correct.
  5. As a cartographer, I want the Lake (Danau) label placed at the accurate spatial coordinates of the lake so that the label is geographically correct.
  6. As a cartographer, I want the Elevation Point feature labels/values placed at their accurate spatial coordinates so that elevation readings are readable on the 3D terrain.
  7. As a cartographer, I want the Contour Line feature rendered with its elevation value so that contour relief can be read in the 3D scene.
  8. As a cartographer, I want each landform zone label to be rendered as an in-scene 3D annotation (not a flat fixed overlay) so that labels remain attached to their zones during rotation, zoom, and tilt.
  1. As a cartographer, I want the KJP zone label placed at the accurate spatial coordinates of the KJP zone so that the label is geographically correct.
  2. As a cartographer, I want the KPG zone label placed at the accurate spatial coordinates of the KPG zone so that the label is geographically correct.
  3. As a cartographer, I want each distinct KPG zone label placed at the accurate spatial coordinates of its own KPG zone so that every karst plateau patch is labeled correctly.
  4. As a cartographer, I want the NNE zone label placed at the accurate spatial coordinates of the NNE zone so that the label is geographically correct.
  5. As a cartographer, I want the Lake (Danau) label placed at the accurate spatial coordinates of the lake so that the label is geographically correct.
  6. As a cartographer, I want the Elevation Point feature labels/values placed at their accurate spatial coordinates so that elevation readings are readable on the 3D terrain.
  7. As a cartographer, I want the Contour Line feature rendered with its elevation value so that contour relief can be read in the 3D scene.
  8. As a cartographer, I want each landform zone label to be rendered as an in-scene 3D annotation (not a flat fixed overlay) so that labels remain attached to their zones during rotation, zoom, and tilt.
  9. As a cartographer, I want the KJP, KPG, NNE, and Danau zone labels placed at the accurate spatial coordinates of their respective zones so that every zone label is geographically correct.
Page 8 of 16

3.6 Scale and Map Reference

  1. As a viewer, I want a scale indicator (SCALE) displayed for the map so that distances on the 3D scene can be interpreted against the source map's scale.
  2. As a viewer, I want the scale reference to reflect the published map scale of 1:30000 so that the visualization's scale relationship matches the official map.
  3. As a viewer, I want the base map scale of 1:25,000 recorded as the source scale of the underlying topographic data so that the accuracy ceiling of the geometry is explicit.
  4. As a viewer, I want a graphic distance scale (as on the source map, with distance divisions in km) rendered alongside the 3D scene so that relative distances can be judged visually.
  5. As a cartographer, I want the scale reference to remain consistent when zooming and tilting so that scale interpretation is never misleading.
  1. As a viewer, I want a scale indicator (SCALE) displayed for the map so that distances on the 3D scene can be interpreted against the source map's scale.
  2. As a viewer, I want the scale reference to reflect the published map scale of 1:30000 so that the visualization's scale relationship matches the official map.
  3. As a viewer, I want the base map scale of 1:25,000 recorded as the source scale of the underlying topographic data so that the accuracy ceiling of the geometry is explicit.
  4. As a viewer, I want a graphic distance scale (as on the source map, with distance divisions in km) rendered alongside the 3D scene so that relative distances can be judged visually.
  5. As a cartographer, I want the scale reference to remain consistent when zooming and tilting so that scale interpretation is never misleading.

3.7 Grid and Coordinate Reference Display

  1. As a cartographer, I want the Grid Geografi grid system represented so that geographic coordinate graticule reference is visible/available.
  2. As a cartographer, I want the coordinate graticule values (e.g., 123°15'0"E–123°30'0"E and 10°30'0"S–10°40'0"S) reflected so that the district's geographic position is explicit.
  3. As a viewer, I want a Location Map context available so that Landu Leko District can be located within the broader Rote Ndao / East Nusa Tenggara region.
  1. As a cartographer, I want the Grid Geografi grid system represented so that geographic coordinate graticule reference is visible/available.
  2. As a cartographer, I want the coordinate graticule values (e.g., 123°15'0"E–123°30'0"E and 10°30'0"S–10°40'0"S) reflected so that the district's geographic position is explicit.
  3. As a viewer, I want a Location Map context available so that Landu Leko District can be located within the broader Rote Ndao / East Nusa Tenggara region.
Page 9 of 16

3.8 3D Interaction and Rendering

  1. As a viewer, I want smooth rotation of the 3D scene so that I can inspect the island from any horizontal angle.
  2. As a viewer, I want smooth zoom control so that I can move between district-wide and close-up views of the terrain.
  3. As a viewer, I want smooth tilt control so that I can adjust the vertical camera angle and observe terrain relief and elevation differences.
  4. As a viewer, I want the 3D camera controls implemented with Three.js / Deck.gl so that the scene performs smoothly and consistently in the browser.
  5. As a viewer, I want the scene to render the full district extent (including the anchor coordinates around 123°15'–123°30'E and 10°30'–10°40'S) so that the entire Landu Leko administrative area is visible.
  1. As a viewer, I want smooth rotation of the 3D scene so that I can inspect the island from any horizontal angle.
  2. As a viewer, I want smooth zoom control so that I can move between district-wide and close-up views of the terrain.
  3. As a viewer, I want smooth tilt control so that I can adjust the vertical camera angle and observe terrain relief and elevation differences.
  4. As a viewer, I want the 3D camera controls implemented with Three.js / Deck.gl so that the scene performs smoothly and consistently in the browser.
  5. As a viewer, I want the scene to render the full district extent (including the anchor coordinates around 123°15'–123°30'E and 10°30'–10°40'S) so that the entire Landu Leko administrative area is visible.
  6. As a viewer, I want the rotation, zoom, and tilt controls to be smooth and continuous so that inspecting the precise island geometry never stutters or snaps.

3.9 Data Sources and Reference Fidelity

  1. As a cartographer, I want the model to be built on the Indonesian Topographic Base Map (scale 1:25,000) and ESDM data so that the geometry derives from authoritative sources.
  2. As a cartographer, I want the rendered island to reproduce the reference map at the published map scale of 1:30000 so that scale relationships on the source map remain meaningful.
  3. As a cartographer, I want all landform classes (KJP, KPG, NNE, Lake) to be sourced from the official landform-type classification so that no landform category is invented or omitted.
  1. As a cartographer, I want the model to be built on the Indonesian Topographic Base Map (scale 1:25,000) and ESDM data so that the geometry derives from authoritative sources.
  2. As a cartographer, I want the rendered island to reproduce the reference map at the published map scale of 1:30000 so that scale relationships on the source map remain meaningful.
  3. As a cartographer, I want all landform classes (KJP, KPG, NNE, Lake) to be sourced from the official landform-type classification so that no landform category is invented or omitted.
  4. As a cartographer, I want the geometry to be derived from official district boundary data (GeoJSON) or precise vector elevation data for Kecamatan Landu Leko so that the model is built on authoritative spatial inputs rather than approximations.
Page 10 of 16

4. User Personas

Cartographer / Geospatial Analyst (primary active persona). Prepares, validates, and corrects the boundary and elevation data, verifies that the 3D island shape matches the official topographic map, classifies landform types (KJP, KPG, NNE, Lake), checks zone label placement, and confirms the coordinate reference is WGS 1984 – Zone 51S. This persona owns data accuracy.

Map Viewer / Evaluator (secondary active persona). Opens the 3D scene to inspect the district's island form, reads the legend, scale, and zone labels, rotates/zooms/tilts the model, and verifies visually against the official map. This persona consumes the visualization but does not edit data.

External Reference Sources (system actors, not personas). The Indonesian Topographic Base Map (scale 1:25,000) and the Ministry of Energy and Mineral Resources (ESDM) data are treated as data sources, not users.

5. Core User Flows

Page 11 of 16

Flow A — Cartographer: Building the Accurate 3D Model

  1. Obtain district administrative boundary data (GeoJSON) and topographic elevation data for Kecamatan Landu Leko.
  2. Confirm the data is in WGS 1984 – Zone 51S (Transverse Mercator, Grid Geografi).
  3. Extract coastline, bay, and peninsula geometry and align it to the official map shape.
  4. Extract inland lake polygons (Danau Usamu / Danau Landu).
  5. Compute the extrusion / terrain mesh from contour lines and elevation points.
  6. Classify and assign landform types (KJP, KPG, NNE, Lake) to their correct spatial extents.
  7. Place each zone label at its zone's true coordinates.
  8. Add the landform legend and scale reference consistent with the source map.
  9. Compare the rendered 3D island against the uploaded PDF map and iterate until the shapes match.

Flow B — Map Viewer: Inspecting the 3D Island

  1. Open the 3D map application.
  2. View the island in its default orientation and read the landform legend and scale.
  3. Rotate the scene to inspect coastlines, bays, and peninsulas.
  4. Zoom in to examine the lakes and terrain relief.
  5. Adjust tilt to view elevation differences across KPG, KJP, and NNE zones.
  6. Read the KJP, KPG, NNE, and Lake labels and confirm their positions against the zone they describe.
Page 12 of 16

Flow C — Evaluator: Verification Against the Official Map

  1. Open the official topographic map (PDF) alongside the 3D scene.
  2. Compare island outline, coastline features, and lake extents.
  3. Confirm the rendered shape matches the map shape without deviation.
  4. Confirm terrain relief reflects the map's contour and elevation values.
  5. Confirm landform types and legend entries match the source classification.
  6. Confirm the scale reference matches the published 1:30000 map scale.
  7. Confirm zone labels sit on their correct zones.

6. Visuals, Colors, and Theme

The source material does not prescribe a visual theme; the following restrained defaults are derived from the domain (topographic cartography), the audience (cartographers and map evaluators), and the accepted delivery shape (an interactive 3D terrain viewer):

  • Base theme: neutral, cartographic — light-to-mid gray/white neutral background so terrain relief and zone colors read clearly.
  • Terrain relief coloring: elevation-graded, low-to-high ramp from pale green/low elevation through tan/brown to lighter gray/dark for high relief, consistent with standard topographic hypsometric conventions.
  • Landform type fills: distinct but muted area colors per landform class so KJP, KPG, NNE, and Lake are visually separable and match the legend — e.g., KJP as pale sandy-yellow (mudflat), KPG as muted tan/green (karst plateau), NNE as pale blue-green (estuarine plain), Lake as clear blue.
  • Labels: high-contrast, legible sans-serif text with subtle halo/backing so labels remain readable over terrain.
  • Contour/linework: thin dark-gray contour lines and administrative boundary lines, subordinate to the zone fills.
  • Legend panel: compact, cartographic legend listing landform types with their names and colors.
  • Scale element: a simple graphic bar with distance divisions in km, plus a numeric scale reference.
  • Accent: a single restrained accent used only for selection or emphasis; no decorative gradients or unrelated branding.
Page 13 of 16

7. Signature Design Concept

The signature concept is a faithful digital twin of Landu Leko's island form: the exact official map outline extruded into a living 3D landmass whose mudflats lie flat, whose karst plateau rises in undulating hills, whose estuarine plain slopes gently, and whose inland lakes sit as flat blue mirrors inside the terrain — all framed by the source map's own legend, scale, and landform classification. The identity of the product is accuracy itself — a viewer should be able to place the official PDF map beside the screen and see the same island, indefinitely rotated in space.

8. Interaction Model & Motion Direction

  • Primary interaction: direct orbit-style 3D navigation — drag to rotate, wheel/pinch to zoom, dedicated tilt control to change vertical camera angle.
  • Motion character: smooth, inertial, continuous movement; camera transitions ease in and out rather than snapping.
  • Labels: anchored to their geographic coordinates; they fade or scale gracefully with distance rather than detaching from the terrain.
  • Legend and scale: persistent, cartographic reference elements that stay legible during navigation.
  • Terrain: static geometry (terrain does not animate), but lighting and contour contrast remain stable while orbiting so that relief stays readable from any angle.
  • Responsiveness: controls must remain smooth during continuous orbit, zoom, and tilt within the browser.
Page 14 of 16

9. Non-Functional Requirements

  • Spatial fidelity: the rendered island outline and coastline must match the official topographic map shape without visible deviation.
  • Coordinate correctness: all geometry must be positioned in WGS 1984 – Zone 51S using Transverse Mercator projection and the Grid Geografi grid.
  • Data authority: geometry and elevation must derive from the Indonesian Topographic Base Map (1:25,000) and ESDM data.
  • Landform completeness: every landform type in the source legend (KJP, KPG, NNE, Lake) must be represented and labeled.
  • Performance: rotation, zoom, and tilt must remain smooth and interactive for a district-scale terrain mesh in a web browser.
  • Scale reference: the source map scale of 1:30000 must be preserved as the mapping reference for the visualization.
  • Label accuracy: every zone label must resolve to its correct spatial coordinate on the terrain.
  • Cross-browser rendering: the 3D scene must render consistently in modern browsers using Three.js / Deck.gl capabilities.

10. Tech Stack

  • 3D rendering and interaction: Three.js and/or Deck.gl (as explicitly specified by the user for rotation, zoom, and tilt control).
  • Spatial data format: GeoJSON district boundary data and vector elevation data for Kecamatan Landu Leko.
  • Coordinate reference: WGS 1984 – Zone 51S; Transverse Mercator projection; Grid Geografi grid system.
  • Source data: Indonesian Topographic Base Map (scale 1:25,000) and Ministry of Energy and Mineral Resources (ESDM) data.
  • Delivery shape: browser-based interactive web application (currently hosted on Replit), rendering a single interactive 3D terrain scene.

No additional application layers (authentication, administration, database, or backend services) are required by the source material, as the product is a client-rendered geospatial visualization.

Page 15 of 16

11. Assumptions and Constraints

  • The official administrative boundary for Kecamatan Landu Leko is available as GeoJSON or an equivalent vector boundary dataset.
  • Precise elevation contour and elevation-point data are available to drive the terrain mesh; without them, accurate relief cannot be produced.
  • The uploaded PDF map defines the authoritative island shape, and the model must conform to it rather than to any prior approximation.
  • All data must be aligned to WGS 1984 – Zone 51S before extrusion and labeling.
  • The landform classification is fixed to the source categories: KJP (Tidal Mudflat Plain, Flat), KPG (Karst Plateau, Undulating to Hilly), NNE (Estuarine and Merged River Plain, Flat to Gently Sloping), and Lake.
  • The existing simplified/block-like geometry is treated as obsolete and is to be replaced.
  • The visualization is a viewer of authoritative data; it is not a data-editing or GIS-authoring system.
  • Smooth 3D control performance is a hard constraint on the mesh detail level chosen.
  • The published map scale of 1:30000 and base map scale of 1:25,000 define the scale references to be displayed.
Page 16 of 16

12. Glossary

  • SRD — System Requirements Document.
  • Kecamatan — District (Indonesian administrative subdivision).
  • Kabupaten — Regency.
  • WGS 1984 – Zone 51S — World Geodetic System 1984 datum, UTM Zone 51 South; the horizontal datum used by the source map.
  • Transverse Mercator — Map projection used by the source map.
  • Grid Geografi — Geographic grid system specified on the source map.
  • KJP — Tidal Mudflat Plain (Flat).
  • KPG — Karst Plateau (Undulating to Hilly).
  • NNE — Estuarine and Merged River Plain (Flat to Gently Sloping).
  • Lake (Danau) — Inland water body category; includes Danau Usamu / Danau Landu.
  • Landform Types — The source map's classification of terrain regions into KJP, KPG, NNE, and Lake.
  • SCALE — Published map scale of 1:30000 (base map data at 1:25,000) used as the distance reference for the visualization.
  • GeoJSON — Open standard format for encoding geographic vector features.
  • Extrusion / Terrain Mesh — 3D geometry generated by raising a surface according to elevation values.
  • Contour Line — Line connecting points of equal elevation on the source map.
  • Elevation Point — Point feature carrying a measured elevation value on the source map.
  • ESDM — Ministry of Energy and Mineral Resources (Indonesia), a source data provider.
  • Three.js — JavaScript 3D rendering library.
  • Deck.gl — WebGL-based data visualization framework used for geospatial rendering.
  • 1:30000 / 1:25,000 — Published map scale and base map scale of the source materials.

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

No user flows yet.

The User Flow Agent will generate per-persona navigation diagrams after SRD updates.

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

No user flows yet.

The User Flow Agent will generate per-persona navigation diagrams after SRD updates.