animation walk

Prompt

# Project: Aralvaimozhi 3D Explorer — A Realistic, Walkable Digital Twin ## Role Act as a senior geospatial software engineer, 3D graphics developer, GIS specialist, and game-engine developer. Build a functional, browser-based 3D exploration application recreating **Aralvaimozhi, PIN 629301, Tamil Nadu, India**, using real geographic data wherever possible. The experience should combine the geographic realism and aerial navigation of Google Earth with the freedom of movement of a first-person open-world game. **The main deliverable is a working, walkable 3D map, not a screenshot, concept design, animation video, or nonfunctional prototype.** ## 1. Geographic scope and accuracy Cover all of Aralvaimozhi that can reasonably be identified from reliable geographic data, including the village's street network, residential areas, surrounding landscape, and nearby mapped landmarks. Before building the environment: 1. Identify the approximate geographic extent of Aralvaimozhi associated with PIN 629301. 2. Use OpenStreetMap and its available geographic data to retrieve roads, intersections, paths, building footprints, and mapped points of interest. 3. Retrieve suitable terrain elevation data where available. 4. Use legally accessible aerial or satellite imagery only where its licensing and usage conditions permit. 5. Preserve real-world geographic coordinates, road connectivity, and relative distances. 6. Verify important landmarks using reliable geographic sources before assigning them exact positions. Do not assume that a postal PIN code precisely defines a village boundary. Establish a reasonable initial coverage area from mapped settlements and available geographic evidence. When data is incomplete, use plausible regional buildings and landscape elements as clearly understood approximations. Never present generated buildings, roads, or landmarks as verified real-world features. ## 2. Visual experience Create a realistic 3D environment featuring: - Accurate street geometry and intersections. - Residential buildings, shops, compound walls, roadsides, and local architectural styles. - The regional terrain and surrounding Western Ghats landscape where supported by elevation and geographic data. - Natural vegetation, roadside trees, fields, and other locally appropriate environmental details. - Realistic sky, sunlight, atmospheric haze, shadows, and optional evening lighting. - Animated clouds, birds, foliage, pedestrians, and traffic where performance permits. - Tamil and English signs only where their content is known; otherwise use generic, non-misleading signs. Use physically plausible building proportions, road widths, terrain elevation, and lighting. Avoid the appearance of a generic city or an invented fantasy village. ## 3. Two navigation modes ### A. Aerial exploration mode Provide a Google Earth–inspired overhead and oblique 3D camera. Requirements: - Zoom from a regional overview down to individual streets. - Rotate and tilt the camera. - Pan smoothly across the mapped area. - Display roads, geographic labels, and available landmarks. - Transition smoothly from the aerial view into street-level exploration. - Include a home button to return to the starting overview. ### B. First-person walking mode Allow the user to explore the actual mapped environment as though walking through the village. Controls: - W: walk forward. - S: walk backward. - A/D: move sideways. - Mouse: look around. - Space: jump, if enabled. - Shift: optional faster walking. - Escape: release mouse capture and open the pause menu. Implement: - Realistic walking speed and acceleration. - Gravity and ground-height detection. - Collision detection against buildings and other solid objects. - Movement constrained by actual road and terrain geometry. - Slope-aware movement where practical. - A stable eye-level camera with optional walking animation. - A reliable reset and recovery mechanism if the player gets stuck. Do not implement walking by merely moving the camera through buildings. Use a player controller that respects collision geometry and terrain. ## 4. Geographic rendering pipeline Use a modular architecture. ### Geographic data - OpenStreetMap data for roads, paths, building footprints, and mapped points of interest. - Suitable digital elevation models for terrain. - Properly licensed imagery or map tiles if available. - A consistent coordinate projection that preserves local distances and geometry. Retain source attribution and comply with the applicable licenses and tile-provider usage policies. Do not scrape Google Earth imagery or reuse restricted map tiles without authorization. ### 3D generation Convert the geographic data into: - Terrain meshes with appropriate elevation. - Connected road surfaces and intersections. - Buildings generated from actual footprints where available. - Procedural building facades and rooftops where detailed models are unavailable. - Trees, vegetation, street furniture, and regional environmental features. Preserve geographic alignment between all layers. Avoid gaps between roads, buildings floating above the ground, incorrect terrain heights, and disconnected road segments. ### Large-area rendering The application must cover the whole target area without loading every detailed asset at once. Implement: - Geographic tiles or spatial chunks. - View-frustum and distance-based culling. - Level of detail for buildings and vegetation. - Instanced rendering for repeated objects. - Progressive loading and a visible loading indicator. - Caching and error handling for missing or unavailable data. Allow the user to explore additional surrounding areas when the required data is available. ## 5. User interface Build a polished, responsive interface with: - Start Exploring button. - Aerial and walking mode toggle. - Interactive minimap showing roads and current position. - Player direction indicator. - Search for available mapped landmarks and streets. - Recenter and reset buttons. - Optional coordinates and approximate location display. - Graphics-quality settings. - Sound and animation toggles. - A help panel listing the controls. - Loading progress and clear error messages. The interface should not obstruct the main 3D view. Ensure that search, menus, and buttons continue working when mouse-look is enabled. ## 6. Recommended technology Use: - Three.js for 3D rendering. - JavaScript or TypeScript with a suitable modern build tool. - OpenStreetMap-compatible geographic data sources. - A suitable terrain-processing pipeline. - A spatial index for nearby objects and collision queries. - Web workers where beneficial for expensive geometry processing. Choose additional libraries only when they solve a real technical requirement. Do not assume that OpenStreetMap automatically provides high-resolution satellite textures, detailed terrain, or complete 3D building models. ## 7. Implementation requirements Develop the application in functional stages. Stage 1: Establish the geographic coverage, download or retrieve real map features, and render the roads and terrain. Stage 2: Generate the buildings and environment. Stage 3: Implement aerial navigation and first-person walking. Stage 4: Add collision detection, minimap, landmarks, and camera transitions. Stage 5: Add environmental animations, lighting, and performance optimizations. Stage 6: Test the application and fix issues. At every stage, maintain a runnable version. Do not replace a difficult feature with a button that does nothing or a placeholder that claims success. ## 8. Testing and acceptance criteria The project is complete only when: 1. The application starts successfully in a desktop browser. 2. The map is based on real geographic data for Aralvaimozhi rather than a manually invented street layout. 3. The mapped area includes the available village road network and surrounding terrain. 4. A user can navigate aerially and zoom to street level. 5. WASD and mouse controls allow smooth first-person exploration. 6. The player respects ground height and cannot freely pass through solid buildings. 7. The minimap and player position remain synchronized. 8. Geographic scale and road alignment are reasonably accurate. 9. Missing geographic data is handled honestly. 10. The application remains usable on a normal desktop computer. Provide the complete source code, project structure, dependency list, data-preparation instructions, attribution notices, and exact commands for installation and local execution. Run the application, test its controls, and fix build errors before declaring completion. If an external data provider requires credentials, explain how to obtain them and provide a working configuration path. Do not hardcode secrets. ## Final priority Prioritize, in this order: 1. Geographic authenticity. 2. A connected and correctly scaled walkable environment. 3. Reliable navigation and collision handling. 4. Coverage of the largest practical portion of Aralvaimozhi. 5. Realistic regional visuals. 6. Animation and visual polish. Build a credible digital twin of the real place, not merely a realistic-looking imitation.