Skip to content
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

modules: Always use current major version in VTK outputs (r.out.vtk, r3.out.vtk, v.out.vtk) #2343

Merged
merged 4 commits into from
Feb 15, 2023

Conversation

wenzeslaus
Copy link
Member

@wenzeslaus wenzeslaus commented Apr 28, 2022

r.out.vtk, r3.out.vtk, and v.out.vtk include software name in the VTK header line for the 'exported from' description text. This removes the hard-coded major version from the string and uses the current major version instead.

Reference data need update too and will need updates in the future. However, the test will fail and show the need to update, so it should be clear.

@wenzeslaus wenzeslaus added this to the 8.4.0 milestone Apr 28, 2022
@wenzeslaus wenzeslaus marked this pull request as ready for review February 10, 2023 19:15
@wenzeslaus wenzeslaus added the vector Related to vector data processing label Feb 10, 2023
@wenzeslaus
Copy link
Member Author

This removes outdated references to v7 from the generated VTK files. With this PR, no further updates will be needed because the version is simply not there.

This is similar to #2342. The any mention of the version is removed completely, so the question is if it is okay.

@wenzeslaus
Copy link
Member Author

Now the current major version is obtained.

Given that the header line should describe the data, title might be actually more appropriate. Full version number could be used too, but similarly to #2342, it would be a change in output, so perhaps a topic for a separate PR.

The existing test is now enabled and the values updated. The test will need an update for the next major version.

@wenzeslaus wenzeslaus changed the title modules: Remove major version from VTK outputs (r.out.vtk, r3.out.vtk, v.out.vtk) modules: Always use current major version in VTK outputs (r.out.vtk, r3.out.vtk, v.out.vtk) Feb 13, 2023
…, v.out.vtk)

r.out.vtk, r3.out.vtk, and v.out.vtk include software name in the VTK header line. This removes the major version from the string.
@wenzeslaus wenzeslaus merged commit b59a047 into OSGeo:main Feb 15, 2023
@wenzeslaus wenzeslaus deleted the no-major-version-in-vtk branch February 15, 2023 00:49
@wenzeslaus wenzeslaus added the bug Something isn't working label Feb 15, 2023
ninsbl pushed a commit to ninsbl/grass that referenced this pull request Feb 17, 2023
…r3.out.vtk, v.out.vtk) (OSGeo#2343)

r.out.vtk, r3.out.vtk, and v.out.vtk include software name in the VTK header line for the 'exported from' description text. This removes the hard-coded major version from the string and uses the current major version instead.
neteler pushed a commit to nilason/grass that referenced this pull request Nov 7, 2023
…r3.out.vtk, v.out.vtk) (OSGeo#2343)

r.out.vtk, r3.out.vtk, and v.out.vtk include software name in the VTK header line for the 'exported from' description text. This removes the hard-coded major version from the string and uses the current major version instead.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working vector Related to vector data processing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant