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.

Sign up for GitHub

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

Jump to bottom

Increase efficiency of GIS API calls #104

Open
smcalilly opened this issue Jan 20, 2022 · 1 comment
Open

Increase efficiency of GIS API calls #104

smcalilly opened this issue Jan 20, 2022 · 1 comment

Comments

@smcalilly
Copy link
Contributor

smcalilly commented Jan 20, 2022 •
edited
Loading

@smcalilly Can you open an issue for increasing efficiency of these API calls? I don't think the ORM has a way to bulk transform a geometry column, but we could maybe use raw SQL and st_transform to add a transformed field to our queryset in one quick PostGIS query.

Originally posted by @hancush in #93 (comment)
@smcalilly
Copy link
Contributor Author

Adding to this discussion more inefficiencies.

The signals that calculate the zone distribution, geographic distance scoring, and socioeconomic distance scoring add more overhead. It would be good to make this as efficient as possible, because it currently makes a lot of database calls for each geojson feature within a feature collection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@smcalilly