DataPress 1.5 Released — Geocoding and more! May 11, 2011

We’ve got a big round of updates to release today, all made possible thanks to a great new member of our team, Zach Wener-Fligner. Zach has been working to make DataPress easier to use for geo data.

You can download the new release on our Google Code page.

We think this release is going to be a huge usability improvement for DataPress. Please let us know if you have any thoughts, feedback, or bug reports!

Automatic Geocoding

You’ll never have to look up latitudes and longitudes again! DataPress can now automatically geocode addresses in your data in the background. We utilize the Google geo-coder in the background so approximate addresses will resolve too. Here are examples of values that will “just work”:

  • 32 Vassar Street, Cambridge MA 02139
  • Massachusetts
  • 02139
  • Mexico

Here’s how it works:

  1. Create a map visualization as you normally would
  2. When selecting your Location Field, pick a property in your data that contains an address and then tell DataPress that this is an “Address” field.
  3. When you save your Exhibit, DataPress will Geocode all of the data in the background and cache the results in its database.

That’s it! When you load your map, everything should just work. We double-check the freshness of the geocoding cache every time a user loads your map, which means if the data changes (you’ve added a new address, for instance) we will automatically add its lat,lng into the cache the first time someone tries to view it.

Reordering Views

One of the problems in past DataPress versions was that it was difficult to re-order views. We’ve added drag and drop functionality so that you can drag your list of views into the order in which you’d like to see them.

Auto-Detecting Data Types

DataPress currently supports Google Spreadsheets and “Exhibit-Style” JSON files. DataPress now auto-detects these two data types, so we’ve removed the requirement that users tell us what kind of data they are linking to. We may add this back in the future if we add new data types. Let us know what you think.

Kanglaonline June 23rd, 2011


We were using the previous version of Datapress, it was working. We recently updated to 1.5 and tried with a google spreadsheet, it’s not working.

We tried to put the url provided in this to to the datapress add link screen in wp admin..

but it always return Warning: Datapress could not parse the provided URL as a Google Spreadsheet. Are you sure this is the publicly-shared sheet URL?

Could you suggest what might be the possible cause. Also is there a way we can use the exhibit plugins hosted in our site instead of using from smit site. We noticed that the server is so slow after we activate the plugins and use it in a wordpress blog.


Nathan July 1st, 2011

I’m having this same problem. Keep getting the warning message that it can’t parse. Would love to use this.

Alexis Wilcox July 27th, 2011

BTW this feed was mentioned by Christian Dillstrom, the mobile & social media marketing specialist – so you must be doing a wonderful job.

Gaptek Update September 19th, 2011

yeah somehow, any gps related issue still cannot working properly on my country.

Tom September 27th, 2011

Add an exhibit menu comes up when we click the icon, but nutting’ works after that.

Mac OS10.7, Safari and Chrome

Glenn February 21st, 2012

Yeah I keep getting the parse error message when trying to link to the google spreadsheet published on a web page –

any solutions out there?

Deimosa March 3rd, 2012

I have been getting the same message, “Warning: Datapress could not parse the provided URL as a Google Spreadsheet. Are you sure this is the publicly-shared sheet URL?” I spent 8+ hours trying to use this plugin yesterday, and there is no coherent explanation that I can find online to fix this, just more people with the same issue. I tried using spreadsheets provided by some of the example projects and it can’t parse them either. I also tried switching browsers and pasting in every type of URL Google Docs provides, from the share button (top right) and the file menu (publish to the web). I am really, really frustrated!