How To Build Online Base Map

GIS basemaps provide a visualization framework for all ArcGIS Server applications. In most cases, you will use a basemap, on top of which you can add your operational GIS layers. Operational layers refer to the map layers that your end users will work with such as layers that you edit or make notes on, layers that represent observations and sensor readings, layers that result from analytic models, and results from map queries.

Basemap alternatives

You have a number of alternatives when you create basemaps for use in your GIS map applications:

• Create a GIS map application that contains a number of independent map layers.
• Use an ArcGIS Server basemap published by another organization such as the ESRI-hosted ArcGIS Online services.
• Build and serve your own GIS basemaps.
• Leverage an existing Web map from Google Maps or Microsoft Bing Maps, onto which you add your operational GIS layers.
• Leverage the Google Earth 3D world map.

This section describes each of these alternatives and the implications of using each.

Creating a GIS map application that contains a number of independent map layers

In many traditional GIS applications, online maps are implemented as a series of independent map layers, where each map layer references a data source and can be toggled on and off in the map display. For example, the map below could be composed of a series of independent map overlays.

When using independent map layers in a Web map, each map layer is typically accessed as a separate map service. This flexibility enables you to combine layers from multiple servers. This can improve the flexibility of your Web map application. However, it can impact performance and simplicity. Not all map layers are designed to work together. In addition, performance can be slower.

This approach is considered to be flexible because each map layer service could potentially be used for a number of purposes.

This is how many ArcIMS map applications are implemented. You have some flexibility because you treat each map layer independently, and you can combine any series of layers in an ad hoc manner.

Performance can decrease if you try to incorporate many independent map services as individual map layers. The user experience for your audience is not as focused and can be perceived as being more complex. They need to know which layers to turn on and off and which to focus on in their work. Applications with many layers tend to lack focus in terms of mission-critical tasks and end-user workflows.

Using an ArcGIS Server basemap published by another organization

Many GIS organizations publish basemap services for use in other organizations. For example, a number of national mapping agencies and state and local government GIS organizations build, manage, and publish fundamental basemap datasets such as multiscale national maps (topographic maps), transportation maps, census maps, parcel maps, hydrology maps, and so on.

These maps are often intended to provide authoritative, accurate, and up-to-date basemap experience for your applications. They provide a very important enabling GIS map service that many other organizations can exploit to great benefit.

We expect an increasing number of users to begin publishing basemap services for use across the GIS community.

Adding your content to ArcGIS Online basemaps

ArcGIS Online basemaps are designed for users to extend by adding their own rich content, especially at larger, more zoomed-in map scales. This enables GIS organizations to leverage their primary content and create map services that take over where ArcGIS Online general maps leave off.

Building and serving your own GIS basemaps

In many cases, you will need to build and serve your own basemaps for use in your applications. This is often the case when your organization is the GIS provider for a particular area of interest and in which your applications and frameworks require specific information themes (for example, parcels, engineering, facilities management, hydrology, utilities, geology, population and demographics, planning, and many other applications).

In these cases, you are typically already compiling fundamental, authoritative base information for one or more applications. This approach leverages content that your organization builds and maintains. In addition, this focuses support on your users by providing a framework or basemap that is fundamental to their daily operations.

Leveraging an existing Web map from Google Maps or Bing Maps onto which you add your operational GIS layers

Using a basemap from a widely used mapping Web service, such as Google Maps or Bing Maps, is very useful in many situations. Most end users will know about and have experience using one of these existing Web mapping applications. They are familiar and comfortable with the end-user experience.

Some GIS organizations serve content to citizens and other casual users in this framework but apply richer, more sophisticated map applications for their operational work.

It is important to note that these consumer basemaps will not support all use cases. Many applications require a more focused information background to provide context. For example, cadastral applications require a parcel framework. Many population mapping applications require administrative or political boundary maps, hydrology requires strong hydrological representations, and so on.

You'll need to weigh the ease of use of applying these consumer basemaps against the requirement that many users face to work with authoritative, up-to-date, locally compiled, and often sensitive content to address their workflows and missions.

In situations where you use Google Maps or Bing Maps, it's important to note that you may be restricted in your use of this information within your organization. You will need to have an appropriate map use license.

Leveraging Google Earth as the basemap onto which you layer your operational information

Many of the same issues discussed above for Google Maps and Bing Maps apply for using Google Earth.

Even so, many GIS practitioners would like to mash up their GIS content for their end users using Google Earth, and this is readily done using ArcGIS support for KML. By default, each map service that you publish using ArcGIS Server will be available as a map service and as a KML network link.

A design checklist for map publishing with ArcGIS Server

Following is a useful checklist that can guide you in designing and creating basemaps for use in ArcGIS Server applications.

• Design for the target GIS map application. The choice of map symbols and display properties will be quite different for a map that is intended for display on a computer screen and one that is intended for printing on paper. And, there are almost as many differences between some of the applications that you will provide to your end users.
  It's important to design your Web maps for the set of targeted Web applications. For example, some basemaps are designed to work on mobile devices with quite small screen displays and resolutions. Mobile maps need to work in the natural light conditions found in the field. Other Web maps are traditional 2D maps intended for use in a Web browser, while others are intended to work in a 3D explorer application.
• Your basemap should be designed for adding and working with operational map layers. Effective maps require some graphical structuring. The GIS basemap you are creating provides a background on which operational information and results will be displayed, visualized, and used.
  Unlike printed basemaps, your online basemap requires map symbols and information presented using more subtle colors, fewer text labels, and less bold symbols. You will reserve the use of these cartographic elements for your operational layers that you layer on top of your basemap. In most cases, you will want to think of your basemap as more of a background display. For example, imagery is often used as a basemap framework onto which operational information is displayed. Consider the graphical hierarchy and organization of your basemap when it is combined with operational information. Scale back its bold display so that your operational layers become the primary focus. Ensure that your basemap provides a strong geographic context and framework in which your operational information is to be visualized and used.
• Designing multiresolution basemaps. A common goal for online basemaps is to create a basemap that can be displayed at multiple map scales. This requires a map design that considers how the map is to be portrayed at each map scale.
  ArcMap can use scale-dependent drawing to accomplish this. However, how you organize the scale dependencies in your ArcMap document is counterintuitive to what you might expect. GIS users typically organize their maps as an ordered list of theme-based map layers. For example, a set of map layers are created, one for each theme such as is shown below.
  Contrast this with the pattern used to build a multiscale basemap. In this case, you will design and create one group layer for each map scale that is to be included in your basemap. Each of these group layers contains all the thematic map layers (along with their drawing, symbol, and label properties) for displaying the map at that map scale. Here is an example table of contents in ArcMap for a multiscale map design:
  Here's a simple way to think about and define your multiscale map design. Suppose that you want to generate a multiscale map that displays at four map scales:

  Maps scale used for design and map creation	Visible scale range settings in ArcMap
  1:100,000	1:75,000 to 1:250,000
  1:50,000	1:40,000 to 1:75,000
  1:25,000	1:15,000 to 1:40,000
  1:12,000	1:5,000 to 1:15,000

  Layer organization in ArcMap group layers for multiscale map documents
  First, you would create a map for each of these map scales. Then, you organize the collection of map layers for each map scale into a group layer for that map scale. In the example above, you see 12 map scales for a national hydrological map. In many states and cities, the map scales you'll need to generate will be more like 4 to 6 map scales.
• Incorporate overview maps for display at the smallest map scales (the most zoomed-out scales) in your basemap. In many cases, you will require an overview map of your entire area of interest that is drawn at a smaller map scale than the map scales at which your users will perform the majority of their work tasks. For example, you will probably want an overview map for your entire study area, or you may need a statewide overview map for your work. In both cases, most of the work is performed within more tightly focused geographic areas (for example, zoomed into a county and closer map scales).
  In these cases, you can leverage an existing Web basemap for your study area-wide views (like those from ArcGIS Online). You can extend such basemaps with a simple display. For example, put your study area polygon on top with a few points of interest and map labels. Alternatively, you can create your own simple overview maps for these small scale displays. The main point is to keep your overview map scales simple and focus your energy and creativity on the more detailed map scales of your multiresolution basemap.
• Plan for a critical set of map overlays in your basemap. However, you will want to limit the number of layers that can be toggled on and off in your basemap. You can enable map layers to be turned on and off in your basemap, but you'll want to keep this list small. Essentially, these become map layers that are independent of your other group layers in your basemap. Examples of common map layers that are often toggled on and off in the end-user application include the following:
  • Place-names
  • Transportation (for example, these overlays are often displayed over image basemaps)
  • Boundaries and place-names, which are also often displayed over image basemaps
  • Shaded relief
  You'll want to limit the number of these because of the following:
  • Your application needs to be easy to use for your end users. Ensure that there are not too many map layers to toggle on and off.
  • Performance can degrade because you have to make too many map requests from additional map services.
  • Maintaining the number of map services and keeping them up-to-date can be more work. Consider what you would do if services go down or are removed, and so on.
  • Your server applications may not scale as well to support a large number of users.
  Use cached map services in place of dynamic map services. One of the key tenets for improving performance in any Web application is to precompute elements in your Server applications. ArcGIS Server can precompute your basemaps as cached map services, which are stored as a series of map image tiles on disk for a range of map scales and levels of detail. Here is a schematic of how a map cache is structured for two levels of detail.
  When users access a map cache using ArcGIS Server, the tiles are returned for the appropriate level of detail instead of the server computing the map view each time. This significantly increases performance and scalability. Caching is the primary mechanism used by Google Earth, Google Maps, and Bing Maps to achieve high performance. You can get a similar effect using cached map services in ArcGIS Server. For information and guidance on building map caches

Production Mapping

What is Production Mapping? (Production Mapping)

Esri Production Mapping streamlines your GIS data and map production by providing tools that facilitate data creation, maintenance, and validation, as well as tools for producing high-quality cartographic products.

Production Mapping provides tools for managing your production from beginning to end. Each organization has workflows that are unique to the type of data being collected and the type of product being delivered. These workflows can be generalized into a basic production workflow that consists of steps to create your geodatabase and capture or load an initial set of data, perform edits to the data, ensure the data is valid and accurate, and produce digital or hard-copy output. Production Mapping is designed to streamline each of these steps while remaining flexible to adapt to your business rules and workflows.

The Esri Mapping and Charting solutions include industry-specific, standards-based templates, rules, and tools. Through configuration, the tools and processes can be adapted to meet maturing business needs, and therefore an API is not included for customization.

The geodatabase

Central to any production workflow is the geodatabase. How you choose to design your geodatabase determines what data needs to be captured and edited, what logical rules exist for validating the data, and the types of output that can be created.

When designing a geodatabase, certain types of validation are built in such as the ability to limit the valid attribute values for a field by using a domain. You can also model the geometric relationships of features through topologies or networks. Production Mapping supports these forms of validation and allows you to define additional business rules using ArcGIS Data Reviewer for Desktop checks stored in a batch job. The batch jobs can be run when you update the attributes of a feature or template, like domains, or as a postprocess like validating the topology.

The product library in Production Mapping provides a framework for managing business rules, data, and map documents in a secure, centralized location. By leveraging the rules stored in the product library, data editing tools are tailored to ensure that features conform to your data collection standards. During cartographic production, the product library can act as a document management system for your map documents and data, allowing you to check files in and out and restore historical versions. The cartographic tools in Production Mapping can also be used to ensure consistent and repeatable symbology as well as provide a number of dynamic surround elements.

Learn more about the product library

Capture

The purpose of data capture is to consume existing data or create new data in your geodatabase. Data can be captured many different ways such as extracting new data from imagery, gathering information in the field with a mobile device, or converting existing data into the geodatabase.

Feature Manager allows you to quickly and easily create new features by using feature templates and construction tools within a centralized editing environment that leverages your enhanced validation rules and provides a new type of feature template called the composite template. Production Mapping also provides the data load automation tools, which allow you to define the mapping between source data, such as shapefiles or coverages, and your geodatabase ahead of time to ensure consistency when converting large amounts of data.

Learn more about the Feature Manager

Edit

The editing stage of the production workflow involves adjusting existing features and adding new features to ensure that your data is up-to-date and accurate. This can involve updating data to match a new source or modifying attributes of data that was collected for a different purpose.

When editing data within Production Mapping, feature attribution is managed through the Feature Manager, which allows you to update fields while ensuring the attributes are valid according to your validation rules as well as batch update attributes and create new features. Production Mapping also provides a number of editing tools for batch geometry updates as well as tools for specific types of data or industries including tools for linear referencing, utilities, contour lines, and z-enabled data.

Learn more about editing in Production Mapping

Review

Data review is important to ensure that the data being created is accurate and fit for its intended purpose before the data is delivered or used for making a map product. The data review or quality control stage of the production workflow often involves three phases: finding issues with the data, whether through manual or automated methods; fixing issues or marking them as exceptions; and verifying that the issue is resolved.

The Data Reviewer component of Production Mapping provides the ability to track records of all issues you find in the Reviewer table, which maintains the status of the record as well as a link between the record and the feature with the issue. Data Reviewer offers the ability to automate data validation through configurable checks that can be run when you choose, scheduled through a Windows service to run at specified times, or run through Python scripts. Automated checks may not be able to find all problems with the data, such as missing features. Data Reviewer also has a number of tools to help with manual or visual quality control including tools to flag missing features and the ability to create a sample set of data for in-depth validation.

Note:

Data Reviewer is available with Production Mapping or as a stand-alone extension.

Learn more about Data Reviewer

Create output

Typically, the final stage of a production workflow is to create the output that will be delivered; however, the workflow may repeat if making a delivery contingent on approval or creating a product that requires regular updates. There are many types of output that may be produced: data exported to a certain format, hard-copy maps, or data that will be served over the Web.

When producing hard-copy products, there is wide range of types of maps or charts that you may need to produce, from one-off maps to map books to highly detailed charts that require version tracking. Production Mapping provides support for hard-copy map production through the product library by providing check-in and checkout capabilities for map documents as well as the ability to track history and roll back to previous versions.

Data visualization and symbology is important when producing a hard-copy product or serving data over the Web. Production Mapping provides the views and visual specification tools for consistent, repeatable, rule-based symbology, where you define what symbol or representation should be applied to features based on their attribute combination. Production Mapping also provides a number of custom surround elements, such as the graphic table element, that allow you to create a table or legend that automatically updates based on the data being displayed.

Learn more about mapping, charting, and visualization

Workflow management

When managing production, it is important to be able to allocate resources and track the status of the project. Being able to ensure that work is being done consistently and that steps are not being skipped is also essential. Production Mapping allows you to tie all the components of data capture, editing, validation, and cartography together in high-level workflows with ArcGIS Workflow Manager for Desktop and in detailed workflows with Task Assistant Manager.

Note:

Workflow Manager is available in the Production Mapping media kit and as its own stand-alone extension.

Workflow Manager allows you to create a job (unit of work), assign or reassign the job to a user, and track the overall status of the project. Each job includes a predefined workflow that you build to represent your processes. When assigned a job, you execute the steps in the workflow to launch the appropriate tools, send e-mail notifications, or ask questions to determine the path the job should take.

Task Assistant Manager allows you to define workflows in ArcMap that guide your users through various tasks. Task assistant workflows can be used to provide step-by-step instructions for complex tasks, minimize confusion for new users, or simply be used as a reference. Clicking a task in a workflow can execute a tool in ArcMap or geoprocessing tools, set up your environment by setting layer or snapping properties, or provide a description of what needs to be done.

Production Mapping solutions

Esri provides three out-of-the-box solutions for the defense mapping, nautical, and aeronautical industries that are all built to utilize and expand on Production Mapping functionality. Production Mapping content is also available on the Esri Resource Centers for many of the user communities.

Production Mapping can be used to build your own solutions by creating a product library to meet the standards of an industry or business.

Pembagian dan Perhitungan Zona UTM TM3

Pembagian zone UTM :

Rumus yang akan diuraikan di tulisan ini tidak berlaku untuk zone utm nomer 31 s/d 33, 35 dan 37 yang terletak di 56 s/d 84 Lintang Utara. Seperti terlihat di gambar untuk daerah tersebut, lebar zone nya tidak sama dengan 6 derajat.

Contoh spreadsheet hitungan yang dipakai adalah :

rumus di F46=C46+(D46/60)+(E46/3600); F47=C47+(D47/60)+(E47/3600), sehingga Lintang dalam unit desimal degree ada di F46 dan untuk Bujur ada di F47.
Cell H46, isikan “S” jika daerah yang akan dicari zonenya ada di Lintang Selatan dan isikan “N” jika ada di lintang utara. Huruf ‘S’ dan ‘N’ harus ditulis dalam huruf BESAR.
Cell H47, isikan “E” jika terletak di Bujur Timur dan “W” jika ada di bujur barat. ‘E’ atau ‘W” harus ditulis dalam huruf BESAR.



A. Hitungan untuk Zone UTM

Dari gambar di atas, untuk perhitungan zone UTM di daerah Bujur Timur dapat ditentukan dengan rumus
ZoneUTM= INT(Bujur/6)+31, sedangkan untuk Bujur Barat, ZoneUTM= 30-INT(Bujur/6)
Apabila rumus untuk bujur barat dan bujur timur digabung, maka rumus ZoneUTM di excel adalah
I47=IF(F47=0,0,IF(H47=”E”,INT(F47/6)+31,30-INT(F47/6)))
Keterangan:
IF(F47=0,0 —> jika F47 atau kolom bujur sama dengan nol, maka zone=0
IF(H47=”E”,INT(F47/6)+31 —> rumus untuk Bujur Timur
30-INT(F47/6) —> rumus untuk Bujur Barat

B. Hitungan untuk Zone TM3
Zone TM3 didapat dengan menambahkan nilai 0.1 atau 0.2 ke Zone UTM. Untuk lokasi yang terletak di sebelah kiri Bujur Tengah TM3 ditambah 0.1, sedangkan untuk yang kanan ditambah dengan 0.2.
Bujur Tengah TM3 (BT_TM3) untuk lokasi di Bujur Timur didapat dengan rumus BT_TM3=(I47-31)*6+3, sedangkan untuk Bujur Barat BT_TM3=(30-I47)*6+3.

Rumus dalam contoh spreadsheet untuk perhitungan  Zone TM3:
J47=I47+IF(H47=”E”,IF(F47<(I47-31)*6+3,0.1,0.2),IF(I47<(30-I47)*6+3,0.1,0.2))
Keterangan:
I47 —> Zone UTM
F47 —> Bujur
(I47-31)*6+3 —> Bujur Tengah untuk lokasi Bujur Timur
+IF(H47=”E”,IF(F47<(I47-31)*6+3,0.1,0.2) —> Jika Terletak di Bujur Timur, dan Bujur<Bujur Tengah, maka ZoneTM3=ZoneUTM+0.1, jika Bujur>Bujur Tengah, maka  Zone TM3=ZoneUTM+0.2
IF(I47<(30-I47)*6+3,0.1,0.2)) —> Jika Terletak di Bujur Barat
Jika ingin diringkas lagi, rumur Zone TM3 dapat ditulis
J47=I47+IF((H47=”E”)*(F47<(I47-31)*6+3),0.1,IF(I47<(30-I47)*6+3,0.1,0.2))