Details

    • Type: Wish Wish
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Number of attachments :
      0

      Description

      Social Change Online did some solid work on the complex_sco branch of GeoServer (http://svn.refractions.net/geoserver/branches/complex_sco/) to put in preliminary support for complex features, with nested XML. We need to roll their work into GeoTools and provide support for all types of complex features. This would allow us to fully pass the CITE tests, as we currently don't do the optional complex tests. Most all this work should take place in GeoTools, but then it would be great if we could put a UI on top of it in GeoServer. It would also be great if we had a way to represent well known schemas, James recently had an interesting idea for having them on the web, so geotools featureTypes could be created directly from them. Would be nice to have users just specify what their schema target is, and then just provide their mappings from their datasource(s) to the schema values.

        Activity

        Hide
        Rob Atkinson added a comment -

        The current (complex_sco branch) provides a level of support for mapping some typical schema patterns to multi-table data sources - it is limited in scope but addresses two major issues that should be useful (the 80/20 rule): allowing a master/detail join construct to support features with a single multi-value property and mapping the actual result set to an explicit schema.

        The big thing it doesnt do yet is support a single query returning related features - for example a road network comprised of road segments and junctions. This requires a more sophisticated "join" capable of merging results from queries on separate data stores.

        This would also make geoserver capable of dealing with some important data standards such as the US TIGER and UK Ordnance Survey topological formats.

        Show
        Rob Atkinson added a comment - The current (complex_sco branch) provides a level of support for mapping some typical schema patterns to multi-table data sources - it is limited in scope but addresses two major issues that should be useful (the 80/20 rule): allowing a master/detail join construct to support features with a single multi-value property and mapping the actual result set to an explicit schema. The big thing it doesnt do yet is support a single query returning related features - for example a road network comprised of road segments and junctions. This requires a more sophisticated "join" capable of merging results from queries on separate data stores. This would also make geoserver capable of dealing with some important data standards such as the US TIGER and UK Ordnance Survey topological formats.
        Hide
        Chris Holmes added a comment -

        There's a number of other issues tracking this stuff...

        Show
        Chris Holmes added a comment - There's a number of other issues tracking this stuff...

          People

          • Assignee:
            Chris Holmes
            Reporter:
            Chris Holmes
          • Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: