<div dir="ltr">Hey,<div>getting something similar to a surface visualization out of points without computing explicit surface is actively researched.</div><div><br></div><div>Usually it's very easy for a graphic card (GC) to drape a texture over a geometry. It is its main purpose. I wouldn't worry too much about that (already done in WebGL). Of course it would be cool to get some color out of raster, maybe with postgis raster (I just began to test it, actually trying to do the inverse : create DEM from points).</div>
<div><br></div><div>What you call average vector is the estimated normal vector of the point.</div><div>It can be estimated with various methods and is required for almost everything (including display to get shadows or lighting effects very useful to better "understand" the surface for an human eye).</div>
<div><br></div><div>If it's just for visualization, you can let the GC do the work. It is incredibly fast. (various "shaders" do it).</div><div><br>If you need normal for other computing (most algorithm use it), you may want to pre-compute.</div>
<div>This can become tricky for 3 reasons : </div><div>_it is in fact a local surface interpolation. So, what surface do you choose, and how local is it (plan, sphere, polynom , fixed distance, fixed number of neighbors ...)</div>
<div>_the computing always involve nearest neighbors. Needless to say you <b>*have*</b> to use a LOD (for example, compute per patch, on small patch, or use an octree).</div><div>_How to store it? You can do it in pointcloud of course but is is a little boring. A dirty workaround would be to store it as float[3][]. Usually in point cloud software it is stored like X,Y,Z and other attributes, something like n_x,n_y ... </div>
<div><br></div><div>If you want to play with point cloud and see various option to visualize with normal based lighting, and to compute normal with various parameters, a very good open source software is <a href="http://www.danielgm.net/cc/">CloudCompare</a>. It is easy (like drag and drop point cloud file) and powerful.</div>
<div><br></div><div>Cheers,</div><div>Rémi-C</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/12/18 Basques, Bob (CI-StPaul) <span dir="ltr"><<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">Rémi</span><span style="font-size:8.0pt;font-family:"Comic Sans MS"">,<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">What are your thoughts about colorizing points, from say aerial photo’s? Do you think this is possible as an on the fly piece of the equation, or something that would need to be
stored in the database? I ask, because a lot of 3D rendering clients have difficulties with displaying stacked images as drapes on a surface, if there were a method to colorize the points on the fly, then multiple colorizing passes would have the same effect
as stacking the source images onto a surface, which with densely packed points, might negate the need to even build a surface model at all.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">Also, have you thought at all about how to store average vectors for each point (a vector perpendicular to a plane created from nearest point averaging) Probably too soon to bring
some of this up, but I thought it might be better up front than later.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS"">Bobb<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""><u></u> <u></u></span></p>
<p class="MsoNormal"><span style="font-size:8.0pt;font-family:"Comic Sans MS""><u></u> <u></u></span></p>
<p class="MsoNormal" style="margin-left:.5in"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a> [mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>]
<b>On Behalf Of </b>Rémi Cura<br>
<b>Sent:</b> Wednesday, December 18, 2013 2:01 AM</span></p><div><div class="h5"><br>
<b>To:</b> PostGIS Users Discussion<br>
<b>Subject:</b> Re: [postgis-users] Old question resurfacing<u></u><u></u></div></div><p></p><div><div class="h5">
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">Hey,<u></u><u></u></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">I contacted the developper of XB PointStream specifically to ask him how to plug it to a postgres DB.<br>
It is no more an active project and he advised against it.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">At the other hand, with a much better licence (FreeBSD), active dev, and build in level Of Detail (LOD) feature (scene graph):<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><a href="http://potree.org/" target="_blank">http://potree.org/</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">I asked the same question and it would be possible to plug it to db.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">We only need to develop a LOD inside DB to to make it possible to use it with huge database (I'm talking about 10's of billions at least in base, and several millions in cache/browser). ( Here my gothub project
doc, the project is not clean enough to be used by others, but the slides contains some images :<a href="https://github.com/Remi-C/LOD_ordering_for_patches_of_points/tree/master/doc" target="_blank">https://github.com/Remi-C/LOD_ordering_for_patches_of_points/tree/master/doc</a> )<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Current WebGL limit with most graphic card seems to be around 10^6 points, it is very small, hence the obligation to have LOD support to have maybe 10 * 10^6 points in cache in LOD structure in browser, and display
only 10^6 points, but cleverly : <u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">more points close to viewer camera and in front of it, few points when far from viewer camera, zero point behind camera.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">These are very old and effective computer graphics tricks.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Cheers,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Rémi-C<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
</div>
<div>
<p class="MsoNormal" style="margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<u></u> <u></u></p>
<div>
<p class="MsoNormal" style="margin-left:.5in">2013/12/17 Basques, Bob (CI-StPaul) <<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a>><u></u><u></u></p>
<p class="MsoNormal" style="margin-left:.5in">Hi Frank,<br>
<br>
I've been watching this approach develop over the past few year. Some intereing approaches to using the point based methods of display that I've zeroed in on use feature that they describe as Surfels and/or Splats. Just Google those two key words and you'll
see what I'm talking about.<br>
<br>
<a href="http://graphics.ucsd.edu/~matthias/Papers/Surfels.pdf" target="_blank">http://graphics.ucsd.edu/~matthias/Papers/Surfels.pdf</a><br>
<br>
One drawback to these approaches is that they are sort of a closed system in that they concentrate on only displaying the point based features. In the end, as a real world tool, I'll need to incorporate into this type of visualizers, I means of mixing feature
types. Surface tins, CAD models, and Points. Having the points reside in a DB will both help with the integration as well as allow some processing of things to be accomplished on the fly in this mixed feature viewer.<br>
<br>
Bobb<u></u><u></u></p>
<div>
<div>
<p class="MsoNormal" style="margin-left:.5in"><br>
<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a> [mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>] On Behalf Of Frank Henze<br>
Sent: Sunday, December 15, 2013 2:10 PM<br>
To: PostGIS Users Discussion<br>
Subject: Re: [postgis-users] Old question resurfacing<br>
<br>
I dont know, at which point the downsampling should take place.<br>
An interesting solution for webbased visualization could be XB Point Stream:<br>
<a href="http://zenit.senecac.on.ca/wiki/index.php/XB_PointStream" target="_blank">http://zenit.senecac.on.ca/wiki/index.php/XB_PointStream</a><br>
<br>
Frank<br>
<br>
Am 15.12.2013 00:45, schrieb Rémi Cura:<br>
> I guess everybody has reached the same conclusion :<br>
> using pointcloud is is possible to manage 100's of billions of points<br>
> and retrieve quickly those of interest.<br>
><br>
> Now most of the usage requiere severe downsampling, which isn't a part<br>
> of anything yet but may come (I'm working on adding this to pointcloud).<br>
> .<br>
><br>
> Cheers,<br>
><br>
> Rémi-C<br>
><br>
><br>
> 2013/12/12 Basques, Bob (CI-StPaul) <<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a><br>
> <mailto:<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a>>><br>
><br>
> Frank,<br>
><br>
> I don't know about a group, or for that matter centering it on just<br>
> PostGIS, but I see 3D as the next big Mapping product line that<br>
> people are going to be looking for. PostGIS is a piece in a bigger<br>
> puzzle. I've been researching different methods for storing and<br>
> segmenting the point cloud data on the server side for a while now<br>
> and PostGIS has percolated up to near the top of the list.<br>
><br>
> There is a big piece related in how to generalize data for 3D<br>
> scaling in the browser, that's the biggest shortcoming I've become<br>
> aware of in order to make something run nicely in the browser, I've<br>
> also of late been forcing myself to think mobile, which has it's own<br>
> set of criteria as far as the browser goes.<br>
><br>
> I would likely join the list of something call PostGIS 3d, but I<br>
> don't know that there is enough interest for a whole community<br>
> (yet), maybe it's better to stay ahead of the curve though.<br>
><br>
><br>
> Bobb<br>
><br>
><br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>><br>
> [mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>>] On Behalf Of Frank Henze<br>
> Sent: Thursday, December 12, 2013 1:17 PM<br>
> To: PostGIS Users Discussion<br>
> Subject: Re: [postgis-users] Old question resurfacing<br>
><br>
> Hi all,<br>
><br>
> briefly a few details to <a href="http://www2.htw-dresden.de/~s68071/3DWebGIS/" target="_blank">
http://www2.htw-dresden.de/~s68071/3DWebGIS/</a>:<br>
><br>
> - Projektauswahl: Baalbek and Palatin are static X3D models (no<br>
> PostGIS)<br>
> - Projektauswahl: W3DS is dynamically generated from a PostGIS 2.0 DB<br>
> via a "GetScene"-request by Geoserver<br>
><br>
> I think Baalbek is too large (too many triangles) and therefore<br>
> possibly leads to crash. Palatin and W3DS should work.<br>
><br>
> The 3D window is a standard WebGL window based on X3DOM. So it<br>
> should run right stable.<br>
><br>
> Once again my question:<br>
> Is there an interest in a PostGIS 3D group?<br>
><br>
> Frank<br>
><br>
> Am 12.12.2013 16:55, schrieb Basques, Bob (CI-StPaul):<br>
> > Frank,<br>
> ><br>
> > Very nice. It froze up for me pretty quickly, I tried both FF<br>
> and Chrome. Still looked good while it ran.<br>
> ><br>
> > This stability aspect is a big piece of being able to make<br>
> something that folks will want to use. Data segregation will be a<br>
> big piece moving forward I think.<br>
> ><br>
> > Bobb<br>
> ><br>
> ><br>
> ><br>
> > -----Original Message-----<br>
> > From: <a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>><br>
> > [mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>>] On Behalf Of Frank<br>
> > Henze<br>
> > Sent: Thursday, December 12, 2013 6:04 AM<br>
> > To: PostGIS Users Discussion<br>
> > Subject: Re: [postgis-users] Old question resurfacing<br>
> ><br>
> > Hi Bobb,<br>
> > hi all,<br>
> ><br>
> > <a href="https://hub.sharedgeo.org/apps/x3d/" target="_blank">https://hub.sharedgeo.org/apps/x3d/</a> looks great!<br>
> ><br>
> > We have similar requirements for a 3d WebGIS.<br>
> > A first prototype you can find at:<br>
> ><br>
> > <a href="http://www2.htw-dresden.de/~s68071/3DWebGIS/" target="_blank">http://www2.htw-dresden.de/~s68071/3DWebGIS/</a><br>
> ><br>
> > For "Projektauswahl:" select "W3DS"<br>
> ><br>
> > and then select "Historische Gebäude" (Historical Buildings)<br>
> ><br>
> > If there is nothing to see, then press on the left side "Alles<br>
> anzeigen"<br>
> ><br>
> > We use the community buildt Geoserver incl. Web 3D service +<br>
> X3DOM + JS.<br>
> ><br>
> > Some of our problems:<br>
> ><br>
> > How to import 3D geometries into PostGIS?<br>
> > Which formats and interfaces (CAD, X3D)?<br>
> > Point clouds in PostGIS (also import of).<br>
> ><br>
> > Is there a 3D PostGIS interest-group?<br>
> > If not, should one established?<br>
> ><br>
> > Frank<br>
> ><br>
> > Am 11.12.2013 17:44, schrieb Basques, Bob (CI-StPaul):<br>
> >> All,<br>
> >><br>
> >> Nothing that far along. Did a couple of proofs of concept so far,<br>
> >> I've done a couple of presentations on the Visualizer approach. We<br>
> >> tried a couple of different things, x3Dom, allover'js<br>
> >><br>
> >> You can see some of them here ( some of the pages take a while to<br>
> >> load the data in the background, be patient):<br>
> >><br>
> >> <a href="https://hub.sharedgeo.org/apps/x3d/" target="_blank">https://hub.sharedgeo.org/apps/x3d/</a> (these will generally need a<br>
> >> webGL enabled browser)<br>
> >><br>
> >> These are purely intended as a test of just how much data could<br>
> >> easily be squished into the browser before if blows, so you<br>
> might experience<br>
> >> some failures. Ideally the data coming into these would be<br>
> segmented<br>
> >> via a SQL call to PostGIS Pointcloud sources.<br>
> >><br>
> >> The last two in the list are using some point clouds cut from our<br>
> >> recent data collect at 8pt per sq meter for the City (6 billion<br>
> >> points in all), these are using about 300k points each for example.<br>
> >><br>
> >> Bobb<br>
> >><br>
> >> *From:*<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>><br>
> >> [mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>>] *On Behalf Of *Rémi<br>
> >> Cura<br>
> >> *Sent:* Wednesday, December 11, 2013 10:08 AM<br>
> >> *To:* PostGIS Users Discussion<br>
> >> *Subject:* Re: [postgis-users] Old question resurfacing<br>
> >><br>
> >> I would be very interested to know any attempt to visualize 3D point<br>
> >> cloud from data base !<br>
> >><br>
> >> We did the same but our solution is far from perfect.<br>
> >><br>
> >> Bob, is you rporject public/open source, have you any paper/doc<br>
> about it ?<br>
> >><br>
> >> Cheers,<br>
> >><br>
> >> Rémi-C<br>
> >><br>
> >> 2013/12/11 Basques, Bob (CI-StPaul) <<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a><br>
> <mailto:<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a>><br>
> >> <mailto:<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a><br>
> <mailto:<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a>>>><br>
> >><br>
> >> Hmm,<br>
> >><br>
> >> I'm working with the Minneapolis International Airport (MSP) on a<br>
> >> project, any chance that data is open/accessible enough to play<br>
> with?<br>
> >> This could tie directly into a project I'm already working on.<br>
> >><br>
> >> Thanks<br>
> >><br>
> >> Bobb<br>
> >><br>
> >> *From:*<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>><br>
> >> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>>><br>
> >> [mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>><br>
> >> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>>>] *On Behalf Of *Gerry<br>
> >> Creager - NOAA Affiliate<br>
> >> *Sent:* Tuesday, December 10, 2013 2:14 PM<br>
> >><br>
> >><br>
> >> *To:* PostGIS Users Discussion<br>
> >> *Subject:* Re: [postgis-users] Old question resurfacing<br>
> >><br>
> >> Bob, all:<br>
> >><br>
> >> I agree. I'll have to spend some time with pointcloud but it DOES<br>
> >> look very promising.<br>
> >><br>
> >> Another application? Lidar. Pointed at the sky, not at the<br>
> ground (we<br>
> >> use 'em to determine cloud layers [ceiling] and sky cover at<br>
> airports<br>
> >> for aviation data...).<br>
> >><br>
> >> Thanks, all!<br>
> >><br>
> >> gerry<br>
> >><br>
> >> On Tue, Dec 10, 2013 at 1:49 PM, Basques, Bob (CI-StPaul)<br>
> >> <<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a><br>
> <mailto:<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a>><br>
> <mailto:<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a><br>
> <mailto:<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a>>>> wrote:<br>
> >><br>
> >> Gerry,<br>
> >><br>
> >> Remi's idea about using a point cloud may be spot on for your use.<br>
> >> It allows you to set a point cloud down to a revolution if need be,<br>
> >> which seems like what you are looking for.. If the data becomes too<br>
> >> massive for insertion into DB at real-time speeds, then you could<br>
> >> also separate this revolution into separate DB's as well, you could<br>
> >> separate a whole number of ways, by elevation, or quadrant, or . . .<br>
> >><br>
> >> I'm very interested in visualization possibilities with something<br>
> >> like this being available in a database. We're doing some<br>
> similar db<br>
> >> 3d visualization stuff on some rather dense point clouds. Your data<br>
> >> once available could use the same visualizer.<br>
> >><br>
> >> Bobb<br>
> >><br>
> >> *From:*<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>><br>
> >> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>>><br>
> >> [mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>><br>
> >> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>>>] *On Behalf Of *Gerry<br>
> >> Creager - NOAA Affiliate<br>
> >> *Sent:* Tuesday, December 10, 2013 1:41 PM<br>
> >> *To:* PostGIS Users Discussion<br>
> >> *Subject:* Re: [postgis-users] Old question resurfacing<br>
> >><br>
> >> Bob<br>
> >><br>
> >> At least preliminarily, I can post-process, so speed of db adds<br>
> isn't<br>
> >> too troubling. Maintaining accurate representation of the bin-volume<br>
> >> data is, however, important.<br>
> >><br>
> >> Typical rotation is 1-3 RPM, and a complete volume scan takes<br>
> ~11 min<br>
> >> in clear air (where you best see biologicals if so inclined) or ~5<br>
> >> min in one of the storm data collection modes. These are for common<br>
> >> WSR88D, stationary radars. SMARTR's and others we have here that are<br>
> >> mobile present a whole host of other options/data eval and speed<br>
> problems.<br>
> >><br>
> >> Current radar data are nominally considered to have a horizontal<br>
> >> resolution of ~250 m, ignoring distortion or keyholing due to<br>
> >> range.Typically 16 elevations are scanned, once or or twice in storm<br>
> >> mode and a few less elevations in clear air mode.<br>
> >><br>
> >> Now, the interesting thing that's on the horizon is Phased Array<br>
> Radar.<br>
> >> When that happens, more data, more resolution, and faster updates.<br>
> >><br>
> >> gerry<br>
> >><br>
> >> On Tue, Dec 10, 2013 at 11:05 AM, Basques, Bob (CI-StPaul)<br>
> >> <<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a><br>
> <mailto:<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a>><br>
> <mailto:<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a><br>
> <mailto:<a href="mailto:bob.basques@ci.stpaul.mn.us" target="_blank">bob.basques@ci.stpaul.mn.us</a>>>> wrote:<br>
> >><br>
> >> Gerry,<br>
> >><br>
> >> Seems like the biggest hangup would be in adding the data to the DB<br>
> >> fast enough. How many points, per revolution, and what is the<br>
> >> frequency of a revolution (stationary Radar, correct, although as I<br>
> >> think about it, it could be mobile if needed, just need to add<br>
> in the<br>
> >> radar location to each record)?<br>
> >><br>
> >> Bobb<br>
> >><br>
> >> *From:*<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>><br>
> >> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>>><br>
> >> [mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>><br>
> >> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users-bounces@lists.osgeo.org" target="_blank">postgis-users-bounces@lists.osgeo.org</a>>>] *On Behalf Of *Gerry<br>
> >> Creager - NOAA Affiliate<br>
> >> *Sent:* Tuesday, December 10, 2013 10:52 AM<br>
> >> *To:* PostGIS Users Discussion<br>
> >> *Subject:* [postgis-users] Old question resurfacing<br>
> >><br>
> >> I asked this years ago, and I think Paul was less than pleased with<br>
> >> me (:-), but:<br>
> >><br>
> >> Has anyone, in the ensuing years looked at encoding radar data<br>
> into a<br>
> >> postGIS database? We've a little idea that might benefit one<br>
> project,<br>
> >> and getting the radar data into a good geospatial format would be<br>
> >> beneficial.The data, of coure, would start out as<br>
> radial-distance and<br>
> >> intensity from the radar site, although we could preprocess it<br>
> by gridding.<br>
> >><br>
> >> Thanks, Gerry<br>
> >><br>
> >> --<br>
> >><br>
> >> Gerry Creager<br>
> >><br>
> >> NSSL/CIMMS<br>
> >><br>
> >> 405.325.6371 <<a href="tel:405.325.6371" target="_blank">tel:405.325.6371</a>><br>
> >><br>
> >> ++++++++++++++++++++++<br>
> >><br>
> >> "Big whorls have little whorls,<br>
> >><br>
> >> That feed on their velocity;<br>
> >><br>
> >> And little whorls have lesser whorls,<br>
> >><br>
> >> And so on to viscosity."<br>
> >><br>
> >> Lewis Fry Richardson (1881-1953)<br>
> >><br>
> >><br>
> >> _______________________________________________<br>
> >> postgis-users mailing list<br>
> >> <a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>
> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>>><br>
> >> <a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br>
> >><br>
> >><br>
> >><br>
> >> --<br>
> >><br>
> >> Gerry Creager<br>
> >><br>
> >> NSSL/CIMMS<br>
> >><br>
> >> 405.325.6371 <<a href="tel:405.325.6371" target="_blank">tel:405.325.6371</a>><br>
> >><br>
> >> ++++++++++++++++++++++<br>
> >><br>
> >> "Big whorls have little whorls,<br>
> >><br>
> >> That feed on their velocity;<br>
> >><br>
> >> And little whorls have lesser whorls,<br>
> >><br>
> >> And so on to viscosity."<br>
> >><br>
> >> Lewis Fry Richardson (1881-1953)<br>
> >><br>
> >><br>
> >> _______________________________________________<br>
> >> postgis-users mailing list<br>
> >> <a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>
> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>>><br>
> >> <a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br>
> >><br>
> >><br>
> >><br>
> >> --<br>
> >><br>
> >> Gerry Creager<br>
> >><br>
> >> NSSL/CIMMS<br>
> >><br>
> >> 405.325.6371<br>
> >><br>
> >> ++++++++++++++++++++++<br>
> >><br>
> >> "Big whorls have little whorls,<br>
> >><br>
> >> That feed on their velocity;<br>
> >><br>
> >> And little whorls have lesser whorls,<br>
> >><br>
> >> And so on to viscosity."<br>
> >><br>
> >> Lewis Fry Richardson (1881-1953)<br>
> >><br>
> >><br>
> >> _______________________________________________<br>
> >> postgis-users mailing list<br>
> >> <a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>
> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>>><br>
> >> <a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br>
> >><br>
> >><br>
> >><br>
> >> _______________________________________________<br>
> >> postgis-users mailing list<br>
> >> <a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>
> >> <a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br>
> >><br>
> > _______________________________________________<br>
> > postgis-users mailing list<br>
> > <a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>
> > <a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > postgis-users mailing list<br>
> > <a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>
> > <a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br>
> ><br>
> _______________________________________________<br>
> postgis-users mailing list<br>
> <a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>
> <a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br>
><br>
><br>
> _______________________________________________<br>
> postgis-users mailing list<br>
> <a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a> <mailto:<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a>><br>
> <a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> postgis-users mailing list<br>
> <a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
> <a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br>
><br>
_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br>
<br>
<br>
_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@lists.osgeo.org" target="_blank">postgis-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><u></u><u></u></p>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-left:.5in"><u></u> <u></u></p>
</div>
</div></div></div>
</div>
<br>_______________________________________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@lists.osgeo.org">postgis-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users" target="_blank">http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users</a><br></blockquote></div><br></div>