Ok, filed as ticket. However, removal of [owned] layers is a useful function, so how would this work otherwise (via GeoServer?)
GL >-- Original Message -- >Date: Wed, 17 Nov 2010 10:20:30 -0500 >From: David Winslow <[email protected]> >Reply-To: [email protected] >Subject: Re: [geonode] Shape upload to demo server fails >To: [email protected] > > >Oops, we do have that option, my mistake. It sounds like the layer removal >functionality has not been kept 'synched' with the rest of GeoNode as we >have changed the way that the Django side of things integrates with the >GeoNetwork and GeoServer side. Can you create a ticket for this bug >(remember the issue tracker has moved to http://dev.geonode.org/trac/). > >As far as the demo site goes, I still see an account there with your email >address... are you sure you have not just made a typo in entering your >password? > >If you like I can reset your password, just let me know (off list). > >-- >David Winslow >OpenGeo - http://opengeo.org/ > >On Wed, Nov 17, 2010 at 10:00 AM, Guido Lemoine < >[email protected]> wrote: > >> David, >> >> After uploading a layer, and visualising it in the map, >> you will have a "remove" link in the "Manage" >> menu, which, well, removes the layer (after confirmation). I am testing >> on my local (vbox) installation, but I guess this action may be restricted >> if I am not the owner of the layer (on the demo server). >> >> But, still, seems to work for me. >> >> GL >> PS. Did the demo server delete the user/passwd combinations after >> a new install? Hence, do I have to re-register? I can't login with my >> existing credentials. >> >> >> >> On 11/17/2010 3:33 PM, David Winslow wrote: >> >> I'm looking into the upload issues on the demo site now, should have a >> resolution today. >> >> However, I am a bit concerned by your comment about 'removing' a layer... >> GeoNode does not support any form of layer or metadata removal right now, >so >> I don't know what you mean by this. >> >> -- >> David Winslow >> OpenGeo - http://opengeo.org/ >> >> >> >> On Wed, Nov 17, 2010 at 6:12 AM, <[email protected]> wrote: >> >>> There are some other curious problems with the upload. >>> I upload a shape layer (OK), then remove it and try to >>> upload again (not OK, the browser (firefox) blocks). >>> >>> After restart of the browser, the layer name will show up >>> in a search, though, but the data cannot be found. The >>> layer appears in the maps_layer table of development.db. >>> >>> Maybe a non-standard use case, but this may explain some >>> of the issues. >>> >>> GL >>> >>> >>> >>> >-- Original Message -- >>> >Date: Tue, 16 Nov 2010 20:48:27 -0500 >>> >From: Chris Holmes <[email protected]> >>> >Reply-To: [email protected] >>> >Subject: Re: [geonode] Shape upload to demo server fails >>> >To: [email protected] >>> > >>> > >>> >? You tried to upload and it didn't work? What do you mean by 'Thi >>> feature >>> >is not ok!'? What was the error you got? >>> > >>> >David, I just tried an upload on demo.opengeo.org, and the upload went >>> fine, >>> >and took me to the metadata page. But then the layer didn't load. But >>> none >>> >of the layers loaded on any of the pages, neither maps nor layers nor >in >>> >map >>> >composer. Though if I go straight to geoserver I can get an openlayers >>> >preview, so it looks like it's not that geoserver is down. >>> > >>> >C >>> > >>> >On Tue, Nov 16, 2010 at 8:05 PM, Fernando Quadro <[email protected]> >>> wrote: >>> > >>> >> David, >>> >> >>> >> Thi features is not ok! >>> >> >>> >> Best regards, >>> >> >>> >> Fernando Quadro >>> >> http://www.fernandoquadro.com.br >>> >> twitter.com/fernandoquadro >>> >> >>> >> 2010/11/16 David Winslow <[email protected]> >>> >> >>> >> Actually the fix included in RC3 was erroneous (I based it on a newer >>> >>> version of Django than the one we actually use... not sure how that >>> got >>> >into >>> >>> my environment). Anyway the issue has been re-fixed on master but >I >>> have >>> >>> not updated the demo site until just now (we usually try to update >on >>> >>> Fridays but last week I forgot to do it). Can you try your upload >>> again? >>> >>> >>> >>> -- >>> >>> David Winslow >>> >>> OpenGeo - http://opengeo.org/ >>> >>> >>> >>> >>> >>> On Tue, Nov 16, 2010 at 7:05 AM, Fernando Quadro <[email protected] >>> >wrote: >>> >>> >>> >>>> Hi David, >>> >>>> >>> >>>> This feature was corrected in the RC3? See the error in attach. >>> >>>> >>> >>>> Best Regards, >>> >>>> >>> >>>> Fernando Quadro >>> >>>> http://www.fernandoquadro.com.br >>> >>>> >>> >>>> 2010/10/21 David Winslow <[email protected]> >>> >>>> >>> >>>> This fix has not been merged to the public git repository yet (it >is >>> >>>>> publicly available under my github account in the interim). I'll >>> merge >>> >it >>> >>>>> tomorrow before putting out the release candidate, which I'll >>> announce >>> >on >>> >>>>> this mailing list. >>> >>>>> >>> >>>>> -- >>> >>>>> David Winslow >>> >>>>> OpenGeo - http://opengeo.org/ >>> >>>>> >>> >>>>> >>> >>>>> On Thu, Oct 21, 2010 at 5:09 PM, Spanring, Christian < >>> >>>>> [email protected]> wrote: >>> >>>>> >>> >>>>>> Hi, >>> >>>>>> >>> >>>>>> I think I just experienced the same issue. >>> >>>>>> >>> >>>>>> FYI, in case it helps... >>> >>>>>> >>> >>>>>> * tried to upload a Shapefile on GeoNode's dev server >>> >>>>>> * GeoNode reported an error, but the Shapefile made it to >>> GeoServers >>> >>>>>> data-dir >>> >>>>>> * manually added shapefile-layer in GeoServer >>> >>>>>> * updatelayers failed with following output >>> >>>>>> >>> >>>>>> $ django-admin.py updatelayers --settings=geonode.settings >>> >>>>>> >>> /home/geonode/develop/cspanring/lib/python2.6/site-packages/registration/models.py:4: >>> >>>>>> DeprecationWarning: the sha module is deprecated; use the hashlib >>> module >>> >>>>>> instead >>> >>>>>> import sha >>> >>>>>> Traceback (most recent call last): >>> >>>>>> File "/home/geonode/develop/cspanring/bin/django-admin.py", line >>> 5, >>> >in >>> >>>>>> <module> >>> >>>>>> management.execute_from_command_line() >>> >>>>>> File >>> >>>>>> >>> "/home/geonode/develop/cspanring/lib/python2.6/site-packages/django/core/management/__init__.py", >>> >>>>>> line 429, in execute_from_command_line >>> >>>>>> utility.execute() >>> >>>>>> File >>> >>>>>> >>> "/home/geonode/develop/cspanring/lib/python2.6/site-packages/django/core/management/__init__.py", >>> >>>>>> line 379, in execute >>> >>>>>> self.fetch_command(subcommand).run_from_argv(self.argv) >>> >>>>>> File >>> >>>>>> >>> "/home/geonode/develop/cspanring/lib/python2.6/site-packages/django/core/management/base.py", >>> >>>>>> line 191, in run_from_argv >>> >>>>>> self.execute(*args, **options.__dict__) >>> >>>>>> File >>> >>>>>> >>> "/home/geonode/develop/cspanring/lib/python2.6/site-packages/django/core/management/base.py", >>> >>>>>> line 218, in execute >>> >>>>>> output = self.handle(*args, **options) >>> >>>>>> File >>> >>>>>> >>> "/home/geonode/develop/cspanring/src/GeoNodePy/geonode/maps/management/commands/updatelayers.py", >>> >>>>>> line 11, in handle >>> >>>>>> Layer.objects.slurp() >>> >>>>>> File >>> >>>>>> >>> "/home/geonode/develop/cspanring/src/GeoNodePy/geonode/maps/models.py", >>> >line >>> >>>>>> 579, in slurp >>> >>>>>> "uuid": str(uuid.uuid4()) >>> >>>>>> File >>> >>>>>> >>> "/home/geonode/develop/cspanring/lib/python2.6/site-packages/django/db/models/manager.py", >>> >>>>>> line 135, in get_or_create >>> >>>>>> return self.get_query_set().get_or_create(**kwargs) >>> >>>>>> File >>> >>>>>> >>> "/home/geonode/develop/cspanring/lib/python2.6/site-packages/django/db/models/query.py", >>> >>>>>> line 381, in get_or_create >>> >>>>>> raise e >>> >>>>>> django.db.utils.IntegrityError: maps_layer.date may not be NULL >>> >>>>>> >>> >>>>>> * layer is listed as option in "maps", but not under "data" >>> >>>>>> >>> >>>>>> Thanks, >>> >>>>>> >>> >>>>>> Christian >>> >>>>>> >>> >>>>>> >>> >>>>>> On Oct 19, 2010, at 9:30 AM, David Winslow wrote: >>> >>>>>> >>> >>>>>> > 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 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 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 is available >>> from >>> >the >>> >>>>>> Django web site. >>> >>>>>> > 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 >>> >>>>>> > >>> >>>>>> >>> >>>>>> >>> >>>>>> Please be advised that the Massachusetts Secretary of State >>> considers >>> >>>>>> e-mail to be a public record, and therefore subject to the >>> Massachusetts >>> >>>>>> Public Records Law, M.G.L. c. 66 ยง 10. >>> >>>>>> >>> >>>>> >>> >>>>> >>> >>>> >>> >>>> >>> >>>> -- >>> >>>> >>> >>>> Fernando Quadro >>> >>>> http://www.fernandoquadro.com.br >>> >>>> twitter.com/fernandoquadro >>> >>>> >>> >>>> >>> >>> >>> >> >>> >> >>> >> -- >>> >> >>> >> >>> >> >>> >> >>> >>> >>> >> >> -- >> ---------------------------------------------------------------- >> Guido Lemoine >> Joint Research Centre, European Commission >> Institute for the Protection and Security of the Citizen (IPSC) >> Global Security and Crisis Management Unit >> Via E. Fermi, 2749 TP 267 Ispra 21027 (VA), Italy >> Tel. +39 0332 786239 (direct line) Fax. +39 0332 785154 >> WWW: http://globesec.jrc.ec.europa.eu >> ---------------------------------------------------------------- >> Disclaimer: >> Views expressed are those of the individual and do not represent >> the views of the European Commission >> >> >>
