Esri Press:: Python Scripting for ArcGIS
This week I noticed Esri Press released a new book titled Python Scripting for ArcGIS.
Python Scripting for ArcGIS is a guide for experienced users of ArcGIS Desktop to get started with Python scripting without needing previous programming experience. Experience with other scripting or programming languages (Perl, VBA, VB script, Java, C++) is helpful but not required. Readers are expected to have good general ArcGIS skills and a basic understanding of geoprocessing procedures. There are 14 chapters with corresponding exercises on an accompanying DVD. Also included is access to a 180-day trial of ArcGIS for Desktop 10.1
So my first reaction was one of bewilderment at the price:
https://twitter.com/jamesmfee/status/289201055227596800
I mean that’s a bit above the normal price for a professional GIS book (which runs about $60) and of course much more above general python books, which run about free. But let’s not get too tied down on the price. I mean if your career depends on using ArcGIS and you want to learn Python, $80 shouldn’t be an impediment to making yourself more desirable.
Ah, but don’t fear. Amazon has Python Scripting for ArcGIS at a much more reasonable $50. Plus Amazon has the first chapter available for review so you can see if it will work for you.
If you’re interested in the author, his University webpage gives a little bit of background. I don’t have the book so I can’t give a recommendation yet. It is still preorder so I guess we’re going to have to wait a bit, but to save $30, why not? If people get the book, let me know how it is and I’ll make sure to share it with everyone else.
Esri Press:: Python Scripting for ArcGIS
This week I noticed Esri Press released a new book titled Python Scripting for ArcGIS.
Python Scripting for ArcGIS is a guide for experienced users of ArcGIS Desktop to get started with Python scripting without needing previous programming experience. Experience with other scripting or programming languages (Perl, VBA, VB script, Java, C++) is helpful but not required. Readers are expected to have good general ArcGIS skills and a basic understanding of geoprocessing procedures. There are 14 chapters with corresponding exercises on an accompanying DVD. Also included is access to a 180-day trial of ArcGIS for Desktop 10.1
So my first reaction was one of bewilderment at the price:
https://twitter.com/jamesmfee/status/289201055227596800
I mean that’s a bit above the normal price for a professional GIS book (which runs about $60) and of course much more above general python books, which run about free. But let’s not get too tied down on the price. I mean if your career depends on using ArcGIS and you want to learn Python, $80 shouldn’t be an impediment to making yourself more desirable.
Ah, but don’t fear. Amazon has Python Scripting for ArcGIS at a much more reasonable $50. Plus Amazon has the first chapter available for review so you can see if it will work for you.
If you’re interested in the author, his University webpage gives a little bit of background. I don’t have the book so I can’t give a recommendation yet. It is still preorder so I guess we’re going to have to wait a bit, but to save $30, why not? If people get the book, let me know how it is and I’ll make sure to share it with everyone else.
Leaving WeoGeo
Today is my last day at WeoGeo. I am looking forward to taking a much needed vacation in Kona, Hawaii and then sitting down and thinking about what I want to do next.
As always, you can reach me at james.fee@gmail.com.
Leaving WeoGeo
Today is my last day at WeoGeo. I am looking forward to taking a much needed vacation in Kona, Hawaii and then sitting down and thinking about what I want to do next.
As always, you can reach me at james.fee@gmail.com.
GeoPackage Comment Period is Open
The comment period is open for the GeoPackage.
The candidate OGC GeoPackage (GPKG) Standard provides an open, non-proprietary, platform-independent container for distribution and direct use of all kinds of geospatial data. The GeoPackage container and related API will increase the cross-platform interoperability of geospatial applications and web services in the mobile world. Standard APIs for access and management of GeoPackage data will provide consistent query and update results across such applications and services.
What’s not to love? I described the need for the GeoPackage from the perspective of WeoGeo over on the WeoGeo Blog:
I have gotten a lot of feedback on my blog and twitter saying that an OGC format like GeoPackage is stupid, bloated, and destined for failure and that we should all continue what we are doing because the market will decide. To me that is just sticking your head in the sand. The market is searching for something besides SHP and GeoTIFF and is waiting for leadership. There is only one organization that can get this implemented across the world (well Google did a pretty good job with KML before that became an OGC format) and that’s the OGC. They are secretive, obfuscated, backwards and their website is a classic case of poor user interfaces. That said, I’m VERY hopeful for GeoPackage becoming a standard.
The GoePackage is going to happen, that’s not in doubt. But if you don’t take the time to comment on the GPKG (I even like typing that) you lose all right to complain about it later. You’ve been warned. I feel like this guy trying to wash a car today. Don’t let this opportunity out of your grasp.
Car Wash
GeoPackage Comment Period is Open
The comment period is open for the GeoPackage.
The candidate OGC GeoPackage (GPKG) Standard provides an open, non-proprietary, platform-independent container for distribution and direct use of all kinds of geospatial data. The GeoPackage container and related API will increase the cross-platform interoperability of geospatial applications and web services in the mobile world. Standard APIs for access and management of GeoPackage data will provide consistent query and update results across such applications and services.
What’s not to love? I described the need for the GeoPackage from the perspective of WeoGeo over on the WeoGeo Blog:
I have gotten a lot of feedback on my blog and twitter saying that an OGC format like GeoPackage is stupid, bloated, and destined for failure and that we should all continue what we are doing because the market will decide. To me that is just sticking your head in the sand. The market is searching for something besides SHP and GeoTIFF and is waiting for leadership. There is only one organization that can get this implemented across the world (well Google did a pretty good job with KML before that became an OGC format) and that’s the OGC. They are secretive, obfuscated, backwards and their website is a classic case of poor user interfaces. That said, I’m VERY hopeful for GeoPackage becoming a standard.
The GoePackage is going to happen, that’s not in doubt. But if you don’t take the time to comment on the GPKG (I even like typing that) you lose all right to complain about it later. You’ve been warned. I feel like this guy trying to wash a car today. Don’t let this opportunity out of your grasp.
Car Wash