Nothing comes to mind directly - could you set DEBUG=True and post the
stack trace?
-Adam
On 12/09, Mark Headd wrote:
> Kaleb,
>
> If you haven't worked past your error, you might try posting it to the
> issues list in ht eODC Github repo.
>
>
https://github.com/azavea/Open-Data-Catalog/issues
>
> The Philly implementation may be running an older version of ODC, so if you
> are using the latest code there may be enhancements not reflected in the
> Philly site.
>
>
> On Sat, Dec 7, 2013 at 2:10 PM, Kaleb Clark <
ka...@codeforsacramento.org>wrote:
>
> > Good Morning,
> >
> > I am working on a deployment for the Sacramento CfA brigade. I have had
> > success getting CSW & ODC running but now running into an error trying to
> > create a resource.
> >
> > *Error*: "Exception Value: Could not create geometry because of errors
> > while reading input."
> >
> > I the WKT geometry field is blank. The sample resource I was adding did
> > not contain any geometries.
> >
> > The error is preventing any resource at all from being added.
> >
> > I also notice that these fields are in the suggestion form as well. When i
> > look at Philly's implementation, these fields are not in the suggestion
> > form. Is there a configuration method to disable the WKT geometries?
> >
> > Thanks,
> > -Kaleb Clark
> > -Code4Sac
> >
> >
>
>
>
--
Adam Hinz
Software Engineer, Azavea
ad...@adamhinz.com | c:
608-445-8391 | Twitter: @ahinz