RoConvert / complete help
RoConvert features and formats guide
Practical guide to using RoConvert in real work: accepted formats, limits, conversions, results and checks before upload.
Recommended workflow for real-world projects
Prepare the file, run the conversion, verify the coordinate system and result, then keep the ZIP package in the project folder.
Sessions, refresh and download
The number of processing sessions is limited to 5 sessions in 10 minutes and 20 per hour. Volume limits for large files remain active separately so the server remains stable.
- If you reach the limit, wait for the "Try again in" message and resume processing after the displayed time expires.
- Do not leave the page or press refresh while processing. The session maintains the connection between the browser, job and download link.
- If you leave the page before completion, you may lose the ability to download and will have to run the processing again.
Server performance and processing queue
RoConvert uses a queue so the website, forms and instant quote calculator remain available while heavy files are processed.
- A maximum of 3 conversions or heavy viewers run simultaneously; the rest wait in the queue and start automatically when a slot becomes available.
- CSV/TXT and point on map are lightweight operations and generally remain available even if LAS/LAZ or CAD/GIS are waiting.
- If the server is busy, LAS/LAZ, Potree viewer or CAD/GIS jobs may be temporarily postponed to protect the processor and concurrent processes.
- The limits protect service stability during periods of simultaneous processing.
CSV/TXT
For point lists in CSV/TXT. Convert ETRS89 lat/lon/h <-> Stereo 70 / EPSG:3844 and MN75 with ROMGEO 25.09.
LAS/LAZ 1 GB
For LAS/LAZ UTM 34N/35N clouds up to 1 GB. The job runs in the queue and delivers a ZIP package with LAS/LAZ format similar to the uploaded file.
Potree LAS/LAZ viewer
For visual verification of LAS/LAZ point clouds up to 1 GB. The server prepares the Potree octree and the browser opens the viewer in a separate window.
CAD/GIS: file conversions
For CAD/GIS layers, choose the route according to the file you have: SHP ZIP, DXF, DWG, KML/KMZ or GPKG. Use the appropriate group: with CRS transformation or format-only.
Point on the map
For rapid verification of a Stereo 70 point on Google Maps, OpenStreetMap, OpenTopoMap and CyclOSM.
Currently accepted formats
| Unealta | Entered data | Result received | Limita | Observatii |
|---|---|---|---|---|
| CSV | ETRS89 or Stereo 70 table | ZIP with converted CSV and offer JPG | 100 MB | Optional header, comma/semicolon/tab delimiter, decimal or DMS coordinates, options for Long/Lat and file without names. |
| TXT | ETRS89 or Stereo 70 table | ZIP with converted CSV and offer JPG | 100 MB | Optional header, comma/semicolon/tab delimiter, decimal or DMS coordinates, options for Long/Lat and file without names. |
| LAS | UTM 34N/35N point cloud | ZIP with LAS or LAZ in the same format as the source, EPSG:3844/MN75, README and offer JPG | 1 GB | Choose Auto, 34N or 35N. The server reads the point cloud in segments, transforms it through pyproj to ETRS89 and then through ROMGEO 25.09 to EPSG:3844/MN75. The result remains LAS if you uploaded LAS or LAZ if you uploaded LAZ. |
| LAZ | UTM 34N/35N point cloud | ZIP with LAS or LAZ in the same format as the source, EPSG:3844/MN75, README and offer JPG | 1 GB | Choose Auto, 34N or 35N. The server reads the point cloud in segments, transforms it through pyproj to ETRS89 and then through ROMGEO 25.09 to EPSG:3844/MN75. The result remains LAS if you uploaded LAS or LAZ if you uploaded LAZ. |
| Potree LAS/LAZ viewer | LAS/LAZ for viewing | Temporary Potree viewer, without coordinate conversion | 1 GB | You upload LAS/LAZ directly for viewing, or open in Potree the result of a conversion or ground filtering. The viewer link is signed and remains available for about 60 minutes. |
| SHP ZIP | SHP ZIP, DXF, DWG, KML/KMZ, GPKG | ZIP with KMZ, DXF, GPKG or SHP ZIP | 500 MB | Upload SHP as ZIP with .shp/.shx/.dbf and ideally .prj; upload DXF directly for KMZ or GPKG; upload DWG directly for DXF without coordinate conversion; upload KML/KMZ directly for DXF or SHP ZIP outputs; upload GPKG directly for DXF. The CAD/GIS limit is 500 MB. |
| DXF | SHP ZIP, DXF, DWG, KML/KMZ, GPKG | ZIP with KMZ, DXF, GPKG or SHP ZIP | 500 MB | Upload SHP as ZIP with .shp/.shx/.dbf and ideally .prj; upload DXF directly for KMZ or GPKG; upload DWG directly for DXF without coordinate conversion; upload KML/KMZ directly for DXF or SHP ZIP outputs; upload GPKG directly for DXF. The CAD/GIS limit is 500 MB. |
| DWG | SHP ZIP, DXF, DWG, KML/KMZ, GPKG | ZIP with DXF, without coordinate conversion | 500 MB | Upload SHP as ZIP with .shp/.shx/.dbf and ideally .prj; upload DXF directly for KMZ or GPKG; upload DWG directly for DXF without coordinate conversion; upload KML/KMZ directly for DXF or SHP ZIP outputs; upload GPKG directly for DXF. The CAD/GIS limit is 500 MB. |
| KML/KMZ | SHP ZIP, DXF, DWG, KML/KMZ, GPKG | ZIP with KMZ, DXF, GPKG or SHP ZIP | 500 MB | Upload SHP as ZIP with .shp/.shx/.dbf and ideally .prj; upload DXF directly for KMZ or GPKG; upload DWG directly for DXF without coordinate conversion; upload KML/KMZ directly for DXF or SHP ZIP outputs; upload GPKG directly for DXF. The CAD/GIS limit is 500 MB. |
| GPKG | SHP ZIP, DXF, DWG, KML/KMZ, GPKG | ZIP with KMZ, DXF, GPKG or SHP ZIP | 500 MB | Upload SHP as ZIP with .shp/.shx/.dbf and ideally .prj; upload DXF directly for KMZ or GPKG; upload DWG directly for DXF without coordinate conversion; upload KML/KMZ directly for DXF or SHP ZIP outputs; upload GPKG directly for DXF. The CAD/GIS limit is 500 MB. |
| Point on the map | North(Y), East(X) Stereo 70 | Lat/lon and Google/OSM links | 1 point | Enter North(Y) and East(X) in metres. ANCPI example: 693771.732 / 310723.519 becomes 47.71566667 / 22.47555556. |
CAD/GIS routes and CRS logic
Choose the route according to the desired effect: some conversions numerically change coordinates between Stereo70 and WGS84, while others only change the file format.
| Caz | Unealta | Entered data | Result received | CRS | Observatii |
|---|---|---|---|---|---|
| With CRS transformation | SHP ZIP -> KMZ | SHP ZIP | KMZ | Stereo70/EPSG:3844 -> ETRS89/WGS84 | Coordinates are numerically transformed between the declared systems. |
| With CRS transformation | DXF -> KMZ | DXF | KMZ | Stereo70/EPSG:3844 -> ETRS89/WGS84 | Coordinates are numerically transformed between the declared systems. |
| With CRS transformation | KML/KMZ -> DXF | KML/KMZ | DXF | ETRS89/WGS84 -> Stereo70/EPSG:3844 | Coordinates are numerically transformed between the declared systems. |
| With CRS transformation | KML/KMZ -> SHP ZIP | KML/KMZ | SHP ZIP | ETRS89/WGS84 -> Stereo70/EPSG:3844 | Coordinates are numerically transformed between the declared systems. |
| No CRS transformation | DWG -> DXF | DWG | DXF | No CRS transformation | Numeric coordinates remain unchanged; only the format changes. |
| No CRS transformation | GPKG -> DXF | GPKG | DXF | No CRS transformation | Numeric coordinates remain unchanged; only the format changes. |
| No CRS transformation | DXF -> GPKG | DXF | GPKG | EPSG:3844 metadata | Coordinates remain unchanged; EPSG:3844 is only the CRS label for output. |
- CAD/GIS options are global: Keep Z preserves the existing Z when the file has it, and Split by layers generates separate files by layer alongside the main result.
- RoConvert cannot safely identify the coordinate system in all workflows. Confirm the source system and check a known point before delivery. GPKG ↔ DXF and DWG → DXF workflows change only the format, without numeric coordinate transformation; for DXF → GPKG, EPSG:3844 is only the output CRS label. DWG → DXF conversion uses a Python parser for tested versions and does not cover all AutoCAD/ODA variants.
What you receive in the download
Downloadable results are ZIP packages so that the converted file and Masuram.ro offer material remain together.
Ground for DTM from LAS/LAZ
The ground extraction tool does not convert coordinates. It reads all classes in the file as a neutral source, ignores existing classification and writes only points estimated as ground to the result, reclassified as LAS class 2 ground.
- CSF means Cloth Simulation Filter: the cloud is inverted, a numerical cloth is dropped over the terrain shape, and points close to the cloth are retained as ground.
- The default Clean DTM profile uses stricter thresholds for topography and limits retained points in areas with vertical objects. Balanced Terrain retains somewhat more context, while Complete (V19-compatible) reproduces the former more permissive filtering for work that depends on it.
- Additional cleaning is optional and runs after ground detection. It removes isolated points from the result; Light retains more, Balanced is the normal choice, and Strong cleans more aggressively, but may thin sparse real areas, ditches, edges or slopes.
- Planar structures / roofs is a separate advanced option, unchecked by default. When you enable it, the engine removes flat, compact components raised above the ground; it may also cut out real terraces, platforms, embankments or retaining walls, so the result must be visually checked.
- The ZIP package includes a technical log with the initial total, exported ground points, points removed as planar structures/roofs, removed isolated points, points filtered as non-ground, the cloth-simulation-filter-csf algorithm and the CSF settings used.
- Visually check the result in areas with dense vegetation, bridges, vertical walls, compact buildings, water or very sparse clouds; no automatic filter replaces final surveying control.
Potree LAS/LAZ viewer
The Potree viewer is for rapid visual inspection of LAS/LAZ point clouds. It does not convert coordinates when you upload a file directly for viewing.
- For direct upload, choose a local LAS or LAZ; the server temporarily builds the Potree octree and the window opens automatically when preparation is complete.
- Converted LAS/LAZ results and ground results can be opened in Potree from the existing actions, without uploading the file again from your computer.
- The viewer starts in Height/elevation mode and supports RGB, Brightness/intensity and LAS Classes when these attributes are present in the point cloud.
- The Quality selector offers Maximum 10M, High 6M, Balanced 3M and Fast 1.5M to balance detail with browser speed.
- The LiDAR flight services link from the viewer remains in a new tab so that the Potree session is not lost.
- Use the viewer for inspection, but check the system, elevation, classes, and deliverables in surveying/CAD/GIS applications before delivery.
CSV/TXT: file structure
Optional header, comma/semicolon/tab delimiter, decimal or DMS coordinates, options for Long/Lat and file without names.
RoConvert detects the delimiter and header, retains additional columns and can reverse the coordinate pair when the file is written in reverse order.
| When to use it | Entered data | First columns | Observatii |
|---|---|---|---|
| With name | ETRS89 | nume, lat, lon, h |
Optional header: name can be name, point, punct or id. |
| With name | Stereo 70 | nume, nord, est, inaltime |
Plane coordinates and elevations are values in metres. |
| No name | ETRS89 | lat, lon, h |
Check the "file without name column" option. |
| No name | Stereo 70 | nord, est, inaltime |
For 4+ columns, the rest become extra attributes. |
Check before upload
Most errors come from the wrong coordinate system, swapped columns or mixed delimiters.
- Confirm whether the file is ETRS89, Stereo 70 / EPSG:3844 or UTM 34N/35N.
- For tables, keep the same column order and select Long/Lat or No names only when the file requires it.
- If you use a decimal comma in coordinates, separate columns with a semicolon or tab.
- For LAS/LAZ, use Auto only when you are unsure of the zone; for final deliveries, note UTM 34N or 35N in the project documentation.
- For CAD/GIS, check a known point, separate layers, preserved Z and the output system before delivery. For DWG/GPKG/DXF format-only, check in CAD/GIS that useful entities were exported; coordinates remain the originals.
- After conversion, check a known point and the rows marked with an error before delivery.
Coordinate format
RoConvert reads simple tables: one point per row, with values separated by commas, semicolons or tabs. Use a dot or comma as the decimal separator, but avoid ambiguous separators in the same file.
| Caz | Accepted format | Exemplu | Observatii |
|---|---|---|---|
| ETRS89 decimal | name, lat, lon, h or lat, lon, h |
P1,47.71566666,22.47555555,162.0 |
Latitude and longitude are decimal degrees. For lon,lat files enable the Long/Lat option. |
| ETRS89 DMS | name, lat_dms, lon_dms, h |
P1,47 42 56.40000,22 28 32.00000,162 |
Degrees, minutes and seconds are accepted. Keep the same column order throughout the file. |
| Stereo 70 / EPSG:3844 | name, north, east, height |
P1,693771.732,310723.519,122.591 |
North(Y), then East(X), in metres. Height is a metric value for the Stereo 70/MN75 workflow. |
| File without point name | lat, lon, h or north, east, height |
47.71566666;22.47555555;162.0 |
Check the "file without name column" option in the interface. |
| Extra columns | coordinate columns + attributes |
P1,47.71566666,22.47555555,162.0,borna,A1 |
Columns after the coordinates are retained as attributes in the resulting CSV. |
DMS notations accepted by RoConvert
For ETRS89, RoConvert accepts multiple degree-minute-second notations in the same latitude or longitude column. Direction is written at the end: N/E remain positive, S/W become negative. If you use a decimal comma in seconds or minutes, use semicolon or tab as the file delimiter, not comma.
| Notatie | Latitude example | Longitude example | Observatii |
|---|---|---|---|
| Degrees, minutes, seconds with symbols | 47°42'56.40000" |
22°28'32.00000" E |
The degree symbol, apostrophe and quotation marks are treated as DMS separators. |
| Degrees minutes seconds separated by spaces | 47 42 56.40000 |
22 28 32.00000E |
RoConvert reads the first three numbers as degrees, minutes and seconds. |
| Grade:minute:secunde | 47:42:56.40000 |
22:28:32.00000E |
Two dots act as separators between degrees, minutes, and seconds. |
| d/m/s letters as separators | 47d42m56.40000sN |
22D 28M 32.00000 E |
d/D and m/M are accepted. For seconds with s/S, also place the direction at the end, for example sN or s E; otherwise a final s can be read as S = South. |
| Degrees + decimal minutes | 47 42.940000 |
22°28.533333' E |
When there are only two numbers, the second is interpreted as decimal minutes. |
| Direction sign or suffix | +47 42 56.40000 |
22 28 32.00000 W |
The minus sign or S/W suffixes produce negative coordinates; N/E preserves the positive value. |
CSV/TXT: file structure
Optional header, comma/semicolon/tab delimiter, decimal or DMS coordinates, options for Long/Lat and file without names.
LAS/LAZ: how the job works
Choose Auto, 34N or 35N. The server reads the point cloud in segments, transforms it through pyproj to ETRS89 and then through ROMGEO 25.09 to EPSG:3844/MN75. The result remains LAS if you uploaded LAS or LAZ if you uploaded LAZ.
CAD/GIS: file conversions
Upload SHP as ZIP with .shp/.shx/.dbf and ideally .prj; upload DXF directly for KMZ or GPKG; upload DWG directly for DXF without coordinate conversion; upload KML/KMZ directly for DXF or SHP ZIP outputs; upload GPKG directly for DXF. The CAD/GIS limit is 500 MB.
Point on the map
Enter North(Y) and East(X) in metres. ANCPI example: 693771.732 / 310723.519 becomes 47.71566667 / 22.47555556.
CAD/GIS limitations
RoConvert cannot safely identify the coordinate system in all workflows. Confirm the source system and check a known point before delivery. GPKG ↔ DXF and DWG → DXF workflows change only the format, without numeric coordinate transformation; for DXF → GPKG, EPSG:3844 is only the output CRS label. DWG → DXF conversion uses a Python parser for tested versions and does not cover all AutoCAD/ODA variants.
Data, expiry and safety
Coordinates entered for the map are not stored. Uploaded files are retained temporarily for processing; ZIP results expire after the first download or after approximately 30 minutes, and Potree viewer links expire after approximately 60 minutes. Do not upload personal documents or sensitive data that are not needed for conversion.
Quick examples
RoConvert speeds up technical checking, but the result must be checked before official use: coordinate system, MN75 elevation, UTM zone, rows with errors and units.
nume,lat,lon,h,descriere
P1,47.71566666,22.47555555,162.0,borna test
nume,nord,est,inaltime,lot
P1,693771.732,310723.519,122.591,A1
Nord(Y),Est(X)
693771.732,310723.519
=> 47.71566667,22.47555556
Transformations and results provided
The example shows the workflow: ETRS89 geographic coordinates as input, conversion through ROMGEO 25.09 verified against test points, and Stereo 70 plane coordinates with MN75 elevations as output.
What to check after conversion
RoConvert speeds up technical checking, but the result must be checked before official use: coordinate system, MN75 elevation, UTM zone, rows with errors and units.
