-
Notifications
You must be signed in to change notification settings - Fork 8
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
opening a new file keeps the old one #16
Comments
Originally this function is intentionally designed like this. The case could be that the user have splitted files, for example a houses.json and a streets.json. Should I therefore keep this feature or put it out? |
OK yeah it's nice, let's keep it. But there seems to be something a bit wrong. I splitted Den Haag from https://www.cityjson.org/datasets/ into terrain.json and buidlings.json, and when I open them both the terrain is "higher", see: If I open them in azul, all is good. Possible that it works if both have the same bbox since you rescale? If the case then in practice it's nearly impossible to have, and then I'd drop the feature. If fixable then I'd keep it. |
but since you modify coordinates then it gets messy, see below.
Probably simpler to just flush the old model and always keep one and one, no?
The text was updated successfully, but these errors were encountered: