-
-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
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
g.region: revision of output formats #3410
Comments
See #3020 for tracking modules that need JSON/YAML output. |
Random ideas
|
A lot of tools need key value format, so some universal translating function would work. Another group might be table data. Some tools would have to keep their own formats at least if we want to stay compatible. The human readable output is also important. YAML can sometimes count like that. What is funny is that GRASS GIS is using basically YAML files since 80s to store things internally. Internal WIND file looks like this: proj: 99
zone: 0
north: 221230
south: 219580
east: 639530
west: 637740
cols: 179
rows: 165
e-w resol: 10
n-s resol: 10
top: 1
bottom: 0
cols3: 179
rows3: 165
depths: 1
e-w resol3: 10
n-s resol3: 10
t-b resol: 1 But for machine readable output, it gets translated to:
which was designed for Bash eval and similar usage, but these days most people would likely choose JSON or YAML as sort of the default machine readable format for this data. Same for raster cellhd and vector head files and what r.info and v.info produce.
|
The text was updated successfully, but these errors were encountered: