WO2011133998A1

WO2011133998A1 - System and method for public works planning

Info

Publication number: WO2011133998A1
Application number: PCT/AU2010/000505
Authority: WO
Inventors: John Florian Csorgo; Geoffrey Lee Rawling; Stephen Anthony Webb; David Patrick Norris; Timothy James Wrathall
Original assignee: South East Water Limited
Priority date: 2010-04-30
Filing date: 2010-04-30
Publication date: 2011-11-03

Abstract

Some embodiments relate to a system for public works planning, comprising: processor-readable storage storing executable program code, the program code including server code for serving page code to a client device, the page code being executable by a browser application to: display geographic imagery of a selected geographic area, display at least one works image overlaid on the geographic imagery indicative of, and geographically corresponding to, a completed, current or planned works project in one or more geographic positions within the geographic area, and selectively display a works project editing tool overlaid on a portion of the geographic imagery to enable user creation and modification of works information for a works project, the works information enabling generation of the at least one works image; at least one processor having access to the processor-readable storage to execute the program code.

Description

SYSTEM AND METHOD FOR PUBLIC WORKS PLANNING TECHNICAL FIELD

Described embodiments relate generally to systems and methods for use in public works planning. In particular, embodiments facilitate the display of works images in relation to a geographical area and allow information to be obtained in relation to a works project that corresponds to the works image.

BACKGROUND

Many different organizations may be involved in various different kinds of public works projects within a certain geographic area. The public works can be related to transport infrastructure, water management infrastructure, power supply and other utilities and provision of telecommunication infrastructure. Where there are multiple works planned or currently running in a certain area, it can be problematic to coordinate performance of these works, particularly where they are carried out by different entities or organizations. Interference of works projects can cause delays, complicate the works logistics and increase the costs of works.

It is desired to address or ameliorate one or more shortcomings or disadvantages of existing public works planning methods or systems, or to at least provide a useful alternative thereto.

SUMMARY Some embodiments relate to a system for public works planning, which may comprise: processor-readable storage storing executable program code, the program code including server code for serving page code to a client device, the page code being executable by a browser application to:

display geographic imagery of a selected geographic area, display at least one works image overlaid on the geographic imagery indicative of, and geographically corresponding to, a completed, current or planned works project in one or more geographic positions within the geographic area, and selectively display a works project editing tool overlaid on a portion of the geographic imagery to enable user creation and modification of works information for a works project, the works information enabling generation of the at least one works image;

at least one processor having access to the processor-readable storage to execute the program code.

The program code may further comprise server code for serving page code to the client device to enable selective display of an image layer selection tool overlaid on a portion of the geographic imagery to enable user selection of different image layers to be displayed, each image layer displaying works images corresponding to different types of works.

The page code may comprise code for displaying a tag including a works type descriptor and an owner descriptor, the tag being displayed adjacent each works image overlaid on the geographic imagery in response to selection of an option displayed on the image layer selection tool adjacent a respective selectable image layer display control. The page code may further comprise code for causing the browser application to automatically display a works project information window adjacent a works image in response to user input to focus on the works image and to automatically hide the information window in response to user input no longer focusing on the works image. The page code may further comprise code for selectively displaying second geographic imagery overlaid on a portion of the first geographic imagery, the second geographic imagery being of smaller scale than the first geographic imagery and showing geographic areas surrounding the selected geographic area.

The page code may further comprise code for displaying a navigation tool comprising selectable controls for changing the displayed geographic area, wherein the navigation tool comprises a tool bar comprising further selectable controls for controlling at least one of display functions and input functions. The navigation tool may comprise a text- based search input component to receive text-based search input in relation to a geographic area to be displayed. The page code may further comprise code for displaying a user controls tool to enable a user of the browser application to selectively control a plurality of control overlays to be displayed over the parts of the geographic imagery. The control overlays may include the works project editing tool and an image layer selection tool. The program code may further comprise a works conflict management component to determine a possible conflict by determining whether the works project geographically and temporally overlaps with, or is within a proximity threshold of, another works project.

The works conflict management component may further determine the possible works conflict during user creation of a new works project or user modification of stored works project and to cause an alert notification of the possible works conflict to be displayed by the browser application when the possible works conflict is determined.

The works conflict management component may further cause a works conflict image to be displayed over the geographic imagery by the browser when the possible works conflict is determined, the works conflict image depicting an area of spatial overlap or proximity of works images of the two or more potentially conflicting works projects.

The works conflict management component may further cause the browser to display a works image of a possibly conflicting stored works project in response to the user creation or modification. The display of the works image of the possibly conflicting stored works project may be caused to occur on-the-fly during the user creation or modification. The display of the works image of the possibly conflicting stored works project may be caused to occur less immediately than on-the-fly but prior to a works project record of the new or modified works project being stored in a database along with other works project records. The code to display the works project editing tool may comprise code to allow user manipulation of the editing tool to graphically define a spatial extent of a new or modified works project in relation to the displayed geographic imagery. The code to display the works project editing tool may comprise code to allow user manipulation of the editing tool to specify a display layer of the new or modified works project. The works project editing tool may allow user manipulation to define one or more graphical works images for a works project, the one or more works images comprising at least one of a polygon object, a line object and a point object. Definition of the polygon object of the system by the user may comprise selection of a location of a plurality of vertices of the polygon and allowing each of these vertices to be re-positioned. Definition of the polygon object by the user may comprise allowing a mid-point of each line extending between neighboring vertices to be re-positioned, thereby creating a new vertex from the mid-point and two new lines extending to the neighboring vertices.

The works project information window may comprise, for users having authorization to edit the works project to which the information window relates, a selectable option to edit the works information for the works project. Selection of the selectable option to edit may cause display of the works project editing tool when it is not already displayed.

The page code may further comprise code to display tools and image overlays over the geographic imagery as being at least partially semi-transparent when not the subject of user input focus to thereby allow at least part of the underlying geographic imagery to be visible. The geographic imagery may be displayed to extend to the borders of the display area provided by the browser application.

Some embodiments relate to a computerized system for public works planning, which may comprise:

computerized interface means in communication with a network to display images and works information for a plurality of works projects, the images comprising at least one works image overlaid on geographic imagery of a selected geographic area, wherein the at least one works image is indicative of, and geographically corresponds to, a works project in one or more geographic positions in the geographic area;

a works project editing tool provided via the interface means and selectively overlaid on a portion of the geographic imagery to enable user creation and modification of works information for a works project, the works information enabling generation of the at least one works image; and

a data store responsive to the interface means to store and retrieve the works information. The works conflict management component which may determine whether the works project geographically and temporally overlaps or is proximate with another works project and to interact with the computerized interface to provide an indication of any determined overlaps or proximities. Some embodiments relate to a computer-implemented method for public works planning, which may comprise:

providing page code to a client computing device, the page code executable by a client browser application to provide a computerized user interface to display images of public works and to receive input in relation to the public works, the images including at least one works image overlaid on geographic imagery of a selected geographic area, wherein the at least one works image is indicative of, and geographically corresponds to, a works project in one or more geographic positions in the geographic area;

receiving via the user interface input to define a new works project, the input specifying at least a geographic extent of the new works project;

determining during the receiving whether the new works project geographically overlaps or is proximate to another works project; and

dynamically indicating a possible works planning conflict via the user interface in response to the receiving if it is determined that there is a geographic overlap or proximity of the new and another works projects. Some embodiments relate to methods used to implement the described systems. Some embodiments relate to computer-readable storage storing executable program instructions for performing the described methods or implementing the described systems.

BRIEF DESCRIPTION OF THE DRAWINGS Embodiments are described in further detail below, by way of example, with reference to the accompanying drawings. In the accompanying drawings:

Figure 1 is a block diagram of a computerized system for public works planning;

Figure 2 is a block diagram showing in further detail computer systems of the system of Figure 1;

Figure 3 is a block diagram of the system of Figure 1, showing a server system in further detail;

Figure 4 is an example interface display to be displayed at a client device;

Figure 5 is an example display of a navigation and function selection tool;

Figure 6 is an example display of a layer selection tool;

Figure 7 is an example information display for a stored works project;

Figure 8 is an example data input window for a works project;

Figures 9A and 9B are example displays showing works images overlaid on geographic images and illustrating layer section;

Figure 10 is an example display of an editing tool for creating and editing works project images and information;

Figure 11 is an example display of an area-type works project image in editing mode;

Figure 12 is an example display of a linear-type works project image in editing mode;

Figure 13 is an example display of a point-type works project image;

Figure 14 is an example display illustrating a works conflict;

Figure 15 is an example display illustrating another works conflict;

Figure 16 is an example display illustrating an image overlay alert;

Figure 17 is a flowchart of a computerized method for public works planning;

Figure 18 is a flowchart of a method of works project editing and conflict determination;

Figure 19 is a flowchart of a method of continuous works project conflict monitoring; Figure 20 is an example display of a comment window for receiving comment input in relation to a works project;

Figure 21 is a flowchart of a method of adding a user comment to a works project;

Figure 22 is a flowchart of a method of viewing comments received in relation to a works project;

Figure 23 is an example display of an alert subscription input window for a works project;

Figure 24 is a flowchart of a method of establishing an alert subscription for a non- registered user in relation to a works project;

Figure 25 is a flowchart of a method of establishing an alert subscription for a registered user in relation to a works project;

Figure 26 is a flowchart of a method of providing alerts to subscribed users in relation to a works project; Figure 27 is an example display of a geographic information bar forming part of the interface display according to some embodiments;

Figure 28 is an example interface display, illustrating an example location search result display portion;

Figure 29 is a flowchart of a method of ordering location search results;

Figure 30 is an example interface display of a works record import interface; and

Figure 31 is a flowchart of a method of importing works records from a different system.

DETAILED DESCRIPTION Described embodiments relate generally to systems and methods for use in public works planning. In particular, embodiments facilitate the display of works images in relation to a geographical area and allow information to be obtained in relation to a works project that corresponds to the works image.

Described embodiments generally operate in a client-server architecture. Although it is common to describe web pages as being displayed on a website that is hosted by a web server, the actual display occurs using a browser application on a client computing device that receives program code from the web server in response to a serve request for a web "page". The program code thus received by the client computing device is then executed by the browser application and applicable plug-ins, if possible, to display the requested web page and to usually provide selectable user interface elements. A user may thus effectively interact with the webpage by providing input at the client computing device that may be converted by the browser application into further requests to the server for data or code or may be handled at the client computing device by browser plug-ins or by applets and/or active code components served from the server. It is in this context that embodiments are further described.

As used in this application, the term "component" or "module" is intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component or module may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a server and the server can be a computer component or module. One or more components or modules may reside within a process and/or thread of execution and a component or module may be localized on one computer and/or distributed between two or more computers. A "thread" is the entity within a process that the operating system kernel schedules for execution. Each thread has an associated "context" which is the volatile data associated with the execution of the thread. A thread's context includes the contents of system registers and the virtual address belonging to the thread's process. Thus, the actual data comprising a thread's context varies as it executes. Referring generally to Figure 1, a system 100 for facilitating planning of works projects is described in further detail. Aspects of system 100 are also shown and described by way of example with reference to Figures 2 and 3. System 100 comprises a server system 110 and at least one client computing device 115 in communication with each other over a network 112. Network 112 may be a public network, such as the Internet, or it may be a private network, semi-private network or a combination of different network types.

System 100 further comprises a data storage system 162,166 accessible to server system 110 for storing data pertinent to operation of server system 110 and provision of service to client computing device 115. System 100 further comprises at least one third party server 140, for example providing geographic information system (GIS) data including map data and satellite imagery, and one or more web services providers 145 in communication with server system 110 and client computing device 115 over network 112.

Client computing device 115 may comprise a desktop, mobile or handheld computing device having at least one processor (e.g. CPU 206), one or more forms of memory 202, 204, an operating system 122 and a user interface. The memory may comprise volatile (e.g. RAM 204) and non-volatile (e.g. hard disk drive 202, solid state drive, Flash memory and/or optical disc) storage. The user interface may comprise a display 220 and at least one input device, such as a touch-screen, a keyboard 216, mouse 218, stylus, speech recognition subsystem or other peripheral device that can be used for providing user input to client computing device 120. A bus 214 communicatively couples CPU 206 with memory (e.g. RAM 204, HDD 202), display 220 (via display adapter 212), network 112 (via network interface card 210) and the input devices (via universal serial bus (USB) connection 208, for example). Server system 110 may comprise similar components and/or features. A number of software applications or applets may be executing or executable by the at least one processor 206 to perform various device-related functions. Such applications may be stored in the non- volatile memory 202 of computing device 115. At least one such software application includes a browser application 117 for enabling a user to navigate to sites accessible over the network 112 to receive content therefrom and render the content to display images on display 220. Other client software applications 118, such as plug-ins or applets, may execute on client system 115 using operating system 122.

In some particular embodiments, software applications 118 include a web application framework (for example, as a browser plug-in) to closely integrate graphics information, controls and interactivity into the runtime environment of client system 115. The web application framework may be arranged to closely integrate remotely sourced GIS data (e.g. from server 140) with geographic navigation and image rendering in combination with browser functions provided by client browser 117.

In the example of system 100 illustrated in Figure 1, client browser 117 can be used to communicate with server system 110 to request content therefrom, in the form of one or more web pages provided as program code executable by the browser application 117, possibly in conjunction with client applications 118.

The web application framework may provide a retained mode graphics system, with user interfaces declared in Extensible Application Markup Language (XAML) and programmed using a subset of the .NET framework, for example. The web application framework may provide the ability to dynamically load Extensible Markup Language (XML) content that can be manipulated through a Document Object Model (DOM) interface. One example of such a web application framework used in some embodiments is Microsoft™ Silverlight™, although some alternative embodiments may employ Adobe™ Flash™ instead. Use of such a web application framework enables a rich and dynamic user interface to be provided by browser application 117, which is advantageous for systems, such as system 100, relying on the dynamic display of geographic images, works information and user-manipulable tools to interact with such images and information. According to some embodiments, server system 110 is configured to provide to client device 115 browser-executable code to display at least one display of works-related information, and more likely many such displays, for consideration by a user (i.e. viewing web pages via browser application 117). Thus, server system 110 may support or act as a public works planning site. Figures 4 to 16, 20, 23, 27, 28 and 30 illustrate example works-related displays and user-interface tools displayable or executable by browser application 117 according to code received from server system 110.

Server system 110 may access geographic information via a GIS server 140 provided by a GIS service provider in order to incorporate accurate geographic information (i.e. maps, topographic satellite images or hybrid images) into the works-related displays. Alternatively, the web application framework, operating as a plug-in to browser application 1 17, may source the GIS data from GIS server 140 as a web service. The web application framework and server system 110 may also source data from other sources, including servers providing web services. The GIS server 140 may thus comprise a web server hosted by or on behalf of the GIS service provider and making available geographic information for presentation with other works-related information via web browser 117 (viewable by the user by accessing server system 110).

Server system 110 comprises at least one processing device 120, and may comprise multiple processing devices 120 operating in cooperation and/or parallel to operate web server functions 128 (e.g. using a hypertext transfer protocol daemon (HTTPD)), data processing functions and data storage and retrieval functions (e.g. using structured query language (SQL or SPARQL) support 132) in conjunction with data storage system 162,166. Server system 110 may also comprise scripting language support 131, such as Microsoft™ ASP, ASP.NET or PHP.

Data storage system 162,166 may comprise a database 162 to store user account and works-related information that is subject to change and that may be queried regularly. Database 162 may comprise a localised or distributed database storing data records for the various works projects, as well as user permissions for each works project.

Server system 110 may comprise or have access to suitable non- volatile data storage 166 and/or memory 121 separate to database 162 for storing executable program code to enable server system 110 to perform its functions, including those functions described herein. Such program code comprises an operating system 124 and a user interface module 152 (as one of a number of software modules 150) for managing display and editing functions in relation to the works-related information and to interact (i.e. receive code requests, serve code, etc.) with client browser application 117. Software modules 150 further comprise an administration module 154 to enable administrative control (and possibly data reporting) and a data security module 156 to govern user access and permissions. GIS server 140 may comprise a similar architecture and similar server- related functions to server system 110, except that it will not have access to data storage system 162,166. As shown in further detail in Figure 3, user interface module 152 comprises modules and components to facilitate user interaction with server system 110 via client computing device 115. Such components and modules include, for example, a display module 310, a conflict management module 320, a navigation component 330 and an editing component 340. Functions of the display module 310 include, by way of example and without limitation, generating browser executable code to be served to client computing device 115 and executed by browser application 117 (using the web application framework provided by one of the client applications 118) so as to provide navigable displays and user- interactive tools to a user of the client computing device 115. Display module 310 thus does not actually display anything at server system 110, but is instead responsible for serving appropriate code to client computing device 115 so that browser application 117 can render appropriate displays in response to serve requests received by the server system 110. For example, display module 310 serves code to generate dynamic displays and provide interactive tools (i.e. applets) as illustrated by way of example in Figures 4 to 16, 20, 23, 27, 28 and 30. For example, display module 310 is responsible for providing code to generate the entire display 400 illustrated in Figure 4, including display elements or components for displaying, and allowing dynamic user manipulation of, a geographic image 404, works images 405, a geographic information bar 406, a navigation and function selection tool 410, a layer selection tool 420, a works related information display window 430, an editing tool 440 and a geographic overview image 450. These display elements are described in further detail below.

Works images 405, navigation and function selection tool 410, layer selection tool 420, works related information display window 430, editing tool 440 and geographic overview image 450 are all displayed as selectable overlay images to be graphically overlaid on a part of any displayed geographic image, although works images 405 can only be displayed if they are located in the geographic area depicted by the displayed geographic image. Such overlay images are dynamically rendered to be semi- transparent or opaque in some instances (e.g. on mouse-over or otherwise), depending on user actions, in order to not obscure the underlying geographic image display. For example, the overlay images may be normally opaque on mouse-over, but made semi- transparent once the mouse-over condition ceases to apply, so that the underlying geographic image 404 may be at least partially visible when the user's apparent focus, as indicated by the mouse-controlled cursor location, is not on the overlay image. As shown in the example displays in Figures 4, 9A, 9B, 14, 15 and 16, for example, substantially the entire available display area (apart from geographic information bar 406) of the browser application 117 is occupied by the geographic imagery, with various tool and other image overlays displayed over that imagery under user control. Further, because of the desirability of displaying as much of the underlying geographic imagery as possible (in order that users have more information than less), the display of selectable overlay images such as the navigation and function selection tool 410 (e.g top left-hand corner), layer selection tool 420 (left-hand side), editing tool 440 (right-hand side) and geographic overview image 450 (top right-hand corner) are provided in non- centralised positions of the display area, but generally not obscuring the edges of the geographic imagery.

The described user interface features allow the user to readily control which tools or informational display components are made visible by interacting with one or more of the tools so that the user can readily optimise on-the-fly the level of information or tools displayed according to the user's preferences.

Display module 310 may access data storage system 162,166 as needed or data stored in memory 121 in order to determine what displays should be generated at client computing device 115 in response to received serve requests. For example, information may be displayed differently, depending on user permissions stored in data storage system 162,166, and filtered, interpreted and managed by data security module 156 whereby the same serve request received from different users may result in different display-related code being served to client computing device 115. Display module 310 may also embed service calls within the code served to client computing device 115, in order to populate appropriate fields or display portions with information or imagery retrieved from web services 145 or GIS server 140.

Conflict management module 320 is responsible for determining the existence of a possible works conflict, for example where two works projects putatively or actually temporally and geographically (i.e. spatially) overlap or are within a proximity threshold applicable to either works project. This involves a comparison of the temporal and geographic extent of any unsaved works project, as it is being created, or newly saved works project with the temporal and geographic extent of a previously stored works project. For newly saved works projects, if there is actual overlap or sufficient proximity, then conflict management module 320 creates a conflict record in database 162 and the conflict record is linked to each of the affected works project records. Additionally, conflict management module 320 sends a notification message to the owners of the affected works projects. If the new works project is in the process of being created and the (still in flux) boundaries of the new works project are determined (for example, as they are being drawn by use of a mouse or pointer and the editing tool 440, as described below) to cross into the area or proximity of an existing stored works project (or other stored overlay), then the conflict management module 320 communicates with the display module 310 to dynamically cause the boundaries of the existing works project (or other stored overlay) to be displayed. This allows the creator of the new works project to immediately learn of the potential conflict, even where there may be no actual spatial or temporal overlap between the new and existing projects. Conflict management module 320 interacts with display module 320 to provide an appropriate pop-up window display 1440, 1540 or 1640 to represent the potential conflict or geographic overlap, as illustrated by example in Figures 14, 15 and 16.

Navigation component 330 comprises the server side software to handle serve requests specifically related to navigation and function selection resulting from user interaction with navigation tool 410 or by other navigation-related use of user-input devices, such as clicking and dragging the displayed geographic image using a pointer or using a scrolling component on a touch pad or mouse. Navigation component 330 cooperates with display module 310 to provide appropriate imagery in response to the navigation or function selection serve requests and also handles the execution of location search queries based on text input received via the navigation tool 410 or layer selection tool 420. Editing component 340 is responsible for enabling creation and modification of works- projects by a user in cooperation with editing tool 440, which is described in further detail below. Editing component 340 is responsive to editing tool 440 to save works project information for a new or modified works projects, including populating appropriate fields and the relevant works project data record with the new or updated works information.

Editing component 340 also queries the database 162 responsive to dynamically received input from client computing device 1 15 during the creation of a new works image by a user using the editing tool 440, in order to determine whether the spatial extent of the new works image overlaps or is spatially proximate (within a configurable threshold distance) the geographic extent of an existing stored works project. If any such possible conflicting existing works projects are identified as the user progressively graphically indicates the geographic extent of the works project, then editing component 340 communicates with display module 310 and conflict management module 320 to cause the works image of the relevant one or more existing works projects to be displayed along with a pop-up notification of the possible conflict. Thus, the editing component 340 is a server-side component that cooperates with the editing tool 440 executing on client computing device 115 (according to editing tool applet code provided by server system 110).

The above system functions are described further below, with reference to the example displays of Figures 4 to 16, 20, 23, 27, 28 and 30 and with reference to the flow charts of Figures 17 to 19, 21, 22, 24, 26, 29 and 31. For ease of reference, the description will be based on the display and user interface features as experienced by the user at the client computing device 115, even though such displays and user interface features are controlled by code provided by server system 110. It will be understood that, where a user interface feature is described, this is supported by functionality of either or both of client device 115 and server system 110.

Figure 4 shows an example display 400 viewable by a user using browser application 117 and the web application framework 118. Although a login screen is not shown, display 400 may be viewable only by users who have successfully logged in, for example by providing an appropriate user name and password. Thus, appropriate home pages and/or login pages may be provided to enable a user to access a specific works related display, such as display 400.

Navigation and function selection tool 410 (described in further detail below with reference to Figure 5) generally serves as a main command tool and provides user controls to change the displayed geographic image 404, which may include a map, satellite imagery or hybrid map and satellite imagery, so that it is shown at a smaller or larger scale, latitudinally or longitudinally shifted or even changed to an entirely different location (for example, by entering a desired location into a text input field 552 (Figure 5)). Navigation and function selection tool 410 also enables the toggling on and off of the display of layer selection tool 420, editing tool 440 and overview image 450. Overview image 450 shares the same geographic centroid as the displayed geographic image 404 but is a zoomed-out view (i.e. at a smaller scale). The differences in scale between the geographic image 404 and the overview image 450 may be system- configured or user-configurable. Overview image 450 may be positioned in or toward a corner or edge of display 400 and is substantially smaller (and smaller in scale) than geographic image 404 so as to not obscure the main display of geographic image 404. In some embodiments, the positions of layer selection tool 420, editing tool 440 and overview image 450 are static, in that they appear in the same display position overlaid on the geographic image when they are caused to appear.

Optionally, a user controllable pointer may also be used to shift the displayed geographic location by, for example, clicking and dragging on a portion of geographic image 404.

Example works images 405, shown in this case as point-type works images, are displayed in an overlay on geographic image 404 to indicate the location of respective works projects. Depending on the layer or layers selected to be visible and the specific geographic area selected to be displayed, zero or more of possibly many different works images may be displayed, corresponding to different works projects. Upon user selection or mouse-over of a works image 405, the works image 405 toggles to a modified display form, such as a slightly enlarged form, a different colour or other image shift that emphasizes the image 405. After mouse-over is continued for a preset delay time, such as a second or so, works information display window 430 may be displayed nearby the works image 405 in order to provide readily viewable information as to the works location, status (e.g. planned, in progress or complete), the dates over which the works are to be (or have been) carried out and the owner of the works project. The owner of the works project may be the utility, council or other organization responsible for carrying out the works. The geographic information bar 406 (shown in more detail in Figure 27) may be positioned at an edge of the display, such as at the bottom right edge of display 400, and conveniently indicates a scale 2706 and zoom level 2704 (of say 1 to 20) of the currently displayed geographic image 404. The information bar 406 may also indicate the latitude and longitude 2702 of the position of the user controlled pointer, or optionally just an approximate latitude and longitude (or other coordinates) 2702 of the geographic image 404 being displayed. In some embodiments, such as are shown by display 2700 in Figure 27, the coordinate system can be selected by clicking on the information bar 406, and optionally, specific two-dimensional coordinates can be input into a pop-up input window 2710 to enable the display to be shifted precisely to a new geographic centroid. Navigation and function selection tool 410, layer selection tool 420 and editing tool 440 are described in further detail below, with reference to figures 5, 6 and 10, respectively.

Referring now to Figure 5, navigation and function selection tool 410 is shown and described in further detail. To be able to pan and zoom geographic image 404, panning and zoom functionality is provided by a panning button 510, with four selectable directional panning arrows 512 corresponding to north, east, south and west, and zoom in and zoom out buttons 521, 522.

Navigation and function selection tool 410 also has a function selection bar 520 and a search bar 550, which together may be represented as a continuous function bar as shown in Figure 5. In some embodiments, if a user selects a central part of panning button 510, the function selection bar 520, search bar 550 and zoom buttons 521, 522 may be caused to furl (be hidden) or unfurl (be visible) in toggling fashion. Function selection bar 520 has a plurality of toggle buttons to enable certain functions to be selected or tools to be activated. Function selection 520 bar includes, for example, a layer selection tool button 532, an editing tool selection button 534, a geographic image type toggle button 536, a geographic overview display button 538, a full screen mode toggle button 540 and a system help button 542. Thus, with the function selection tool 410 furled and the editing tool 440, geographic overview image 450 and layer selection tool 420 toggled off, the user can effectively hide all overlays apart from panning button 510, if desired, thereby maximizing the visible area of geographic image 404 and thus allowing a better appreciation for how one or more works projects may fit within a larger works scheme over a larger geographic area.

Selection of the layer selection tool button 532 invokes an applet to display an image of layer selection tool 420 over a portion of geographic image 404. The user can interact with the layer selection tool 420 in order to select different visual display layers corresponding to different types of works or other overlays (e.g. heritage, cultural or environmental) and having different statuses or temporal extents, as described in further detail with reference to Figure 6.

Selection of editing tool selection button 534 causes execution of an applet to provide a display of editing tool 440 over a portion of the geographic image 404, for example toward, but not against, a right side edge of the geographic image 404. The operation of editing tool 440 is described in further detail below with reference to Figures 10, 11 and 12.

Geographic image type toggle button 536 toggles the display type of geographic image 404 between: map; satellite image; and a hybrid of map and satellite images. Geographic overview display button 538 toggles the on/off display of overview image 450 in a portion, for example in a corner, of the display area.

Address search bar 550 has a text input field 552 for receiving search text input, for example once the input field 552 is selected, as well as a query button 554 and a cancellation button 556. Once a user has input desired search text into the input field 552, the user may select the query button 554 in order to initiate a search of geographical locations based on the input text (which is passed by an applet associated with search bar 550 to navigation component 330) or may instead select cancellation button 556 in order to clear text from the input field 562 or halt the performance of a query that has been initiated.

Where the search text input into field 552 is determined by performance of the query to match unambiguously with a single location for which a geographic image 404 can be displayed, then navigation component 330 and display module 310 cooperate to identify and, in some embodiments, automatically display that location. On the other hand, where a number of locations match the search text, a selectable list of such locations may be displayed in a drop-down extension of search bar 550 (an example of which is shown in Figure 28 as 2810) or in a separate window over geographic image 404. The ordering of the displayed list items may be determined according to the location of the currently displayed geographic image 404, as is explained in further detail below with referene to Figures 28 and 29. Once one of the displayed list items is selected, navigation component 330 and display module 310 cooperate to enable a new geographic image 404 to be displayed, corresponding to the user's selection of a displayed list item.

As shown in Figure 4, navigation and function selection tool 410 may be positioned in a top left corner of display 100 in order to minimally obscure the underlying geographic image 404. However, in other embodiments, navigation and function selection tool 410 may be positioned in other corners of display 400 or may be broken into separate display components, whereby function selection bar 520, search bar 550, panning button 510 and zoom buttons 521, 522 are displayed as distinct and/or separate image components.

The search function provided by search bar 550 provides the ability to search and locate a geographic area independent of works project records stored in database 162. Navigation component 330 is configured to parse the input search text and to cause an error to be displayed if the search text relates to an unknown or invalid location or address or if the search text is otherwise unparseable. Parseable input text includes, for example, street number, street name, suburb, city or township and state, province or territory. Country selection may not be available if system 100 is configured to be confined to works to be displayed in only a single country or possibly a small group of bordering countries where organizations may share responsibility for the performance of works in more than one of those countries. In some embodiments, works-related displays visible to each user may be confined to a single state, province or territory or to a small group of neighbouring states, provinces and/or territories. In some other embodiments, there may be no geographic restriction on location searches or works- related searches.

Referring now to Figure 6, layer selection tool 420 is shown and described in further detail. Layer selection tool 420 comprises a layer selection section 610 comprising a plurality of pairs of check box controls to either show or hide works projects of specific types, each of which may be shown on a separate display layer. For example, and as illustrated in Figure 6, capital type works may include gas, power, road work, sewer, stormwater, telecommunications and water works, each of which may be displayed on the same geographic image 404 (if they are located within the geographic area for that image) if the respective check-box is selected to make each of those layers visible. Depending on user permissions, not all users may be able to select to have all works layers displayed.

Other layers may also be displayed using optionally displayable check boxes to display, for example, environmental, water management or cultural heritage overlays (which can effectively be created as works projects using editing tool 440). Such overlays are considered to be works projects for purposes of works conflict identification. Figures 9A and 9B illustrate use of the layer selection tool 420 to display (Figure 9A) a works project image 910 for a sewer type works project, along with works project images 920 and 930 for respective water type works projects. As can be seen from Figure 9A, the check-box to make sewer type works projects visible over geographic image 404 is checked. In comparison, as shown in Figure 9B, the check-box to display sewer type works projects is unchecked, and sewer type works image 910 is no longer displayed. As the water type works project check box is checked in both Figures 9 A and 9B, works images 920 and 930 for water type works projects remain visibly overlaid on geographic image 404. Thus, the check-boxes for the different types of works shown in layer selection tool 420 control which works image layers are turned on or off.

In the layer selection section 610, each pair of check-boxes allows the checking or unchecking of one of the check boxes for layer visibility, while the second of each pair of check-boxes enables the visibility of a tag (1412, 1422, Figure 14), indicating the layer and the owner of the works project, to be displayed in relation to each displayed works project in that selected layer.

Layer selection tool 420 also has a search section 620 with a text input field, a query button and a cancellation button arranged in a similar manner to search bar 550, as described above, and is operable in a similar way to identify works in specific geographic areas specified by the search terms entered in the search field of search section 620.

In addition to geographic searching for works projects using search section 620, a parameter search section 630 is also provided within layer selection tool 420 for enabling works projects to be identified by one or more of three possible statuses (i.e. planned, in-progress or completed), or to be identified as falling partially or wholly within a specified date range. Parameter search section 630 comprises check boxes to enable statuses to be selected and comprises pop-up selectable calendar buttons in order to enable selection of start and end dates. Start and end date fields are also provided that, if clicked on, enable manual entry of a start and end date, respectively.

Referring now to Figure 7, works project information display 430 is shown and described in further detail. Information display 430 comprises a works project reference number 705, an information section 710, an additional information section 730 (which can be displayed or hidden by toggling selection of additional information button 720) and a revision section 740. Revision section 740 has an edit button 745 that, if enabled (depending on user permissions), allows the works related information and works image data to be modified using the editing tool 440. Optionally, a logo or symbol of the recorded works project owner may be displayed as part of information display 430, for example near a header portion of the display.

The information shown in works information section 710 is information that is captured using a data input window 800 (Figure 8) when a new works project record is created using editing tool 440. The information displayed in information section 710 includes, as an example, information in 8 different fields, including the works project type (e.g. water), a description of the works (e.g. water renewal), an owner of the works project, an address or area in which the works project is to be conducted or which will be affected by the works project, start and end dates of the works, the status of the works project, a contact name (and preferably contact phone number or e-mail) and a unique reference allocated by the owner to the works project. This unique reference can act as a key linking field among the database records. Additional information that may be shown in the additional information section 730 may include further details of the works project, for example describing the works with greater specificity to provide more information as to the nature of the works to be carried out. The additional information may also include more detailed address or location information.

The revision section 740 may indicate the last modification date of the works information and the user who made those modifications, in addition to enabling editing of the works information by selection of edit button 745 (if permitted according to user permissions), which would cause editing tool 440 to be displayed.

The information shown in works information display 430 is intended to provide adequate information to enable another user to understand the nature, location, geographical and temporal extent of the works, in order to enable such a user to use this information in planning other works projects or to determine the extent of any possible conflict of works that may be identified by conflict management module 320. Greater or lesser amounts of information may be shown in sections 710, 730 and 740, depending on particular system requirements.

In some embodiments, works information display 430 may also include a selectable option to subscribe to an alert notification regarding changes to the works project status, timing or geographic extent so that interested users can be informed of such changes and consider how they may be affected. An example alert subscription window 2300 and subscription method 2400 are shown and described below, with reference to Figures 23 and 24.

Referring now to Figure 8, an example of data input window 800 is shown and described in further detail. Like editing tool 440, data input window 800 is displayed as an image overlay over a part of geographic image 404, for example on the right-hand side of the display. When data input window 800 is displayed, for example in response to selection of information button 1016, the editing tool 440 may be replaced or covered by the data input window 800. Similarly, when data input window 800 is closed, editing tool 440 is again displayed. The user may thus toggle between the display of editing tool 440 and data input window 800.

As shown in data input window 800, a plurality of descriptors 830 are shown for input fields 832 arranged sequentially down the window 800. The descriptors 830 and input fields 832 are for capturing the information shown in information sections 710 and 730, for example, in addition to further or more detailed information as required. Data input window 800 also has a save button 810 in order to save the information inputted into fields 832 into the applicable works project record stored in database 162. A return button 812 is also provided on window 800 in order to close the window, whether the information has been saved or not. The works-specific reference number 705 and owner of the works are also displayed in a header section 820 toward the top of window 800. If necessary, window 800 may have a scroll bar for enabling a scrolled list of input fields 832 to be displayed.

Referring now to Figures 10, 1 1 and 12, use of editing tool 440 is shown and described in further detail. Editing tool 440 comprises a series of command buttons, including a new works button 1010, a save button 1012, a cancel button 1014 and an information button 1016. Selection of the new works button 1010 allows the user to start graphically creating a new works project image over the geographic image 404 using one of the drawing tools corresponding to line button 1030, polygon button 1032, point button 1034 and eraser button 1036. Once the new works image has been completed and the required works information has been input into an associated data input window 800, the user can select save button 1012 in order to save a new works project record into database 162 based on the newly created works image and information. Cancel button 1014 can be used to cancel a newly drawn works image or changes made to an existing works image or information without saving a new or modified data record for that works image in database 162. Information button 1016 causes the data input window 800 to be displayed (in addition to or in place of editing tool 440) so that the appropriate data fields 832 can be populated with information to describe the new works project. If editing tool 440 is being used to modify an existing works project record, information button 1016 can be used to display the data input window 800 so that the appropriate data fields 832 can be modified and then saved using button 810.

A layer selection button 1020 can be selected in order to drop down a list of display layers corresponding to different works types within which a new works project can be created. Selection of a particular display layer from the drop down list may then dictate the style in which the works image is to be depicted. Alternatively, there may be more than one available style in which to create the works image in the selected works type layer. If available based on user permissions, different styles can be selected by selecting style button 1040 and then subsequently selecting a list item from a drop down list. Not all users will have access to creating new works projects in all layers. For example, a water-type works project may not be allowed to be created by a telecommunications utility user.

Each of drawing buttons 1030, 1032 and 1034 may be selected to give the pointer a specific function to be used to create a new works image, although each different type of works image suggests different things about the works project. For example, line button 1030 may be used to create a works image for a works project that is primarily directed along linear regions, such as streets, pipelines, telecommunications cables, etc. Figure 12 illustrates a display 1200 including a works image 1210 that is of a generally linear nature. Line button 1030, if selected, enables the creation of a line 1216 or series of lines 1216 having start and end points 1220, vertices 1212 and midpoints 1214.

Polygon button 1032 may be used for works projects or other overlays that are intended to cover a relatively large or irregular area (in a public works sense) that cannot be defined by one or more line segments but can be defined by a polygon. Display 1100 shown in Figure 1 1 shows an example area-type works project image 1 110 defined by an irregular outline. The irregular outline is defined by a series of straight lines 1 1 16 connected to each other at vertices 1 112 and each having a midpoint 1 1 14. Start and end points 1 120 may be selected once the polygon is completed (i.e. to enclose an area) to finish creating the polygon and allow the works image to be saved (along with works information to be captured via data input window 800).

For line and polygon-based works images, each straight line 1 116, 1216 of the image can be moved by clicking and dragging on one of the vertices 1212 or 1112. If a vertex 1212, 1 112 is shared by more than one linel 116, 1216, all lines 1 116, 1216 sharing that vertex 1212, 1 1 12 are changed by the repositioning of that vertex. Midpoints 11 14, 1214 can also be moved, for example by clicking and dragging on them, to effectively turn that midpoint 11 14, 1214 into a vertex 1112, 1212 at the new position of what was a midpoint 1 1 14, 1214, while creating two new angled lines, each having their own newly created midpoints 1114, 1214. In this way, complex lines and polygons can be drawn using editing tool 440, and their shapes and spatial extents can be readily modified, if needed. This dynamic creation or modification of the geographic extent of a works project can be particularly advantageous for authorized users in the planning of their works projects by providing an easy to use, graphics-based input paradigm for works project planning. In some embodiments, the editing tool 440 (and editing component 340) may be configured to allow only contiguous lines 1 1 16, 1216 to be created as the works image for each line or polygon-type works project, so that only a single continuous works image represents each works project. If a planned works project would have differently located project components, these components are each treated as separate works projects for present purposes, each having separate works images and separate works project records in database 162. The works information for each such project component may, however, include a reference and optionally a link to the other related project components.

In some embodiments, editing tool 440 and editing component 340 may enable more than one works image to be created in respect of a works project, thereby allowing the definition of works components or sub-projects within a larger works project. Such multiple works project components may comprise works of different types, spatial and temporal extents and locations. For example, a works project may include several point type works project components located in relatively close proximity and scheduled for performance during or around a similar period of time. Additionally, such works project components may involve the creation of works images including different types of works images, for example such as the combination of a point type works image and a differently located (but nearby) polygon types work image. Thus, the user may be free to use editing tool 440 to create multiple works project images (within a vicinity of say a few kilometers) over geographic image 404 before proceeding to save such images within a works project data record. The works project record for each works project component or sub-project may be of substantially the same form as the main works project data record, but comprising a link or pointer thereto.

The line and polygon drawing tools may be configured to create vertices wherever a user clicks or otherwise selects a position on the geographic image 404, automatically drawing a line image between successive vertices and, in the case of the polygon drawing tool, shading the space thus far enclosed by the vertices. For both tools, the pointer position may correspond with a hanging vertex to be established wherever the user clicks the pointer next, with a hanging line image extending between that hanging vertex and the previously created vertex. Through simple manipulation of the pointer, the user may thus dynamically position the vertices of the image as it is created and then dynamically reposition any vertex after a start/end button (i.e. the initial vertex) 1 120, 1220 has been selected to finish the initial drawing.

A point type works image 1310 is illustrated by way of example in display 1300 in Figure 13. This type of image 1310 is intended to indicate a type of works project that is highly localized (e.g. less than 100 meters across) and can be positioned on geographical image 404 by selecting point button 1034 and then clicking or otherwise selecting a specific location on geographic image 404. The actual image displayed for a point-type works image 1310 may vary depending on the layer (i.e. works type) it belongs to. For example, an image of an excavator (as in Figure 13) may be shown for point-type works projects that involve earth moving, while an image of an optic fiber bundle may be shown for point-type telecommunications works projects.

Where the user wishes to remove part or all of a works image, eraser button 1036 can be selected and then the user's pointer then functions as an erasing element to remove part or all of a works image.

Editing tool 440 and navigation component 330 cooperate to determine the precise geographical extent of a new works project when it is to be saved based on the works image newly overlaid on the geographic image 404. Thus, the user effectively provides a spatial or geographic definition of the extent of the works project when creating the polygon, line or point works images and this spatial information is saved in the works project data record. The spatial information for a works project may be stored in the form of a series of latitude and longitude values of successive vertices of the works image, for example for polygon and line-based works images, or as a latitude and longitude value pair for a point-based works image. Recording the spatial definition within spatial information for each works project data record allows the works image to be dynamically scaled along with the geographic image 404 and allows a comparison of the geographic and the temporal extent of overlapping or adjacent works projects to determine whether there may be a possible works conflict.

Figure 14 illustrates an example display 1400 of a geographic image 404 of an area where overlapping works images 1410 and 1420 are displayed. The works project corresponding to works image 1410 is in the sewer layer, as indicated by tags 1412, while the works project corresponding to works image 1420 is in the water layer, as indicated by tag 1422. However, because the works projects overlap each other geographically and temporally, works conflict management component 320 has determined there to be a potential works conflict, in which performance of either of the works projects may be compromised or affected by the other. As shown in display 1400, the specific region in which the geographic extent of the two works projects overlap is indicated by overlapping region 1430, shown in a different pattern or style to the display styles of the works images 1410 or 1420. This assists the user in discerning the specific area in which the conflict may exist. Additionally, a notification window 1440 is displayed nearby the overlapping region 1430 in order to provide further information to the user. The notification window 1440 may include information concerning either or both of the conflicting works projects, such as a description of the conflicting works, the location of the conflicting works, the owner(s) of the conflicting works, the start and end dates of the conflicting works and the contact name (and optionally phone number) of the person at the owner organization responsible for one or each of the conflicting works project.

As mentioned above, a potential conflict may be determined to exist where the spatial extent of two works projects is within a threshold proximity, even where there may be no actual overlap. Such potential conflicts may be visually represented by an artificially created overlapping region 1430 that extends between the closest points of the two works images. The threshold proximity may be a pre-set distance reckoned in differences of latitude and longitude, for example, and may vary depending on the works types, at issue. For example, road works may be considered to not conflict with other nearby road works that are more than a threshold distance of about 500 metres away, but for telecommunications works, that threshold distance may be 100 metres. Although it may, not be discernible in Figure 14, the different works images shown on different layers are displayed with different colours or patterns in order to be more visibly distinguishable as belonging to different layers (and hence different works types). Each of the works images in each layer toggles to a modified visual representation, for example by changing colour or contrast or, if the works image is for a point, changing shape, colour, contrast or size, upon mouse-over of the works image.

Figure 15 illustrates an example display 1500 of a geographic image 404 of an area where overlapping works images 1510 and 1520 are displayed. The overlap displayed in display 1500 is indicated by an overlapping region 1530 displayed while works image 1520 is in the process of being created (as illustrated by the presence of vertices and midpoints 1112, 1 114 shown defining the perimeter of works image 1520). As illustrated by display 1500, where works image 1520 is extended to cause an overlap in region 1530, works image 1510, which may be in a different display layer (i.e. of a different works type), may become displayed, together with an alert notification 1540 to describe the nature of the potential conflict and give details of the works project that has been previously stored and represented by works image 1510. Alert notification 1540 may provide a description of the works type of the works project corresponding to works image 1510, together with its location, owner, start date, end date and contact person. Notification window 1540 may also comprise selectable options, such as a view button 1542, a collaborate button 1544 and an ignore button 1546. If the user selects the view button 1542, more comprehensive details regarding the potentially conflicting works projects may be displayed and the user interface may remain in edit mode to enable further changes to the new or modified works image or information (e.g. by changing the date range in window 800). A selection of collaborate button 1544 may open a collaboration window 2000 (Figure 20), by which the creator of the works project corresponding to works image 1520 may communicate with the contact person for the works project corresponding to works image 1510 in order to resolve the potential conflict. Selection of ignore button 1546 will allow the user to continue creating or modifying the works project record corresponding to works images 1520, but will save a works conflict record once the works project for works image 1520 is saved (assuming that the overlap was not removed by further editing of the works project image 1520 or its temporal data).

Figure 16 illustrates an example display 1600 of a geographic image 404 of an area where a works project image 1620 overlaps with an overlay image 1610 that relates to a zoning, use or sensitivity overlay that is not directly associated with a works project. Such overlays may be recorded within database 162 in a similar manner to works project records, but may have open ended date ranges or date ranges that extend for many years. Alternatively, such overlays may effectively define moratoria for works projects in certain areas, for example to allow environmental recovery in a certain area after the completion of an earlier works project.

As with displays 1400 and 1500, display 1600 includes a displayed overlapping region 1630 where works project 1620 spatially and temporally overlaps overlay 1610. As with display 1500, the overlapping region 1630 and presence of overlay 1610 is dynamically displayed during the creation of works image 1620. Similarly, a notification window 1640 is dynamically displayed to indicate that the overlay may be of a particular type, such as a heritage overlay, indicate the owner, stake holder or body that has responsibility for management of the overlay, and a contact person with contact details. The notification window 1640 may also provide a view button 1642 and a collaborate button 1644 that function in a similar manner to view button 1542 and collaborate button 1544 described above.

Referring now to Figure 17, a computerized method for public works planning is shown and described in further detail. Method 1700 begins at step 1705 at which a user may provide log-in information in order to be allowed to access server system 110 as an authorized user. Step 1705 may involve the user causing web browser 117 to access a specific URL associated with server 110, which may allow the display of a home page and allow the input of a user name and password pair. Server 110 receives the user name and password pair and compares them against records of authorized users to determine whether the attempted log-in is successful and, if so, server system 110 then accesses user preferences, if any, associated with a user account, at step 1710. The user preferences may be used to determine a "home" location or default region for which geographic image 404 is to be displayed. At step 1715, server system 110 accesses geographic images for the default or home region specified in the user preferences. Alternatively, geographic images for the most recent geographic image 404 displayed for that user may be retrieved.

At step 1720, display module 310 cooperates with browser application 117 to generate an interface display including geographic images sourced according to user preferences or default settings. This interface display includes navigation and function selection tool 410 and, optionally as a default, geographic overview image 450, plus geographic information bar 406.

Where user preferences specify a default layer selection, works images corresponding to works projects of a type corresponding to that layer (and that are located at least partly within the geographic area covered by geographic image 404) are displayed as part of step 1720. At step 1725, the user is free to navigate the display generated by browser application 117 and manipulate the tools to provide appropriate overlays, as desired. Depending on whether the user selects a navigation function, a layer selection function or an editing function, for example, server system 1 10 may cooperate with client device 115 to provide further or different displays via browser application 117, may update data records and/or access stored works project information.

If a navigation function is selected at step 1730, then at step 1735, display module 310 may access GIS server 140 (or prompt browser application 117 to access GIS server 140) to generate a new display of a selected geographic area and/or a search results list, for example if layer location search text was input to search field 552 or in the "locate works" section 620 of layer selection tool 420. Any works projects located within the new geographic image 404 area to be displayed are accessed in database 162 to determine how each relevant works image is to be displayed as an overlay on geographic image 404. Display module 310 then cooperates with browser application 117 to generate an appropriate depiction of the relevant works images 405 that are applicable to the selected image display layer (i.e. for one or more different works types).

