Extract Latitude/Longitude from Geopoint
Infoveave Data Automation — Geospatial
Your system exports location as (19.0760, 72.8777). You need separate Latitude and Longitude columns. One step splits them — no SPLIT formula, no SUBSTRING, no regex.
Legacy systems, IoT platforms, and some database exports store geographic coordinates as a single combined string in formats like (12.9716, 77.5946) rather than as separate numeric columns. When coordinates arrive combined, analysts cannot directly use them for numerical filtering, arithmetic, map coordinate binding, distance calculations, or exporting to systems that consume lat and lon separately. Splitting the coordinate string back into typed numeric columns requires SPLIT or MID formulas in Excel, SPLIT_PART or REGEXP_SUBSTR in SQL, or string parsing in Python — all of which require knowing the separator and position of each component. Extract Latitude/Longitude from Geopoint handles this parsing automatically, reading the parenthetical coordinate string and producing typed latitude and longitude columns that downstream steps can use without any formula coding.
What Extract Latitude/Longitude from Geopoint does
Extract latitude and longitude from a combined geopoint column into two separate numeric columns in Infoveave. Reverse-parse parenthetical coordinate strings such as (lat, lon) into typed Latitude and Longitude columns for calculations, filtering, and display without SPLIT or REGEX formulas.
When to use Extract Latitude/Longitude from Geopoint
- Your data source exports location as a combined coordinate string in parenthetical format like (12.9716, 77.5946) and you need separate Latitude and Longitude columns for distance calculations, filtering, map binding, or joining with other coordinate datasets
- You are reversing a previous geopoint combination step to recover individual latitude and longitude values for display in a report or export to an external system that requires separate coordinate fields
- You are standardizing a mixed dataset where some records have combined geopoint strings and others have separate lat/lon columns — extract the combined ones into separate columns so the dataset is uniform before downstream spatial analysis
- You need to compute Euclidean or geographic distance using the numeric latitude and longitude values from each row, and your geopoint column stores them as a combined string that must be split before arithmetic operations
When to avoid it
- Your geopoint is in WKT format (POINT(longitude latitude)) rather than parenthetical (latitude, longitude) format — the specific format handled by this transformation is the parenthetical style; WKT points are parsed differently
- You want to create a WKT geopoint from separate columns rather than extract from a combined column — use Create GeoPoint from Latitude/Longitude for the reverse direction
- Your goal is to compute the area, centroid, or perimeter from polygon or linestring geometries rather than extract coordinate values from a point — use Extract from Geocolumn for WKT polygon/linestring parsing
Where it fits in your Infoveave automation
Extract Latitude/Longitude from Geopoint is one step inside a multi-step Infoveave workflow. Chain it with other activities — no code, no manual hand-offs.
Build this workflow visually in Infoveave Data Automation — drag, connect, and schedule with no infrastructure setup.
How teams use Extract Latitude/Longitude from Geopoint
Real scenarios where this transformation saves hours of manual work.
Extract Customer Coordinates for Distance-Based Delivery Zone Assignment
A retail company's order management system exports customer addresses with a combined GeoLocation field in the format (19.0760, 72.8777). The delivery routing pipeline needs separate Latitude and Longitude numeric columns to compute distance from each customer to their nearest fulfillment center. Extract Latitude/Longitude from Geopoint splits the GeoLocation column into CustomerLat and CustomerLon for immediate use in the Compute Distance step.
Parse Combined Site Coordinates for Equipment Location Reporting
A facilities management team receives IoT sensor data where each record includes a CombinedLocation column exported by the sensor platform in the format (lat, lon). The plant management dashboard requires separate latitude and longitude columns for map pin rendering. Extract Latitude/Longitude from Geopoint produces Latitude and Longitude columns from the combined string so each sensor location displays correctly on the equipment location map.
Recover Separate Coordinates from Legacy Banking Location Dataset
A bank consolidating branch location data from a legacy system receives records where branch coordinates are stored as a single ParenthesizedCoord field. The new network planning tool requires separate BranchLat and BranchLon columns. Extract Latitude/Longitude from Geopoint splits the legacy combined fields, producing the typed numeric columns needed for the planning tool's distance and coverage calculations.
See Extract Latitude/Longitude from Geopoint in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
GeoLocationLatitudeLongitudeInput Data
| LocationID | BranchName | GeoLocation |
|---|---|---|
| 1 | Mumbai Office | (19.0760, 72.8777) |
| 2 | Delhi Branch | (28.7041, 77.1025) |
| 3 | Bangalore Hub | (12.9716, 77.5946) |
| 4 | Chennai Center | (13.0827, 80.2707) |
| 5 | Kolkata Depot | (22.5726, 88.3639) |
Output Data
| LocationID | BranchName | GeoLocation | Latitude | Longitude |
|---|---|---|---|---|
| 1 | Mumbai Office | (19.0760, 72.8777) | 19.0760 | 72.8777 |
| 2 | Delhi Branch | (28.7041, 77.1025) | 28.7041 | 77.1025 |
| 3 | Bangalore Hub | (12.9716, 77.5946) | 12.9716 | 77.5946 |
| 4 | Chennai Center | (13.0827, 80.2707) | 13.0827 | 80.2707 |
| 5 | Kolkata Depot | (22.5726, 88.3639) | 22.5726 | 88.3639 |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
GeoPoint Column
Select the column that contains the combined coordinate string in parenthetical format (latitude, longitude). The transformation expects a parenthesis-wrapped, comma-separated coordinate pair. Rows that do not match this format or contain null values produce nulls in the output latitude and longitude columns.
Latitude Column
Enter the name for the new column that will receive the extracted latitude value (first number inside the parentheses). The output is a numeric decimal degree value that can be used in arithmetic, filtering, and geospatial calculations.
Longitude Column
Enter the name for the new column that will receive the extracted longitude value (second number inside the parentheses). The output is a numeric decimal degree value.
Frequently asked questions
Everything you need to know about Extract Latitude/Longitude from Geopoint in Infoveave.
Also in Geospatial — and what runs before & after
Transformations in the same family as Extract Latitude/Longitude from Geopoint, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Extract Latitude/Longitude from Geopoint is one of over 80 transformation activities available inside Infoveave workflows. Chain transformations together — no code, no exports, no waiting for IT.
Ready to see Infoveave in action?
