What are the most common source and target CRS values to use?

EPSG:4326 is the WGS84 geographic coordinate system used by GPS devices and most raw location data — coordinates are in decimal degrees. EPSG:3857 is Web Mercator, used by Google Maps, OpenStreetMap, Mapbox, and other web tile services — coordinates are in meters. The most common conversion scenario is EPSG:4326 to EPSG:3857 for web map preparation.

Why do I need to change the coordinate system for distance calculations?

Distance and area calculations require coordinates in a metric projected CRS where one unit equals one meter. In WGS84 (EPSG:4326), coordinates are in decimal degrees where one degree of latitude is approximately 111 km but one degree of longitude varies by latitude. Computing distance in degree units produces incorrect results unless a haversine formula is used. Converting to a metric CRS lets you compute distances in meters directly.

Can I convert from one projected CRS to another projected CRS?

Yes. The transformation is not limited to geographic-to-projected conversions. Any EPSG code pair is supported — you can convert from one national grid system to another, from one UTM zone to another, or from any other supported CRS pairing.

Does this activity change the visual position of points on a map?

No — the physical location does not change, only the coordinate representation. The same point on Earth has WGS84 coordinates of 12.9716,77.5946 in degrees and produces different numeric values in Web Mercator. Both coordinate pairs refer to the same physical location; the difference is the mathematical system used to express that location.

What happens to rows with invalid coordinate formats?

Rows where the geopoint column contains unparseable values produce null or empty output in the transformed column. The rest of the dataset is processed normally.

Do I need to know the EPSG code of my source data?

Yes. The source CRS must match the actual CRS of the coordinate values in the input column. If the source data is GPS-derived, it is almost certainly EPSG:4326. For data from GIS systems or CAD tools, check the metadata of the source export — the CRS is usually documented in the file properties or API documentation.

Data TransformationGeospatialIntermediate

Change Coordinate System

Infoveave Data Automation — Geospatial

WGS84 latitude/longitude pairs convert to Web Mercator projected coordinates in one step so geospatial datasets from different sources align when overlaid on the same map.

Geospatial datasets from different sources — GPS devices, GIS systems, satellite imagery, OpenStreetMap imports — routinely use different Coordinate Reference Systems. A dataset in WGS84 (EPSG:4326) and a basemap in Web Mercator (EPSG:3857) will not align correctly when overlaid without CRS transformation. Distance and area calculations also require coordinates in a projected CRS — computing distances in degrees from WGS84 coordinates produces incorrect results because one degree of latitude does not equal one degree of longitude in meters. Change Coordinate System transforms the coordinate values in a geopoint column from the source CRS to the target CRS, enabling datasets from different sources to be combined correctly for spatial analysis, routing, geofencing, and map visualization.

Input:Tabular dataset with a geopoint or geometry column containing geographic coordinates in the source Coordinate Reference System (e.g., EPSG:4326)Output:Tabular dataset with a new column containing the transformed coordinates in the target CRS, with the original geopoint column retained alongside

Book a Demo View Documentation

Try Change Coordinate System in Infoveave

No SQL or scripting required
Visual drag-and-drop workflow builder
Runs automatically on a schedule
Connects to 100+ data sources

Part of Infoveave Data Automation

What Change Coordinate System does

Transform geographic coordinates in a geopoint column from one Coordinate Reference System to another in Infoveave. Convert between WGS84, Web Mercator, UTM, and other CRS projections so geospatial data aligns correctly across mapping tools, spatial analysis, and export formats.

When to use Change Coordinate System

You are combining geospatial data from two different source systems — for example GPS tracking data in WGS84 and a GIS export in a projected local CRS — and need both datasets in the same coordinate system before performing spatial joins, proximity calculations, or map overlay
You are preparing location data for a mapping library — Mapbox, Leaflet, Google Maps — that requires Web Mercator (EPSG:3857) coordinates rather than the WGS84 latitude/longitude values in your source dataset
You need to compute accurate distances or areas using geospatial calculations, which require a projected metric CRS rather than the degree-based geographic WGS84 CRS, and your source data is in EPSG:4326
You are exporting geospatial data to a format or system that requires a specific CRS standard, such as a government GIS portal that mandates a national grid projection, and your source data is in a different CRS

When to avoid it

You just need to separate existing latitude and longitude values into two separate columns — that is Extract Lat/Lon from GeoPoint, not a coordinate system transformation
You need to create a WKT GeoPoint column from raw latitude and longitude columns — use Create GeoPoint from Latitude/Longitude for that construction step
Your data uses the same CRS as the destination system and no transformation is needed — pass the geopoint column through without applying a coordinate transformation

Where it fits in your Infoveave automation

Change Coordinate System is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.

ConnectLoad geospatial data from GPS exports, GIS systems, or satellite datasets that use a specific Coordinate Reference System

You are hereChange Coordinate SystemConfigure the geopoint column, source CRS (EPSG:4326), and target CRS (EPSG:3857 or other) for projection conversion

Compute DistanceUse the projected coordinates in Compute Distance Between Geospatial Points for metric distance calculations in the target CRS

Create AreaApply Create Area Around Geopoint to generate buffer zones using the projected coordinate values in metric units

Export or VisualizePass the reprojected coordinates to a mapping tool or GIS export that requires the target CRS

Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.

Infoveave — Workflow Builder

● SavedSchedule: Daily 06:00

How teams use Change Coordinate System

Real scenarios where this transformation saves hours of manual work.

Retail

Convert Store Coordinates from WGS84 to Web Mercator for Map Overlay

A retail geospatial team maintains a store location dataset in WGS84 (EPSG:4326) — latitude and longitude values from GPS device exports. The team's mapping platform renders tiles in Web Mercator (EPSG:3857) and requires coordinates in the projected system for correct rendering. Change Coordinate System transforms the store location geopoints from EPSG:4326 to EPSG:3857 so store markers are plotted at the correct positions when overlaid on the Web Mercator basemap.

Manufacturing

Reproject Plant Perimeter Geometries to Local Metric CRS for Area Calculation

A manufacturing site planning team exports plant perimeter geometries from a CAD system in a local metric CRS (EPSG:2154 for France) but needs to combine them with satellite data in WGS84. Change Coordinate System converts the satellite data geopoints to EPSG:2154 so both datasets are in the same metric projection, enabling accurate area measurements and spatial joins between plant zones and satellite-tagged infrastructure points.

Finance

Standardize Branch Location Coordinates for National GIS Analysis

A bank's operations team receives branch location data from different regional systems using different CRS standards. Some use WGS84, others use a national grid system. Change Coordinate System standardizes all branch coordinates to a single CRS, enabling the team to overlay all branches on a single national GIS map for coverage gap analysis and branch distribution reporting.

See Change Coordinate System in action

Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.

Geo Column:Location

Transformed Column Name:New

Source CRS:EPSG:4326

Target CRS:EPSG:3857

Input Data

ID	Location
1	12.9716,77.5946
2	34.0522,-118.2437
3	48.8566,2.3522
4	51.5074,-0.1278
5	40.7128,-74.0060

Output Data

ID	Location	New
1	12.9716,77.5946	1.4283e+06,1.2873e+06
2	34.0522,-118.2437	-1.3172e+07,4.0281e+06
3	48.8566,2.3522	2.6207e+05,6.2359e+06
4	51.5074,-0.1278	-1.4215e+04,6.8499e+06
5	40.7128,-74.0060	-8.2390e+06,4.9786e+06

Configuration

Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.

Geo Column

Select the column containing the geographic coordinates to transform. The column should contain latitude and longitude values in the format expected by the source CRS. For WGS84 (EPSG:4326), values are in decimal degrees in lat,lon order.

Source CRS and Target CRS

Specify the CRS of the input data and the CRS you want to convert to using EPSG codes. Common source values are EPSG:4326 (WGS84 geographic, the GPS standard) and EPSG:3857 (Web Mercator, used by most web mapping tiles). Target CRS depends on the destination system — EPSG:3857 for web maps, national grid codes for specific country GIS portals, or UTM zone codes for metric distance calculations.

Frequently asked questions

Everything you need to know about Change Coordinate System in Infoveave.

Also in Geospatial — and what runs before & after

Transformations in the same family as Change Coordinate System, often chained together in the same Infoveave workflow.

Geospatial

Compute Distance Between Geospatial Points

Geospatial

Create GeoPoint from Latitude/Longitude

Geospatial

Extract Lat/Lon from GeoPoint

Geospatial

Create Area Around Geopoint

Part of Infoveave Data Automation

80+ transformations. Zero manual steps.

Change Coordinate System is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.

View all transformations Book a Demo

Ready to see Infoveave in action?

Book a personalised demo with our data experts

Book a Demo

Infoveave® is a product of Noesys