-
Notifications
You must be signed in to change notification settings - Fork 391
-
Greetings, train_ds = SemanticSegmentationRandomWindowGeoDataset.from_uris(
class_config = class_config,
image_uri = train_image_uri,
label_vector_uri = train_label_uri,
label_vector_default_class_id = class_config.get_class_id('roof'),
size_lims=(150, 200),
out_size=256,
max_windows=400,
transform=data_augmentation_transform) The error I got is in the attached pdf document. Please suggest what I need to do. Thank you so much!!! |
Beta Was this translation helpful? Give feedback.
All reactions
Replies: 1 comment · 17 replies
-
Hi. Can you please post the full error in the post itself rather than in a PDF? |
Beta Was this translation helpful? Give feedback.
All reactions
-
|
Beta Was this translation helpful? Give feedback.
All reactions
-
Looks like mapping the coordinates in your label GeoJSON file to pixel coordinates results in |
Beta Was this translation helpful? Give feedback.
All reactions
-
Beta Was this translation helpful? Give feedback.
All reactions
-
Okay, one problem I can see from this is that your GeoJSON has a CRS that is not EPSG:4326. Raster Vision expects the CRS to be EPSG:4326. You will need to re-save your labels with the correct CRS or somehow transform the existing GeoJSON. Edit 2024-04-11: this is no longer true in v0.30. RV now supports GeoJSONs with arbitrary CRS's. |
Beta Was this translation helpful? Give feedback.
All reactions
-
Does it mean that I need to transform the crs of raster tiff to EPSG:4326 as well? |
Beta Was this translation helpful? Give feedback.
All reactions
-
No. Just the GeoJSON. |
Beta Was this translation helpful? Give feedback.
All reactions
-
It did fix the error! Hooray! Thank you so much! Curious, why the crs needs to be 4326, if that's the case, won't the label pixel not aligning the raster tiff? |
Beta Was this translation helpful? Give feedback.
All reactions
-
The GeoJSON standard does not officially support CRS's other than 4326, so RV doesn't either.
No, RV makes sure they are aligned. You can visualize your data to check if the imagery and labels are aligned.
It does not. Can you share an example of the predictions being shifted? |
Beta Was this translation helpful? Give feedback.
Okay, one problem I can see from this is that your GeoJSON has a CRS that is not EPSG:4326. Raster Vision expects the CRS to be EPSG:4326. You will need to re-save your labels with the correct CRS or somehow transform the existing GeoJSON.
Edit 2024-04-11: this is no longer true in v0.30. RV now supports GeoJSONs with arbitrary CRS's.