Hi,
Two very quick questions regarding the Tiger version of Grass-GIS 6.4
(from William K).
1) It is just me, or are the drop-down menus missing from the GIS
manager GUI? (I can get by with command lines, but some of my users
might jack up ...)
2) I'm trying to test a WFS; Grass asks for Xerxes-c support. How do I
achieve this in the OSX environment?
Cheers all,
Richard C
On Nov 25, 2008, at 10:59 PM, Richard Chirgwin wrote:
Hi,
Two very quick questions regarding the Tiger version of Grass-GIS 6.4
(from William K).1) It is just me, or are the drop-down menus missing from the GIS
manager GUI? (I can get by with command lines, but some of my users
might jack up ...)
TclTk or wxPython GUI?
For the TclTk GUI I now use an Aqua TclTk (ActiveTcl). The menus are where you would find them in any other normal Mac application, not in the window.
I've seen random ocurrences in wxpython GUI where the titlebar gets covered by the menbar. I think it may have something to do with a mismatching runtime Python vs what GRASS was compiled for.
2) I'm trying to test a WFS; Grass asks for Xerxes-c support. How do I
achieve this in the OSX environment?
? Asks for?
My GDAL framework has Xerces support, for ILI and GML formats.
There is no xerces program that GRASS can run, so Xerces would have to be used as a library and compiled into GRASS.
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/
"History is an illusion caused by the passage of time, and time is an illusion caused by the passage of history."
- Hitchhiker's Guide to the Galaxy
Richard Chirgwin wrote:
Two very quick questions regarding the Tiger version of Grass-GIS 6.4
(from William K).1) It is just me, or are the drop-down menus missing from the GIS
manager GUI? (I can get by with command lines, but some of my users
might jack up ...)2) I'm trying to test a WFS; Grass asks for Xerxes-c support. How do I
achieve this in the OSX environment?
First, note that the Xerces check in the v.in.wfs script is broken; it
uses "ldd", which (AFAIK) is specifc to Linux. You might want to try
removing the lines:
if [ -z "`ldd $OGRINFO | grep xerces`" ] ; then
g.message -e "OGR needs to be compiled with xerces-c support"
exit 1
fi
from the $GISBASE/scripts/v.in.wfs file.
Other than that, I don't know whether William's GDAL framework
includes Xerces. If it doesn't, you'll probably need to build GDAL
(and possibly Xerces itself) from source.
--
Glynn Clements <glynn@gclements.plus.com>
On Nov 25, 2008, at 11:22 PM, Glynn Clements wrote:
First, note that the Xerces check in the v.in.wfs script is broken; it
uses "ldd", which (AFAIK) is specifc to Linux. You might want to try
removing the lines:if [ -z "`ldd $OGRINFO | grep xerces`" ] ; then
g.message -e "OGR needs to be compiled with xerces-c support"
exit 1
fifrom the $GISBASE/scripts/v.in.wfs file.
Even if there is a similar tool on OSX (otool provides that info), this will only work if Xerces is linked as a shared library. I build my GDAL framework with a static Xerces since GDAL is the only thing I've encountered so far that uses it.
I see another problem - OSX does not have lynx. Wouldn't curl or wget work for this, and be more universally available? (curl for OSX)
Other than that, I don't know whether William's GDAL framework
includes Xerces. If it doesn't, you'll probably need to build GDAL
(and possibly Xerces itself) from source.
It does.
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/
"History is an illusion caused by the passage of time, and time is an illusion caused by the passage of history."
- Hitchhiker's Guide to the Galaxy
First, an embarrassed 'mea culpa' about the menus. I'm so accustomed to
dragging the GIS manager to my second screen that I didn't even look at
the primary screen for the menus! Sorry 'bout that ... <blush>
Now for the serious stuff ...
William Kyngesburye wrote:
On Nov 25, 2008, at 11:22 PM, Glynn Clements wrote:
First, note that the Xerces check in the v.in.wfs script is broken; it
uses "ldd", which (AFAIK) is specifc to Linux. You might want to try
removing the lines:if [ -z "`ldd $OGRINFO | grep xerces`" ] ; then
g.message -e "OGR needs to be compiled with xerces-c support"
exit 1
fifrom the $GISBASE/scripts/v.in.wfs file.
Even if there is a similar tool on OSX (otool provides that info),
this will only work if Xerces is linked as a shared library. I build
my GDAL framework with a static Xerces since GDAL is the only thing
I've encountered so far that uses it.I see another problem - OSX does not have lynx. Wouldn't curl or wget
work for this, and be more universally available? (curl for OSX)
So which would be safer, to remove the check from v.in.wfs, or try some
other workaround?
By the way, the error from v.in.wfs is "OGR needs to be compiled with
xerces-c support".
RC
Other than that, I don't know whether William's GDAL framework
includes Xerces. If it doesn't, you'll probably need to build GDAL
(and possibly Xerces itself) from source.It does.
-----
William Kyngesburye <kyngchaos*at*kyngchaos*dot*com>
http://www.kyngchaos.com/"History is an illusion caused by the passage of time, and time is an
illusion caused by the passage of history."- Hitchhiker's Guide to the Galaxy
On Wed, Nov 26, 2008 at 6:55 AM, William Kyngesburye
<woklist@kyngchaos.com> wrote:
On Nov 25, 2008, at 11:22 PM, Glynn Clements wrote:
First, note that the Xerces check in the v.in.wfs script is broken; it
uses "ldd", which (AFAIK) is specifc to Linux. You might want to try
removing the lines:if [ -z "`ldd $OGRINFO | grep xerces`" ] ; then
g.message -e "OGR needs to be compiled with xerces-c support"
exit 1
fi
Done (in 6.4.svn).
I see another problem - OSX does not have lynx. Wouldn't curl or wget work
for this, and be more universally available? (curl for OSX)
Fixed using curl (in 6.4.svn).
I have also fix TMP file cleanup and added cmd history.
To test the module (in LatLong location):
# fetch registered GRASS users:
v.in.wfs wfs="http://mapserver.gdf-hannover.de/cgi-bin/grassuserwfs?REQUEST=GetFeature&SERVICE=WFS&VERSION=1.0.0"
out=grass_users
cheers
Markus
William Kyngesburye wrote:
I've seen random ocurrences in wxpython GUI where the titlebar gets
covered by the menbar. I think it may have something to do with a
mismatching runtime Python vs what GRASS was compiled for.
The only parts of the wx GUI which are "compiled" for any version of
[wx]Python are the vdigit and nviz modules. The core GUI doesn't
include any compiled code.
> 2) I'm trying to test a WFS; Grass asks for Xerxes-c support. How do I
> achieve this in the OSX environment?
>
? Asks for?My GDAL framework has Xerces support, for ILI and GML formats.
There is no xerces program that GRASS can run, so Xerces would have to
be used as a library and compiled into GRASS.
v.in.wfs uses v.in.ogr to perform the actual work, but this relies
upon GDAL/OGR having Xerces support.
The script tries to be clever and detect whether this is the case, but
the end result is that it often refuses to run simply because it
incorrectly concludes that GDAL lacks Xerces support.
--
Glynn Clements <glynn@gclements.plus.com>
William Kyngesburye wrote:
I see another problem - OSX does not have lynx. Wouldn't curl or wget
work for this, and be more universally available? (curl for OSX)
Yes. You just need some way to retrieve the data for a URL. The 7.0
version uses Python's urllib module.
--
Glynn Clements <glynn@gclements.plus.com>
Richard Chirgwin wrote:
So which would be safer, to remove the check from v.in.wfs, or try some
other workaround?
Remove the check.
By the way, the error from v.in.wfs is "OGR needs to be compiled with
xerces-c support".
Right. This is printed by the script when it fails to detect Xerces
support (in this case, because the check is broken).
--
Glynn Clements <glynn@gclements.plus.com>
On Wed, Nov 26, 2008 at 6:47 PM, Glynn Clements
<glynn@gclements.plus.com> wrote:
Richard Chirgwin wrote:
So which would be safer, to remove the check from v.in.wfs, or try some
other workaround?Remove the check.
... or update from SVN or get the next SVN snapshot on Saturday 
Markus
Markus Neteler wrote:
On Wed, Nov 26, 2008 at 6:47 PM, Glynn Clements
<glynn@gclements.plus.com> wrote:
Richard Chirgwin wrote:
So which would be safer, to remove the check from v.in.wfs, or try some
other workaround?
Remove the check.
... or update from SVN or get the next SVN snapshot on SaturdayMarkus
Thanks everybody, and I'll report back when I've fixed the script ...
Cheers,
Richard