This chapter describes the shell commands for Google Earth Enterprise Fusion. You can use the shell commands to set up an automated environment to build and deliver databases from frequently updated or new source data.
In addition, if you have a large number of sources to process, you can build a command line script to add them rather than adding them individually using the Google Earth Enterprise Fusion GUI.
Note: The commands included in previous releases that began with kh have all been changed to begin with ge since version 3.0. They are documented by their new names in this guide.
A feature of an automated system is the ability to optimize your work at all phases of data collection--resource, project, and database definition. You can:
You can use the Google Earth Enterprise Fusion shell commands to access all components in each building phase of a servable set of GIS data. This appendix provides a list of commands grouped by component--resource, project, or database--and then describes each command in an alphabetical listing. In addition to the information in this appendix, you can determine each command’s usage by simply entering the command with the --help
option, for example
genewimageryresource --help
This appendix uses the following typographic conventions:
Italic
|
Information that the user must supply |
| Bold | Text that the user must type exactly as shown |
| Ellipsis ... | Parameter that can be repeated several times in a command line |
| Square brackets [ ] | Optional items |
| Curly braces { } with options separated by pipes |; for example: {even | odd} | Set of choices from which the user can select only one |
| Parentheses ( ) | Grouped items that function together. |
Courier font
|
Code or program output |
This section describes the commands you can use to define and modify terrain, imagery, and vector resources from the command line:
You can use these commands for bulk processing when you have large quantities of data to process. See the Defining Resources chapter for more information.
When defining and modifying resources, keep these points in mind:
modify
commands (gemodifyimageryresource
, gemodifyterrainresource
, or gemodifyvectorresource
) and specify a resource that does not exist, Google Earth Enterprise Fusion creates a new resource with the name you specify.
modify
command to change properties for an existing resource. If you use the one of the new
(genewimageryresource
, genewterrainresource
, or genewvectorresource
) commands and a resource with the name and type you specify already exists, the command fails.
When you define an imagery or terrain resource, the source file must include geo-reference information. Typically the coordinate and projection information is part of the imagery file itself (as with a GeoTIFF file, for example). However, if your imagery source file does not contain geo-coordinate information, you must provide it in a separate external file. (See Special Cases in the Defining Resources chapter for details about external files.)
If you purchase preprocessed imagery or terrain data from Google or receive preprocessed data from another Google Earth Enterprise Fusion user, it arrives as a complementary pair of folders. These folders share the same name but have different extensions. Folders with a .kip
extension are imagery data. Folders with a .ktp
extension are terrain data. Folders with a .kmp
extension are mask files. Folders with a .kvp
extension are vector data.
You must use the Google Earth Enterprise Fusion command line tools to add preprocessed data to your asset root. The command line tools for importing preprocessed data are:
These commands have similar options and parameters.
You must specify the --havemask option to correctly import the preprocessed mask files with the imagery. You can associate provider copyright information with the resource by specifying the --provider option and the appropriate provider key. You specify the resource name and target location in the asset tree with the -o
option (for example: -o assets/imagery/north_america/usa/ca/usgsLandSat
), followed by the full path to the source data.
cd /gevol/assets
Tip: Although this step is not necessary, it allows you to use auto-completion (pressing TAB after typing the first few letters of a file name) on the command line, which helps you avoid typographical errors.
genewimageryresource
command, for example:genewimageryresource --provider <PROVIDER_KEY> --havemask -o path/to/resource/directory/resourcename /path/to/imagery.kip
Google Earth Enterprise Fusion defines the resource.
cd /gevol/assets
genewimageryresource
command, for example:genewterrainresource --provider <PROVIDER_KEY> --havemask -o path/to/resource/directory/resourcename /path/to/terrain.kip
Google Earth Enterprise Fusion defines the resource.
After defining resources, the next phase in producing a Google Earth database involves defining projects and adding resources to them. For your database, you can define up to three different projects--imagery, terrain, and/or vector.
This section describes the commands you can use to define and modify terrain, imagery, and vector projects from the command line:
As with resource commands, you can use these commands for bulk processing when you have large quantities of data to process. See Defining Projects for more information.
When defining and modifying resources, keep these points in mind:
modify
commands as a single command to achieve this operation, rather than having to use the addto
or dropfrom
commands to change the resources in an existing project. That is, when you use the project modification command, the resources you specify replace the previous set of resources for that project.
addto
command to add resources to an existing project. To add resources to a project that has not yet been defined, use the new
command.
This section describes the commands you can use to define and modify terrain, imagery, and vector databases from the command line:
As with resource and project commands, you can use these commands for bulk processing when you have large quantities of data to process. See Defining a Database for more information.
Before publishing your project and resource data to a Google Earth Enterprise Server, you must define a database. A database typically contains at least a single project--imagery, terrain, or vector. It can contain one project of each type for a total of three projects.
When you define a database without one of the three project types, that project type is supplied by the default project data specified in your Google Earth Enterprise Fusion system configuration. For example, if you define a database using your own imagery and terrain projects, but you supply no vector project, the default vector project is used. (See the Google Earth Enterprise Administration Guide for a description of the default project settings.)
Tip: The gemodifydatabase
command exists as a convenience when you must redefine the projects for a given database. However, it is not recommended that you use this command to repeatedly redefine the projects for a single database. For example, if you want to view different vector data projects in relationship to the same imagery and terrain projects, you should define two separate databases with different vector projects rather than repeatedly redefining the same database in order to switch vector data.
This section describes the commands you can use to build any type of asset--resource, map layer, project, or database--from the command line:
Google Earth Enterprise Fusion allows you the flexibility of building the entire database and its components at the same time or building the individual components one at a time. This flexibility is particularly useful when source data updates become available at varying times, and you want to build some components before other components are updated.
When you define or modify a resource, you are defining the source file and configuration settings for the resource. When you build the resource, you are using those settings to actually produce the resource itself, which is a group of related files that are the result of this processing.
You can use the gecancel
command to cancel a build that is in progress. If, for example, you realize that you’ve specified an incorrect value for the configuration of a resource that is already building, you can use this command to stop the build.
Sometimes a build fails for external reasons, such as lack of disk space or file permissions set incorrectly. When that happens, after you resolve the disk space problem, you can use the geresume
command to continue building the asset from the point at which the build failed. The purpose of the geresume
command is to continue a build on a version where there has been no change to the data itself--only changes to external factors.
On the other hand, if the build failed because of a configuration or inherent data problem, you can change the configuration of the asset (such as removing a resource from a project or changing the visibility range for a display rule). Then you must use gebuild
to rebuild the resource, since the underlying data actually changed.
Unlike the gebuild
command, geresume
does not define a new version of the resource; it rebuilds a previously failed or canceled version.
You can use the gequery
command to debug the process of building an asset when it fails to build or to find a specific version of an asset. Typically, you use the --status
parameter to determine the initial status of a particular asset.
If for some reason the asset build fails, you can use the other available querying parameters to further expose the details of the build for that asset in order to identify the specific point at which the build failed. A typical debug process involves the following steps:
gequery --dependencies imagery/Mississippi/RiverDelta
gequery
command on the failed element to view its log file.gequery --showlog imagery/Mississippi/RiverDelta/RiverDelta?version=3
Note: You can use the gequery
command for an asset or for source data.
Each time you build an asset, Google Earth Enterprise Fusion creates a new version for that asset. As a consequence, many updates to an asset can take up significant disk space. You can use the geclean
command to clean out assets whose prior versions are no longer needed and are not being referenced by other projects or databases.
For details on cleaning assets and the requirements for this process, see Cleaning Asset Versions in the Building Assets chapter.
Using the gesetbad
command, you can change the status of a resource, project, or database to Bad after it has been successfully built. This command is useful if, for example, you incorrectly configure an asset but do not realize it until after the build is complete. By marking the asset as Bad, you can prevent other users (or yourself) from building on that asset in the future.
For example, you can create two versions of an imagery resource, build them both, and preview them, and then decide which one you want to keep. You can use the gesetbad
command to prevent the rejected resource from being used to build projects and databases.
To revert the Bad status to the prior status, use the --off parameter.
After you define a database with its project components, you must build it before publishing it to the server. If you have already built some components of your database, Google Earth Enterprise Fusion does not repeat that work when it builds the database. It only builds the components that have not yet been built. However, even if all of your database components have been built prior to being added to the database, you must still build the database before publishing it.
This section describes the command you use when you are publishing a database:
After you successfully build a database, you can publish it to a stream and search server association and then view the data with Google Earth EC. See Publishing a Database for more information about publishing.
There are several commands you can use to perform various miscellaneous Google Earth Enterprise Fusion tasks from the command line, including:
geaddtoimageryproject geaddtoterrainproject --o projectname resourcename...
To add one or more resources to an existing imagery or terrain project. Use spaces between resources.
This example adds two resources to the project nySectorB
.
geaddtoimageryproject --o projects/imagery/ImageryProjectA imagery/nySector2imagery/nySector3
--o projectname
Required. Specify the name of the project relative to the asset root, for example, vector/VectorProjectA
.
resourcename
Required. Specify at least one resource to add to the project, for example, vector/VectorResourceA
.
geaddtomapproject -o projectname layername...
To add map layers to an existing map project.
geaddtomapproject -o Projects/map/MapProjectA MapLayers/SFneighborhoods
-o projectname
Required. Specify the location and name of the project relative to the asset root, for example, Projects/Map/MapProjectA
.
layername
Required. Specify the location(s) and name(s) of one or more map layers to add to the project.
geaddtovectorproject --o projectname ([--template filename] [vectorresource...])
To add one or more resources to an existing vector project.
This example adds one resource to vector project vectorTemplateB
.
geaddtovectorproject --o vector/VectorProjectA --template templates/vectorTemplateB NewYorkCityStreets
--o projectname
Required. Specify the name of the project relative to the asset root, for example, vector/VectorProjectA
.
--template filename
Required. Specify the template file that contains the display rules you want to apply to your vector layer. To create a template file, see Exporting Display Rules in the Defining Projects chapter.
vectorresource
Required. Specify one or more vector resources to add to the project relative to the asset root, for example, vector/VectorResourceA
. Google Earth Enterprise Fusion applies the specified template to each resource.
geapplylayertemplate [--displayrules] [--legend] --project projectname{--layer layername | --layerid channelid} --template filename
To apply a display rules template to a project layer. Use single quotes for names with spaces and when listing more than one layer.
geapplylayertemplate --displayrules --legend --project ‘CA Roads’ --layer CAHighways geapplylayertemplate --displayrules --project ‘CA POIs’ --layer ‘LayerA|LayerB|LayerC’
--displayrules
Optional. Include if you want to apply the display rules from the template.
--legend
Optional. Include if you want to apply the legend specifications from the template.
--project projectname
Required. Specify the name of the project that contains the layers to which you want to apply the template.
--layer layername | --layerid channelid
Optional. Specify the name of the layer(s) or channel(s) to which you want to apply the template. If omitted, Google Earth Enterprise Fusion applies the template to all layers in the specified project.
--template filename
Required. Specify the file name of the template you want to apply.
gebuild assetname
To build any type of asset (resource, map layer, project, or database).
gebuild imagery/SourceInc/MississippiDeltaRegion
assetname
Required. Specify the location and name of the asset (resource, map layer, project, or database) that you want to build relative to the asset root, for example, Projects/Vector/VectorProjectA
.
gecancel assetname [version]
To cancel a build in progress on the specified asset.
gecancel projects/TransitData/BostonTransitLines 2
assetname
Required. Specify the location and name of the asset (resource, map layer, project, or database) whose build you want to cancel relative to the asset root, for example, Projects/Vector/VectorProjectA
.
version
Optional. Specify the version number of the asset you want to cancel, or enter current
or lastgood
. If you omit the version specification, Google Earth Enterprise Fusion cancels the current version of the specified asset.
geclean assetname [version]
To clean a particular version of the specified asset.
geclean imagery/SourceInc/MississippiDeltaRegion
assetname
Required. Specify the location and name of the asset (resource, map layer, project, or database) whose version you want to clean relative to the asset root, for example, Projects/Vector/VectorProjectA
.
version
Optional. Specify the version number of the asset you want to clean, or enter current
or lastgood
. If you omit the version specification, Google Earth Enterprise Fusion cleans the current version of the specified asset.
geclearbad assetname [version]
To revert a version of an asset that has been marked as Bad to its prior status.
geclearbad projects/TransitLines/BostonTransitLines 2
assetname
Required. Specify the location and name of the asset (resource, map layer, project, or database) whose version you want to revert relative to the asset root, for example, Projects/Vector/VectorProjectA
.
version
Optional. Specify the version number of the asset you want to revert, or enter current
or lastgood
. If you omit the version specification, Google Earth Enterprise Fusion reverts the current version of the specified asset to its previous status.
gedropfromimageryproject gedropfromterrainproject gedropfromvectorproject --o projectname resourcename...
To remove one or more resources from the specified project.
gedropfromimageryproject --o projects/imagery/ImageryProjectA imagery/nySector2 imagery/nySector3
--o projectname
Required. Specify the location and name of the project relative to the asset root, for example, Projects/Vector/VectorProjectA
.
resourcename
Required. Specify the location and name of at least one resource that you want to drop from the project relative to the asset root, for example, Resources/Vector/VectorResourceA
.
gedropfrommapproject -o projectname layername...
To drop map layers from an existing map project.
gedropfrommapproject -o Projects/map/MapProjectA SFneighborhoods
-o projectname
Required. Specify the location and name of the project relative to the asset root, for example, Projects/Map/MapProjectA
.
layername
Required. Specify the name(s) of one or more map layers to drop from the project.
geexportlayertemplate --project projectname --layer layername -o templatefile
or
geexportlayertemplate --project projectname --alllayers -o outdir
To export a template from the display rules defined for one or more layers in a specific project.
geexportlayertemplate --alllayers -o fusion/templates
--project
Required. Specify the name of the project that contains the layers for which the display rules you want to export have been defined.
--layer
Required. Specify the name(s) of the layer(s) for which the display rules you want to export have been defined. You can specify more than one layer within single quotes, separated by pipes, for example:
--layer ‘folder1|folder2|layerA’
where folder1
and folder1
are folders that contain a group of layers.
-o templatefile
Required. Specify this option with the --layer
option. Enter the location and name of the directory where you want to store the template. This location can be anywhere on your network where Google Earth Enterprise Fusion has write permission.
--alllayers
Required. Specify this option if you want to export templates for all layers in separate files within the specified output folder.
-o outdir
Required. Specify this option with the --alllayers
option. Enter the location and name of the directory where you want to store the templates. This location can be anywhere on your network where Google Earth Enterprise Fusion has write permission.
geinfo [--a_srs override_srs] [--dump] [--formats] [--minmax] [--nogcp][--nometa] [--sample] [--srs override_srs] [--writeprj prjfile] [--writetfw tfwfile] input
To provide information about the specified raster file.
geinfo --writeprj projectionfile.prj myimage.tif
--a_srs override_srs
Optional. Specify the SRS to override.
--dump
Optional. Dump the contents of the raster file.
--formats
Optional. Display all supported formats in the raster file.
--minmax
Optional. Compute and display the minimum and maximum pixel values in the raster file.
--nogcp
Optional. Do not display ground control points in the raster file.
--nometa
Optional. Do not display metadata in the raster file.
--sample
Optional. Sample the pixel data in (but not print) the raster file.
--srs override_srs
Optional. Specify the SRS to override.
--writeprj prjfile
Optional. Write a PRJ file with the raster file’s projection.
--writetfw tfwfile
Optional. Write a TFW file with the raster file’s extents.
input
Required. Specify the name of the raster file on which to take the specified action(s).
gemaskgen { [--extract] [--mask] [--prep] [--preview] } { [--band num] [--debug] [--feather num] [--fill 0-255] [--formats][--holesize num] [--maxsize num] [--oformat] [--tolerance num] [--whitefill] }rasterproduct output
To create a mask file for a raster (imagery or terrain) file.
gemaskgen --mask --feather 200 raster.kip file-maskold.tif
Modes:
--extract
Optional. Specify this mode to extract the image from the specified raster file. No mask is created. The output data type matches the original image file type.
--mask
Optional. Specify this mode to generate an 8-bit mask file (the default) from the specified raster file.
--prep
Optional. Specify this mode to generate an 8-bit mask prep file from the specified raster file.
--preview
Optional. Specify this mode to generate an RGBA preview file from the specified raster file.
Options:
--band num
Optional. Specify the band number (0-based) to use for the mask and prep files. The defaults are 1 for imagery and 0 for terrain.
--debug
Optional. Read the input and compute the size of the specified raster file but not to write it to the output file.
--feather num
Optional. Specify the number of pixels to feather. The default is no feather, 0.
--fill 0-255
Optional. Specify the pixel value to treat as fill. The default is the corner colors.
--formats
Optional. Display the supported output formats.
--holesize num
Optional. Specify the minimum size of the interior holes of the fill color to be masked. The default is not to look for holes.
--maxsize num
Optional. Specify the maximum mask size. The default is 16000.
--oformat
Optional. Specify the output file format. The default is GTiff. (Use the --format
option to determine the supported formats.)
--tolerance num
Optional. Specify the deviation from the value specified for --fill
that should also be considered as fill.
--whitefill
Optional. Specify white as an additional fill color.
rasterproduct
Required. Specify the name and location of the raster file for which you want to create a mask file.
output
Required. Specify the name and location of the output file containing the mask. This location can be anywhere on your network where Google Earth Enterprise Fusion has write permission.
genewdatabase gemodifydatabase -o dbname [--imagery imgproject[?version=x]] [--terrain terrainproject[?version=x]] [--vector vectorproject[?version=x]]
To define or modify a database.
genewdatabase -o msDelta --imagery imagery/MississippiDelta?version=21 --terrain terrain/msDeltaTerrain?version=20 --vector vector/msDeltaCities
-o dbname
Required. Specify the location and name of the database relative to the asset root, for example, databaseA
.
--imagery imgproject
Optional. Specify the location and name of the imagery project relative to the asset root, for example, Projects/Imagery/ImageryProjectA
.
--terrain terrainproject
Optional. Specify the location and name of the terrain project relative to the asset root, for example, Projects/Terrain/TerrainProjectA
.
--vector vectorproject
Optional. Specify the location and name of the vector project relative to the asset root, for example, Projects/Vector/VectorProjectA
.
version=x
Optional. The version parameter can be applied to any, none, or all of the imagery, terrain, or vector project values. x
must be a valid project version to be used with the database.
genewmapdatabase gemodifymapdatabase [--meta key=value] -o dbname [--imagery imgproject] [--map mapproject] [--mercator | --flat]
To define or modify a map database.
A Flat Projection map database:
genewmapdatabase -o Databases/msDelta --imagery Projects/Imagery/MissDelta --map Projects/Map/MissWaterways
A Mercator Projection map database:
genewmapdatabase -o Databases/msDeltaMercator --imagery Projects/Imagery/MissDeltaMercator --map Projects/Map/MissWaterways --mercator
--meta key=value
Optional. This option supports any number of optional name/value pairs that you want to store for the data. For example, you might want to provide additional information about the data provider, such as the specific airplane that took the photo, or you might want to assign your confidence level with the data. If the name or value string contains white space, it should be enclosed in quotation marks.
-o dbname
Required. Specify the location and name of the map database relative to the asset root, for example, Databases/databaseA
.
--imagery imgproject
Optional. Specify the location and name of the imagery project relative to the asset root, for example, Projects/Imagery/ImageryProjectA
.
--map mapproject
Optional. Specify the location and name of the map project relative to the asset root, for example, Projects/Map/MapProjectA
.
--mercator | --flat
Optional. Default value is --flat
. Specifies the projection
of the map database. Only applies to new imagery resources. Glossary: Flat
Projection, Mercator Projection.
genewimageryproject gemodifyimageryproject genewterrainproject gemodifyterrainproject -o projectname {[--maxlevel=num] insetresource ...}
To define or modify an imagery or terrain project.
genewimageryproject -o projects/imagery/ImageryProjectAimagery/MississippiDeltaRegion
-o projectname
Required. Specify the location and name of the project relative to the asset root, for example, Projects/Imagery/ImageryProjectA
.
--maxlevel=num
Optional. Specify the maximum number of levels in the project.
insetresource
Optional. Specify the location(s) and name(s) of one or more imagery or terrain resources to add to the project.
genewmaplayer --legend=legend_name --output=map_layer_name [options] {[--template=filename] vectorresource}...
Creates a new map layer.
genewmaplayer --legend=cars --output=ca-car_map-layer --layericon=car --template=/home/doe/template_1.kmdsp Resources/Vector/cities Resources/Vector/villages --template=/home/doe/template_2.kmdsp Resources/Vector/counties
--legend=legend_name
Required. Name of the layer as it appears in a web browser.
--output=map_layer_name
Required. Name of the map layer asset as it appears in the Asset Manager.
This value is relative to the asset root and should not include an extension (eg.
Resources/Vector/counties
).
layericon=icon_name
Optional. Basename of the icon png file as it appears in the icon browser
(eg. cars
).
--default_state_on
Optional. Sets this layer's default state to 'on' in the web browser.
--template=filename
Optional. A KMDSP filename (absolute) and a corresponding vector resource (relative to asset_root and without extension). Specifies the display rules and the vector resource for a sublayer; KMDSP files can be exported from the Map Layer widget of the Fusion GUI. More than one template and vector resource pair can be specified.
genewmapproject gemodifymapproject -o projectname layername...
To define or modify a map project.
genewmapproject -o Projects/map/MapProjectA MapLayers/SFneighborhoods
-o projectname
Required. Specify the location and name of the project relative to the asset root, for example, Projects/Map/MapProjectA
.
layername
Required. Specify the location(s) and name(s) of one or more map layers to add to the project.
genewvectorproject gemodifyvectorproject -o projectname {[--template filename] vectorresource...}
To define or replace a vector project.
This example updates the PhoenixRoads project with three resources and applies an existing template to the data:
genewvectorproject --template templates/cityRoadData resources/vector/RoadData/PhoenixRoad1resources/vector/RoadData/PhoenixRoad2 resources/vector/RoadData/PhoenixRoad3
-o projectname
Required. Specify the location and name of the project relative to the asset root, for example, Projects/Vector/VectorProjectA
.
--template filename
Required. Specify the template file that contains the display rules that you want to apply to the specified resources for this project. To create a template file, see Exporting Display Rules in the Defining Projects chapter.
You can apply different templates to different resources as follows:
gemodifyvectorproject -o projects/vector/PhoenixRoads --templatetemplates/cityRoadData resources/vector/RoadData/PhoenixRoad1 resources/vector/RoadData/PhoenixRoad2 --template templates/countyRoadData resources/vector/RoadData/PhoenixRoad3 vectorresource
Optional. Specify one or more vector resources to add to the project.
genewimageryresource gemodifyimageryresource genewterrainresource gemodifyterrainresource [--havemask] [--nomask] [--mosaicfill nn,nn,nn] [--mosaictolerance n] [--band n] [--feather radius] [--feet | --scale num] [--holesize n] [--masktolerance n] [--meta name=value] [--provider key] [--sourcedate string] [--whitefill] [--srs srs_def] -o [path] resourcename {sourcefile ... | --filelist file} [--mercator | --flat]
To define or modify an imagery or terrain resource.
This example defines a single mosaic imagery resource from three source files, specifying white
as the fill value and setting the feather to 80 pixels for automask generation.
genewimageryresource --feather 80 --fill 255,255,255 --provider SourceInc --sourcedate 2003-05-10 -o imagery/MississippiDeltaRegion /vol/machine2/SourceInc/msRiver1.tif /vol/machine2/SourceInc/msRiver2.tif /vol/machine2/SourceInc/msRiver3.tif
--havemask
Optional. Use this option if you have an alpha mask or file that you want to use. The mask for your input must be located in the same folder as the source file, and the file name must match the name of the source file with -mask
appended. For example, if your source file is called NewYork.tif
, its mask file must be named NewYork-mask.tif
.
Note: You can use the --havemask
option only when you include a single source file in the resource. The mask file must be either of the same file format as the original image file, or it must be a TIFF file.
--nomask
Optional. Use this option if you do not want Google Earth Enterprise Fusion to generate an alpha mask for the resource.
--mosaicfill nn,nn,nn
Optional. Typically, you specify a fill value if you are importing several imagery files whose borders overlap in the resultant mosaic. Specify the fill value in decimal format. Height map imagery needs a signed 16-bit value (a numeric range between -32,767 and 32,767), whereas color map imagery needs a 24-bit value or a 3x8 bit color. In general, the fill color depth should match that of your source data.
--mosaictolerance n
Optional. Tolerance specifies the color range for mask selection. The default tolerance is zero, which is adequate for many fill colors that are typically pure black or pure white. However, because imagery compression and decompression can affect fill values by 1 or 2 color values, you can adjust the tolerance to compensate for any loss in precision. Typically, a setting of 1 or 2 is adequate in those situations.
If you do not specify --nomask
or --havemask
, Google Earth Enterprise Fusion automatically generates a mask. In that case, the following options are also available:
--band n
Optional. Specify the band to use when generating the auto mask. If this option is unspecified, Google Earth Enterprise Fusion uses the green channel. The legitimate values for this option are 0, 1, 2, corresponding to red, green, and blue, respectively.
--feather radius
Optional. Specify the feather value in pixels. If you omit this option, the default value is 100.
--feet |
--scale num (terrain only)
Optional. This option sets the elevation scale for your height map imagery. Google Earth Enterprise Fusion interprets height map values as meters. If the elevation unit for your data is not meters, you must use this option to provide the correct conversion number from your data’s unit to meters. For example, if your source height map file has decimeters for its height unit, you would specify .1
for the scale value in order to have the elevation represented in meters.
Alternatively, you can use the --feet
parameter as a shorthand mechanism for --scale .3048
, which represents feet units in their metric equivalent.
Note: Meters is the default scale elevation. If you do not specify this option when defining terrain resources, the elevation units are treated as meters.
--holesize n
Optional. Use this option if you have masked regions inside the boundaries of your imagery data. The default setting for hole size is 0, which is OFF.
The hole size indicates the number of contiguous pixels Google Earth Enterprise Fusion uses when matching any color region inside your imagery with the same value specified as your fill. For example, if you set the value to 100 and the imagery has 100+ contiguous pixels with the same color as one of the corners (fill value), it treats that area as a “hole” in the data and applies the mask to it. The end result is that whatever data is under the masked data shows through.
--masktolerance n
Optional. Specify the tolerance to be used when comparing pixels against mask fill value. Tolerance specifies the color range for mask selection. The default tolerance is 0, which is adequate for many fill colors that are typically pure black or pure white. However, because imagery compression and decompression can affect fill values by 1 or 2 color values, you can adjust the tolerance to compensate for any loss in precision. Typically, a setting of 1 or 2 is adequate in those situations.
--meta name=value
Optional. This option supports any number of optional name/value pairs that you want to store for the source data. For example, you might want to provide additional information about the data provider, such as the specific airplane that took the photo, or you might want to assign your confidence level with the data. If the name or value string contains white space, it should be enclosed in quotation marks.
--provider key
Optional. Specify a string that identifies the provider of the source data you are importing. This provider key must match the provider key in your database that corresponds to the source data. The provider name and copyright fields associated with this key are displayed for this resource in Google Earth EC. If the key contains white space, you must use quotation marks around the string.
Note: If you are importing several source files to define a single resource, Google Earth Enterprise Fusion assumes that they have a common provider.
--sourcedate string
Optional. This option is a string that represents the date of acquisition for your source file. It must in the ISO 8601 format (yyyy-mm-dd).
--whitefill
Optional. Use this option if imagery holes in your source data are filled with white. In some cases, source providers fill missing data inside the imagery with white and use a different color for the boundary mask.
--srs srs_def
Optional. Specify the spatial reference set to use instead of the embedded SRS. The coordinate systems that can be passed are anything supported by the OGRSpatialReference.SetFromUserInput()
call, which includes EPSG PCS and GCSes (for example, EPSG:4296
), PROJ.4 declarations, or the name of a .prf
file containing well known text.
-o path resourcename
Required. Specify the path and name of the resource relative to the asset root, for example, Resources/Imagery/ImageryResourceA
. If you indicate a subfolder that does not yet exist, Google Earth Enterprise Fusion creates it for you.
sourcefile
Required. Specify the path and file name of the source file for the resource. You can reference any network-available source file as this value. (Optional if you specify --filelist
file.)
--filelist file
Optional. Specify the path and file name of a file that contains a list of source files that you want to include in the resource. You can use this option, list files individually, or use a combination of the two.
--mercator | --flat
Optional. Default value is --flat
. Specifies the projection
of the map database. Only applies to new imagery resources. Glossary: Flat
Projection,
Mercator Projection.
genewvectorresource [--encoding type] [--layer num] [--meta name=value] [--provider key] [--sourcedate string] -o [path] resourcename sourcefile ... gemodifyvectorresource [--encoding type] [--layer num] [--meta name=value] [--provider key] [--sourcedate string] -o [path] resourcename sourcefile ...
To define or modify a vector resource.
genewvectorresource --layer 2 --encoding ISO8859-1 --sourcedate 2003-05-15 -o vector/MyVectorProvider/ResourceAssetA/vol/machine2/source/vector/ResourceSourceA.shp
--encoding type
Optional. If the field data in your vector resource has a particular encoding for characters, such as ISO8859-1, set this parameter to correctly display your data in Google Earth EC. If you omit this option, the character encoding defaults to ASCII (plain text). The table below lists the supported encoding formats.
Note: If the encoding strings contain white space, you must use quotation marks around the string.
| Apple Roman | CP 1258 | ISO 8859-15 | ISO-10646-UCS-2 |
| Big5 | CP 874 | ISO 8859-2 | JIS7 |
| CP 1250 | GB18030 | ISO 8859-3 | KOI8-R |
| CP 1251 | GBK | ISO 8859-4 | KOI8-U |
| CP 1252 | IBM 850 | ISO 8859-5 | SJIS |
| CP 1253 | ISO 8859-1 | ISO 8859-6 | TSCII |
| CP 1254 | ISO 8859-10 | ISO 8859-7 | UTF-8 |
| CP 1255 | ISO 8859-11 | ISO 8859-8 | eucJP |
| CP 1256 | ISO 8859-13 | ISO 8859-8-I | eucKR |
| CP 1257 | ISO 8859-14 | ISO 8859-9 eucKR |
--layer num
Optional. Use this option if your source data contains multiple layers and you want to extract a specific layer for your resource. The first layer of your data is 0. If you omit this option, Google Earth Enterprise Fusion uses the first layer of the source file to define the resource.
In most circumstances, source vector data has only one layer; however, Tiger vector data can contain multiple layers. Because there is a one-to-one correspondence between a vector resource and a single vector layer, resource creation from multi-layer data must specify a layer. If you are unsure which layer to indicate in defining a resource from multi-layer source data, you can open the vector source file in the Preview pane. The Preview List pane lists all of the layers in the source data, and you can examine each layer in order to select the appropriate one to import.
--meta name=value
Optional. Specify any number of name/value pairs that you want to include about the source data. For example, you might want to provide additional information about the data provider. If the name or value string contains white space, you must use quotation marks around the string.
--provider key
Optional. Specify a string that identifies the provider of the source data you are importing. This provider key must match the provider key in your database that corresponds to the source data. The provider name and copyright fields associated with this key are displayed for this resource in Google Earth EC.
Note: If you are importing several source files to define a single resource, Google Earth Enterprise Fusion assumes that they have a common provider.
--sourcedate string
Optional. Specify a string to represent the date of acquisition for your source file. It must in the ISO 8601 format (yyyy-mm-dd).
-o path resourcename
Required. Specify the path and name of the resource relative to the asset root, for example, Resources/Vector/VectorResourceA
. If you indicate a subfolder that does not yet exist, Google Earth Enterprise Fusion creates it for you.
sourcefile
Required. Specify the path and file name of the source file for the resource. You can reference any network-available source file as this value.
gepolymaskgen [--feather <int_feather>] --base_mask <geotiff_mask_file> [options] --output_mask <geotiff_mask_file> gepolymaskgen [--feather <int_feather>] --base_image <geotiff_image_file> [options] --output_mask <geotiff_mask_file>
Creates a mask file in .tiff format. Accepts geotiff image or mask files, KML polygons, or .shp files as input.
 Feather can be 0, positive, or negative. Default is 0.
