UCS-2000 coordinate transform

SK-63 / SK-42 ↔ UCS-2000 ↔ WGS-84

Pick source and target CRS, paste points (x y or lon lat). For cadastral work, cross-check critical points against Digitals.

From To

Batch points (x y per line)

Coordinates are sent only for transformation and are not stored.

Online transform between SK-63, SK-42, UCS-2000 and WGS-84. Geographic systems: lon lat as x y. Projected: easting northing in metres.

Built on pyproj with UCS-2000 EPSG codes. Requests go same-origin via /api/proj and are not stored.

For cadastral work cross-check critical points in Digitals.

FAQ

In which order should I enter x and y?

Always x then y: lon lat for geographic systems, easting northing in metres for projected ones.

Why might results differ from Digitals?

Common causes are a different SK-63 zone, rounding, or local keys. For legal boundary acts treat Digitals as the reference.

How many points can I transform in one request?

Up to 5000 points per request.

How can I export the result?

After a successful transform you can download CSV or a simple GPX.

Which SK-63 zone should I use for Kyiv?

Zones 4–5 often work; test neighbouring zones against a known control point.

Is a GPX file uploaded to the server?

No. Only a coordinate array is sent for the transform.

What should I do if I see “Failed to fetch”?

The transform API is unreachable. Reload the page; traffic uses same-origin /api/proj.

Are local municipal CRS supported?

Local systems vary. Send EPSG parameters and we can add a preset when possible.