Batch Latitude & Longitude Converter

Typical Use Cases

Scenario 1: Batch Calibration for Map Development — You scraped WGS84 coordinates for nationwide POIs from an open data source, but Amap (Gaode) uses the GCJ02 coordinate system. You need to convert thousands of points at once.

Scenario 2: Coordinate Standardization for Logistics Systems — Your company's logistics platform uses Baidu Map's BD09 coordinates, but the raw GPS data from partners is in WGS84. You need to batch convert them before saving to the database.

Scenario 3: POI Data Migration — You want to migrate merchant coordinates from Amap to Tencent Maps (both use GCJ02, but verification is sometimes needed), or export data from Baidu Maps for use in other mapping services.

Complete Example (Main Use Case)

Suppose you have a batch of WGS84 coordinates to convert to GCJ02 (Amap coordinate system). Open our converter and paste the following three lines of data into the input box:

116.397428,39.90923,wgs84,gcj02
121.473701,31.230393,wgs84,gcj02
104.065735,30.572258,wgs84,gcj02

Click "Start Conversion", and the system will return the target coordinates for each line. For example, the result for the first line (near Tiananmen Square, Beijing): Longitude 116.397428 → 116.397637, Latitude 39.90923 → 39.908287 (6 decimal places). You can view all three conversion records in the right-hand result area and click "Export to Excel" to save them.

Comparative Example: Edge Cases

When coordinates are near national borders or oceans, the conversion accuracy remains consistent. For instance, a WGS84 coordinate 100.0,0.0,wgs84,gcj02 (on the equator) converts to 100.0,0.0 (GCJ02 error near the equator is minimal).

For a negative longitude like -73.935242,40.730610,wgs84,gcj02 (New York), the process is the same: fill in the format in the input box, and after conversion, Longitude -73.935242 → -73.935637, Latitude 40.730610 → 40.729432. Note that our tool supports global coordinates, not just regions in China.

Common Mistakes / Pitfalls

1. Reversed Format: The input order must be "Longitude, Latitude, Source Coordinate System, Target Coordinate System". Many users mistakenly enter "Latitude, Longitude", causing the converted results to be offset by dozens of kilometers.
2. Coordinate System Case Sensitivity: The system only recognizes lowercase letters. For example, "WGS84" must be written as "wgs84", "GCJ02" as "gcj02", and "BD09" as "bd09".
3. Forgetting to Remove Headers: When pasting, only paste the data rows. Do not include headers like "lng,lat,from,to", otherwise the first row will be processed as coordinates, resulting in an error.
4. Incorrect Source Coordinate System: If your data is actually BD09 but you select gcj02 as the source, the converted results will be inaccurate. Always verify the coordinate system of your raw data.

How to Interpret the Results

The converted coordinates can be used directly in the corresponding map APIs or frontend displays. Because GCJ02 and BD09 apply non-linear offsets to the original WGS84 coordinates, searching for a location using the converted values will typically differ from the original WGS84 positioning by a few hundred meters to a few kilometers (depending on the region and encryption strength).

Important Notes

• This converter is based on public encryption algorithms with a conversion accuracy at the 0.001-second level (approx. 0.1 meters), suitable for daily scenarios like navigation, logistics, and map annotation.
• For military or surveying-grade accuracy requirements (centimeter level), please use official encryption equipment.
• Batch conversion supports up to 500 records per request. For larger datasets, please process them in batches.
• Resulting coordinates are rounded to 6 decimal places, which is sufficient for most applications.
• This tool does not store user data. Once the conversion is complete, the results are only available for download and are not retained on our servers.

Frequently Asked Questions (FAQ)

1. Why is there little change in the coordinates before and after conversion?
The offset from WGS84 to GCJ02 in mainland China is roughly in the range of a few hundred meters. If your coordinates are located in China, the numerical difference will indeed only appear in the decimal places, making it look "unchanged," which is normal.

2. My coordinates are in Degrees, Minutes, and Seconds (DMS) format. Can I convert them directly?
No. Please convert DMS (e.g., 116°23′50.74″) to decimal degrees (116.397428) before inputting. We may support this in future versions.

3. Do you support converting Baidu coordinates to WGS84?
Yes. Simply write the input format line as lng,lat,bd09,wgs84. Note that Baidu's BD09 is further encrypted on top of GCJ02, so converting BD09 to WGS84 requires two inverse operations.

4. Can multiple batches of data be merged and exported?
Currently, each batch conversion is exported as an independent Excel file. You can manually merge the files.

5. Is the conversion accuracy sufficient for navigation?
Standard in-car navigation requires an accuracy of 5-10 meters. Our algorithm's error margin is within 1 meter, which is more than sufficient.

6. What is the difference between the free and paid versions?
The free version can only convert a single coordinate at a time. The paid version supports batch processing (up to 500 records), text pasting, Excel uploads, and exporting results to Excel.

You can now try converting your own coordinate data in the calculator above.