<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Hello Wendell.<br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">For you to know, we are all on this mailing list:<br><a href="https://lists.osgeo.org/mailman/listinfo/mobilitydb-dev">https://lists.osgeo.org/mailman/listinfo/mobilitydb-dev</a><br><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">To make the communication easier in the future, can you please register to that mailing list.<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">We think your comments are important to all of us, and more people that are already in the list can not read or comment. (unless we forward the mail)<br></div><br><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Note that I do not need to add that long list of people when sending this mail as it will be received by all of us because we are all registered to the mailing list.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Thanks for your comprehension.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif">Vicky<br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jun 13, 2022 at 8:40 AM Wendell Turner <<a href="mailto:WTurner@cssiinc.com">WTurner@cssiinc.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Hello Esteban,<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
I'm not using PostGreSQL version 11 anywhere. I have one 12.8 that should be upgraded, and most of my other installations are 14.2.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Also, I've recently upgraded to Shapely 1.8 + PyGEOS 0.12 + GeoPandas 0.10. It took some effort, but I got it working. Will MEOS be anything like that? I could try out MEOS if you need test customers.<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
I have some ideas about how to calculate the intersections of tgeompoints with "temporal polygons" (!), that is, a polygon with a Period, and would like your opinion & advice.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Air traffic controllers vector aircraft away from their planned routes for various reasons. If the original flight plan would have taken the flight through bad weather, then the controller
<i>had </i>to vector the aircraft (that is, the vectoring/maneuvering away from the planned route wasn't because of traffic congestion).</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
I get raster weather radar data about storms every 15 minutes, and using GDAL's Polygonize(), convert radar levels above a threshold (30 dBz) into polygons. I store those into PostGIS with a Period of "[now, next interval)".</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Currently I make linestrings of the planned flight path and of the flown flight route through a particular airspace. If they're about the same, then there is no issue. If the flown flight path is much longer than the planned flight path, then the air traffic
controller had to "work the aircraft", and it would be nice to know why that was.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Here's my idea: make tgeompoint arrays of the planned flight path and somehow temporally intersect that with the various radar polygons over the course of the flight. The flight may span several 15-minute intervals including several weather polygons, so I
may have to union together all intersections to eliminate overlaps that would end up duplicating intersections. The distance (or time) of the intersections would indicate the about of weather that the flight
<i>would have encountered</i> if it had remained on its original planned flight path.</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
That way, when the airline asks "why was my aircraft late?", or the controller's supervisor asks "what were you doing all day?", the controller could answer "let me show you the scores calculated by Wendell's MobilityDB project."<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Thank you,</div>
<div style="font-family:Calibri,Arial,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
Wendell<br>
</div>
<div id="gmail-m_-8540516697786452526appendonsend"></div>
<hr style="display:inline-block;width:98%">
<div id="gmail-m_-8540516697786452526divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Esteban Zimanyi <<a href="mailto:estebanzimanyi@gmail.com" target="_blank">estebanzimanyi@gmail.com</a>><br>
<b>Sent:</b> Thursday, June 9, 2022 10:46 AM<br>
<b>To:</b> Wendell Turner <<a href="mailto:WTurner@cssiinc.com" target="_blank">WTurner@cssiinc.com</a>><br>
<b>Cc:</b> SCHOEMANS Maxime <<a href="mailto:Maxime.Schoemans@ulb.be" target="_blank">Maxime.Schoemans@ulb.be</a>>; SAKR Mahmoud <<a href="mailto:mahmoud.sakr@ulb.be" target="_blank">mahmoud.sakr@ulb.be</a>>; Vicky Vergara <<a href="mailto:vicky@georepublic.de" target="_blank">vicky@georepublic.de</a>>; Regina Obe <<a href="mailto:lr@pcorp.us" target="_blank">lr@pcorp.us</a>><br>
<b>Subject:</b> [EXTERNAL] PostgreSQL Version Support in MobilityDB</font>
<div> </div>
</div>
<div>
<div dir="ltr">Dear Wendell
<div><br>
</div>
<div>I hope you are well. I wanted to ask you a quick question. </div>
<div><br>
</div>
<div>As you know, we are working on building a C library called MEOS (Mobility Engine Open Source) that has a similar API as MobilityDB but does not have any PostgreSQL dependency so it can be used in any programming language, much as the GEOS library.</div>
<div><br>
</div>
<div>However, the MEOS library code (actually an excerpt of the MobilityDB code base) should also work when building MobilityDB and must support multiple PostgreSQL versions. We are having problems supporting this with PostgreSQL version 11.</div>
<div><br>
</div>
<div>Would it be reasonable to require at least version 12 for MobilityDB ?</div>
<div><br>
</div>
<div>Thanks for your feedback.</div>
<div><br>
</div>
<div>Esteban</div>
<div><br clear="all">
<div>
<div dir="ltr">
<div dir="ltr">
<div>------------------------------------------------------------<br>
Prof. Esteban Zimanyi<br>
Department of Computer & Decision Engineering (CoDE) CP 165/15 <br>
Universite Libre de Bruxelles <br>
Avenue F. D. Roosevelt 50 <br>
B-1050 Brussels, Belgium <br>
fax: + 32.2.650.47.13<br>
tel: + 32.2.650.31.85<br>
e-mail: <a href="mailto:esteban.zimanyi@ulb.be" target="_blank">esteban.zimanyi@ulb.be</a><br>
Internet: <a href="http://cs.ulb.ac.be/members/esteban/" target="_blank">http://cs.ulb.ac.be/members/esteban/</a><br>
------------------------------------------------------------</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><pre>Georepublic UG (haftungsbeschränkt)
Salzmannstraße 44,
81739 München, Germany
Vicky Vergara
Operations Research
eMail: vicky@<a href="http://georepublic.de" target="_blank">georepublic.de</a>
Web: <a href="https://georepublic.info" target="_blank">https://georepublic.info</a>
Tel: +49 (089) 4161 7698-1
Fax: +49 (089) 4161 7698-9
Commercial register: Amtsgericht München, HRB 181428
CEO: Daniel Kastl
<span></span></pre></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>