Tag: Android

ArcGIS for Android v1.0 Released!

The Mobile Team is proud to announce the initial release of ArcGIS on the Android platform!! You can download it from the Android Market now!

Use the ArcGIS application to connect to ArcGIS Online or your on-premise ArcGIS Server and extend the reach of GIS to Android devices within your organization.

Using the application you can:

  • Browse ArcGIS Online or your on-premise ArcGIS Server to find maps
  • Display and navigate map content
  • Collect GIS data using the map or using GPS
  • Tap on the map and discover rich GIS content using popups
  • Find addresses and places
  • Identify your location on the map or tap on the map to get location details
  • Measure lines and areas
  • Share maps with others

For more details please visit the ArcGIS for Android Resource Center.

Mobile Team 

IMPORTANT NOTICE: Version 1.0 of the ArcGIS for Android application has been designed specifically for Android Phones equipped with ARMv7 or higher processors running OS version 2.2 or higher. If you cannot find the ArcGIS application when searching the Marketplace then it is more than likely your device does not meet the minimum specifications of ARMv7 processor and/or Android OS version 2.2 or higher.

The following is a list of devices that are running ARMv7 (note this list may be incomplete and Esri has not yet tested with all of these devices):

  • Acer
    Iconia Tab A500
  • Acer
    Liquid, Liquid A1
  • Advent
    Vega (P10AN01)
  • Archos
    101 Internet Tablet
  • Barnes&Noble
    Nook Color (root required)
  • Dell
    Streak, Streak 7
  • HTC
    Desire
  • HTC
    Desire S
  • HTC
    Desire HD (AT&T Inspire 4G)
  • HTC
    Droid Incredible/HTC Droid Incredible 2
  • HTC
    EVO 4G, EVO Shift 4G
  • HTC
    Flyer
  • HTC
    Glacier (T-Mobile myTouch 4G)
  • HTC
    Incredible S
  • HTC
    Inspire 4G
  • HTC
    Nexus One
  • HTC
    Sensation
  • HTC
    Thunderbolt 4G
  • Huawei
    Ideos S7
  • LG
    Optimus 2X
  • LG
    Optimus Black (P970)
  • LG
    Optimus Z
  • Motorola
    Atrix 4G
  • Motorola
    Bravo
  • Motorola
    Cliq 2
  • Motorola
    Defy
  • Motorola
    Droid 2, Droid 2 Global
  • Motorola
    Droid Pro (Motorola PRO)
  • Motorola
    Droid X
  • Motorola
    Xoom
  • POV
    Mobii Tegra Tablet
  • Samsung
    Continuum (i400)
  • Samsung
    Droid Charge
  • Samsung
    Galaxy S (i9000, Captivate, Fascinate, Vibrant, Epic 4G)
  • Samsung
    Galaxy S 4G
  • Samsung
    Galaxy S II
  • Samsung
    Galaxy Tab, Galaxy Tab 10.1
  • Samsung
    Infuse 4G
  • Samsung
    Nexus S
  • Samsung
    T-Mobile Sidekick 4G
  • Samsung
    4G LTE SCH-i520/Inspiration/Droid Charge/Stealth V
  • Sharp
    Galapagos 003SH, 005SH
  • Sony
    Ericsson Xperia Arc
  • Sony
    Ericsson Xperia Play
  • Viewsonic
    gTablet

If your device is not on the above list, we recommend that you research the device itself for details on the processor. The following is a list of devices known to be running ARMv6 and as such are not compatible with the ArcGIS application:

  • Asus
    Garmin nuvifone A50 (T-Mobile Garminfone)
  • Augen
    GENTouch 78 Tablet
  • Coby
    Kyros Internet Tablet (MID7015)
  • Geeksphone
    One, Geeksphone Zero
  • HTC
    Aria
  • HTC
    ChaCha
  • HTC
    Dream (T-Mobile G1, Android Dev Phone 1)
  • HTC
    Droid Eris
  • HTC
    Espresso (T-Mobile myTouch 3G Slide)
  • HTC
    Hero (T-Mobile G2 Touch)
  • HTC
    Legend
  • HTC
    Magic (T-Mobile myTouch 3G, T-Mobile G1 Touch)
  • HTC
    Salsa
  • HTC
    Tattoo
  • HTC
    Wildfire
  • Huawei
    Ascend
  • Huawei
    Ideos U8150-B (T-Mobile Comet)
  • Huawei
    U8110 (T-Mobile Pulse Mini)
  • Huawei
    U8230
  • LG
    Ally (Apex) (LG VS740)
  • LG
    GW620 (Eve, InTouch Max, LinkMe)
  • LG
    Optimus, Optimus M, Optimus T, Optimus S, Optimus V
  • LG
    Vortex
  • MAG
    iMiTO iM7
  • MAG
    iMiTO iM7S
  • Motorola
    Backflip
  • Motorola
    Citrus
  • Motorola
    Cliq (MB200)
  • Motorola
    Dext
  • Motorola
    Devour
  • Motorola
    i1
  • Motorola
    Spice XT300
  • Motorola
    Quench XT5 XT502
  • Pandigital
    Novel
  • Samsung
    Behold, Behold 2
  • Samsung
    GT-S5570 Galaxy Mini
  • Samsung
    i5500 Galaxy 5 (Corby)
  • Samsung
    i5700 Galaxy Portal (Spica)
  • Samsung
    i5800 Galaxy 3
  • Samsung
    i7500 Galaxy
  • Samsung
    Intercept
  • Samsung
    M900 Moment
  • Samsung
    S5830 Galaxy Ace
  • Samsung
    Transform
  • Sanyo
    ZIO M6000
  • Sony
    Ericsson Xperia X8
  • Sony
    Ericsson Xperia X10 Mini
  • Sony
    Ericsson Xperia X10 Mini Pro
  • Superpad
    10.2″ Tablet PC
  • Viewsonic
    ViewPad 7 Tablet
  • Velocity
    Micro T103 Cruz tablet
  • Vodafone
    845
  • ZTE
    Blade / San Francisco
  • ZTE
    Light / V9

We are investigating the possibility of supporting devices running ARMv6 processors but have not yet determined if this is feasible.

Posted in Mobile | Tagged , , , | Leave a comment

Today and Tomorrow: A State of the Union Address to the Esri Java Community

Here we are already. It is already the middle of June, 2011. Another Esri User Conference is shimmering on the horizon again. ArcGIS 10 is making history and making a significant impact in and around the world, and yet at the same time, the buzz can already be heard surrounding prospects of a major, revolutionary release of the next ArcGIS System not so far down the road. Exciting times indeed!

So it seems as though it’s about time to pause now and take a realistic overview of where Esri’s Java Platform strategy is today and where it is trending. The intention of this post is to update you all, certainly. I would add, too, that an equally important goal of this post is to give confidence to you that Esri is committed to supporting your business needs with respect to the entire Java platform, from mobile to desktops to enterprise.

It’s been a while since we’ve collectively reviewed this Java state of the Union, so to speak. Let me clarify what I mean by “we”; I mean “you”, the Java users and developers as well as those of us at Esri that work to serve “you”. Together, I mean “us”. A community. I know, it sounds a bit “touchy-feely”, as Americans would say. I do mean that with all sincerity, but I’ll move on to the matter at hand.

Java continues to be an important platform for Esri’s GIS solutions and offerings going forward through versions 10.x and beyond.

Java also continues to be the world’s most widely used platform for building real, robust and secure enterprise systems. Industries such as finance, insurance, health care, government, national defense, all rely on the Java platform because of its proven reliability and versatility on many runtime platforms over the years. Esri recognizes the pervasiveness of Java throughout these industries where GIS is also critical.

Let’s take a closer look at how Esri is supporting the Java developer and user community today as well as what Esri’s plans are for the foreseeable future.

ArcGIS for Server

Typically, one thinks of Server as mapping to Java Enterprise Edition (Java EE); Web Services, Web Applications, and the various Java technologies surrounding these platforms. Historically, the showcase product here from Esri has been the Java Web ADF. This is a true JSF/MVC implementation for rapidly building GIS Web applications that consume services from ArcGIS Server and OGC standard servers.

With the WebADF, developers find a clearly defined Model/View/Controller (MVC) implementation, and the framework adheres to tried and true Java EE standards, i.e JSF, AJAX, SOAP/XML, and more. It is a beautiful stack, actually. The Java enterprise architect gets it. However, the pure GIS professional developer who is not familiar with these Java EE standards struggles with it. Is it finished and perfect? No. Is it successful, yes it is, or was, in many areas. In other spheres, though, it was quite complex. Users and developers found it difficult to scale and maintain, in the end.

At version 10.0 of ArcGIS, the Java Web ADF has been deprecated; the 10.1 version of ArcGIS will be the last release of the Web ADFs, both Java and .NET.  Folks that are planning new projects having to do with ArcGIS Server are highly advised to eliminate the Web ADF from consideration.

With respect to the “View” section of the MVC model, Esri has been heavily investing in the promotion of the RESTful ArcGIS Web APIs. Javascript (dojo/AJAX), Flex, Silverlight are all very productive platforms, and we have seen a great deal of uptake and success in the past 2 years within GIS developer communities. These are simple APIs and easy to develop with, which has translated to quicker-time-to-market for a lot of Esri customers and business partners.

Of course, the foundation for these APIs is REST. The ArcGIS REST API handlers define the basis of the “Controller” tier, if you will. The Model is core ArcGIS Server. This is key to Esri’s strong Services platform for Enterprise GIS. The ArcGIS REST API is a public specification, and is published as the open Geoservices API.

While the ADF has been deprecated, as previously mentioned, the ArcGIS Java Web Services API (AgsJWS), the underpinning API for the WebADF, has not.  This is an important point to make. SOAP/XML is till the Web Services standard for SOA integration. Esri does not plan to deprecate this Web Services solution for ArcGIS Server. The AgsJWS is a pure Java Web Services API, based on JAXB, and is an excellent solution for building , connecting and integrating great geospatial analysis and visualization in your Java EE based solutions. Esri continues to cultivate and support its community today and into the future.

For the back-end Server, building Server Object Extensions (SOEs) with the ArcObjects SDK for Java has been and continues to be the leading solution for creating custom ArcGIS Server Web Services. There have been compelling success stories from users who to extend the Server with Java APIs, using the powerful Eclipse tooling to build and deploy them. A good example of a success story is ArcGIS for INSPIRE, a product that heavily relies on Java-based SOEs. SOEs can be exposed instantly as REST and SOAP, so if you develop with any of the RESTful Web APIs a front end to your system, your custom Java implementation and capabilities in the Server can immediately be realized in the View tier of MVC.

ArcGIS for the Desktop

ArcGIS Desktop is extensible using Java. Java developers can use the ArcObjects Java SDK Eclipse plug-ins to write, debug and extend ArcObjects and the Geoprocessing framework, and deploy their add-ins and extensions as jar files. ArcGIS Desktop is Java-enabled! ArcGIS Desktop ships with its own Java runtime. 5 or 6 years ago, could anyone have imagined that this would become possible? This came about in response to a lot of Java developers wanting to customize ArcGIS Desktop, ArcMap and ArcCatalog, using their chosen skill and expertise, and Esri listened and responded. The ArcObjects SDK for the Java platform continues to be the go-to developer kit for building custom, feature-rich desktop applications that leverage the powerful ArcGIS Engine runtime.

ArcGIS for Lightweight and Mobile Devices

At version 10.1 of ArcGIS, Esri will introduce a new suite of products under the platform strategy called “Lightweight GIS”. GIS is accessible and usable via mobile devices such as laptops, tablets and phones in connected, disconnected, and “sometimes”-connected environments. This lightweight GIS platform provides new developer APIs for Java desktop, mobile, and embedded device developers. There are two key products based on this platform that Java developers can take advantage of: The ArcGIS Runtime SDK for Java SE based GIS applications, and the ArcGIS for Android SDK for Android phones and tablets. These SDKs are founded upon the Web API and Smartphone API object models. They are pure Java APIs and both have strong Eclipse IDE
integration support, making development easy, quick and extremely intuitive.

Version Support

ArcGIS versions 10 and 10.1 both support Java SE 6 and Java EE 5. Esri continues to monitor the progress of the Java EE 6 and Java SE 7 specifications to see if the features they offer will make sense for the ArcGIS product line.

Summary

To summarize, Esri’s ArcGIS and Java strategy is pervasive, in and through all of the key computing environments that Java is found in, from Mobility to the desktop and to the Enterprise. This makes Esri’s GIS and Java a perfect match for any Java-based implementation that requires the delivery of geospatial or location services and capabilities.

So until next time, please let us know your thoughts and feedback by sharing comments questions. This will help us in serving you better, the Java developer and user community. We hope to meet with you at the ESRI International User Conference in July!

Posted in Developer | Tagged , , , , , , , , , , | 2 Comments

Data Collection Playground and ArcGIS on Smartphones

Your iPhone, Windows Phone, iPad or iPod Touch can become a powerful tool for field data collection. Using the ArcGIS application that is available from Apples’ App Store and the Windows Phone Marketplace, you can collect GIS features using the GPS receiver in your device or by sketching on the map, fill out intelligent attribute forms  and attach photos/videos to them. All edits are instantly synchronized with your enterprise geodatabase.

Getting started is as simple as using your smartphone. The Mobile team has hosted a number of data collection maps in a group called “Collection Samples” that is accessible directly on your phone and can be found inside of the Gallery. Here is how you can access the collection maps using your iPhone…

After tapping on one of the maps in the Collection Samples group (Infrastructure for example), you will find that the map itself contains additional functionality within the Map Tools called Collect. Tap on Collect to choose a Feature Type or Template from the editable map layers and then follow the additional steps to collect a new GIS feature.

These maps are available using ArcGIS Online and are publicly shared in a group called Esri Data Collection Playground for you to get started with. Feature layers provide templates for data collection inside of the ArcGIS application. Each of the collection sample maps available within the smartphone app have an associated Map Package that you can download to your server as well. To find the map package, look at the details of the map inside of ArcGIS Online. Looking at the details of the Infrastructure Map you will find a link to the Infrastructure Map Package. Opening the map package you can then host your own Feature Service and then either use ArcGIS Online or your own on-premise server to host maps for use on your smartphone device.

We would like to see you start leveraging smartphones for data collection today. Please try the Collection Sample maps and let us know what you think. Send your feedback to arcgis4iphone@esri.com.

NOTE: The features you add to the maps hosted inside of the Esri Data Collection Playground are archived and then scrubbed nightly. Please do not expect features to be maintained. This is a playground and we are here to pick up after your edits…

Also, ArcGIS will be coming to Android devices very soon and the capabilities listed above will be available to your favorite Droids in the near future…

Thank you!

Mobile Team

Posted in Mobile | Tagged , , , , , | 1 Comment

The ArcGIS API for Android Beta Program is now Open!

We are excited to announce that the ArcGIS API for Android is in public beta and available for download…. more details.

Posted in Mobile | Tagged , | Leave a comment

The ArcGIS API for Android Beta Program is now open

 

We are excited to announce that the ArcGIS API for Android is in public beta and available for download from our beta community site! Use it to build Android mapping applications that:

 

·       Access dynamic, tiled, and feature map services

·       Overlay graphics

·       Search and identify

·       Perform advanced analysis

·       Collect and edit data from your android phone and tablet devices

 

Access the Online documentation and Get started today!

 

The Android Team

 

Posted in Developer | Tagged , | Leave a comment

Twitter Poll for ArcGIS Mobile

The ArcGIS Mobile Team is looking for your feedback!

Please cast your vote on the following Polls:

Hardware Devices & Platforms: http://twtpoll.com/zjlqb3

Feature Enhancements: http://twtpoll.com/fs6jn8

 

Follow us on Twitter: @mgcopping, @jeffshaner and @ffaubry

Posted in Mobile | Tagged , , , , , , | Leave a comment

The Mobile Web

A lot of people have asked us when we will add support for the iPhone, Blackberry and what about Android? Imagine the reaction we receive when we the answer is – we already do! Well, sort of. To explain, lets first discuss the target user of ArcGIS Mobile and then discuss how the Mobile Web fits into the picture…

Enterprise Field Worker

ArcGIS Mobile is designed and engineered to fit the needs and workflows of the enterprise field worker. Viewing and navigating to locations, collecting new spatial and tabular data, and locating/updating existing assets in the field are all common tasks for the enterprise field worker. They demand highly focused, workflow driven applications that are fully functional whether you are connected in the field or not. Where do you find the enterprise field worker? He/she inspects their city infrastructure, performs state or county surveys, responds to incidents when something bad happens, and much more. They leverage the corporate investment in GIS to manage their infrastructure in the field.

The Mobile Consumer

Those local and state agencies that are moving to ArcGIS Server and deploying mobile GIS to their field operations using ArcGIS Mobile are not the only field workforce that consumes corporate spatial data – citizens within a local government, tax payers within a county are as well. The mobile consumer wants to discover corporate information that is managed by their state or local government. For example, why can’t I see all of the recycling centers in my city using my iPhone or Blackberry? How about public transportation routes and schedules?

So how can a local government support so many different devices…

ArcGIS Server and Mobile Web Browsers

Mobile browsers come in a variety of flavors. They range from browsers that support basic or partial HTML rendering to those which support full HTML, JavaScript & CSS. Leading the pack right now is the iPhone Safari with support for all the above plus SVG graphics with JavaScript binding and an on device database. Several other mobile device manufacturers also integrate full fledged browsers, including Opera Mobile/Mini, Mobile Explorer, Blackberry Browser, etc. (A comprehensive list can be found at http://en.wikipedia.org/wiki/Microbrowser). 

At the 9.3 release, ArcGIS Server includes REST access to mapping and other geospatial services. These services can be easily accessed through simple HTTP calls, which can be made through any server side scripting language such as Php, Perl, Ruby, Python, etc or languages such as Java & C# or within client applications through JavaScript or FLEX/ActionScript.

Simple Web Mapping

With the rest of this blog posting, we will explain how you can use the new ArcGIS Server REST API to add a map into an HTML page and allow basic map navigation using links on the page and serve your consumers with your corporate data. We will use one of the ArcGIS Online map services as the map to display.The following is the PHP code for building this simple mobile web mapping application.

  • Determine the size of the map image to be requested, based on the browser’s USER-AGENT.

$userAgent = $_SERVER["HTTP_USER_AGENT"];if (strstr($userAgent, “iPhone”)) {
  …
}else if (…) {
  …
}

else {
  echo $userAgent;
}

  • Determine whether there is an extent already passed to it in the url query or initialize the map to a pre-defined extent.

$bbox = $ _ GET["bbox"];

if ($bbox == “”) {
  $bbox = “…”;
}

$bbox = explode(“,”, $bbox);
$left = (double) $bbox[0];

  • Create image request to ArcGIS Server REST,  passing size, format and extent information in the image url

 “<img src=”http://server.arcgisonline.com/…/export?f=image&format=jpg&bbox=” . $left . “,” . $bottom . “,” . $right . “,” . $top . “&” . $size . “” width=”" . $imgWidth . “” height=”" . $imgHeight . “” />”;

  • Calculate extents and create links based on navigation operations; zoom in/out and pan north/east/south/west. These links call the page itself and pass the calculated extent.

“<a href=”" . $base . “?” . “bbox=” . expand($left, $bottom, $right, $top, $width, $height, 0.5) . “”>+</a> | “;
“<a …>-</a> || “;

“<a href=”" . $base . “?” . “bbox=” . offset($left, $bottom, $right, $top, $width, $height, 0, $panFactor) . “”>N</a> | “;
“<a …>E</a> | “;
“<a …>S</a> | “;
“<a …>W</a> | “;

The following are screenshots of this simple mapping application running on different device emulators:

iPhone 2.1

Blackberry Curve (8320)

 

Android (v1)

This blog post is the first in a series of blog entries that will be published on how you can leverage the Mobile Web. Thanks go to Jayant Sai (lead developer of the Javascript API) for contributing this article.

Mobile Team

Posted in Mobile | Tagged , , , , , | Leave a comment