If at step 1740, a layer selection function is selected, then at step 1745, display module 310 accesses database 162 to determine which works images need to be rendered over display 404 according to the layer selection or deselection received via the layer selection tool 420 and further coded and transmitted from server system 110 to client system 115 for execution by browser application 117. Browser application 117 then locally generates the updated display to include or exclude the relevant work images in the newly selected or deselected layers.

If at step 1750, the editing function is selected, for example by the user clicking on editing tool toggle button 534, then method 1800 and/or 1900 is performed, as described in further detail below with reference to Figures 18 and 19.

While server system 110 determines that the user remains logged in at step 1760, the user is allowed to continue to perform the functions provided by the downloaded code executed by browser application 117. Thus, steps 1725 to 1750 may be repeated, depending on the user's actions. Although not specifically shown in Figure 17, further options are selectable by the user in the manner described herein, such as the optional display of geographic overview image 450 or popping up of a works project information window 430 upon mouse-over of a works image 405. Further options may be provided, such as user preference set-up options, help functions or collaboration/conflict identification functions, as described herein.

Referring now to Figure 18, a method 1800 of works project editing and conflict determination is shown and described in further detail. Method 1800 begins at step 1805, in which editing tool 440 is displayed in relation to geographic image 404, for example by selection of editing tool button 534 or edit button 745. At step 1810, server system 110 receives input via browser application 117 in relation to a new or stored works project, for example corresponding to user manipulation of an existing works image (if authorized) or selection of one of drawing tool buttons 1030, 1032, 1034 and 1036. Alternatively, the input may include changes to works project information via data input window 800. At step 1815, the user input of step 1810 is allowed to be continued until the changes are saved or, at step 1820, the changes are cancelled. If the changes are cancelled at step 1820, method 1800 returns to step 1805. If the changes are saved at step 1815, then at step 1825 editing component 340 causes a new works project record to be stored in database 162 or causes the updating of the previously stored works project record to reflect the changes.

At step 1830, conflict management module 320 determines whether there is a temporal and spatial overlap of the new or modified works project with another stored works project. This determination is made by comparing the spatial and temporal extent of the new or modified works project with each nearby stored works project and, where the spatial and temporal extents of the neighbouring works projects overlap or are within a configured temporal or spatial proximity threshold, a potential works conflict is flagged in relation to each affected works project and, at step 1835, conflict management module 320 cooperates with display module 310 to generate and display an alert message regarding the possible conflict of works. As previously described in relation to Figures 14, 15 and 16, geographic image 404 may be updated in response to storage or pre- saving (i.e. during editing) of a new or modified works project record to include a display of an affected overlapping or proximate area between the affected works projects to clearly indicate the area of 1430, 1530 or 1630 of potential conflict. The temporal proximity threshold may be a set time period, such as a week or a month, for example, and is only tested where there is determined to be spatial proximity within the spatial proximity threshold.

At step 1840, the details of the potential conflict of works are stored in a conflict record and linked to each affected works project, at step 1840. Separately from step 1840, and subsequent to step 1835, conflict management module 320 generates and sends an alert message, for example by e-mail or text message, to a contact e-mail or phone number associated with at least the senior (i.e. previously recorded) works project, at step 1845. Optionally, an alert message may be generated and sent to the creator of the new or modified works project that resulted in the detection of the possible conflict, although it is likely that that creator will be aware of the possible conflict by virtue of the dynamic conflict identification process 1900, described further below with reference to Figure 19. Optionally, step 1810 may involve dynamically monitoring the possible occurrence of a works conflict during the creation or modification of a particular works project, whereby possibly conflicting works projects are immediately identified as such by causing the relevant works images to appear when the newly created or modified works image gets too close to or actually overlaps with the stored works project. This process is graphically depicted by the flowchart of Figure 19. Method 1900 depicted in Figure 19 is initiated when a user invokes the editing tool 440 and begins to create a new works project or modify an existing works project.

Method 1900 involves a continuous monitoring process that loops while the works project record is open for editing and until it is saved. This process involves the receiving of user input in relation to the addition or modification of works image geometry or meta data for a works record and the subsequent querying of database 162 for works records that have overlapping or proximate spatial and temporal extents. Where an overlap or close proximity is detected, the display provided by browser application 117 is updated (either immediately or once editing is stopped or paused for a predetermined time) to include a display of the stored works project that may be affected by the proposed change and to indicate a geographic area of potential overlap. In some embodiments, a conflict may be identified based on spatial extent only, for example where data as to the temporal extent of the proposed new or modified works project has not been received or is unconfirmed. Completed works projects may be excluded from conflict determinations in some embodiments, although in other embodiments they may be involved to the extent that they define a temporal proximity threshold (or moratorium) that remains current.

Process 1900 further involves the generation and display of an alert message 1540, 1640 as an overlap on image 404 regarding the possible works conflict and inviting the user to select one of several options to be performed in relation to the potential conflict, including for example "collaborate", "ignore" and "view". Selection of the collaborate option causes conflict management module 320 to store the details of the newly created or modified works project and invoke a collaboration process between the owners of the two possibly conflicting works, whereby those two owners may exchange messages, for example via a works collaboration window 2000, shown in Figure 20. If a user elects to ignore the potential works conflict, then steps 1840 and 1845 are performed, as in method 1800. If the user selects the view option, then more detailed information as to the stored works project may be displayed, together with the applicable works images of the stored works projects, and the user may then provide further input via editing tool 440 to modify the extent of the proposed new or changed works project. Figure 21 is a flow chart of a method 2100 for allowing the user to comment on a works project, either owned by the same owner or a different owner. System 100 contemplates that there will be a number of authorized users authorized to create works projects for a single owner. Method 2100 involves the selection of an option to add a comment to a works project record, checking user permissions to determine whether the user is authorized to comment, and then allowing or refusing the addition of comments, depending on user permissions. Where comments are allowed, the user may be allowed to see any existing comments entered in relation to that works record and any new comments added by the user may be stored in relation to the works project record and notified to the contact person for that works project. As a further option, the addition of the comment to the works project record may be notified to other users that have subscribed to alert notifications for that works project. Figure 22 is a flow chart of a method 2200 for viewing stored comments in relation to works project records. Method 2200 involves the user initiating a request to view comments in relation to a specific works project record, checking database 162 for user permissions to determine whether the user is authorized to view the comments. Depending on whether the user is authorized, they will either be allowed to view the comments or receive a notification that they are not authorized.

Figure 23 is an example display of a window 2300 for allowing a user to subscribe to an alert notification in respect of a specific works project, so that the user can be notified of any changes or status updates (i.e. a change from "planned" to "in-progress") or changes to temporal or spatial extent. A method 2400 of enabling alert subscription in this regard is shown in the flow chart of Figure 24 and involves the capturing of user notification details and user account details and storing those details in a subscription record linked to the relevant works project record in database 162.

The method 2400 of Figure 24 is applicable to receiving subscriptions from users not associated with an owner of works projects, but nevertheless having an interest in the performance of the works projects. Such users may thus be considered to be a different class of user to users that are authorized to create and modify works project information and records. For this latter class of users, the flow chart of Figure 25 illustrates a method 2500 for allowing alert notification subscription in relation to one or more works projects.

Figure 26 is a flow chart of a method 2600 for providing alert notifications to subscribed users upon a change of status or temporal or spatial extent of a works record. Method 2600 involves checking for a linked subscription in relation to a works project record when that record is updated, determining the nature of the change to the works project record, for example by comparing the previous version of the record with an updated version, generating a notification regarding the change to the works project record and then sending that notification to subscribed users, for example by e-mail or text message or, in some instances, providing viewable notifications for relevant users upon log-in. A recipient of such notifications may be provided with a selectable option on the notification window to view the relevant works project record and/or view the works image for the project overlaid on a geographical image 404. Figures 28 and 29 illustrate a feature of the location search function provided by search bar 550. As shown in Figure 28 by display image 2800, where the search text "Portsea" is input to field 552, the search results are provided in a drop-down list 2810 indicating one result for Portsea in the United Kingdom and another result for Portsea in Australia. As the geographic image 404 displayed in display 2800 is of Portsmouth in the United Kingdom, display module 310 determines in accordance with method 2900 that the search result for Portsea in the United Kingdom is likely to be more relevant to the user's interests and therefore lists that search result higher than the search result for Portsea in Australia. This illustrates the hierarchical ranking of location based search results based on the geographic area currently being displayed in geographic image 404, as well as the country in which it is located. For example, if there were another Portsea in another part of the United Kingdom identified by the search, then this would be located intermediate the "Portsea, Portsmouth" search result and the "Portsea, Australia" search result. Where in-country search results are located that do not correspond to the geographic area currently displayed, these may be ranked in drop-down list 2810 by various configurable criteria, for example including alphabetical order or a relative proximity to the current geographic area being displayed.

