GeoServer

Improve experience configuring geometryless feature types

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 1.6.1
  • Fix Version/s: 2.0.x
  • Component/s: Configuration
  • Labels:
    None
  • Number of attachments :
    0

Description

Adding tables that do not contain geometries is important for uses where the client software will be joining tables that have geometries with those that don't. This often happens in a normalized relational database layout.

The New FeatureType configuration page recognizes that the table has no geometry and assigns an SRS of -1 and empty bounding box info by default. It should instead set default values so that clicking submit doesn't return an error. At the moment, a user has to specify a valid SRS (like 4326) and enter "0" in all bounding box fields. Perhaps an SRS of 0 or -1 could be used to denote no geometry and the BBox info could be filled in with zeros.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrea Aime added a comment -

The title and the description are confusing me a little. The title seems to imply a solid failure, the description the lack of forgiving defaults.

In this case I guess the GeoServer UI could force in 4326 and full world extension in without asking the user in fact.

Show
Andrea Aime added a comment - The title and the description are confusing me a little. The title seems to imply a solid failure, the description the lack of forgiving defaults. In this case I guess the GeoServer UI could force in 4326 and full world extension in without asking the user in fact.
Hide
Permalink
Amos Hayes added a comment -

Thanks Andrea. I'm very glad it works at all (it was broken a few releases back) but having it work with a sensible set of defaults without those extra steps will be great for our environment where people who are not computer/geomatics types are sometimes responsible for making their data available via geoserver.

Show
Amos Hayes added a comment - Thanks Andrea. I'm very glad it works at all (it was broken a few releases back) but having it work with a sensible set of defaults without those extra steps will be great for our environment where people who are not computer/geomatics types are sometimes responsible for making their data available via geoserver.
Hide
Permalink
Aleda Freeman added a comment -

Glad I found this description. Just tried with 2.0.1 and got an error because I had to guess what to put in for spatial information. Since geometryless tables have no spatial information it's difficult to know that each bounding box box should have a 0. It would be great to fill that in by default in the UI, and also any EPSG (since it doesn't matter). That way, the user can publish the tables without needing to guess.

Show
Aleda Freeman added a comment - Glad I found this description. Just tried with 2.0.1 and got an error because I had to guess what to put in for spatial information. Since geometryless tables have no spatial information it's difficult to know that each bounding box box should have a 0. It would be great to fill that in by default in the UI, and also any EPSG (since it doesn't matter). That way, the user can publish the tables without needing to guess.

People

Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.