Shapely VS django-countries

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.

Hi, CountryField comes from django-countries (https://github.com/SmileyChris/django-countries) and is definitely not the source of the problem (for context, I have already created a basic API endpoint that displays a user profile i.e an instance of CustomUser). As for your second question, I concur that this is probably where the error lies from discussing with people over SO. However, I am not entirely sure how I can fix it. If I swap out `'''`CustomUserDetailSerializerSM''' for '''CustomUserSocialMediaSerializer''', my view would only show the user_id, social_media and social_media_url, whereas I am trying to show both the social media details as well as details about the '''CustomUser''' instance associated with those social media details (as queried using the '''username''' argument in the URL pattern).

You're using an old version of the django_countries package. It has a bug that was fixed in this commit and which should be fixed in the latest release.