Figures 30 and 31 illustrate a process of data record importation 3100 to allow for the bulk importation of works project data to form new works project records in database 162. This process may be used by organizations wishing to migrate data from different systems into system 100. As illustrated in the flow chart of Figure 31, a client device 115 may be used to initiate the export of data from client device 1 15 or another device, such as a server, to which client device 115 has access, to export that data to database 162 of system 100. This exporting may involve the extraction and formatting of works related data into an extract form for provision in a common format file to server system 1 10.

Editing component 340 may handle the parsing of the received works project data extracts uploaded to server system 1 10 and saving of those extracts as new works project records, where possible. Editing component 340 and editing tool 440 may also be involved in the validation and verification of the imported works project information, in a similar manner to the previously described modification of an existing works record or creation of a new works project record. For example, where apparent or potential works project conflicts seem to arise, an opportunity for user collaboration or modification of the imported works project record may be provided prior to that works record being saved, thereby avoiding an actual conflict being recorded in respect of such a works project.

Once the imported works project records are sufficiently verified, those suitable for recording into database 162 can be approved by the importing user for publication to database 162, as applicable. General publication of some works projects may be declined, whereby such works projects may be saved to database 162, but not be visible to the general public or to any unauthorized users.

Throughout this specification and claims which follow, unless the context requires otherwise, the word "comprise", and variations such as "comprises" and "comprising", will be understood to imply the inclusion of a stated integer or step or group of integers or steps but not the exclusion of any other integer or step or group of integers or steps. The reference in this specification to any prior publication (or information derived from it), or to any matter which is known, is not, and should not be taken as an acknowledgment or admission or any form of suggestion that that prior publication (or information derived from it) or known matter forms part of the common general knowledge in the field of endeavour to which this specification relates.

Claims

1. A system for public works planning, comprising:

processor-readable storage storing executable program code, the program code including server code for serving page code to a client device, the page code being executable by a browser application to:

display geographic imagery of a selected geographic area, display at least one works image overlaid on the geographic imagery indicative of, and geographically corresponding to, a completed, current or planned works project in one or more geographic positions within the geographic area, and

selectively display a works project editing tool overlaid on a portion of the geographic imagery to enable user creation and modification of works information for a works project, the works information enabling generation of the at least one works image;

2. The system of claim 1, wherein the program code further comprises server code for serving page code to the client device to enable selective display of an image layer selection tool overlaid on a portion of the geographic imagery to enable user selection of different image layers to be displayed, each image layer displaying works images corresponding to different types of works.

3. The system of claim 2, wherein the page code comprises code for displaying a tag including a works type descriptor and an owner descriptor, the tag being displayed adjacent each works image overlaid on the geographic imagery in response to selection of an option displayed on the image layer selection tool adjacent a respective selectable image layer display control.

4. The system of claims 1 to 3, wherein the page code further comprises code for causing the browser application to automatically display a works project information window adjacent a works image in response to user input to focus on the works image and to automatically hide the information window in response to user input no longer focusing on the works image.

5. The system of any one of claims 1 to 4, wherein the page code comprises code for selectively displaying second geographic imagery overlaid on a portion of the first geographic imagery, the second geographic imagery being of smaller scale than the first geographic imagery and showing geographic areas surrounding the selected geographic area.

6. The system of claim 5, wherein the page code further comprises code for displaying a navigation tool comprising selectable controls for changing the displayed geographic area, wherein the navigation tool comprises a tool bar comprising further selectable controls for controlling at least one of display functions and input functions.

7. The system of claim 6, wherein the navigation tool comprises a text-based search input component to receive text-based search input in relation to a geographic area to be displayed.

8. The system of any one of claims 1 to 7, wherein the page code further comprises code for displaying a user controls tool to enable a user of the browser application to selectively control one or more control overlays to be displayed over the parts of the geographic imagery.

9. The system of claim 8, wherein the control overlays include the works project editing tool and an image layer selection tool.

10. The system of any one of claims 1 to 9, wherein the program code further comprises a works conflict management component to determine a possible conflict by determining whether the works project geographically and temporally overlaps with, or is within a proximity threshold of, another works project.

11. The system of claim 10, wherein the works conflict management component is further to determine the possible works conflict during user creation of a new works project or user modification of stored works project and to cause an alert notification of the possible works conflict to be displayed by the browser application when the possible works conflict is determined.

12. The system of claim 1 1, wherein the works conflict management component is further to cause a works conflict image to be displayed over the geographic imagery by the browser when the possible works conflict is determined, the works conflict image depicting an area of spatial overlap or proximity of works images of the two or more potentially conflicting works projects.

13. The system of claim 11 or claim 12, wherein the works conflict management component is further to cause the browser to display a works image of a possibly conflicting stored works project in response to the user creation or modification.

14. The system of claim 13, wherein the display of the works image of the possibly conflicting stored works project is caused to occur on-the-fly during the user creation or modification.

15. The system of claim 13, wherein the display of the works image of the possibly conflicting stored works project is caused to occur prior to a works project record of the new or modified works project being stored in a database along with other works project records.

16. The system of any one of claims 1 to 15, wherein the code to display the works project editing tool comprises code to allow user manipulation of the editing tool to graphically define a spatial extent of a new or modified works project in relation to the displayed geographic imagery.

17. The system of claim 16, wherein the code to display the works project editing tool comprises code to allow user manipulation of the editing tool to specify a display layer of the new or modified works project.

18. The system of claim 16 or claim 17, wherein the works project editing tool allows user manipulation to define one or more graphical works images for a works project, the one or more graphical works images comprising at least one of a polygon object, a line object and a point object.

19. The system of claim 18, wherein definition of the polygon object by the user comprises selection of a location of a plurality of vertices of the polygon and allowing each of these vertices to be re-positioned.

20. The system of claim 19, wherein definition of the polygon object by the user comprises allowing a mid-point of each straight line extending between neighboring vertices to be re-positioned, thereby creating a new vertex from the mid-point and two new lines extending to the neighboring vertices.

21. The system of claim 4 or anyone of claims 5 to 20 when dependent on claim 4, wherein the works project information window comprises, for users having authorization to edit the works project to which the information window relates, a selectable option to edit the works information for the works project.

22. The system of claim 21, wherein selection of the selectable option to edit causes display of the works project editing tool when it is not already displayed.

23. The system of any one of claims 1 to 22, wherein the page code further comprises code to display tools and image overlays over the geographic imagery as being at least partially semi-transparent when not the subject of user input focus to thereby allow at least part of the underlying geographic imagery to be visible.

24. The system of any one of claims 1 to 23, wherein the geographic imagery is displayed to extend to the borders of the display area provided by the browser application.

25. A method for public works planning, comprising:

executing at a server system program code, the program code including server code for serving page code to a client device, the page code being executable by a browser application to:

26. A computerized system for public works planning, comprising:

a data store responsive to the interface means to store and retrieve the works information.

27. The system of claim 26, further comprising a works conflict management component to determine whether the works project geographically and temporally overlaps or is proximate with another works project and to interact with the computerized interface to provide an indication of any determined overlaps or proximities.

28. A computer-implemented method for public works planning, comprising:

dynamically indicating a possible works planning conflict via the user interface in response to the receiving if it is determined that there is a geographic overlap or proximity of the new and another works projects.

29. A system comprising means for performing the method of claim 28.

30. Computer-readable storage storing executable program code for performing the method of claim 25 or claim 28 or for implementing the system of any one of claims 1 to 24, 26, 27 and 29.