I really think its possible, but would it worth the effort? I mean, this way you could also put a camera on a long arm and do a good nadir picture, but what's the objective of a street view? I think its different from 360cities, for example. At google street view the goal is not the perfect stitch, is much more get the whole world shot. I really don't mind with its parallax errors.
Anyway, its a very interesting idea and discussion. Once I have been an electronic engineer :). If I had the time I would probably be interested in doing that... by the way, there's a very good DIY projects site at instructables.com with some electronic projects that could help someone here interested in doing this. Carlos. 2011/5/24 Rogier Wolff <rew-googlegro...@bitwizard.nl> > On Mon, May 23, 2011 at 11:07:14PM -0400, Yuval Levy wrote: > > On May 23, 2011 04:30:27 PM Bruno Postle wrote: > > > I've often thought that the way to do a camera-on-a-car panorama rig > > > is to space the cameras out in a line instead of trying (and > > > failing) to put them all in the same place. Then when you are > > > driving around you shoot a panorama by firing the shutters in > > > sequence such that each photo is taken from exactly the same > > > location. > > > > if you have not done it yet, you should patent this idea ;-) > > Too late. Publication before patent means no patent. :-) > > > although in practical term it is a challenge to measure speed and > > synchronize time to trigger each camera's shutter precisely at the > > right moment. > > Speed doesn't change too much over short periods. So once you have a > speed reading. you can calculate the inter-shutter-times. Then you > trigger the cameras at precisely the right moment. > > Some cameras, especially the ones supporting "liveview" might have 60 > fps framerate, so once you press the shutter, the camera might take > the next frame at say 1-17ms after your trigger (i.e. 1 ms constant > delay and 0-16ms wait-for-start-of-frame). Humans won't notice the > difference, but when driving along at 15m/s, will give a 0.25m spread > in triggerspots. I think nikon DSLRs are good at having a > deterministic time between trigger and image taken. > > Swiss (and Russian?) banknotes have small holes in them. (Hold the > bill against the light to see them). Making those holes works the same > way: the speed is measured, which sets the trigger-speed for each of > the holes.... > > > > The result would be zero parallax errors, but there would > > > be new errors with peoples and moving objects. > > > > There is enough space to fit six cameras (rather than four) on the roof > of a > > car, which should give enough leeway to generate sufficient overlap to > cover > > for most moving objects. Then the problem is determining the optimal > seam > > lines... > > > > > You would need some > > > way to synchronise the shutters and the speed of the car, but there > > > are no doubt plenty of ways of doing this. > > > > maybe not a timer / spedomeeter then. if a helper vehicle could stand > still > > for the time that the 4-6 cameras pass through the NPP, it could beam a > > synchronizing laser that would trigger each camera when it is on the > right > > spot. So this helper vehicle would move forward to beam the laser for > the > > next shooting position, stop, wait for all cameras on the camera vehicle > to > > cross the beam, then move on to the next position and repeat. > > Much too complicated. Google manage do do "streetview" just because > they /only/ had to drive through all streets. Nothing more complicated > than that. Sure, there are lots and lots of streets, but if you can > just drive through them at 50km/h that's much simpler than stopping > and starting for each shot every few meters..... > > If you're prepared to stop for each pano-shoot, you can save yourself > 3 or 5 cameras and rotate one camera around for each pano-shot. (with > 135-170 degrees FOV, wouldn't 3 cameras suffice?) > > Just have a sensor on one of the rear wheels. From the time one > revolution takes, you know the speed, then you calculate the trigger > times and trigger the cameras. Really easy. If you do this just after > the sensor triggers, the speed reading will be as fresh as possible. > > With gopro cameras being < 10cm, you can place 4 of them in about 30cm > of space along the car. This would mean all four cameras trigger > inside a 20ms window at 50km/h. Not much movement is going to happen > inside that time. You'll do MUCH MUCH better than streetview with this > trick. > > > Roger. > > -- > ** r.e.wo...@bitwizard.nl ** http://www.BitWizard.nl/ ** +31-15-2600998 ** > ** Delftechpark 26 2628 XH Delft, The Netherlands. KVK: 27239233 ** > *-- BitWizard writes Linux device drivers for any device you may have! --* > Q: It doesn't work. A: Look buddy, doesn't work is an ambiguous statement. > Does it sit on the couch all day? Is it unemployed? Please be specific! > Define 'it' and what it isn't doing. --------- Adapted from lxrbot FAQ > > -- > 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 > -- 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