--feather_border int
If flag is non-zero, border is feathered. Otherwise, border is left in tact. Flag remains in effect until it is modified. Default is border is feathered.
--and_neg_mask <mask_file>
Bitwise AND of negative image of polygon or raster mask
with the current mask.
Polygons can be given in
.kml or .shp files and are
assumed to be filled with
0x00. Raster masks should be
.tif files with the same pixel dimensions as the base mask.
Care should be taken not to overlap feathered regions.
--or_mask <mask_file>
Bitwise OR of polygon or raster mask to the current mask. Polygons can be given in .kml or .shp files and are assumed to be filled with 0xff. Raster masks should be .tif files with the same pixel dimensions as the base mask. Care should be taken not to overlap feathered regions.
--threshold <thresh_byte>
All pixels at or below the threshold byte are set to 0x00; all other pixels are set to 0xff.
gepublishdatabase [--delete db_name [--serverurl url]][--listdbs [--serverurl url]][--publish dbname [--server nickname]][--publisheddbs [--serverurl url]]
To publish a database (locally or remotely).
gepublishdatabase --publish msDelta gepublishdatabase --publish msDelta --server mainServer gepublishdatabase --listdbs --serverurl http://private.company.com
--delete db_name
Delete a registered database from the server.
--serverurl url
Optional. Use a specific server URL, such as http://private.company.com.
--listdbs
List all databases registered on the server.
--serverurl url
Optional. Use a specific server URL, such as http://private.company.com.
--publish dbname
Specify the location and name of the database that you want to publish relative to the asset root, for example, Databases/databaseA
.
--server nickname
Optional. Specify the nickname of the server association to which you want to publish. If you omit the server specification, Google Earth Enterprise Fusion publishes to the default server. (Consult your administrator or refer to the Google Earth Enterprise Administration Guide for information about setting up server associations.)
--publisheddbs
List all of the published databases on the server.
--serverurl url
Optional. Use a specific server URL, such as http://private.company.com.
gequery [--blockers] [--dependencies] [--geocode] [--infiles] [--logfile] [--outfiles] [--showlog] [--taillog] [--status] [--versions] assetname [version]
To query Google Earth Enterprise Fusion about a particular asset’s build.
gequery --dependencies imagery/TestProject?version=1
--blockers
Optional. Display sub-versions that block the specified version.
--dependencies
Optional. List the dependencies for the indicated asset and the status of each, such as Succeeded
, Blocked
, or Failed
. The purpose of being able to view the dependencies of an asset is to allow easier troubleshooting of failed asset builds. After you view the dependency list for an asset, you can use additional options to query a failed dependent element in order to find out why it failed. For example, you might use --logfile to determine the path to the log file for a failed asset.
--infiles
Optional. Provide the file name and location of the input file for the named asset. You typically use this command on a dependency for an asset file that is listed as Failed
. For example, if you learn that a project build phase fails, you could use the --infile parameter to determine specific image source file for that phase of the build.
--logfile
Optional. List the path to log file for the specified asset.
Note: Not all resources have log files.
--outfiles
Optional. List the files output by the specified dependency. This option allows you to trace forward in the dependency chain to see the next step in the process.
--showlog
Optional. Display the contents of the log file for the specified version.
Note: Not all resource versions have log files.
--taillog
Optional. Display the contents of the log file for the specified version, but in a manner similar to the UNIX command tail -f
.
Note: Not all resource versions have log files.
--status
Optional. List the completion and availability status of assets by version. If no version is specified, it reports the status of the current version. The table below lists the possible status values for each asset.
| Status | Description |
|---|---|
| Waiting | The asset is waiting for its input data to finish. |
| Blocked | The asset version cannot proceed. One or more of its input data or subcomponents has failed, is marked bad, or is otherwise unavailable. The responsible component is listed. |
| Queued | The asset version (or its subcomponents) is queued and waiting to be built. |
| InProgress | The asset version (or subcomponents) are actively being built. |
| Failed | The asset version failed. |
| Succeeded | The asset version (and subcomponents) succeeded. |
| Canceled | The asset version was canceled. |
| Offline | The version of this asset is unavailable because it has been cleaned up. |
| Bad | The version of this asset has been marked bad. |
--versions
Optional. List the version numbers for the indicated asset.
assetname
Required. Specify the location and name of the asset (resource, map layer, project, or database) whose build you want to query relative to the asset root, for example, Projects/Vector/VectorProjectA
.
version
Optional. Specify the version number of the asset you want to query, or enter current
or lastgood
. If you omit the version specification, Google Earth Enterprise Fusion queries the current version of the specified asset.
geraster2kml [--url url_root] [--output dirname] [--layer_name name] [--tile_size size] [--kml_only] [--no_kmz] [--jpg_quality qual] [--debug]--kip raster.kip --kmp mask.kmp
To convert a Google Earth Enterprise Fusion resource to the KML Region hierarchy, so you can access the data in any Google Earth client.
If the imagery resource has a source date, that date will be passed to the rasterized KML as well.
geraster2kml --kip myimage.kip --kmp myimage-mask.kmp
--url url_root
Optional. Specify the URL root for all links.
--output dirname
Optional. Specify the name of the output directory.
--layer_name name
Optional. Specify the name of the layer to appear in the Layers panel in Google Earth EC.
--tile_size size
Optional. Specify the output tile size (256
, 512
, or 1024
).
--kml_only
Optional. Generate KML files only (no imagery).
--no_kmz
Optional. Specify no compression to KMZ files, to output to KML only.
--jpg_quality qual
Optional. Specify the quality for the JPG compression.
--debug
Optional. Specify adding debug geometry to the output file.
--kip raster.kip
Required. Specify the name of the imagery file.
--kmp mask.kmp
Required. Specify the name of the mask file.
gereproject [--version] [--formats] [--query] [--snapup] [-co “NAME=VALUE”]* [-dstnodata] [-et err_threshold] [-multi] [-of format] [-order n] [-ot Byte/Int16/...] [-q] [-rb] [-rc] [-rcs] [-rn] [-s_srs srs_def] [-srcnodata value ...] [-t_srs srs_def] [-te xmin ymin xmax ymax] [-tr xres yres] [-ts width height] [-wm memory_in_mb] [-wo “NAME=VALUE”] [-wt Byte/Int16] srcfile dstfile
A simple utility used for image warping.
gereproject -s_srs EPSG:4326 usgsLanSat.tif usgsLanSat_rep.tif gereproject --query SFNorth.img
--version
Optional. The project version you want to warp.
--formats
Optional. Display the supported output formats.
--query
Optional. Provides information about the specified source file.
--snapup
Optional. Force the imagery to be magnified to a predefined level.
Options:
-co “NAME=VALUE”
Optional. Specify construction arguments to pass to the output GDAL dataset. Multiple -co options are allowed.
-dstnodata
Optional. Set nodata values for output bands (different values can be supplied for each band). If more than one value is supplied, all values should be quoted to keep them together as a single operating system argument. New files will be initialized to this value and if possible the nodata value will be recorded in the output file.
-et err_threshold
Optional. Specify the error threshold for transformation approximation in pixels. The default is 0.125.
-multi
Optional. Use multi-threaded warping implementation. Multiple threads will be used to process chunks of image and perform input/output operation simultaneously.
-of format
Optional. Specify the output format. The default is GeoTIFF (GTiff). Use the short format name.
-order n
Optional. Specify the order of polynomial used for warping (1 to 3). The default is to select a polynomial order based on the number of GCPs.
-ot {Byte|Int16|UInt16|UInt32|Float32|Float64|CInt16|CInt32|CFloat32|CFloat64}
Optional. Specify the data type of the output bands. The default is to match the input.
-q
Optional. Quiet; do not display the process messages in the terminal window.
-rb
Optional. Use bilinear as the resampling method.
-rc
Optional. Use cubic as the resampling method.
-rcs
Optional. Use cubicspline as the resampling method.
-rn
Optional. Use near as the resampling method.
-s_srs srs_def
Optional. Specify the source spatial reference set. The coordinate systems that can be passed are anything supported by the OGRSpatialReference.SetFromUserInput()
call, which includes EPSG PCS
and GCSes
(for example, EPSG:4296
), PROJ.4
declarations, or the name of a .prf
file containing well known text.
-srcnodata value...
Optional. Specify no data masking values for input bands. (You can specify different values for each band.) If you enter more than one value, use single quotes to keep them together as a single argument. Masked values will not be used in interpolation.
-t_srs srs_def
Optional. Specify the target spatial reference set. The coordinate systems that can be passed are anything supported by the OGRSpatialReference.SetFromUserInput()
call, which includes EPSG PCS
and GCSes
(for example EPSG:4296
), PROJ.4
declarations, or the name of a .prf
file containing well known text.
-te xmin ymin xmax ymax
Optional. Specify the geo-referenced extents of output file to be created.
-tr xres yres
Optional. Specify the output file resolution in target geo-referenced units.
-ts width height
Optional. Specify the output file size in pixels and lines.
-wm memory_in_mb
Optional. Specify the amount of memory (in megabytes) that the warp API is allowed to use for caching.
-wo “NAME=VALUE”
Optional. Specify the warp options. See Warp Options.
-wt {Byte|Int16}
Optional. Specify the working pixel data type in the source image and destination image buffers.
srcfile
Required. Specify the source file name(s).
dstfile
Required. Specify the destination file name.
The warp options (for -wo
) are:
INIT_DEST=
value
or INIT_DEST=NO_DATA
Forces the destination image to be initialized to the indicated value (for all bands) or indicates that it should be initialized to the NO_DATA value in padfDstNoDataReal/padfDstNoDataImag. If this value isn't set the destination image will be read and overlayed.
WRITE_FLUSH={YES
|NO}
Forces a flush to disk of data after each chunk is processed. In some cases this helps ensure a serial writing of the output data otherwise a block of data may be written to disk each time a block of data is read for the input buffer resulting in a lot of extra seeking around the disk, and reduced IO throughput. The default at this time is NO.
SKIP_NOSOURCE={YES
|NO}
Skip all processing for chunks for which there is no corresponding input data. This will disable initializing the destination (INIT_DEST) and all other processing, and so should be used careful. Mostly useful to short circuit a lot of extra work in mosaic creation situations.
Normally when computing the source raster data to load to generate a particular output area, the warper samples transforms 21 points along each edge of the destination region back onto the source file, and uses this to compute a bounding window on the source image that is sufficient. Depending on the transformation in effect, the source window may be a bit too small, or even missing large areas. Problem situations are those where the transformation is very non-linear or “inside out”. Examples are transforming from WGS84 to Polar Steregraphic for areas around the pole, or transformations where some of the image is untransformable.
The following options provide some additional control to deal with errors in computing the source window:
SAMPLE_GRID={YES
|NO}
Setting this option to YES will force the sampling to include internal points as well as edge points which can be important if the transformation is esoteric inside out, or if large sections of the destination image are not transformable into the source coordinate system.
SAMPLE_STEPS
Modifies the density of the sampling grid. The default number of steps is 21. Increasing this can increase the computational cost, but improves the accuracy with which the source region is computed.
SOURCE_EXTRA
This is a number of extra pixels added around the source window for a given request, and by default it is 1 to take care of rounding error. Setting this larger will increase the amount of data that needs to be read, but can avoid missing source data.
geresume assetname [version]
To resume a build process that was canceled, blocked, or failed, after correcting the problem, if necessary.
geresume imagery/SourceInc/MississippiRiverDelta geresume imagery/TestImage.kiresource/mosaic.kia?version=1
assetname
Required. Specify the location and name of the asset (resource, map layer, project, or database) whose build you want to resume relative to the asset root, for example, Projects/Vector/VectorProjectA
.
version
Optional. Specify the version number of the asset whose build you want to resume, or enter current
or lastgood
. If you omit the version specification, Google Earth Enterprise Fusion resumes the build of the current version of the specified asset.
gesetbad assetname [version]
To specify a version of an asset as Bad.
gesetbad projects/TransitLines/BostonTransitLines 2
assetname
Required. Specify the location and name of the asset (resource, map layer, project, or database) whose version you want to set as Bad relative to the asset root, for example, Projects/Vector/VectorProjectA
.
version
Optional. Specify the version number of the asset you want to set as Bad, or enter current
or lastgood
. If you omit the version specification, Google Earth Enterprise Fusion sets as Bad the current version of the specified asset.
gesplitkhvr [--rows num] [--cols num] [--overlap num] [--quiet] input.khvr
To create two or more source files from a large imagery or terrain source file to reduce the size of each source file to under 80 GB in raw size. (Raw size = number of pixels width * number of pixels height * 3.) This tool produces a grid of image files designated as rows and columns.
gesplitkhvr --rows 4 --cols 4 --overlap 10 image_file.khvr
--rows num
Required. Specify the number of resulting image files across.
--cols num
Required. Specify the number of resulting image files high.
--overlap num
Optional. Specify the number of pixels of overlap between the resulting images. The default is 300.
--quiet
Optional. Do not display the progress messages in the terminal window.
input.khvr
Required. Specify the name of the input file. It must be a .khvr
file.
getop --delay seconds
Displays a list of what Google Earth Enterprise Fusion is currently working on and whether gesystem
and gehttpd
are currently running.
getop 30
--delay seconds
Required. Specify the number of seconds delay between refreshes. For example, if you specify 30
, getop
runs every 30 seconds.
getranslate [--formats] [-ot Byte|Int16|UInt16|UInt32|Float32|Float64|CInt16|CInt32|CFloat32|CFloat64] [-not_strict] [-of format] [-b band] [-outsize xsize[%] ysize[%]] [-scale src_min src_max [dst_min dst_max]] [-srcwin xoff yoff xsize ysize] [-a_src projection] [-projwin ulx uly lrx lry] [-co “NAME=VALUE”]* [-mo “META-TAG=VALUE”]* [-quiet]
A simple utility used for image reprojection. You must use this tool for:
Since Google Earth Enterprise Fusion can perform the following tasks, you do not need this utility for:
getranslate -of Jpeg -a_srs WGS84 usgsSFHiRes.tif HiRes_translate.jpg
-a_src projection
Optional. Specify the projection for the output. Options are:
NAD27|NAD83|WGS84|WGS72
EPSG:
num
PROJ.4
definition
.prj
)
--formats
Optional. Display the supported output formats.
-b band
Optional. Specify the band to copy (1-based indexing). You can specify this value multiple times. For example, the following entry reverses the bands:
-b 3 -b 2 -b 1 -co “NAME=VALUE”*
Optional. Specify construction arguments to pass to the output GDAL dataset.
-mo “META-TAG=VALUE”*
Optional. Specify that metadata is to be included in the output.
-not_strict
Optional. Be forgiving of mismatches and lost data when translating to the output format.
-of format
Optional. Specify the file format of the output. The default is GTiff
. Use the short format name.
-ot Byte|Int16|UInt16|UInt32|Float32|Float64|CInt16|CInt32|CFloat32|CFloat64
Optional. Specify the data type of the output bands. The default is to match the input.
-outsize xsize[%] ysize[%]
Optional. Specify the output image size in pixels or percent of original.
-projwin ulx uly lrx lry
Optional. Specify the extents and size of the output window. (Similar to -srcwin
but uses georeferenced coordinate.)
-quiet
Optional. Do not display the process messages in the terminal window.
-scale src_min src_max [dst_min dst_max]
Optional. Specify the scale of the input pixel values.
-srcwin xoff yoff xsize ysize
Optional. Specify the extents and size of the output window.
gevirtualraster [--crop pixelx,pixely,pixelx,pixelh] [--fill a,b,...] [--lut lutfile] [--src override_srs] [--tolerance num] [--validate] -o output.khvr {sourcefile ... | --filelist file}
To create a virtual mosaic, which allows you to use a mask created outside of Google Earth Enterprise Fusion for an imagery mosaic.
gevirtualraster --fill 0,0,0 -o /gevol/src/imagery/usa/XX/new_location/all_files.khvr/gevol/src/imagery/usa/ XX/new_location/*.tif
--crop pixelx,pixely,pixelx,pixelh
Optional. Crop the image to the specified pixel extents.
--fill a,b,...
Optional. Specify band values to use as fill.
--lut lutfile
Optional. Specify a LUT file for the entire image.
--src override_srs
Optional. Specify the SRS.
--tolerance num
Optional. Specify the tolerance to be applied to the fill. The default is 0.
--validate
Optional. Validate the inputs and exit.
-o output.khvr
Required. Specify the name of the output file, which must have the .khvr
extension.
sourcefile
Required. Specify the path and file name of the source file for the resource. You can reference any network-available source file as this value. (Optional if you specify --filelist
file.)
--filelist file
Optional. Specify the path and file name of a file that contains a list of source files that you want to include in the resource. You can use this option, list files individually, or use a combination of the two.


{{set . "title" "Basic Chat room"}} {{template "header.html" .}}
{{.Text}}
{{.User}} joined the room
{{.User}} left the room


We built a powerful machine learning model from thousands of past Kickstarter campaigns, in order to help you assess your own chances of success. Try it out below, or directly search our database for similar campaigns.


orgutils: Helper Functions for Org Files
Helper functions for Org files (<http://orgmode.org/>):
a generic function 'toOrg' for transforming R objects into Org
markup (most useful for data frames; there are also methods for
Dates/POSIXt) and a function to read Org tables into data frames.
| Version: |
0.4-1 |
| Imports: |
textutils |
| Suggests: |
RUnit |
| Published: |
2017-03-21 |
| Author: |
Enrico Schumann |
| Maintainer: |
Enrico Schumann <es at enricoschumann.net> |
| License: |
GPL-2 | GPL-3 [expanded from: GPL (≥ 2)] |
| NeedsCompilation: |
no |
| Materials: |
NEWS |
| CRAN checks: |
orgutils results |
Downloads:
Reverse dependencies:
Linking:
Please use the canonical form
https://CRAN.R-project.org/package=orgutils
to link to this page.


{% extends "managerModalBase.html" %} {% block label %} Modified Documents {% endblock %} {% block instructions %} Here you will find a complete list of documents of all types that have been modified and can be committed. {% endblock %}


PAINT
Taking beauty to another level!
to your neighbourhood
Paint is coming closer to your vicinity. With over 200 global branches,Paint seeks to ensure availability to customers.
There also exists services in form of Proffesional advice in case if needed.


This example shows the available renderers for different layouts.
VerticalLayout
This lays out all elements under each other.
HorizontalLayout
This lays out all elements next to each other.
Group
A group behaves like a VerticalLayout with a custom heading.
Complex example
This example consists of a Group (green) which contains a HorizontalLayout (red), which contains two VerticalLayout (blue).
Each of the VerticalLayouts contains two controls.


Scottish hotel taped off after body found
by Scotsman ReporterA Scottish hotel was partly closed this morning after a body was found.
Emergency services were called to the scene at Drummond’s Hotel, Fife, shortly after 10am after the sudden death of a man.
Following the arrival of several police vehicles, scenes of crime officers then arrived and began to tape off parts of the hotel for further investigation.
Social media has been rife with unsubstantiated rumours, but one person said that officers from Police Scotland had been “doing door-to-door asking for anyone with CCTV to make it available for viewing” by the investigation team.
Inspector Rachael Burns of Glenrothes Police Station said: “Officers were called to an address on Balbirnie Street, Markinch on Wednesday, November 20 following the sudden death of a man.
“The death is being treated as unexplained and inquiries are ongoing.”
READ MORE - Ex-NASA engineer reveals quickest way to defrost windscreens


new Planet(sys_id)
Procedurally generates a planet and it's nodes.
Parameters:
| Name | Type | Description |
|---|---|---|
sys_id |
String | The coordinates of the sector containing the planet in the form of 'x,y'. |
Methods
(async) genAccomodations()
NOT YET IMPLEMENTED
Determines the building accomodation tags the planet is given based off of its terrain type and other miscelaneous factors.
(async) genID() → {String}
Generates the planet's 3 digit ID.
Returns:
The planet's 3 digit ID.
- Type
- String
(async) genInhabitants()
NOT YET FULLY IMPLEMENTED
Generates a random number of NPCs inhabiting the planet's surface based off of its size.
(async) genInhabitants() → {Array}
Determine and generate the appropriate number of NPCs based off the planet's size.
Returns:
Returns a String Array containing the IDs of the NPCs on the planet.
- Type
- Array
(async) genNodeBase()
Determines the node_base based off of the planet's size.
(async) genNodes() → {Array}
Determines the number of nodes the planet has based off its size, and then generates the nodes.
Returns:
The array holding the planet's nodes.
- Type
- Array
(async) genPlanetoids() → {Array}
Creates an randomly sized Array, based of the sector's classification, of generated planetoid objects.
Returns:
An array of planetoid objects.
- Type
- Array
(async) genRestrictions()
NOT YET IMPLEMENTED
Determines the building restriction tags the planet is given based off of its terrain type and other miscelaneous factors.
(async) genSize() → {Number}
Uses a weighted generation algorithm to obtain the size ID of the planet.
Returns:
The size ID for the planet.
- Type
- Number
(async) genType()
Randomly selects the type of the planet.
Returns:
the type of the planet.
(async) getNodeIDs() → {Array}
Returns the IDs of the planet's nodes
Returns:
A String Array of the IDs of the nodes.
- Type
- Array
(async) getPlanetoidIDs() → {Array}
Returns:
All the sector's planetoid's IDs.
- Type
- Array
(async) save()
Creates and modifies a temporary object, holding all the data of the planet, and saves it to a json file in root/maps.


THE BLAIR WITCH PROJECT Reviewed by Jamie Peck
Rating: *** (out of ****) Artisan Entertainment / 1:27 / 1999 / R (language, intensity) Cast: Heather Donahue; Michael Williams; Joshua Leonard Director: Daniel Myrick; Eduardo Sanchez Screenplay: Daniel Myrick; Eduardo Sanchez
In a day when cities never sleep and the crime rates in them soar, the woods would seem to offer nature's last refuge, a simple, reassuring solace from the hectic hustle and bustle of the real world. But along comes "The Blair Witch Project," this year's Little Movie That Could, to promptly and potently shoot that notion out of the water. If "Blair Witch" breaks out - and robust pre-release buzz certainly suggests that it will - expect weekend camping trips to become a thing of the past. You won't be able to sleep soundly in your own bed. Kiss the wilderness goodbye forever.
An exercise in mounting dread set in the murky "Black Hills" of Maryland, "The Blair Witch Project" was the hot ticket at this year's Sundance Film Festival, inspiring additional screenings and even a studio bidding war as a result of the blazingly positive word-of-mouth - raves that must have blindsided the first-time filmmakers of this impressive independent feature. They are Daniel Myrick and Eduardo Sanchez, and their directorial debut - cleverly spun as if the story actually happened and shot on 16mm and home video to further hit the horror home - is clearly one to remember. As if you'll be able to forget it.
Know this going in - that "Blair Witch" is a purely fictional creation - and the impact is perhaps lessened a bit; to make up for any potential viewing drawbacks, just assure friends that the events displayed here are factual, drag them along and watch them squirm. Which isn't to say that those in the know won't get a mean case of "Witch" willies - the three main performers in Blair are so authentic that it's easy to believe in the on-screen dread they expertly convey. Heather Donahue, Michael Williams and Joshua Leonard never strike false notes as student filmmakers interviewing the yokels and exploring the terrain of Frederick County in their quest to document the existence of a local urban legend.
Unfortunately for them, their trek into the forest takes exceedingly nasty turns - the less said of which the better. Worth noting: The movie's concise mythology might leave you craving more. As tension slowly, steadily builds over "Blair Witch"'s 87-minute run, disagreements and skirmishes amongst the trio grow in both number and anxiety, often escalating to shouting matches studded with various expletives. Realistic, yes, and also redundant. But once "Project" kicks into high gear for its final third - a non-stop stomach-churner - there's little time for the cast to catch their breath enough to scream, let alone swear.
Even with this intense noise-making, genre fans expecting an all-out splatterfest are sure to be disappointed: "The Blair Witch Project," proudly respecting the power of the unseen, assaults the mind with psychological terror instead of the eyes with explicit gore. Following suit, Myrick and Sanchez also keep their ghastly antagonist completely in viewers' imaginations for the duration of the film. Whether it's intentional or merely a side effect of "Blair Witch"'s shoestring budget, this game of no-show is a smart, sensical move - and the key to the movie's scary success.
© 1999 Jamie Peck E-mail<EMAIL_ADDRESS>Visit The Reel Deal Online: http://www.gl.umbc.edu/~jpeck1/ "The best possible argument for including [a shot of Bruce] Willis' genitals would have been that the movie, after all, contains everything else." -Roger Ebert on "Color of Night"
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


HIGHLIGHTS
IQ Test
You have 200s to take the quiz.
Keep in mind that incorrect answer will penalize your time by ten seconds!
Start Quiz


{% extends "layouts/default.html" %}
{% import "scaffolding/macros.html" as scaffold with context %}
{% block layout_content %}
{% for post in posts %}
{{post.title}}
By {{post.created_by}} on {{scaffold.print(post.created)}}
{{post.content}}
{% if this.user == post.created_by %}
Edit
{% endif %}


org.cidarlab.minieugene.rules
Enum RuleOperator
java.lang.Object
java.lang.Enum<RuleOperator>
org.cidarlab.minieugene.rules.RuleOperator
- All Implemented Interfaces:
- java.io.Serializable, java.lang.Comparable<RuleOperator>
public enum RuleOperator
- extends java.lang.Enum<RuleOperator>
|
Method Summary |
static RuleOperator |
valueOf(java.lang.String name)
Returns the enum constant of this type with the specified name. |
static RuleOperator[] |
values()
Returns an array containing the constants of this enum type, in
the order they are declared. |
| Methods inherited from class java.lang.Enum |
compareTo, equals, getDeclaringClass, hashCode, name, ordinal, toString, valueOf |
| Methods inherited from class java.lang.Object |
getClass, notify, notifyAll, wait, wait, wait |
STARTSWITH
public static final RuleOperator STARTSWITH
ENDSWITH
public static final RuleOperator ENDSWITH
AFTER
public static final RuleOperator AFTER
ALL_AFTER
public static final RuleOperator ALL_AFTER
SOME_AFTER
public static final RuleOperator SOME_AFTER
NEXTTO
public static final RuleOperator NEXTTO
ALL_NEXTTO
public static final RuleOperator ALL_NEXTTO
SOME_NEXTTO
public static final RuleOperator SOME_NEXTTO
LEFTTO
public static final RuleOperator LEFTTO
ALL_LEFTTO
public static final RuleOperator ALL_LEFTTO
SOME_LEFTTO
public static final RuleOperator SOME_LEFTTO
RIGHTTO
public static final RuleOperator RIGHTTO
ALL_RIGHTTO
public static final RuleOperator ALL_RIGHTTO
SOME_RIGHTTO
public static final RuleOperator SOME_RIGHTTO
ALL_BEFORE
public static final RuleOperator ALL_BEFORE
BEFORE
public static final RuleOperator BEFORE
SOME_BEFORE
public static final RuleOperator SOME_BEFORE
CONTAINS
public static final RuleOperator CONTAINS
NOTCONTAINS
public static final RuleOperator NOTCONTAINS
MORETHAN
public static final RuleOperator MORETHAN
NOTMORETHAN
public static final RuleOperator NOTMORETHAN
EXACTLY
public static final RuleOperator EXACTLY
NOTEXACTLY
public static final RuleOperator NOTEXACTLY
REVERSE
public static final RuleOperator REVERSE
SOME_REVERSE
public static final RuleOperator SOME_REVERSE
ALL_REVERSE
public static final RuleOperator ALL_REVERSE
FORWARD
public static final RuleOperator FORWARD
SOME_FORWARD
public static final RuleOperator SOME_FORWARD
ALL_FORWARD
public static final RuleOperator ALL_FORWARD
REPRESSES
public static final RuleOperator REPRESSES
INDUCES
public static final RuleOperator INDUCES
DRIVES
public static final RuleOperator DRIVES
BINDS
public static final RuleOperator BINDS
MATCHES
public static final RuleOperator MATCHES
NOTTHEN
public static final RuleOperator NOTTHEN
THEN
public static final RuleOperator THEN
WITH
public static final RuleOperator WITH
NOTWITH
public static final RuleOperator NOTWITH
NOTEQUALS
public static final RuleOperator NOTEQUALS
EQUALS
public static final RuleOperator EQUALS
ORTHO
public static final RuleOperator ORTHO
values
public static RuleOperator[] values()
- Returns an array containing the constants of this enum type, in
the order they are declared. This method may be used to iterate
over the constants as follows:
for (RuleOperator c : RuleOperator.values())
System.out.println(c);
- Returns:
- an array containing the constants of this enum type, in
the order they are declared
valueOf
public static RuleOperator valueOf(java.lang.String name)
- Returns the enum constant of this type with the specified name.
The string must match exactly an identifier used to declare an
enum constant in this type. (Extraneous whitespace characters are
not permitted.)
- Parameters:
name
- the name of the enum constant to be returned.
- Returns:
- the enum constant with the specified name
- Throws:
java.lang.IllegalArgumentException
- if this enum type has no constant
with the specified name
java.lang.NullPointerException
- if the argument is null


const registry = new CustomElementRegistry();
registry.define('daily-question', DailyQuestion);const root = document.querySelector('#app');
root.attachShadow({ mode: 'open', registry });root.shadowRoot.innerHTML =
'<daily-question>Tabs or spaces?</daily-question>';
We get to create a new CustomElementRegistry, use it to define our custom elements
and attach it to a shadow root.
Attaching a scoped registry to a Shadow DOM because it provides an encapsulation
mechanism out of the box
Custom elements resolution is of course changed. If a CE is inside a shadow DOM, the browser will
check if that has a registry and if the CE is defined there; otherwise, it will check the global registry.
Now Web Components libraries, instead of definining custom elements on their own on the global
registry, can take a registry as a dependency and use it instead.
Scoped Custom Elements Registries


Photos as Lagos Task Force uncovers lion in Indian’s home
by The Eagle OnlineThe Lagos State Environmental Sanitation and Special Offences (Enforcement) Unit have uncovered a lion in the home of an Indian in the state, The PUNCH is reporting.
According to the newspaper, the operatives of the Task Force have been deployed to guard the house for the evacuation of the lion.
The operatives were deployed on Friday.
The Head of the task force, Yinka Egbeyemi, told the newspaper: “The lion was found on No. 229 Muri Okunola Street.
“Our Black Maria and men have been there since Friday.
“They will remove the animal on Monday.
“The Indian man rented the apartment and lied to the owner of the house that he wanted to be staying there.
“He claimed that the house was under renovation and brought the animal there.
“The neighbours saw the thing and that was how we got a petition from them.
“We have sent him a letter that he should come and talk to us.
“So, by tomorrow (Monday), we will like to know how he got the animal.
“He will have to tell us why he is rearing a lion in a city; that is a wild animal and anything can happen.
“So, he may be prosecuted.”
Previous Post
Dad demands sex before paying my school fees, impregnated me thrice — Pastor’s daughter


Goleta Beach Triathlon Race Report
Pre- Race
I had been looking forward to racing at Goleta Beach for quite a while, a friend of mine, Aaron, had contacted me via text during Wildflower weekend to see if I had signed-up yet because prices were going up. Unfortunately, in the end, Aaron was not able to attend.
I drove up with my mom on Saturday afternoon. It was a quick drive up PCH then 101, we stayed at the Motel 6 in Carpinteria as we didn’t make reservations until the last minute. It was a nice motel. We went to a Tapas bar before heading over to have dinner. I found a great place while studying at UCSB, it is called Olio e Limone, a super swanky Italian restaurant right off of State St. Did a little hob-knobing with the local Santa Barbarians and went straight to bed.
Race Morning
I woke up at 1:28am, unable to sleep, the air-conditioning had been turned off and it was way too hot in there. I was so excited for the race that I couldn’t fall back asleep the entire night. I read blogs of other triathletes, in the darkness, as well as slow-motion videos of a dude throwing-up milk, which I found hilarious. I tried to contain my laughter in bed.
We arrived to the event at about 5:30am and my wave didn’t start until 8:00am so that gave me plenty of time to chill. It was extremely foggy that morning, you could barely see the giant yellow buoys in the distance, this caused the race to be delayed a few minutes. I felt very relaxed and confident, I knew it would be a great race.
Swim – 25:56 ~1:28/100yds
I had a really good swim. All the training sessions with Tower 26 have really began to come to fruition and allowed me to be a faster swimmer than ever before. As the swim started a few guys jetted out and never looked back, leaving me with everyone else, vying for position towards the front. As we approached the first turn buoy there were a few people ahead of me. This allowed me to get behind their feet, drafting, saving energy. Before I knew it, I was in the front of this giant pack of men, to the point where I turned around to make sure I was not off-course. It was a very unusual feeling for me. I was pushing as hard as I could while still maintaining a calm demeanor. At one point the pace was too intense, nevertheless, I managed to keep my cool and return to a more comfortable pace.
I can’t believe what an improvement I have made from last year where I did the same swim in 33:24.
T1 - 00:02:39
I was out of breath by the time I reached the timing mat. I ran as fast as I could over to my bike and wiped my dirty feet with the towel I had. I opted not to use socks with my road shoes, it was totally fine.
I forgot to hit the lap button on my Garmin until I was a few miles out on the bike course, this messed up my times with the GPS.
Bike - 01:10:39 - 18.7 MPH
The bike leg went OK, I don’t think I did enough training on the bike, it felt as if my full potential could not be reached. I wanted to go faster but my legs simply wouldn’t let me. At one point I got totally “chicked” by a UCLA bruin #407, Kelly Kosmo, she passed me by as if I was standing still, even though I was pushing as hard as I could. I tried to keep-up at one point, to no avail, leaving me in the dust within minutes. She later lapped me on the run. It was very inspiring, hopefully one day I will be that fast.
The bike course was very familiar as it was where I first started training for triathlons back in November of 2012. There were many pot holes along the road, however, many of them have been fixed since I last rode on it. There were many sharp, blind, dangerous turns on the course which slowed the pace down quite a bit. There were no aid stations during this part, I had to carry my own water, which I was expecting, so it wasn’t so bad. I had two bottles, each one with a GU salt tablet, creating electrolyte enhanced water, just what I needed to avoid cramping.
I began to realize what a huge difference there is with the longer distance races as there is hardly any time to even drink as you are pushing as hard as you can the entire way. Whereas, with the longer distances, they require a more steady flow of energy throughout, allowing the feeding process to be more calm.
Also, another thing worth mentioning was that the bike course was a narrow two-way course, so passing other riders was a rather perilous affair, risking a head-on collision every time.
T2 00:02:21
I un-buckled my bike shoes as I was approaching T2, it was the culmination of many attempts at doing T2 in races. Flawless. Hoped off/racked my bike, but m Brooks Pure Cadence 2 shoes on and ran out of T2 as fast as possible.
Had to brush my feet clean a bit, obviously, could’ve been faster but I was satisfied with what I did at the moment.
Run - 5 miles - 00:38:40 - 00:07:44 min/mi
The run course was spectacular, very short and comfortable. You could see the entirety of the course from the beginning, this allowed you to see how the competition was doing. I could see people catching up to me and then passing me with little or no problem. My legs felt great at this point, when I would look at my watch I kept thinking that I was going too fast as I usually can’t run much faster than 8:00 minute/mi on my training runs. However, in retrospect, I could’ve pushed the pace much more.
I hadn’t paid much attention to the map details prior to the start of the race, so, I wasn’t exactly sure how long the run distance was, only that it was 4 laps.
I felt very relaxed the entire run, making sure to thank the volunteers as I passed them. Towards the end, though, I felt more focused and ran past without even looking.mnm
Finish
At the end of the 4th lap of the run I asked one of the volunteers what to do next, he gave me directions and I ran to the finish line. My legs were beginning to show slight signs of cramping as I had forgotten my race belt at home, I didn’t have my salt pills.
I felt an overwhelming sense of joy at what I had just accomplished, I knew I could push so much harder and would do that much better in the future. There was still adrenaline racing through my veins and I couldn’t really eat for about 30 minutes, at which point I gained a ravenous appetite. I smelled gnarly. Luckily, the Motel 6 room had a 12 pm check-out, this left me a whole hour to shower and get ready for the drive back
.


Before Change
global newstartnumber
newstartnumber = 1
endnumber = len(constantsymbols)
constants_found = [None]*(endnumber + 2)
// make a mapping to send all constantsymbols to S.One and use
// that to make sure that term ordering is not dependent on
// the indexed value of C
After Change
// System of expressions
if isinstance(expr, (set, list, tuple)):
return type(expr)(constant_renumber(Tuple(*expr),
variables=variables, newconstants=newconstants))
// Symbols in solution but not ODE are constants


Your Selected Blueprint is being Launched, kindly check back in a while.
{{launchMessage.message}}
{{launchMessage.message}}
{{logsErrorMessage}}
{{log.timestamp | timestampToLocaleTime}}
{{log.log}}
{{log.timestamp | timestampToLocaleTime}}
{{log.log}}


| DOSE: |
3 bowls |
smoked |
Cannabis |
(plant material) |
First of all let me say that I started using cannabis approx 5 years ago. I now only smoke homegrown organic stuff, the strongest I can find. This stuff is pretty much the chronic (bubonic chronic that made me choke, this ain't no joke). Usually I smoke 3-4 bowls and I'm good to go.
It is possible to achieve CEVs with this substance. I have never experienced OEVs even while being phenomeally blitzed by brownies (much higher dose than attainable by smoking). I would describe calypso as being a meditative tool. Ideas and social interaction each flow more freely. It's also a great muscle relaxer and adds to the appreciation of art, especially in music where layers become more distinct. I find that the details of surfaces tends to increase while high, though they increase in graininess (I almost see a cyan and magenta 'pixels' underneath surface appearance).
After a variety of usage schedules (once per week, daily, etc), I found I prefer not using cannabis more often than every other day. This keeps the experience fresh and vivid every time, and doing it any more often will inevitably raise my tolerance (and reduce the intensity/quality of the high).
I look down somewhat on daily users, since sooner or later what they're buying isn't worth the experience. One needs to exert a little willpower, but I think this pretty much guarantees a great experience everytime.
I also would like to report that the health effects of smoking have been lessened by taking large quantities of antioxidants, specifically Vitamins C and E.  Even pouring a little Odwalla (Mo Beta Antioxidant) in the bong can notably lessen the irritation of taking a hit, so I can take a slightly bigger hit. Even orange juice helps a little.
The only thing I find cannabis to go well with is opium, and only then a little opium (opium by itself is kinda boring). This MJ+Op combo is particularly intense sexually (delays and extends the big O). I just don't do anything that requires fine motor coodination ;).
Cannabis is a great, mind-opening substance that is great as long as I respect it and have the self control not to use it every day.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Black to Play 53
Unlimited Game
pips Black=136 White=134
(CorrectAnswer= 0/0, ErrorScore= 0)
1. 14/9 10/7 eq:+0.489 59.88% (G:19.23% B:0.48%) 40.12% (G:8.05% B:0.28%) 2. 14/6 eq:+0.367 (-0.122) 57.99% (G:20.25% B:0.49%) 42.01% (G:7.74% B:0.31%) 3. 14/11 10/5 eq:+0.347 (-0.142) 57.92% (G:19.60% B:0.35%) 42.08% (G:7.04% B:0.21%) 4. 14/11 13/8 eq:+0.332 (-0.157) 57.05% (G:16.91% B:0.48%) 42.95% (G:7.37% B:0.26%) 5. 14/9 8/5 eq:+0.328 (-0.161) 56.96% (G:18.45% B:0.31%) 43.04% (G:7.38% B:0.22%)


{% load url from future %}
| fit | ttrs | neighbors | ||||||||||||
| {{ fitid }} |
|
{% for neighbor_fitid in neighbors %} {{ neighbor_fitid }} {% endfor %} |
No fits found!!! :( Maybe you need to run the flag_suspect_fits preprocessing?
{% endif %} {% include "svweb/footer.html" %}


Bluecadet Javascript Toolkit
jQuery.animateauto (https://github.com/bluecadet/JS_Toolkit/blob/master/js/lib/bc/jquery/jquery.animateauto.js)
Determines the value of the property when set to auto. Animates that property to the stored value and sets the property to 'auto' once animation has completed.
Bacon ipsum dolor sit amet shoulder tenderloin pork chop, ham
leberkas tri-tip hamburger. Brisket meatball chuck pork biltong
corned beef filet mignon tongue sirloin flank ham hock turkey.
Corned beef ham pastrami meatball bresaola ground round andouille
pork loin.


{% extends 'base.html'%} {% block content%}
Colorful places to live with your family and good enviroment for your kids.
Colorful places to live and play.
View Neighbourhood
{{hood.name}}


Constructor
new Profile(data)
- Source:
Creates a new Profile
Parameters:
| Name | Type | Description |
|---|---|---|
data |
PlayerData | The raw profile data |
Members
countries :Map.<string, CountryInfo>
- Source:
Per-country info for the player
Type:
- Map.<string, CountryInfo>
(readonly) image :string
- Source:
The URL to the player's profile picture
Type:
- string
(readonly) level :number
- Source:
The experience level of the player
Type:
- number
(readonly) nick :string
- Source:
The in-game nickname of the player
Type:
- string
(readonly) registered :string
- Source:
The registration data of the player
Type:
- string
(readonly, nullable) squadron :string
- Source:
The squadron name of the player, if he is in any. Returns null if the player is not in a squadron
Type:
- string
(readonly) stats :Map.<string, ProfileStats>
- Source:
The player's statistics
Type:
- Map.<string, ProfileStats>
(readonly, nullable) title :string
- Source:
The title of the player, if he has set any. Returns null if the player does not have a title set.
Type:
- string


SCOT stands for Smart Contract Organizational Token. It’s a Steem-Engine.com project. We’re taking the white paper for Smart Media Tokens (SMTs) and delivering on it to the best of our ability NOW. This post marks the formal beginning of live testing of the prototype we call Novel Distribution: Smart Contract Organizational Token (ND SCOT).
Who are we?
aggroed manages the project as a whole
crystalhuman and clayboyn help out with customer support and content
The project involves a number of contributing devs-
harpagon built the smart contract software and runs the node
yabapmatt built steem-engine.com as a private front end to the smart contract node. He also realized and designed the SCOT system to operate on the Steem-Engine platform
he handed the development work off to beggars who is constructing the more recent additions
someguy123 built and manages the token converter that allows other cryptos like btc, bch, ltc, and doge to the exchange for trading
Holger80 has constructed the voting bot that we’re using to launch the SCOT service
inertia has built a block explorer and helps us with engineering decisions, some programming, and customer concerns
(Special thanks to asgarth who built the dex, and wehmoen who made the first block explorer for the project)
You have a community and you’d like to monetize it. You create a token, distribute it, and users stake it. They go to yourcoolwebsite.com where you run something that looks a lot like steemit.com (condenser) or your own custom UI; however, the rewards are in COOL tokens, the users don’t see every steem post out there by default, and you have more control of what’s happening on the site. You’ve created your own custom website, from and for your own community, with your own token, and it distributes similarly to Steem. It trades on steem-engine.com against Steem but you can trade it for BTC, LTC, BCH, and DOGE nor or against ETH/EOS/BTS/Tron in the near future.
Your token is a success and you’re able to sell what you bought, traded, mined, earned, or minted to the community.
It’s like the vision for SMTs, but happening today through Steem-Engine.com.
Where is the project at now?
This is literally my first post that’s using the tag scottest
which is SCOT test. It’s not live on the main production site now. We’re still on the test servers. So, no, you can’t start today, but we’re going live with testing as of right now! Hopefully before the end of May everyone who wants one can get their own community started.
The project is moving in iterative steps from centralized to decentralized as it’s progressing. Right now we’re running the SCOT distribution features through essentially a python voting bot, which is a centralized service that is controlled by individual devs and project owners. As we get this nailed down and working correctly we’ll also implement a way to have the same distribution handled by smart contract through Steem-Engine. We’ll let both options exist, but the smart contract version reduces the amount of trust needed in the leaders for the project to be successful.
How’s it work?
 Data is stored on the main chain through custom json operations that are added to the main chain by witnesses as users submit actions. Steem as a blockchain has no idea what any of the Steem-Engine transactions mean, but the blockchain can make sure that all the data provided is validated by consensus. Any standard Steem block that has transactions that are regarding Steem-engine are picked up and put into a separate chain we call a side chain.
Our side chain is literally a subset of transactions that were stored on Steem. The side chain ignores all but the Steem-Engine relevant transactions. Then the Steem-Engine node kicks in to read the data that is stored on the side chain, interpret it, and execute on it. “Transfer 17 COOL tokens from aggroed to yabapmatt.” “Issue 30 Drama Tokens” and other activities are executed by the node. The node doesn’t have a p2p layer beyond the witnesses yet, but before the end of the year we hope to have a fully functioning P2P consensus layer for the Steem-Engine nodes (as opposed to witness nodes) with separate block production and block production rewards. In the meantime you get pretty close to that by independently running your own node to verify transactions so that you can see we’re not randomly adding extra tokens to ourselves.
And yes, the node software is opensource!
Want to run your own token and build your own community website?
We’re working on making this as simple as possible. Some trickiness we can’t escape, but it should look something like this and be available in May-
Getting Started
Step 1. Make a token, set some parameters, and work with us get the voting bot working and potentially (optionally) decide to create your own web portal with it
Step 2. Issue tokens to users
Step 3. Users stake tokens
Step 4. Users create posts on regular steem sites (steempeak, busy, steemit, cryptoempirebot) and just use a tag, or they go through your custom website
Step 5. Users vote on each others posts in the normal way, but now they get Steem and other tokens as well!
Why is this a big deal?
SMTs seem infinitely delayed. They’re likely game changing, but it’s tough to know how far into the future we’d have to wait for them to arrive. In the meantime everyone can create their own Steemit.com like site with their own tokenonimcs starting sometime in May. If you don’t have a community behind you it may not make a big deal. If people with communities behind them start forming their own token based community here it’ll have a drastic effect towards user acquisition, retention, and community empowerment.
People = Value
We need more people hodling Steem, and this can help get them!
Also, think of whaleshares, peerplays, bearshares, and some of the other chain forks that have happened. Each time they go off on their own it causes some disruption to the main chain. Imagine instead of forking all of Steem and moving off to a separate community they instead just issued their own token and stayed right here? They could get the best of both worlds. They’d still be on Steem which would limit the technical requirements of what they would need to setup a new token, they could still tap into the existing user base instead of starting from scratch, but now they can also get their own token with a distribution that may not be as fucked or be as fucked, but now benefiting new people.
Keeping people in the ecosystem and growing this ecosystem is how we moon. SCOT facilitates creating and keeping new communities on the blockchain and that to me represents an amazing human growth potential for Steem and crypto as a whole.
Is there a benefit to the layer 2 solution and this whole side chain thing?
The three biggest positives are timeline to readiness, not requiring Steem hardforks to make changes, and smart contract flexibility.
Speed: I’d like to think SMTs would have already been here, but they aren’t. I’d like to think they might get formed this year, but I have my doubts. Every day it seems Steem is slipping a little more on the rankings, and that’s bad for price and community size. Getting launched now puts us ahead of any other blockchain in terms of being able to really create a community that you own through tokenization. It also removes some of the bad behavior seen on steem or bad actors. Bad actors likely aren’t going to interact much with your posts because they may not receive much steem, but they’ll be worth tons of tokens so hopefully they’ll be ignored by some of the usual suspects We need growth and we need it now. This gets us going.
Hardforks: If SMTS are built onto the steem blockchain itself then serious changes are going to require hardforks of STEEM. A hardfork is a particularly scary time. Not all of the exchanges are good at handling them, and as a consequence any time they come around we risk being offline with some of the major exchanges for days, weeks, or months. We could also end up with a stopped chain for a while as has happened before. All of that is bad for the price of Steem and subsequently the activity on it. If every time the community wants changes to SMTs we have to hardfork it then that’s going to cause challenges to getting changes put into the system and changes when they are put into the system.
When we’re on a side chain we can hardfork the side chain without worrying as much about the exchanges. After we make more headway we’ll create exchange nodes that the exchanges can run so they can trade our coins, but at the moment we don’t have to worry about it. This gives us some flexibility to grow and change the way the tool works without major disruptions to the entire ecosystem.
Smart Contracts: SMTs are essentially a smart contract for distributing tokens. It’s pretty robust, but it reminds me of the Henry Ford Quote about the Model T: “it comes in whatever color you want so long as that color is black.” Essentially, it’s a robust tool, but it can do exactly one set of things. We’re instead creating a smart contract platform that has the potential to respond to any if:then statement and create logic around it. We can replicate SMTs as we’re doing now, but we don’t have to stop there. We can create other contracts and do so faster than the Steem blockchain can be changed.
 It’s all voluntary, but right now Steem-Engine has enormous potential and we’re in the process of unlocking it. Hopefully you’ll join us.
You can find us in Discord here: https://discord.gg/HykXgCQ
This page is synchronized from the post: ‘SCOT Testing underway!!! Are you ready for your own token that can distribute like Steem?’


This sample node.js web application demonstrates how the node-cntk module can be used to host CNTK models inside a node.js web-server.
The hosted model in this web app consists of a Convolutional Neural Network that was trained on the MNIST dataset.
For more information regarding the training procedure and the architecture of the model, please refer to the following CNTK tutorial.
How to use: draw a digit in the left box and then click the "Recognize" button to send the drawn digit to the server. The recognized digit will be then shown in the right box. Use the "Clear" button to clear the current drawing.
|
|


I have been using the Nuvaring for a few months now.

SENT2
I figured the pain was just from the first time but the pain continued every time I had intercourse and I rarely even wanted to have sex; because it hurt and I had no sex drive. My boobs have grown a size and I have gained approximately 10 pounds. I thought there was something wrong with my body and the low sex drive was a symptom of depression. After reading the reviews I feel so relieved to know there's nothing wrong with me. I've decided to switch birth controls, however other than those side effects, the nuvaring has kept me from getting pregnant and regulated my period


{% extends "source/base.html" %}
{% block slides %}
{% include "source/title.html" %}
{% include "source/whoami.html" %}
{% include "source/thanks_to_paypal.html" %}
{% include "source/slack.html" %}
{% include "source/expectations.html" %}
{% with active="intro" %}{% include "source/introduction.html" %}{% endwith %}
{% with active="terminal" %}{% include "source/terminal.html" %}{% endwith %}
{% with active="install-python" %}{% include "source/install_python.html" %}{% endwith %}
{% with active="starting-python" %}{% include "source/starting_python.html" %}{% endwith %}
{% with active="install-virtualenv" %}{% include "source/install_virtualenv.html" %}{% endwith %}
{% with active="install-atom" %}{% include "source/install_atom.html" %}{% endwith %}
{% with active="first-program" %}{% include "source/first_program.html" %}{% endwith %}
{% with active="debugging" %}{% include "source/debugging.html" %}{% endwith %}
{% include "source/recap.html" %}
{% include "source/thankyou.html" %}
{% endblock %}