Hmmm.... not sure what to say. I know that a view properly registered in
geometry_columns should work as a regular table.

You can try turning up logging to GEOTOOLS_DEVELOPER_LOGGING and see if any
logs indicate where the issue lies.

-Justin

On Mon, Feb 7, 2011 at 12:54 AM, jose garcia <josega...@gmail.com> wrote:

> Hi Justin
>
> The view is very simple. I tried for now a SELECT * FROM table. Also is
> registered in geometry_columns.
>
> I get no error in the console, just the bbox fields are empty after trying
> to compute bbox (the response in firebug seem ok, but with this information
> empty). I think is related to no primary key in the view (although includes
> the primary key from table, but not managed as a primary key in the view),
> not really sure for now.
>
> Regards,
> Jose García
>
>
>
> On Fri, Feb 4, 2011 at 6:23 PM, Justin Deoliveira <jdeol...@opengeo.org>wrote:
>
>> Hi Jose,
>>
>> It is indeed possible to use a view as long as it is registered in
>> geometry_columns. So the problem must lie elsewhere, possibly in the
>> view definition or something.
>>
>> What is the error your receive on the console?
>>
>> -Justin
>>
>> On Fri, Feb 4, 2011 at 2:48 AM, jose garcia <josega...@gmail.com> wrote:
>>
>>> Hi
>>>
>>> I have create a view in Postgres from a spatial table. The view is also
>>> registered in geometry columns table and can use it to create a layer in
>>> GeoServer (2.0.2). When clicking on the "Compute from data"or "Compute from
>>> native bounds" buttons, no bbox are retrieved. No error in console log also.
>>>
>>> Using the table instead of the view, works ok. Is not possible to
>>> calculate bbox from postgres views?
>>>
>>> Thanks and regards,
>>> Jose García
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> The modern datacenter depends on network connectivity to access resources
>>> and provide services. The best practices for maximizing a physical
>>> server's
>>> connectivity to a physical network are well understood - see how these
>>> rules translate into the virtual world?
>>> http://p.sf.net/sfu/oracle-sfdevnlfb
>>> _______________________________________________
>>> Geoserver-users mailing list
>>> Geoserver-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>
>>>
>>
>>
>> --
>> Justin Deoliveira
>> OpenGeo - http://opengeo.org
>> Enterprise support for open source geospatial.
>>
>>
>


-- 
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to