+ Tj ,^RIHt^RIHtHtRRltR#))SpatialReference)DEFAULT_DB_ALIAS connectionsNcT;'g\p\V,p\VPR4'g \ R4hVP P 'g \ R4hVPP4p\V\4'g \V4pVPf \ R4hRVPRTRT;'g VPR VP/pVPP4Uu0uFqPkK p pR V 9dVPVR &R V 9dT;'g VPVR &VP P#V4P%VPR 7R#uupi TP&d0TP P#T4P(!R /TBR#i;i)a Take a GDAL SpatialReference system and add its information to the `spatial_ref_sys` table of the spatial backend. Doing this enables database-level spatial transformations for the backend. Thus, this utility is useful for adding spatial reference systems not included by default with the backend: >>> from django.contrib.gis.utils import add_srs_entry >>> add_srs_entry(3857) Keyword Arguments: auth_name: This keyword may be customized with the value of the `auth_name` field. Defaults to 'EPSG'. auth_srid: This keyword may be customized with the value of the `auth_srid` field. Defaults to the SRID determined by GDAL. ref_sys_name: For SpatiaLite users only, sets the value of the `ref_sys_name` field. Defaults to the name determined by GDAL. database: The name of the database connection to use; the default is the value of `django.db.DEFAULT_DB_ALIAS` (at the time of this writing, its value is 'default'). spatial_versionz=The `add_srs_entry` utility only works with spatial backends.z4This utility does not support your database backend.NzMSpatial reference requires an SRID to be compatible with the spatial backend.srid auth_name auth_srid proj4textsrtext ref_sys_name)r)rrhasattrops Exceptionfeaturessupports_add_srs_entryspatial_ref_sys isinstancerrproj4_meta get_fieldsnamewktobjectsusingget DoesNotExistcreate) srsr r r database connection SpatialRefSyskwargsfsrs_field_namess &&&&& Q/var/www/idalgo/venv/lib/python3.14/site-packages/django/contrib/gis/utils/srs.py add_srs_entryr(s>+++HX&J :>>#4 5 5WXX    5 5 5NOONN224M c+ , ,s# xx 3   YY**#((SYY F(5':':'E'E'GH'G!vv'GOH?"77x(!-!9!9~? ##H-11sxx1@I  % %?##H-44>v>?sF5Fr-s43I?r,