#25734: Nodata value not excluded when computing GDALBand min/max values
-------------------------------------+-------------------------------------
     Reporter:  yellowcap            |                    Owner:  nobody
         Type:  Bug                  |                   Status:  new
    Component:  GIS                  |                  Version:  1.8
     Severity:  Normal               |               Resolution:
     Keywords:  raster gdal gis      |             Triage Stage:  Ready for
                                     |  checkin
    Has patch:  1                    |      Needs documentation:  0
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------

Comment (by Tim Graham <timograham@…>):

 In [changeset:"0e7d59df3ed6988cd5a45e26414c013ad40c7402" 0e7d59d]:
 {{{
 #!CommitTicketReference repository=""
 revision="0e7d59df3ed6988cd5a45e26414c013ad40c7402"
 Refs #25734 -- Relaxed GDALRaster statistics test to use
 assertAlmostEqual.

 Some versions of GDAL give slightly different results.
 }}}

--
Ticket URL: <https://code.djangoproject.com/ticket/25734#comment:15>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.be71872fc83a9eede3c1401a3d07c659%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to