Discount Software Promotions for AvisMap GIS Technologies

Listed below are all the discount promotions for software by AvisMap GIS Technologies. If you see a 'Buy Now' button simply click to use the coupon code and get an instant discount direct from the vendor. For past deals you can click the 'I Want This' buttons and if we run the deal again you'll get an email notification.

Visit the AvisMap GIS Technologies website.

AvisMap Deskpro

A Professional Desktop GIS Application

for PC

AvisMap GIS Engine

Advanced GIS Development Software

for PC

Vendor Pulse

The latest news, straight from our vendors.

Jun 7 2009 at 10:51pm

Style Mapping Table for GIS and CAD Data Conversion

Data in different GIS or CAD software have specified line styles, fonts, symbols, and fill styles which might not be kept as usual after being imported into AvisMap format. In order to keep original style settings to the full extent, we present the conception of Style Mapping Table which can be generated by user self in outside. User can specify the corresponding relationships of each line style, font, symbol, and fill style.

Format description of Style Mapping Table

There are seven parts involved in the table:
a. Table title
b. Font reference
c. LineStyle reference
d. Symbol reference
e. Fillstyle reference
f. Color mode
g. DXF’s path and file name
The table title has three rows:
AvisMap Style Mapping Table
Version 3.00
Separator “&”

Where, the characters in the double quotation marks after Separator are delimiters between fields in the Style Mapping Table. It is specified by user to avoid conflicting with characters in the text. The default is a comma (,) the ASCII code.

The reference part of the font begins with FontBegin, and ends with FontEnd. Each row between them represents a kind of corresponding relationship of font. And it is made up of four domains being separated by delimiters. The four domains are grouped as below:

Domain 1	Domain 2	Domain 3	Domain 4
Text Style Name/Font face/ID in outer data	Scale of font width	Scale of font height¹	Font face in AvisMap

Note:

a.Text style name should be specified in Field 1 if it is AutoCAD data. Font face or ID should be specified if it is Microstation DGN data;

b.The font width and height of outer data will be read by program, but the zoom scales of them should be specified by user self.

Import: outer font width * font width zoom scale ==> AvisMap font width

Import: outer font height * font height zoom scale ==> AvisMap font height

Export: AvisMap font width / font width zoom scale ==> outer font width

Export: AvisMap font height / font height zoom scale ==> outer font height

That is, you can use the same .srt file to export the imported data. Therefore, you can get the same font width and height as original ones before imported, and vice versa.

The reference part of the linestyle begins with LineStyleBegin, and ends with LineStyleEnd. Each row between them represents a kind of corresponding relationship of LineStyle. And it is made up of two domains being separated by delimiters. The two domains are grouped as below:

Domain 1	Domain 2
Linestyle name/ID in outer data	Linestyle ID in AvisMap

The reference part of fillstyle is similar with the one of linestyle.

The reference part of the symbol begins with SymbolBegin, and ends with SymbolEnd. Each row between them represents a kind of corresponding relationship of symbol. And it is made up of three domains being separated by delimiters. The three domains are grouped as below:

Domain 1	Domain 2	Domain 3
Symbol name/ID in outer data	Symbol zoom scale	Symbol ID in AvisMap

Note:

The symbol size of outer data will be read by program, but the zoom scale should be specified by user self.

Import: outer data’s symbol size * symbol zoom scale = AvisMap symbol size

Import: SupeMap symbol size / symbol zoom scale = outer data’s symbol size

That is, you can use the same .srt file to export the imported data. Therefore, you can get the same symbol size as original one before imported, and vice versa.

Text color setting:

If there is no special setting involved in text, just use the color being set in “Import or Export color mode”.

The DXF file includes two rows:
dxffile
jr12.dxf

Where, the second row shows the DXF file and path name which can be absolute or relative, or no path used here. In this case, the DXF file must be saved in the same path as the Style Reference Table file.

The extension name of the file is *.srt.
All notes begin with // just like the case in C++, but without /* */ marking
There is no upper or lowercase distinction in style reference table. Besides the title must lie in the beginning of the file, other five parts have no particular order, that is, they can be mixed but can’t be nested.
In some GIS or CAD software, their linestyles, symbols, fonts, or fillstyles may not be marked with a name but with an ID or number. In this case, to enhance the general availability of the .srt file, the outer data’s linestyles, symbols, fonts, or fillstyles can be identified by name or ID. In AvisMap, a font is identified with name, while linestyles, symbols, and fillstyles are identified with IDs.
The contents of DXF file are the outer data’s style and names/IDs. In style reference, the system will search for them in the specified DXF file.
There are three color modes of DXF file (imported or exported):
a. Specified by layer. The color of an object in DXF file is specified by the reference file of the corresponding layer.
b. Specified by user. User can specify a field as the color index. If there is no specification, use the field “Color”, and if the field not found, use the color of object itself as described in below c.
c. Use the color of an object itself.

Examples of Style Table Reference:

Sample Data =====> without notes

AvisMap Style Mapping Table
Version 3.00
Separator “,”

FontBegin
1 , 0.83333333 , 1.0 , Arial
7 , 0.50000000 , 0.66666 , Arial
23 , 0.83333333 , 0.66666 , Arial
135 , 1.0 , 1.0 , aips_AM
205 , 0.50000000 , 1.0 , Bold
..
FontEnd

LineStyleBegin
al, 3
DASHED, 54
3, 1
..
LineStyleEnd

SymbolBegin
0301__, 10.0, 301
0302__, 10.0, 302
0303__, 10.0, 303
0401__, 10.0, 401
0402__, 10.0, 402
..
SymbolEnd

FillStyleBegin
1, 3
2, 4
3, 1
..
FillStyleEnd

dxffile
jr12.dxf

ColorModeBegin

StyleColor ByLayer
StyleColor ByColorIndexField FieldName
StyleColor ByGeometry

TextColor ByLayer
TextColor ByColorIndexField [FieldName]
TextColor ByGeometry

ColorModeEnd

Sample Data=====>with notes
//the text match no case
AvisMap Style Mapping Table //the mark of file type
Version 3.00 //Version Number
Separator “&” // strongly recommended, but can be ignored, here, the default is “,”. In this example, we use && as delimiter.
//In the following code, the font, lineStyle, symbol, and fillStyle have no particular order, but can’t be nested.
FontBegin //font begins
//outer font name/ID, font width scale, font height scale, AvisMap font name
1 && 0.83333333 && 1.0 && Arial //Normal
7 && 0.50000000 && 0.66666 && Arial
23 && 0.83333333 && 0.66666 && Arial
135 && 1.0 && 1.0 && aips_AM //Morse
205 && 0.50000000 && 1.0 && Bold //Bold
..
FontEnd //font ends

LineStyleBegin //linestyle begins
//outer linestyle name/ID, AvisMap linestyle name
1 && 3
2 && 4
3 && 1
..
LineStyleEnd //linestyle ends

SymbolBegin //symbol begins
//outer symbol’s name/ID, symbol scale, AvisMap symbol’s ID
0301__&& 10.0&& 301 //outer symbol size * zoom scale –> AvisMap symbol size
0302__&& 10.0&& 302
0303__&& 10.0&& 303
0401__&& 10.0&& 401
..
SymbolEnd //symbol ends

FillStyleBegin //fillstyle begins
//outer fillstyle’s name AvisMap fillstyle’s ID
1 && 3
2 && 4
3 && 1
..
FillStyleEnd //fillstyle ends

dxfffile
c:datadxffilejr12.dxf //the directory and name of the dxf file

ColorModeBegin

// The separators can be space, comma, && etc (ASCII)
// You can select one of them.
StyleColor ByLayer
StyleColor ByColorIndexField FieldName // (The default ColorIndex can be used)
StyleColor ByGeometry

// Select one of them
TextColor ByLayer
TextColor ByColorIndexField [FieldName] //(optional)
TextColor ByGeometry

ColorModeEnd

Read Whole Post

Jun 7 2009 at 10:47pm

Reserved Keywords in Database

There are some restrictions in datasets or fields creation, especially about their names:

The length of name string can not be zero or over 30 bytes (that is 30 letters or 15 Chinese characters are allowed ), typically to SDM for Oracle data, the actual length is 18 bytes because some extra characters may be appended to the original name after some operations such as index creation being performed.
Figure, underline or initial with “sm” are not allowed.
All characters except for figure, letter, Chinese character, underline are not allowed;
Can not conflict with the reserved keywords of databases which has been listed as below:

In Oracle or Microsoft Access database, there are some reserved keywords can not be used when creating dataset or field. In addition to the following listed keywords, the system generated objects in Oracle will be named with SYS_ as prefix; therefore, any prefixes with SYS_ will be rejected in Oracle.

