Tag Archives: OGC

GeoTools 8.6 Released

The GeoTools community is pleased to announce the availability of GeoTools 8.6 for download from source forge:
  • geotools-8.6-bin.zip
  • geotools-8.6-doc.zip
  • geotools-8.6-userguide.zip
  • geotools-8.6-project.zip
This release is also deployed to the OSGeo Maven Repository. For more information on setting up your project with Maven consult the Quickstart.

About GeoTools 8.6

This is a bug fix release containing fixes and improvements, including:
  • Several fixes in the WFS client, making it work against TinyOWS and ArcGIS WFS server
  • Improvements in usage of filter fuctions from SLD (some functions did not properly convert their arguments from string to numeric)
  • Removed tiling artifacts when rendering oversampled grid coverages
  • Sped up the usage of FIDFilter objects in map rendering
Full details are available in Jira's release notes.
Upgrading from GeoTools 2.7
For those migrating from GeoTools 2.7, upgrade instructions are available. No additional GeoTools 2.7 released are scheduled. Thanks for using GeoTools, and Enjoy!
The GeoTools Community

Read More »

GeoServer 2.2.4 Released

The GeoServer team is happy to announce the release of GeoServer 2.2.4, now available for download.

This is the latest release of the stable 2.2 series. The changes that might interest the most users are:

  • the monitoring extension module just got promoted to official extension [GEOS-5538]
  • the status page does not throw errors after catalog reloads anymore [GEOS-5371]
  • one critical fix in the REST configuration of freemarker templates [GEOS-5533]

The changelog also contains the following minor bug fixes

  • [GEOS-5338] – Filter function IEEERemainder mishbehaves in SLD
  • [GEOS-5537] – Tiling artifacts with RasterSymbolizer using bilinear interpolation (when oversampling raster)
  • [GEOS-5551] – WFS 1.0 capabilities will NPE with misconfigured OGR and XSLT output formats
  • [GEOS-5565] – workspace admin unable to create sql view
  • [GEOS-5570] – QueryProcess fails if called with an OGC filter (either 1.0 or 1.1)
  • [GEOS-5197] – Use the layer abstract as the GeoRSS channel description
  • [GEOS-5561] – Missing i18n support for ReprojectPage
  • [GEOS-5562] – Missing i18n support for WorkspaceEditPage
  • [GEOS-5563] – slight mixed up order of Y-parameters in AffineTransformPanel

Also, looking at the corresponding GeoTools release changelog we have the following extra goodies in:

  • improvements in the WFS cascading, we can now better interact with remote WFS servers running on TinyOWS and ArcGIS
  • imageio-ext was upgraded to version 1.1.6, which means from now on GeoServer uses GDAL 1.9 to extends the range of raster formats it supports

Download GeoServer 2.2.4, try it out, and provide feedback on the GeoServer mailing list.

Thanks again for using GeoServer!

Read More »

pycsw Receives OGC Compliance Certification and Reference Implementation Status‏

14 January
The pycsw development team is happy to announce that pycsw 1.4.0 is now 
certified OGC Compliant for OGC CSW 2.0.2 [1], and passes all 103 CITE 
As well, pycsw is now an official OGC Reference Implementation. A 
demonstration instance of the reference implementation is available.
Standards are at the core of pycsw; acheiving OGC compliance and 
reference implementation status is part of the project's ongoing 
commitment to an open source, standards-based metadata and catalogue 
component of spatial data infrastructures.
pycsw is an OGC Compliant CSW server implementation written in Python. 

The pycsw Development Team.
Read More »

GeoServer 2.2.3 released

The GeoServer team is happy to announce the release of GeoServer 2.2.3, now available for download.

This is the latest release of the stable 2.2 series and contains some small new features and interesting fixes:

  • [GEOS-3885] – Update Freemarker templates through REST API
  • [GEOS-5325] – Add title and abstract to LayerGroupInfo
  • [GEOS-5462] – The rendering thread can block forever under request cancellation
  • [GEOS-5479] – Error in Documentation: </PropertyName> tag used instead of </Literal>
  • [GEOS-5483] – json output in WPS extension does not work due to missing library
  • [GEOS-5485] – Border artifacts when reprojecting single banded (scientific) raster data

Also, looking at the corresponding GeoTools release changelog we have the following extra goodies in:

  • better support for chaining rendering transformations
  • fixes to time/date handling in CQL
  • Oracle specific SDO_NN function to find the N nearest objects to a given location

We also welcome our newest committer, Davide Savazzi, and thank him for the work on Freemarker template through the REST API and the title and abstract support in layer groups, as well as the SDO_NN work back in GeoTools.

