Aug
6
A day with TileCache: generating KML Super-Overlays
Filed on August 6th, 2008 at 12:55 pm under Apache, devs, FeatureServer, GDAL, GeoServer, GIS, kml, MapServer, MetaCarta, OpenLayers, Python, SharpMap, TileCache, TMS, Tutorials, WMS | 6 Comments
My friend Diego Guidi is the smartest GIS/.NET developer I personally know here in Italy. He is the developer of NetTopologySuite, the port in the .NET world of the popular Java's JTS Topology Suite from VIVID Solutions. I wanted, sooner or later, write some stuff here about WMS and TMS, and now I am very happy that Diego asked me to publish this brilliant article about this topic.
First of all, let me thanks Paolo for hosting this post! I hope that this article can be interesting and useful like other stuff that you can find here…
Introduction
There are a lot of discussions out there about how to define Google Earth, Google Maps, and related apps… are they GIS? Viewers? Video games? Even a neologism was created: Neogeography. I think that all the folks out there have the same idea in mind: maybe Google don't make the same business as ESRI, but Google Earth is cool, and it's funny to play with it!
Jun
6
Spatial Database for Postgres and ArcGis users: how to choose
Filed on June 6th, 2008 at 5:45 pm under ArcGis Desktop, ArcIMS, ArcObjects, ArcSde, FeatureServer, GeoServer, GIS, gvSIG, PostGIS, QGIS, uDig, ZigGis | 13 Comments
As many of you can have already read, ArcSde for Postgres is coming out at ArcGis 9.3 (it is currently in the release candidate state). It will let you store geometries in two formats, Esri geometry and PostGis geometry, in the same fashion ArcSde for Oracle is letting Esri or Oracle geometries be stored.
I have seen some interest in the GIS community about this new, and i was reading interesting posts by Bill Dollins, Paul Ramsey, James Fee and Dave Bouwman, so I thought i would post here my opinion. Plus, as some of you may already know, zigGis 2.0 is out, so I am very interested in understanding where it would be better to use one (ArcSde) or the other (zigGis 2.0) solution.
First let me introduce you my point of view: i am since the ARC/INFO era a great fan of Esri software, and I am one of the many users in the GIS community saying that Esri is much much better vs Open Source in the GIS desktop products sector.
In fact, while also in the GIS OS scenario there are good products like QGIS, uDig, gvSIG (and some other), in my opinion no one of them still can even fairly reach what ArcGis Desktop and its extensions can actually do (with the big limit that you can use it only in a Microsoft box, but that is another story).
Read more
May
3
A day with FeatureServer #2
Filed on May 3rd, 2008 at 2:13 am under devs, FeatureServer, Flickr, GIS, OpenLayers, OpenStreetMap, PostGIS, Python, Twitter, Ubuntu, Web2.0, WFS, Windows, WMS | 4 Comments
In the previous post we have seen an introduction to FeatureServer, and we were just playing with the base edit sample, with the scribble layer.
Now it is time to use FeatureServer with our datasets: I am assuming that you will want to create FeatureServer services for shapefiles, PostGis layers, OpenStreetMap, Twitter and Flickr.
Feb
21
A day with FeatureServer #1
Filed on February 21st, 2008 at 10:10 pm under Apache, devs, FeatureServer, GIS, gvSIG, PostGIS, Python, QGIS, Ubuntu, uDig, WFS, Windows, WMS | 6 Comments
Some friends already spoke me well about FeatureServer by MetaCarta in the last weeks, so I already was waiting for having a bit of time to get started with it. Then James posted this on his blog, and my curiosity was definitely fired.
So I decided to spend a day for installing and testing it, without thinking of the lack of documentation (FeatureServer is still a young project, so no wonder here if the only way to get infos is digging in the source code and posting to the mailing list). The day I considered to spend on it then spawned to more and more hours that I could imagine, and given my actually very busy schedule at my job, I had to find free hours during the night and the weekend. I then decided to write this post to help people in getting started with FeatureServer in a quicker way that was for me.
FeatureServer is a simple and powerfull RESTful-Pythonic WFS server.
Only from this last sentence there are 3 very important things that made me like (and you should - also) FeatureServer before even getting started with it:
- Its RESTful architecture
- It is written in Python, and having chosen Plone as our CMS here at my office I am starting to like this language very much
- I truly believe that WFS is the way to go for remotely editing GIS data
