-
Notifications
You must be signed in to change notification settings - Fork 38
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
Tiled data not saved to directory #142
Comments
@yby026 what CRS are your crowns and geotiffs in? It appears to be related to that. We recommend using the UTM CRS suitable for your region. You can reproject with |
@PatBall1 they are all in NZGD2000 (EPSG2193), I've tried to reproject it into EPSG2134 (NZGD 2000 UTM Zone 59S), the problem still preserves. |
@yby026 have you tried reducing the If you are still having problems, I can have a look at your data. Not that it should affect things, but you are using quite small tiles that are not square, |
Thanks! reduced threshold to 0.3 solved the problem! |
Hello, I somehow have exactly the same issue at hand, i get this warning message, when calling tile_data_train: /home/…/miniconda3/envs/myenv/lib/python3.10/site-packages/detectree2/preprocessing/tiling.py:47: UserWarning: GeoDataFrame's CRS is not representable in URN OGC format. Resulting JSON will contain no CRS information. I used the following tiling Parameters: I am working on 1km x 1km tiles with EPSG:25832, but also tried using the cambridge data from the urban model, all modifications did not change anything. The logging shows no other warnings besides the one mentioned above. This is my error trace: /home/.../miniconda3/envs/myenv/lib/python3.10/site-packages/torch/functional.py:512: UserWarning: torch.meshgrid: in an upcoming release, it will be required to pass the indexing argument. (Triggered internally at ../aten/src/ATen/native/TensorShape.cpp:3587.) During handling of the above exception, another exception occurred: Traceback (most recent call last): Do you have any advice regarding this issue, that could point me towards a solution? Best Regards, |
Hi @Jonetz , thanks for raising this. Would you please share the sequence of code you ran? The original warning against the CRS of the geopandas dataframe may be the source of the problem. You may want to project into a compatible CRS. |
Hello James, as an update, I was able to eliminate the CRS warning, changing the structure of the geopandas dataframe a bit, but this did not mitigate the original problem. This is my source code:
I use the following modules:
|
@Jonetz, thanks for sharing the code. The problem is not immediately obvious to me but you should try: In If you are happy to do so, you can share your data with me ([email protected]) and I'll have a little look. |
Hi there, when I tried to adjust my settings in tilling for training my dataset using codes below, the
tile_data_train
didn't save the tiled data into my target folder. The codes correctly created the folders, but none of the tiled result appears in the folders.I'm running it on Google colab, the problem is not always happening (works fine in most cases), but this time it happened when I simply changed
tile_width
andtile_height
for the same dataset, changingdtype_bool=True
or removenan_threshold
are not working neither. Not sure where is this bug coming from.There's no error message, and the output is like this:
The text was updated successfully, but these errors were encountered: