The open source lightweight web mapping library Leaflet quickly became very popular in the past year or so, and now there's Leaflet version 0.7 released for us to play with.
From the announcement: "This is a bugfix-heavy release — as Leaflet becomes more and more stable feature-wise, the focus shifts towards stability, usability and API improvements over new features. [...] You can check out the detailed changelog of what’s already done over the recent months for 0.7 (about 90 improvements and bugfixes) [...] There are several big undertakings in refactoring Leaflet that I’d want to switch to immediately after releasing 0.7 — I’ve been holding them off for too long, and they’ll be extremely beneficial for plugin and Leaflet-based API authors." The full list is available in their announcement.
Here's the recent geonews in batch mode, covering a too long timespan once again.
On the open source / open data front:
On the Esri front:
On the Google front:
In the everything-else category:
In the maps category:
From the official page: "CLAVIN (Cartographic Location And Vicinity INdexer) is an award-winning open source software package for document geotagging and geoparsing that employs context-based geographic entity resolution. It extracts location names from unstructured text and resolves them against a gazetteer to produce data-rich geographic entities. CLAVIN does not simply "look up" location names – it uses intelligent heuristics to identify exactly which "Springfield" (for example) was intended by the author, based on the context of the document. CLAVIN also employs fuzzy search to handle incorrectly-spelled location names, and it recognizes alternative names (e.g., "Ivory Coast" and "Côte d'Ivoire") as referring to the same geographic entity. By enriching text documents with structured geo data, CLAVIN enables hierarchical geospatial search and advanced geospatial analytics on unstructured data."
Bloggage update: Over a year ago I QC'd UK Ordnance Survey data for East Anglia, and sent the polyline spike and kickback errors to the Agency, who posted the corrections this year. They noted the errors I reported fell below their own QC criteria, but they invited me to retest their updated dataset. If results were very good in 2010, with 25 errors out of 1777 polygons, they were even better in the 2013 update at only 1 spike out of 1779 polygons! Again, making public data available does help spur on data improvements, and online data validation helps identify errors quickly and efficiently. This makes it easier for the public to communicate, and for data custodians to high-grade their holdings.
Here's the recent Google-related geonews.
From official sources:
From other sources:
(sorry for the recent down time and geonews hiatus, we'll be back to full speed soon!)
Yesterday Mozilla announced their own location services, here's a discussion named Mozilla Location Service: Geolocation Lookups From Cell Towers and WiFi Data.
The slashdot summary: "Mozilla today launched an experimental pilot project called Mozilla Location Service. The organization explains its goal is to provide geolocation lookups based on publicly observable cell tower and WiFi access point information. Mozilla admits that many commercial services already exist in this space, but it wants to provide a public one. The company points out there isn't a single 'large' public service that provides this data, which is becoming increasingly important when building various parts of the mobile ecosystem."
The GeoExt community is proud to announce the release of GeoExt 2.0.0.
Download it at https://github.com/geoext/geoext2/releases/tag/v2.0.0
GeoExt 2.0.0 is the first official GeoExt version that is built atop of OpenLayers 2.13.1 and ExtJS 4.2.1. It is being released 2 weeks after release candidate 1 was published and no serious bugs were discovered.
The newest major version of GeoExt wants to provide mostly the same API you know and love from the 1.x-series. It comes with support for the autoloading-mechanism of ExtJS, support for the single-file build tool of sencha and with exhaustive documentation that is built using the same tools that the mother library ExtJS uses (see http://geoext.github.io/geoext2/docs/ and http://geoext.github.io/geoext2/docs-w-ext/).
This release wouldn't have been possible without the sponsors of the above mentioned sprint. Also we want to thank the companies behind the contributors of GeoExt for supporting GeoExt development in numerous ways and for such a long time.
We invite you all to use GeoExt 2!
Tidbits published a short story named The iPhone’s Positioning Sensors Were Never Good that summarizes the recent findings regarding smartphones accuracy of their positioning sensors, specifically the level, gyroscope, compass and accelerometer.
From the article: "Some were off as much as 20 degrees, and the worst deviation came in three different iPhone 5 units. TechHive also tested the compass of the Android-powered LG G2 smartphone and found that it was the closest to the Suunto, off by only 3 to 4 degrees. [...] In short, despite the proven problems, the iPhone’s positioning sensors still work sufficiently well for the uses that most people demand of them."
HALE is an open source solution that brings interactive visual decision support to schema transformation projects, such as providing INSPIRE-compliant geodata.
To make the start with HALE easier, HALE now offers the possibility to use project templates, e.g. for mapping to the INSPIRE Application Schemas. This saves you steps such as loading the schemas and setting up codelists. You can share your own projects as templates, example, or even as reference mappings online, to let others in your community profit from them:
The Join Retype operation
HALE now offers attribute based joins of different feature classes – to an arbitrary depth.
Export to JSON/GeoJSON
Transformed data can now be exported to JSON or GeoJSON, independently of what kind of schema the data is associated to. Objects are generically encoded as JSON/GeoJSON according to their structure.
Improved support for INSPIRE
HALE now supports the new code list XML format introduced recently by the INSPIRE registry. These code lists are relevant for the latest versions of the Annex II and III Application Schemas. In addition, transformed INSPIRE compliant features can now be saved to GML directly as an INSPIRE SpatialDataSet instead of the deprecated GML FeatureCollection.
To learn more about HALE, visit http://blog.dhpanel.eu.
Bloggage update: More and more free data are available that are quality-controlled and verifiable. Guardian Data Blog's @smfrogers (now at Twitter) was quite sanguine about this: "Comment is free, but facts are sacred". This reflects the geo-industry's credo is "say what you want, but ensure your data's Triple-A rating: available, accurate and auditable."
Guardian Data posted Great Britain's train station data, and they used Google Fusion Tables to post some of the data. I downloaded the data set, mapped it against UK post code data from Doogal UK to place stations at post code centerpoints, and classified it by year and frequency. UK Ordnance Survey County and District data, and NOAA GSHHS coastal outline subset completed the picture. The maps were created on ArcMap for Home Use. then posted on arcgis.com. giscloud.com loader for ArcMap data was then used to post it online here and below, together with USGS SRTM web map service for background.
This is yet another example where posting data and making it publicly available can move forward map making through mashups of various data sources. The key proviso, however, is that data sources are acknowledged all the way. Not only will it allow auditing and referral, but it also allows others to create more of the same according to their particular expertise. Isn't that, after all, what crowdsourcing is all about?