Download GeoServer 2.2.3, try it out, and provide feedback on the GeoServer mailing list.


Read More »

OGC Draft GeoPackage Specification - Finally the Shapefile Format Replacement?

Can this be true? Finally a Shapefile replacement which would be a standard coming from the OGC? Maybe we're getting there! Here's an entry on the OGC Draft 'GeoPackage' Specification. You must take a look at the short presentation (below).

From Spatially Adjusted: "The specs are right what I’m looking for:

  • SQLite container
  • Vectors are Simple Features SQL (SpatiaLite)
  • Support for Rasters and Tiles (SQL Tables and API)
  • AtomPub

When I first saw it and the words OGC tied to it, I tried to hate it, I really did. But there is much here to like."

This is a topic we discussed a few times in the past in stories like: The future of the Shapefile format?FOSS4G Notes: SpatiaLite, the Shapefile of the Future?, and The Shapefile 2.0 Manifesto.


OGC Plenary GeoPkg_SWG 1-14

Read More »

OpenGeo Suite 3.0: Interview With Rolando Peñate from OpenGeo


OpenGeo has recently released OpenGeo Suite 3.0. Slashgeo sat down with Rolando Peñate, the Product Manager for the OpenGeo Suite, to discuss this new release. Here are the results of our interview:

Slashgeo: What are some of the most exciting features available in the OpenGeo Suite 3.0 release?

Rolando: We’re most excited about bringing spatial processing to the OpenGeo Suite. With processing, our customers can work with larger data and perform just-in-time analysis with fewer bottlenecks than with a desktop-based GIS workflow. We believe that exposing processing on the web will provide IT professionals the flexibility to solve unique problems in innovative ways—either by directly invoking existing WPS processes, writing new processes in common scripting languages, using rendering transformations to style data, or even in ways we haven’t yet considered.

OpenGeo Suite 3.0 adds the ability to perform spatial processes on the server and designates the server as the place where processes are defined. The OGC Web Processing Service (WPS) specification makes powerful processing tools available for broad consumption on the web. Combined with server-side scripting libraries, this makes it possible for web developers to create processes that perform complex analysis using familiar languages like Python or JavaScript. This enables IT professionals to build web applications that can run spatial processes on-the-fly against data from anywhere using standard web development practices.

One place we’ve implemented this is a prototype for the USGS National Hydrography Dataset that allows editing of data while validating against strict topology rules across multiple layers. Their current tools require up to six hours for a single edit, but our prototype drastically reduced the effort—down to about one minute—by using a web-based editor.

We are also working to make processing operations easier in browser-based visualizations. Rendering transformations enable just-in-time use of any WPS process as part of a layer’s style. The process is applied on-the-fly to transform the area being viewed, rather than the full data set (as it would with desktop based GIS), and provide immediate visual feedback. For example, NASA’s Global Learning and Observations to Benefit the Environment (GLOBE) program leverages this feature for fast, dynamic presentation of interpolated surfaces derived from environmental measurements collected at schools around the world. Similarly, one could create topography maps in real-time by applying a process to a digital elevation model and defining a style for the resulting contour lines.

Slashgeo: How does OpenGeo Suite 3.0 measure up to comparable proprietary solutions?

Rolando: One of our goals for the OpenGeo Suite is to solve many of the same problems as proprietary solutions, though not necessarily by providing the same tools. Our product and proprietary solutions can both publish data from a variety of enterprise databases, including Oracle Spatial and Microsoft SQL Server. Both offer web services for querying and editing features, publishing and caching map tiles, and running processes on spatial data. Both provide tools for building web mapping applications or mobile applications.

The primary differences are in approach. While proprietary solutions use server-client architecture that’s been adapted to accommodate web services, the OpenGeo Suite was built for the web from the ground up and encompasses best practices from the IT field. Rather than build a kitchen sink product with many highly-specialized features, we focus on developing a powerful base of functionality and providing tools for building applications to solve specific problems. While traditional GIS requires ‘certified’ experts with extensive training to pull data into expensive desktop tools and provide derivative data, the OpenGeo Suite exposes similarly powerful functionality on the web in ways that are integrated with the tools that IT professionals use every day.

Slashgeo: How does cloud computing factor into OpenGeo’s plans for the future?

Rolando: Many of our customers already use our software in the cloud and we offer support for those who wish to deploy OpenGeo Suite on Amazon Web Services (AWS). As cloud computing steadily gains acceptance, we will continue to ensure that our products are reliable and scalable. We’re keen to expand these offerings so stay tuned and we’ll make sure to keep you updated on what we expect to do in the future.

Slashgeo: What major trends in the geospatial technology arena do you see developing in the next 5 years, and how will those trends impact OpenGeo?

Rolando: Much like how source code is managed with distributed version control, we anticipate a future where spatial data will live in a collaborative infrastructure that is able to track data’s origin and evolution. Although spatial data is really just one aspect of the greater information technology landscape for any given enterprise, it has traditionally been siloed and forced through specialized workflows. As with other types of ‘big data’, we foresee increased difficulty storing, managing, and maintaining spatial data across enterprises. Thanks in large part to the reactions to geospatial crowd-sourcing efforts like OpenStreetMap and Ushahidi, we see a significant shift in how geospatial data is conceived of, stored, and distributed.

Adopting the distributed version control model pioneered with source code will play a critical role in alleviating the difficulties that have historically plagued users of geospatial data. A distributed version control model can better address such problems as collaborating between users or organizations, maintaining authoritative data, and enabling offline, low-bandwidth, or intermittent connectivity. Just as access to source code enables a developer to change software by adding to or changing its functionality and appearance, access to underlying geospatial data enables cartographers and analysts to fix mistakes, conduct analysis and modeling, and update datasets. We foresee true collaboration around geospatial information having profound implications for users of geospatial data and have begun investing in solutions to support them.

Slashgeo: Is OpenGeo an example of a successful business model built around open source software? If so, what can other organizations learn from this business model?

Rolando: Given how much we’ve grown in the last several years we believe that a business built around open source software can not only succeed, but thrive. The appetite for open source software is growing; companies like RedHat and JBoss have proven that an open source development model does not inhibit growth, but can often enable it.

In a recent presentation at the Texas GIS forum, Paul Ramsey delivered a compelling introduction to open source and why it’s being adopted faster than ever. Among the many takeaways was the simple fact that startups love open source. Why? Because startups cannot afford artificial limits on their growth. While the cost of computing hardware falls every year, the cost of proprietary software licenses does not. If you’re using software licensed per CPU or core, the primary driver of scaling cost is software cost, and that math does not benefit the consumer. Larger enterprises are being strangled by the immense license costs they are being forced to pay year-over-year. Today we’re all expected to do more with less. With open source functionality meeting or exceeding proprietary solutions, license costs are quickly being targeted as an obvious way to cut costs.

While open source software lacks explicit license costs, all software has maintenance, operating and other related costs.  Unsupported open source software shifts these costs to the end user, which isn’t an issue if the end user or their enterprise has expertise in the relevant software and is willing to pay for support using staff time.  Commercial open source provides the option to save time and reduce direct labor costs by outsourcing maintenance and support to experts. OpenGeo steps in when enterprises lack the time, resources, or internal expertise to maintain open source software. OpenGeo’s mission is to lower costs while continually enhancing the functionality of open source, and our customers value that highly. We expand on these idea in our white paper, “The Value of the OpenGeo Suite”, which outlines our model and why it’s beneficial to all parties involved.


We appreciate the participation of OpenGeo, and of Rolando, in this interview. We hope you enjoyed reading it.

Read More »

Rasdaman: Geospatial Raster Data Manager

I had to investigate OGC's WCS standard and in the process I learned about Rasdaman, a geospatial radar data manager software which is apparently the only software that currently support WCS 2.0 both as a server and client. Rasdaman exists both in a commercial 'rasdaman enterprise' version and as open source with the 'rasdaman community' version. We never really mentioned rasdaman before.

The rasdaman community introduction: "Rasdaman extends standard relational database systems with the ability to store and retrieve multi-dimensional raster data ( arrays) of unlimited size through an  SQL-style query language. On such sensor, image, or statistics data appearing, e.g., in earth, space, and life science applications rasdaman allows to quickly set up array-intensive services which are distinguished by their flexibility, speed, and scalability.

Rasdaman is brought to you by the guys writing the geo raster standards, including  OGC WCS and  WCPS, the OGC raster query language. The petascope component of rasdaman provides service interfaces based on the  OGC  WCS,  WCPS,  WCS-T, and  WPS. For several of these, rasdaman will be reference implementation. Since April, rasdaman is available on the  OSGeo Live DVD. Rasdaman embeds itself smoothly into  PostgreSQL; further, a  GDAL rasdaman driver is available, and likewise a  MapServer integration (beta). A  PostGIS query language integration is under work, see our planning. EarthLook is a demonstration site showcasing rasdaman in a variety of 1-D to 4-D geo use cases."
Read More »

pycsw 1.4.0 released

The pycsw team announces the release of pycsw 1.4.0.
The 1.4.0 release brings numerous features, enhancements and fixes to the codebase, including:
 * WSGI server support
 * harvesting support for WFS, WCS, WPS, and other CSW endpoints
 * support for Open Data Catalog integration
 * enhanced support for GeoNode 2.0 (GeoNode development branch)
 * support for distutils setup/install, which enables pycsw to be installed as a library
 * support for PyPi
 * support for displaying counts for GetDomain requests based on queryable properties
 * support for requestId request parameter
 * fix GetRecords sortby parameter support for HTTP GET
 * support for W3C XLink 1.1 migration
 * support for Debian and Ubuntu packaging
 * support for sorting GetRecords requests by geometry area
 * support for PostGIS enabled PostgreSQL
This release also marks our migration to GitHub for source code management, issue tracking and wiki.
The full list of enhancements and bug fixes is available at https://github.com/geopython/pycsw/issues?milestone=2&page=1&state=closed
pycsw is an OGC CSW server implementation written in Python.  pycsw implements clause 10 (HTTP protocol binding (Catalogue Services for 
the Web, CSW)) of the OpenGIS Catalogue Service Implementation Specification, version 2.0.2.
pycsw allows for the publishing and discovery of geospatial metadata.  Existing repositories of geospatial metadata can be exposed via  OGC:CSW 
2.0.2.  pycsw is Open Source, released under an MIT license, and runs on all major platforms (Windows, Linux, Mac OS X).
Source and binary downloads:
The source code is available at:
Testers and developers are welcome.
The pycsw developer team.
Read More »

Batch Geonews: Shapefiles in Bing Maps, 80% of Data is Not Spatial?, In-Location Alliance, ArcGIS for AutoCAD 300, and much more

This is my tentative to catch up the geonews since my mid-August holidays. Here they are!

On the open source / open data front:

  • UDig 1.3.2 has been released with several new features and supports Axios spatial editing tools again
  • Since the USGS provides the Landsat archive, but this entry mentions that a substantial part of the Landsat archive is available on the fast and reliable public Google Earth Engine cloud storage

On the Esri front:

  • The free plugin ArcGIS for AutoCAD version 300 is now available
  • There's now an ArcGIS Runtime for iOS for ArcGIS WebMaps

On the Google front:

  • Google made a few Google Maps announcements, including voice guided directions in India, Map Maker in New Zealand and new Street View in 150 university campuses
  • In another entry, Google offers a roundup of their August Google Maps related news, most news we already shared with our users
  • Nothing surprising, new imagery released on September 1

On the Microsoft front:

  • Microsoft shares an entry on overlaying Esri shapefiles in BIng Maps
  • Microsoft's Global Ortho Project is complete for the United States, meaning there's high resolution 30cm imagery everywhere in the country
  • There's a new Bing Get Me There App for iOS for London, UK
  • An entry on Bing Maps V7 AJAX Highlights

In the everything else category:

  • James shares a must-read short entry named '80% of Data Is Not Spatial So Stop Claiming It Is', read the comments for insights
  • Here's a pertinent entry related to a UN paper, Criticism - Future Trends in Geospatial Information Management: The Five to Ten Year Vision
  • Here's an update on the OGC standards and the semantic web (aka Linked Data)
  • APB informs us that 22 companies formed the In-Location Alliance to Enhance Indoor Positioning
  • O'Reilly links to an article on Yelp Checkins to Measure Geopositioning Accuracy Across Phones
  • Slashdot discuss the Location Privacy Act Approved By California Legislature
  • Other stories at Slashdot, The Rapid Rise of License Plate Readers and UK License Plate Cameras Have "Gaps In Coverage"
  • Big numbers, APB indicates that the GIS market will soon reach between 3.7 - 10.6 Billions, depending on who you ask

In the maps category:

  • On APoD, there's a pretty interesting map of hurricane and tropical storms paths (screenshot below)
  • An interesting map of the Global Decline in Religiosity
  • Some London Olympics maps: The politics of London Olympic medal counts

Read More »

GeoServer 2.2-RC3 released

The GeoServer team is happy to announce the release of GeoServer 2.2-RC3.The release is available for download from:

This release comes with assorted bug fixes and small improvements, and aims to be the latest RC before the final release. Notable changes:
  • improvements in the security subsystem upgrade from the 2.1.x series
  • bug fixes and improvements in the control-flow module (you won’t be wondering anymore if it’s properly installed, or not)
  • avoid deadlocks on some WFS transactions
The entire change logfor the 2.2-RC3 release is available in the issue tracker:
A very special thanks to all those who contributed bug fixes and improvementsto this release.
–The GeoServer Team
Read More »