|
Written by Eric Pimpler
|
|
Friday, 21 August 2009 20:54 |
|
This article is the final part of a five part series covering the ArcGIS JavaScript API and the ArcGIS JavaScript Extension for the Google Maps API. It was previously published at GeoChalkboard in the form of a six-part article, and has been reproduced here with permission.
The previous part part, Integrating the Google Maps API Geocoder, was published yesterday.
Graphics in the ArcGIS Server JavaScript API are points, lines, polygons, or text that are drawn on top of your map in a layer that is independent of any other data layers associated with a map service. Most people associate a graphic object with the symbol that is displayed on a map to represent the graphic. However, each graphic in an ArcGIS Server JavaScript application can be composed of up to four objects including:
- Geometry of the graphic
- Symbology associated with the graphic
- Attributes that describe the graphic
- Info template that defines the format of the InfoWindow that appears when a graphic is clicked.
|
|
Read more...
|
|
Written by Eric Pimpler
|
|
Wednesday, 19 August 2009 13:33 |
|
This article is the third in a five part series covering the ArcGIS JavaScript API and the ArcGIS JavaScript Extension for the Google Maps API. It was previously published at GeoChalkboard in the form of a six-part article, and has been reproduced here with permission.
The second part, Working with the Map Extent was published yesterday. The remaining articles in this series will be published this week.
The previous article briefly introduced the concept of events and pointed you to an example that showed you how to get the current extent through the use of Map events, and specifically the “onExtentChange” Map event. Today I would like to expand on the concept of events and how they are implemented within the ArcGIS Server JavaScript API. Events are actions that are typically triggered by end users. This can include actions such as the click of a mouse, dragging the map in a pan operation, loading a page, executing a task, clicking a button, and many other actions.
|
|
Read more...
|
|
Written by Eric Pimpler
|
|
Monday, 17 August 2009 09:26 |
|
This article is the first in a five part series covering the ArcGIS JavaScript API and the ArcGIS JavaScript Extension for the Google Maps API. It was previously published at GeoChalkboard in the form of a six-part article, and has been reproduced here with permission. The remaining articles in this series will be published this week.
This article is the first in a new series covering the new ArcGIS JavaScript API and the ArcGIS JavaScript Extension for the Google Maps API. I am particularly interested in the integration of ArcGIS Server with Google Maps and Google Mapplets so my focus will be oriented toward that particular subject. Today I will introduce the ArcGIS JavaScript API and show you how easy it is to create simple web mapping applications with this API. Future articles in this series will focus more on the integration of ArcGIS Server with Google Maps and Mapplets.
|
|
Last Updated on Monday, 17 August 2009 09:46 |
|
Read more...
|
|
|
Written by Eric Pimpler
|
|
Thursday, 20 August 2009 07:59 |
|
This article is the fourth in a five part series covering the ArcGIS JavaScript API and the ArcGIS JavaScript Extension for the Google Maps API. It was previously published at GeoChalkboard in the form of a six-part article, and has been reproduced here with permission.
The third part, Using Events, was published yesterday. The final article in this series will be published tomorrow.
Today I will continue my series of posts on the new ArcGIS Server JavaScript API with an article that describes how you can integrate the Google Maps API geocoder with ArcGIS Server. In this article I am going to use the Portland_ESRI_Landbase_AGO map service from ESRI’s Sample Server 1 ArcGIS Server instance as a base layer, and we’ll show how you can geocode an address using the Google Maps API. This address will then be represented as a point graphic created from the ArcGIS Server JavaScript API. You could certainly use an ESRI locator service to do the geocoding, but it’s a fun exercise and useful if you don’t have access to a geocoding service. This is a very simple example with a hard-coded address meant only to show the potential for integration.
|
|
Last Updated on Thursday, 20 August 2009 08:08 |
|
Read more...
|
|
Written by Eric Pimpler
|
|
Tuesday, 18 August 2009 07:44 |
|
This article is the second in a five part series covering the ArcGIS JavaScript API and the ArcGIS JavaScript Extension for the Google Maps API. It was previously published at GeoChalkboard in the form of a six-part article, and has been reproduced here with permission.
The first part, Getting Started was published yesterday. The remaining articles in this series will be published this week.
Continuing with our series on the ArcGIS Server JavaScript API, today we will cover various ways that you can work with the map extent. If you don’t include extent information when an instance of the map is created in your code, the default or initial extent will be the extent of the map as it was last saved in the map document (.mxd). For example, the code snippet below does not include any extent information in the constructor for the map. This would result in a default extent being applied which was the extent of the map when it was last saved in the map document.
|
|
Read more...
|
|
Written by Ines Lemke
|
|
Monday, 20 July 2009 10:33 |
|
Geotagging is becoming increasingly widespread. All kinds of internet content (pictures, videos, blogs, Wikipedia articles etc.) are not only being indexed, but they are also tagged with geographical metadata. The increasing use of this information is resulting in substantial changes in the field of internet search. Directories, travel sites and real estate portals are starting to present their points of interests (POIs) on maps. All of them have to face several challenges: constantly changing data, keeping high performance, and providing a user-friendly presentation. The display of geo-points on a map is not difficult due to the services of various map providers. But displaying more than 1,000 POIs can cause problems as website performance significantly declines and geo-points become indistinct clouds. |
|
Last Updated on Tuesday, 28 July 2009 05:53 |
|
Read more...
|
|