Name : Liadira Kusuma Widya | Student ID : P66087047

GEOSPATIAL INFORMATION SHARING AND STANDARDS

Homework 1

1. Introduction
A geographic information system (GIS) is a framework to manage, gather, and analyze
the many types of data. Not only about it, GIS also to organize, coomunicate, and
understand the science of all the world. GIS has a good impact for helping users make
smarter decisions. In various geospatial applications, it is needed to integrate spatial
information between various associations, with various substance and structures for
kind of utilization. Nowadays, various GIS sofware were developed by various spatial
database management system, such as (QGIS, Google Earth, AutoCAD, MapInfo,
ArcGIS, etc.). The data format from each software may have different format, such as
data format for GoogleEarth is .kml or .kmz; data format for ArcGIS or QGIS is .shp;
and data format for MapInfo is .tab, etc. In spite of the fact that the information in
databases may be similar information in the same data.
Developing the information technology all over the world, a lot of geospatial
information from various sources is delivered ceaselessly. Many information were
followed by developing of computer science and networks of internet. It must be
handled from various programming to be conveyed over the system. There were many
types of GIS software while each GIS program has own package to develop the internal
data format and storage methods. Therefore, it was needed to compare of spatial data
type, data format, and convert utilities from every software. To understanding the
restrictions of every software in term of conversion the data information, it was
conducted a number of simulations by creating an assortment of geometries features
either straightforward or complex which will be changed to a several data format. So,
It could be resolved the methods of converting information to support
information/data sharing among different software.

2. Data, Tools and Methodology

In this assignment was showed in two different scenarios, such as ArcGIS and MapInfo
Pro, etc. The first scenario applied direct conversion and the second used via data
exchange format. The data used from various types of geometry and the software that
should be prepare, such as ArcGIS, QGIS, MapInfo Pro, GoogleEarth Pro.

2.1. Data and Tools

There were two types of data, spatial data (.shp and .tab) and information for attribute
data. Spatial data were created by software programs, such as ArcGIS, MapInfo Pro,
Google Earth, QGIS, etc.
ArcGIS is a GIS software which the scope about maps and geographic information. It
is used for creating maps, analyzing mapped information, sharing geographic
information and managing geographic information in a database. ArcGIS desktop
licensed software which is developed by ESRI. For this assignment, I used ArcGIS
 desktop standards which in addition to the functionality, includes more tools for
manipulation of shapefiles and geodatabases. The licensed code that I used form my
campus EVA674115160.
MapInfo Pro is a GIS software is produced by Pitney Bowes and used for mapping and
location analysis. MapInfo Pro allows users to visualize, analyze, edit, interpret,
understand and output data to reveal relationships, patterns, and trends. MapInfo Pro
allows users to explore spatial data within a dataset, symbolize features, and create
maps. For this assignment, I installed it using trial MapInfo Pro.
QGIS is a GIS software which is a free an open sources platform that supports viewing,
editing, and analysis of geospatial data. QGIS functions as GIS software, acquiesce
users to analyze and edit spatial information, in addition to compose and export
graphical maps.

2.2. Methodology
The exercise was used two scenarios from different software, ArcMap and MapInfo
Pro. The first scenario applied direct conversion and the second used via data
exchange format. So, I used two data format for original data. I used .shp that
developed by ESRI and .tab that developed by MapInfo. QGIS and GoogleEarth used
for geometry data simulation. Moreover, the Feature Manipulation Engine (FME) is a
package to interdict of spatial information among geometric and data format and
convert into several types of format data. The steps of this assignment shows in figure
1.

Figure 1. The methodology of this assignment

2.2.1. Create Geometry Objects
The geometry objects were made using ArcGIS, and MapInfo, which ArcGIS was used
to make the single geometry objects while MapInfo was used to make the multi
geometry objects.
• The single geometry objects
The exercise needed some objects with data format (such as .shp, .tab) which will be
converted to other data format. Figure 2 shows several types of geometry objects that
will be created by .shp, such as :

Figure 2. The single geometry objects

1. A polygon with holes

2. Multi polygon with holes
3. Multi Polygon
4. A Circle
5. An Ellipse
6. A Line
7. Line string
8. A Point
9. Multi point
10. Multi line string
11. Line ring
12. A polygon
13. Self-intersecting curves.
The single geometry objects was created using ArcGIS with their own data format, .shp
(shapefile). The steps to create the single types of objects shows in tables below.
Table 1. Steps to creat single objects.

Steps Figures Descriptions

1 For the first step was
creating a new shapefile in
the chosen folder that will
be saved.

2 After that give the name of

shapefile, choose the feature
type and define the
coordinate system.
3 Then, to start drawing, click
“start editing” in the editor,
continue to create a feature
and select the shape of the
object that wants to create. It
was Start editing the feature.
And then, create feature by
editing windows.

4 When add the information

from the features, it can click
open attribute table.

5 And then, Klik add field to

add the new table for giving
new description of
feature/geometry.
 6 After that a dialog box shows,
put the name field and
choose type of the table
(such as text/string, long
integer, double, float, etc).
Klik OK

7 In this case, I will add the

information of area by using
calculate geometry.

8 This was the result from

calculate geometry.

All the types of creating single geometry using ArcGIS was displayed in table .
 Table 2. Single geometry objects created

No. Geometry Objects Description

1. Point The object represents a single point in space. The
point can be either two dimensional (x,y) or three
dimensional (x,y,s). In this case was using Point
shapefile, respectively.
Afterward, click start editing in the editor, create the
feature and select .
2. Line For line was be using Polyline shapefile, respectively.
Then, create the feature and select . The
difference between line is the used point which line
has 2 points on start and the end of the line

3 Multipoint The object shows a collection of points and consists

of a list of coordinate-tuples. In this case, I choose
multi point as feature type was using Multipoint
shapefile, respectively.
Afterward, click start editing in the editor, create the
feature and select .
4 Line String The object represents a sequence of points joined
together to form a line. Hence, a line consist of a list
at least 2 coordinate tuples. For line-string were using
Polyline shapefile, respectively. Then, create the
feature and select . It has more than 2 points.

5 Line Ring The objects shows a special Line String which is

6 Multi Line String
closed. It closes itself automatically on every
addPoint/removePoint by adding a copy of the first
point as the last point.
The object shows a collection of lines and consist of a
list of line-like sequences.

7 Multi Polygon The object represents a collection of polygons that

consist of a list of polygons-like sequences that
 constract from exterior ring and (possible) hole list
tuples.

8 Polygon and Polygon with holes The object shows a filled area that consists of a list of
at least three coordinate tuples that forms the
outerior ring and a (possible) list of hole polygons.

9 Multi Polygon with holes The polygon with hole and multi-polygon with hole
are same like the process to make polygon with
adding another polygon inside after finish makes the
first polygon.

10 Self-intersecting curves The curve was using Polyline shapefile. After that,
create the geometry and select and then
. The curves will have many nodes.

11 Circle The objects was from polygon that was represent

from all points equidistant from a central point.
The circle and ellipse were using Polygon shapefile
12 Ellipse with creating and feature,
respectively. Both circle and ellipse contain by many
nodes.

All the shapefile data format I put some attribute data to test whether the data could
be read or not after transformation. Original data is displayed in table 1. Coordinates
Reference System Geographic Coordinate System WGS 84 with projected coordinate
system WGS 84 UTM Zone 49S and Coordinates Reference System Geographic
Coordinate System WGS 84 with datum WGS84 were create in this assignment.

• The multigeometry objects

The multi geometry objects was created using MapInfo Pro, because It could not
develop using ArcGIS in one layer. So, the multi geometry data format has .tab format
created While, .tab format was used to simulate multi geometry objects. All of the
shapefile format will be added some attribute data to check whether the data could
be read or not after being converted.
Table 3. Multi geometry objects created

Steps Figures Descriptions

1 To create multi-geometry object in
MapInfo, first step must klik New
Table in Table bar. And then, klik
create.

2 Then, add name and projection for

the object.
 3 Set the location for storing the
feature data. The data will have .tab
format.

4 After that draw the multi-geometry

in MapInfo with various of feature
data/geometry data (such as point,
polyline, polygon, ellipse, so on).

The multi geometry was created to know how if its format converted to other data
format. The multi geometry objects shows in figure 3.

Figure 3. The multi geometry objects

 The various geometry objects in one layer using MapInfo were multiple point, a point,
polyline with point, polygon, ellips, polygon with holes, polyline, curves, and line. The
geometry objects saved as MapInfo format standard which is .tab. The result looks like
using ArcGIS. In any case, the ellipse’s node in MapInfo was not same as ArcGIS. The
nodes of the ellipse in ArcGIS are in the entire shape of the curve itself. While in
MapInfo, the nodes of the ellipse just controlled by 4 in each side of the ellipse. The
representation of it shows in Figure 4.

Figure 4. Comparison ellipse geometry between using MapInfo and ArcGIS

2.2.2. Data Format Conversion

There were two scenario that actualizing in this assignment. The first was direct
conversion which the objective was perceived how profound the ability of every
software to convert the data format. The second was indirect conversion. It was using
spatial conversion tool which was universal translator using FME (The Feature
Manipulation Engine) and export tools. The objective for using two scenarios was
compared between data format types. The two types of geometry objects which
videlicet single geometry and multi geometry, will be tried in two different scenarios.
The object has been transformed to several data format, whether the continuing to
check the result conversion will be success or fail. Figure 5 shows the transformation
steps of direct conversion and figure 6 shows indirect conversion.
Figure 5. The process of direct conversion

Figure 6. The process of indirect conversion

• Direct Conversion
In the first scenario, ArcGIS and MapInfo are already used as the first software to
create geometry objects. Where the standard format of the two will be transferred to
various data formats, such as KML, GML, MIF, SHP, GeoJSON. In addition, QGIS and
Google Earth are involved in this scenario.
ArcGIS
ArcGIS can read a variety of different file formats. Shapefile is one of the spatial data
formats that you can work on and edit in ArcGIS. Shapefile is a format provided to
store geometric locations and geographic feature attribute information, there are
approximately 7 data formats that are attached as well when creating shapefiles using
ArcGIS.
From the .shp format, geometry data will be converted to KML and then opened and
analyzed with Google Earth. Figure 7 shows the conversion process is layer by layer
using the Layer to KML tool. Keyhole Marking Language (KML) is an XML-based
language provided by Google ™ to define graphical displays of spatial data in
applications such as Google Earth ™ and Google Maps ™. KML allows this application
to support the open integration of special data layers from many GIS users. KML files
have a .kml file extension or a .kmz file extension (for compressed and zipped KML
files).

Figure 7. SHP data format to KML data format using ArcGIS

QGIS
This software (QGIS) allows users to assess and edit specific information, in addition to making
and making available graphic maps. The SHP data obtained from ArcGIS can be directly opened
using QGIS. In addition, the geometry data in QGIS will be converted from the SHP format to
KML, GML, MIF and GeoJSON and will then be opened and analyzed with the Google Earth
and GeoJSON sites. Figure 8 to 9 shows the conversion process is layer by layer by clicking the
Layers menu and saving it as a file based on the chosen data format. But, before you convert,
you must add your data on the QGIS workspace. After that, It can be done repeatedly to other
data format, such as KML, GML, MIF, TAB and GeoJSON.
 Figure 8. The first steps to convert .shp to others format

Figure 9. .SHP to others data format

MapInfo
The table structure for MapInfo in ASCII format (* .TAB) is the main file for MapInfo
tables. Geometry data in MapInfo will be converted from TAB to SHP, GML and MIF
formats and then opened and analyzed with Google Earth and QGIS. Illustrations are
 shown in Figures 10 to 12, respectively. However, conversion from TAB to KML,
GeoJSON format is not supported through MapInfo software. Conversion data format
using MapInfo with function of export and Universal Translator.

Figure 10. The first step to convert from .tab to other format that provide by MapInfo

Figure 11. The second steps of coversion data format

 Figure 12. Approval dialog if the conversion steps was successfully

• Indirect Conversion
The second scenario is indirect conversion through data exchange format software.
MapInfo has been selected to perform this scenario. MapInfo develops the format
data conversion function through Universal Translator with Feature Manipulation
Engine (FME) which is a platform that streamlines the translation of spatial data
between geometric and digital formats. This is intended primarily to deal with using
GIS tools.
It facilitates the transformation of spatial data into various formats, data models and
repositories for transmission to end users. This process is called spatial extract, and
conversion. Therefore, the SHP data format obtained from ArcGIS will be converted
to MIF, and GML through .tab conversion data format.

2.2.3. Geometry Analysis

The result of geometry objects will be analyzed and examined more in results and
discussion part. It was separated into two part of results. The first result was about
direct conversion which will analyze the geometry, information data and coordinates
of the objects with consider on the utilized software. The second result will be
investigated on the geometry, information data and coordinates of the objects with
consider on the information of data format.

3. Result
3.1. Direct and Indirect Conversion
The direct conversion procedure was characterized. The result part was analyzed the
coordinates and nodes.
• Point Object
A few of criterion were checked to know how favorably the conversion. The criterion,
for example, geometry type and coordinates object. In the coordinate of objects was
recorded not too different, that implies the conversion result is successful. Table 4
shows the result analysis of difference in each file of point object from various data
format.
Table 4. The analyze of point data in each data format

Data Location Coordinate Features of Data Description

Format (X, Y)
.shp Surabaya Top : Attribute data
(Point) Zoo -7.295837 could be read.
Left :
112.736248
Bottom :
-7.295837
Right :
112.736248
.kml Surabaya Top : Attribute data
Zoo -7.295837 could be read.
Left :
112.736248
Bottom :
-7.295837
Right :
112.736248

.tab Surabaya Top : Attribute data

Zoo -7.295837 could be read.
Left :
112.736248
Bottom :
-7.295837
Right :
112.736248
 .GeoJSON Surabaya Top : Attribute data
(Feature) Zoo -7.295837 could be read.
Left :
112.736248
Bottom :
-7.295837
Right :
112.736248

* GCS_WGS_1984

• Line Object
Table 5 shows the results of the analysis of each file of line object about the difference
in terms of data type, could all the data format read the attribute or not, length and
coordinate point. From this table the .shp could be transformed very well because
there are no data missing.
Table 5. The analyze of line object in each data format

Data Location Coordinate Features of Description

Format (X, Y) Data
.shp Road Top : Length :
(Polyline) Surabaya- -7.243968 7204 m
Porong Left : 4.476615 mi
112.697328
Bottom : Attribute data
-7.304236 could be read
Right :
112.709509

.kml Road Top : Length :

Surabaya- -7.243968 7204 m
Porong Left : 4.476615 mi
112.697328
Bottom : Attribute data
-7.304236 could be read
Right :
112.709509
 .tab Road Top : Length :
Surabaya- -7.243968 4.497 mi
Porong Left :
112.697328 Attribute data
Bottom : could be read
-7.304236
Right :
112.709509

.GeoJSON Road Top : Length :

(Feature) Surabaya- -7.243968 7204 m
Porong Left : 4.476615 mi
112.697328
Bottom : Attribute data
-7.304236 could be read
Right :
112.709509

* GCS_WGS_1984

• Multipoint
A few of criterion were checked to know how favorably the conversion. The criterion,
for example, geometry type and coordinates object. In the coordinate of objects was
recorded not too different, that implies the conversion result is successful. Table 6
shows the result analysis of difference in each file of multipoint object from various
data format.
 Table 6. The analyze of multipoint data in each data format

Data Location Coordinate Features of Data Descriptions

Format (X, Y)
.shp Jagir Top : Attribute
(Multipoint) -7.289165 data could be
Left : read, There
112.780455 are 20 points
Bottom :
-7.326649
Right :
112.793004

.kml Jagir Top : Attribute

-7.289165 data could be
Left : read, There
112.780455 are 20 points
Bottom :
-7.326649
Right :
112.793004

.tab Jagir Top : Attribute

-7.289165 data could be
Left : read, There
112.780455 are 20 points
Bottom :
-7.326649
Right :
112.793004

.GeoJSON Jagir Top : Attribute

(Feature) -7.289165 data could be
Left : read, There
112.780455 are 20 points
Bottom :
-7.326649
Right :
112.793004

* GCS_WGS_1984
• Line String
Table 7 shows for checking the conversion file result for the polyline object, especially
for line string object, we can see the results of the analysis of each file of line string
object about the difference in terms of data type and coordinate the object.
Table 7. The analyze of line string data in each data format

Data Location Coordinate Features of Data Description

Format (X, Y)
.shp Around Top : Length :
(Polyline) Jambangan, -7.307477 6251 m
Surabaya Left : 3.884072 mi
112.710400 Attribute
data could be
Bottom :
read.
-7.327810
Right :
112.721838

.kml Around Top : Length :

Jambangan, -7.307477 6251 m
Surabaya Left : 3.884072 mi
112.710400 Attribute
data could be
Bottom :
read.
-7.327810
Right :
112.721838

.tab Around Top : Length :

Jambangan, -7.307477 3.896 mi
Surabaya Left : Attribute
112.710400 data could be
read.
Bottom :
-7.327810
Right :
112.721838
 .GeoJSON Around Top : Length :
(Feature) Jambangan, -7.307477 6251 m
Surabaya Left : 3.884072 mi
112.710400 Attribute
data could be
Bottom :
read.
-7.327810
Right :
112.721838

* GCS_WGS_1984

• Line Ring
Table 8 shows for checking the conversion file result for the polyline object, especially
for line ring object, we can see the results of the analysis of each file of line string
object about the difference in terms of data type and coordinate the object.
Table 8. The analyze of line ring data in each data format

Data Location Coordinate Features of Data Description

Format (X, Y)
.shp Jemursari Top : Length :
(Polyline) Area -7.319707 6933 m
Left : 4.308008 mi
112.735653 Attribute
data could
Bottom :
be read.
-7.329873
Right :
112.762987

.kml Jemursari Top : Length :

Area -7.319707 6933 m
Left : 4.308008 mi
112.735653 Attribute
data could
Bottom :
be read.
-7.329873
Right :
112.762987
 .tab Jemursari Top : Length :
Area -7.319707 4.309 mi
Left : Attribute
112.735653 data could
be read.
Bottom :
-7.329873
Right :
112.762987
.GeoJSON Jemursari Top : Length :
(Feature) Area -7.319707 6933 m
Left : 4.308008 mi
112.735653 Attribute
data could
Bottom :
be read.
-7.329873
Right :
112.762987

* GCS_WGS_1984

Table XX shows that features of object from several the coordinate of point object was
no change.

• Multi Line String

A few of criterion were checked to know how favorably the conversion. The criterion,
for example, geometry type and coordinates object. In the coordinate of objects was
recorded not too different, that implies the conversion result is successful. Table 9
shows the result analysis of difference in each file of multi-line string object from
various data format. The result shows that features of object from several the
coordinate of object was no change.
Table 9. The analyze of multi line string data in each data format

Data Location Coordinate Features of Data Description

Format (X, Y)
.shp Keputih Top : Length :
(Polyline) Area -7.289165 9259 m
Left : 5.753 mi
112.780455 Attribute data could
Bottom : be read.
-7.326649
Right :
112.793004
.kml Keputih Top : Length :
Area -7.289165 9259 m
Left : 5.753 mi
112.780455 Attribute data could
Bottom : be read.
-7.326649
Right :
112.793004

.tab Keputih Top : Length :

Area -7.289165 5.765 mi
Left : Attribute data could
112.780455 be read.
Bottom :
-7.326649
Right :
112.793004

.GeoJSON Keputih Top : Length :

(Feature) Area -7.289165 9259 m
Left : 5.753 mi
112.780455 Attribute data could
Bottom : be read.
-7.326649
Right :
112.793004

* GCS_WGS_1984
• Multi Polygon
A few of criterion were checked to know how favorably the conversion. The criterion,
for example, geometry type and coordinates object. In the coordinate of objects was
recorded not too different, that implies the conversion result is successful. Table 10
shows the result analysis of difference in each file of multi-polygon object from various
data format.
Table 10. The analyze of multi-polygon data in each data format

Data Location Coordinate Features of Data Description

Format (X, Y)
.shp Menur Top : Area :
(Polygon) Area -7.254840 5381751.000
Left : m
112.756427 2.078 mi
Perimeter :
Bottom :
11.345 mi
-7.280076
Attribute
Right : data could
112.798138 be read.
.kml Menur Top : Area :
Area -7.254840 5381751.000
Left : m
112.756427 2.078 mi
Perimeter :
Bottom :
11.345 mi
-7.280076
Attribute
Right : data could
112.798138 be read.

.tab Menur Top : Area :

Area -7.254840 2.0864 mi
Left : Perimeter :
112.756427 11.368 mi
Attribute
Bottom :
data could
-7.280076
be read.
Right :
112.798138
.GeoJSON Menur Top : Area :
(Feature) Area -7.254840 5381751.000
Left : m
112.756427 2.078 mi
Perimeter :
Bottom :
11.345 mi
-7.280076
Attribute
Right : data could
112.798138 be read.

* GCS_WGS_1984
• Polygon
A few of criterion were checked to know how favorably the conversion. The criterion,
for example, geometry type and coordinates object. In the coordinate of objects was
recorded not too different, that implies the conversion result is successful. Table 11
shows the result analysis of difference in each file of polygon object from various data
format.
Table 11. The analyze of polygon data in each data format

Data Location Coordinate Features of Data Description

Format (X, Y)
.shp Tambak Top : Area :
(Polygon) Rejo -7.342675 9030484 m
Left : 3.486689 mi
112.766926 Perimeter :
8.663801 mi
Bottom :
Attribute data
-7.372017
could be read.
Right :
112.807023

.kml Tambak Top : Area :

Rejo -7.342675 9030484 m
Left : 3.486689 mi
112.766926 Perimeter :
8.663801 mi
Bottom :
Attribute data
-7.372017
could be read.
Right :
112.807023

.tab Tambak Top : Area :

Rejo -7.342675 3.501 mi
Left : Perimeter :
112.766926 8.676 mi
Attribute data
Bottom :
could be read.
-7.372017
Right :
112.807023
 .GeoJSON Tambak Top : Area :
(Feature) Rejo -7.342675 9030484 m
Left : 3.486689 mi
112.766926 Perimeter :
8.663801 mi
Bottom :
Attribute data
-7.372017
could be read.
Right :
112.807023

* GCS_WGS_1984

• Polygon with Holes

A few of criterion were checked to know how favorably the conversion. The criterion,
for example, geometry type and coordinates object. In the coordinate of objects was
recorded not too different, that implies the conversion result is successful. Table 12
shows the result analysis of difference in each file of polygon with holes object from
various data format.
Table 12. The analyze of polygon with holes data in each data format

Data Location Coordinate Features of Data Description

Format (X, Y)
.shp Around Top : Area :
(Polygon) Gresik -7.148965 17234346
Harbour Left : m
112.612587 6.654218
Bottom : mi
-7.215164 Attribute
Right : data could
112.663086 be read.

.kml Around Top : Area :

Gresik -7.148965 17234346
Harbour Left : m
112.612587 6.654218
Bottom : mi
-7.215164 Attribute
Right : data could
112.663086 be read.
 .tab Around Top : Area :
Gresik -7.148965 6.683 mi
Harbour Left : Attribute
112.612587 data could
Bottom : be read.
-7.215164
Right :
112.663086

.GeoJSON Around Top : Area :

(Feature) Gresik -7.148965 17234346
Harbour Left : m
112.612587 6.654218
Bottom : mi
-7.215164 Attribute
Right : data could
112.663086 be read.

* GCS_WGS_1984

• Multi Polygon with Holes

A few of criterion were checked to know how favorably the conversion. The criterion,
for example, geometry type and coordinates object. In the coordinate of objects was
recorded not too different, that implies the conversion result is successful. Table 13
shows the result analysis of difference in each file of multi polygon with holes object
from various data format.
 Table 13. The analyze of multi polygon with holes data in each data format

Data Location Coordinate Features of Data Description

Format (X, Y)
.shp Around Top : Area :
(Polygon) Perak -7.194250 9562866 m
Harbour Left : 3.692mi
112.723160 Perimeter :
Bottom : 16.536mi
-7.242058 Attribute
Right : data could
112.771471 be read.

.kml Around Top : Area :

Perak -7.194250 9562866 m
Harbour Left : 3.692mi
112.723160 Perimeter :
Bottom : 16.536mi
-7.242058 Attribute
Right : data could
112.771471 be read.

.tab Around Top : Area :

Perak -7.194250 3.7075mi
Harbour Left : Perimeter :
112.723160 16.582mi
Bottom : Attribute
-7.242058 data could
Right : be read.
112.771471

.GeoJSON Around Top : Area :

(Feature) Perak -7.194250 9562866 m
Harbour Left : 3.692mi
112.723160 Perimeter :
Bottom : 16.536mi
-7.242058 Attribute
Right : data could
112.771471 be read.

* GCS_WGS_1984

• Self Intersecting Curves

Table 14 shows the results of the analysis of each file of curve using object about the
difference in terms of data type, could all the data format read the attribute or not,
length and coordinate point. From this table the .shp could be transformed very well
because there are no data missing. I was draw the curve with line and curve with
intersect that could be seen in a shape, in .shp data format the curve is look really
smooth but in .kml and .geojson this curve looks rough and could be seen the edge
from each line
Table 14. The analyze of multi line string data in each data format

Data Location Coordinate Features of Data Descriptions

Format (X, Y)
.shp Krian Top : Length :
(Polyline) area -7.390113 15.863499mi
Left : 25530 meters
112.566663 Attribute data
Bottom : could be read.
-7.457993
Right :
112.619336

.kml Krian Top : Length :

area -7.390113 15.863499mi
Left : 25530 meters
112.566663 Attribute data
Bottom : could be read.
-7.457993
Right :
112.619336

.tab Krian Top : Length :

area -7.390113 15.89 mi
Left : Attribute data
112.566663 could be read
Bottom :
-7.457993
Right :
112.619336
 .GeoJSON Krian Top : Length :
(Feature) area -7.390113 15.863499mi
Left : 25530 meters
112.566663 Attribute data
Bottom : could be read.
-7.457993
Right :
112.619336

* GCS_WGS_1984

• Circle
A few of criterion were checked to know how favorably the conversion. The criterion,
for example, geometry type and coordinates object. In the coordinate of objects was
recorded not too different, that implies the conversion result is successful. Table 15
shows the result analysis of difference in each file of circle object from various data
format.
Table 15. The analyze of multi line string data in each data format

Data Location Coordinate Features of Data Description

Format (X, Y)
.shp Dukuh Top : Area :
(Polygon) Pakis -7.267604 1242950 m
Left : 0.479906 mi
112.687769 Attribute
Bottom : data could
be read.
-7.278980
Right :
112.699161

.kml Dukuh Top : Area :

Pakis -7.267604 1242950 m
Left : 0.479906 mi
112.687769 Attribute
Bottom : data could
be read.
-7.278980
Right :
112.699161
 .tab Dukuh Top : Area :
Pakis -7.267604 0.4819mi
Left : Attribute
112.687769 data could
Bottom : be read.
-7.278980
Right :
112.699161

.GeoJSON Dukuh Top : Area :

(Feature) Pakis -7.267604 1242950 m
Left : 0.479906 mi
112.687769 Attribute
Bottom : data could
be read.
-7.278980
Right :
112.699161

* GCS_WGS_1984

• Ellipse
A few of criterion were checked to know how favorably the conversion. The criterion,
for example, geometry type and coordinates object. In the coordinate of objects was
recorded not too different, that implies the conversion result is successful. Table 16
shows the result analysis of difference in each file of ellipse object from various data
format.
Table 16. The analyze of multi line string data in each data format

Data Location Coordinate Features of Data Description

Format (X, Y)
.shp Lontar Top : Area :
(Polygon) Area -7.274029 1518323 m
Left : 0.586228 mi
112.658025 Perimeter :
Bottom : 3.076735 mi
-7.282281 Attribute
data could
Right :
be read.
112.677210
 .kml Lontar Top : Area :
Area -7.274029 1518323 m
Left : 0.586228 mi
112.658025 Perimeter :
Bottom : 3.076735 mi
-7.282281 Attribute
data could
Right :
be read.
112.677210
.tab Lontar Top : Area :
Area -7.274029 0.5887 mi
Left : Perimeter :
112.658025 3.078 mi
Bottom : Attribute
-7.282281 data could
be read.
Right :
112.677210
.GeoJSON Lontar Top : Area :
(Feature) Area -7.274029 1518323 m
Left : 0.586228 mi
112.658025 Perimeter :
Bottom : 3.076735 mi
-7.282281 Attribute
data could
Right :
be read.
112.677210
* GCS_WGS_1984

• Multigeometry
The result of multigeometry that created via MapInfo (.tab), there was some lack
when the conversion process. Multigeometry features .tab convert to data format
.shp, the geometry automatically devide by each feature (such as, arc, ellipse, point,
polyline, polygon/region). So that, I didn’t continue the conversion data format to
others data format (such as, KML and GeoJSON). In this case, the multi geometry that
create by using MapInfo whish has .tab data format. So, the conversion data format
has only .tab to MIF, SHP and GML. The data format .mif and .gml, the multigeometry
still a feature “multigeometry’, the opposite of that .tab (9 types of geometry) to .shp
the features had been separate be 5 types of features ( arc, ellipse, point, polyline,
region/polygon).

3.2. Conversion strategies and the limitations

The spatial data conversion standard or GIS software has solved the tackled the issue
of spatial data conversion between difference various GIS software. Nevertheless, it
was not an ideal strategy. The data sharing was based on the files, which can be
utilized for data however can't express precisely and data information missing
happens. In addition, real time spatial data updates and consistency data sharing at
the level of features. In one aspect, due to of lack the description method for spatial
objects can't be realized through external data exchange. To get great conversion data
format results, we can use the global coordinate system to avoid related problems.
Based on the exercise that I used to convert the shapefile data format in QGIS with
the coordinate system used projected UTM Zone 49S to the GeoJSON data format. In
geojson.io, the WGS 84 coordinate system is actually used in the framework. Because
of that I transformed the coordinates features to a global system objects using ArcGIS,
GCS-WGS 84, so that it can be opened on geojson.io. I have done the transformation
but the results show that the geometry object deviates slightly from its original point.
By using a global coordinate system, it can minimize the lacks with geometry
calculations. Because the universal coordinate system uses units of degrees, whereas
for calculating distances and areas, units of length, such as meters, kilometers, feet,
miles, etc. are needed.
MIF and TAB are converted datasets from MapInfo, MIF files are created by exporting
TAB files. MIF format is more supported for the interchange format. MapInfo data sets
provide more data types in writing and reading than other formats. Therefore,
information is added to Map Info, so before using the MIF / TAB format it must be
transferred to the required format.
SHP has a limitation of not being able to provide geometry collections in one layer. So
that the collection of geometries breaks down into data types provided by the SHP
(e.g. Points, polylines, regions, ellipses, polygons). Other limitations are in terms of
features that cannot be supported such as multi-patch or multipoint geometry,
geometry that crosses the dateline, or self-intersections in polygons. So that it can
affect changes in data in a file after transferring by following the types of features,
such as line, polygon, and point.
KML uses a tag-based structure with nested elements and attributes based on the XML
standard. This can only be displayed on an Earth Browser (e.g., Google earth pro) that
depends on the internet. Earth browser in this case cannot support changing the type
of object in the Earth browser.
Meanwhile, GeoJSON is a data format used to encode information using JSON which
is created as text and has a flexible scheme. Therefore, GeoJSON can only be accessed
through web services (eg Geojson.io, ArcGIS online) and must be in UTF-8 encoding.
Therefore, KML can be produced by creating features using the Mapbox Editor or by
transferring the data to another format.
MapInfo has restrictions in terms of transferring to several types of formats. Because,
the universal translator from MapInfo only has the Autodesk AutoCAD format (dxf,
dwg), Bentley Micro Station Design (fc1, pos, with), Esri Arc Info Export (e00), Esri
geodatabase (gdb), Esri Shape (Shp), GML SF-0 (gml, xml, gz) and MapInfo (mif, tab).
So, if you want to convert from .tab to GeoJSON you can use QGIS software or online
web, because MapInfo cannot support the format data conversion to GeoJSON.
Meanwhile, QGIS supports many formats including MIF, TAB, SHP, KML, GML and
GeoJSON. Moreover, QGIS can also transfer and open several other types of data
formats. For example, the SHP format generated by MapInfo can displayed in QGIS.
To prevent the lack of data information and change, when importing MIF format to
 QGIS (e.g., Geometry Collection), transfer to GeoJSON and KML can be done from SHP
after transferring MIF to SHP using universal translator from MapInfo.
GeoJSON can be converted using between ArcGIS online and QGIS, while KML can be
seen between the Earth browser and ArcGIS because ArcGIS has a conversion tool
between formats and KML layers on the ArcGIS desktop. While between ArcGIS and
MapInfo, KML and GeoJSON cannot be used as data conversion. If you want to convert
the data between ArcGIS and MapInfo, it needs to do transfer data move into a format
that is supported in every previous software.

4. Conclusion
Based on the result, considering the limitations from every data format, data
conversion was better utilized with .KML between ArcGIS and Earth program.
Meanwhile, Conversion tools that developed by MapInfo was Universal Translator.
Data transfer can be done using a universal translator in MapInfo and saved in a data
format that can be opened through QGIS. In the other case, data is converted to
another format without any data changes, lacking or missing data. Sometimes, if the
data feature is not successfully transferred to other data formats because it becomes
one of the limitations of the software. In addition, sometimes there is no change in
coordination after transfer.
Whatever QGIS does not support displaying geometry collections in one layer,
transferring data formats can be done easily using QGIS rather than MapInfo.
Considering the limitations of each format, transferring data is better using platforms
that support the KML data format between ArcGIS and the Earth browser.
Although ArcGIS and QGIS have many similarities including the format of data they
can retrieve, workspace files generated by software in ArcGIS (.mxd) cannot be
accessed easily from QGIS and vice versa (QGIS workspace format was .qgs map files
not really compatible when opened using ArcGIS). This shows that there are several
mapping components provided in ArcGIS such as labeling, symbology, legends etc.
must be regenerated in QGIS if the user must switch between the two applications.