Luca just succeeded uploading my shape files in his bugfixed release. So, I'll await RC2 end of this week.
Sphinx looks a bit too archaic to me. In general, I don't speak python. Our contributions will probably come mostly from testing and as feature requests, though I wouldn't mind contributing use case documentation. Guido >-- Original Message -- >Date: Tue, 19 Oct 2010 09:30:04 -0400 >From: David Winslow <[email protected]> >Reply-To: [email protected] >Subject: Re: [geonode] Shape upload to demo server fails >To: [email protected] > > >Yes, the demo site is still running RC1. I don't expect to be able to >update it before this Friday, when I will update the demo site as part of >the process of releasing RC2. > >RC2 will include either the patch in question or a variant thereof. Review >is taking place on github - http://github.com/GeoNode/geonode/pulls > >You're right, the name field is a bit of a sore point. We automatically >fill it out based on the filename of the data you're uploading, but it's >first on the form so not all users are likely to notice that. On top of >that, many parts of the UI use the *title* instead of the name to identify >the layer for users, so the name isn't actually that important. It is >mostly used as a slug <http://en.wikipedia.org/wiki/Slug_(web_publishing)> >and >for WFS/WMS clients (which is the reason of the restrictions on its >content.) We'll probably be revisiting the entire upload form before too >long. > >Ways you can help include: > > - *Try it* (and report back). What you're doing now (trying things out > and telling us when GeoNode seems broken or poorly designed). > - *Documentation*. We are using Sphinx <http://sphinx.pocoo.org/> to > build the manual, but if you aren't comfortable learning the markup you >can > use your favorite word processor and someone else can do the translation >to > Sphinx. > - *Translation*. GeoNode has been written with support for UI > translation in mind; however the English translation is the only complete > one at this point. If you are fluent in another language, contributing >a > translation for the Django user interface would be a great way to help >out. > Documentation on building translations for >Django<http://docs.djangoproject.com/en/1.2/topics/i18n/localization/>is >available from the Django > web site <http://djangoproject.org/>. > >So if you are interested in helping out with GeoNode you're actually off >to >a pretty good start :) > >-- >David Winslow >OpenGeo - http://opengeo.org/ > >On Tue, Oct 19, 2010 at 6:31 AM, [email protected] < >[email protected]> wrote: > >> Hi Guido, >> don't know if it's related but RC1 of GeoNode has a problem with >> data upload. This patch [1] solved the problem in my testing server, but >> the issue remains for GeoTIFF data. >> Can you send me your data so I can test it in my server? >> >> Ciao >> Luca >> >> 2010/10/19 <[email protected]>: >> > Hi, >> > >> > Just starting to use GeoNode, and before going through >> > the install, I tried out the demo server, in particular >> > the data upload at http://demo.geonode.org/data/upload >> > >> > I tried to upload a "land use" sahpe file for Port-au-Prince >> > (Haiti) for testing. It has 8 vectors with an ad-hoc land >> > use classification. All loads without problems in QGIS. >> > I do not have the .prj file (with is said to be optional) >> > but data is in EPSG:4326 (lat-lon). Vectors are MULTIPOLYGON >> > type. >> > >> > Upload fails, and I only get "An error occurred while loading >> > the data.". As a sideline, the name field complains about non- >> > character fields (-, space, etc.) which is somewhat awkward >> > for "natural" naming. >> > >> > My prime interest, for the moment, is to test the meta-data >> > tagging, and WMS and WFS fucntionalities, including re-projection >> > and re-formatting. Mid-term, we may be interested to set up >> > internal and external GeoNodes. >> > >> > I read the recent FOSS4G presentations, and am buying into the >> > idea that GeoNode is a step ahead. Documentation is somewhat >> > poorish, though, and community momentum slowly building up. >> > We'd be interested to know how we can contribute (as users, mostly) >> > >> > Guido Lemoine >> >> >> >> >> -- >> Luca Casagrande >> http://www.lucacasagrande.net >> twitter: lucacasagrande >>
