GPX conversions to Osm/Gml/Gpx/Topojson have some problems in specifix input

Aspose.GIS Product Family
1

Hi Alexander,
Here are some conversion that succeeded but in QGIS is not same.

Gpx → Osm
https://app.screencast.com/9BYewaRMFc1SG

Gpx → Gml
https://app.screencast.com/1RsdoDrcUmN3f

Gpx → Gpx
https://app.screencast.com/Rw5WjOTxdmyMe

Gpx → Topojson
https://app.screencast.com/I4LMTnecXh1SD

Attached Input + Output +QGIS files
4524 - Aspose.7z (1.5 MB)

Your quick answer is appreciated.
Thanks,

2

Hi, @danies8
I need to explore your request. I’ll be back with an answer in a couple of days.

1 Like
3

Hi, @danies8

Please, write your questions here, not inside the videos.

Gpx → Gpx
I check Gpx → Gpx and result the same in Qgis. I didn’t notice problem here!

Gpx → Osm
Converting GPX to OSM format is generally considered a “bad idea” (or at least a counterproductive one) for several technical and structural reasons:

  1. Fundamental Logic Difference
  • GPX (GPS Exchange Format) is designed to record movement. It captures a sequence of points in time (trackpoints) with timestamps, elevation, and sensor data (heart rate, speed).
  • OSM (OpenStreetMap XML) is designed to describe static geography. It focuses on permanent features like roads, buildings, and land use, using a node-way-relation model.
  • The Conflict: Converting a GPX track directly into an OSM “way” creates a messy line with hundreds of unnecessary points (nodes) representing every slight wobble of your GPS, rather than a clean, mapped road.
  1. Lack of Meaningful Metadata (Tags)
  • GPX data is “dumb” regarding semantics. A GPX file knows where you went, but it doesn’t know what you were on.
  • OSM relies on tags (e.g., highway=residential, surface=asphalt). A raw conversion won’t magically know how to tag the path. You end up with a geometric line that has no data attached to it, making it useless for rendering or routing.
  1. Precision vs. Accuracy
  • GPS Noise: Consumer GPS devices have a margin of error (3–10 meters). If you convert a GPX track directly to an OSM object, you are hardcoding “noise” and signal drift into a map that is supposed to be an idealized representation of reality.
  • OSM Standards: In the OSM community, GPX tracks are used as a background reference (a guide) to trace over manually, rather than being imported directly as map objects.
  1. Topology Issues
  • Connectivity: OSM is a topological network where roads must connect at shared nodes to allow for navigation.
  • Direct Import: If you convert and import a GPX track, it won’t be connected to the existing road network. It will just be a “floating” line, which breaks routing engines (like OSRM or GraphHopper).
4

So is there solution to GPX to Osm? Or to leave it.
What about two last conversions.

5

As for as Gpx → Gml and Gpx → Topojson i made conversion and saw that QGIS didn’t show result. I can’t explain why QGIS don’t show geometry, but i check files and files ok. Morefor if we make conversion these files back to Gpx then QGIS show geometry correctly. So i make conclusion that files are ok and conversions were success.

6

Osm is not a format for storing arbitrary geodata.
Can you explain why you wanna convert GPX to Osm ? I can’t imagine

7

My converter do not know this info.
The user need to know i have matrix from 15 to 15 formats.
Is it?

8

exclude Osm from this matrix.
You can convert from Osm, but it doesn’t make sense convert to Osm.

9

OK. I will exclude Osm from this matrix.
You can convert from Osm, but it doesn’t make sense convert to Osm.
What about osm to osm is ok
What to write in log to user if they want to convert
From osm to other format, what error message
Do you think to write?

10

No, we have reported bug about it which need to fix

User can convert at your own risk. To many restrictions which we can’t support. Sometimes conversion will succeed

11

1.So…Osm-> Osm you will fix and I will leave, all others conversion to Osm I will block.
When will it be fixed in 26.4?
2.What the message that I will tell the user when I blocked him? Can you suggest me general message
why is not possible for log proposes, to convert to Osm from other formats?

12

Waiting to your answer.
Your quick answer will be appreciated!!!

13

Hi, @danies8

I have to finish my work for today.
I will back with answer on monday.

1 Like
14

Is it reproduced and fixed in 26.4?

15

unfortunately, no

16

Gpx → Osm -removed in my code since is not making sence.

Gpx → Gml – OK (QGIS problem)
Open bug in QGIS:

Gpx → Gpx -OK

Gpx → Topojson – OK (QGIS problem)
Open bug in QGIS:

17

Yes, correct.
About Gpx → Topojson and Gpx → Gml I not sure that is QGIS problem, but hope they help understand

18

Qgis answer:
The GML layer type is a GeometryCollectionZ. QGIS has no support for rendering geometry collections. You can use ogr2ogr -explodecollections out.gml "gpx- gml/Output/output.gml"

19

Thank you, It help!
As for as Topojson I have the idea what can be wrong. I will test and write later.

20

1.Regarding Qgis answer:
Do you need to do something in your side, or QGIS has no support for rendering geometry collections?
2. Qgis: you can use ogr2ogr -explodecollections out.gml "gpx- gml/Output/output.gml"
you can supported in your side ?

Can you please clarify?

P.S
On this Wednesday our QA will pass intensively on all my Matrix (1073 samples + other formats I’m preparing from Internet ) and will use your GIS API last version + comparison with QGIS when conversion does succeeded.

Can you please fix all the open bugs, I provided till end of May it is very important to us and also to the community and to our customers. Your help is very appreciated here.

On next Sunday, our first customer will use in production our tool based on your GIS API.
I will get impressions how it works and maybee more sample to explore.
I will open bug accordingly.

Our second customer, will use all your fixes you do in May.

Thank you very much.