Real vehicle IDs, coordinates, route IDs and observation timestamps; speed, heading and occupancy only when supplied.
Protobuf. One shared refresh per 35 seconds in this single-process application. No API key required in the verified request. CC BY 4.0; credit data.gov.my and the respective transport operators.DATA TRANSPARENCY · KETELUSAN DATA
Know what moves your map.
Johor opens with official data. A live feed failure never substitutes simulated vehicles. UTHM and the optional Johor demo are explicitly labelled simulations.
Initial successful integration on 30 September 2026 retrieved 75 vehicles and imported 21 routes with 988 stops. These are verification observations, not promised current fleet counts.
Connected data & services
Official agencies, routes, stops, trips, ordered stop times and route shapes.
ZIP/CSV. Imported automatically when missing or older than 24 hours, or with npm run ingest. The app uses a representative trip per route; it does not yet evaluate calendars or offer departure-time routing.MapLibre vector basemap style, linked tiles, glyphs and sprites.
Public instance, no configured API key. Availability has no application-controlled SLA. Style-linked resource URLs are resolved by MapLibre, not hard-coded API assumptions.Roads, place labels and geographical basemap information through OpenFreeMap.
© OpenStreetMap contributors, ODbL. The application preserves on-map attribution and does not bulk-cache third-party tiles.Vector tile schema and basemap attribution.
MapLibre displays the attribution supplied by the provider. The active 3D map uses OpenStreetMap building footprints and provider render heights (which may be estimated). No surveyed terrain is claimed.User-submitted geotags, descriptions, optional images and operator status changes.
Application-owned data in local JSON or PostgreSQL/PostGIS. Not a Malaysian municipal API. No synthetic reports are seeded. Reports are public; images are re-encoded client-side.Standards & official documentation
App Router manifest and service-worker integration.
The matching installed Next.js documentation was also read locally under node_modules/next/dist/docs/.CSV field and coordinate interpretation.
Includes service-day time semantics. Calendar-aware routing and all-trip shape matching remain future work.VehiclePosition protobuf semantics and optional fields.
Omitted occupancy and speed are unknown, not invented observations. The national integration uses VehiclePosition only.Supported agencies, update frequency and feed limitations.
Documents approximately 30-second updates. No connected national TripUpdates or ServiceAlerts endpoint is claimed.Official static endpoints and refresh guidance.
Used to select BAS.MY Johor. KTMB and Prasarana endpoints are research references, not connected feeds in this release.Upstream request budgeting.
Published limit: 4 requests per minute. In-process coalescing is implemented; multiple production replicas require a shared ingestion owner/cache.Government open-data attribution.
CC BY 4.0. Field transformations and runtime source timestamps are documented.Civic service-request interoperability reference.
No municipal Open311 gateway is connected. GERAK does not claim Open311 conformance.Design & architecture inspiration
Modern rider UI, localisation and transit-region configuration research.
Not installed or copied.Geographic transforms and map/3D integration research.
GERAK ultimately uses independent MapLibre and R3F renderers with a shared geographic projection contract, not this custom-layer implementation.Static GTFS import/query architecture reference.
Not installed. GERAK uses fflate and csv-parse for a bounded importer.Geographic route preparation reference.
Not installed; GERAK builds its own GeoJSON route layers.User-requested inspiration for a playful Malaysian miniature city and camera exploration.
No code, images or models copied; not a transport data provider.User-requested inspiration for teal scenery, miniature urban forms and approachable 3D presentation.
Visually inspected. No code, images or models copied; not an API.Moving transit visualization, tracking and performance design research.
MIT project. Architecture inspiration only; not installed or called.Transit entities, freshness and rider-facing information architecture.
Not a GERAK backend dependency; no OneBusAway API is connected.Production multimodal routing architecture research.
Not deployed. GERAK’s present planner discovers direct/one-transfer connections from a representative official stop sequence.Public issue-report lifecycle and location-based reporting research.
No AGPL application code copied or deployed. GERAK implements its own reporting UI and API.Large-fleet and geospatial visualization research.
Not installed. Current rendering uses MapLibre and React Three Fiber.PWA caching architecture research.
Not installed. GERAK uses a custom service worker and the Next.js manifest API.Researched, not connected
Future feed-quality validation.
Not installed or executed. The current adapter implements its own essential normalization checks.Official historical ridership context research.
Not ingested. GERAK displays no invented historical ridership or impact metrics.Potential future weather/flood context.
Not connected. Community flood reports are not official weather alerts.Official confirmation of campus transport and the existing tracking service.
Institutional source, not a telemetry endpoint. UTHM demo corridors are illustrative.Existing university tracker and prospective authorised integration.
No public ingestion API or authorisation verified. GERAK does not scrape it.Recommended production import validation.
Not run or installed in this MVP. The importer currently enforces archive bounds and essential coordinate/CSV checks.What is not claimed
No official ETA, fare, delay, accessibility audit, current crowd level or service-alert data is invented. 3D building footprints come from OpenStreetMap; heights may be estimated, and no surveyed terrain is claimed. Civic reports remain within GERAK unless a future authority integration is agreed. Route connections are not an operational timetable.
Code dependencies and complete licence references are recorded in package-lock.json and docs/SOURCES.md. No paid Mapbox API, Google Maps API, Mapbox terrain service, external AI API or analytics tracker is used.