The latest version of Ingres relational database now also includes support for geospatial data. GIS functions and spatial data types are included out-of-the-box (i.e. do not require additional plug-ins) and make it easy to enable web mapping. Ingres 10S supports spatial applications, such as Esri’s ArcGIS for Desktop and FME but also MapServer and GeoServer.
Ingres 10S is supported by other programming libraries including GDAL/OGR and GeoTools, allowing import, export and manipulation of vector data. Ingres 10S leverages the GEOS geometry and PROJ cartographic projection libraries for manipulating and transforming spatial data between dozens of geographic and planar co-ordinate systems.
Ingres 10S is an open source, enterprise grade database, not as popular as MySQL or PostgesSQL but, as the other options, can be downloaded and used for free. Ingres was first created as a research project at the University of California, Berkeley in the early 1970s. Since the mid-1980s, Ingres has spawned a number of commercial database applications, including Sybase, Microsoft SQL Server, NonStop SQL, but also open source PostgreSQL (which with PostGIS extension is the most popular open source spatial database).
One of the most exciting things about the architecture of the web is how easily it supports mashups—URLs, IFRAMEs, XHR, and more make it easy to build great new services on top of building blocks from others. As more and more people use the web for non-public data, we need new techniques to secure those building blocks. That’s where OAuth comes in—an open, standard way for users to grant permission for an application to access part of their account.
Since we announced support for OAuth in 2008, we’ve seen tremendous usage growth in our APIs that require user authorization, like Calendar and Docs. While the spec isn’t completely finalized, Google is pleased to announce our experimental support of an easier way for developers to obtain user authorization for our APIs: OAuth 2.0 with bearer tokens. Whether you use our updated client libraries or just write to the protocol, you should be able to do more with less code.
In addition to supporting a simplified protocol, we’re also introducing a simpler, cleaner consent page for OAuth 2.0:
Google believes in open systems that give users value, transparency and control. We hope the OAuth 2.0 protocol helps developers deliver just that: powerful applications that make use of user data without compromising on safety or security. Check out our documentation to get started with OAuth 2.0.