OwlCyberSecurity - MANAGER
Edit File: srs.cpython-39.pyc
a ���e� � @ s* d dl mZ d dlmZmZ ddd�ZdS )� )�SpatialReference)�DEFAULT_DB_ALIAS� connections�EPSGNc C s |pt }t| }t|jd�s$td��|jjs4td��|j�� }t| t �sPt | �} | j du rbtd��| j ||pp| j | j d�}dd� |j � � D �}d |v r�| j|d < d |v r�|p�| j|d < z|j�|�j| j d � W n, |jy� |j�|�jf i |�� Y n0 dS ) 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'). Zspatial_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_sridZ proj4textc S s h | ] }|j �qS � )�name)�.0�fr r �]/home/gouroczh/virtualenv/pat/3.9/lib/python3.9/site-packages/django/contrib/gis/utils/srs.py� <setcomp>A � z add_srs_entry.<locals>.<setcomp>Zsrtext� ref_sys_name)r )r r �hasattr�ops� Exception�featuresZsupports_add_srs_entryZspatial_ref_sys� isinstancer r Zproj4�_metaZ get_fieldsZwktr �objects�using�getZ DoesNotExist�create) Zsrsr r r Zdatabase� connectionZ SpatialRefSys�kwargsZsrs_field_namesr r r � add_srs_entry s6 �� r )r NNN)Zdjango.contrib.gis.gdalr Z django.dbr r r r r r r �<module> s �