Contractors come and go
Access is needed only for specific work, but shared credentials remain with former participants.
For construction projects
RTK infrastructure for a construction site
Deliver corrections from your own base to survey crews, contractors, and compatible machinery while keeping access manageable throughout every project stage.
- Separate access for every contractor
- Mountpoints organized by zone and stage
- One connection procedure for the site
Site architecture
Bases, contractors, and machinery in one model
Primary site base
RTCM
Backup base
RTCM
YouCORS
Private NTRIP caster and access management
Surveyors · 8 rovers
Contractors · 10 clients
RTK-compatible machinery
Core teams receive permanent clients while contractors receive separate access for the required stage. One organization can be removed without disrupting every other team.
Important: YouCORS delivers corrections from your base stations to rovers, machinery, and applications. It does not sell access to a third-party RTK network or generate corrections without a source.
Complexity on a large site
Project participants change faster than shared access settings
Every stage introduces new contractors, work zones, and devices. Without one access model, it is difficult to revoke credentials safely or locate the source of a problem.
One login cannot be revoked safely
Changing a shared password affects surveyors, contractors, and machinery at once.
Teams use different settings
Inconsistent base and stream names increase the risk of selecting the wrong project zone.
The work area keeps expanding
New zones and stages require a clear structure for mountpoints and clients.
The primary source is unavailable
Without a prepared procedure, teams do not know which stream and settings to use next.
The failure is not isolated
The base, internet, caster, and rover are investigated at the same time without a clear owner.
Responsibility is fragmented
The owner, general contractor, and subcontractors define RTK infrastructure boundaries differently.
One site-wide architecture
From the survey control to a contractor's individual client
Define the correction source, stream structure, and access procedure before participants connect at scale.
- 1
Fix the base parameters
The responsible surveyor records coordinates, settings, and the purpose of each base station.
- 2
Publish RTCM to the caster
The site base sends its correction stream to the private NTRIP caster over the internet.
- 3
Separate mountpoints
Use clear names organized by project, work zone, or construction stage.
- 4
Issue individual clients
Permanent staff and every contractor receive separate credentials.
- 5
Limit access
Assign streams by role and disable clients when the relevant stage is complete.
- 6
Maintain one procedure
Document connection, change, diagnostic, and access-revocation steps.
YouCORS does not establish a common coordinate system by itself. Accuracy depends on correct base coordinates, survey control, RTCM format, and equipment configuration.
Project participants
Every organization receives only the access it needs
Separate permanent users, temporary contractors, and compatible machine-control systems while retaining centralized management.
Owner's survey team
Permanent access to core streams and responsibility for the survey control.
General contractor
Access for coordinating internal crews and assigned work areas.
Subcontractor crews
Separate clients limited to the duration and zone of specific work.
Machine-control systems
RTK/NTRIP-compatible terminals connected after their parameters are validated.
As-built survey team
Access to the assigned stream while completed work is measured and documented.
Technical inspection
Agreed access for independent verification and stage acceptance.
Access by project stage
The connection roster changes with the project
Define the roles, required stream, and access end point for every stage in advance.
- 01
Site preparation
- Who connects
- Survey team, general contractor, and grading crews.
- When to revoke access
- Temporary crews after layout and preparation are complete.
- 02
Earthworks
- Who connects
- Surveyors, earthwork contractors, and compatible machine control.
- When to revoke access
- Contractors when the earthwork package is closed.
- 03
Utilities
- Who connects
- Installation crews, surveyors, and technical inspection.
- When to revoke access
- Installation contractors after the as-built survey for their zone.
- 04
Roads and hardscape
- Who connects
- Road contractors, machinery, and the survey team.
- When to revoke access
- When work in the assigned zone is complete.
- 05
Structural installation
- Who connects
- Erection crews, surveyors, and inspection staff.
- When to revoke access
- Subcontractors after the relevant stage is accepted.
- 06
As-built survey
- Who connects
- The survey team and designated contractor specialists.
- When to revoke access
- After as-built documentation is delivered and verified.
- 07
Handover and operations
- Who connects
- The operator and designated archive users.
- When to revoke access
- All project and contractor clients are reviewed and disabled.
Example configuration
2 bases, 8 rovers, and 10 temporary contractor clients
Core users receive permanent clients, contractors receive separate limited access, and mountpoints are named by zone and stage.
- base stations
- 2
- permanent rovers
- 8
- temporary clients
- 10
| Stage | Roles | Stream | Access period | Owner |
|---|---|---|---|---|
| Earthworks | Surveyors, machinery | SITE-EARTH | Until stage close | Lead surveyor |
| Utilities | 2 subcontractors | SITE-UTIL | 90 days | General contractor |
| Roadworks | Crew and machinery | SITE-ROAD | Work schedule | Project engineer |
| As-built survey | Survey team | SITE-ASBUILT | Permanent | Project owner |
This is an example access matrix, not a universal sizing rule. The final design depends on project scale, participants, work zones, equipment, and redundancy requirements.
Reliability and ownership
Diagnose the correction chain by control zone
YouCORS simplifies correction transport and access management, but the result depends on every link from the base to the receiver's working conditions.
A caster cannot correct wrong base coordinates, obstructed sky, radio interference, or incompatible RTCM. Assign an owner and diagnostic procedure to every link.
- Zone 1
Base and source observations
Coordinates, antenna, satellite observations, and RTCM generation.
- Zone 2
Base internet connection
Connectivity, routing, and the ability to publish the stream externally.
- Zone 3
NTRIP caster and server
Source reception, mountpoint, authorization, and delivery to clients.
- Zone 4
Client parameters
Host, port, mountpoint, credentials, and RTCM compatibility.
- Zone 5
Field conditions
Sky visibility, interference, satellite geometry, and rover or machine settings.
Site launch plan
Deploy the infrastructure before contractors mobilize at scale
Validate the technical chain and access rules with one crew, then connect the remaining participants stage by stage.
- 1
Step 1
Assign an owner for the site's RTK infrastructure.
- 2
Step 2
Document bases, work zones, stages, and every participant.
- 3
Step 3
Create a test caster and a clearly named mountpoint.
- 4
Step 4
Run a field test with one survey crew.
- 5
Step 5
Prepare one standard connection and diagnostic guide.
- 6
Step 6
Connect contractors through individual clients by stage.
- 7
Step 7
Design and validate a fallback procedure.
- 8
Step 8
Review active access and responsible owners regularly.
Launch resources
Prepare the site's technical procedure
Complete guide to RTK GNSS
Understand the base, rover, corrections, and conditions required for RTK.
Read articleManaging RTK field crews
Individual clients, groups, and temporary access for project teams.
Read articlePrivate NTRIP caster checklist
Validate the source, server, and one test rover in a clear sequence.
Read articleWhy RTK Fix fails
Isolate problems across the base, transport layer, and receiver.
Read articleFrequently asked questions
Before launching RTK on a construction project
Do we need our own base station on the construction site?
You need a configured source of RTCM corrections—typically a site base or another compatible source you are authorized to use. YouCORS does not generate corrections itself.
Can equipment from different manufacturers connect?
Yes, when equipment supports compatible NTRIP and RTCM versions. Validate every model, firmware version, and operating scenario before connecting at scale.
How do we provide access to a subcontractor?
Create a separate client, assign the required mountpoint, and disable the credentials when work is complete. Other participants do not need to be reconfigured.
Can one caster serve multiple construction projects?
Projects can be separated through mountpoints, clients, and groups. The choice between one or several casters depends on scale, ownership, regions, and isolation requirements.
How should we prepare a backup correction stream?
Define the backup source, mountpoint, client settings, and transition procedure, then test them on real equipment. Do not assume failover is automatic unless the configuration explicitly provides it.
Who is responsible for correct base coordinates?
The designated project survey team remains responsible. YouCORS transports the received stream and does not validate survey control or station coordinates.
What if the client is connected but RTK Fix is unavailable?
Check the chain in order: base observations, RTCM, internet, caster source status, client permissions, and rover conditions. A successful caster connection alone does not guarantee Fix.
Discuss your configuration
Prepare the RTK design before contractors enter the site
Describe the project scale and participants. Your email application will open a prepared message with the information needed to discuss a pilot.
Already validated the technical design?
Create an account and start a pilot with one base and one survey crew.
Continue to registration