|Top Previous Next|
This class is used for generating output from calculations. Typically as a GIS file with coordinates, but CSV and DBF files are also possible.
It is mostly used internally, but made available to users too. There is less error checking in this class, so you are to a higher degree responsible for what you are doing, if you use it directly. The sample uses it several times.
This table lists the 11 classes, which all has the same interface:
Despite most of the file formats can hold mixed object types (SHP being the exception), we only support using a single object type.
This is not file based opposed to the other formats. Not suited for very large datasets or you may hit an out-of-memory error.
This always uses , as field delimiter, no matter regional settings.
This always uses . as decimal point, no matter regional settings.
First line in the file contains the field names.
Stores codepage information in byte 29 in the header. This is standard, but not all software reads the information.
If you don't specify a filename for output, the content is stored in a string property called GeoJSON instead.
You should only use KML if your coordinate system is already lat/long, WGS84.
Requires MIMFAL1500.DLL or MIMFAL1500_64.DLL on the path.
The generated table includes a spatial index and makes it slower to write than MITAB.
Not all versions of RW Net 4 includes MFAL support.
The new UTF-8 formatted MIF file for MapInfo 15.2 (64-bit) and up.
Requires MITAB.DLL or MITAB64.DLL on the path.
The generated table is without a spatial index. Pack the table in MapInfo to add this.
CPG file is a simple text file with the codepage number. ArcGIS can read this information.