Thoughts on the GeoDesign Summit
I’m sure many of you have been following #geodesign on Twitter, but I thought I’d add some of my deeper thoughts. First off, yes everyone in attendance realizes that we’ve all been doing this since the beginning of time. GeoDesign wasn’t invented by anyone in particular, that was clear to everyone.
So I guess the next question what is GeoDesign and why do we need to even define it, especially if we’ve been doing this for years anyway Since we’ve all be already been doing this for years shouldn’t this be easy to define since we already have an understanding of it A Wikipedia entry has been started and I’d encourage everyone to take a look at it and refine it based upon your experiences.
I think a couple things helped bring so many people together from so many different disciplines. With Architects, Planners, Engineers, Technologists, Researchers, Professors, Graduate Students and “other”; there was academia, government and private industry. The one person in our industry that has the pull to get this done is of course Jack Dangermond. He was also gracious enough to allow the organizers to use the new ESRI Q Building which was perfectly set up for a conference of this size.
Adena Schutzberg and Matt Ball both did a great job diving deep into the conference and it would be a good idea to read up on what was discussed and what needs to be done to move forward. What I’m going to talk about is what I think came out of the Summit and what should be the next steps.
First off, there was a little push-back that was acknowledged at the Summit which seemed to revolve around the fact that some small group of people seemed to think they could take ownership of something everyone has been doing for years, GeoDesign. I was also a little on edge about what might have come out from this Summit, but in the end it was unfounded. The group of folks from Michael Goodchild to Carl Steinitz all where very pragmatic about GeoDesign, how we involve more in the process of design (how crowdsourcing can be involved), to even deeper issues such as how we must fundamentally change how we as humans impact our environment.
Many showed examples of GeoDesign projects that they are currently work on to ones that were completed decades ago. Also despite the Summit occurring on ESRI’s campus, there were many examples showed that included non-ESRI technology such as GRASS, Google Earth and SketchUp. Jack also stood up on stage and hoped next year the organizers could include other software platforms and technologies that weren’t on stage this year.
So this brings up what to do next. Where do we go from here. Jack asked everyone in attendance if they thought we should move forward with the GeoDesign concept and everyone agreed we should. The details on how were to do so was what we discussed Friday morning. There will be a GeoDesign Summit next year. Tom Fisher the Dean for the College of Design at University of Minnesota offered to host it there. Given the warm weather though many though Redlands would be a great location to hold it again (Mid 70s in January is hard to beat). Jack said that if the committee wanted to hold it at ESRI again he would offer up the facilities again. Jack also said he wanted to unbrand the summit from ESRI and have it stand alone. To do this the Summit will be moving off of the ESRI servers on to its own and engage other potential stakeholders.
Since there was so much content created and organized there was a discussion on how to best disseminate the data out to everyone. This was probably the most contensious discussion. On one had you have those who wanted to write books (grey hairs) and on the other there were those who wanted to set up a wiki and get more community involvement. In the end it appears we will have both, a GeoDesign book you can get signed by your favorite GeoDesigner and a wiki the community can showcase their ideas and collaborate.
One problem is how to get this information out to the community at large. Organizations such as the APA have the tools in place (and not ESRI branded) to facilitate getting the word out to their members. Since there were many researchers present, there was also questions about how we can get funding in place from NSF or possibly even the World Bank since better planning and design is critical to helping reverse the destruction of the planet.
So bottom line I admit I’m not one with too much patience for “University think” and there was plenty at the first GeoDesign Summit. But at the same time there was so much practicality shown that it isn’t hard to want to get Design and GIS more interconnected. One group that I think was underrepresented at the Summit was Technologists (I can’t say Architects or Designers because in this crowd that means something else). The gap between “GeoDesigners” and the public needs to be bridged with our work and our expertise. Making sure that this is represented in this GeoDesign initiative is important and we are those who need to make sure this is grounded in reality and not locked up in University research.
So lets see what happens. Will there be continued push back to “GeoDesign” from the geospatial community or will people want to be involved on the ground floor defining and encouraging GeoDesign I think we all realize powerful things happen when there is a marriage of design and GIS.
5 predictions Geo for 2010 and 5 things that won’t happen
Here are 5 predictions for Twenty Ten.
- The shapefile dies: SpatiaLite + ESRI’s File Geodatabase API finally put a dagger in the shapefile.
- GIS on iPhone/iSlate (Apple Tablet) and Android/Chrome OS: With Apple and Google owning the mobile space, we’ll see more proprietary and open source projects being ported to these platforms. Microsoft Tablet PCs and Windows Mobile/CE begin to die off.
- 64-bit: There will be some holdouts (cough ESRI), but most of us will be running native 64-bit code on our desktops and servers. Now to just get more RAM in this laptop.
- Mobile: If you aren’t running on the iPhone/Android/Blackberry you aren’t relevant. Web mapping apps become mobile browser aware. Those that aren’t were probably irrelevant anyway.
- Google: Google’s APIs continue to push the envelope and they continue to be the standard for everyone mapping on the interweb. Google is able to throw so much money and manpower at “problems” and their solutions are coming faster than anyone else can match.
Here are 5 things that won’t happen:
- Augmented Reality: Much like the Nintendo Virtual Boy, it sounds great until you try and use it.
- OpenStreetMap Dominates: Between Google’s quick improving of their database and continued licensing issues OSM plateaus. Companies will continue to try and figure out how to monetize OSM, but fail.
- ESRI + Microsoft: This was on the top 10 lists for many people in 2009, but I don’t think we’ll be seeing deeper integration. ESRI will continue to support multiple platforms (Google, OSM, Microsoft, “other”) and not become a Microsoft shop. As Google continues to erode away at SharePoint and Bing Maps, ESRI will make sure that they don’t get caught in Microsoft’s blind spot.
- Geolocation other than Twitter, Apple and Google (TAG): Foursquare, Brightkite, and others will fade as TAG rolls out new APIs and ensure their mobile devices are tagging everything you do.
- MySQL falls apart: Despite the dire predictions of Oracle or Monty destroying the project, too many people have too much invested in the project to let it fail. MySQL will be fine and LAMP will continue to power Badgers.
Hey, don’t worry… It’s gonna be a bright, sun-shiny day!
5 predictions Geo for 2010 and 5 things that won’t happen
Here are 5 predictions for Twenty Ten.
- The shapefile dies: SpatiaLite + ESRI’s File Geodatabase API finally put a dagger in the shapefile.
- GIS on iPhone/iSlate (Apple Tablet) and Android/Chrome OS: With Apple and Google owning the mobile space, we’ll see more proprietary and open source projects being ported to these platforms. Microsoft Tablet PCs and Windows Mobile/CE begin to die off.
- 64-bit: There will be some holdouts (cough ESRI), but most of us will be running native 64-bit code on our desktops and servers. Now to just get more RAM in this laptop.
- Mobile: If you aren’t running on the iPhone/Android/Blackberry you aren’t relevant. Web mapping apps become mobile browser aware. Those that aren’t were probably irrelevant anyway.
- Google: Google’s APIs continue to push the envelope and they continue to be the standard for everyone mapping on the interweb. Google is able to throw so much money and manpower at “problems” and their solutions are coming faster than anyone else can match.
Here are 5 things that won’t happen:
- Augmented Reality: Much like the Nintendo Virtual Boy, it sounds great until you try and use it.
- OpenStreetMap Dominates: Between Google’s quick improving of their database and continued licensing issues OSM plateaus. Companies will continue to try and figure out how to monetize OSM, but fail.
- ESRI + Microsoft: This was on the top 10 lists for many people in 2009, but I don’t think we’ll be seeing deeper integration. ESRI will continue to support multiple platforms (Google, OSM, Microsoft, “other”) and not become a Microsoft shop. As Google continues to erode away at SharePoint and Bing Maps, ESRI will make sure that they don’t get caught in Microsoft’s blind spot.
- Geolocation other than Twitter, Apple and Google (TAG): Foursquare, Brightkite, and others will fade as TAG rolls out new APIs and ensure their mobile devices are tagging everything you do.
- MySQL falls apart: Despite the dire predictions of Oracle or Monty destroying the project, too many people have too much invested in the project to let it fail. MySQL will be fine and LAMP will continue to power Badgers.
Hey, don’t worry… It’s gonna be a bright, sun-shiny day!
Have a Very Merry Christmas!
So we are sitting around watching Santa work his way toward Tempe, AZ and it is time to send the boy to bed. I hope everyone who has read my blog this year has a very Merry Christmas.
Have a Very Merry Christmas!
So we are sitting around watching Santa work his way toward Tempe, AZ and it is time to send the boy to bed. I hope everyone who has read my blog this year has a very Merry Christmas.
Twitter Acquires GeoAPI — The New GeoLocation Platform of Choice?
Given what we’ve witnessed since October, 2009 is sure going out with a bang. Google dumps Tele Atlas for their own mapping dataset and then gives away navigation, Microsoft adds street level imagery, Google adds oblique imagery and then gives away a spatial query server and Mapquest adds street level imagery as well. But today Twitter did something that just seems to fit perfectly with just about any mobile application. They went ahead and picked up GeoAPI.
Twitter clearly sees location as important as anything they do (I guess microblogging is something they do as well). Tagging tweets with location is something fairly new to the Twitter API, but with smartphones probably being the primary method of tweeting, location becomes natural with tweeting. We’ve been speculating that we could analyze tweets during “events” and see locations of tweets with information about what is being observed (flooding/fire/babes). Having a richer geo-api will only facilitate this further and could be the real killer crowdsourcing app.
The only pushback I’ve seen on twitter is the location API can be very accurate. I’d love to see them enable something like Fire Eagle where you can have it return a city level geocode rather than a hyperaccurate one. I mean I’m glad everyone knows how often I visit the Apple store, but I’d like @pbissett to wonder just a little.
So I’m sitting here just fantasizing what can be done with the data provided by Twitter and GeoAPI.