... る通常の フィールドオプション に加えて、空間フィールドには以下の追加オプションがあります。すべてオプションです。 srid ¶ BaseSpatialField. srid ¶ ジオメトリフィールドの SRID [ 2 ] (Spatial Reference System Identity) を指定した値に設定します。デフォルトは ... The SRID is an integer specifier that corresponds to the projection system that will be used to interpret the data in the spatial database. [ 3 ] Projection systems give the context to the coordinates that specify a location. Although the details of ge ... ters and miles). Using a geographic coordinate system may introduce complications for the developer later on. For example, SpatiaLite does not have the capability to perform distance calculations between geometries using geographic coordinate systems, e ... ... る通常の フィールドオプション に加えて、空間フィールドには以下の追加オプションがあります。すべてオプションです。 srid ¶ BaseSpatialField. srid ¶ ジオメトリフィールドの SRID [ 2 ] (Spatial Reference System Identity) を指定した値に設定します。デフォルトは ... The SRID is an integer specifier that corresponds to the projection system that will be used to interpret the data in the spatial database. [ 3 ] Projection systems give the context to the coordinates that specify a location. Although the details of ge ... ters and miles). Using a geographic coordinate system may introduce complications for the developer later on. For example, SpatiaLite does not have the capability to perform distance calculations between geometries using geographic coordinate systems, e ... ... e", and one security issue with severity "low" in 5.2.16. CVE-2026-15307: Server-side file-write and request forgery via spatial lookups ¶ Spatial lookups allowed str and dict lookup values to be passed to GDALRaster when they represented rasters. Dep ... ing via lookup_allowed() , the flaw was reachable by staff users with view permission on any registered model containing a spatial field. The following types are now disallowed by spatial lookups: dict A str that is not a valid GEOSGeometry , e.g. a ser ... nments to model fields are unaffected and still accept these input types. For guidance on how to keep using these types in spatial lookups, on validating untrusted input, and on further security considerations, see raster security considerations . This ... ... e", and one security issue with severity "low" in 5.2.16. CVE-2026-15307: Server-side file-write and request forgery via spatial lookups ¶ Spatial lookups allowed str and dict lookup values to be passed to GDALRaster when they represented rasters. Dep ... ing via lookup_allowed() , the flaw was reachable by staff users with view permission on any registered model containing a spatial field. The following types are now disallowed by spatial lookups: dict A str that is not a valid GEOSGeometry , e.g. a ser ... nments to model fields are unaffected and still accept these input types. For guidance on how to keep using these types in spatial lookups, on validating untrusted input, and on further security considerations, see raster security considerations . This ... ... urity issue with severity "low", and several bugs in 6.0.7. CVE-2026-15307: Server-side file-write and request forgery via spatial lookups ¶ Spatial lookups allowed str and dict lookup values to be passed to GDALRaster when they represented rasters. Dep ... ing via lookup_allowed() , the flaw was reachable by staff users with view permission on any registered model containing a spatial field. The following types are now disallowed by spatial lookups: dict A str that is not a valid GEOSGeometry , e.g. a ser ... nments to model fields are unaffected and still accept these input types. For guidance on how to keep using these types in spatial lookups, on validating untrusted input, and on further security considerations, see raster security considerations . This ... ... urity issue with severity "low", and several bugs in 6.0.7. CVE-2026-15307: Server-side file-write and request forgery via spatial lookups ¶ Spatial lookups allowed str and dict lookup values to be passed to GDALRaster when they represented rasters. Dep ... ing via lookup_allowed() , the flaw was reachable by staff users with view permission on any registered model containing a spatial field. The following types are now disallowed by spatial lookups: dict A str that is not a valid GEOSGeometry , e.g. a ser ... nments to model fields are unaffected and still accept these input types. For guidance on how to keep using these types in spatial lookups, on validating untrusted input, and on further security considerations, see raster security considerations . This ... ... This issue has severity "moderate" according to the Django security policy . CVE-2026-87890: Potential request forgery via spatial lookup byte values ¶ Spatial lookups accepted raster values provided as bytes without requiring them to be explicitly wrap ... le preparing the lookup. This issue could be exploited by applications that passed attacker-controlled bytes directly to a spatial lookup. It was overlooked in the fix for CVE-2026-15307. To mitigate this issue, raster values provided as bytes must now ... be wrapped in GDALRaster before being used in spatial lookups. Byte values representing valid hexadecimal geometries remain accepted. This is a backward incompatible change. As ... ... This issue has severity "moderate" according to the Django security policy . CVE-2026-87890: Potential request forgery via spatial lookup byte values ¶ Spatial lookups accepted raster values provided as bytes without requiring them to be explicitly wrap ... le preparing the lookup. This issue could be exploited by applications that passed attacker-controlled bytes directly to a spatial lookup. It was overlooked in the fix for CVE-2026-15307. To mitigate this issue, raster values provided as bytes must now ... be wrapped in GDALRaster before being used in spatial lookups. Byte values representing valid hexadecimal geometries remain accepted. This is a backward incompatible change. As ... ... This issue has severity "moderate" according to the Django security policy . CVE-2026-87890: Potential request forgery via spatial lookup byte values ¶ Spatial lookups accepted raster values provided as bytes without requiring them to be explicitly wrap ... le preparing the lookup. This issue could be exploited by applications that passed attacker-controlled bytes directly to a spatial lookup. It was overlooked in the fix for CVE-2026-15307. To mitigate this issue, raster values provided as bytes must now ... be wrapped in GDALRaster before being used in spatial lookups. Byte values representing valid hexadecimal geometries remain accepted. This is a backward incompatible change. As ... ... This issue has severity "moderate" according to the Django security policy . CVE-2026-87890: Potential request forgery via spatial lookup byte values ¶ Spatial lookups accepted raster values provided as bytes without requiring them to be explicitly wrap ... le preparing the lookup. This issue could be exploited by applications that passed attacker-controlled bytes directly to a spatial lookup. It was overlooked in the fix for CVE-2026-15307. To mitigate this issue, raster values provided as bytes must now ... be wrapped in GDALRaster before being used in spatial lookups. Byte values representing valid hexadecimal geometries remain accepted. This is a backward incompatible change. As ... 2026年10月08日