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

Investigate performance of getAvailableCoordinateReferenceSystems #7643

Open
ben-polinsky opened this issue Feb 3, 2025 · 0 comments
Open

Investigate performance of getAvailableCoordinateReferenceSystems #7643

ben-polinsky opened this issue Feb 3, 2025 · 0 comments
Assignees
@ben-polinsky

Comments

@ben-polinsky
Copy link
Contributor

ben-polinsky commented Feb 3, 2025 •
edited
Loading

Filtering getAvailableCoordinateReferenceSystems by extent through native code is much slower than pre-fetching the crs list and then filtering in node.

Call to native to filter by extent: 1.45s
Call to TS to filter by extent: 15 ms
@ben-polinsky ben-polinsky self-assigned this Feb 3, 2025
@ben-polinsky ben-polinsky changed the title Investigate performance of getAvailableCoordinateReferenceSystems when passing extent for comparison Investigate performance of getAvailableCoordinateReferenceSystems Feb 5, 2025
@ben-polinsky ben-polinsky mentioned this issue Feb 5, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ben-polinsky ben-polinsky

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ben-polinsky