Re: [Xastir] Quirks compiling Xastir on Centos6

2012-05-19 Thread Curt, WE7U

On Sat, 19 May 2012, David A. Ranch wrote:

Yeah.. I haven't tried GM yet but the older version of IM seems to be working 
well.  Is GM really that much faster, better, etc. than IM?


It's a fork of the IM code, so it is very similar, but seems to dot all the i's 
and cross the t's better than IM does for releases.  A bit more stable.


Ok.. I'll give it a look but I take it that not many people use this feature 
of Xastir?  Too bad Xastir can't just store this information in a flat file 
and reload it upon restart.


It would be a lot of file access keeping it up-to-date.  No, most people don't 
know about this feature and don't use it.  I think it was in alpha stage last I 
recall.


Yup.. I'll try that out.  Jerry, KA6HLD also turned me only some MapQuest 
servers that offer tiled satellite images!  I'm going to try that one as well 
and if I can get it to work, I'll see if I can upload the .geo to CVS.  I 
think that would be a slick addition to Xastir.. that and maybe a merged 
image + map view like how Google does it.


You can't upload via CVS unless you're listed as one of the developers on 
SourceForge.  You can submit it to a developer and have them bless it and 
commit it to CVS though.  Generally Tom Russo or myself are the best options 
for that.


No.. not hard unless you want to do everything in RPMs (even the Perl 
modules).  I've done all of that and there are also differences between 
Centos5 and Centos6 that I've captured in my doc.


Roger.  I've done RPM's for OpenSuSE before, and in fact have a spec file and 
scripts I use to generate those.  Haven't done that in a while though.

--
Curt, WE7U.http://www.eskimo.com/~archer
U.S. Weather Alerts:  Firenet.us, port 14580, filter "t/n e/WE7U-WX"
___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Quirks compiling Xastir on Centos6

2012-05-19 Thread David A. Ranch


Hello Curt,

It could be a bad package for IM, or it could be an IM package that 
had some compile-time parameters set that aren't compatible with Xastir.
For those kinds of cases I just install GM.  If problems with GM, I 
try IM.


Yeah.. I haven't tried GM yet but the older version of IM seems to be 
working well.  Is GM really that much faster, better, etc. than IM?





Reloading previous data (maybe with a faster decay algorithm) is 
something I was looking for.  Does anyone else on the list know if 
this code (say with the MySQL backend) is working?  Is there 
documentation on how to configure Xastir to use the proper DB, 
credentials, etc?


You'd have to do searches back through the Xastir or Xastir-Dev 
mailing lists to find out.  I think you should be able to figure it 
out from that and perhaps from looking at comments in the source code.


Ok.. I'll give it a look but I take it that not many people use this 
feature of Xastir?  Too bad Xastir can't just store this information in 
a flat file and reload it upon restart.





Just look at one of the current .geo files to see the format.  It 
should be easy to copy it to a newly-named file, tweak it a bit, then 
test.  The file will have to be down in the 
/usr/local/share/xastir/Maps/ directory tree somewhere, and indexed so 
that Xastir knows the .geo file is there.


Yup.. I'll try that out.  Jerry, KA6HLD also turned me only some 
MapQuest servers that offer tiled satellite images!  I'm going to try 
that one as well and if I can get it to work, I'll see if I can upload 
the .geo to CVS.  I think that would be a slick addition to Xastir.. 
that and maybe a merged image + map view like how Google does it.







  
http://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#21.xastir-compile


I'm using CentOS quite a bit at work but I haven't done a test compile 
of Xastir on any of the servers recently.  I don't remember having to 
do all that much earlier to get Xastir running on CentOS though.


No.. not hard unless you want to do everything in RPMs (even the Perl 
modules).  I've done all of that and there are also differences between 
Centos5 and Centos6 that I've captured in my doc.


--David
___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Quirks compiling Xastir on Centos6

2012-05-18 Thread Curt, WE7U

On Wed, 16 May 2012, David A. Ranch wrote:

ImageMagick-6.5.4.  Once I installed that, the Oosm_tiled_mapnik map came 
right up!  Woohoo!  I'll troubleshoot this tonight to see if it's something 
specific to that one ImageMagick RPM or see if it's something directly in the 
newer ImageMagick code but since there weren't any errors showing up, I don't 
know where I should even start..   If this is an issue in the new ImageMagick 
code, seems like this needs to be investigated and fixed.


Can anyone give me some pointers on how to troubleshoot this silent issue?


It could be a bad package for IM, or it could be an IM package that had some 
compile-time parameters set that aren't compatible with Xastir.

For those kinds of cases I just install GM.  If problems with GM, I try IM.


Reloading previous data (maybe with a faster decay algorithm) is something I 
was looking for.  Does anyone else on the list know if this code (say with 
the MySQL backend) is working?  Is there documentation on how to configure 
Xastir to use the proper DB, credentials, etc?


You'd have to do searches back through the Xastir or Xastir-Dev mailing lists 
to find out.  I think you should be able to figure it out from that and perhaps 
from looking at comments in the source code.


As a test, I did installed GraphicsMagick and recompile Xastir but the 
./configure script wasn't selecting GraphicsMagick as it's default.  Even 
when I used --without-ImageMagick, Xastir's configure set the system to "No 
ImageMagick / GraphicsMagick".  Maybe I need another CPPFLAGS section to find 
it.  I'll try that out tonight.


You need both the GM and the GM-dev package (header files) for Xastir to pick 
it up.  You may also need to specify some options to configure if it's not 
looking in the correct directories where you installed it.



  http://wiki.openstreetmap.org/wiki/TopOSM


Try creating a .geo file for it and test.


Ok, I'll have to look through the email archives, etc. to see if this is 
documented.  I have no clue how to do it.  Any pointers?


Just look at one of the current .geo files to see the format.  It should be 
easy to copy it to a newly-named file, tweak it a bit, then test.  The file 
will have to be down in the /usr/local/share/xastir/Maps/ directory tree 
somewhere, and indexed so that Xastir knows the .geo file is there.


PS.  I updated my huge Centos / Hamshack documentation set to reflect this 
new Xastir setup with Centos6 which might help other Linux users compile up 
their own version of Xastir.  It's fairly complicated but it's all done 
properly via RPMs.   I also made the xastir.spec file available (would be 
nice if it could be put into the official Xastir sources) for other RPM 
users.  I'd be more than happy to upload the Centos6 binaries if anyone would 
find them useful as well.



  
http://www.trinityos.com/HAM/CentosDigitalModes/hampacketizing-centos.html#21.xastir-compile


I'm using CentOS quite a bit at work but I haven't done a test compile of 
Xastir on any of the servers recently.  I don't remember having to do all that 
much earlier to get Xastir running on CentOS though.

--
Curt, WE7U.http://www.eskimo.com/~archer
APRS in Search and Rescue:  http://wetnet.net/~we7u/search_and_rescue.html
___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Quirks compiling Xastir on Centos6

2012-05-16 Thread David A. Ranch


Howdy Everyone,

Success!  See below..




There are a lot of other options available in the help for configure 
but I don't know if those options are being enabled by default or not


 - Is GraphicsMagick recommended over ImageMagick?


Generally yes, unless IM works better on your system.  Usually GM 
works better and is more stable long-term.


As a test, I uninstalled the 64bit ImageMagick v6.7.6 RPM I downloaded 
directly from the ImageMagick website  and went for the older Centos 
provided ImageMagick-6.5.4.  Once I installed that, the 
Oosm_tiled_mapnik map came right up!  Woohoo!  I'll troubleshoot this 
tonight to see if it's something specific to that one ImageMagick RPM or 
see if it's something directly in the newer ImageMagick code but since 
there weren't any errors showing up, I don't know where I should even 
start..   If this is an issue in the new ImageMagick code, seems like 
this needs to be investigated and fixed.


Can anyone give me some pointers on how to troubleshoot this silent issue?



  --with-postgisEnable Postgresql with PostGIS 
<--- Is it a good idea to enable the database 
functionality (postgres or MySQL)?
 --with-mysql  Enable MySQL, with spatial support if 
available.

 --with-bdb-libdir=DIR Berkeley DB lib files are in DIR
 --with-bdb-incdir=DIR Berkeley DB include files are in DIR


I'd leave the postgres/mysql options alone.  As I recall that was some 
experimental code that hasn't been fully fleshed out yet.  I may be 
wrong though.  I think it was intended to flush the current station 
info out to the database so that when you restarted it pulled the old 
data back in to the map.


Reloading previous data (maybe with a faster decay algorithm) is 
something I was looking for.  Does anyone else on the list know if this 
code (say with the MySQL backend) is working?  Is there documentation on 
how to configure Xastir to use the proper DB, credentials, etc?




I also noticed that "Davis WX" is not enabled by default (it's also 
not in the same section with all the other features)


I would only enable that in the case where someone was actually using 
a Davis WX station.  Same for LaCrosse.  Most people don't have such 
equipment and/or don't set up all the other stuff needed to use them 
with Xastir.


Fair enough though I'd argue that it's placement in the ./configure 
--help section should be lower to be put with the other options.  Very 
minor complaint for sure.





  *** Done with WX Alert log files
TBD: I don't think we can deal with colorspace != RGBTBD: I don't 
think we can deal with colorspace != RGBTBD: I don't think we can 
deal with colorspace != RGBTBD: I don't think we can deal with 
colorspace != RGB


I'm not seeing that TBD message here.  Perhaps you're running your 
screen in 8-bit or 24-bit mode?  Try 16 or 32-bit mode instead.  There 
aren't enough bits in 8-bit to make nice maps, although I used to run 
it this way on Solaris years ago.  I seem to remember there may be 
some issues with 24-bit screens as well.


Lovely KDE4 doesn't say anything about bitdepth but X.org.0.log shows:
--
[450476.461] (**) intel(0): Depth 24, (--) framebuffer bpp 32 
<-

[450476.461] (==) intel(0): RGB weight 888
[450476.461] (==) intel(0): Default visual is TrueColor
[450476.461] (II) intel(0): Integrated Graphics Chipset: Intel(R) 
Sandybridge Mobile (GT2)

--

Since the problem seems to have been ImageMagick, it seems Xastir works 
fine with this color depth.







You can try removing the imagemagick-devel package and installing 
graphicsmagick and graphicsmagick-devel, then configure;make;make 
install to see if it works better for you.  If both are installed, 
Xastir will choose GM over IM.



The only other things I can think of is that I'm running a very new 
version of ImageMagick-6.7.6.  Maybe something there?


As a test, I did installed GraphicsMagick and recompile Xastir but the 
./configure script wasn't selecting GraphicsMagick as it's default.  
Even when I used --without-ImageMagick, Xastir's configure set the 
system to "No ImageMagick / GraphicsMagick".  Maybe I need another 
CPPFLAGS section to find it.  I'll try that out tonight.



Could be that, could be a non-functional version of libcurl.  You can 
remove the libcurl-devel package and install wget, then 
configure;make;make install again to see if that fixes it.
There are still several OSM maps that aren't working either due to 
errors from libcurl or invalid headers.  I'll start a new thread on that 
topic in a bit just so this can be tracked and either fixed on the 
Xastir side or bubbled up to the OSM folk.







  http://wiki.openstreetmap.org/wiki/TopOSM


Try creating a .geo file for it and test.


Ok, I'll have to look through the email archives, etc. to see if this is 
documented.  I have no clue how to do it.  Any pointers?



Anyway.. thank you so much Curt for your help and patience to get me 
running

Re: [Xastir] Quirks compiling Xastir on Centos6

2012-05-16 Thread Tom Russo
On Wed, May 16, 2012 at 04:31:54AM -0700, we recorded a bogon-computron 
collision of the  flavor, containing:
> > TBD: I don't think we can deal with colorspace != RGBTBD: I don't think we 
> > can deal with colorspace != RGBTBD: I don't think we can deal with 
> > colorspace 
> > != RGBTBD: I don't think we can deal with colorspace != RGB
> 
> I'm not seeing that TBD message here.  Perhaps you're running your screen in 
> 8-bit or 24-bit mode?  Try 16 or 32-bit mode instead.  There aren't enough 
> bits in 8-bit to make nice maps, although I used to run it this way on 
> Solaris years ago.  I seem to remember there may be some issues with 24-bit 
> screens as well.

I have been running with 24-bit for years.  There's nothing wrong with
24-bit support.

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick

___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Quirks compiling Xastir on Centos6

2012-05-16 Thread Curt, WE7U

On Tue, 15 May 2012, David A. Ranch wrote:


./configure CPPFLAGS="-I/usr/include/libgeotiff"


Here's the "configure.suse" script that I use:

--
#!/bin/sh
./configure CPPFLAGS="-I/usr/include/libgeotiff"
--


There are a lot of other options available in the help for configure but I 
don't know if those options are being enabled by default or not


 - Is GraphicsMagick recommended over ImageMagick?


Generally yes, unless IM works better on your system.  Usually GM works better 
and is more stable long-term.



 --with-motif-libs :: are these on by default?


Yes.  Without them the GUI doesn't work.


  --with-postgisEnable Postgresql with PostGIS 
<--- Is it a good idea to enable the database functionality 
(postgres or MySQL)?

 --with-mysql  Enable MySQL, with spatial support if available.
 --with-bdb-libdir=DIR Berkeley DB lib files are in DIR
 --with-bdb-incdir=DIR Berkeley DB include files are in DIR


I'd leave the postgres/mysql options alone.  As I recall that was some 
experimental code that hasn't been fully fleshed out yet.  I may be wrong 
though.  I think it was intended to flush the current station info out to the 
database so that when you restarted it pulled the old data back in to the map.

Berkeley DB options:  You should only need those if Xastir isn't finding the 
libs or include files for it.


I also noticed that "Davis WX" is not enabled by default (it's also not in 
the same section with all the other features)


I would only enable that in the case where someone was actually using a Davis 
WX station.  Same for LaCrosse.  Most people don't have such equipment and/or 
don't set up all the other stuff needed to use them with Xastir.


So after all this, and everything shows up as a "Yes" in the configure stage 
yet OSM Mapnik still doesn't work though it downloads the tiles but 
everything else works..


I'm using the OSM_tiled_mapnik.go here.  The tiled options work much 
better/faster than the earlier options where the entire map was downloaded each 
time.



*** Done with WX Alert log files
TBD: I don't think we can deal with colorspace != RGBTBD: I don't think we 
can deal with colorspace != RGBTBD: I don't think we can deal with colorspace 
!= RGBTBD: I don't think we can deal with colorspace != RGB


I'm not seeing that TBD message here.  Perhaps you're running your screen in 
8-bit or 24-bit mode?  Try 16 or 32-bit mode instead.  There aren't enough bits 
in 8-bit to make nice maps, although I used to run it this way on Solaris years 
ago.  I seem to remember there may be some issues with 24-bit screens as well.

You can try removing the imagemagick-devel package and installing 
graphicsmagick and graphicsmagick-devel, then configure;make;make install to 
see if it works better for you.  If both are installed, Xastir will choose GM 
over IM.


The only other things I can think of is that I'm running a very new version 
of ImageMagick-6.7.6.  Maybe something there?


Could be that, could be a non-functional version of libcurl.  You can remove 
the libcurl-devel package and install wget, then configure;make;make install 
again to see if that fixes it.



Hmmm.. it seems like a bad design to hardcode in names like this


They're not hard-coded, they are in the .geo files.  You can add your own .geo 
files at any time, or edit the existing ones and change where they point.  
There are a few older .geo files that trigger hard-coded URL's and methods in 
Xastir, but the OSM stuff doesn't.



  http://wiki.openstreetmap.org/wiki/TopOSM


Try creating a .geo file for it and test.

--
Curt, WE7U.http://www.eskimo.com/~archer
APRS in Search and Rescue:  http://wetnet.net/~we7u/search_and_rescue.html
___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Quirks compiling Xastir on Centos6

2012-05-16 Thread David A. Ranch


Hello Tom,




You can live without geotiff support, but if you want it you have to have
both libproj and libgeotiff (and associated development headers) installed,
and libgeotiff must be built to use libproj.
Ok, it seems that the Xastir ./configure script doesn't recognize that 
geotiff is supported by the package "libgeotiff" as named in Centos:



# rpm -qa | grep -i -e libgeotiff
libgeotiff-1.2.5-5.el6.x86_64
libgeotiff-devel-1.2.5-5.el6.x86_64


In a later email from Lee Bengston, he recommended to another HAM:

 ./configure CPPFLAGS="-I/usr/include/geotiff"


I changed it to libgeotiff and with installing a missing gdal-devel, it *ALL* 
shows yes now!

 ./configure CPPFLAGS="-I/usr/include/libgeotiff"




xastir 2.0.1 has been configured to use the following
options and external libraries:

MINIMUM OPTIONS:
  ShapeLib (Vector maps) . : yes

RECOMMENDED OPTIONS:
  GraphicsMagick/ImageMagick (Raster maps) : yes (ImageMagick)
  pcre (Shapefile customization) . : yes
  dbfawk (Shapefile customization) ... : yes
  rtree indexing (Shapefile speedups)  : yes
  map caching (Raster map speedups) .. : yes
  internet map retrieval . : yes (libcurl)

FOR THE ADVENTUROUS:
  AX25 (Linux Kernel I/O Drivers)  : yes
  libproj (USGS Topos & Aerial Photos) ... : yes
  GeoTiff (USGS Topos & Aerial Photos) ... : yes
  Festival (Text-to-speech) .. : yes
  GDAL/OGR (Obtuse map formats) .. : yes
  GPSMan/gpsmanshp (GPS downloads) ... : yes

xastir will be installed in /usr/local/bin.
Type 'make' to build Xastir (Use 'gmake' instead on some systems).




There are a lot of other options available in the help for configure but 
I don't know if those options are being enabled by default or not


  - Is GraphicsMagick recommended over ImageMagick?

  --with-motif-libs :: are these on by default?

   --with-postgisEnable Postgresql with PostGIS 
<--- Is it a good idea to enable the database 
functionality (postgres or MySQL)?
  --with-mysql  Enable MySQL, with spatial support if 
available.

  --with-bdb-libdir=DIR Berkeley DB lib files are in DIR
  --with-bdb-incdir=DIR Berkeley DB include files are in DIR

I also noticed that "Davis WX" is not enabled by default (it's also not 
in the same section with all the other features)







TBD: I don't think we can deal with colorspace != RGBTBD

One or more of your selected maps has an image colorspace that Xastir doesn't
like.  Unfortunately, the error message doesn't say which one, but grepping
through the source code shows a similar error message in the handlers for
OSM, WMS, geo and tiger map formats.

Guess I'll have to update those comments to be unique per section and
try again.


So after all this, and everything shows up as a "Yes" in the configure 
stage yet OSM Mapnik still doesn't work though it downloads the tiles 
but everything else works..


   - communicates with the KISS-attached AX.25 TNC
   - receives APRS stations
   - plots them on a basic vector map
   - transmits APRS position


But just no pretty maps!  Grrr.

--
[root@hampacket2 config]# xastir


Built-in map types:
  gnis   USGS GNIS Datapoints
   pop   USGS GNIS Datapoints w/population
   map   APRSdos Maps
   map   WinAPRS/MacAPRS/X-APRS Maps
   pdb   PocketAPRS Maps

Support for these additional map types has been compiled in:
   geo   Image Map (ImageMagick/GraphicsMagick library, many 
formats allowed)

   geo   URL (Internet maps via libcurl library)
   geo   URL (OpenStreetMaps via libcurl library
  Copyright OpenStreetMap and contributors, CC-BY-SA)
   shp   ESRI Shapefile Maps (Shapelib library)
   tif   USGS DRG Geotiff Topographic Maps (libgeotiff/libproj)
   xpm   X Pixmap Maps (XPM library)
   tab   MapInfo TAB
   mid   MapInfo MID
   mif   MapInfo MIF
   ddf   Spatial Data Transfer Standard (SDTS)
   rt1   US Census Bureau TIGER/Line
   s57   International Hydrographic Organization (IHO) S-57
   dgn   MicroStation DGN

festival_client: connect to server failed
SayText: Couldn't open socket to Festival
Indexing maps...
Finished indexing maps
*** Reading WX Alert log files
*** Done with WX Alert log files
TBD: I don't think we can deal with colorspace != RGBTBD: I don't think 
we can deal with colorspace != RGBTBD: I don't think we can deal with 
colorspace != RGBTBD: I don't think we can deal with colorspace != RGB



I've blown away the .xastir directory, didn't help.  I pan around in the 
UI and it's seemingly downloading the proper Mapnik tiles but nothing 
shows, e

Re: [Xastir] Quirks compiling Xastir on Centos6

2012-05-14 Thread Tom Russo
On Mon, May 14, 2012 at 09:12:10PM -0700, we recorded a bogon-computron 
collision of the  flavor, containing:
> 
> Hello Tom,
> 
> Thanks so much for the reply..  Please see inline..
> 
> > Without this you can't use GeoTIFF format maps.  The USGS used to distribute
> > lots of topo maps in this format, and it is still popular around the world
> > for other types of maps.
> Ok, that's probably not good.  

You can live without geotiff support, but if you want it you have to have
both libproj and libgeotiff (and associated development headers) installed,
and libgeotiff must be built to use libproj.

I am not sure that the Centos build of proj and libgeotiff are actually usable
in Xastir (there are details which can interfere) --- Centos, if I am not
mistaken, is very similar to Fedora and may use the same package repository.
Fedora's libproj and libgeotiff have issues, and the installation notes for
Fedora on the Xastir wiki recommend not using the packaged versions of these,
preferring instead a source code build.  See the Installation Notes section
of the Xastir wiki under Fedora 15 for details.

If you don't want to go through the trouble, what you give up is USGS topo maps
and any other maps provided in GeoTIFF format (none of the on-line maps require
this).

> I've posted the output of building Xastir 
> here:
> 
> 
> 
> Looking around trying to troubleshoot the "Xpm" issue,
> --
> checking X11/xpm.h usability... yes
> checking X11/xpm.h presence... yes
> checking for X11/xpm.h... yes
> checking for library containing XpmWriteFileFromPixmap... -lXpm
> checking Xm/XpmI.h usability... no
> checking Xm/XpmI.h presence... no
> checking for Xm/XpmI.h... no


