We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I made a .KMZ with
ogr2ogr chtpoor.kmz chtpoor.csv -f LIBKML -oo X_POSSIBLE_NAMES=lon -oo Y_POSSIBLE_NAMES=lat
that looked like
<Placemark id="chtpoor.3"> <ExtendedData> <SchemaData schemaUrl="#chtpoor.schema"> <SimpleData name="mcc">466</SimpleData> <SimpleData name="mnc">92</SimpleData> <SimpleData name="lac">24600</SimpleData>
but in Viking there was no way to see that any of that even existed when clicking on a node and checking Properties.
OK, I'll try GPX instead of KMZ.
ogr2ogr chtpoor.gpx chtpoor.csv -oo X_POSSIBLE_NAMES=lon -oo Y_POSSIBLE_NAMES=lat -dsco GPX_USE_EXTENSIONS=YES
<wpt lat="24.19219" lon="120.855395"> <extensions> <ogr:mcc>466</ogr:mcc> <ogr:mnc>92</ogr:mnc> <ogr:lac>24600</ogr:lac>
Still no way to see any of that in Properties of a given waypoint.
No, clicking GPX extensions in the image #246 (comment) doesn't show them either.
Usage case: Clicking on a cell tower to see its details (without using the balloon method.)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I made a .KMZ with
that looked like
but in Viking there was no way to see that any of that even existed when clicking on a node and checking Properties.
OK, I'll try GPX instead of KMZ.
Still no way to see any of that in Properties of a given waypoint.
No, clicking GPX extensions in the image #246 (comment) doesn't show them either.
Usage case:
Clicking on a cell tower to see its details (without using the balloon method.)
The text was updated successfully, but these errors were encountered: