My wife always complains that she can’t buy me any books because I buy them before she even hears of them. Well if she wants to surprise me this year, she can take a look at the kite aerial photography gift guide over at MAKE.
I’ll only have to wait for some wind to take up to date aerial photography of areas I’m working on. Heck and you can take it all on the road with you and amaze your friends.
Even back in 1750 Ben Franklin was an avid kite aerial photographer
The Yahoo! Brickhouse closing put some projects in jeopardy, but apparently Fire Eagle is “alive and well”.
Rest assured that whilst Brickhouse may be gone, Fire Eagle itself lives and thrives within the Yahoo! Geo Technologies Group. Fire Eagle has been, and will continue to be, a core component of Yahoo’s Geo Technology and User Location strategies and we’re committed to developing features, applications and support without interruption.
Fire Eagle and Pipes are two of Yahoo!’s better projects and hopefully the problems at Yahoo! won’t hurt their development.
We’ve been loading our tile caches in Amazon S3 for quite some time now and it looks like others are trying to take advantage of the service. I’ve come to the conclusion that using S3 for your tile cache makes a ton of sense for performance and reliability issues. Our S3 tile caches are more reliable than our file servers in serving up the tiles and do it so much faster. Is anyone else noticing the benefits of S3 or has is been problematic for you?
Jack Dangermond was interviewed on CRBonline this week and there was one comment that caught my eye. When Jack commented on ArcLogistics on mobile, the interviewer asked him this:
Q. Does it run on the iPhone/BlackBerry Storm/Windows Mobile/Google Android? If not, when will it?
A. We’ve standardised on Windows Mobile as a platform that gives us a level of device independence. We are looking at other platforms, but see Windows Mobile as a primary IT platform for professionals.
Yikes, I guess we and our clients won’t be running ArcGIS on their mobile devices in the coming year.
Of course I could be over analyzing Jack’s comments like others are.
Redfin seems to have set off criticism of Microsoft’s VE API. Their reasons for their move are outlined on their blog and many seem to agree with their conclusions about Microsoft’s and Google’s mapping APIs. I’m not sure I agree the VE API is much slower than Google’s, but I suppose if you are hypersensitive you’ll notice the difference. For us it usually is local network conditions that cause one API to be slower than the other, but YYMV.
Vish does a great job of listing what he is missing from the Virtual Earth API. Many ESRI users are exposed to these differences in the ArcGIS JavaScript Extenders for Google Maps and Virtual Earth when they move back and forth between them. I suppose if I had to come out and say which API was our development “standard”, I’d probably go with Google Maps API, but it wouldn’t be enough to call it a preference. The one feature that keeps us coming back to Virtual Earth is the Bird’s Eye imagery which many of our clients just love (planning and architecture seem to gain much from those, much more than street level imagery taken from a car in traffic).
My biggest problem with Virtual Earth is trying to figure out what the heck the “Live” platform is.
Running the new ArcGIS License Manager? You might want to download the latest update from ESRI’s servers. Those running ArcGIS on laptops should definitely look.
Issues Addressed in this update
- NIM003128 ‘ The ArcGIS License Manager for Windows is now supported without hardware keys.
- NIM006141 ‘ The ArcGIS License Manager is now supported on RedHat and SUSE LINUX.
- NIM000652 ‘ The license manager is losing its connection with the USB key when a laptop goes to sleep, resulting in the failure of the license manager when the laptop ‘wakes up’.
- NIM013222 ‘ A remote user can gain access to files on the license server using the License Manager as a gateway.
- NIM040406 – The AIX License Manager has been updated to support systems running AIX 5.3 ML04 and higher.
And before you get too excited, license borrowing won’t be implemented until after 9.3.
Looks like Google Map Maker is now available in 164 countries?around the world. If only they’d be less evil and work with OpenStreetMap. I don’t know about you, but my time is too valuable to give it to Google without compensation.
I always toss a little Google on in the morning when I want to take over the world.
What? I need to use Flex APIs (and thus GeoWeb 2.0) to do this?
GeoWeb 2.0 would need to be able to answer spatial questions and solve real-life problems in the spatial context’in addition to locating and visualizing data on maps. For example, it should be able to answer questions, like when the fire broke out, taking into account wind direction and speed, which area will be effected by the smoke and how many residents will be effected; or what critical infrastructure needs to be protected. It should also be able to pinpoint the nearest safe shelters for residents likely to be affected, the best evacuation routes; and the best way to setup road blocks so that the least number of U-turns will occur.
Why does someone need to propose GeoWeb 2.0 (other than I’m sure O’Reilly requires appending the 2.0 suffix to any article you write) when we can do everything Zhang outlines with GeoWeb Classic 1.0? Good grief indeed!
The ArcGIS Server REST[ful] API has been a wonderful addition to the ESRI developer world. I’ve seen more people talking and deploying RESTful API applications since it was released than I did with 9.2 (YMMV of course). One thing about it though is there still isn’t a community built around it. Sure the forums are there, but even those are not as dynamic as they should be. The Server Resource Page is very static and developers cannot add comments or suggestions to the code examples or the API reference for others to learn by. I’ll be bringing this up yet once again at the ESRI Developer Summit at what will hopefully be a JavaScript SIG (Not at the same time as the .NET SIG please).
That brings me to OpenLayers and ArcGIS Server. The RESTful API gives easy access to ESRI ArcGIS Server services to OpenLayers and other APIs, yet there is no way to collaborate such development on the ESRI community pages. I’d like to see ESRI adopt OpenLayers as readily as they have adopted Flex, Google and Microsoft APIs so that ESRI developers can deliver the applications their clients demand. There is some really good code floating around there for using ArcGIS Server REST API with OpenLayers, just not where it probably belongs to get ESRI developers started. For now just head on over to the OpenLayers email list or IRC and get involved.
As I said on Twitter, this is probably a good move for ESRI and building a community around the User Conference. Facebook is a closed ecosystem (you have to sign up to participate) but given Facebook’s traction online, it is the right move. So if you want to keep up on the ESRI UC news, sign up for Facebook and join the Official ESRI UC group.
**Update: **As some have pointed out on Twitter, not every company allows access to Facebook so the community might be missing key people.