The absense of XpmI.h is not a problem.  It is not necessary for every 
check to come up with a "yes" here --- configure is trying to figure out what
is what on your system, and adapt accordingly.  My system doesn't have 
XpmI.h either.

> >
> >> TBD: I don't think we can deal with colorspace != RGBTBD
> > One or more of your selected maps has an image colorspace that Xastir 
> > doesn't
> > like.  Unfortunately, the error message doesn't say which one, but grepping
> > through the source code shows a similar error message in the handlers for
> > OSM, WMS, geo and tiger map formats.
> Guess I'll have to update those comments to be unique per section and 
> try again.
> 
> 
> > See if OSM_tiled_mapnik works for you.  If so, then it is likely there is
> > something up with the OSM server you've selected.  Lots of the other errors
> > you're posting below imply that is the source of some of these issues.
> 
> Nope.. mapnik doesn't work.

Does it give the same error?  I use OSM_tiled_mapnik all the time and it
always works.  

> >> --
> >> When I try to load the OSM_tiled_osmarender map
> >> --
> >>
> >> Download error for tile: 
> >> http://tah.openstreetmap.org/Tiles/tile/8/39/98.png
> >> curl told us 6
> > Look suspiciously like there's a problem with the osmarender server.
> 
> It doesn't even resolve.. where do these hostnames come from?  Is there 
> a master tile server that Xastir queries or are these hostnames 
> hardcoded into the Xastir source code?
> 
> [dranch@hampacket2 ~]$ host tah.openstreetmap.org
> Host tah.openstreetmap.org not found: 3(NXDOMAIN)

tah.openstreetmap.org doesn't resolve here, either.

The tile servers are defined in the .geo file associated with the online
map selected.  tah.openstreetmap.org is in the OSM_tiled_osmarender.geo 
file.  OSM_tiled_mapnik.geo uses tile.openstreetmap.org, which resolves
Just Fine here:

> nslookup tile.openstreetmap.org
Server: 127.0.0.1
Address:127.0.0.1#53

Non-authoritative answer:
tile.openstreetmap.org  canonical name = tile.geo.openstreetmap.org.
tile.geo.openstreetmap.org  canonical name = us.tile.openstreetmap.org.
us.tile.openstreetmap.org   canonical name = london.tile.openstreetmap.org.
Name:   london.tile.openstreetmap.org
Address: 193.63.75.98


-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick

___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Quirks compiling Xastir on Centos6

2012-05-14 Thread David A. Ranch


Hello Tom,

Thanks so much for the reply..  Please see inline..


Without this you can't use GeoTIFF format maps.  The USGS used to distribute
lots of topo maps in this format, and it is still popular around the world
for other types of maps.
Ok, that's probably not good.  I've posted the output of building Xastir 
here:




Looking around trying to troubleshoot the "Xpm" issue,
--
checking X11/xpm.h usability... yes
checking X11/xpm.h presence... yes
checking for X11/xpm.h... yes
checking for library containing XpmWriteFileFromPixmap... -lXpm
checking Xm/XpmI.h usability... no
checking Xm/XpmI.h presence... no
checking for Xm/XpmI.h... no
checking for pj_init in -lproj... yes
checking xtiffio.h usability... no
checking xtiffio.h presence... no
checking for xtiffio.h... no
*** Warning: geotiff include files not found.
--

I think I have all of the required dependencies installed and there *is* 
a similar file on the file system.  Maybe this "P" file is a newer 
version than the "I"?   If not, any ideas what package might install it?


rpm -ql openmotif-devel | grep -i Xpm
/usr/include/Xm/XpmP.h





GDAL/OGR (Obtuse map formats) .. : no<--

You lose essentially nothing by not having this.  GDAL support in Xastir
doesn't actually exist, and only a small number of obsolete map formats
(notably raw TIGER/Line files) were every really implemented in OGR support.

Good to know.  I won't worry about that one








TBD: I don't think we can deal with colorspace != RGBTBD

One or more of your selected maps has an image colorspace that Xastir doesn't
like.  Unfortunately, the error message doesn't say which one, but grepping
through the source code shows a similar error message in the handlers for
OSM, WMS, geo and tiger map formats.
Guess I'll have to update those comments to be unique per section and 
try again.




See if OSM_tiled_mapnik works for you.  If so, then it is likely there is
something up with the OSM server you've selected.  Lots of the other errors
you're posting below imply that is the source of some of these issues.


Nope.. mapnik doesn't work.




--
When I try to load the OSM_tiled_osmarender map
--

Download error for tile: http://tah.openstreetmap.org/Tiles/tile/8/39/98.png
curl told us 6

Look suspiciously like there's a problem with the osmarender server.


It doesn't even resolve.. where do these hostnames come from?  Is there 
a master tile server that Xastir queries or are these hostnames 
hardcoded into the Xastir source code?


[dranch@hampacket2 ~]$ host tah.openstreetmap.org
Host tah.openstreetmap.org not found: 3(NXDOMAIN)


--David
___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


Re: [Xastir] Quirks compiling Xastir on Centos6

2012-05-12 Thread Tom Russo
On Sat, May 12, 2012 at 08:27:06PM -0700, we recorded a bogon-computron 
collision of the  flavor, containing:
> 
> Hello Everyone,
> 
> I just updated my docs on getting Xastir compiled on Centos to support 
> v6 in full RPMs but I had two questions:
> 
> 1. Two items are missing what I run Xastir's configure but I was curious 
> if I would be really missing anything from these two options?  I'm not 
> really looking to do anything fancy with Xastir though I'd like to be 
> able to support offline cached map tiles:
> --
> 
>GeoTiff (USGS Topos&  Aerial Photos) ... : 
> no<--

Without this you can't use GeoTIFF format maps.  The USGS used to distribute
lots of topo maps in this format, and it is still popular around the world
for other types of maps.

>GDAL/OGR (Obtuse map formats) .. : 
> no<--

You lose essentially nothing by not having this.  GDAL support in Xastir
doesn't actually exist, and only a small number of obsolete map formats
(notably raw TIGER/Line files) were every really implemented in OGR support.

> --
> 
> 2.  When I load different maps with the compiled code working with a Kenwood 
> D710 in KISS mode, I'm always getting
> a few of these errors from the 2.0.1CVS code (downloaded 2 days ago).  Any 
> ideas?
> --
> TBD: I don't think we can deal with colorspace != RGBTBD
> TBD: I don't think we can deal with colorspace != RGBTBD
> TBD: I don't think we can deal with colorspace != RGBTBD
> TBD: I don't think we can deal with colorspace != RGBTBD
> TBD: I don't think we can deal with colorspace != RGBTBD
> TBD: I don't think we can deal with colorspace != RGBTBD

One or more of your selected maps has an image colorspace that Xastir doesn't
like.  Unfortunately, the error message doesn't say which one, but grepping
through the source code shows a similar error message in the handlers for
OSM, WMS, geo and tiger map formats.

See if OSM_tiled_mapnik works for you.  If so, then it is likely there is
something up with the OSM server you've selected.  Lots of the other errors
you're posting below imply that is the source of some of these issues.

> --
> When I try to load the OSM_tiled_osmarender map
> --
> 
> Download error for tile: http://tah.openstreetmap.org/Tiles/tile/8/39/98.png
> curl told us 6

Look suspiciously like there's a problem with the osmarender server.
> 
> --
> When I try to load the OSM_tiled_skiiing map
> --
> xastir: improper image header `/root/.xastir/OSMtiles/skiing/8/39/98.png' @ 
> error/png.c/ReadPNGImage/3651.
> Removing /root/.xastir/OSMtiles/skiing/8/39/98.png

I'm guessing the server is returning an HTML error page instead of a PNG
file, and Xastir is objecting.

-- 
Tom RussoKM5VY   SAR502   DM64ux  http://www.swcp.com/~russo/
Tijeras, NM  QRPL#1592 K2#398  SOC#236http://kevan.org/brain.cgi?DDTNM
"And, isn't sanity really just a one-trick pony anyway? I mean all you get is
 one trick, rational thinking, but when you're good and crazy, oooh, oooh,
 oooh, the sky is the limit!"  --- The Tick

___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir


[Xastir] Quirks compiling Xastir on Centos6

2012-05-12 Thread David A. Ranch


Hello Everyone,

I just updated my docs on getting Xastir compiled on Centos to support 
v6 in full RPMs but I had two questions:


1. Two items are missing what I run Xastir's configure but I was curious 
if I would be really missing anything from these two options?  I'm not 
really looking to do anything fancy with Xastir though I'd like to be 
able to support offline cached map tiles:

--

xastir 2.0.1 has been configured to use the following
options and external libraries:

MINIMUM OPTIONS:
  ShapeLib (Vector maps) . : yes

RECOMMENDED OPTIONS:
  GraphicsMagick/ImageMagick (Raster maps) : yes (ImageMagick)
  pcre (Shapefile customization) . : yes
  dbfawk (Shapefile customization) ... : yes
  rtree indexing (Shapefile speedups)  : yes
  map caching (Raster map speedups) .. : yes
  internet map retrieval . : yes (libcurl)

FOR THE ADVENTUROUS:
  AX25 (Linux Kernel I/O Drivers)  : yes
  libproj (USGS Topos&  Aerial Photos) ... : yes
  GeoTiff (USGS Topos&  Aerial Photos) ... : no<--
  Festival (Text-to-speech) .. : yes
  GDAL/OGR (Obtuse map formats) .. : no<--
  GPSMan/gpsmanshp (GPS downloads) ... : yes
--

2.  When I load different maps with the compiled code working with a Kenwood 
D710 in KISS mode, I'm always getting
a few of these errors from the 2.0.1CVS code (downloaded 2 days ago).  Any 
ideas?
--
TBD: I don't think we can deal with colorspace != RGBTBD
TBD: I don't think we can deal with colorspace != RGBTBD
TBD: I don't think we can deal with colorspace != RGBTBD
TBD: I don't think we can deal with colorspace != RGBTBD
TBD: I don't think we can deal with colorspace != RGBTBD
TBD: I don't think we can deal with colorspace != RGBTBD

--
When I try to load the OSM_tiled_osmarender map
--

Built-in map types:
  gnis   USGS GNIS Datapoints
   pop   USGS GNIS Datapoints w/population
   map   APRSdos Maps
   map   WinAPRS/MacAPRS/X-APRS Maps
   pdb   PocketAPRS Maps

Support for these additional map types has been compiled in:
   geo   Image Map (ImageMagick/GraphicsMagick library, many formats 
allowed)
   geo   URL (Internet maps via libcurl library)
   geo   URL (OpenStreetMaps via libcurl library
  Copyright OpenStreetMap and contributors, CC-BY-SA)
   shp   ESRI Shapefile Maps (Shapelib library)
   xpm   X Pixmap Maps (XPM library)
festival_client: connect to server failed
SayText: Couldn't open socket to Festival
Indexing maps...
draw_geo_image_map:sscanf parsing error
draw_geo_image_map:sscanf parsing error
draw_geo_image_map:sscanf parsing error
draw_geo_image_map:sscanf parsing error
1 File  could not be read
Finished indexing maps

*** Reading WX Alert log files
*** Done with WX Alert log files
Download error for tile: http://tah.openstreetmap.org/Tiles/tile/8/39/98.png
curl told us 6
curlerr: Couldn't resolve host 'tah.openstreetmap.org'
Download error for tile: http://tah.openstreetmap.org/Tiles/tile/8/39/99.png
curl told us 6
curlerr: Couldn't resolve host 'tah.openstreetmap.org'
Download error for tile: http://tah.openstreetmap.org/Tiles/tile/8/39/100.png
curl told us 6
curlerr: Couldn't resolve host 'tah.openstreetmap.org'
Download error for tile: http://tah.openstreetmap.org/Tiles/tile/8/40/98.png
curl told us 6
curlerr: Couldn't resolve host 'tah.openstreetmap.org'
Download error for tile: http://tah.openstreetmap.org/Tiles/tile/8/40/99.png
curl told us 6
curlerr: Couldn't resolve host 'tah.openstreetmap.org'
Download error for tile: http://tah.openstreetmap.org/Tiles/tile/8/40/100.png
curl told us 6
curlerr: Couldn't resolve host 'tah.openstreetmap.org'
Download error for tile: http://tah.openstreetmap.org/Tiles/tile/8/41/98.png
curl told us 6
curlerr: Couldn't resolve host 'tah.openstreetmap.org'
Download error for tile: http://tah.openstreetmap.org/Tiles/tile/8/41/99.png
curl told us 6
curlerr: Couldn't resolve host 'tah.openstreetmap.org'
Download error for tile: http://tah.openstreetmap.org/Tiles/tile/8/41/100.png
curl told us 6
curlerr: Couldn't resolve host 'tah.openstreetmap.org'
Download error for tile: http://tah.openstreetmap.org/Tiles/tile/8/42/98.png
curl told us 6
curlerr: Couldn't resolve host 'tah.openstreetmap.org'
Download error for tile: http://tah.openstreetmap.org/Tiles/tile/8/42/99.png
curl told us 6
curlerr: Couldn't resolve host 'tah.openstreetmap.org'
Download error for tile: http://tah.openstreetmap.org/Tiles/tile/8/42/100.png
curl told us 6
curlerr: Couldn't resolve host 'tah.openstreetmap.org'
xastir: unable to open image `/root/.xastir/OSMtiles/osmarender/8/39/9