Netzknoten Navigator translates GPS positions, coordinates, and map points into German road references built from road, network node, section, and stationing, then resolves those references back to a real-world location. It connects office and field workflows without repeated copy-and-paste between maps and agency portals. For traffic control contractors, planning, handoff, documentation, and integration become easier to manage.
Why does one road location become an operational problem so quickly?
A German traffic control contractor rarely receives every project location in the same format. One customer sends coordinates. Another specification names a classified road, network section, and station. A project manager drops a pin on a map. A field crew sends its current GPS position from a phone.
All of these can describe the same place, but they do not necessarily work equally well in the next step of the job.
Estimating may begin with a tender document. Project preparation then needs the actual road segment. Dispatch has to tell a crew where to go. A supervisor may need the location in a road authority’s referencing system. Later, the same place can reappear in inspection records, reports, GIS data, billing documentation, or another business application.
The friction is usually not finding the first point. It is preserving the meaning of that point while it moves between people, devices, and systems.
Germany’s supra-local road network measured about 229,500 kilometers at the beginning of 2025. The federal trunk road network alone covers about 51,000 kilometers, while road transport accounted for approximately 71 percent of freight transport performance in 2023 according to Germany’s Federal Ministry of Transport.
For a contractor handling changing work zones, temporary traffic control, inspections, and field assignments, road location is therefore not merely a mapping detail. It is operational data.
What is Netzknoten Navigator designed to do?
Vextario Netzknoten Navigator is designed around the German road network reference model rather than around street addresses alone.
A user can start with GPS, coordinates, or a selected point on the map. Where the regional source data supports it, the application can identify the corresponding road, network nodes, section, and stationing. The process can also run in reverse, turning an existing network reference back into a geographic location that can be displayed and navigated to.
That makes the application less like a conventional map search and more like an operational translation layer.
An estimator may start with agency data. A dispatcher needs something the crew can open. A project manager wants the road section and stationing in documentation. A GIS workflow needs coordinates. An internal system may eventually require the same road location through an API.
The underlying place has not changed. The representation has.
How does German road stationing relate to a physical point on the map?
For U.S. readers, German stationing can loosely be compared with route-location or milepoint concepts, but the German system has its own structure and terminology.
The road information systems used by German authorities organize roads through network nodes, sections, branches, and stationing. The Federal Road Information System, known as BISStra, stores federal trunk road network information in a structure aligned with the German road information database specification and supports geographic visualization and analysis of that data.
A physical point can therefore have more than latitude and longitude. It can also have a position within the formal road network.
Netzknoten Navigator connects both views.
A WGS84 coordinate can be resolved into a road reference. A map point can be evaluated against nearby network nodes and sections. Conversely, a reference consisting of a road section and station can be translated back to geographic coordinates and placed on a map.
The application can also present the same location in WGS84 decimal format, degrees-minutes-seconds, and ETRS89/UTM Zone 32 using EPSG:25832. This is useful when one team works in GIS, another uses agency documentation, and the field crew simply needs a destination on a phone.
Stationing direction and actual travel direction are treated as different concepts, which matters around divided highways, ramps, branches, and complex interchanges.
Where do road-location handoffs usually fail in day-to-day work?
The most common problems are often mundane.
Someone copies coordinates from an email into a map. A screenshot is sent to a supervisor. The supervisor describes the location in a work order. A crew member searches for the same location again on a phone. Later, an office employee tries to reconstruct the relevant road section from the original documents.
Every individual step seems harmless.
The risk increases when the site sits near a ramp, a complex interchange, a parallel carriageway, a municipal boundary, or another plausible section of the same road. A point that appears acceptable on a general-purpose map may still need a different network reference for agency documents or internal records.
Another frequent situation is mixed referencing. A tender may contain stationing, a drawing may show construction chainage, a photo carries GPS metadata, and the crew receives a pin in a messaging app. When everybody is talking about the same site, the process works. When two references diverge, it can take considerable effort to determine which one should govern the job.
The objective should therefore not be to add more text to the work order. It should be to preserve one location while translating it into the representation needed for each task.
How does the workflow compare with conventional map-based handling?
| Workflow step | Conventional approach | With Netzknoten Navigator |
|---|---|---|
| Receive a project location | Search an address, map pin, or coordinate manually | Use the available coordinate or network reference directly |
| Determine the road reference | Compare agency portals, maps, and documents | Bring road, network nodes, section, and stationing together |
| Convert coordinates | Copy values into another converter | Use WGS84, DMS, and ETRS89/UTM32 from the same location |
| Send the site to the field | Share screenshots, text, or raw coordinates | Share a persistent result link or QR code |
| Navigate to the site | Enter the destination again | Hand the location directly to supported navigation |
| Process project lists | Re-enter records into spreadsheets or GIS | Use batch processing, CSV, GeoJSON, and suitable OKSTRA workflows |
| Review data provenance | Research the source separately | Keep source, data vintage, and regional capability associated with the result |
The main difference is continuity. Instead of treating every representation as a new search, the road location becomes an object that can move through the workflow.
How can a traffic control contractor use it before a work zone starts?
Consider a typical project preparation process.
A contractor receives a work zone on a classified road. The location has to be reviewed before crews, signs, barriers, vehicles, and scheduling are finalized. The project manager needs to understand not only where the site appears visually, but which road section it belongs to and how it relates to the authority’s road reference.
Netzknoten Navigator allows that location to be evaluated on the desktop and then passed forward without rebuilding it for every recipient.
The project manager can work with the road reference. Dispatch can use the same result when preparing the assignment. A field crew can open the location through a shared link or QR code and send it to navigation. If somebody in the field identifies another relevant position, that location can move back to the office in the opposite direction.
This is especially useful for companies where the same employees handle several functions and where a complicated enterprise GIS workflow would create more administrative work than it removes.
Why can bridge and structure information matter to traffic control operations?
Road work rarely exists independently of the infrastructure around it.
A work zone may begin next to a bridge, cross an engineering structure, affect an access point, or require a contractor to identify an asset referenced in agency documents. The federal trunk road network includes roughly 40,300 bridges, according to Germany’s Federal Ministry of Transport.
For that reason, the Netzknoten Navigator product scope also includes the ability to search for road structures by official identifiers and connect available structure information with the surrounding road reference. Nearby structures can also be relevant when reviewing a site.
For traffic control contractors, the practical value is straightforward. A project document may contain a structure identifier that is more meaningful to the road authority than to the crew. The field operation needs the physical place. Connecting both reduces another manual lookup.
How can the same result move from a desktop to a field crew?
Device changes are a small but persistent source of rework.
An employee prepares a site on a desktop, then sends a string of coordinates to a crew member. The crew member copies the values into a phone. Someone else receives only a screenshot and has to recreate the destination manually.
Netzknoten Navigator allows a result to be shared through a persistent link or QR code. The recipient can open the same result rather than rebuilding it from a message. Supported navigation services can then receive the target position directly.
This also works in the opposite direction. A field employee can identify a road location and send it back to dispatch or project management.
That makes the shared result useful beyond simple communication. It becomes a handoff object between office and field operations.
How does the product deal with regional differences and changing road data?
Road data should not be treated as permanent.
Road sections change, interchanges are rebuilt, attributes are updated, and state-level data sets do not always expose identical information. A unified interface does not eliminate those underlying differences.
Netzknoten Navigator is therefore designed to keep source information, data vintage, regional capabilities, and available quality indicators connected to the result.
When more than one assignment is plausible, the system does not need to conceal that fact by forcing a single answer. When a required attribute cannot be supported by the regional source data, the safer behavior is to report that limitation rather than generate a convenient substitute.
This matters particularly around ramps, branches, complex network nodes, and divided carriageways, where geometric proximity by itself can be misleading.
Operational feedback can also be captured in a structured way. A field report about an incorrect road assignment does not silently rewrite the source data. It can instead be reviewed before it affects subsequent processing.
How can a contractor process an entire project list instead of one point at a time?
Single-location lookup solves one category of work. Project data creates another.
A traffic control contractor may receive a spreadsheet containing many project sites, inspection points, planned work zones, or coordinates from another system. Manually processing those records one by one quickly becomes inefficient.
Professional Netzknoten Navigator workflows therefore include CSV batch processing and column mapping. Coordinates can be resolved into road references in bulk, while road references can also be translated back to geographic positions.
A problem in one row does not have to invalidate the entire job. Exceptions can be separated for review while successfully processed records continue through the workflow.
Results can be exported as CSV or GeoJSON for spreadsheet, GIS, or downstream processing. For suitable data environments, the product scope also includes OKSTRA-compliant export with schema validation. The currently published OKSTRA release is version 2.023.
This creates a path from an individual field lookup to repeatable project-data processing without forcing a mid-sized contractor to build its own road-reference engine.
How can Netzknoten Navigator fit into existing business software?
A useful specialist application should not require every future workflow to stay inside its own user interface.
The road-location functionality behind Netzknoten Navigator is therefore also designed for programmatic use. API functions can resolve a geographic location into a road network reference, translate stationing back into a geographic position, retrieve available road context, and expose regional capabilities to connected software.
MCP support extends the same principle to compatible assistant systems. Instead of asking an AI application to infer German road references from general map data, the assistant can call dedicated road-network functions.
For a mid-sized contractor, this can matter when digital processes mature. A location might originate in estimating, appear in a job-management system, move to a field application, and later be included in reporting. Rebuilding the same domain logic inside every application would create unnecessary maintenance.
The stronger architecture is to maintain the road-location logic once and reuse it where the business needs it.
Why does browser-based access matter for field operations?
Traffic control companies operate across very different hardware environments.
An estimator may use a large desktop monitor. A supervisor may work on a tablet. A crew leader may only have a phone available at the site. Requiring a specialized desktop installation for every lookup would limit the value of the workflow.
Netzknoten Navigator runs in the browser on desktop, tablet, and smartphone and can be installed as a progressive web app. Its interface is intended for both office work and mobile use, including large touch targets and short interaction paths for common field tasks.
The product also supports German, English, Spanish, Turkish, Polish, and Romanian interfaces. That can be valuable in companies where the operational team is multilingual but the underlying German road terminology still has to remain consistent.
Core functionality can be tried without creating an account. Professional plans extend the workflow with organizational administration, higher-volume use, batch processing, exports, and system integration.
Companies can open the Netzknoten Navigator directly to work with a road location. The broader Vextario product portfolio covers additional workflows for traffic control companies, field operations, and road-related business processes.
The manufacturer is KrambergAI GmbH, https://krambergai.com/.
Why is road referencing an operational capability rather than a GIS feature?
A road location is used by more people than the GIS specialist.
It appears in estimating, project preparation, temporary traffic control planning, dispatch, field instructions, inspection records, customer communication, and operational documentation. In more mature digital processes, the same location may also move through APIs, GIS layers, reporting systems, and assistant tools.
That makes road referencing part of operational data management.
Netzknoten Navigator is designed around this point. It does not replace engineering judgment, traffic-control planning, or the verification responsibilities of experienced personnel. Its purpose is to prevent the same site from being repeatedly rediscovered and reinterpreted simply because another person or another system needs a different representation.
For a mid-sized contractor, that is often where specialized software creates the most practical value: not by adding another isolated database, but by removing repeated translation work from a process the company already performs every day.
Sources for the statistics used in this article
German Federal Statistical Office, “Transport infrastructure data, including road lengths for 2021 to 2025”:
https://www.destatis.de/DE/Themen/Branchen-Unternehmen/Transport-Verkehr/Unternehmen-Infrastruktur-Fahrzeugbestand/Tabellen/verkehrsinfrastruktur.html
German Federal Ministry of Transport, “Bedarfsplan für die Bundesfernstraßen”:
https://www.bmv.de/SharedDocs/DE/Artikel/StB/bedarfsplan-bundesfernstrassen.html
German Federal Ministry of Transport, “Bundesfernstraßen kompakt”:
https://www.bmv.de/SharedDocs/DE/Artikel/StB/uebersicht-bundesfernstrassen-kompakt.html
Further reading
German Federal Ministry of Transport: Geoinformation and the Federal Road Information System BISStra
https://www.bmv.de/SharedDocs/DE/Artikel/Z/geoinformationen.html
Hessen Mobil: Official road network node maps for the State of Hesse
https://mobil.hessen.de/service/downloads-und-formulare/netzknotenkarten-hessen
OKSTRA: Current Object Catalog for Roads and Transportation
https://www.okstra.de/schema.html
FAQ
Who is Netzknoten Navigator designed for?
Netzknoten Navigator is designed for traffic control contractors, project managers, dispatchers, estimators, and field crews that need dependable road locations. It is especially useful for work zones on classified roads, inspection routes, site documentation, bid preparation, and any workflow where German network nodes, road sections, and stationing appear in work orders or public-agency documents.
Can Netzknoten Navigator be used without registration?
Core functions are available through the Basic access without registration. Users can look up a road location, translate coordinates into a network reference, and share the result with a coworker or subcontractor. Business plans add higher usage, team administration, exports, batch processing, and integration functions for companies that need the workflow at operational scale.
What information can a road network reference contain?
Depending on the available source data, a result can include the road, network nodes, section, stationing, stationing direction, travel direction, and coordinates. Netzknoten Navigator only presents attributes that can be supported by the underlying regional data. When a value is unavailable, the application does not manufacture a replacement simply to fill the screen.
Can I turn stationing back into a map location?
Yes. The workflow works in both directions. An existing network reference made up of a road, section or network nodes, and stationing can be translated back into a geographic location and displayed on the map. This is useful when a location from a specification, traffic order, asset record, or internal document needs to be found in the field.
Which coordinate systems does Netzknoten Navigator support?
The application can present the same position as WGS84 decimal coordinates, degrees-minutes-seconds, and ETRS89 UTM Zone 32. That makes it easier to move one verified road location into GIS, plans, documentation, customer communication, or field instructions without performing another lookup or manually converting values in a separate tool.
What happens when more than one result is plausible?
Ambiguous road situations are not silently collapsed into a single supposedly correct result. When multiple network references are technically plausible, Netzknoten Navigator can expose that situation and provide supporting context. This matters around ramps, complex interchanges, parallel carriageways, and closely spaced sections, where a fast automatic answer can otherwise create an operationally expensive error.
Can results be shared with field crews or subcontractors?
Results can be shared through a stable link or QR code so the recipient does not have to retype the road reference. This is useful for work orders, traffic control plans, site instructions, and last-minute coordination between dispatch, project management, field crews, and subcontractors. The same location can move from the office to a phone without re-entry.
Are there export options for larger data sets?
Professional workflows include CSV batch processing and exports to CSV and GeoJSON. For suitable data environments, OKSTRA-compliant export can also be used. Individual problem rows should not force an entire batch to fail; they can be identified separately so teams can correct exceptions without rerunning every successful record in a large coordinate or road-reference list.
How are data source and data vintage handled?
The source of the road data, its data vintage, and available quality indicators remain visible with the result. Regional differences are treated as capabilities rather than hidden behind a uniform interface. Users can therefore see whether a function is supported in the current data region, whether several assignments are possible, or whether the requested attribute is not reliably available.
Can Netzknoten Navigator integrate with other systems?
Yes. Professional integrations can use API and MCP functions to process network references, stationing, and road context in machine-readable form. This allows road referencing to become part of internal applications, mobile workflows, assistant systems, or automated data pipelines without rebuilding the same domain logic independently inside every downstream system used by the company.
