You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.
Hi!
We're been testing GTFS to NeTEx conversion using the command line tool https://github.com/afimb/chouette/blob/master/doc/command/examples.md
Could someone help by either commenting what's wrong here or by providing any documentation how to troubleshoot GTFS importing errors?
Any help is appreciated :)
Problem: There seems to be no stop lat & lon coordinates in the generated NeTEx.
By trial and error it was found out that setting in gtfs "stops.txt" the "location_type" to "1" (station) produces <Location> elements into the result with Longitude and Latitude values. How can we get coordinates to output NeTEx xml for "0" (stop) type stops as well? (For details please refer to code snippets in the end of this issue)
In our input material stops.txt defines LAT and LON in WSG84 projection and output NeTEx should have the same. So we set "projection_type" : "4326" in exportNetex.json. Problem: coordinates are not exactly the same in input GTFS stops.txt and output NeTEx xml
Does the tool do some conversion or assignment which causes the inaccuracy, and how can we avoid that? (For details please refer to code snippets in the end of this issue)
--- Relevant code snippets of input, configuration and output data: ---
shell: ./chouette.sh -i ../convert-input/importGtfs.json -o ../convert-input/exportNetex.json -f ../convert-output/netex-modified.zip ../convert-input/gtfs-modified.zip
Using mobi.chouette.command-3.4.8 from the maven repo.
The text was updated successfully, but these errors were encountered:
philosotractor
changed the title
GTFS import errors, coordinates for GTFS location_type 1, Presere GRFS LAT & LON coordinate accuracy for NeTEx output
GTFS import errors, coordinates for GTFS location_type 1, Preserve GTFS LAT & LON coordinate accuracy for NeTEx output
Oct 23, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi!
We're been testing GTFS to NeTEx conversion using the command line tool
https://github.com/afimb/chouette/blob/master/doc/command/examples.md
Could someone help by either commenting what's wrong here or by providing any documentation how to troubleshoot GTFS importing errors?
Any help is appreciated :)
Problem: There seems to be no stop lat & lon coordinates in the generated NeTEx.
By trial and error it was found out that setting in gtfs "stops.txt" the "
location_type
" to "1
" (station) produces<Location>
elements into the result with Longitude and Latitude values.How can we get coordinates to output NeTEx xml for "0" (stop) type stops as well?
(For details please refer to code snippets in the end of this issue)
In our input material stops.txt defines LAT and LON in WSG84 projection and output NeTEx should have the same. So we set "
projection_type" : "4326
" in exportNetex.json.Problem: coordinates are not exactly the same in input GTFS stops.txt and output NeTEx xml
Does the tool do some conversion or assignment which causes the inaccuracy, and how can we avoid that?
(For details please refer to code snippets in the end of this issue)
--- Relevant code snippets of input, configuration and output data: ---
shell:
./chouette.sh -i ../convert-input/importGtfs.json -o ../convert-input/exportNetex.json -f ../convert-output/netex-modified.zip ../convert-input/gtfs-modified.zip
inputReport.json:
stops.txt: with location_type set to 1:
importGtfs.json:
exportNetex.json:
Part of generated NeTEx: when location_type set to 1:
Using mobi.chouette.command-3.4.8 from the maven repo.
The text was updated successfully, but these errors were encountered: