<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Developing Big Data Analytics Architecture for Spatial Data</article-title>
      </title-group>
      <contrib-group>
        <aff id="aff0">
          <label>0</label>
          <institution>Purnima Shah Supervised by Sanjay Chaudhary School of Engineering and Applied Science, Ahmedabad University</institution>
          ,
          <country country="IN">India</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2019</year>
      </pub-date>
      <fpage>3963</fpage>
      <lpage>3965</lpage>
      <abstract>
        <p>The main goal of the research work is to solve a wide range of data problems by offering batch, iterative, and interactive computations in a unified architecture. The dissertation proposes an integrated architecture to manage a large amount of massively distributed data including spatial data. The implementation architecture has three major components: data preparation, data analytics, and data visualization. As a part of the implementation, a novel big spatial data analytics framework is developed to load, store, process, and query spatial and non-spatial data at scale. As proof of concept, spatial analytics applications are developed using agricultural reallife datasets.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. INTRODUCTION</title>
      <p>
        In the mobile and Internet era, massive scale data is generated from
disparate sources with spatial components. Today’s users demand
high speed, scalable, sophisticated, economic, and accessible
solutions to perform relevant analytics on complex and distributed
data including spatial data. The conventional systems for data
management are becoming less capable to scale out extensively to
meet the current users’ demand due to limited computational power
and storage. The modern technologies like Big Data and Big Data
Analytics (BDA) have a huge potential to handle massive scale data
with high scalability and low latency. Though the modern big data
management tools such as Not only SQL (NoSQL) databases,
Hadoop [1], and Spark [
        <xref ref-type="bibr" rid="ref1">2</xref>
        ] are highly efficient, they offer limited
functions and methods for spatial data management. In addition, in
modern application development, only one specific big data tool
would not be able to manage big data efficiently and effectively.
Hence, it is highly enviable to exploit the potential features of big
data tools and technologies and propose integrated frameworks and
architectures built on top of more than one technology to develop
robust and powerful applications including geospatial data.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. REVIEW STATUS</title>
      <p>The research reviewed existing databases, frameworks, and
architectures for spatial data management.</p>
    </sec>
    <sec id="sec-3">
      <title>2.1 Database technologies for spatial data</title>
      <p>
        NoSQL databases such as Cassandra [
        <xref ref-type="bibr" rid="ref2">3</xref>
        ] do not offer native support
for spatial data. As an exception, MongoDB [
        <xref ref-type="bibr" rid="ref3">4</xref>
        ] offers query
operations on geospatial data with index support. Though
MongoDB is the best suitable NoSQL database for geospatial data,
it does not offer complex spatial operations like KNN search,
spatial join, and KNN join. It also does not provide support for
aggregated queries. Ben Brahim et al. [
        <xref ref-type="bibr" rid="ref4">5</xref>
        ] have developed a spatial
extension for the Cassandra database to solve spatial range queries.
      </p>
    </sec>
    <sec id="sec-4">
      <title>2.2 Big data computational frameworks for spatial data</title>
      <p>
        The Big data computational frameworks such as Spark and Hadoop
don’t offer native support for spatial data. A number of extended
systems have made important contributions to extend the
functionality of Hadoop/Spark engine for spatial data management.
These extension systems include parallel DB systems such as
Parallel Secondo, MapReduce systems such as ESRI Tools for
Hadoop [
        <xref ref-type="bibr" rid="ref5">6</xref>
        ], SpatialHadoop [
        <xref ref-type="bibr" rid="ref6">7</xref>
        ], Hadoop-GIS [
        <xref ref-type="bibr" rid="ref7">8</xref>
        ], and systems that
use Resilient Distributed Datasets (RDD) [
        <xref ref-type="bibr" rid="ref8">9</xref>
        ] such as GeoTrellis
[
        <xref ref-type="bibr" rid="ref9">10</xref>
        ], SpatialSpark [11], GeoSpark [
        <xref ref-type="bibr" rid="ref10">12</xref>
        ], Magellan [
        <xref ref-type="bibr" rid="ref11">13</xref>
        ],
LocationSpark [
        <xref ref-type="bibr" rid="ref12">14</xref>
        ], and Spatial In-Memory Big Data Analytics
(SIMBA) [
        <xref ref-type="bibr" rid="ref13">15</xref>
        ]. However, these frameworks are only able to execute
spatial operations on datasets that are available in text-based file
formats (CSV/GeoJSON/shapefiles and WKT), and stored in
HDFS or local disk. There is no big data analytics framework
available which reads data from the NoSQL database and performs
spatial analytics on those data.
      </p>
    </sec>
    <sec id="sec-5">
      <title>2.3 Big data architectures for spatial data</title>
      <p>
        Generally, big data architectures are designed and developed to
achieve a specific goal. Many big data architectures such as
Lambda [
        <xref ref-type="bibr" rid="ref14">16</xref>
        ], Kappa [
        <xref ref-type="bibr" rid="ref15">17</xref>
        ], Liquid [
        <xref ref-type="bibr" rid="ref16">18</xref>
        ], BDAS [19], SMACK [20],
and HPCC [21] have been developed on top of integrated
infrastructures. However, there have been insufficient discussions
about how these architectures perform spatial data management.
The research reviewed the existing platforms and architectures such
as IBM PARIS [22], SMASH [23], and ORANGE [24] for spatial
data management. In comparison with the existing big spatial data
architectures, the proposed architecture is in-memory and open
source.
      </p>
      <p>There are many big spatial data frameworks have been developed
on top of big data stack composed of Spark and Cassandra. The
Cassandra-Solr-Spark framework has been developed by Datastax
to enable spatial query processing on top of the big data stack. The
framework provides SQL like query interface to perform spatial
operations. However, it does not support join operations. It has also
not been evaluated based on the performance metric. P. Shah et al.
[25, 26] have developed a big data analytics framework including
geospatial data. The spatial analytics applications in the agriculture
domain have been developed using third-party GeoSpark libraries.
The major drawback of the framework is data duplication.
GeoSpark is a spatial extension for spark which can only access
data available in HDFS or local disk.</p>
    </sec>
    <sec id="sec-6">
      <title>3. BIG DATA ANALYTICS</title>
    </sec>
    <sec id="sec-7">
      <title>ARCHITECTURE FOR SPATIAL DATA</title>
      <p>The big data analytics architecture [26] is built and implemented on
big data open source technologies for the enrichment of massive
scale data including spatial data. The architecture is designed to
provide scalable, flexible, extendible, and cost-effective solutions
with available infrastructures and tools for agriculture. Architecture
implementation has three components: data preparation, big spatial
analytics, and data visualization. There are four types of user
interaction with the architecture: 1) System developer, 2) Data
scientist, 3) Domain expert, and 4) End users. The proposed
architecture is shown in figure 1.</p>
    </sec>
    <sec id="sec-8">
      <title>3.2 Big Spatial Data Analytics Framework</title>
      <p>
        The main purpose of a big spatial data analytics framework [
        <xref ref-type="bibr" rid="ref17">27</xref>
        ] is
to enable spatial data management on large scale data. The
consistent datasets generated by data preparation services are
processed and analyzed using data analytics framework. It is an
integrated infrastructure designed to manage spatial data efficiently
and effectively by exploiting the potential features provided by the
standard storage and processing big data frameworks. It is realized
on top of big data stack with Spark as a core processing engine and
Cassandra as a data storage. The big spatial data analytics
framework is shown in figure 3.
      </p>
    </sec>
    <sec id="sec-9">
      <title>3.1 Data Preparation Framework</title>
      <p>The data preparation framework is implemented to fetch consistent
and clean data from disparate sources and store into a persistent
database. It provides two layers of data abstraction. First, it hides
all physical data sources from the data repository. Second, it further
unifies the data available in a data repository using various complex
tools and techniques such as data fusion algorithms, schema
mapping tools, and record linkage algorithms. The implementation
architecture for data preparation framework is shown in figure 2.
A NoSQL i.e. Cassandra based spatial data storage framework is
built and implemented. The framework offers distributed and
scalable APIs for spatial operations such as location search,
proximity search, and KNN search.</p>
      <p>The framework provides a convenient web-based REST interface
to the end user. Cassandra performs fast data retrieval based on
partition key and clustering key compared to Spark. The application
architecture facilitates end users to execute ad-hoc queries on a
suitable framework either Spark or Cassandra via a common user
interface. The low latency queries are executed on Cassandra,
whereas complex queries (e.g. aggregated and spatial queries) are
executed on the Spark framework. The analytical results are
explored to end users through visualization and REST interface.
The performance of the framework is evaluated in terms of latency
against the variable size of data. The performance of the framework
is compared with the baseline technology, i.e. Cassandra for low
latency queries.</p>
    </sec>
    <sec id="sec-10">
      <title>3.3 Data Visualization Framework</title>
      <p>Data visualization makes complex data more accessible,
understandable, and usable. The implementation architecture
provides a web-based user interface by developing analytical and
visualization services through Restful ad-hoc APIs and interactive
maps.</p>
      <p>The Data visualization framework [26] is implemented to showcase
the analytical results with dynamic layouts. A dashboard
application is designed and implemented to depict the analytical
results in the agriculture domain.</p>
    </sec>
    <sec id="sec-11">
      <title>4. REALIZATION OF ARCHITECTURE IN</title>
    </sec>
    <sec id="sec-12">
      <title>APPLICATION DOMAIN</title>
      <p>The challenges related to big data application development in
agriculture is different in developed countries and developing
countries. In developing countries, the major barriers for big data
application development in agriculture are lack of tools,
infrastructures, data standards, semantics, integrated data models,
developers APIs, unified access points for public and private data,
technical expertise, and finally the data.</p>
      <p>The prototype applications in the agriculture domain are developed
on top of the big data analytics architecture. Spatial and non-spatial
data on weather, crop, and market are collected from different
sources like meteorological departments, agriculture universities,
and web portals. The summary of data collection is given in Table
1. The snapshots of the dashboard results are shown in figure 4 and
5.</p>
    </sec>
    <sec id="sec-13">
      <title>5. Implementation Status – Present and</title>
    </sec>
    <sec id="sec-14">
      <title>Future</title>
      <p>The big data analytics architecture is designed and developed for
massive scale data management including spatial data. The
architecture is developed to address two big data challenges:
Variety and Volume. The data preparation framework is designed
with two levels of data abstraction. As a part of implementation, the
REST interface is designed and implemented to fetch and collect
data from different data sources with different formats such as PDF,
spreadsheets, documents, web pages, and online services. The
integration of data collected through the REST interface is the most
critical module in data preparation framework. An algorithmic
solution is to be devised to link a variety of data from diverse
sources in aid of the unified search, query, and analysis.
The core component of big data analytics architecture, i.e. big data
analytics framework is implemented for spatial data management.
The framework is to be extended by developing complex spatial
operations like spatial join and kNN join. The spatial applications
like spatial aggregation and spatial auto-correlation are to be
developed on top of the framework. The complex applications in
the agriculture domain are to be developed by identifying new data
sources, formats, and data types. The real-life datasets including
real-time and streaming data are to be collected and stored in a data
repository to perform further analytics. The near real-time data
analytics and visualization algorithms are to be devised to process
real-time data like weather, disaster, etc. The analytical services
like rainfall prediction, crop recommendation, crop price
prediction, agro-inputs procurement, supply chain management,
crop disease alert, fertilizer recommendations, etc. are to be
implemented. These services can be used to generate customized
and multilingual solutions in the form of weather-based crop
calendar and alerts based on adverse events.</p>
    </sec>
    <sec id="sec-15">
      <title>6. ACKNOWLEDGMENTS</title>
      <p>I would like to acknowledge and thank my Ph.D. thesis supervisor
Dr. Sanjay Chaudhary, for his excellent guidance, constant
encouragement, patience, care, and support. This work is a part of
a research project on ‘Developing Data Analytics Architecture,
Applications in Agriculture’, funded by NRDMS and NSDI,
Department of Science and Technology, Government of India.</p>
    </sec>
    <sec id="sec-16">
      <title>7. REFERENCES</title>
      <p>[1] Hadoop, Apache. "Hadoop." 2009-03-06. http://hadoop.</p>
      <p>apache.org (2009).
[11] Web site of</p>
      <p>http://simin.me/projects/spatialspark/</p>
      <p>Stack.</p>
      <p>,
[23] Sinnott, Richard O., Luca Morandini, and Siqi Wu. "SMASH:
A cloud-based architecture for big data processing and
visualization of traffic data." In Data Science and Data
Intensive Systems (DSDIS), 2015 IEEE International
Conference on, pp. 53-60. IEEE, 2015.
[25] Shah, Purnima, Deepak Hiremath, and Sanjay Chaudhary.
"Big data analytics architecture for agro advisory system." In
High Performance Computing Workshops (HiPCW), 2016
IEEE 23rd International Conference on, pp. 43-49. IEEE,
2016.
[26] Shah, Purnima, Deepak Hiremath, and Sanjay Chaudhary.
"Towards development of spark based agricultural
information system including geo-spatial data." In Big Data
(Big Data), 2017 IEEE International Conference on, pp.
34763481. IEEE, 2017.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Zaharia</surname>
            , Matei, Mosharaf Chowdhury,
            <given-names>Michael J.</given-names>
          </string-name>
          <string-name>
            <surname>Franklin</surname>
            ,
            <given-names>Scott</given-names>
          </string-name>
          <string-name>
            <surname>Shenker</surname>
            , and
            <given-names>Ion</given-names>
          </string-name>
          <string-name>
            <surname>Stoica</surname>
          </string-name>
          .
          <article-title>"Spark: Cluster computing with working sets."</article-title>
          <source>Hot Cloud</source>
          <volume>10</volume>
          , no.
          <fpage>10</fpage>
          -
          <lpage>10</lpage>
          (
          <year>2010</year>
          ):
          <fpage>95</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Lakshman</surname>
            , Avinash, and
            <given-names>Prashant</given-names>
          </string-name>
          <string-name>
            <surname>Malik</surname>
          </string-name>
          .
          <article-title>"Cassandra: a decentralized structured storage system</article-title>
          .
          <source>" ACM SIGOPS Operating Systems Review</source>
          <volume>44</volume>
          , no.
          <issue>2</issue>
          (
          <year>2010</year>
          ):
          <fpage>35</fpage>
          -
          <lpage>40</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>[4] Website of MongoDB, http://www.mongodb.org.</mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Brahim</surname>
            ,
            <given-names>Mohamed</given-names>
          </string-name>
          <string-name>
            <surname>Ben</surname>
            , Wassim Drira, Fethi Filali, and
            <given-names>Noureddine</given-names>
          </string-name>
          <string-name>
            <surname>Hamdi</surname>
          </string-name>
          .
          <article-title>"Spatial data extension for Cassandra NoSQL database</article-title>
          .
          <source>" Journal of Big Data</source>
          <volume>3</volume>
          , no.
          <issue>1</issue>
          (
          <year>2016</year>
          ):
          <fpage>11</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Esri</surname>
            ,
            <given-names>G. I. S.</given-names>
          </string-name>
          "Tools for Hadoop.
          <source>"</source>
          (
          <year>2015</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Eldawy</surname>
            , Ahmed,
            <given-names>and Mohamed F.</given-names>
          </string-name>
          <string-name>
            <surname>Mokbel</surname>
          </string-name>
          .
          <article-title>"Spatialhadoop: A mapreduce framework for spatial data." In Data Engineering (ICDE</article-title>
          ),
          <year>2015</year>
          IEEE 31st International Conference on, pp.
          <fpage>1352</fpage>
          -
          <lpage>1363</lpage>
          . IEEE,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Aji</surname>
            , Ablimit, Fusheng Wang, Hoang Vo,
            <given-names>Rubao</given-names>
          </string-name>
          <string-name>
            <surname>Lee</surname>
            , Qiaoling Liu, Xiaodong Zhang, and
            <given-names>Joel</given-names>
          </string-name>
          <string-name>
            <surname>Saltz</surname>
          </string-name>
          .
          <article-title>"Hadoopgis: a high performance spatial data warehousing system over mapreduce." Proceedings of the VLDB Endowment 6</article-title>
          , no.
          <volume>11</volume>
          (
          <year>2013</year>
          ):
          <fpage>1009</fpage>
          -
          <lpage>1020</lpage>
          . \
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Zaharia</surname>
          </string-name>
          , Matei, Mosharaf Chowdhury,
          <string-name>
            <surname>Tathagata Das</surname>
          </string-name>
          ,
          <string-name>
            <surname>Ankur Dave</surname>
          </string-name>
          , Justin Ma,
          <string-name>
            <surname>Murphy</surname>
            <given-names>McCauley</given-names>
          </string-name>
          ,
          <string-name>
            <given-names>Michael J.</given-names>
            <surname>Franklin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Scott</given-names>
            <surname>Shenker</surname>
          </string-name>
          , and
          <string-name>
            <given-names>Ion</given-names>
            <surname>Stoica</surname>
          </string-name>
          .
          <article-title>"Resilient distributed datasets: A fault-tolerant abstraction for in-memory cluster computing."</article-title>
          <source>In Proceedings of the 9th USENIX conference on Networked Systems Design and Implementation</source>
          , pp.
          <fpage>2</fpage>
          -
          <lpage>2</lpage>
          . USENIX Association,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Kini</surname>
            , Ameet, and
            <given-names>Rob</given-names>
          </string-name>
          <string-name>
            <surname>Emanuele</surname>
          </string-name>
          .
          <article-title>"Geotrellis: Adding geospatial capabilities to spark." Spark Summit (</article-title>
          <year>2014</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [12]
          <string-name>
            <surname>Yu</surname>
            , Jia, Jinxuan Wu, and
            <given-names>Mohamed</given-names>
          </string-name>
          <string-name>
            <surname>Sarwat</surname>
          </string-name>
          .
          <article-title>"Geospark: A cluster computing framework for processing large-scale spatial data."</article-title>
          <source>In Proceedings of the 23rd SIGSPATIAL International Conference on Advances in Geographic Information Systems</source>
          , p.
          <fpage>70</fpage>
          . ACM,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [13]
          <article-title>Web site of Magellan</article-title>
          . https://github.com/harsha2010/magellan. Magellan - https://hortonworks.com/blog/magellan-geospatial
          <string-name>
            <surname>-</surname>
          </string-name>
          analyticsin-spark/; https://github.com/harsha2010/magellan.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [14]
          <string-name>
            <surname>Tang</surname>
            , Mingjie,
            <given-names>Yongyang</given-names>
          </string-name>
          <string-name>
            <surname>Yu</surname>
          </string-name>
          ,
          <string-name>
            <surname>Qutaibah M. Malluhi</surname>
          </string-name>
          , Mourad Ouzzani, and
          <string-name>
            <surname>Walid</surname>
            <given-names>G.</given-names>
          </string-name>
          <string-name>
            <surname>Aref</surname>
          </string-name>
          .
          <article-title>"Locationspark: a distributed inmemory data management system for big spatial data." Proceedings of the VLDB Endowment 9</article-title>
          , no.
          <volume>13</volume>
          (
          <year>2016</year>
          ):
          <fpage>1565</fpage>
          -
          <lpage>1568</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [15]
          <string-name>
            <surname>Xie</surname>
            , Dong,
            <given-names>Feifei</given-names>
          </string-name>
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>Bin</given-names>
          </string-name>
          <string-name>
            <surname>Yao</surname>
            ,
            <given-names>Gefei</given-names>
          </string-name>
          <string-name>
            <surname>Li</surname>
            ,
            <given-names>Liang</given-names>
          </string-name>
          <string-name>
            <surname>Zhou</surname>
            , and
            <given-names>Minyi</given-names>
          </string-name>
          <string-name>
            <surname>Guo</surname>
          </string-name>
          .
          <article-title>"Simba: Efficient in-memory spatial analytics."</article-title>
          <source>In Proceedings of the 2016 International Conference on Management of Data</source>
          , pp.
          <fpage>1071</fpage>
          -
          <lpage>1085</lpage>
          . ACM,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [16] “Lambda Architecture,” http://lambda-architecture.
          <source>net/</source>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [17] “Kappa Architecture,” http://radar.oreilly.com/
          <year>2014</year>
          /07/
          <article-title>questioning-the-lambda-architecture</article-title>
          .html,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [18]
          <string-name>
            <surname>Fernandez</surname>
            ,
            <given-names>Raul</given-names>
          </string-name>
          <string-name>
            <surname>Castro</surname>
          </string-name>
          ,
          <string-name>
            <surname>Peter R. Pietzuch</surname>
          </string-name>
          , Jay Kreps, NehaNarkhede, Jun Rao, Joel Koshy, Dong Lin, Chris
          <string-name>
            <surname>Riccomini</surname>
            , and
            <given-names>Guozhang</given-names>
          </string-name>
          <string-name>
            <surname>Wang</surname>
          </string-name>
          .
          <article-title>"Liquid: Unifying Nearline and Offline Big Data Integration."</article-title>
          <source>In CIDR</source>
          .
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [27]
          <string-name>
            <surname>Shah</surname>
            , Purnima, and
            <given-names>Sanjay</given-names>
          </string-name>
          <string-name>
            <surname>Chaudhary</surname>
          </string-name>
          .
          <article-title>"Big Data Analytics Framework for Spatial Data."</article-title>
          <source>In International Conference on Big Data Analytics</source>
          , pp.
          <fpage>250</fpage>
          -
          <lpage>265</lpage>
          . Springer, Cham,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>