WO2003098482A1 - Portail de donnees spatiales - Google Patents

Portail de donnees spatiales Download PDF

Info

Publication number
WO2003098482A1
WO2003098482A1 PCT/US2003/015303 US0315303W WO03098482A1 WO 2003098482 A1 WO2003098482 A1 WO 2003098482A1 US 0315303 W US0315303 W US 0315303W WO 03098482 A1 WO03098482 A1 WO 03098482A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
spatial
tool
dataset
layer
Prior art date
Application number
PCT/US2003/015303
Other languages
English (en)
Inventor
Scott A. Evans
Original Assignee
Celeritasworks, L.L.C.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Celeritasworks, L.L.C. filed Critical Celeritasworks, L.L.C.
Priority to AU2003241459A priority Critical patent/AU2003241459A1/en
Publication of WO2003098482A1 publication Critical patent/WO2003098482A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/29—Geographical information databases

Definitions

  • the present invention relates to the field of spatially linking one or more disparate datasets.
  • a dataset is a collection of data that relates to a topic or thing.
  • the dataset has data attributes that describe the collection of data.
  • the data attributes are related to each other and related to the topic or thing of the dataset.
  • a business dataset for a set of oil wells may contain a set of attributes for a lease for land on which the oil wells are located or for oil well production statistics.
  • Geographic information system (GIS) products provide geographic information, such as maps or other geographic data, based on some input. With most GIS products, if you want to relate data from multiple disparate datasets to geographic data you must permanently merge the data from the disparate datasets with the geographic data. However, this requires that the data be replicated.
  • the data may require conversion prior to replication.
  • Other GIS products provide the ability to join or associate one or more datasets with geographic data, but only as long as the datasets are in the same database in which the geographic data is housed. Thus, new systems and methods are needed to enable linking different datasets with spatial data without replicating the datasets and to enable a user to access the datasets spatially.
  • a system and method linking one or more disparate datasets with one or more spatial layers to create linked datasets One or more data attributes common to the dataset and the spatial layer are identified, and the linkage is defined between the dataset and the spatial layer.
  • the spatial layer and the linked data set then may be queried using a singe input query.
  • Features from the spatial layer and features from the linked dataset that match the query are generated for display.
  • Figure 1 is a diagram of a spatial system for linking a spatial layer with a dataset in accordance with an embodiment of the present invention.
  • Figure 2 is a block diagram of layers in a spatial system in accordance with an embodiment of the present invention.
  • Figure 3 is a diagram of a linked datasets in a spatial system in accordance with an embodiment of the present invention.
  • Figure 4 is a diagram of inputs and outputs for a spatial system in accordance with an embodiment of the present invention.
  • Figure 5 is a diagram of a process for linking a spatial layer with a dataset in accordance with an embodiment of the present invention.
  • Figure 6 is a diagram of a user interface for a spatial system in accordance with an embodiment of the present invention.
  • FIGS. 7-30 are screen diagrams of a user interface for a spatial system in accordance with an embodiment of the present invention.
  • Figures 31-55 are screen diagrams of an administrative assistant of a user interface for a spatial system in accordance with an embodiment of the present invention.
  • the systems and methods of the present invention link one or more disparate datasets with one or more spatial layers so that data from the datasets does not have to be replicated for the spatial layer or the other datasets. Additionally, in some embodiments, one or more datasets from different data locations, including different databases and/or databases from different vendors and/or databases in different physical locations, are linked with the spatial layer. Thus, disparate data from disparate sources may be accessed using spatial data queries. In another embodiment, one or more documents are linked to one or more datasets for one or more spatial layers.
  • the spatial portal system 102 of Figure 1 includes a spatial processing system 104, a user interface 106, and a data system 108.
  • the spatial portal system 102 optionally may include another data system 110 and/or an input/output device 112 associated with the user interface 106.
  • the spatial processing system 104 processes spatial data and business data or other dataset data and spatially links the spatial data to the dataset data to create one or more spatially linked datasets.
  • the spatial processing system 104 then enables performing queries of the linked dataset data using a query of the spatial data and the business data.
  • the spatial processing system 104 includes one or more processors to process the spatial data and the dataset data, to link the spatial data and the dataset data, and to perform queries. Memory is used to store data being processed.
  • the user interface 106 presents spatial data and/or dataset data for display to a user.
  • the spatial data and/or dataset data is received at the user interface 106 from the spatial processing system 104.
  • the user interface 106 also enables a user to enter input data to be used for queries, linking datasets and spatial layers, or otherwise building an application.
  • the queries are sent to, and processed by, the spatial processing system 106.
  • the data systems 108 and 110 store and/or retrieve spatial data, dataset data, and/or other data.
  • the data systems 108 and 110 communicate with the spatial processing system 104 to transmit data to, and/or receive data from, the spatial processing system.
  • the data systems each represent one or multiple data systems.
  • the data system 110 is optional.
  • the data system 108 and/or the data system 110 is a data system internal to the spatial processing system 104. In this embodiment, the data system 108 and/or the data system 110 can be accessed via an intranet connection.
  • the data system 108 and/or the data system 110 can be connected directly to, or be a sub-component of, the spatial processing system 104.
  • the data system 108 and/or the data system 110 is an external data system.
  • the external data system 108 and/or 110 communicates with the spatial processing system 104, such as over a connection, to transmit data to, and receive data from, the spatial processing system.
  • the external data system 108 and/or 110 is accessed via an internet connection.
  • the spatial processing system 104 processes a universal resource locator (URL) or another designation to connect to the external data system 108 and/or 110 and to communicate with the external data system for retrieving and/or sending data.
  • URL universal resource locator
  • the input/output device 112 includes a monitor, a printer, another data output device, a mouse or pointer, a keyboard, another data entry device, other input or output devices, or a combination of the foregoing.
  • the user interface 106 is generated for display on the input/output device 112. In another embodiment, the user interface 106 receives input data from the input/output device
  • the spatial portal system 102 links datasets with one or more spatial layers.
  • the spatial layers and the datasets include features, and features include spatial attributes and/or data attributes.
  • a spatial attribute is one or more points, lines, and/or polygons that represent a geographical element or another physical element.
  • a geographical element includes a building, a city, a county, a selected area, a state, a country, an address, a zip code, a location, point in space, or another element.
  • a geographical element has a position, such as a position in space.
  • a physical element has a position, such as a position in space
  • a data attribute is one member of a collection of data that has a relationship to an element, either directly or indirectly. For example, when grouping population data for a census for a state, the population is a data attribute that has a relationship to the state. In another example, when grouping finance information for leases of land for oil wells, the finance information is a data attribute that has a relationship to a lease for land.
  • a feature is an element that has one or more feature attributes, including one or more data attributes and one or more spatial attributes.
  • the data and/or spatial attributes have a relationship to each other because of the relationship to the element.
  • a cell tower is a feature that has a height data attribute and a location spatial attribute.
  • a second cell tower is another feature that has a height data attribute and a different location spatial attribute.
  • Each cell tower is a different feature because each cell tower can be separately identified with its data attributes and/or spatial attributes.
  • a specific oil well is a feature that has a well depth as a data attribute.
  • a first population statistic is a data attribute of a first zip code feature
  • a second population statistic is a data attribute of a second zip code feature.
  • the zip code is a spatial element because it has at least one spatial attribute, such as a position and boundaries.
  • Natural attributes of a feature are those attributes that are inherent to the feature.
  • a natural attribute of a well is a well type, such as oil, gas, water, or other.
  • Each data attribute and each spatial attribute has a data value.
  • the height attribute and the location attribute of the first cell tower each are populated with a data value.
  • These data values are collected in datasets.
  • the datasets may be in one or more databases, in discrete data sources, or in other locations.
  • the data value for the data attribute is referred to as the data attribute for ease.
  • a layer is a collection of similar features that have common types of data attributes and/or spatial attributes.
  • a cell tower layer includes the first cell tower as a first feature and the second cell tower as a second feature. The features are grouped in the cell tower layer because they have similar data attributes of cell data.
  • a well layer for an oil well application represents a collection of wells, where each well is a separate feature having at least one data attribute in common.
  • Layers include a spatial layer, a dataset layer, and/or other layers.
  • a spatial layer contains or identifies some spatial information, such as for a city, county, region, or another spatial element.
  • spatial layers are a set of one or more features that have a set of one or more data attributes. For example, a layer of United States counties might have census related population statistics and gender and race related statistics, in addition to the spatial information that describes the polygons that make of the shape of each county.
  • Figure 2 depicts an example of the above referenced relationship between attributes 202-208, features 210-212, and a layer 214.
  • a first feature 210 has a first attribute 202 to an Nth attribute 204.
  • a second feature 212 has another first attribute 206 to another Nth attribute 208.
  • Figure 3 depicts an embodiment of a spatial processing system 104A process.
  • the spatial processing system 104 spatially links one or more spatial layers 302-304 with one or more disparate datasets 306-310 to create one or more spatially linked datasets 312.
  • spatial layers have data attributes that are native to the spatial feature.
  • a county may have a polygon shape. But it also may have other attributes, such as population and other attributes. These natural data attributes are the data attributes that are part of the spatial layer.
  • a dataset contains or identifies a collection of data that relates to a topic or thing.
  • a dataset such as a data table, may be a dataset in a database or location other than a database containing spatial information for the spatial layer and other than a location of another dataset.
  • a disparate dataset refers to a dataset that is not co-located with another dataset or is not in a same data system or database as the other dataset.
  • Disparate datasets may be located in different storage areas, such as different databases or different relational database management system (RDMS) database tables. However, some disparate datasets may be located in the same storage area, such as a same database, but organized as different data tables.
  • the disparate datasets are not a part of the feature attributes of the spatial layer, the datasets can be linked to the spatial layer using data attributes from the dataset that are inherently related to the spatial layer (referred to as natural keys), such as from a common data attribute, to create linked datasets. A user then can access the disparate datasets spatially.
  • Accessing a dataset spatially refers to querying a linked dataset that has a natural relationship to spatial data in a spatial layer and selecting data from the linked dataset based on the selected spatial data.
  • a wells spatial layer has an oil well feature that has a first dataset with production over time data attributes.
  • An oil production statistic could be added to the data attributes of the oil well feature.
  • the specific attribute for the oil production statistic would only represent one moment in time, that is oil production at the time of creation of the well spatial layer. If the oil production statistics are left in a second dataset that is disparate from the first dataset, production statistics representing different points in time may be accessed without having to change the spatial layer representing wells for each point in time that is of interest.
  • the linked datasets in this example may be accessed spatially, for example, by querying the wells spatial layer for all wells in a region that are producing oil from a selected formation and that have a selected oil production statistic.
  • the production data from the resulting wells at various points in time will be produced.
  • the production data is spatially accessed via the spatial attributes of the wells spatial layer, i.e. the wells in a region, and the data attributes for the wells, i.e. the selected formation and the selected oil production statistic.
  • disparate datasets are dynamically linked at run time with a spatial layer to create a linked dataset, thereby extending the natural data attributes of the spatial layer with those from the linked dataset.
  • the datasets are linked using a spatial attribute common to both datasets and are linked without copying data from one dataset to the other.
  • the spatial system 102 links the disparate datasets so that the datasets remain in their respective original data location, file, table, database, or other location. Thus, the need to replicate the data to get it into the same (non-disparate) database as the spatial data or the same database as another dataset is eliminated.
  • This combination of disparate datasets and a spatial layer is referred to as a linked dataset.
  • multiple datasets are identified from a query and the databases are merged at run time using a data attribute common to a spatial layer and to the multiple datasets.
  • the datasets and the spatial data are linked dynamically at run time, not permanently.
  • any number of linked datasets can be established for a spatial layer without altering the spatial and data attributes of the spatial layer or requiring any alterations of the disparate datasets.
  • the spatial system enables linking datasets from different databases and database types.
  • a dataset is spatially linked with a spatial layer by identifying an attribute common to the spatial layer and to the dataset and defining a linkage between the spatial layer and the dataset for that attribute.
  • the linkage instmcts the spatial processing system 104 where to find the dataset and how to relate it to the spatial layer.
  • a common attribute is identified between the spatial layer and the dataset, the location of the data attribute for the dataset is identified, and the data attribute is linked to the same attribute of the spatial layer.
  • a spatial layer is linked to a data attribute that is present in both the spatial layer and the dataset.
  • a spatial layer is linked to a first dataset by linking a data attribute that is present in both the spatial layer and the first dataset, and the spatial layer is Unked to a second dataset by linking another data attribute that is present in both the spatial layer and the second dataset.
  • the spatial layer is spatially linked to the first dataset and the second dataset, and the first dataset and the second dataset are indirectly linked to each other via the spatial layer.
  • the first data attribute is different from the second data attribute.
  • the spatial layer is linked to a first dataset by linking a data attribute that is present in both the spatial layer and the first dataset, and the spatial layer is linked to a second dataset by linking the same data attribute, which also is present in the second dataset.
  • a query may be performed for the spatially linked data. Both the spatial layer and the linked dataset are queried with an input. The spatial layer is queried to identify spatial features that match the input, if any. The Unked dataset is queried to identify data attributes from the Unked dataset that match the input, if any. In one embodiment, the spatial layer is queried first, and the Uked dataset is queried next. In another embodiment, the liked dataset is queried first, and the spatial layer is queried next. In one embodiment, a standard query language (SQL) query is performed on the linked dataset data. In another embodiment, an SQL query is performed on the spatial layer.
  • SQL standard query language
  • the spatial features associated with the match are generated to a map image.
  • the map image is generated to a display in one embodiment.
  • the dataset features associated with the match are generated to a feature output. These features are referred to herein as selected features.
  • the selected features are generated to a display in one embodiment as a tabular Ust.
  • a query match also identifies linked features and/or Unked documents. The Unked features and/or Unked documents are generated to a display in one embodiment.
  • the spatial portal system 102 has a GUI user interface with a configuration manager that is used to define the relationships between one or more datasets and one or more spatial layers. This may be, for example, a textual definition of the relationship that a spatial layer will have at run-time to one or more disparate datasets.
  • the linking relationships may be defined via extensible markup language (XML) entries within the spatial portal system 102.
  • the linked dataset configuration definitions then are stored by the configuration manager in XML for use by the spatial portal system 102. Thus, a user does not have to write code to Unk the datasets.
  • Unked datasets Once a user has defined Unked datasets, the user may use the Unked datasets within the definitions of user tools.
  • the tools may include search, filter, or view tools that are published for use by a spatial portal system 102 application.
  • the spatial portal system 102 appUcation then can use these published tools to obtain information from spatial layers and linked datasets.
  • Linked datasets can be used within defined tools as if the features of the Unked dataset were natural data attributes of a spatial layer.
  • a filter tool might be created that highUghts zip codes that have household poverty levels exceeding a given level.
  • the filter tool uses a Unked dataset on the zip code layer to provide household poverty statistics because the poverty data was not present in the data attributes of the zip code layer.
  • the tool actually uses data attributes of the linked dataset to narrow the set of spatial features that result from the tool's query operation.
  • the data attributes of the linked dataset appear to the rest of the spatial portal system 102 as if they were just part of the native attributes of the spatial layer.
  • a pubUshed query tool such as a filter tool or a search tool
  • a map image iUustrating the results of the query is generated for display
  • optionaUy a tabular Ust of data attributes that resulted from the query operation is generated for display.
  • These include attributes from the spatial layer feature and attributes from the datasets.
  • a user selects a spatial layer feature that has defined Unked datasets
  • a tabular display of the feature's natural data attributes is generated.
  • Each row of the table is a different feature, and each column depicts a different attribute of the feature.
  • the table may include column headings to identify the feature attributes.
  • a Ust of the linked datasets (associated with the feature's parent layer) that have available data also is generated. The user then can select any of the available Unked datasets to display a tabular Ust of records from the selected Unked dataset.
  • the spatial portal system 102 can dynamically Unk documents to spatial features to aUow for the ability to organize documents and navigate to documents spatiaUy, effectively building a run-time relationship between individual spatial features and one or more documents. For example, a document containing city level homeland security statistics for the Seminole county in Oklahoma can be linked to a "Seminole OK" feature of the Counties layer.
  • a user interface is used to insert a new document into a document index database and bind this index entry to a specified spatial layer.
  • the user interface queries the user for the document location and the specific spatial layer feature to which the document wiU be Unked.
  • the document may be "bound" to the spatial feature of the spatial layer in a document index table.
  • SQL is used to insert the document index relationship entries to specify documents are associated with what features.
  • a GUI wizard can faciUtate this process.
  • a user can access Unked documents by selecting spatial features on the map. If Unked documents exist for the selected feature, references identifying the document titles are displayed. The user can then display these Unked documents, in their native form, by selecting the respective document reference.
  • Figure 4 depicts an exemplary embodiment of selectable options and outputs of a spatial processing system 104B.
  • the selectable options and outputs are exemplary.
  • One or more spatial layers 402 may be defined for an application of the spatial processing system 104B.
  • the particular application such as an oil weU appUcation, a population statistics appUcation, or a ceU tower appUcation, determine the particular spatial layers that are defined.
  • spatial layers are defined for a counties layer, a states layer, a roads layer, and other layers.
  • the spatial layers that are defined and selected for processing may be queried, and the corresponding spatial features may be generated to a map image or other image.
  • the tools include a search tool 404, a filter tool 406, and a view tool 408.
  • the tools may be used to query one or more spatial layers and Unked datasets or view spatial and data attributes of one or more spatial layers or Unked datasets.
  • the search tool 404 enables a query for a search layer.
  • a corresponding input is used to search the selected spatial layer or layers and the Unked dataset or datasets.
  • the input is entered via a user interface.
  • the filter tool 406 enables a query for a filter layer.
  • a corresponding input is used to search the selected spatial layer or layers and the Unked dataset or datasets.
  • the input is entered via a user interface.
  • the view tool 408 enables viewing an item selected from the viewed tool.
  • the selected item is viewed via a user interface.
  • One or more outputs are generated if a match between an input and one or more spatial layers and one or more Unked datasets is identified for a query. If a query match is identified for one or more spatial layers, the selected spatial layer features 412 resulting from the match are generated for display, such as in a map image. If a query match is identified for one or more datasets on which the query is performed, the selected dataset features 414 resulting from the match are generated for display, such as in a tabular Ust specifying each selected dataset feature and its corresponding data attributes.
  • each Unked feature reference can be selected to display a tabular list specifying the corresponding dataset feature and its data attributes.
  • the conesponding Unked documents 418 resulting from the match are generated for display, such as each with a linked document reference in a list.
  • each Unked document reference can be selected to display the corresponding document.
  • Figure 5 depicts an exemplary embodiment of Unked dataset definition process 502.
  • a spatial layer is selected at step 504.
  • a dataset having a natural relationship with the selected spatial layer, that is having one or more common data attributes, is selected at step 506.
  • a common data attribute is selected from the selected spatial layer at step 508.
  • the common data attribute is selected from the selected dataset at step 510.
  • the selected spatial layer data attribute is defined to the selected dataset data attribute in a configuration file or other configuration element at step 512.
  • Steps 508-512 may be repeated to define another common data attribute for the selected spatial layer and the selected dataset.
  • Steps 504-512 may be repeated to define a common data attribute for another spatial layer and/or another dataset.
  • SQL-type statements are used to describe a query that spans the spatial layers and the Unked datasets.
  • the query is used to match an input for a search or filter to the spatial layer(s) and the linked dataset(s).
  • SQL-type statements describe multiple transactions used to query the spatial layer(s) and the Unked dataset(s).
  • the statements use extensible markup language (XML) to describe how to select data fields for the query.
  • the statements include a selection clause to identify elements that are wanted, a from clause to identify from what spatial layer(s) and/or dataset(s) the data is to be queried, a where clause to identify what criteria is used to select data, an order clause to identify the order used to present data that matches the query, and a group clause to identify how common/like data is to be grouped, such as by rows.
  • the statements are presented with database/data system neutral definitions and vendor neutral definitions.
  • Figure 6 illustrates an exemplary embodiment of a user interface used to enter search criteria, select tools for searches, and generate spatial data and feature data for display.
  • the user interface may be used to configure tools, define Unked datasets, and perform other operations.
  • the user interface 402 has a map browser 604.
  • the map browser 604 in the example of Figure 6 includes a map frame 606, a command bar 608, a thumbnail map 610, a map legend 612, and a zoom scale 614.
  • the map browser 604 includes the map frame 606.
  • the map browser 604 includes the map frame 606 and a combination of one or more of the command bar 608, thumbnail map 610, map legend 612, and zoom scale 614.
  • the map frame 606 displays a map image.
  • the map image may include spatial data and/or other data, such as dataset data.
  • One or more points may be selected within the map frame 606 to cause generation of additional map displays or generation of feature data.
  • the map frame 606 provides image display capabilities for a map image, such as pan and zoom, based on input commands from an input device, such as a mouse or pointer.
  • the command bar 608 includes function buttons that control the behavior of the map image display generated to the map frame 606 and what other subcomponents of the map browser 604 are available.
  • the command bar 608 includes buttons for turning the legend on and off, turning the overview map on and off, changing the unit of measurement for representing distance between miles and kilometers, and measuring distance on the map image display by selecting a point on a map and moving to another point on the map so that the distance measurement tool generates a straight Une distance representation.
  • the command bar 608 in this embodiment also includes a refresh button, a center map button to center the map where selected, a pan button, a zoom in button, a zoom out button, and a lasso button.
  • the lasso button enables a user to draw a square or other shape or designation around an area to select feature data within that area for the selected spatial layers.
  • the Unked datasets conesponding to the selected area also are used to provide the feature data.
  • the thumbnail/overview map 610 displays a smaUer version of the map image display zoomed out so that the user can visuaUy identify the approximate location of the map image display relative to other spatial features.
  • the overview map 610 displays a map area of a selected state relative to several surrounding states.
  • the map legend 612 identifies the spatial layers that currently are visible on the map image display.
  • the map legend 612 also may depict colors or other feature designations for selected layers or features.
  • the zoom scale 614 enables a user to zoom the map image display area in or out relative to the cunent map image display area.
  • the current relative zoom level may be indicated by a square or dot on the zoom scale or in another manner. The user may select a location on the zoom scale to zoom in or out.
  • the user interface 602 also includes a tools frame 616.
  • the tools frame 616 includes a search tool 618 to enable input for a query for a search layer, a filter tool 620 to enable an input for a query for a filter layer, and a view tool 622 to view an item selected from the viewed tool.
  • the tools frame 616 also may include a tools tab 624 and a layers tab 626 to enable toggUng between selections of tools and layers.
  • the tool input frame 628 enables a user to input query data.
  • the query data may be performed on attribute data for a spatial layer and/or a linked dataset.
  • the spatial layer may include, for example, an address, a county, a city, a state, or another spatial identification.
  • the attribute data for the query may include a value for population, income, lease identification, weU identification, statistical selection data, or other data appUcable to the appUcation in which the tool input frame 628 is located.
  • the user interface 602 also includes a feature display frame 630 in which the feature data is provided. Data may be displayed in the feature display frame 630 as tabular attribute information from layer features, including text data, image data, or other data.
  • the feature display frame 630 may include selected features data 632, Unked features data 634, and Unked documents 636.
  • the selected features display the attribute data from the selected features.
  • the Unked features 634 display the attribute data for Unked features of Unked datasets.
  • the linked documents 636 enables selection of documents, including word processing documents, spreadsheet documents, images, hypertext markup language (HTML) documents, PDF documents, and other documents.
  • the exemplary screen views of Figures 7-30 depict a user-level user interface for an application used to select population related data for a state and spatial/geographic entities within the state, including counties, cities, urban areas, addresses, and other spatial/geographic entities. Also included is an example of an application for identifying spatial/geographic data and dataset data for gas weUs.
  • the spatial/geographic data includes location, county, and other spatial data.
  • the dataset data in this example includes weU name, well number, lease number, lease identification (ID), operator, status, formation, and other data.
  • the screen views of Figures 31-55 depict embodiments of an administration assistant interface.
  • Figure 7 depicts an example of a screen generated for display to a user for a population statistics appUcation.
  • the population statistics appUcation provides Unked data set data to the user.
  • the spatial data portal user screen 702 includes a map frame 704 in which a map browser is generated.
  • the map browser may include the map image display and, optionaUy, a command bar, a thumbnail map, a map button, and a zoom scale.
  • the user screen 702 also includes a tools frame 706 that enables a user to select one or more search tools 708, filter tools 710, and/or view tools 712.
  • a tool input frame 714 also is provided.
  • the tool input frame is coUapsed.
  • the user screen 702 also includes a feature display frame 716.
  • the feature display frame 716 displays, and enables selection of, selected features 718, linked features 720, and Unked documents 722.
  • Figure 8 depicts an exemplary embodiment of a screen in which an address search tool 802 and a conesponding address input tool 804 are used to query the spatiaUy Unked datasets.
  • the address tool 802 enables the user to locate a street address, a cross-street address, or a sub-portion of a street address, such as state, city, or zip code.
  • the state portion of the address was entered, resulting in a map image display 806 that depicts the state entered in the address tool input 804.
  • the map frame also includes a command bar 808, an overview map 810, a map legend 812, and a zoom scale 814.
  • Figure 9 depicts a screen display in which a list of values (LOV) tool is used.
  • the LOV tool in this example is a county tool 902.
  • LOV tools enable a user to select a feature from a Ust of features associated with a given spatial layer.
  • LOV tools are appUed to a unique field of a spatial layer or a data layer, enabUng a user to select at least one feature contained within the layer.
  • selection of the county tool 902 results in a conesponding county tool input 904 displayed to the user.
  • the user may select a county from a drop down Ust in this example.
  • the county tool has been applied to a name field of a county layer to enable the user to select a county by its county name.
  • other fields of other layers may be used.
  • the map image display 906 depicts a reduced map area that more fully depicts the selected spatial attributes, which in this case is the selected county.
  • the overview map 908 also changes to depict more closely the selected spatial element and the surrounding spatial elements.
  • the map legend 910 also is modified to depict map legends for conesponding spatial features.
  • Figure 10 depicts an example of a screen in which a city tool 1002 is selected to apply a search to a cities spatial layer.
  • a conesponding city tool input 1004 is provided for entry of a city.
  • an LOV tool input is provided for selection of a city from a drop-down Ust.
  • the city of Ada is selected, causing the spatial element of Ada and sunounding spatial features to be generated for the map image display 1006.
  • Figure 11 depicts a screen in which a query type search tool is selected.
  • the query tool in the example of Figure 11 enables a user to locate a county by name 1102.
  • a query tool enables a user to query spatial features from a selected layer.
  • the criteria for locating spatial features are provided to the user in the query tool input 1104.
  • the spatial data portal application will use the query input to query attributes of the associated spatial layer and/or data attributes of a Unked data set that may be associated with the designated spatial layer.
  • a query using the query search tool results in the map area of the map image display to include the minimum area that incorporates all features that are selected by the query operation.
  • an "S" with a wildcard, designated with an asterisk is provided as the query input for a counties layer.
  • the features located by the query 1106 are depicted with the same color or shade as selected for the filter display color 1108.
  • the query tool results return a coUection of data set attributes 1110 that are derived from the Unked datasets.
  • the data set attributes are displayed in tabular form within the selected features tab 1112 of the feature display frame.
  • the data attributes of Figure 11 include name, FIPS code, population 1990, population 1997, households, males, females, Caucasian, African American, Native American, Asian Pacific Islander, and other data attributes.
  • the data attributes are populated for the specific selected features, which include Stephens county, Seminole county, and Sequoyah county in Figure 11.
  • Figure 12 depicts an example of another search for the counties layer search tool.
  • the input for the query tool input has been modified to provide a more specific query.
  • the resulting features and resulting data set attributes are narrowed by the query to depict data for Seminole county and Sequoyah county.
  • Figure 13 depicts a query tool for locating cities by population 1302 and a conesponding query tool input 1304 for locating a city by a population.
  • the inputs required for the locate cities by population tool 1302 are defined as part of the appUcation. In this example, a minimum population value is used as the input.
  • Features that match the search criteria are highlighted on the map image display. In this example, aU cities with 1990 populations greater than or equal to 45000 are highUghted.
  • AdditionaUy the data set attributes that result from the query can be displayed. The information displayed corresponds to the data for the data set attributes associated with the features located by the search.
  • Figure 14 depicts a screen in which a query type search tool is used to locate counties with population projections that exceed a specified timit. The counties layer has been spatiaUy Unked to a data set that contains projected population statistics by county and decade.
  • a potential for more than one row of attribute data per county may exist.
  • a state name and a 2005 projected population is entered for the query input tool 1404 corresponding to the counties by population projections tool 1402.
  • Multiple features are identified in the map image display 1406, and multiple rows of attribute data corresponding to the selected features is identified in the feature display frame 1408.
  • Figure 15 depicts an example of the effect of changing a default input to the counties by population projections tool 1402.
  • An input is added to the county name field of the query tool input 1404 resulting in a nanowed match with features in the counties layer.
  • the map image display 1406 depicts the selected feature more fully.
  • the attribute data is displayed in the feature display frame 1408, and the attribute data is nanowed by the search.
  • Figure 16 depicts a screen using a spatial filter.
  • a filter query is similar to a search query.
  • a filter query can be configured to output a different set of data set attributes than a search query.
  • the filter tool does not alter the map display area when the search is completed so that the map display area does not zoom in or out.
  • the filter tool query results in altering the map display area so that the map display area identifies more closely the features that match the filter query.
  • the spatial filter when appUed, remains in effect until removed. In stiU another embodiment, the spatial filter remains in effect only for a single filter query.
  • the features within the map display area that match the filter's search criteria are highlighted or otherwise designated, such as by placing a shape around the matching features.
  • Spatial filters, Uke spatial searches, can incorporate Unked datasets into the filter's query, thus aUowing disparate Unked datasets to affect the results of the filter query.
  • the filter for the display cities by minimum population 1602 is selected.
  • a minimum population of 45000 is entered for the tool input frame 1604.
  • the features that match the spatial filter query are depicted in the map image display 1606.
  • AdditionaUy the data set attributes that match the selected features are depicted in the feature display frame 1608.
  • the results of the spatial filter query depict different attribute data than was depicted by the locate cities by population spatial search query.
  • the outputs of the spatial search queries and the spatial filter queries are configurable and may show different features and/or data set attributes.
  • Figure 17 depicts an example of a rubber-band zoom.
  • a user selected an area around four cities that are highUghted. This selection is depicted by the square sunounding these selected cities.
  • Figure 18 depicts an example of the results of the rubber-band zoom of Figure 17.
  • the map display area 1802 is reduced relative to the area shown in the previous screen to more closely identify the selected features.
  • the data set attributes that result from the filter operation are altered to include the matching features within the cunent map display area 1802.
  • Figure 19 depicts another example of a spatial fUter query.
  • the spatial filter for display counties by minimum jobless rate 1902 results in a conesponding tool query input 1904 for minimum unemployment rate.
  • the spatial filter for display counties by minimum jobless rate 1902 uses the unemployment rate data attribute from a linked data set to restrict the set of features included in the filter results.
  • the selected features included in the filter results are depicted in the map image display 1906.
  • Conesponding data attributes are depicted in the feature display frame 1908. It wiU be appreciated that features can be depicted using feature designations other than a filter display color, including crosshatching or other patterns, outlining, and other feature designations.
  • Figure 20 depicts another spatial filter for household poverty levels 2002.
  • the query tool input 2004 enables entry of a minimum percentage of households below a poverty level. Effecting the query search causes the matched features to be depicted in the image display area 2006. Corresponding data set attributes are depicted in the feature display frame 2008.
  • Figure 21 depicts an example of features in the map display area 2102 being enabled as hot spots.
  • a hot spot is a selectable area on an image display area. Selecting the hot spot results in attribute data and Unked information being presented in the feature display frame 2104.
  • the Atoka County was selected from the map image display 2102. Because the county layer was enabled for hot spots, the data set attributes for the counties layer are displayed. AdditionaUy, the datasets that are linked to the counties layer are displayed.
  • Figure 22 depicts a screen in which the 2000 poverty statistics by county linked feature from Figure 21 was selected.
  • the spatiaUy Unked data set's attributes are displayed in tabular form in the Unked features tab.
  • Figure 23 depicts a selection of another Unked data set from the feature results of Figure 21.
  • the population projections by county Unked data set were selected, and the data set's attributes are shown in the Unked features tab.
  • Figure 24 depicts a selection of another Unked data set from Figure 21.
  • the linked data set for 2000 jobless statistics was selected, and the data set's attributes are displayed in the Unked features tab.
  • Figure 25 depicts an example of both Unked datasets and Unked documents.
  • selection of Seminole County causes the filter query results to be presented for the matching data set attributes, the Unked datasets, and the linked documents.
  • Figure 26 depicts an example in which a Unked document was selected from the filter query results of Figure 25.
  • the sales tax rates for selected cities document was selected causing the document to be displayed in the linked documents tab.
  • Figure 27 depicts an example in which multiple different types of documents are supported as Unked documents.
  • a PDF document is provided as a Unked document.
  • Other document types including spreadsheets, word processing documents, HTML documents, CSV files, and other document types are supported.
  • Figure 28 depicts an example in which a PDF document is selected.
  • the PDF document is displayed in the Unked documents tab.
  • Figure 29 depicts an embodiment of a layers tab configuration.
  • the layer configuration may be different for each appUcation.
  • the layer configuration includes layer groups 2902, layers 2904, and layer properties 2906.
  • the layer groups 2902 are configured groupings of layers.
  • a layer 2904 may be selected to enable the layer, if disabled, or disable the layer, if enabled.
  • the layer properties 2906 may be selected to enable the layer property, if disabled, and to disable the layer property, if enabled.
  • Figure 30 depicts another application in which disparate datasets are spatiaUy linked.
  • the example of Figure 30 depicts an appUcation for oil and gas weUs.
  • the tools 3002 include spatial search tools and spatial filter tools for identifying oil and/or gas weUs.
  • the query tool input 3004 depicts an example of multiple inputs that can be entered for a filter weUs by depth filter.
  • the results of the filter query are depicted in the map image display 3006 with the matching features identified by a selected color. It wiU be appreciated that feature designations other than a specific color may be used.
  • the data attributes matching the selected features are depicted in the selected features tab of the feature display frame 3008.
  • Linked datasets and linked documents also may be provided. In the example of Figure 30, the first fifty records are returned, and the next group of records may be selected by selecting the Next button.
  • Figures 31-55 depict an exemplary embodiment of an administration assistant used for creating spatial tools and user interfaces and for further defining linked datasets and features.
  • the examples of Figures 31-55 depict an administration assistant 3102 for an oU and gas application.
  • the administration assistant 3102 may be used for other applications, including a population statistics appUcation and other appUcations in which disparate datasets are spatiaUy linked using a spatial layer.
  • the administration assistant 3102 is used to create pubUc tools identified in the tool selection frame 3104, including spatial search tools, spatial filter tools, and spatial view tools. After a tool is created, a tool may be selected, and the tool's input is presented in a tool prototype input frame 3106. Tools that are being created or edited are presented in a tool configuration frame 3108.
  • the administration assistant 3102 has command buttons that enable a user to create, modify, or delete tools.
  • a new tool button 3110 enables a user to create a new tool.
  • An import tool definitions button 3112 enables a user to import tool definitions from other sources into the cunent tool definitions.
  • An export tool definitions button 3114 enables a user to export one or more tool definitions from a current tool definition to another source, such as to an XML file.
  • An edit tool button 3116 enables a user to modify an existing tool.
  • a delete tool button 3118 enables a user to delete a currently designed tool. In one embodiment, if a tool is pubUshed, the tool must be unpubtished/revoked before it can be deleted.
  • a published/revoked tool button 3120 enables a user to pubUsh a tool for general use or to revoke a pubUshed tool from general use.
  • Figure 32 depicts an example of different tool types and how the tool types are selected to create a new tool or to modify an existing tool.
  • the type of tool may be selected from a tool type drop-down Ust 3202 in the example of Figure 32.
  • the defined tool types then may be depicted in the tool selection frame 3104, including a search tool Ust, a filter tool Ust, and a view tool Ust.
  • Figure 33 depicts a screen in which a search tool type is defined for a search tool using a search tool type drop-down Ust 3302.
  • the search tool type drop-down Ust 3302 enables a user to select the type of search tool to be created.
  • search types include custom, Ust of values (LOVs), and address.
  • Custom search tools enable a user to create a spatial query that can incorporate data from spatial layers and disparate datasets. LOVs produce a drop-down Ust of values from a data field of a spatial layer.
  • Address search tools enable a user to locate a geographic point based on entry of an address or a partial address.
  • Figure 34 depicts a screen that enables a user to define a source layer for an LOV tool.
  • a user may select a source layer from a drop- down Ust for selection of the layer that wiU be used as the source of data for the LOV tool.
  • Figure 35 depicts a screen that enables a user to select the data field to be used for display for the LOV tool and the data field to be used as a key value for a search.
  • the drop-down lists include aU of the fields of the previously chosen layer. The dropdown lists are used to select the data field to display to the user in the LOV Ust and the data field to be used when querying the spatial layer for a query match.
  • Figure 36 depicts a screen that enables a user to provide a title and a description of the tool. Instructions for the tool's use also can be provided in a description field.
  • Figure 37 depicts an exemplary screen used to confirm that the new tool has been created. Selecting the OK button completes creation of the tool.
  • Figure 38 depicts a screen used to display a summary of a tool's attributes.
  • the summary screen typicaUy is displayed after creation of a tool or when a tool is chosen from the tool selection frame 3104.
  • the tool is grouped by its main tool type, such as search, filter, or view. Selecting a tool from the tool selection menu causes the tools inputs to be presented in the tool prototype input frame 3106. Once the tool is selected, the tool can be tested by entering an input and pressing the search button.
  • Figure 39 depicts an exemplary screen used to define a "custom" search tool or a "custom” filter tool drop-down Ust 3902, which enables a user to select the type of input field that wiU be used to gather the input from the user.
  • the tool input type drop-down Ust may be either a text field or an LOV.
  • the query source 3904 enables a user to select the source of the field that wiU be compared to the input value.
  • the query field is designated in the query field Ust 3906. Sources can be the tool's associated spatial layer or a Unked data set.
  • a query comparison type selector 3908 enables a user to select a type of comparison that wiU be made between the input value and the selected source field.
  • a default value field 3910 enables a user to specify a default input field.
  • Figure 40 depicts a screen that enables a user to title individual tool inputs.
  • a prompt or label may be provided.
  • Figure 41 depicts a screen that enables a user to refine definitions of linkages between a spatial layer and a dataset.
  • a query joins wizard aUows the user to join data fields within the tool's associated spatial layer with those of a Unked dataset during the query operation to provide a custom tinkage between a spatial layer and the dataset.
  • This wizard can also be used to compare a spatial layer field or dataset column to a Uteral value.
  • a user selects a layer and a field or a dataset and a dataset field, such as a business table column, for the left hand side of the comparison. The user then selects a comparison operator.
  • a dataset and dataset field or spatial layer and field are selected for the right hand side of the query "where clause" like component.
  • Figure 42 depicts a screen that enables a user to select data attributes from a selected spatial layer or dataset.
  • the data attributes are displayed to the user when the tool is executed.
  • the available fields initiaUy include aU of the data attributes from the tool's associated spatial layer and any datasets that have been Unked (joined) as part of the query operation. As data attributes are chosen for display, they are added to the fields to display box.
  • Figure 43 depicts a screen that enables a user to change titles, assign display formats, and change the display order associated with the data attributes that have been chosen for display. If the data attribute must be displayed in a format other than its native form, the user can enter a display format specification in the format field to alter the formatting of the field. For example, the format field might be used to enter a date format to alter the display format of the date value.
  • Figure 44 depicts a screen that enables a user to assign a color to the features selected during execution of the tool.
  • Figure 45 depicts a screen that enables a user to set the initial map area that will be considered during the execution of the tool.
  • Figure 46 depicts a screen that enables a user to establish a title for the tool and to provide instmctions for the tool's use.
  • Figure 47 depicts a screen in which a tool is being deleted.
  • Figure 48 depicts a screen depicts the initial display of a document Unking wizard when the "Document Links" tab is selected in the administrative assistant.
  • Users can manage and view existing Unked documents from the Layer Centric or Document Centric tabs. These tabs aUow the user to access Unked documents from a spatial layer perspective or from a document perspective.
  • the layer centric view aUow s the user to navigate through a treed menu of layers and features to the documents that have been Unked.
  • the document centric view aUows a user to navigate a treed menu of documents to the features and layers to which the documents have been linked. New documents can be linked by pressing this New Link button.
  • Figure 49 depicts a screen that enables a user to select the feature to which the document or documents wiU be Unked.
  • Figure 50 depicts a screen with a second step for Unking a document. Once a feature has been selected, the feature identifier wUl be shown on this screen. The user can select the feature identifier text to display a pop-up dialog displaying the selected features data attributes.
  • Figure 51 depicts a screen that enables a user to specify one or more files to be uploaded and linked to the previously selected spatial feature (Figure 50). Files specified via this page will be uploaded from the user's (cUent side) system to the spatial processing system 104.
  • Figure 52 depicts a screen that enables a user to specify one or more remote files to be Unked to the previously selected spatial feature (Figure 50). In this example, URLs are entered.
  • Figure 53 depicts a screen that enables a user to specify one or more documents (that have already been Unked to other features) to be Unked to the selected spatial feature.
  • the user may use either the layer centric or document centric trees to navigate to a document that has previously been Unked to a feature other than the feature cunently selected.
  • Figure 54 depicts a screen that displays a selected document and its associated data attributes. The user also can use this screen to alter the document Unk title or delete the documents Unk. A document Unk can be deleted by pressing the "Delete
  • This File was uploaded (not Unked via
  • Figure 55 depicts a screen with a Document Centric document navigation tree.
  • the "Document Centric" tab is selected to view document tinks from a document centric vantage point.
  • documents have associated layers and features as is iUustrated in this expanded document node, showing the layer (WeUs) and the feature ("14567-2315") to which this document is Unked.

Abstract

L'invention concerne un système et un procédé de liaison d'un ou plusieurs ensembles de données disparates (306) à une ou plusieurs couches spatiales pour créer des ensembles de données liés (Figure 3). Un ou plusieurs attributs de données communs à l'ensemble de données et la couche spatiale (302) sont identifiés, et la liaison est définie entre l'ensemble de données et la couche spatiale. La couche spatiale et l'ensemble de données lié (312) peuvent être ensuite demandés par une seule demande d'entrée. Les caractéristiques de la couche spatiale et celles de l'ensemble de données lié qui correspondent à la demande sont générées pour affichage.
PCT/US2003/015303 2002-05-15 2003-05-15 Portail de donnees spatiales WO2003098482A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2003241459A AU2003241459A1 (en) 2002-05-15 2003-05-15 Spatial data portal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US38104502P 2002-05-15 2002-05-15
US60/381,045 2002-05-15

Publications (1)

Publication Number Publication Date
WO2003098482A1 true WO2003098482A1 (fr) 2003-11-27

Family

ID=29550058

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2003/015303 WO2003098482A1 (fr) 2002-05-15 2003-05-15 Portail de donnees spatiales

Country Status (2)

Country Link
AU (1) AU2003241459A1 (fr)
WO (1) WO2003098482A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5032989A (en) * 1986-03-19 1991-07-16 Realpro, Ltd. Real estate search and location system and method
US5897619A (en) * 1994-11-07 1999-04-27 Agriperil Software Inc. Farm management system
US6278994B1 (en) * 1997-07-10 2001-08-21 International Business Machines Corporation Fully integrated architecture for user-defined search
US6282547B1 (en) * 1998-08-25 2001-08-28 Informix Software, Inc. Hyperlinked relational database visualization system
US20020091758A1 (en) * 2001-01-05 2002-07-11 Singh Raj R. Map viewing, publishing, and provisioning system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5032989A (en) * 1986-03-19 1991-07-16 Realpro, Ltd. Real estate search and location system and method
US5897619A (en) * 1994-11-07 1999-04-27 Agriperil Software Inc. Farm management system
US6278994B1 (en) * 1997-07-10 2001-08-21 International Business Machines Corporation Fully integrated architecture for user-defined search
US6282547B1 (en) * 1998-08-25 2001-08-28 Informix Software, Inc. Hyperlinked relational database visualization system
US20020091758A1 (en) * 2001-01-05 2002-07-11 Singh Raj R. Map viewing, publishing, and provisioning system

Also Published As

Publication number Publication date
AU2003241459A1 (en) 2003-12-02

Similar Documents

Publication Publication Date Title
US8224867B2 (en) Spatial data portal
US7599909B2 (en) System and method for transforming and using content in other systems
US8468444B2 (en) Hyper related OLAP
US6199059B1 (en) System and method for classifying and retrieving information with virtual object hierarchy
US7509591B1 (en) Generation engine for a treemap display
US7716172B2 (en) Method of splitting a multi-dimensional cube between a multi-dimensional and a relational database
US6424980B1 (en) Integrated retrieval scheme for retrieving semi-structured documents
US6732102B1 (en) Automated data extraction and reformatting
US7428705B2 (en) Web map tool
CN101882149B (zh) 重排序和提高搜索结果的相关性
CA2669479C (fr) Creation de presentations utilisateurs finals a partir de donnees structurees
US7539693B2 (en) Spatially directed crawling of documents
US6604108B1 (en) Information mart system and information mart browser
CN101622619B (zh) 用于导航和可视化关系数据库和/或多维数据库中的数据的方法和系统
US7404142B1 (en) Systems and method for rapid presentation of structured digital content items
WO2006060773A2 (fr) Systemes informatiques et procedes pour la visualisation de donnees avec generation de reperes
WO2005024663A1 (fr) Procede permettant des affichages arborescents de donnees
US7080086B2 (en) Interaction with query data
EP1577808A1 (fr) Traitement analytique en Ligne Hyper Relié.
WO2003098482A1 (fr) Portail de donnees spatiales
US20220156253A1 (en) Compact display of matching results
KR100343524B1 (ko) 통계데이터 분석방법
Kropla Using Query Mode
Sifer Exploring Web logs with coordinated OLAP dimension hierarchies
WO2002089005A2 (fr) Procede et systeme de recherche automatique des donnees

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NI NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP