StreetFactory Client
Change record
|
Issue |
Date |
Change description |
Author |
|
A |
|
Creation |
Fabrice FONTENOY |
Approval sheet
|
Responsibility |
Name |
Visa |
|
Work Package Manager |
Frédéric VIAULT |
|
|
Project Manager |
Philippe GASTAL |
|
|
Quality Assurance Manager |
Nicolas HESTIN |
|
3.3 Workflows and Activities perspective
3.4 Running Processes perspective
3.7 Projections and Datum perspective
Table of figures
Figure 4 : Perspectives buttons
Figure 5 : External Tools buttons
Figure 8 : Editor in edition mode
Figure 10 : Project Explorer panel
Figure 11 : Project Editor panel
Figure 12 : Local Objects explorer
Figure 13 : Local Objects edition panel
Figure 17 : Drawing polygon menu
Figure 19 : Information Panel for AOI panel
Figure 20 : Information Panel for Block panel
Figure 21 : Information Panel for Dataset panel
Figure 22 : Workflow and Acitivies perspective
Figure 23 : Available Workflows view
Figure 24 : Available Activities view
Figure 25 : Workflow Representation panel
Figure 26 : Activity Configuration editor
Figure 27 : Running processes perspective
Figure 29 : Workflow Representation view
Figure 30 : Activity Parameters view
Figure 31 : Error Information view
Figure 32 : Execution Information view
Figure 34 : Platforms perspective
Figure 37 : Logger messages panel
Figure 38 : Projections and Datum perspective
Figure 40 : Projection Explorer panel
Figure 41 : Custom Datum editor
Figure 42 : Custom Projection editor
Figure 43 : Block Sequence view
Figure 44 : Block Explorer panel
Figure 45 : Blocks / Image Links editor
Figure 46 : Block Sigma editor
Figure 48 : Images Rules explorer
Figure 49 : GCP Rules explorer
Figure 51 : Subfield extraction panel
Figure 52 : Drivers perspective
Figure 54 : Driver Edition panel
Figure 55 : Server Monitoring HTML page
Figure 56 : Cluster Nodes Status view
Figure 57 : Terminal perspective
Figure 58 : Image Viewer perspective
Figure 59 : Users management view
Street Factory application allows fully automatic processing of any oblique and street imagery for the generation of 3D urban models.
This application is a fully integrated solution with software and hardware allowing high productivity and fast, automated processing of imagery in order to manufacture 3D digital urban model as 3D Textured Triangle Irregular Network.
In order to provide such efficiency, quality and automation, Street Factory is designed around four main axes:
Moreover the system uses parallel GPU server processing efficiency in order to deliver fast productivity even with thousands of images.
Street Factory runs on a parallel distributed processing system. All the computation work is done on a server and compute nodes. The server is the machine that provides a variety of services that are needed by the system including database maintenance and dispatching computing jobs to the nodes. Computing nodes are the machines used mainly for computation. Nodes receive the computation jobs from the server.
This project consists in the development of the StreetFactory client part.
This document is the User’s Manual (UM) of the StreetFactory client part.
The document is the Software Design Document. It is composed with the following parts:
|
Term |
Definition |
|
Block |
Group of images that are adjusted together for geometry in a single block. |
|
Camera compound |
Platform used for images acquisition |
|
Computation node |
Machine on which Street Factory™ software computation is performed. |
|
Dataset |
Images and their metadata which are imported into SF. |
|
Tile |
Processing area for 3D model construction. Each Tile is computed separately in a single job. The 3D output (3D Mosaic) is made up of several Tiles. |
|
Unitary Camera |
Single camera, part of a camera compound. |
|
Acronym |
Definition |
|
AOI |
Area of interest |
|
GeoTIFF |
Tagged Image File Format with additional geo-reference information (projection, coordinates system, dating information, ...) |
|
CSV |
Comma Separated Values |
|
DSM |
Digital Surface Model |
|
GCP |
Ground Control Points |
|
KML |
Keyhole Markup Language |
|
JPEG |
Joint Photographic Experts Group |
|
SHP |
SHaPe file (ESR vector data format) |
|
TBC |
To Be Confirmed |
|
TBD |
To Be Defined |
|
TIFF |
Tagged Image File Format |
|
TPR |
Table Population Rule |
|
Id |
Title |
Reference |
|
[AD01] |
Installation and Maintenance Manual |
C0057270-IAM-15-045 |
|
Id |
Title |
Reference |
|
|
|
|
Street Factory™ allows fully automatic processing of any oblique and street imagery for the generation of 3D urban models.
Street Factory™ is a fully integrated solution with software and hardware allowing high productivity and fast, automated processing of imagery in order to manufacture 3D digital urban model as 3D Textured Triangle Irregular Network (TIN).
In order to provide such efficiency, quality and automation, Street Factory™ is designed around four main axes:
· precise and robust geometry management
· effective photogrammetric measurement from any sensors
· 3D automated textured TIN generation from multiple views
· open output format for easy integration with OpenSceneGraph.
Moreover the system uses parallel GPU server processing efficiency in order to deliver fast productivity even with thousands of images.
Street Factory™ runs on a parallel distributed processing system. All the computation work is done on a server and compute nodes. The server is the machine that provides a variety of services that are needed by the system including database maintenance and dispatching computing jobs to the nodes. Computing nodes are the machines used mainly for computation. Nodes receive the computation jobs from the server
This chapter introduces the user to the basic interfaces in Street Factory™ as well as the inputs and outputs of the System.
On the workstation, the user launches the main interface of StreetFactory™ client.
A dialog allowing to choose the workspace location (where are stored the user preferences) is displayed:
When the workspace location is chosen, the login panel is displayed:
Figure 1 : Login window
There are two login options.
· To use an existing Username and Password and to click on Login button ,
· To create a new account by clicking on Sign-up button which will provide a dialog box that needs to be filled in:
Figure 2 : Create user window
The main interface opens after successfully logging.
Thanks to the views buttons, the user can navigate between the different.
Project view is opened by default at start.
Figure 3 : General window
The StreetFactory tools bar is dicided in three parts:
· The Perspectives buttons,
· The External Tools buttons,
· The other buttons.
The Perspectives buttons allow the user to switch from one perspective to another.
Figure 4 : Perspectives buttons
These buttons correspond each to one perspective. You can easily switch from one perspective to another using them. The available perspectives are:
|
Projects perspective:
|
|
|
Map perspective:
|
|
|
Workflow and Activities
perspective: |
|
|
Running Processes
perspective: |
|
|
Platforms perspective:
|
|
|
Logs perspective:
|
|
|
Projection and Datum
perspective: |
|
|
Blocks perspective:
|
|
|
Rules perspective: |
|
|
Drivers perspective:
|
|
|
Monitoring perspective |
|
|
Terminal perspective:
|
|
|
Image Viewer
perspective: |
|
|
|
|
For more information about perspectives, see §2.3.
The external tools buttons allow to execute the external tools installed with StreetFactory distribution:
Figure 5 : External Tools buttons
The other buttons allow to access to miscellaneous StreetFactory client features:
Figure 6 : Others buttons
The following other buttons are available at the right of the tools bar:
|
Users Management: Manage rights between users and projects. |
|
|
Parameters: Customize StreetFactory |
|
|
About StreetFactory |
|
|
Switch off |
The Status Bar provides general information.
Figure 7 : State Bar
|
/ |
Name of active project opened. |
|
User Name logged in this session. |
|
|
/ |
Connection status. |
When the status is disconnected, a right-clicking on the connection status allows to reconnect to the StreetFactory™ client.
The StreetFactory client graphical interface offers edition features through several editors.
In all StreetFactory client editors, the mandatory fields are signaled by a “*” character. For example:
All StreetFactory client editors offer the following buttons:
|
Allows to enter in
edition mode |
|
|
Allows to exit the
edition mode by cancelling the modifications |
|
|
Allows to exist the
edition mode by saving the modifications |
When the edition mode in enable, an “*” character is displayed in the editor header. For example:
Figure 8 : Editor in edition mode
The Projects perspective allows to manage the (creation, modification, deletion) the StreetFactory projects.
Figure 9 : Project view
The Projects perspective is composed with the following views:
· the Projects explorer,
· the Project editor,
· the Local Objects explorer.
The projects available for the logged user are listed in the Project Explorer panel. When a project is open, a tree of the open project gives access to the project AOIs, Datasets, Blocks and Tiles.
Figure 10 : Project Explorer panel
The Projects view offers the following buttons:
|
Allows to open the
selected project: this action closes the open project if any) |
|
|
Allows to close the
selected project |
|
|
Allows to remove the selected project: this action closes the project to remove is the current project (Available only if a project is selected) |
|
|
Allows to create a new project |
Project Editor allows you to fill information about project at creation time and edition time.
Figure 11 : Project Editor panel
At project creation, the following attributes must be set:
· General information
o Name: Name of the project.
o Priority: Priority of the project.
o Home Folder: Path where project will be saved.
o Main AOI: Local object used for main AOI in the project.
· Specifications information
o Projection: Projection used in the project.
o Datum: Datum of the project.
o Altitude Reference: Altitude Reference of the project.
o Building Height: Building Height of the project
· If “Use custom DSM Parameters” is checked, it is necessary to set the DSM information:
o DSM: Path of the DSM to use.
o Projection: Projection of the DSM to use.
o Datum: Datum of the DSM to use.
o Altitude Reference: Altitude Reference of the DSM to use.
o Type: Type of the DSM to use.
· User access: allows to specify the users having access to the project. By default, the current user is checked and can’t be unchecked.
At project modification, only the following attributes can be set in Specific Information zone:
· Range Z min: Z min of the project
· Range Z max: Z max of the project
· Building Height: Building height of the project
The Local Objects explorer allows to manage the AOI which are not associated to a project.
Figure 12 : Local Objects explorer
A local object can be created:
· either by loading a graphic (SHP or KML) file file (see after),
· either by drawing a polygon in the map view (see §3.2.2).
From the Local Objects explorer, it is possible, by a contextual menu, to:
· remove a local object,
· import a new local object by loading graphic file (SHP or KML file),
· rename an existing local object,
· convert an existing local object into an AOI of the open project,
· edit an existing local object by adding / removing / editing the points of the associated polygon:
Figure 13 : Local Objects edition panel
The Map perspective allows to visualize the content of the open project in a graphical representation:
Figure 14 : Map perspective
The Map perspective is composed with the following views:
· the Layers view,
· the Map view,
· the Selection view,
· the Information view,
· the Local Objects explorer.
The Map also offers a dataset editor allows to modify the images of a dataset of the project.
The Layers View gives the list of the layers composing the open project:
· the project AOIs (each AOI is considered as a layer),
· the project datasets (each dataset is considered as a layer),
· the projects blocks (each block is considered as a layer),
· the project tiles (each tile is considered as a layer),
Figure 15 : Layers view
The Layers view gives two representations:
· a hierarchical presentation of the layers where layers are grouped by type and where it is possible, to
o enable or disable visibility of each layer in the Map view. This action is performed by checking or un-checking the check box associated to the layer in the tree view,
o activate / deactivate a layer for layer selection in the Map view This action is performed by the contextual menu available on each layer in the tree,
o edit the dataset (see §3.2.6). This action is performed by the contextual menu available on each dataset layer in the tree.
· a flat presentation of the layer where layers are listed in the order they appear on the Map view.
The Layers view offers the following buttons:
|
Allows to switch in hierarchical presentation of the layers |
|
|
Allows to switch in flat presentation of the layers |
|
|
Allows to move the
selected layer at the foreground |
|
|
Allows to move up the
selected layer |
|
|
Allows to move down the
selected layer |
|
|
Allows to move the
selected layer at the background |
The Map perspective allows to visualize the open project objects in a graphical representation:
Figure 16 : Map view
The Layers view offers the following buttons:
|
Allows to activate/deactivate the transparancy (transparency is time-consuming) |
|
|
Allows to show/hide tracks |
|
|
Allows to show/hide ceiling footprints of the checked dataset(s) images |
|
|
Allows to show/hide DTM footprints of the checked dataset(s) images |
|
|
Zoom In / Zoom out |
|
|
Allow to pan the map |
|
|
Allows to select
object(s) |
|
|
Allows to zoom to active layer. If several layers are active, the zoom is made on a box bounding the active layers |
|
|
Allows to display full extent of all displayed layers |
|
|
Allows to show/hide world map in background |
|
|
|
Allows to show/hide latitude / longitude grid: The granularity of the grid adapts itself to the zoom. |
|
Export the selected footprint(s): You can save active element as shapefile (.shp) or .kml file. |
|
|
Allows to draw a polygon using the following contextaul menu: |
Figure 17 : Drawing polygon menu
|
Draw rectangle |
Create a rectangle by drawing it in the map |
|
Draw polygon |
Create manually a polygon by drawing the points in the map. If two points are drawn, the resulting polygon is the rectangle with the two points as opposite corners (bounding box) |
|
Draw by coordinate |
Create manually a polygon by entering the coordinates of the points. If two points are entered, the resulting polygon is the rectangle with the two points as opposite corners (bounding box) |
The selection view allows to list the object selected in the map:
Figure 18 : Selection view
As soon as an object is selected in the map view, it appears in the selection view. It is possible to remove each object from the selection:
· temporary by unchecking the object in the list
· permanently by removing it from the view using the remove button
The Selection view offers the following buttons:
|
Allows to remove the
focused object |
|
|
Allows to empty the Selection view to deleselect all objects selected in the Map view |
|
|
Allows to temporary remove all objects from the selection |
|
|
Allows to reselect all objects temporary removes from the selection |
|
|
Allows to display the
focused image (See §3.13) |
See §3.1.3.
The Information view allows to display the information about the object focused in the selection view:
Figure 19 : Information Panel for AOI panel
Figure 20 : Information Panel for Block panel
Figure 21 : Information Panel for Dataset panel
The Dataset editor allows to display / edit the image associated to a dataset:
The Dataset editor allows to display / edit the images associated to a dataset. For each image, the followings details are displayed in a table:
· Image Id: the identifier of the image,
· Order Id: the image rank,
· Image Name: the name of the image,
· Camera Id: the identifier of the camera which took the image,
· Track Number: the identifier of the track associated to the image,
· Shot Number: the image number in the track,
· Shot Time: Time where the image has been taken.
On image selection, some additional parameters are displayed in the detailed zone:
· X: X coordinates associated to the image,
· Y: Y coordinates associated to the image,
· Z: Z coordinates associated to the image,
· Phi: Phi angle associated to the image,
· Omega: Omega angle associated to the image,
· Kappa: Kappa angle associated to the image,
It is possible:
· to edit the Camera Id, Track Number and Shot Number parameters of the selected image if only one image is selected,
· to edit the Track Number parameter of the selected images if several images are selected,
· to display the selected image(s) using the Image Viewer perspective (see §3.13).
The Workflow and Activities perspective allows to instantiate a workflow or a standalone activity and to configure it.
Figure 22 : Workflow and Acitivies perspective
The Workflow and Activities perspective is composed with the following views:
· the Available Workflows view,
· the Available Activities view,
· the Workflow Representation view,
· the Activity editor.
The Available Workflows view displays the workflows available for the open project. The workflows are sorted by group.
Figure 23 : Available Workflows view
The instantiation of a workflow is performed by double-clicking on it. On workflow instantiation, the selected workflow appears in the Workflow Representation view (see §3.3.3).
The Available Activities view displays the standalone activities available for the open project. The activities are sorted by group.
Figure 24 : Available Activities view
The instantiation of a standalone activity is performed by double-clicking on it. On standalone activity instantiation, the selected activity appears in the Workflow Representation view (see §3.3.3).
The Workflow Representation view allows to visualize a graphical representation of the instantiated workflow or standalone activity.
Figure 25 : Workflow Representation panel
The workflow activities are displayed in a specific color according to its status (each color is configurable through User Preferences management):
· Selected,
· Configured,
· Not configured.
Remark: a standalone activity is represented as a workflow containing only one activity.
By selecting an activity, it is possible to configure it using the Activity Configuration editor (see §3.3.4).
When all activities of the workflow are configured it is possible to create it.
The Workflow Representation view offers the following buttons:
|
Allows to cancel the configuration of all activities of the Workflow |
|
|
Allows to create the
workflow |
The Activity Configuration editor allows to configure the activity selected in the Workflow Representation view.
Figure 26 : Activity Configuration editor
The Activity Configuration editor is:
· either a generic editor: in this case, the editor is generated according to the activity definition given by the Street Factory server (see Street Factory server for more information),
· either a specific editor: in this case, the editor is applied to a specific activity, not is the scope of this document.
The Running Processes perspective allows to visualize the state of the workflows and activities running for the open project.
Figure 27 : Running processes perspective
The Running Processes perspective is composed with the following views:
· the Jobs view,
· the Workflow Representation view,
· the Activity Parameters view,
· the Error Information view,
· the Execution Information view,
· the Submit File view.
The Jobs view allows to visualize the state of the workflows and activities running for the open project:
Figure 28 : Jobs view
As soon as a workflow or a standalone activity is created from the Workflows and Activities perspective, it appears in the Jobs view.
For each workflow or a standalone activity, the following settings are displayed:
· Name: name of the workflow or the activity
· Status: status of the workflow or the activity which can be:
o CREATED: the workflow or the activity has been created from the Workflows and Activities perspective,
o SUBMITTED: the workflow or the activity has been submitted to the StreetFactory server,
o STARTED: the workflow or the activity has been started by the StreetFactory server,
o RUNNING: the workflow or the activity is running at the StreetFactory server side,
o STOPPED (only available for a workflow): the workflow has been stopped by a breakpoint,
o CANCELED: the workflow or the activity has been manually cancelled by the user,
o WARNING: the workflow or the activity execution is correctly finished but has thrown warning’s),
o FAILED: the workflow or the activity execution has failed,
o SUCCESSFUL: the workflow or the activity execution is correctly finished without warning.
· Progress: workflow or the activity progress percentage,
· Start time: workflow or the activity start time,
· End time: workflow or the activity end time
· Duration: workflow or the activity duration,
· Owner: user which has been submitted the workflow or the activity
· Id: workflow or the activity identifier,
· Execution host: host on which runs the workflow or the activity.
For each workflow, the child activities are displayed with the associated status.
For ach activity, the child jobs are listed with the associated status.
The Jobs view offers the following filter capabilities:
|
Allows to show/hide the workflows |
|
|
Allows to show/hide the standalone activities |
|
|
Allows to show/hide the workflows and activities having the CREATED status |
|
|
Allows to show/hide the workflows and activities having the RUNNING status |
|
|
Allows to show/hide the workflows and activities having the STOPPED status |
|
|
Allows to show/hide the workflows and activities having the SUCCESSFUL status |
|
|
Allows to show/hide the workflows and activities having the WARNNING status |
|
|
Allows to show/hide the workflows and activities having the FAILED status |
|
|
Allows to show/hide the workflows and activities which belong to the current logged user |
|
|
Allows to show/hide the workflows and activities which do not belong to the current logged user |
|
|
Allows to filter using
a Java regular expression |
In addition, the Jobs view offers the following buttons:
|
Allows to start the
execution of the selected workflow or activity |
|
|
Allows to cancel the
execution of the selected workflow or activity |
|
|
Allows to remove the
execution of the selected workflow or activity |
The Workflow Representation view allows to visualize a graphical representation of the running workflow or standalone activity:
Figure 29 : Workflow Representation view
The workflow activities are displayed in a specific color according to its status (each color is configurable through User Preferences management):
· Selected,
· Configured
For each activity of the displayed workflow, the progress percentage is displayed.
By selecting an activity, it is possible to visualize its configuration in the Activity Parameters view (See §3.4.3).
The Activity Parameters view displays the parameters assigned for the activity selected in the Workflow Representation view:
Figure 30 : Activity Parameters view
It is possible to edit the activity parameters if and only if the concerned activity has one of the following states: CREATED, CANCELLED or FAILED.
The Error Information view displays the potential errors occurred during the execution of the activity selected in the Workflow Representation view:
Figure 31 : Error Information view
The Error Information view is filled as soon as the activity is executed with error(s) or warning(s) (i.e. its state is equal to WARNING or FAILED).
The Execution Information view displays any concerning the execution of the activity selected in the Workflow Representation view:
Figure 32 : Execution Information view
The Execution Information view is filled as soon as the activity execution is finished (i.e. its state is equal to SUCCESSFUL, WARNING or FAILED).
The Submit File view displays the information concerning the parameters of the execution of the activity selected in the Workflow Representation view:
Figure 33 : Submit File view
The Error Information view is filled as soon as the activity execution is started (i.e. its state is not CREATED).
The Platform Management perspective allows to configure the unitary cameras and cameras compounds:
Figure 34 : Platforms perspective
The Platform Management perspective is composed with the following views:
· the Cameras explorer
· the Camera editor
If no project is open, the Cameras explorer lists all available cameras compounds. If a project is open, the Cameras explorer filters, by default, the cameras compounds used in the open project.
Figure 35 : Cameras explorer
The Cameras explorer offers the following buttons
|
Allows to filter /
un-filter the cameras compounds associated to the open project |
|
|
Allows to add a new unitary
camera in the selected camera compound |
|
|
Allows to create a new camera compound |
|
|
Allows to remove the
selected unitary sensor |
|
|
Allows to remove the
selected camera compound |
|
|
Allows to copy the
selected element |
|
|
Allows to paste the
copied element |
The Camera editor allows to display the settings of the selected camera compound of the selected unitary camera:
Figure 36 : Camera editor
The Camera editor is a generic editor: it is generated according to the activity definition given by the StreetFactory server (see Street Factory server for more information).
The Logs perspective displays the events logged by the StreetFactory:
Figure 37 : Logger messages panel
For each logged event, the following details are displayed:
· Level: the event level represented by an icon:
|
|
Debug level |
|
Information level |
|
|
Warning level |
|
|
Error level |
|
|
Fatal level |
· Date: the event generation,
· Message: the event description.
The Logs perspective offers the following filter capabilities:
|
|
Allows to show / hide the events having the Debug level |
|
Allows to show / hide the events having the Information level |
|
|
Allows to show / hide the events having the Warning level |
|
|
Allows to show / hide the events having the Error level |
|
|
Allows to show / hide the events having the Fatal level |
|
|
Allows to filter using
a Java regular expression |
The Projections and Datum perspective allows to manage the custom datum and projections of the StreetFactory application:
Figure 38 : Projections and Datum perspective
The Projections and Datum perspective is composed with the following views:
· the Custom Datum explorer,
· the Custom Projections explorer,
· the Custom Datum editor,
· the Custom Projections explorer,
The Custom Datum explorer allows to manage the Custom Datum available in StreetFactory application.
Figure 39 : Datum explorer
The Datum explorer offers the following buttons
|
Allows to add a new custom datum |
|
|
Allows to delete the selected datum |
|
|
Allows to duplicate the selected datum |
The Custom Datum explorer allows to manage the Custom Projections available in StreetFactory application.
Figure 40 : Projection Explorer panel
The Projections explorer offers the following buttons:
|
Allows to add a new custom projection |
|
|
Allows to delete the
selected projection |
|
|
Allows to duplicate the
selected projection |
The Custom Datum editor allows to edit the settings of a newly created custom datum and to save it.
Figure 41 : Custom Datum editor
The settings of a custom datum are:
· Name: the datum name,
· Content: the datum content as a characters string.
The Custom Datum editor does not allow to edit the settings of an existing custom datum.
The Custom Projection editor allows to edit the settings of a newly created custom projection and to save it.
Figure 42 : Custom Projection editor
The settings of a custom datum are:
· Name: the projection name,
· Content: the projection content as a characters string.
The Custom Projection editor does not allow to edit the settings of an existing custom projection.
The Blocks perspective allows to manage the blocks of the open project:
Figure 43 : Block Sequence view
The Blocks perspective is composed with the following views:
· the Blocks explorer,
· the Blocks / Images Links editor,
· the Blocks Sigma editor.
The Block explorer lists all the blocks of the open project:
Figure 44 : Block Explorer panel
The blocks are listed according the optimization sequence. It is possible to change this sequence using the following buttons available in the explorer:
|
Allows the move the selected block(s) at the beginning
of the optimization sequence |
|
|
Allows the move up the selected block(s) in the
optimization sequence |
|
|
Allows the move down the selected block(s) in
optimization sequence |
|
|
Allows the move the selected block(s) at the end of
the optimization sequence |
For each block,
· the number of linked images is given (G: XX)
· the number of not linked images is given (R: XX)
The Blocks / Images Links editor allows the link / unlink images to the block:
Figure 45 : Blocks / Image Links editor
The Blocks / Images Links editor lists for, the block currently selected in the Blocks explorer:
· the images from the open project datasets which are linked with the current block (in green),
· the images from the open project datasets which are not linked with the current block (in red).
The Blocks / Images Links editor offers the images filtering capabilities:
|
Show / hide the images linked with the current block |
|
|
Show / hide the images not linked with the current block |
|
|
Show / hide the image of the selected camera(s) |
It is possible to link / unlink images with the current block using the following buttons available in the Blocks / Images Links editor:
|
Allows the link the selected image(s) with the block
currently selected in the Block explorer |
|
|
Allows the unlink the selected image(s) from the block currently selected in the Block explorer (Available only if at least an image is selected) |
The Blocks Sigma editor allows to edit the sigma parameter of the block currently selected in the Block explorer:
Figure 46 : Block Sigma editor
Each sigma parameter can be modified by modifying its double value.
The Rules perspective allows to manage the parsing rules for metadata file (Images and GCP) import.
Figure 47 : TPR Loader view
The Rules perspective is composed with the following views:
· the Images rules explorer,
· the GCP rules explorer,
· the Rules editor.
The Images Rules explorer allows to manage the Images metadata parsing rules:
Figure 48 : Images Rules explorer
The Images Rules explorer offers the following buttons
|
Allows to export the
selected image rule in a XML file |
|
|
Allows to import an Image rule from an XML file |
|
|
Allows to create a new image rule |
|
|
Allows to delete the
selected image rule |
|
|
Allows to duplicate the
selected image rule |
The CGP Rules explorer allows to manage the GCP metadata parsing rules:
Figure 49 : GCP Rules explorer
The CGP Rules explorer offers the following buttons
|
Allows to export the
selected GCP rule in a XML file |
|
|
Allows to import an GCP rule from an XML file |
|
|
Allows to create a new GCP rule |
|
|
Allows to delete the
selected GCP rule |
|
|
Allows to duplicate the
selected GCP rule |
The Rules editor allows to display and edit the setting of the rule selected in the Image or CGP Rules explorer:
Figure 50 : Rules editor
The settings of a custom datum are:
· Type: the type of the rule (Image or GCP),
· Name: the name of the rule,
· File pattern: regular expression giving the name of the files which can be parsed with this rule,
· Source file: an example file allowing to illustrate / configure the parsing rule,
· Start line: the first line of the input file which containing data,
· Delimiters: the character(s) separating the fields in the input file,
· Ignore empty lines: indicates if the parsing must ignore the empty lines,
· Ignore the lines starting with: characters string giving the prefix for comment lines to ignore,
· Ignore multi-delimiters: indicates if multi-delimiters must be ignored,
· Ignore white space: indicates if white spaces must be ignored in the fields parsing,
· For each field of the rule:
o Column number: the index of the column where the field is stored in the input file (the first column has the index number 1),
o Unit or Format: the fields unit or the date/time format if the field represents a time,
o Subfield: Optional extraction information containing
§ a secondary delimiter allowing to split the field,
§ a field selection allowing to choose the subfield(s) to extract: For examples:
· 1: allows to extract only the first subfield
· 1,3: allows to extract only the first and the third subfields,
· 1-3: allows to extract the three first subfields.
§ a filter specifying the first index and the last index of the substring to take into account from the extracted subfield(s)
Figure 51 : Subfield extraction panel
The Drivers perspective allows to manage the drivers available in the StreetFactory application:
Figure 52 : Drivers perspective
The Drivers perspective is composed with the following views:
· the Drivers explorer,
· the Driver editor.
The Driver explorer lists the metadata drivers available in StreetFactory application.
Figure 53 : Drivers explorerl
The Projections explorer offers the following buttons:
|
Allows to create a new metadata driver rule |
|
|
Allows to delete the
selected metadata driver |
|
|
Allows to duplicate the
selected metadata driver |
The Driver editor allows to display and configure the settings of the driver selected in the Drivers explorer.
Figure 54 : Driver Edition panel
The settings of a custom datum are:
· Name: the driver name,
· Rule name: the name of the rule associated to the driver,
· Camera name: the name of the compound camera associated to the driver,
· Conditioners: the ordered list of conditioners of the driver.
The Monitoring perspective allows to monitor the StreetFactory application. This perspective is composed with the following views:
· The Server Montoring view,
· The Cluster Nodes Status view.
The Server Monitoring view allows to display an HTML page (generated at StreetFactory server side by Ganglia) containing the information to monitor the StreetFactory server.
Figure 55 : Server Monitoring HTML page
See StreetFactory server documentation for more details.
The Cluster Nodes Status view allows to display the state of the computation nodes used by StreetFactory server.
Figure 56 : Cluster Nodes Status view
The Cluster Nodes Status view displays in two different tables:
· the machines status,
· the jobs status.
The content of these tables is generated by the StreetFactory server. See StreetFactory server documentation for more details.
The Terminal perspective allows to simulate a command line window.
Figure 57 : Terminal perspective
Under Windows operating system, the Terminal perspective can be used as a windows cmd shell.
Under Linux operating system, the Terminal perspective simulates a sh shell. In this case, some commands are forbidden (vi, vim, more, cmd, cmd.exe.sh, bash).
Remark: If a project is open for the first opening of the Terminal perspective, the open project path is set as current path of the terminal.
The Image Viewer perspective allows to display image(s) from the open project.
Figure 58 : Image Viewer perspective
There are two means to display images in the Image Viewer perspective:
· by loading image(s) directly in the Image Viewer perspective,
· by loading image from the Selection view (See 3.2.6),
· by loading image(s) from the Dataset editor (see).
The Image Viewer perspective offers the following buttons:
|
Allows to open image file(s) from the file system |
|
|
Allows to zoom in the
displayed image |
|
|
Allows to zoom out the
displayed image |
Remark: The format of images which can be loaded in the Image Viewer perspective are:
· JPEG,
· TIFF
· GeoTIFF.
The StreetFactory distribution is provided with the following external tools, accessible via the tools bar:
|
MosaicEditor |
|
|
AsvGeoViewer: |
|
|
Bundle View (only available under Linux operating system) |
It is possible to add other external tools via the plugin system (see [] for more information).
MosaicEditor is a tool used to extract a portion of the mesh and to save it as an individual file.
The tiles selected in the Map view shall be used as input for the MosaicEditor external tool.
AsvGeoViewer is a tool used to visualize 3D reconstruction.
The tiles selected in the Map view shall be used as input for the AsvGeoViewer external tool.
BundleView is a tool used to filter, optimize and edit tie points for the Bundle Adjustment process.
The block selected in the Map view is used as input for the BundleView external tool. If no block is selected, or if more than several blocks are selected, BundleView tool can’t be launched.
The other features are accessible via the tools bar:
|
Users Management |
|
|
User’s Preferences |
|
|
About |
The User Management feature allows to display and edit projects accesses by users.
Figure 59 : Users management view
For a user or a set of users, it is possible to view the assigned project(s), using the check box before the project name:
|
The project is not affected to any of the selected users |
|
|
The project is not affected to a least one of the selected users |
|
|
The project is not affected to all selected users |
It is also possible to modify the project(s) assignment of the selected user(s), by checking / unchecking the check box before the project name.
Remark: The General Information panel at the right of the User Management view shows the details of the focused project (these details are in read-only mode).
The user’s preferences allow to customize some feature of StreetFactory client.
Figure 60 : Preferences view
The user’s Preferences define the following sections:
· Colors,
· Capabilities.
For each user’s preference, a default value is hard coded. This default value can be restored at any time.
The user’s preferences are stored in the application workspace chosen at application start (see §2.1).
The Colors section allows to configure the colors used in StreetFactory client:
· the colors of AOIs displayed in the Map view,
· the colors of images footprints according to the state of the corresponding dataset: IMPORTED, IN_PROCESSING,
· the colors of blocks displayed in the Map view according the block state: CREATED , GEOMETRY_EXPORTED, GEOMETRY_EXPORTING, OPTIMIZED, OPTIMIZING, PICKTIEPOINTED, PICKTIEPOINTING, RECTIFIED, RECTIFYING, VALIDATED,
· the colors of the tiles displayed in the Map view according the tile state: CREATED, DATA_PACKAGE_COMPLETED, DATA_PACKING, GENERATING_POINT_CLOUDS, GLOBAL_MESH_COMPLETED, GLOBAL_MESHING, MESH_TEXTURE_COMPLETE, OUTPUT_GEO_COMPLETED, OUTPUT_OSGB_COMPLETED, OUTPUTING_GEO, OUTPUTING_OSGB, POINT_CLOUDS_COMPLETE, REFINE_MESH_COMPLETED, REFINE_MESHING, SELECT_PAIRS_COMPLETED, SELECTING_PAIRS, SIMPLIFY_MESH_COMPLETED, SIMPLIFY_MESHING, TEXTURING,
· the color of an activity in the Workflow Representation view according to its state: NOT_CONFIGURED, CONFIGURED.
The Capabilities section allows to configure the visibility of the features in StreetFactory client:
· the visibility of available workflows,
· the visibility of available activities,
· the visibility of available external tools.
The Other section allows to manage:
· the size of the sample extract displayed in Rules editor (see §3.9.3) by specifying
o a header size defining the number of lines to display before the configured start line,
o a footer size defining the number of lines to display after the configured start line,
· the maximum number of events displayed in the Logs perspectives.
The About window allows to display information about StreetFactory installation.
Figure 61 : About window
The StreetFactory application version is displayed in the window header,
The StreetFactory server version is displayed,
The version of the installed StreetFactrory client plugins is displayed.
The StreetFactory application comes with a contextual online help which by be activated using the shortcut F1.
Figure 62 : Online Help
When clicking on F1, the help is opened on the page corresponding to the perspective on which the user was and if the user goes to another perspective while the help is still open, then the help page is updated to this new open perspective.
A table of contents is also provided to allow the user to easily navigate through the user manual.
The toolbar provides the home button which allows coming back to the first page of the manual.
Figure 63 : Help Home page
APPENDIX 1: Java regular expressions
A regular expression defines a search pattern for strings. The search pattern can be anything from a simple character, a fixed string or a complex expression containing special characters describing the pattern. The pattern defined by the regular expression may match one or several times or not at all for a given string.
A simple example for a regular expression is a (literal) string. For example, the Hello World regular expression will match the "Hello World" string. “.” (dot) is another example for a regular expression. A dot matches any single character; it would match, for example, "a" or "z" or "1".
The following tables lists several example regular expressions and describes which pattern they would match.
|
Matches |
|
|
this is text |
Matches exactly "this is text" |
|
this\s+is\s+text |
Matches the word "this" followed by one or more whitespace characters followed by the word "is" followed by one or more whitespace characters followed by the word "text". |
|
^\d+(\.\d+)? |
^ defines that the patter must start at beginning of a new line. \d+ matches one or several digits. The ? makes the statement in brackets optional. \. matches ".", parentheses are used for grouping. Matches for example "5", "1.5" and "2.21". |
The following description is an overview of available meta characters which can be used in regular expressions. This chapter is supposed to be a references for the different regular expression elements.
|
Regular Expression |
Description |
|
. |
Matches any character |
|
^regex |
Finds regex that must match at the beginning of the line. |
|
regex$ |
Finds regex that must match at the end of the line. |
|
[abc] |
Set definition, can match the letter a or b or c. |
|
[abc][vz] |
Set definition, can match a or b or c followed by either v or z. |
|
[^abc] |
When a caret appears as the first character inside square brackets, it negates the pattern. This ccontent/an match any character except a or b or c. |
|
[a-d1-7] |
Ranges: matches a letter between a and d and figures from 1 to 7, but not d1. |
|
X|Z |
Finds X or Z. |
|
XZ |
Finds X directly followed by Z. |
|
$ |
Checks if a line end follows. |
The following meta characters have a pre-defined meaning and make certain common patterns easier to use, e.g., \d instead of [0..9].
|
Description |
|
|
\d |
Any digit, short for [0-9] |
|
\D |
A non-digit, short for [^0-9] |
|
\s |
A whitespace character, short for [ \t\n\x0b\r\f] |
|
\S |
A non-whitespace character, short for [^\s] |
|
\w |
A word character, short for [a-zA-Z_0-9] |
|
\W |
A non-word character [^\w] |
|
\S+ |
Several non-whitespace characters |
|
\b |
Matches a word boundary where a word character is [a-zA-Z0-9_]. |
A quantifier defines how often an element can occur. The symbols ?, *, + and {} define the quantity of the regular expressions:
|
Regular Expression |
Description |
Examples |
|
* |
Occurs zero or more times, is short for {0,} |
X* finds no or several
letter X, |
|
+ |
Occurs one or more times, is short for {1,} |
X+ - Finds one or several letter X |
|
? |
Occurs no or one times, ? is short for {0,1}. |
X? finds no or exactly one letter X |
|
{X} |
Occurs X number of times, {} describes the order of the preceding liberal |
\d{3} searches for three digits, .{10} for any character sequence of length 10. |
|
{X,Y} |
Occurs between X and Y times, |
\d{1,4} means \d must occur at least once and at a maximum of four. |
|
*? |
? after a quantifier makes it a reluctant quantifier. It tries to find the smallest match. This makes the regular expression stop at the first match. |
END OF DOCUMENT


“im sorry, its a girl” said the doctor to the father.
“no, im sorry, youre a sexist” said the girl child to the world
Adhiraj Singh
These stories belong to the authors whose names appear below them, who reserve all the rights to them.


--- layout: default title: No idea what this page is... ---
Hello. I see you have found the homepage of this website. Good job!
What did you expect to find here, other than a snarky comment congratulating you?
Perhaps a nice gif or something? Well, if you insist...


--- layout: base --- {% include banner.html %}
You might want to double-check your link and try again. (404)


Nowadays people are paying more and more attention to their health and diets. Choosing the correct foods to meet your personal diet plan and to achieve your physique goals is not always easy. Quantitative nutritional information is now openly accessible from this interactive webpage, allowing everyone and anyone to create nutritious and achievable menus at home or on the go.


procedure InitializeSurface(NewWidth, NewHeight: Integer; ClearBuffer: Boolean); virtual; abstract;
Initializes the surface with the dimensions of NewWidth x NewHeight both measured in pixels. Each pixel has to be 4 byte (ARGB) in size. The allocated memory has to be contiguous with the stride being the length of NewWidth. GR32 currently does not support stride lengths different from the width of the new surface. The pointer to the allocated memory has to be written to the protected member FBits.
The ClearBuffer parameter determines whether clearing the buffer is required or not.
This method is called internally by the default ChangeSize method implementation of TBackend.
New back-end classes need to implement this method to do their internal allocation of memory for the surface.


--- title: Faster PHP Apps - Profile Your Code with Xdebug date: 2007-04-23 14:08:52 +1000 modified: 2007-04-24 00:08:52 +1000 uid: http://paul.annesley.cc/articles/2007/04/24/faster-php-apps-profile-your-code-with-xdebug layout: post ---
Using Xdebug and WinCacheGrind or KCacheGrind to profile PHP script execution.
read more | digg story


 The reason: many farms use crowded pens where salmon are easily infected with lice, may be treated with antibiotics and can spread disease to wild fish (one reason Alaska has banned salmon farms). In addition, it can take as much as three pounds of wild fish (and fishmeal) to raise one pound of salmon.
    One of the main reasons I buy Salmon Cookies is because the calorie count is 180, keeping me under my 200 breakfast limit that I try to keep. They actually taste like an oatmeal cookie and are sooo yummy. Upon opening the package, they don't seem terribly large, but one cookie really does fill me up. I love these things and wish they were easier to find. I was thrilled to see them available for Prime Pantry. These breakfast cookies are perfect for on the go and this was the easy breakfast of choice when my family go on vacation.
Monday - Tuesday: OFF
Wednesday - Sunday: 8am - 6pm


Home
About Us
Listings
Welcome to Home Listings!
A variety of home listings around New York
Few Words About Us
Handpicked Craigslist listings from different cities in NY.
Listings
Various home listings sorted by city
All
Binghamton
Buffalo
Niagra
Poughkeepsie
Rochester
Rome
Syracuse
Utica
Watertown
12 bed Student House
$525/month/pp
2 Bedroom
1044 Kenmore Avenue
Brand New Town Home
$1950/month rent
4 Bed Country House
$1000/ month rent
Orange Commons
$900/month rent 3 Br


