On 19 March 2010 00:25, Bruno Postle <br...@postle.net> wrote: > On Thu 18-Mar-2010 at 09:55 -0700, Tom Sharpless wrote: >> >> 3) Much of the info -- especially on sensors, mfgr's codes, etc. -- >> should be kept up to date by a dedicated central agency, and updates >> must be easy to get hold of. Bruno's idea of an online query facility >> is not farfetched, but the now traditional automatic update of a local >> db off the internet is essential. > > Actually I'm suggesting the opposite: we could harvest the results of > thousands of people stitching panoramas and use it to build the database. > For this we need some way to reasonably 'average' lens parameters, I > suggested an internal conversion from panotools polynomial to a spline model > would work for averaging. > > -- > Bruno >
That sounds nice. If I got it you mean that the user would send the information to the database and the database would publish the parameters which are the most frequent for given lens. I like that idea because it doesn't need anyone to check the parameters. Lukas -- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to hugin-ptx@googlegroups.com To unsubscribe from this group, send email to hugin-ptx+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/hugin-ptx To unsubscribe from this group, send email to hugin-ptx+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
