All fields marked with an asterisk (*) are mandatory in order to save the form.
There are the same fields as for Database (Single). The only difference are the Datasources.
||Not editable. After saving the feature form the feature gets automatically a simple id.
||Project the feature belongs to.
||Name of the feature. Use a descriptive one for better handling and usability.
||Any description relating to the feature.
||Minimum map scale for displaying the feature in the client.
||Maximum map scale for displaying the feature in the client.
||Attribute that contains the geometry information. After setting the database connection, the Geometry field will be set automatically if only one exists.
||Geometry type for the feature class:
- Area = Polygon
||Primary_Key of the feature table where the geometry objects are stored. The client references to this during all actions relating to geometry. If you want to check Is locatable a key field has to be defined.
||Determines whether the feature class in the client may be set active or not. Corresponds to locatable off/on in GeoMedia. To be able to check the box a key field has to be defined.
IsLocatable doesn't appear for Type Raster and/or for Png and Jpeg as an Output type.
- Cached: The feature class is published in advance and cached on the server. Caching increases Web performance. Tiles that have already been loaded onto the client can be used again locally and offline.
- Live: The feature class is created on-the-fly when it is requested by the client. Live published data is always the most up-to-date. The map will be newly created for every new map view.
- CachingOnDemand: This is a combination of live-loading and caching. Whenever the client changes the map view, it sends a request to the server and looks for any change in tiles that should be loaded. If there are new ones, the tiles will be generated at once and downloaded - and will be ready to use for other clients.
- Offline: If you have feature(s), which are captured offline, you have to choose this Feature loader
||Type of representation in Smart Client. The following display options are available:
- Every loaded feature gets Default as an interpretation type.
- If you want to make server side redlining available you have to set the feature to Redline. So it is possible to see Redlining edits from all users on the same server.
- If you want to use databased labeling, the labeling feature has to be set to the interpretation Label.
- Like the interpretation Redline it is also possible to allow server side dimensioning. So it is possible to see Dimensioning edits from all users on the same server.
- This interpretation is just for public safety.
||Data type for the client to obtain all feature information.
- GdoPlus: Data type for all geometry objects provided in Smart Client. GDO+ is a binary format to reduce file size. It uses GDO (Geographic Data Objects) to store the geometry information as well as additional data (for example, ID, tooltip, and style ID).
- Jpeg: Output type for raster feature classes. Images containing many colors (true-color graphics; 24 bit) - such as aerial or satellite photos - are best published in .jpg format. Note that JPEG may compress images, which can lead to a loss of contrast and image quality. The compression ratio or degree of loss can be set with the parameter Raster Quality. The initial raster data is best saved as .ecw files or RGB-colored .tiff files.
- Png: Output type for raster feature classes. Photos with few colors or gray levels (£ 256; 8bit) - such as ground or town maps - are best published in .png format. This format compresses without loss and supports transparency and color index tables. The file size depends essentially on whether the image contains large, homogeneous areas of color, or whether the pattern of colors changes often from area to area. The initial data is best saved as indexed tiff files.
Output type to Png or Jpeg for vector data too.
It is possible to change the
||Definition of attribute and style to display in client when the mouse moves over the element. Short info (= tooltips) are only displayed for active feature classes. For additional information to configure tooltips, see here.
|Feature Area (Optional):
||Concerning the extent of the entire project area, you can specify bounds for a single feature class. The advantage of this approach is that when you use Cache as a feature loader, the tiles will not be produced for the entire project extent, but only for the extent of the feature class. With this option you have also the possibility to restrict a feature extent for certain users.
You have to click to enable Feature Area.
- East (Min): Most western point of your bounding box or X-value of the lower-left corner of the feature class.
- North (Min): Most southern point of your bounding box or Y-value of the lower-left corner of the feature class.
- East (Max): Most eastern point of your bounding box or X-value of the upper-right corner of the feature class.
- North (Max): Most northern point of your bounding box or Y-value of the upper-right corner of the feature class.
If you have raster files, the feature area is set by the system automatically.
||Number of rows for tiles during publishing process. Width and height of the tiles are automatically calculated in meters.
Only active when FeatureLoader is set to Cache or CachingOnDemand.
||Number of columns for tiles during publishing process. Width and height of the tiles are automatically calculated in meters.
Only active when FeatureLoader is set to Cache or CachingOnDemand.
||Shows the date of the last date/time the feature was published. The value "0" indicates that the feature has not yet been published.
If you have raster files, you can use the following excel sheet to compute the necessary rows and columns.
||If the feature has an other coordinate system than the project, you change it here. You can also add a coordinate system by clicking on the button. You will forwarded to the same modal form as you adding a coordinate system for your project.
||Name of the feature data table.
||Type of the database provider:
For detailed information about connections see Connections for file based features.
||Connection parameters to the data source of the feature class.
||Enables snapping to this feature class during geometry collection and editing in the client.
The field Is snapable is not available for Type is Raster and/or Output type is Png respectively Jpeg for raster respectively vector data.
||Transparency of a feature, usually defined by its alpha channel. Use values between 0 and 1. Value 1 = default and means no transparency.
||Enlargement value when fitting the map. 1.25 = default. If you set here a negative value for example -2000, then the value gets an fixed scale (Scale 1:2000). Can be important if you want to zoom in to a specific geometry if a workflow is opened (for example: Editing a geometry) or if a query gets executed.
||Specifies the tile size in pixels (number of pixels required down the longer tile side, no decimals!).
Map resolution is only available for Type is Raster and respectively or Output type is Png/Jpeg for raster respectively vector data.
Map resolution can be extracted from the excel sheets above.
||Compression ratio for .jpeg files; file size decreases accordingly.
Raster quality is only available for Type is Raster and/or Output type is Jpeg for raster/vector data.
Click Save to store the feature.
- ↑ Wikipedia Retrieved November 22 2013
- ↑ FotoForensics Retrieved November 22 2013