On Wed, Jun 29, 2011 at 11:16 AM, Ma, Amy <[email protected]> wrote: > The developers of the XD-Solutions at the Cubic Corporation are currently > developing a web-based proxy server for the GeoNode to allow a specific > group of users to send requests and receive responses from the GeoNode. The > following are some of the issues we encountered so far. > > > 1. Missing tabs on the GeoNode pages when accessing from other machine. > > When requesting GeoNode pages from local host, everything looks like it's > supposed to be. However when accessing from other machine, we noticed some > tabs were missing, such as Explore Maps and Create Maps tabs were absent > from the home page of the GeoNode. > > We tried the suggestion of using the actual IP address of the machine > instead of localhost for the SITEURL in settings.py, the problem remains.
This is almost certainly a misconfiguration of the GEONODE_CLIENT setting in your settings.py or local_settings.py. Can you verify what those are set to and report back to this list. Thanks! > 2. The GeoNode can't upload projection information. It only upload .tif > data. > > The GeoNode does not include the projection information such as .tfw. Jeff > Johnson from OpenGeo.org has filed this as a bug/feature request against > geonode recently. This was (just now) filed as ticket #992 http://dev.geonode.org/trac/ticket/992 > 3. Using the gdal utility tool, the GeoTiff data was translated to include > the projection information. But the resulting image of using the translated > data did not appear very clear. > > Jeff Johnson had used the gdal command line utilities and created a new > .tif with the projection information included. We uploaded the new data, and > the GeoNode page showed a not-so-clear picture. Can you give us some idea what you mean by "not so clear picture". There should be no difference between the original tiff and the one converted into a GeoTiff by the gdal tools. > 4. For the WCS request for GeoTiff(getcoverage), we were told we can do it > in a browser, or 'curl' or 'wget' it. If via the browser, the string to be > typed is long and is prone to the typos when doing so. Is there a plan in > the future for people in the OpenGeo.org to add an interface to the page so > the WCS request can be done by a point/click action? You should *not* be _typing_ wcs requests directly with curl or wget. If you need to make wcs requests directly, you should be using a library like owslib or similar to make properly formatted requests without running the risk of making typing errors. If you can provide more detail as to what you are trying to accomplish by point/click action, we can probably help out further. Jeff > Thanks for all the ideas for resolving the issues. > > Best Regards, > Amy Ma
