Geowanking moving to O’Reilly
Brady has just posted the news on the Geowanking list. Full text after the jump.
Howdy!
Joshua has been quietly looking for a good home for Geowanking for a while. He approached O’Reilly and we have agreed to support the list.
I’d like to thank Joshua for starting the list and helping the community grow. He’s put in a lot of time and energy for us. Thanks!
O’Reilly is invested in the geospace. Where 2.0 is one of our strongest conferences and I consider the geowanking community to be the conference’s primary constituent. So when we were asked to take on the list it was an obvious yes to me. We want to support this community and help it grow.
What does this mean?
- Later today or tomorrow we will be moving the list to O’Reilly servers.
** The domain will change.** Joshua is keeping?http://burri.to, but is giving us geowanking.org. The new list address will be??geowanking@geowanking.org
The archives and your subscriptions are intact, but you may need to reset your user password and digest settings.
The archives will still be public.
Please mail me for admin or other issues about the list. Laura Painter, an O’Reilly employee, has spent a lot of time on this (thanks!). She’ll be monitoring the list for technical hiccups.
What about the future? We’ve got a couple of ideas for how to support the community and I would love to hear your thoughts on them. I’ve been thinking that a planet installation on geowanking.org would be great.Any others?
Cheers,
brady
Kudos to O’Reilly for stepping up and keep Geowanking running.
Concerned about stacks?
I’ve been hearing much about stacks these last few weeks.
We want an all ESRI stack
We want to break out of the ESRI stack
I want an all OSGeo stack
Bill Gates’ stack is the work of the devil
I want to avoid the [INSERT LEAST FAVORITE SOFTWARE COMPANY HERE] stack at all costs
Why concern yourself with branding stacks? OK, maybe if your corporate IT department dictates that you must go a route you have to worry about it, but otherwise concerning yourself with an overarching stack just distracts you on matching your needs with the best hardware/software. Stack away, but focus on the individual parts, not the whole suite. Leave the marketing terms such as LAMP/WAMP/XXXX to others and pick what works.
Be careful with stacks
Be careful with stacks
Concerned about stacks?
I’ve been hearing much about stacks these last few weeks.
We want an all ESRI stack
We want to break out of the ESRI stack
I want an all OSGeo stack
Bill Gates’ stack is the work of the devil
I want to avoid the [INSERT LEAST FAVORITE SOFTWARE COMPANY HERE] stack at all costs
Why concern yourself with branding stacks? OK, maybe if your corporate IT department dictates that you must go a route you have to worry about it, but otherwise concerning yourself with an overarching stack just distracts you on matching your needs with the best hardware/software. Stack away, but focus on the individual parts, not the whole suite. Leave the marketing terms such as LAMP/WAMP/XXXX to others and pick what works.
Be careful with stacks
Be careful with stacks
Catching up
I was out last week in New Orleans and of course had no time to block so I’m going to try and catch up this week.
“I strongly agree with Dave Bouwman’s assumption that this is the result of a long lasting strategy of trying to cram desktop GIS into the browser with GIS manufacturers concentrating on developing utterly generic ‘out-of-the-box’ WebGIS products. So this wants us GIS developers make to believe that we are able to produce WebGIS applications in a jif. But the simple fact is that 99% of so called WebGIS apps have a quite narrow purpose, thus need pretty focused functions and user interfaces instead of bloated generic UI’s.”
It is clear GIS developers understand what hasn’t worked in the past and what needs to be done in the future. The trick is to enable complex GIS analysis in a way end users can take advantage of it. If it was easy, everyone would already be doing it.
More baseball geography; Five Migrations in Baseball History. Lets see, statistics, geography, beer, despair. Is there nothing baseball can’t teach us?
Yes, ArcGIS Server Flex API 1.0 was released last week. Cue the “Where is Silverlight?” questions. Might be a great topic to discuss at the 2009 Developer Summit.
Google Earth for the iPhone has been released. After playing with it for a week a couple things come to the surface.
- First it is very well done and visually impressive. Fingers can navigate 3D globes.
- The Edge network is too slow.
- I almost got run over by a streetcar navigating the globe. Could that be worse than texting with your head down?
- The tilt function is confusing when you are walking. I want to hold the unit in front of my face, not look strait down (see #3).
I can’t wait to see the next version and start using the iPhone to interact with network KML.
- whit has more iPhone/OpenLayers goodness on his blog.
Catching up
I was out last week in New Orleans and of course had no time to block so I’m going to try and catch up this week.
“I strongly agree with Dave Bouwman’s assumption that this is the result of a long lasting strategy of trying to cram desktop GIS into the browser with GIS manufacturers concentrating on developing utterly generic ‘out-of-the-box’ WebGIS products. So this wants us GIS developers make to believe that we are able to produce WebGIS applications in a jif. But the simple fact is that 99% of so called WebGIS apps have a quite narrow purpose, thus need pretty focused functions and user interfaces instead of bloated generic UI’s.”
It is clear GIS developers understand what hasn’t worked in the past and what needs to be done in the future. The trick is to enable complex GIS analysis in a way end users can take advantage of it. If it was easy, everyone would already be doing it.
More baseball geography; Five Migrations in Baseball History. Lets see, statistics, geography, beer, despair. Is there nothing baseball can’t teach us?
Yes, ArcGIS Server Flex API 1.0 was released last week. Cue the “Where is Silverlight?” questions. Might be a great topic to discuss at the 2009 Developer Summit.
Google Earth for the iPhone has been released. After playing with it for a week a couple things come to the surface.
- First it is very well done and visually impressive. Fingers can navigate 3D globes.
- The Edge network is too slow.
- I almost got run over by a streetcar navigating the globe. Could that be worse than texting with your head down?
- The tilt function is confusing when you are walking. I want to hold the unit in front of my face, not look strait down (see #3).
I can’t wait to see the next version and start using the iPhone to interact with network KML.
- whit has more iPhone/OpenLayers goodness on his blog.
I come to praise the Web ADF, not to bury it
I was just talking to someone today about web applications for ArcGIS Server 9.3 and they were surprised that I was using the Web ADF to create an application after my post earlier this week on the JavaScript API. I feel like I need to clarify some things about that post. It wasn’t so much a?desertion of the Web ADF, but point that one should be looking toward the JavaScript API (and I suppose the Flex API) for most mapping situation and use the Web ADF (Java and .NET) when it best makes sense. I’m using the Web ADF on this project because the requirements of the end user is best met with the Web ADF. The great thing about the JavaScript API, the Flex API, the .NET Web ADF, the Java Web ADF and even the JavaScript extenders for the JavaScript API is that they all can be called on if needed. Of course the Web ADF does have licensing issues that ESRI needs to address that limit its appeal even when it is the best choice for the solution.
ESRI has given their developers choices that we aren’t accustom to and in turn ESRI developers should be looking at the choices when making a decision of what SDK to use. Also just because you use the JavaScript API or the Flex API doesn’t mean you’ll end up with a great application. So much more goes into it and there isn’t any reason why the Java Web ADF can’t give you a great application anymore than the Flex API can.
Et tu, James?
Et tu, James?