-
Notifications
You must be signed in to change notification settings - Fork 22
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
Reconsider DB schema #93
Comments
From the top of my head: the tags are in a separate table by design. It's because the information can be optionally added and its columns can be individually queried. Having everything in one table would remove this functionality. |
Ah ok, then you'd have to basically duplicate a lot of POIs if they have a lot of additional tags, right? Yeah, that'd be stupid, true. OK thanks for the hint! |
It is like this:
ops_planet_pois
ops_planet_pois_categories
ops_planet_pois_tags
Example:
...
...
The |
e.g.
|
Things to think about:
uuid
is mostly useless it seems, it's not the PK in most tablesintersects
query stage. Would be nicer than only querying for centroids, which is often meaningless for big areas like parks or even true MultiPolygon objects.The text was updated successfully, but these errors were encountered: