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

use geometry for selects #185

Closed
wants to merge 13 commits into from

Conversation

MarkusZehner
Copy link
Contributor

added geometry as Column in data table, select and insert function to be able to select more precise spatially. as the column is simply added at the moment, this might lead to an error with the prior data table.

… be able to select more precise spatially. as the column is simply added at the moment, this might lead to an error with the prior data table.
…pdate missing geometries by removing and adding scenes again from data table. fixed get_colnames
…pdate missing geometries by removing and adding scenes again from data table. fixed get_colnames
…ds to target different tables than only data
…into add_geometry

� Conflicts:
�	pyroSAR/drivers.py
@MarkusZehner
Copy link
Contributor Author

The table substitution does now work properly, although there is no easy way around to reading all data again for ingestion, but that would be needed anyway for the geometry column.

@johntruckenbrodt
Copy link
Owner

closed in favor of #296

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants