Skip to content
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

Bug: uploaded tabular datasets have a fixed bounding box of 0,0,0,0 #18

Open
mwallschlaeger opened this issue Oct 9, 2024 · 2 comments
Labels
52n bug Something isn't working documentation Improvements or additions to documentation enhancement New feature or request

Comments

@mwallschlaeger
Copy link

but in geonode e.g. documents have a default bounding box of:

Min Lat-90.000000
Min Lon-180.000000
Max Lat90.000000
Max Lon180.000000

In my opinion this is the preferred way of dealing with tabular data.

@mwallschlaeger mwallschlaeger added bug Something isn't working documentation Improvements or additions to documentation enhancement New feature or request 52n labels Oct 9, 2024
@ridoo
Copy link
Member

ridoo commented Oct 10, 2024

@mwallschlaeger does this relates to #19 somehow? There you describe the effect what happens if a bbox gets extended unintentionally. However, using the globe as bbox would have a similar effect, right?

@mwallschlaeger
Copy link
Author

@ridoo yes it is related to #19 . If a map contains geodata and non geodata the bbox should only build from datasets with subtype != "tabular". But if a map only contains of tabular data the map must have the worldwide bbox tabular data is suppose to have as well. Or bbox can be overwritten using api or ui

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
52n bug Something isn't working documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants