13 March 2017

  • We’ve added postalcodes to the Who’s on First import process and enabled the postalcode-only query type, so users can now find postalcodes directly! 90210 anyone?
  • Dependencies, like San Jose, PRI, should now have the proper alpha3 ISO codes of their own in the country abbreviation (country_a) properties, instead of alpha2 of the parent country as it did previously.
  • Washington DC wasn’t getting a region abbreviation at all for a while, but that’s water under the Arlington Memorial Bridge now!

Warning: We are having some technical difficulties with the polylines data generated from the OSM
road network. This data is used to populate our street index and interpolation service. Both features will continue working as before, but data will be stale until a fix is implemented.
We will be using the last known good version, which was built on February 27th, 2017.
We will definitely keep everyone posted as soon as an updated working version is available. Sorry for any
inconvenience this may have caused.

6 February 2017

We bring you another data update this week, but don’t worry, we’re busy working on cool new features and improvements. If you’re curious what those might be, come read all about them here!

1 February 2017

This release is just a data refresh since it’s hard to keep up with the leaps and bounds that openaddresses is growing by!

27 January 2017

Thanks to some wild activity in the openaddresses project, this is the first Mapzen Search build with over 400 million documents!

We are excited to see open data continue to grow and improve and looking forward to the big half billion milestone. :)

New features

Bug fixes

  • We’ve fixed a bug where structured queries would always return ‘fallback’ as the ‘match_type’.

17 January 2017

For our second release of the year we bring the first new batch of street data for our polylines dataset (derived from OSM) that we introduced late last year. We’ll now be updating that data weekly like everything else!

New features

  • The /v1/structured endpoint now supports the venue parameter, which allows for searching for venues with a particular name.
  • We’ve improved result balance when using focus.point in the autocomplete endpoint. In particular, searching for cities far away from the focus point should work much better. More improvements to focus.point are planned for the near future.

5 January 2017

Our first release of 2017 is here! Due to some build issues, this is the first update of data since mid-November. We’re happy to be back and have improved our build validation along the way.

28 December 2016

New features

  • Searches for St Louis, MO and Saint Louis, MO now return the same thing (the same goes for towns starting with Mount/Mt and Fort/Ft)
  • Structured geocoding no longer fails horribly when the address parameter consists of only a house number

05 December 2016

This week includes only code changes, no data updates. Our production build failed do to an error reading whosonfirst data. We’ll either kick off a new build for release later this week, or resume data updates with our usual cadence next week.

New features

  • We’ve released what was previously referred to as component geocoding in the new structured geocoding endpoint! It lives at /v1/search/structured
  • We fixed a bug where specifying the same parameter twice (eg /v1/search?text=paris&sources=geonames&sources=gn) would cause a 500 error. It now returns a helpful 400 error message that includes which parameter is duplicated, so that the request can be fixed.
  • Other errors that should have been 500 errors were being returned with status code 400. Fixing this will allow us to more quickly catch any 500 errors that happen in the future.

18 November 2016

  • We’ve just released beta support for component geocoding so instead of passing in a single input to the /v1/search endpoint, the parts of an address can be sent to /v1/beta/component! An example of this is address=201+Spear+St&locality=San+Francisco&region=CA. We haven’t officially named this geocoding type yet, so if you have a naming suggestion, please weigh in here! Our basic design doc for using this new beta feature is here, please check it out. We’re still working out the final implementation (why it’s currently deployed to our /v1/beta test bed) so check it out and don’t hesitate to raise any issues you might encounter. Check out the acceptance tests for some more examples.
  • We’re enabling support for more response scenarios from libpostal! This release we’re adding support for city+country, so requests for Paris, France and Reykjavík, Iceland are a lot cleaner.
  • Speaking of Reykjavík, Iceland, support for inputs containing diacritics has improved. Now whether the input is Reykjavík, Iceland or Reykjavik, Iceland, results should be the same.
  • Whether your input contains a 2- or 3-character ISO country code (FRA vs FR), we’ll find it!

24 October 2016

10 October 2016

  • libpostal, the super-sophisticated address parser, has been integrated for more accurate analysis of inputs at /v1/search.
  • Street names containing post-directionals (e.g. - 186 Tuskegee St SE Atlanta GA -> 186 Tuskegee St SouthEast Atlanta GA) are now treated the same as their pre-directional brethren.
  • 10/10, would release again - geocoding fallback rules that favor traditional geocoding behavior instead of search engine behavior

19 September 2016

Another data-only release. Stay tuned for next week!

12 September 2016

  • Get excited for the addition of ✨ STREETS ✨! That’s right, with this release Mapzen Search gets a brand new street layer, which contains OSM street centroids. With this addition, if we can’t find the exact address you’re looking for we’ll return the street record. Stay tuned for an in-depth blog post in the next few days. 👏

7 September 2016

22 August 2016

No changes in functionality at all, just the freshest data! We did clean up some tests and do other work only visible to developers and those who run their own Pelias instance, but nothing major.

Stay tuned for next week’s release where we already have some nice changes queued up.

18 August 2016

  • After much feedback we’ve added the boundary.country parameter for autocomplete! It works just like the one on the search endpoint.
  • To help make Leaflet maps display results better, we now use use the lbl:bbox property on Who’s on First records. This is useful for places like San Francisco where the mathematical bounding box is bigger than people expect.
  • The API was incorrectly warning against using the boundary.circle parameter. Now it doesn’t complain!
  • We’ve added a new /v1/nearby endpoint that is currently in early alpha! There’s no documentation, probably some bugs, and any part of the interface is still subject to change.
  • Finally, we’re now running Node.js 4 in production, rather than Node.js 0.12. For those running their own Pelias instance, be aware that we’ll be dropping support for Node.js 0.12 in September. At first, things may work on Node.js 0.12, but we’re very excited to finally start using ES2016, so that won’t last too long.

8 August 2016

Incremental release resolving the final outstanding tasks in the Elasticsearch 2 upgrade.

We have registered a new website http://pelias.io which has information about the milstones we have planned for the current quarter.

  • Elasticsearch 2+ does not support co-ordinate wrapping as it did prior to the 2 release. Some front-ends allow users to ‘wrap’ around the globe. Floats outside of the normal -90/+90 -180/+180 geographic coordinate ranges cause Elasticsearch to error. We added a function to the API which unwraps these coordinates; providing better compatibility with these tools.
  • We added borough as a possible layer for Geonames
  • Since the beginning of the project the Elasticsearch _index name has always been hard-coded as ‘pelias’, the index names configurable PRs allow this behaviour to be adjusted in your individual pelias config files.
  • We removed the focus.viewport API which was undocumented and never used outside of test suites.

2 August 2016

Another bigger than usual release, we had some ops related challenges to resolve after the update to Elasticsearch 2, as well as some data issues, but we also have some great improvements in store!

We also have two known issues in this build:
* Some OpenAddresses records for the statewide data in Massachusetts, USA are incorrect. This is because of an issue when changing data sources that will be resolved in the next OpenAddresses build
* Geonames localadmin records, like the City of New York will have extra components in the label (in this case, “Brooklyn, New York”). The fix for this is merged but was accidentally omitted from this build. Look forward to it next week!

07 July 2016

  • Big news: We’ve finally upgraded to Elasticsearch 2.3! This brings improved performance and more importantly sets us up for lots of improvements from the new features of Elasticsearch 2. Elasticsearch 1.7 is no longer supported.
  • As part of the Elasticsearch 2 upgrade we’ve also improved a few edge cases for searching for numeric values, and with single character tokens. You can read more in the Github issue for the upgrade.
  • We’ve also fixed some lingering issues where a few places in Denmark were listed as being part of Sweden. This was due to the same data bug as mentioned in our recent blog post.
  • The OpenAddresses importer now has better whitespace cleanup, so there won’t be any extra spaces in street names.
  • We recently added data to new layers in Geonames, but the API didn’t know about it, and prevented you from searching for them. We fixed it.

13 June 2016

  • Who’s on First importer: records now use the label centroid if it’s present. The previous behavior was to always use the center of the record’s bounding box. In cases like San Francisco, this caused the record to not show up where people expect!
  • Openstreetmap importer: A bug in config parameter handling that caused admin lookup to be disabled when it shouldn’t was fixed. Thanks to @dylanFrese for helping us catch this tricky one.

26 May 2016

  • We did it… we removed an Elasticsearch analyzer that was presumptuously assuming all queries were in English! The k-stemming analysis would do strange things like turn Daly into Dale, so finding “Daly City” was a challange. Well, no more! Word of warning, in /search we are now less forgiving when someone uses a plural version of a word where the real name is singular.

23 May 2016

  • All the extra 0’s have been eradicated in addresses coming from OpenAddresses. You should not see any house numbers that reduce to 0 or any leading 0’s in house numbers.
  • Added the mysteriously missing source_id property to response features. This property represents the original id at the source, if one existed, like in OSM and WOF. Where it didn’t we made one up to help uniquely identify each record.

09 May 2016

  • Cleaned up some invalid address data from our OpenAddresses import by removing anything with words like NULL, UNDEFINED, and UNAVAILABLE.
  • Improved error reporting in the API so users can decipher what went wrong much easier. More specifically, there are errors that Elasticsearch reports and we propogate up to the API response.

29 April 2016

  • A big improvements to autocomplete results coming from numerous bug fixes and improvements! More details can be found in the pull requests: pelias/schema#127 and pelias/api#526. Some highlights include:
  • Single digit housenumbers like 8 Main St can be found more easily
  • Support for searching for the street name before the house number, as is common in many European countries, is improved.
  • Searches that end in common words no longer return no results. These were being treated as stopwords internally in Elasticsearch. Now queries such as Moscone West will work better
  • Remove OpenAddresses records with 0 housenumbers in US/CA

18 April 2016

  • Address parsing now works without spaces after commas. This was our bad. Feel free to leave those spaces out as long as you provide commas to delimit admin parts.
  • Further streamlining of labels. You can expect the labels to a have more consistent and minimal feel. If the results are coming from New York, expect boroughs such as Manhattan, Brooklyn, Queens, etc. to be part of the label. You’re welcome New Yorkers! :heart:
  • Fixed a bug where specifying layers=macrocounty would fail due to a typo in the API code. You can see how easy it is to mistype macrocounty and not notice that macrocountry is incorrect. #onlyhuman

08 April 2016

This release marks the official integration of the Mapzen Who's on First data set into Mapzen Search. This data is replacing Quattroshapes across the entire service. Any forward usage or references to Quattroshapes will be replaced with WhosOnFirst. This substitution allows us to fix long-standing encoding issues in administrative hierarchy place-names. We’ve also added a bounding box for individual features in the results, not only the all-encompassing bounding box at the top level of the geojson results. Also, the all-encompassing bounding box will extend to include the bounding boxes of all the features in the results, not only their centroids.
Another major improvement that many have been waiting for is the addition of more filters for the /autocomplete endpoint. Users can now ask /autocomplete to filter by layers and sources, as documented here.
See the detailed list of changes below for more specifics.

  • Switched from Quattroshapes to WhosOnFirst as the canonical source for administrative hierarchies and corresponding geometries.
  • No longer importing Quattroshapes data since WhosOnFirst contains all those records and more. Going forward, any use of quattroshapes or qs in queries will resolve to whosonfirst or wof automatically.
  • New bbox property has been added to individual results, for which geometry was available in the original source. This does not affect POI and address data.
  • Drastic improvements have been made to the label generation logic.
  • id and gid format has changed to make the ids more unique.
  • New id format resolves previously outstanding bugs related to geonames ids being invalid for lookup via the /place endpoint.
  • Additional place-types have been introduced, such as macroregion, macrocounty, and borough.
  • gid values have been added for each parent in the admin hierarchies of results.
  • /autocomplete now allows filtering by sources and layers.
  • Fixed a bug that allowed /autocomplete to accept the size parameter. The default and only size of /autocomplete results is now 10, as originally intended.