ABORT	COMMIT	EXIT	LIMITED	ORDER	ROWLABEL	TERMINATE
ACCEPT	COMPRESS	FALSE	LOCK	OTHERS	ROWNUM	THEN
ACCESS	CONNECT	FETCH	LONG	OUT	ROWS	TO
ADD	CONSTANT	FILE	LOOP	PACKAGE	ROWTYPE	TRIGGER
ALL	CRASH	FLOAT	MAX	PARTITION	RUN	TRUE
ALTER	CREATE	FOR	MAXEXTENTS	PCTFREE	SAVEPOINT	TYPE
AND	AND	FORM	MIN	PLS_INTEGER	SCHEMA	UID
ANY	CURRVAL	FROM	MINUS	POSITIVE	SELECT	UNION
ARRAY	CURSOR	FUNCTION	MLSLABEL	POSITIVEN	SEPARATE	UNIQUE
ARRAYLEN	DATABASE	GENERIC	MOD	PRAGMA	SESSION	UPDATE
AS	DATA_BASE	GOTO	MODE	PRIOR	SET	USE
ASC	DATE	GRANT	MODIFY	PRIVATE	SHARE	USER
ASSERT	DBA	GROUP	NATUAL	PRIVILEGES	SIZE	VALIDATE
ASSIGN	DEBUGOFF	HAVING	NATURALN	PROCEDURE	SMALLINT	VALUES
AT	DEBUGON	IDENTIFIED	NEW	PUBLIC	SPACE	VARCHAR
AUDIT	DECLARE	IF	NEXTVAL	RAISE	SQL	VARCHAR2
BETWEEN	DECIMAL	IMMEDIATE	NOAUDIT	RANGE	SQLCODE	VARIANCE
BINARY_INTEGER	DEFAULT	IN	NOCOMPRESS	RAW	SQLERRM	VIEW
BODY	DEFINITION	INCREMENT	NOT	REAL	START	VIEWS
BOOLEAN	DELAY	INDEX	NOWAIT	RECORD	STATE	WHEN
BY	DELETE	INDEXES	NULL	REF	STATEMENT	WHENEVER
CASE	DESC	INDINDICATOR	NUMBER	RELEASE	STTDEV	WHERE
CHAR	DIGITS	INITIAL	NUMBER_BASE	REMR	SUBTYPE	WHILE
CHAR_BASE	DISPOSE	INSERT	OF	RENAME	SUCCESSFUL	WITH
CHECK	DISTINCT	INTEGER	OFFLINE	RESOURCE	SUM	WORK
CLOSE	DO	INTERFACE	ON	RETURN	SYNONYM	WRITE
CLUSTER	DROP	INTERSECT	ONLINE	REVERSE	SYSDATE	XOR
CLUSTERS	ELSE	INTO	OPEN	REVOKE	TABAUTH	TEXT
COLAUTH	ELSIF	IS	ROWLABEL	ROLLBACK	TABLE	.
COLUMN	EXCLUSIVE	LEVEL	OPTION	ROW	TABLES	.
COMMENT	EXISTS	LIKE	OR	ROWID	TASK	.

Read Whole Post

Jun 7 2009 at 10:42pm
About SDM for Oracle Spatial
- You should make sure there are records in the database view: User_sdo_geom_metadata, otherwise no dataset will be included in a new Oracle Spatial datasource. The possible solution is: users try to add records to the view User_sdo_geom_metadata outside manually according to the particular data and then create datasource.
- Primary Key must be specified in spatial data table.
- Point, line, region, text and tabular datasets are supported in SDM for Oracle Spatial engine. Where, the geospatial data in point, line and region datasets is stored in the field Mdsys.Sdo_Geometry, the text dataset uses the same storage format with the one in SDM for Oracle.
- The supported Sdo_Gtypes in Mdsys.Sdo_Geometry:
- 1/2001/3001/2005/5
  2/2002/3002/2006/6
  3/2003/3003/2007/7
- Projection transformation is not supported in SDM for Oracle Spatial.
- Encoded type of dataset is not supported in SDM for Oracle Spatial.
- Once a SDM for Oracle Spatial datasource has been created, it will not keep the boundaries and indexes for all connected datasets or the ones being copied form outside, if there is not any geometry in dataset, please re-compute or rebuild boundary and spatial index for the dataset.
- Image dataset in SDM for Oracle Spatial is not the image format regulated by Oracle Spatial but uses the format as the one in SDM for Oracle.
- Dataset Name Regulations in SDM for Oracle Spatial: To the non AvisMap created dataset, the name is like: TableName_GeospatialcolumnName, for example, a Shapefile Street with geospatial column Shape, the corresponding dataset name in AvisMap is: Street_Shape. If there are multi Sdo_Geometry type columns in a table, each column will have a dataset or a layer to correspond. To the dataset created by AvisMap software, its name is identical with the table.
Read Whole Post

Jun 7 2009 at 10:34pm

Transaction in AvisMap GIS Engine

Short transaction and Long transaction are all supported in AvisMap GIS Engine.

What’s transaction?

Transaction is a common conception in database applications, which is a series of operations being performed based on a single logistic work cell. There are four properties to each logistic work cell, called ACID (Atomicity, Consistency, Isolation and Durability) which are absolutely necessary to a transaction. Among these properties, the concurrency and atomy are the key points needed to be concerned especially in GIS applications. Where, concurrency can control a GIS data can not be modified by two or more users simultaneously or one user can not edit the data before the other ones has committed the updates; and atomicity can insure that all work flows in a transaction can be treated and finished just as an integrated group. If there is one step failed, the other should stop to be continued. This kind of mechanism of transaction is provided by database management system (DBMS), and surely supported by AvisMap GIS Engine, that is short transaction mechanism.

Limitations of short transaction:

As short as possible.
Users other than the one who is editing a GIS dataset can not edit even browse the dataset.
Transaction can not span long period of time; it must be committed or rolled back before you shut down your computer at least.
If there are some unexpected circumstances occurring, for example, power interruption or computer down, the changes will be lost.

Long transaction in AvisMap GIS Engine:

GIS users have some specialized transactional requirements:

Transactions must span long periods of time, sometimes days and months, not just seconds or minuets.
Once modifications have been done, it would not lost even some unexpected circumstances mentioned above have taken place.
Users can roll back all changes at any time if they are not satisfied with them.
Any changes being committed can be seen by other users.
The other users can modify the area previously locked by one user only after it has been committed or rolled back.

The long transactions in AvisMap GIS Engine SDM can completely meet the above requirements. The comparisons between the short and long transactions in AvisMap GIS Engine SDM are listed as below:

Characteristics	Long Transactions	Short Transactions
Multiuser editing	Yes	No
Time	Long (days, months or longer)	Short
Unexpected circumstances occurring	Changes will be kept	Changes will be lost

How to use long transaction in AvisMap GIS Engine SDM?

It is very easily to use the long transaction functions of SDM datasource, the soLongTransaction object is provided to perform the operations of long transaction. We can get the object through the following code (here, take the VB code as example):

Dim objLT As soLongTransaction
Set objLT = objDatasource.LongTransaction ……

Operations in long transaction:

There are three basic operations in long transaction object: CheckOut, CheckIn and UndoCheckOut.

CheckOut: Identify the transaction has started and lock the data required to be edited until the transaction terminated, and during the period other users can only view and get the state of the data before it has been checked out.
CheckIn: Commit all changes modified by user, and determine whether the data will be continued checked out which is set according to the parameter involved in the method. After calling the method, other users can view the newest data.
UndoCheckOut: Once you undo all changes, the data will be rolled back to its original state. If the property AutoCheckOut of soLongTransaction object has been set as False, the locked data will be released otherwise locked continuously.

Operable data level:

The long transaction can be done on three data levels: DataSource, Dataset and Recordset.

DataSource: Perform transactions in dataSource in which all data except for those locked by other users will be checked out.
Dataset: Perform transactions in dataset (layer or table) in which all data except for those locked by other users will be checked out.
Recordset: Perform transactions in recordset in which all records that meet the condition or a certain area in layer will be checked out.

Descriptions of Properties and Methods:

All the properties and methods listed below are involved in the object soLongTransaction:

Properties	Type	Description
User	BSTR	User name logged in long transaction.
Password	BSTR	Long transactional user’s password
Logged	Boolean	Identifies whether a user has successfully logged in long transaction environment.
AutoCheckOut	Boolean	Identifies whether the state of CheckOut will be kept continuously after committing or rolling back the changes.

Methods	Data Level	Description
LogIn	-	Logs in long transaction.
LogOut	-	Logs out long transaction.
CheckOut	DataSource	Checks out or locks the datasource to begin transaction process.
CheckIn	DataSource	Checks in or commits the changes to datasource.
UndoCheckOut	DataSource	Undoes or rolls back the changes to datasource.
CheckOutDataset	Dataset	Checks out or locks the specified dataset (table or layer).
CheckInDataset	Dataset	Checks in or commits the changes to dataset (table or layer).
UndoCheckOutDataset	Dataset	Undoes or rolls back the changes to dataset (table or layer).
CheckOutRecordset	Recordset	Checks out or locks a certain recordset (or an area of a layer).
CheckInRecordset	Recordset	Checks in or commits the changes to recordset.
UndoCheckOutRecordset	Recordset	Undoes or rolls back the changes to recordset.

Tips:

Long transaction is available in SDM for Oracle and SDM for SQL Server.
Long transaction user should be created in server side by DBA before you log in the environment. For example, if you have installed the Oracle client software, open Oracle Enterprise Manager Console, click Database and expand solutions, select a certain instance and find SMLTUSERS table, right-click Browse/Edit Directory…, you can add users and set passwords for them in this table, or use SQL statements directly.
If you have logged on long transaction environment, but have not set the property AutoCheckOut as True, the data could not been edited.
The data definition language for instances creating or deleting table, creating or deleting field etc will do the really changes to database and can not be rolled back in long transaction, therefore, you should check in or undo your changes before performing any DDLs.

Read Whole Post

Jun 7 2009 at 10:11pm

Match Table of Field Copy

The method CopyField of soRecordset can copy one field to another; even the different types of fields, the corresponding match rule are listed below:

	Boolean	Byte	Integer	Long	Currency	Single	Double	Date	Text	Memo
Boolean	Y	Y¹	Y¹	Y¹	N	Y¹	Y¹	N	Y²	Y²
Byte	Y³	Y	Y	Y	Y	Y	Y	N	Y	Y
Integer	Y³	Y⁴	Y	Y	Y	Y	Y	N	Y	Y
Long	Y³	Y⁴	Y⁴	Y	Y	Y	Y	N	Y	Y
Currency	N	Y⁴	Y⁴	Y⁴	Y	Y	Y	N	Y	Y
Single	Y³	Y⁴	Y⁴	Y⁴	Y	Y	Y	N	Y	Y
Double	Y³	Y⁴	Y⁴	Y⁴	Y⁴	Y⁴	Y	N	Y	N
Date	N	N	N	N	N	N	Y	Y	Y	Y
Text	N	Y⁵	Y⁵	Y⁵	Y⁵	Y⁵	Y⁵	N	Y	Y
Memo	N	Y⁵	Y⁵	Y⁵	Y⁵	Y⁵	Y⁵	N	Y	Y

How to read the table?

Each Y or N means field can be copied or not from the corresponded row to column, and Y means yes and N means no. The particular Y or N with superscript has restrictions shown as below which should be noticed in practical operations.

1- Boolean to Numeric, True becomes to 1 and False becomes to 0;
2- Boolean to String, True becomes to “true” and False becomes to “false”, but in some special databases, true will become to “1″ and false become to “0″
3- Numeric to Boolean, non-zero value becomes to True and zero becomes to False;
4- Possibaly occurring data truncated.
5- If there are non-numeric characters involved in text, for example, “aaa”, it would fail to match the specified type.

Descriptions:

The match table of field copy may have difference in details due to the different engines, for example, the Memo field is only supported by SDB or SDBPlus engine, not in SQL and others.
In essential, field copy is implemented via the standard SQL sentences of database: Update TableName Set DestFieldName = SourceFieldName. If you have any questions about the function, please refer to the usage in particular database.

Read Whole Post

Discount Deal Coupons for Windows and Mac Software Apps

Software Search

Daily Bits Email

Discount Software Promotions for AvisMap GIS Technologies

AvisMap Deskpro

A Professional Desktop GIS Application

AvisMap GIS Engine

Advanced GIS Development Software

Vendor Pulse

What’s transaction?

Limitations of short transaction:

Long transaction in AvisMap GIS Engine:

How to use long transaction in AvisMap GIS Engine SDM?

Operations in long transaction:

Operable data level:

Descriptions of Properties and Methods:

Tips:

How to read the table?

Descriptions:

© Copyright 2012 BitsDuJour LLC. All Rights Reserved. Privacy Policy