-
Notifications
You must be signed in to change notification settings - Fork 32
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
Question: Merge function fails due to the "transform" key not being found #188
Comments
It's loaded but it's not printed by that function. If you do this you should see it: print(cityjson_cm.transform) See there how to use it: Hope this helps |
Hey! thanks for your help! I can now see the 'transform' information using the solution you proposed. I still can't get it to work properly when trying to merge the different tiles together using merge().
it results in this error:
|
Still trying to figure this out. On my work machine it works flawlessly, but on my personal machine it always stops with this error. I have double checked the versions and have made multiple venv's with the requirements.txt from my work PC's venv. Anyone any clue? |
Hi @rob-scholten95 , could you try:
You'll find some more material here: https://github.com/3DGI/3dbag-workshop-foss4gnl2021 . The workshop explains how the different parts of cjio work together at the moment. |
I have been trying to merge four tiles, downloaded through WFS in Blender:
3DBAG tiles:
['9/248/576', '9/248/580', '9/252/576', '9/252/580']
The code i use for loading in the file to be read:
Now, in this file, I have verified multiple times that there is no "transform" key in the file. Now when I load it in as an normal JSON,
the 'transform' key does exist. The key also exists when I download the tile from the WFS service:
This is the output:
of this code:
this is the collapsed structure of the downloaded JSON file, where the transform key is visible:
I am probably missing something, but i am desperate. Any help would be greatly appreciated!
The text was updated successfully, but these errors were encountered: