Posts Tagged ‘arcsde’

MAPublisher 8.2 Released with GeoPDF, KML + Spatial Database Support (Avenza)

Wednesday, November 25th, 2009


[Editor's note: Expression Builder gets a needed upgrade, too, and the web map authoring tool's new features deserve a second look. The ESRI GeoDB support (Windows only for now) comes with a $349 upgrade price tag for existing maintenance customers. I'd like to see scripting (recordable with Illustrator actions) in their next release, and a method to export cut map tiles for mashups.]

Republished from Avenza (1, 2, 3).

Avenza Systems Inc., producers of MAPublisher cartographic software for Adobe Illustrator and Geographic Imager spatial tools for Adobe Photoshop is pleased to announce the release of MAPublisher 8.2 for Adobe Illustrator. MAPublisher 8.2 is the latest version of this powerful mapmaking software used to produce high quality maps from GIS data for both print and electronic distribution and now offers support for both creating geospatial PDF files from within Adobe Creative Suite and importing GIS map data directly from ESRI geodatabases.

MAPublisher 8.2 for Adobe Illustrator is a full product upgrade that is free of charge to all current MAPublisher Maintenance Program subscribers and replaces the current shipping version of MAPublisher, version 8.1, for all new customers using Adobe Illustrator CS3 and/or CS4.

“MAPublisher 8.2 is another major advance for this powerful and widely used cartographic and map-design platform,” said Ted Florence, President of Avenza, “MAPublisher now offers the first and only solution for creating geospatial PDF files from within Adobe Creative Suite and with the inclusion of import support for ESRI geodatabases offers a truly comprehensive map design and publishing solution.” he added.

MAPublisher 8.2 includes all the significant functionality introduced in earlier releases of MAPublisher as well as the following new features and enhancements.

New Features of MAPublisher 8.2 for Adobe Illustrator

  • Export to Geospatial PDF with optional retention of attributes and referencing for re-import to Illustrator
  • Support for the new MAPublisher spatial database import system for ESRI geodatabases (additional license required. Windows only)
  • Upgraded functionality for the MAPublisher LabelPro collision-free rule-based labeling system (additional license required)
  • Dozens of improvements & enhancements for the MAP Web Author Tool for automatic creation of interactive Flash maps
  • New MAP Measurement tool for measuring lengths, perimeters and areas in page or map units
  • Import and export of KMZ files
  • Enhanced grid and graticule functionality with a number of new features including full support for rotated MAP Views
  • New functionality to create attributes for text objects from corresponding map features
  • New functionality to create a map index using additional feature attributes
  • Enhanced Expression Builder with recently used list and many new functions
  • Enhanced Preferences options includes dozens of new customizable items for most MAPublisher functions
  • Upgraded MAP View panels with new functionality
  • Various other user interface improvements and performance enhancements to improve usability

Features of the MAPublisher Geospatial PDF Exporter

The MAPublisher Geospatial PDF exporter offers the ability to generate Adobe Acrobat PDF files that contain all the cosmetic features of the completed Adobe Illustrator map document as well as all the GIS data attributes and co-ordinate information of the original GIS data files, such that within Adobe Acrobat the following functionality can be performed without the aid of any special tools, plugins or other special extensions to Adobe Acrobat.

  • View map locations in various coordinate systems including decimal degrees, DMS, Military Grid and more.
  • Find a location in a map and mark it with a comment
  • Measure distances on a map using real-world units (miles, kilometers, feet, etc.)
  • Reveal the attributes of map features by clicking on the feature within the map document
  • Search by map attribute values to reveal all map features that satisfy the query
  • Option to retain attributes and georeferencing for re-import to Illustrator/MAPublisher

Features of the MAPublisher spatial database importer

  • Direct import from ESRI Personal Geodatabase (requires ArcGIS license)
  • Direct import from ESRI File Geodatabase (requires ArcGIS license)
  • Direct import from ArcSDE servers (requires ArcGIS or ArcReader license)
  • Support for point, line, polygon and Bezier curve geometries
  • Support for Annotations
  • SQL attribute query support executed on import to enable import of specific features only
  • Spatial filter executed on data import to enable selective importation based on defined data extents
  • Support for subtypes and domains during import

The MAPublisher spatial database importer for Illustrator is available as an add-on option for MAPublisher 8.2, for Windows only, for US$599. MAPublisher users with active MAPublisher maintenance may purchase the MAPublisher spatial database importer for only US$349. New MAPublisher 8.2 licenses including MAPublisher spatial database functionality are US$1549. Academic, floating license and volume pricing is available. Prices include 1 year of maintenance. Full details are available at

More about MAPublisher for Illustrator

MAPublisher for Illustrator is powerful map production software for creating cartographic-quality maps from GIS data. Developed as a suite of plug-ins for Adobe Illustrator, MAPublisher leverages the superior graphics capabilities of this graphics design software for working with GIS data and producing high-quality maps with efficiency.

MAPublisher 8.2 for Illustrator is available free of charge to all MAPublisher for Illustrator customers with a valid maintenance subscription and as an upgrade for non-maintenance members at US$549. New licenses are US$1249. Academic, floating and volume pricing is available. Prices include 1 year of maintenance. Full details are available at

Interview with MarineMAP Mashup Developers (Kelso)

Tuesday, April 21st, 2009


[Editor's note: MarineMAP is a cutting edge mashup built using PostGIS, GeoDjango, Ajax, Flash, OpenLayers, GeoServer and MapServer with Google base map tiles. It assists stakeholders in the design of MPAs (Marine Protected Areas) in mapping oceanographic, biological geological, chemical and human dimensions of the ocean and coastal areas. I talk with Will McClintock and Chad Burt of the Marine Science Institute at University of California at Santa Barbara about the technical underpinnings and development philosophy behind the project. One key to the project's success (rolled out Dec. 2008) has been the hiring of dedicated programmers to implement design ideas and new technology to extend an earlier version's usability and reach. Thanks Melissa and Sebastian!]

Interact with the MarineMAP at

Interactive Map Tool Objective: MarineMap is an internet-based decision support tool that provides the capacity for the SCRSG (South Coast Regional Stakeholder Group) to view data layers, create individual MPA concepts, assemble collections of individual MPA concepts into MPA arrays, receive basic feedback on how well MPA concepts and arrays meet guidelines for MPA design, and submit MPA arrays to staff as MPA proposals. This tool will be the primary way in which MLPA Initiative staff and SCRSG members capture and store information regarding MPA proposals.


(Above) Screenshot above showing Marine mammal and Nearshore habitat layers on base map with area Measurement Tool enabled.

(Question) Kelso’s Corner: What technologies are leveraged in MarineMAP?

(Anwer) MarineMAP: We’re not using ArcGIS at all, save for cutting map tiles (using ArcGIS Desktop and Arc2Earth) and, as a non-critical component of the system, ArcSDE / SQL Server. We’re mainly using PostGIS, GeoDjango, Ajax, Flash, OpenLayers, GeoServer and MapServer and will soon switch to the Google Earth API.

We are using OpenLayers, rather than the Google Maps API for our “slippy map”. OpenLayers is pure javascript, as is most of the client application. We are using Flex, but only for the charting component. [Editor's note: OpenLayers is using the Google Maps tiles.]

(Q) Kelso’s Corner: How many programmers do you have on staff to deal with all the software components?

(A) MarineMAP: Currently, two of our developers work full-time on MarineMap, while our other two developers work half time. We also have several GIS analysts and a cartographer to deal with the data end of things. We are now looking for a full-time, in-house Assistant Web Developer to continue working on MarineMap. As we extend MarineMap to different geographies and planning processes, we anticipate that we’ll be looking for one or two more programmers as well.

(Q) Kelso’s Corner: What was the rational for doing this substantial map development in house? Did you evalutate other routes, consultants, off the shelf software before going this route, why was this option preferable? Did you have a good cheat sheet for how to develop / implement this technology? Did you have to hire new staff to do the programming or did you have existing expertise to draw on?

(Anwer) MarineMAP: We did not have a cheat sheet for how to develop / implement this technology. This was a brand new application using some new technologies, and some that we were familiar with. Of course, we had experience developing other applications and some of these technologies overlapped. But, there was a significant amount of learning happening for all of our developers.

The MLPAI is an on-going process that will terminate sometime around 2011. Until then, we need to have a highly functional and stable application that can be adapted to the changing needs of the process. It turned out to be much more cost-effective and time efficient to hire in-house developers to work on the application year-round. Before we built our team, we spent a significant amount of time considering a host of alternatives, including trying to maintain and tweak Doris, contracting out all of the work, etc.  Initially, we felt we did not have enough in-house expertise. Although we already had Chad Burt (UCSB), Jared Kibele (UCSB), Tim Welch (Ecotrust) and, now, Ken Vollmer (Ecotrust) as our in-house crew, we eventually contracted two developers from Farallon Geographics (Dennis Wuthrich and Alexei Peters) for a limited period to  help with developing the database schema. This was particularly nice given that we had only 6 months to get the first version of MarineMap out the door. Dennis and Alexei are no longer working on the project but I am very grateful that we had access to their time and expertise during the initial phases.

(Q) Kelso’s Corner: What was Doris?

(Anwer) MarineMAP: At the beginning of the Marine Life Protection Act Initiative (MLPAI), staff chose to hire consultants to build an application (eventually called “Doris”) that was built on ArcGIS Server 9.1 technologies. It shared some of the features of MarineMap, including drawing MPAs and arrays, and generating reports on what was being captured inside those MPAs. Doris had a poorly designed interface and, perhaps more significantly, it was dreadfully slow. Consequently, few stakeholders used it. Furthermore, because the application was built using technologies with which we had no particular in-house expertise, and because these technologies were proprietary, we had a difficulty updating the application or tweaking it on the fly. (I had been running ArcSDE / ArcIMS and ArcGIS Server applications for a couple years but had no real development expertise in, say, ArcObjects, or VB .Net.)

(Q) Kelso’s Corner: It seems there are many more RubyOnRails developers than Django. Have you found this a hindrance for hiring staff or when looking for trouble shooting advice?

(Anwer) MarineMAP: It does seem to be a bit of a challenge finding Django developers, particularly those that can / will work locally. I have not tried to hire a RubyOnRails expert so I have no direct means comparison.

(Q) Kelso’s Corner: Why will you be switching to the Google Earth API? Is this only for the front end? Have you been happy with GeoDjango?

(Anwer) MarineMAP: GeoDjango has been fantastic. Using the Google Earth API does not mean ditching GeoDjango. Rather, using the Google Earth API represents a shift away from the OpenLayers API. We’ll still be using GeoDjango extensively.

[Our lead developer] was a big proponent of RubyOnRails for quite some time, but Django has taken many of its best ideas to Python. While Ruby is aesthetically a beautiful language, Python is usually much faster and has a more mature set of modules to build on. The only thing I miss after switching over to Django is the database migrations Rails offers. Most open source GIS packages also have bindings for Python, where as there a few similar tools for Ruby.

Switching to the Google Earth API will just mean replacing OpenLayers. OpenLayers is a very good library, but the Earth API is much faster due to the fact that it is a compiled plugin rather than being written in javascript. This allows it to display thousands of placemarks on screen at once, which is one of the primary reasons for switching. Google Earth can also display temporal and 3d data.

(Q) Kelso’s Corner: Besides the change to Google Earth API, what other changes, updates do you plan for this online map?

(Anwer) MarineMAP: Besides switching to the Google Earth API, there is one major upcoming update to MarineMap. Specifically, we will be implementing a map-based (i.e., location based) discussion forum. Users will be able to zoom into a location on a map and tag objects (MPAs, data, places) with a comment. Other users will see these comments (if they have comments “turned on”) as they zoom in to a location or if they load an MPA. Users can then participate in a dialog via a traditional discussion forum that is linked to the map. Furthermore, users will be able to define a geographic region and subscribe to RSS feeds (using GeoRSS) for any activity within that region. One might choose to do this, for example, if they want to be notified by email any time somebody draws a new MPA in, or makes a comment about a data layer in a specific region that he / she cares most about. I believe the map-based discussion forum will go a long way in facilitating discussion about MPAs, particularly outside the in-person monthly stakeholder meetings.

Conclusion: Thanks so much for the informative Q&A session. Please check out the MarineMap project at