Fixed the projection from projected to geographic CRS.
There were 2 problems:
When a file was reprojected, the same number of important digits was used as in the original file. I fixed this to keep the original number only if both CRS are projected or if both are geographic. Otherwise for geographic I keep 6 important digits and 3 for projected. :
Even though the scale was float, if we had more that 3 important digits the json.dumps would convert the float to its scientific form. This would cause the city.json to have the scale in scientific form. I had to tweak the encoder to do that. Found the answer here: https://stackoverflow.com/a/70154903/3709062
This is how a 3DBAG tile looked like when transformed to 4979 before(pink) and after (blue):
Fixed the projection from projected to geographic CRS. There were 2 problems:
When a file was reprojected, the same number of important digits was used as in the original file. I fixed this to keep the original number only if both CRS are projected or if both are geographic. Otherwise for geographic I keep 6 important digits and 3 for projected. :
Even though the scale was float, if we had more that 3 important digits the json.dumps would convert the float to its scientific form. This would cause the city.json to have the scale in scientific form. I had to tweak the encoder to do that. Found the answer here: https://stackoverflow.com/a/70154903/3709062
This is how a 3DBAG tile looked like when transformed to 4979 before(pink) and after (blue):