[Mobilitydb-dev] [EXTERNAL] PostgreSQL Version Support in MobilityDB

[Vicky Vergara]

Hello Wendell.

For you to know, we are all on this mailing list:
https://lists.osgeo.org/mailman/listinfo/mobilitydb-dev

To make the communication easier in the future, can you please register to
that mailing list.
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)

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.

Thanks for your comprehension.
Vicky


On Mon, Jun 13, 2022 at 8:40 AM Wendell Turner <WTurner at cssiinc.com> wrote:

> Hello Esteban,
>
> 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.
>
> 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.
>
> 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.
>
> 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 *had *to vector the aircraft
> (that is, the vectoring/maneuvering away from the planned route wasn't
> because of traffic congestion).
>
> 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)".
>
> 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.
>
> 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 *would have encountered* if it had
> remained on its original planned flight path.
>
> 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."
>
> Thank you,
> Wendell
> ------------------------------
> *From:* Esteban Zimanyi <estebanzimanyi at gmail.com>
> *Sent:* Thursday, June 9, 2022 10:46 AM
> *To:* Wendell Turner <WTurner at cssiinc.com>
> *Cc:* SCHOEMANS Maxime <Maxime.Schoemans at ulb.be>; SAKR Mahmoud <
> mahmoud.sakr at ulb.be>; Vicky Vergara <vicky at georepublic.de>; Regina Obe <
> lr at pcorp.us>
> *Subject:* [EXTERNAL] PostgreSQL Version Support in MobilityDB
>
> Dear Wendell
>
> I hope you are well. I wanted to ask you a quick question.
>
> 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.
>
> 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.
>
> Would it be reasonable to require at least version 12 for MobilityDB ?
>
> Thanks for your feedback.
>
> Esteban
>
> ------------------------------------------------------------
> Prof. Esteban Zimanyi
> Department of Computer & Decision Engineering  (CoDE) CP 165/15
> Universite Libre de Bruxelles
> Avenue F. D. Roosevelt 50
> B-1050 Brussels, Belgium
> fax: + 32.2.650.47.13
> tel: + 32.2.650.31.85
> e-mail: esteban.zimanyi at ulb.be
> Internet: http://cs.ulb.ac.be/members/esteban/
> ------------------------------------------------------------
>


-- 

Georepublic UG (haftungsbeschränkt)
Salzmannstraße 44,
81739 München, Germany

Vicky Vergara
Operations Research

eMail: vicky at georepublic.de
Web: https://georepublic.info

Tel: +49 (089) 4161 7698-1
Fax: +49 (089) 4161 7698-9

Commercial register: Amtsgericht München, HRB 181428
CEO: Daniel Kastl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mobilitydb-dev/attachments/20220613/f4dc49f1/attachment.htm>