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

Consider allowing geometry fields through foreign key relations #8

Open
stewjb opened this issue Apr 10, 2021 · 1 comment
Open

Consider allowing geometry fields through foreign key relations #8

stewjb opened this issue Apr 10, 2021 · 1 comment

Comments

@stewjb
Copy link

stewjb commented Apr 10, 2021

It seems like features can only be generated with querysets from models that have embedded geometry fields. There are times where it makes more sense to start with another model and access the geometry field through a foreign key relation.

@vdboor
Copy link
Contributor

vdboor commented May 17, 2021

Thanks an interesting idea, and I'm all for supporting that.

This change will no doubt bump into a lot of issues but they are totally solvable within the current design (e.g. the FeatureType / XSD type abstractions)

I do would like to ask if you could write a PR for this. This isn't something we're expecting to need in the near future.

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

No branches or pull requests

2 participants