Closed mlauu closed 1 year ago
Can you explain more about what you were expecting for the line string? Note that the coordinates will be in your local projection, not lat/lon.
Hi, I checked the projection of the output again and it is as I assumed. Had a bug in my setup. My app did not save the output correctly and used an old output with a different srid for the following conversion... fixed it and it works fine now. Thanks for the prompt response!
Hi,
I tried to map-match a trace and followed all steps in your README (used osm2po, altered the table for the projection, ...) (I used the projection 4087).
I used the CLI and a GPX file as input. I wrote the output to a file. The edge ids are correct for the original noisy trace of the GPX file but the LINESTRING contains weird positions and I have no idea why.
Is there a known solution to this issue (I assume I made a mistake during setup, but the fact that the Edge IDs are correct baffles me)
Here is the input & output of the simulated trace in London. input(GPX_not_supported).txt output.txt
Many thanks in advance!