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

GTC-2868 Force use of only XY (2 dimensions) from the dataset #547

Merged
merged 3 commits into from
Jun 27, 2024

Conversation

danscales
Copy link
Collaborator

GTC-2868 Force use of only XY (2 dimensions) from the dataset

Added "-dim xy" (same as "-dim 2") to the ogr2ogr command line.

Added "-dim xy" (same as "-dim 2") to the ogr2ogr command line.
@codecov-commenter
Copy link

codecov-commenter commented Jun 26, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.03%. Comparing base (c9bcbf5) to head (b0b229f).

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #547   +/-   ##
========================================
  Coverage    82.03%   82.03%           
========================================
  Files          126      126           
  Lines         5665     5665           
========================================
  Hits          4647     4647           
  Misses        1018     1018           
Flag Coverage Δ
unittests 82.03% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@dmannarino
Copy link
Member

Change looks good! How hard would it be to have a test for the CSV case at least?

@danscales
Copy link
Collaborator Author

Change looks good! How hard would it be to have a test for the CSV case at least?

Maanas indicated to me that the 3-dimension problem wasn't relevant for CSV or wasn't needed, so I didn't make any changes to load_vector_csv_data.sh. So, can't do a test on that. I tested this in dev using the dataset that Maanas gave to me (s3://gfw-data-lake-dev/landmark_icls_pt/v202406/raw/CommunityLevelData_pt.zip ) and will test again once this change is in staging.

@manukala6
Copy link
Member

@dmannarino According to TableAssetCreationOptions there are specific lat/long columns for ingesting CSVs, so by definition they should be 2 dimensions

@danscales
Copy link
Collaborator Author

Thanks for the reviews!

@danscales danscales merged commit 5e0e58e into develop Jun 27, 2024
2 checks passed
@danscales danscales deleted the gtc-2868 branch June 27, 2024 23:03
@manukala6 manukala6 mentioned this pull request Jul 1, 2024
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants