Shapely VS fastapi

https://github.com/shapely/shapely First paragraph of readme agrees w/ me

The frames' vector data is generated using a sketch made with my vsketch framework (it involves loading GeoJSON data, processing it with Shapely, and projecting it in 3D with NumPy).

As has been said the definition of a GIS dev is far from written in stone, but to chime in from a personal standpoint: most of what I do is data wrangling/analysis with shapely/geopandas for vectors (or pygeos / fiona for performance when data volumes get large, but seeing as Shapely 2.0 just got released one can likely skip this part) + rasterio for rasters as well as parallelising these tasks for performance if needed (ray is great for that) and then performing machine learning learning against the data (mostly with sklearn and torch).

geopandas and the underlying geometry library shapely provide an alternative to the majority of the basic GIS functionality of qgis. See e.g. https://autogis-site.readthedocs.io/en/latest/ for a tutorial for the basics of these libraries.

It has been an interesting exercise developing this wrapper component. The fact that it seamlessly integrates with the FastAPI framework is just a bonus for me; I didn't plan for it since I hadn't learned FastAPI at the time. I hope you find this post useful. Thank you for reading, and stay safe as always.

FastAPI is a modern, high-performance web framework for building APIs with Python, based on standard Python type hints.

In this tutorial, I will demonstrate how to use Burr, an open source framework (disclosure: I helped create it), using simple OpenAI client calls to GPT4, and FastAPI to create a custom email assistant agent. We’ll describe the challenge one faces and then how you can solve for them. For the application frontend we provide a reference implementation but won’t dive into details for it.

That’s when I found FastAPI.

FastAPI & Uvicorn

Discussion at FastAPI GitHub: https://github.com/tiangolo/fastapi/issues/2696

An API application framework (such as FastAPI)

It’s been my experience that async Python frameworks tend to turn IO bound problems into CPU bound problems with a high enough request rate, because due to their nature they act as unbounded queues.

This ends up made worse if you’re using sync routes.

If you’re constrained on a resource such as a database connection pool, your framework will continue to pull http requests off the wire that a sane client will cancel and retry due to timeouts because it takes too long to get a connection out of the pool. Since there isn’t a straightforward way to cancel the execution of a route handler in every Python http framework I’ve seen exhibit this problem, the problem quickly snowballs.

This is an issue with fastapi, too- https://github.com/tiangolo/fastapi/issues/5759

Fast API.