Geo Triangulation

MPTriangulation turns map data and 2D outlines into ready-to-render 3D meshes while your game is running. Feed it OpenStreetMap or GeoJSON and get buildings with walls and pitched roofs, and streets with clean joins and caps. Feed it a Vector2 array and get a filled, triangulated shape.

Version 2.0 is a major update: much faster chunked and multithreaded mesh generation, async loading without frame spikes, roof shapes, configurable street joins, feature picking, a URP shader and five new demo scenes. Updated for Unity 6000.6 and the Universal Render Pipeline 17.6.

WHAT YOU CAN BUILD

- Location-based games and AR: generate the city around the player's GPS position.

- City and world visualisation: stylised dioramas, a city bent around a tiny planet, 3D map dashboards.

- Procedural shapes: polygons and concave outlines from your own code or from sensors, for example contours from a depth camera.

HIGHLIGHTS

- Real-world data in: OpenStreetMap JSON, GeoJSON (for example an export from mygeodata.cloud) or plain Vector2 arrays.

- Buildings with walls and roofs: heights from the OSM tags (height, building:levels and the min_ variants) or fixed and random heights. Flat, gabled, hipped and pyramidal roofs with an adjustable pitch. Related OSM roof:shape values such as half-hipped, mansard or dome map to the closest shape.

- Streets with proper geometry: miter, bevel or round joins, butt, square or round caps, width from the highway and lanes tags.

- Fast: features are merged into spatial chunk meshes, so a whole city needs only a handful of draw calls. Geometry is built on worker threads.

- Loads without stalling: RenderJsonDataAsync and RenderJsonTextAsync triangulate (and parse) off the main thread and create the GameObjects within a per-frame time budget you set.

- Styling built in: solid, random-from-palette or height-gradient colors written to the vertex colors, darkened wall bases, smooth or hard wall corners, UV scaling, shadow settings. Includes the lit URP shader MPTriangulation/MapSurface; any other material works too.

- Grow animation: buildings rise from the ground, staggered from the center of the map outwards.

- Feature picking: raycast the map and find out which building or street was hit, get its name from the data and highlight all of its triangles.

- Your own features: fill a GeoFeatureSet from code, render it, and read the projected points back, for example to place props along a street.

- Low level triangulators: an Earcut port with hole support and allocation-free per-thread instances, plus a simple polygon triangulator. Safe on worker threads.

- Polygon and street settings are ScriptableObject assets (Assets > Create > PolygonConfig / StreetConfig).

HOW IT WORKS

1. Add MeshGenerator and DataConnector to a GameObject.

2. Create a PolygonConfig and a StreetConfig, give them a material.

3. Call DataConnector.RenderJsonData (or the async versions) with your data and a center point. The map is built around that point.

FIVE DEMO SCENES

- Munich from an OpenStreetMap dump with a day / night time-lapse: lit windows, street lamps and cars driving along the streets, all drawn with GPU instancing and no extra GameObjects.

- The same city bent around a tiny planet, with a sun that sweeps day and night over the surface and planes flying over the city on light trails.

- Custom data: regular polygons and concave stars from Vector2 outlines.

- A countryside diorama from a GeoJSON export: gabled houses, patchwork fields, roadside trees, farm tracks and hover picking that highlights a building and shows its name.

- The city drawing itself feature by feature from the center outwards.

DOCUMENTATION

A full documentation file is included in the package: quick start, API reference, data formats, a reference for every setting, shader properties and notes on threading and memory. A changelog and an upgrade guide for users of version 1.0 are included as well.

UPDATING FROM 1.0

Delete the old MPTriangulation folder before importing 2.0, files were moved and renamed. All types are now in namespaces (MPTriangulation, Triangulation). RenderJsonData and RenderPointData keep their signatures, but you should pass a center and set batching to PerFeature if you rely on one GameObject per feature. See the changelog for details.