{{+bindTo:partials.standard_nacl_article}}
NOTE:
Deprecation of the technologies described here has been announced
for platforms other than ChromeOS.
Please visit our
migration guide
for details.
This glossary defines terms and names commonly used throughout the Native Client documentation.
width=0
and height=0
, which means that nothing is
drawn on the page).postMessage()
to send
messages. The way a web page interacts with a Native Client module
is analogous to the way it interacts with web workers.


Functions | |
| grib_iterator * | grib_iterator_new (grib_handle *h, unsigned long flags, int *error) |
| Create a new iterator from a handle, using current geometry and values. | |
| int | grib_iterator_next (grib_iterator *i, double *lat, double *lon, double *value) |
| Get the next value from an iterator. | |
| int | grib_iterator_previous (grib_iterator *i, double *lat, double *lon, double *value) |
| Get the previous value from an iterator. | |
| int | grib_iterator_has_next (grib_iterator *i) |
| Test procedure for values in an iterator. | |
| int | grib_iterator_reset (grib_iterator *i) |
| Test procedure for values in an iterator. | |
| int | grib_iterator_delete (grib_iterator *i) |
| Frees an iterator from memory. | |
| grib_nearest * | grib_nearest_new (grib_handle *h, int *error) |
| Create a new nearest from a handle, using current geometry . | |
| int | grib_nearest_find (grib_nearest *nearest, grib_handle *h, double inlat, double inlon, unsigned long flags, double *outlats, double *outlons, double *values, double *distances, int *indexes, size_t *len) |
| Find the 4 nearest points of a latitude longitude point. | |
| int | grib_nearest_delete (grib_nearest *nearest) |
| Frees an nearest from memory. | |
| int | grib_nearest_find_multiple (grib_handle *h, int is_lsm, double *inlats, double *inlons, long npoints, double *outlats, double *outlons, double *values, double *distances, int *indexes) |
| Find the nearest point of a set of points whose latitudes and longitudes are given in the inlats, inlons arrays respectively. |
| int grib_iterator_delete | ( | grib_iterator * | i | ) |
Frees an iterator from memory.
| i | : the iterator |
| int grib_iterator_has_next | ( | grib_iterator * | i | ) |
Test procedure for values in an iterator.
| i | : the iterator |
| grib_iterator* grib_iterator_new | ( | grib_handle * | h, | |
| unsigned long | flags, | |||
| int * | error | |||
| ) |
Create a new iterator from a handle, using current geometry and values.
| h | : the handle from which the iterator will be created | |
| flags | : flags for future use. | |
| error | : error code |
| int grib_iterator_next | ( | grib_iterator * | i, | |
| double * | lat, | |||
| double * | lon, | |||
| double * | value | |||
| ) |
Get the next value from an iterator.
| i | : the iterator | |
| lat | : on output latitude in degree | |
| lon | : on output longitude in degree | |
| value | : on output value of the point |
| int grib_iterator_previous | ( | grib_iterator * | i, | |
| double * | lat, | |||
| double * | lon, | |||
| double * | value | |||
| ) |
Get the previous value from an iterator.
| i | : the iterator | |
| lat | : on output latitude in degree | |
| lon | : on output longitude in degree | |
| value | : on output value of the point* |
| int grib_iterator_reset | ( | grib_iterator * | i | ) |
Test procedure for values in an iterator.
| i | : the iterator |
| int grib_nearest_delete | ( | grib_nearest * | nearest | ) |
Frees an nearest from memory.
| nearest | : the nearest |
| int grib_nearest_find | ( | grib_nearest * | nearest, | |
| grib_handle * | h, | |||
| double | inlat, | |||
| double | inlon, | |||
| unsigned long | flags, | |||
| double * | outlats, | |||
| double * | outlons, | |||
| double * | values, | |||
| double * | distances, | |||
| int * | indexes, | |||
| size_t * | len | |||
| ) |
Find the 4 nearest points of a latitude longitude point.
The flags are provided to speed up the process of searching. If you are sure that the point you are asking for is not changing from a call to another you can use GRIB_NEAREST_SAME_POINT. The same is valid for the grid. Flags can be used together duing an or.
| nearest | : nearest structure | |
| h | : handle from which geography and data values are taken | |
| inlat | : latitude of the point to search for | |
| inlon | : longitude of the point to search for | |
| flags | : GRIB_NEAREST_SAME_POINT, GRIB_NEAREST_SAME_GRID | |
| outlats | : returned array of latitudes of the nearest points | |
| outlons | : returned array of longitudes of the nearest points | |
| values | : returned array of data values of the nearest points | |
| distances | : returned array of distances from the nearest points | |
| indexes | : returned array of indexes of the nearest points | |
| len | : size of the arrays |
| int grib_nearest_find_multiple | ( | grib_handle * | h, | |
| int | is_lsm, | |||
| double * | inlats, | |||
| double * | inlons, | |||
| long | npoints, | |||
| double * | outlats, | |||
| double * | outlons, | |||
| double * | values, | |||
| double * | distances, | |||
| int * | indexes | |||
| ) |
Find the nearest point of a set of points whose latitudes and longitudes are given in the inlats, inlons arrays respectively.
If the flag is_lsm is 1 the nearest land point is returned and the grib passed as handle (h) is considered a land sea mask. The land nearest point is the nearest point with land sea mask value>=0.5. If no nearest land points are found the nearest value is returned. If the flag is_lsm is 0 the nearest point is returned. values, distances, indexes (in the "values" array) for the nearest points (ilons,ilats) are returned.
| h | : handle from which geography and data values are taken | |
| is_lsm | : lsm flag (1-> nearest land, 0-> nearest) | |
| inlats | : latitudes of the points to search for | |
| inlons | : longitudes of the points to search for | |
| npoints | : number of points (size of the inlats,inlons,outlats,outlons,values,distances,indexes arrays) | |
| outlats | : returned array of latitudes of the nearest points | |
| outlons | : returned array of longitudes of the nearest points | |
| values | : returned array of data values of the nearest points | |
| distances | : returned array of distances from the nearest points | |
| indexes | : returned array of indexes of the nearest points |
| grib_nearest* grib_nearest_new | ( | grib_handle * | h, | |
| int * | error | |||
| ) |
Create a new nearest from a handle, using current geometry .
| h | : the handle from which the iterator will be created | |
| error | : error code |


Get Numeric Analysis Information Use-Case.Description:Gets information about the created numerical analysis.Assumptions:Success of [Create Analysis].Exceptions:None.


A such amaze voice controlled browser game that is not so 2010.
Please make doge happy by a simple wow tweet. Thx much.
*Works best in Chrome, microphone access dependent.
Tweet
Ready your mic..
@hoppydoge is crafted with such love for #staticshowdown
Built in less than 48 hours by
@acedimasuhid ,
@rbmrclo ,
@iallenchun ,
@samrosecruz.


A simple log writer implementation with different levels and standard formatting. Messages written is appended to level and timestamp. You can turn off unwanted categories by modifiying the table at log.categories.
For messages shorter than 4096 bytes a static buffer is used to improve performance. C time.h functions are used as Lua builtin’s is not compiled by LuaJIT. This statement applies to all log functions, except log.dump.
Example output: [S 2013/07/15 18:58:03] [web.lua] 200 OK GET / (<IP_ADDRESS>) 0ms
To enable or disable categories, modify the table in turbo.log.categories.
As default, it is declared as such:
log = {
["categories"] = {
-- Enable or disable global log categories.
-- The categories can be modified at any time.
["success"] = true,
["notice"] = true,
["warning"] = true,
["error"] = true,
["debug"] = true,
["development"] = false
}
}
Log to stdout. Success category. Use for successfull events etc. Messages are printed with green color.
| Parameters: | str (String) – Log string. |
|---|
Log to stdout. Notice category.  Messages are printed with white color.
| Parameters: | str (String) – Log string. |
|---|
Log to stderr. Warning category. Use for warnings. Messages are printed with yellow color.
| Parameters: | str (String) – Log string. |
|---|
Log to stderr. Error category. Use for critical errors, when something is clearly wrong. Messages are printed with red color.
| Parameters: | str (String) – Log string. |
|---|
Log to stdout. Debug category. Use for debug messages not critical for releases.
| Parameters: | str (String) – Log string. |
|---|
Log to stdout. Development category. Use for development purpose messages. Messages are printed with cyan color.
| Parameters: | str (String) – Log string. |
|---|
Stringify Lua table.
| Parameters: |
|
|---|---|
| Return type: | String |