Create GeoPoint from Latitude/Longitude
Infoveave Data Automation — Geospatial
Your data has lat and lon as separate columns. Every downstream geospatial transformation needs POINT(lon lat). One step converts them — no formula, no CONCAT, no ST_MakePoint query.
Most raw location data arrives with latitude and longitude as separate numeric columns from GPS devices, address geocoding APIs, or spreadsheet exports. Geospatial analysis tools, spatial database functions, and GIS visualization systems expect coordinates in a combined geometry format — typically WKT POINT(longitude latitude). Bridging this gap normally requires a CONCAT formula in Excel, a ST_MakePoint call and geometry cast in PostGIS, or a Point() construction in Python shapely. Create GeoPoint from Latitude/Longitude performs this combination directly in the data pipeline, adding a well-formatted WKT POINT column that all subsequent Infoveave geospatial transformations expect. It also validates latitude values during the process, producing empty output for rows with invalid or out-of-range latitude values rather than silently passing malformed geometry downstream.
What Create GeoPoint from Latitude/Longitude does
Combine separate latitude and longitude columns into a single WKT-format GeoPoint column in Infoveave. Convert raw coordinate pairs to POINT(longitude latitude) geometry for use in geospatial transformations, spatial analysis, and map visualizations without writing PostGIS or shapely code.
When to use Create GeoPoint from Latitude/Longitude
- Your dataset from a GPS device, IoT sensor, field data collection app, or geocoding API arrives with latitude and longitude as separate numeric columns and you need a single WKT POINT column for subsequent geospatial transformations, proximity calculations, or map visualization
- You are preparing data to use the Compute Distance Between Geospatial Points, Create Area Around Geopoint, or Extract from Geocolumn transformations, which expect geopoint input in WKT POINT format
- You are ingesting address records that have been geocoded to latitude/longitude pairs and need to standardize them into a geometry column for spatial joins and geographic filtering
- You are building a geospatial analytics pipeline from scratch with raw coordinate data and need to produce the geometry column that serves as the starting point for all downstream location analysis
When to avoid it
- Your geopoint data is already in WKT POINT format in a single column — skip this step and use downstream geospatial transformations directly
- You need to extract latitude and longitude from an existing WKT geopoint column back into separate numeric columns — use Extract Latitude/Longitude from Geopoint for the reverse operation
- Your coordinates need to be converted to a different coordinate reference system before use — use Change Coordinate System after creating the geopoint to reproject to the required CRS
Where it fits in your Infoveave automation
Create GeoPoint from Latitude/Longitude 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 Create GeoPoint from Latitude/Longitude
Real scenarios where this transformation saves hours of manual work.
Combine Store Geocoded Coordinates into Geopoint Column for Catchment Analysis
A retail operations team imports a list of store locations that was geocoded using an address-to-coordinates API. Each record has separate Latitude and Longitude numeric columns. The team needs a single geopoint column to use in the Create Area Around Geopoint transformation for catchment polygon generation. Create GeoPoint from Latitude/Longitude is configured with the Latitude and Longitude columns, producing a StoreGeopoint column in POINT(lon lat) format that immediately feeds the catchment area step.
Convert Asset GPS Readings to Geopoint Column for Distance Calculation
A manufacturing firm tracks the last-known GPS location of field assets in a dataset where each record has Lat and Long columns from GPS device exports. The team needs to compute each asset's distance from the headquarters location. Create GeoPoint from Latitude/Longitude creates an AssetLocation WKT POINT column from the Lat and Long columns, which is then passed to Compute Distance Between Geospatial Points using the Another Geospatial Column compare type.
Standardize Branch and ATM Coordinates for Network Coverage Mapping
A bank consolidates its branch and ATM location data from multiple regional spreadsheets, each using different column names but consistently having separate latitude and longitude fields. Create GeoPoint from Latitude/Longitude standardizes all records into a single LocationPoint WKT column after column renaming, enabling a unified coverage polygon generation and spatial overlap analysis across the entire network.
See Create GeoPoint from Latitude/Longitude in action
Input data (left) is transformed using the configuration below. The output table (right) is ready for dashboards or downstream steps.
LatitudeLongitudeLocationGeoPointInput Data
| LocationID | Name | Latitude | Longitude |
|---|---|---|---|
| 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 | Invalid Row | 200.0000 | 77.5946 |
Output Data
| LocationID | Name | Latitude | Longitude | LocationGeoPoint |
|---|---|---|---|---|
| 1 | Mumbai Office | 19.0760 | 72.8777 | POINT(72.8777 19.0760) |
| 2 | Delhi Branch | 28.7041 | 77.1025 | POINT(77.1025 28.7041) |
| 3 | Bangalore Hub | 12.9716 | 77.5946 | POINT(77.5946 12.9716) |
| 4 | Chennai Center | 13.0827 | 80.2707 | POINT(80.2707 13.0827) |
| 5 | Invalid Row | 200.0000 | 77.5946 |
Configuration
Key fields to configure in the Infoveave workflow builder. Full reference available in the documentation.
Latitude Column
Select the column that contains latitude values in decimal degrees. Valid latitudes range from -90 to +90. Rows with values outside this range or non-numeric values produce an empty geopoint in the output column. This built-in validation prevents malformed geometry from propagating to downstream geospatial steps.
Longitude Column
Select the column that contains longitude values in decimal degrees. Valid longitudes range from -180 to +180.
Geo Point Column Name
Enter the name for the new WKT geopoint column that will be added to the dataset. The output format is POINT(longitude latitude) — longitude first, then latitude — which is the standard WKT coordinate order used by all Infoveave geospatial transformations.
Frequently asked questions
Everything you need to know about Create GeoPoint from Latitude/Longitude in Infoveave.
Also in Geospatial — and what runs before & after
Transformations in the same family as Create GeoPoint from Latitude/Longitude, often chained together in the same Infoveave workflow.
Part of Infoveave Data Automation
80+ transformations. Zero manual steps.
Create GeoPoint from Latitude/Longitude 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?
