Bryce L Nordgren a écrit :
> Standard deviation is only standard deviation if the calculation is
> performed on a random sampling of a normal distribution. You can use
> the equation on any set of numbers, of course, but that doesn't mean
> that a standard deviation pops out. :) I think in this scenario, we're
> talking about systemic errors resulting from the transformation
> parameters being slightly off. I could live with the notion of a
> "bounded error" (min error and max error) instead of a std dev.
In my understanding, "Root Mean Squared Error" sound like an appropriate name
for what is being calculated.
> I like your "Statistics" approach, below. However, I think there might
> already be a 19115 metadata object that has min/max values at least.
> Maybe if we need extra fields, we should just extend that?
I don't remember a ISO 19115 metadata object holding that? (there is too many
metadata object to remember...). If you can point me to such object, for sure
it
would be nice to extend it.
> I fear this approach for coverages with many points. It smacks of good
> design, but seems like it would be a memory hog. Perhaps a
> Map<DirectPosition,DirectPosition> where the values are calculated from
> the keys on demand?
I think that peoples will typically have something like 10 or 100 points, 1000
at most. We should not have as many points as in a coverage. With too many
points, the rounding error in calculator algorithms may become significant
anyway.
Thanks,
Martin
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
