[Xastir] [Xastir-dev] ATTENTION: Preparing for next release: Please thrash on the code

Fri May 31 14:18:50 PDT 2019

That makes sense. And I was an early proponent of sticking to
WGS84/NAD83... I didn't want to accept NAD27 because of the historical
cruft introduced by a number of congressional mandates, but, I digress. At
one point, when DAFIF was available, that gave us access to WGS84 lat/lon
(CED)  as well as other coordinate systems. DAFIF is the basis for the FAA
sectionals, and its free distribution was stopped supposedly because it had
international data some countries considered proprietary; YMMV on that
argument.

I'll start reviewing datums and projections; that skill has atrophied as I
took on more Cray HPC and user wrangling. I need to get back to something
fun!

gerry

On Fri, May 31, 2019 at 4:11 PM km5vy Tom Russo <russo at bogodyn.org> wrote:

> On Fri, May 31, 2019 at 04:05:19PM -0500, we recorded a bogon-computron
> collision of the <gerry.creager at noaa.gov> flavor, containing:
> > Tom
> >
> > Thanks for the expansion. Let me wrap my head around the current work
> > environment, and I'll see if I can get some coding time at home at
> night...
> >
> > As for the "less accurate Molodensky" transform... I recall writing those
> > in F77 and F90 from scratch a long time ago. I went with Molodensky
> because
> > it was simpler, and "good enough" for most of the geodesy I was doing at
> > the time! I don't see how it's too bad for ham radio apps. A couple of cm
> > error, even a meter or so, won't make much difference in most of what we
> do!
>
> It isn't "too bad."  It's more likely "plenty good enough for APRS work."
> But it is indeed less accurate than using NADCON datum shift grids as
> PROJ.4
> does.  At the moment, Xastir only knows about WGS84 lat/lon (native
> APRS datum and coordinate system), WGS84/NAD83 UTM, and NAD27 UTM in
> normal
> operation.  Where it starts to be a problem is when folks try to use our
> geotiff code for geotiffs created by agencies other than USGS (even in
> North
> America --- for example, FAA sectional charts in GeoTIFF format, which are
> often in Lambert Conformal Conic).
>
> Using gdal's raster warping capability (which relies on Proj) to handle
> rasters in other datums and coordinate systems would be a Good Thing, but
> at the moment it can only be done as a preprocessing step before telling
> Xastir about the images (using GDAL command line tools).
>
> > On Fri, May 31, 2019 at 2:43 PM km5vy Tom Russo <russo at bogodyn.org>
> wrote:
> >
> > > On Fri, May 31, 2019 at 02:29:36PM -0500, we recorded a bogon-computron
> > > collision of the <gerry.creager at noaa.gov> flavor, containing:
> > > > So, a question. I've been lurking, but this working thing has gotten
> in
> > > the
> > > > way of my ham and Xastir time.
> > > >
> > > > With gdal and proj support deprecated,
> > >
> > > Just a quick correction:  these are not "deprecated" (i.e. unsupported,
> > > with
> > > users encouraged not to use them), they're removed.
> > >
> > > GDAL support in Xastir was almost non-existent.  A few OGR vector data
> > > types were supported with hard-coded rendering rules, but the full
> > > flexibility
> > > of OGR vector types with the sort of user-defined rendering control
> that
> > > we
> > > have for shapefiles was never implemented.
> > >
> > > Support for GDAL raster types was basically never done.
> > >
> > > So what we've actually removed was half-written, mostly unused code
> that
> > > did nobody any good.
> > >
> > > PROJ support in Xastir was never real.  We only needed proj because
> > > libgeotiff
> > > needed it, and since we didn't get rid of libgeotiff support, we still
> do
> > > require linking of proj libraries.  The only direct use in Xastir of
> proj
> > > libraries was in a couple of functions that existed solely because
> > > libgeotiff
> > > and gdal provided identical functions, and therefore frequently caused
> > > linking
> > > or other runtime failure.  So a single function of libgeotiff was cut
> and
> > > pasted into Xastir source code and renamed to eliminate the conflict,
> and
> > > that
> > > one function used proj directly.  Since we no longer link in gdal, the
> > > conflict is no longer an issue so that cut/paste hack and direct use of
> > > proj
> > > is gone.
> > >
> > > Datum translation in Xastir is done via the less accurate Molodensky
> > > transformations that are coded in datum.c and datum.h.  We have never
> used
> > > proj for datum or coordinate system transformation directly.
> > >
> > > > any thought of incorporating some of
> > > > the Python (3) approaches to proj and gdal, and incorporating
> cartopy? I
> > > > realize the code is not python, and it could incorporate problems by
> > > trying
> > > > to shoe-horn it in. This is a request for information...
> > >
> > > > I'm thinking, though, that this could be a good way to snag WMS/WFS
> data,
> > > > create static maps for future use, etc. Things that might be
> offloaded.
> > >
> > > Honestly, if someone wanted to expend the effort to incorporate
> gdal/ogr
> > > and
> > > proj usage into Xastir in a good, useful way, I would welcome it ---
> > > done right, gdal and ogr can bring a lot of good support into Xastir.
> But
> > > I am
> > > not sure who will do that, and I am sure that the old code wasn't
> where we
> > > needed to start to get that done.
> > >
> > > If you want to implement such a thing and make a pull request, have at
> it.
> > >
> > > > Thanks. I'll go back in my cave now.
> > > >
> > > > AND, Congratulations on the new release!
> > > > gerry
> > > >
> > > > On Thu, May 30, 2019 at 12:38 PM Curt Mills <curt.we7u at gmail.com>
> wrote:
> > > >
> > > > > Rgr. Will post announcement today then.
> > > > >
> > > > > On Thu, May 30, 2019 at 10:33 AM km5vy Tom Russo <
> russo at bogodyn.org>
> > > > > wrote:
> > > > >
> > > > > > On Thu, May 30, 2019 at 11:12:03AM -0600, we recorded a
> > > bogon-computron
> > > > > > collision of the <russo at bogodyn.org> flavor, containing:
> > > > > > > On Mon, May 27, 2019 at 11:52:53AM -0700, we recorded a
> > > bogon-computron
> > > > > > collision of the <curt.we7u at gmail.com> flavor, containing:
> > > > > > > > Fine by me. I can do all the announcements.
> > > > > > >
> > > > > > > It is likely that I'll go ahead and walk through the git steps
> of
> > > doing
> > > > > > > the release tonight instead of tomorrow.
> > > > > >
> > > > > > Or now.
> > > > > >
> > > > > > It is done.
> > > > > >
> > > > > > https://github.com/Xastir/Xastir/releases/tag/Release-2.1.2
> > > > > >
> > > > > > > My "friday off" turns out to be a
> > > > > > > day of household chores.
> > > > > > >
> > > > > > > Actually stepping through the release process is only a few
> > > minutes,
> > > > > and
> > > > > > the
> > > > > > > longest steps are those that verify that the easy steps were
> done
> > > > > > correctly.
> > > > > > >
> > > > > > > I'll shoot a message to the lists when it's done, and then the
> > > proper
> > > > > > announcing
> > > > > > > can happen.
> > > > > > >
> > > > > > > > On Mon, May 27, 2019, 10:07 AM Tom Russo <russo at bogodyn.org>
> > > wrote:
> > > > > > > >
> > > > > > > > > On Thu, May 23, 2019 at 01:05:53PM -0600, we recorded a
> > > > > > bogon-computron
> > > > > > > > > collision of the <russo at bogodyn.org> flavor, containing:
> > > > > > > > > > On Thu, May 23, 2019 at 07:15:52AM -0700, we recorded a
> > > > > > bogon-computron
> > > > > > > > > collision of the <curt.we7u at gmail.com> flavor, containing:
> > > > > > > > > > > Anyone else have any reports, good or bad?
> > > > > > > > > > >
> > > > > > > > > > > FWIW: For the types of things I do the latest code has
> been
> > > > > > stable for
> > > > > > > > > me.
> > > > > > > > > > >
> > > > > > > > > > > We're getting close to a release and Tom will most
> likely
> > > be
> > > > > the
> > > > > > one
> > > > > > > > > doing
> > > > > > > > > > > it. No target date has been mentioned. If we run into
> any
> > > nasty
> > > > > > bugs
> > > > > > > > > that
> > > > > > > > > > > might delay.
> > > > > > > > > >
> > > > > > > > > > Let's set a date right now.  I can set aside the time to
> do
> > > the
> > > > > > release
> > > > > > > > > > on only a few days in the upcoming weeks (it doesn't take
> > > long,
> > > > > > but it's
> > > > > > > > > > a process that takes some attention, and is documented in
> > > > > > > > > README.developers.md).
> > > > > > > > > >
> > > > > > > > > > The days I could do it are:
> > > > > > > > > >   Friday, 31 May
> > > > > > > > > >   Friday, 14 June
> > > > > > > > > >   Sometime on the weekend of 21-23 June.
> > > > > > > > >
> > > > > > > > > Can we pick one?  I propose we just rip off the band-aid
> and
> > > do it
> > > > > > > > > Friday 31 May.  I can take care of the git work if you'll
> > > handle
> > > > > > doing all
> > > > > > > > > the various announcements.
> > > > > > > > >
> > > > > > > > > > I think that we are already at a point where there has
> been
> > > > > > sufficient
> > > > > > > > > time
> > > > > > > > > > to shake out the code on master, and we could release
> today
> > > if we
> > > > > > wanted
> > > > > > > > > > to.  Next friday is the earliest I have the opportunity
> to
> > > spend
> > > > > > on it.
> > > > > > > > > >
> > > > > > > > > > If someone else wanted to try out the release process,
> it's
> > > all
> > > > > > > > > documented
> > > > > > > > > > in gory detail in README.developers.md, and if followed
> > > > > precisely
> > > > > > would
> > > > > > > > > > produce a new release that would be ready (down to file
> > > names of
> > > > > > > > > tarballs)
> > > > > > > > > > to slot into the package creation processes various
> distros
> > > use,
> > > > > > just by
> > > > > > > > > > changing the version number.  Or pick a date and I'll do
> it
> > > then.
> > > > > > > > > >
> > > > > > > > > > > On Fri, May 17, 2019 at 6:16 PM Lee Bengston <
> > > > > > lee.bengston at gmail.com>
> > > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > I've played with it some and and have not found any
> > > issues. I
> > > > > > put
> > > > > > > > > together
> > > > > > > > > > > > a BPQ packet node in January, and I haven't fully
> > > back-filled
> > > > > > what I
> > > > > > > > > had
> > > > > > > > > > > > "stolen" from aprs, so testing capability is fairly
> > > limited.
> > > > > > From
> > > > > > > > > what I
> > > > > > > > > > > > can tell, though, it's nice and stable.
> > > > > > > > > > > >
> > > > > > > > > > > > I do have a few questions about the source ( yeah,
> > > always one
> > > > > > in the
> > > > > > > > > crowd
> > > > > > > > > > > > :-) )
> > > > > > > > > > > >
> > > > > > > > > > > > - In dlm.c noticed references to "curl-multi" and
> > > evidently
> > > > > the
> > > > > > > > > capability
> > > > > > > > > > > > to leverage parallel downloading of map tiles as
> > > supported by
> > > > > > > > > libcurl. Is
> > > > > > > > > > > > whether or not that is supported in our platform
> based on
> > > > > what
> > > > > > > > > version of
> > > > > > > > > > > > curl is installed?
> > > > > > > > > > > >
> > > > > > > > > > > > - now that dlm.c handles downloading tiles, is there
> > > anything
> > > > > > left in
> > > > > > > > > > > > tile_mgmnt.c that is still needed or could
> tile_mgmnt.h
> > > and
> > > > > > > > > tile_mgmnt.c be
> > > > > > > > > > > > removed?  It seems at a minimum the "getOneTile"
> portion
> > > of
> > > > > > > > > tile_mgmnt.c is
> > > > > > > > > > > > no longer needed.
> > > > > > > > > > > >
> > > > > > > > > > > > Looks like you guys are doing a lot of cleanup in
> this
> > > > > > release, so
> > > > > > > > > brought
> > > > > > > > > > > > that up just in case there's some stuff there that
> could
> > > be
> > > > > > > > > streamlined a
> > > > > > > > > > > > bit.
> > > > > > > > > > > >
> > > > > > > > > > > > Fyi, my Odroid XU4 (arm based) beats the pants off my
> > > Intel
> > > > > > Celeron
> > > > > > > > > based
> > > > > > > > > > > > laptop in terms of map download speed.  Both are on
> > > Ubuntu
> > > > > > 18.04
> > > > > > > > > with the
> > > > > > > > > > > > MATE desktop. Am wondering if the fact that the XU4
> has
> > > an
> > > > > > octa-core
> > > > > > > > > cpu
> > > > > > > > > > > > makes a difference with respect to curl-multi.
> > > > > > > > > > > >
> > > > > > > > > > > > The cleaner compiling is very noticeable, and the
> earlier
> > > > > note
> > > > > > about
> > > > > > > > > newer
> > > > > > > > > > > > compilers spitting out more warnings matches what I
> saw.
> > > > > > Compiling
> > > > > > > > > is
> > > > > > > > > > > > cleaner in Debian Stretch and Ubuntu 16.04 than it
> is in
> > > > > Ubuntu
> > > > > > > > > 18.04, but
> > > > > > > > > > > > it still builds fine.  (And even in Ubuntu 18.04 the
> new
> > > code
> > > > > > still
> > > > > > > > > > > > compiles a lot cleaner that the older code did)
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks,
> > > > > > > > > > > >
> > > > > > > > > > > > Lee
> > > > > > > > > > > > K5DAT
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > On Thu, May 9, 2019 at 9:57 AM Curt Mills <
> > > > > curt.we7u at gmail.com
> > > > > > >
> > > > > > > > > wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > We're planning to do a release within a few weeks.
> It
> > > might
> > > > > > be as
> > > > > > > > > few as
> > > > > > > > > > > > 2
> > > > > > > > > > > > > weeks.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Please check out / compile / thrash on the latest
> > > Github
> > > > > > Xastir
> > > > > > > > > code.
> > > > > > > > > > > > Find
> > > > > > > > > > > > > anything that broke with our latest code fixes.
> > > Exercise
> > > > > all
> > > > > > types
> > > > > > > > > of
> > > > > > > > > > > > > interfaces, messaging, bulletins, weather stations,
> > > > > tracking,
> > > > > > > > > following
> > > > > > > > > > > > > stations, maps, etc. Anything you can think of.
> > > > > > > > > > > > >
> > > > > > > > > > > > > The latest code compiles much cleaner and a lot of
> > > fixes
> > > > > > went in
> > > > > > > > > to make
> > > > > > > > > > > > > that possible. We'd like this release to function
> > > well, so
> > > > > > > > > whatever you
> > > > > > > > > > > > can
> > > > > > > > > > > > > do to exercise the code would be most appreciated.
> > > > > > > > > > > > >
> > > > > > > > > > > > > If you find a bug or odd operation, report it here:
> > > > > > > > > > > > >
> > > > > > > > > > > > >   https://github.com/Xastir/Xastir/issues
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks!
> > > > > > > > > > > > >
> > > > > > > > > > > > > --
> > > > > > > > > > > > > Curt, WE7U        http://we7u.wetnet.net
> > > > > > > > > > > > > http://www.sarguydigital.com
> > > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > > Xastir mailing list
> > > > > > > > > > > > > Xastir at lists.xastir.org
> > > > > > > > > > > > > http://xastir.org/mailman/listinfo/xastir
> > > > > > > > > > > > >
> > > > > > > > > > > > _______________________________________________
> > > > > > > > > > > > Xastir mailing list
> > > > > > > > > > > > Xastir at lists.xastir.org
> > > > > > > > > > > > http://xastir.org/mailman/listinfo/xastir
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > Curt, WE7U        http://we7u.wetnet.net
> > > > > > > > > http://www.sarguydigital.com
> > > > > > > > > > > _______________________________________________
> > > > > > > > > > > Xastir mailing list
> > > > > > > > > > > Xastir at lists.xastir.org
> > > > > > > > > > > http://xastir.org/mailman/listinfo/xastir
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Tom Russo    KM5VY
> > > > > > > > > > Tijeras, NM
> > > > > > > > > >
> > > > > > > > > >  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr
> > > > > [a-m][n-z]
> > > > > > > > > [n-z][a-m]
> > > > > > > > > >
> > > > > > > > > > _______________________________________________
> > > > > > > > > > Xastir-dev mailing list
> > > > > > > > > > Xastir-dev at lists.xastir.org
> > > > > > > > > > http://xastir.org/mailman/listinfo/xastir-dev
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Tom Russo    KM5VY
> > > > > > > > > Tijeras, NM
> > > > > > > > >
> > > > > > > > >  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr
> > > [a-m][n-z]
> > > > > > > > > [n-z][a-m]
> > > > > > > > >
> > > > > > > > > _______________________________________________
> > > > > > > > > Xastir mailing list
> > > > > > > > > Xastir at lists.xastir.org
> > > > > > > > > http://xastir.org/mailman/listinfo/xastir
> > > > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Tom Russo    KM5VY
> > > > > > > Tijeras, NM
> > > > > > >
> > > > > > >  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr
> [a-m][n-z]
> > > > > > [n-z][a-m]
> > > > > >
> > > > > > --
> > > > > > Tom Russo    KM5VY
> > > > > > Tijeras, NM
> > > > > >
> > > > > >  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr
> [a-m][n-z]
> > > > > > [n-z][a-m]
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Curt, WE7U        http://we7u.wetnet.net
> > > > > http://www.sarguydigital.com
> > > > > _______________________________________________
> > > > > Xastir-dev mailing list
> > > > > Xastir-dev at lists.xastir.org
> > > > > http://xastir.org/mailman/listinfo/xastir-dev
> > > > >
> > > >
> > > >
> > > > --
> > > > Gerry Creager
> > > > NSSL/CIMMS
> > > > 405.325.6371
> > > > ++++++++++++++++++++++
> > > > *The way to get started is to quit talking and begin doing.*
> > > > *   Walt Disney*
> > >
> > > --
> > > Tom Russo    KM5VY
> > > Tijeras, NM
> > >
> > >  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z]
> > > [n-z][a-m]
> > >
> > >
> >
> > --
> > Gerry Creager
> > NSSL/CIMMS
> > 405.325.6371
> > ++++++++++++++++++++++
> > *The way to get started is to quit talking and begin doing.*
> > *   Walt Disney*
>
> --
> Tom Russo    KM5VY
> Tijeras, NM
>
>  echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z]
> [n-z][a-m]
>
>

-- 
Gerry Creager
NSSL/CIMMS
405.325.6371
++++++++++++++++++++++
*The way to get started is to quit talking and begin doing.*
*   Walt Disney*