-
-
Notifications
You must be signed in to change notification settings - Fork 393
v.profile: Add JSON output format #6875
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
Open
saket0187
wants to merge
6
commits into
OSGeo:main
Choose a base branch
from
saket0187:adds-json-output-in-v.profile
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
+392
−69
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
petrasovaa
reviewed
Jan 6, 2026
petrasovaa
reviewed
Jan 6, 2026
petrasovaa
requested changes
Jan 6, 2026
Contributor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the contribution, please read our contributing guidelines, specifically pre-commit to get the formatting correct.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #6232
Problem Description
The
v.profilemodule only supported plain text output with pipe-delimited or custom separators. We were required to add JSON support as well.Solution
Implemented comprehensive output format support with three options:
Plain format (default): Traditional CSV-style output with quoted string values. Maintains full backward compatibility with existing scripts.
CSV format: Unquoted delimiter-separated values optimized for spreadsheet applications. Uses the same separator parameter as plain format but omits quotes for cleaner parsing.
JSON format: Structured output with proper data type handling. Each feature is represented as a JSON object containing:
category: Feature category number (always present, even without database)distance: Distance along profile lineattributesImplementation details:
G_json_*functions) for JSON serialization with proper NULL value handlingG_warning()for database operation failuresTesting
Automated Tests (test_v_profile.py):
Added
testJsonFormat()that validates:All 6 test suite tests pass, including the new JSON format test.
Manual Testing with NC Basic dataset:
JSON Output example :-
[ { "category": 572, "distance": 19537.972502200733, "attributes": { "cat": 572, "feature_id": "986138", "featurenam": "Greshams Lake", "class": "Reservoir", ... } } ]