<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: whosonfirst</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/whosonfirst.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2024-08-01T23:14:49+00:00</updated><author><name>Simon Willison</name></author><entry><title>Towards Standardizing Place</title><link href="https://simonwillison.net/2024/Aug/1/towards-standardizing-place/#atom-tag" rel="alternate"/><published>2024-08-01T23:14:49+00:00</published><updated>2024-08-01T23:14:49+00:00</updated><id>https://simonwillison.net/2024/Aug/1/towards-standardizing-place/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://www.dbreunig.com/2024/07/31/towards-standardizing-place.html"&gt;Towards Standardizing Place&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Overture Maps &lt;a href="https://overturemaps.org/overture-maps-foundation-releases-general-availability-of-its-open-maps-datasets/"&gt;announced General Availability of its global maps datasets&lt;/a&gt; last week, covering places, buildings, divisions, and base layers.&lt;/p&gt;
&lt;p&gt;Drew Breunig demonstrates how this can be accessed using both the &lt;a href="https://explore.overturemaps.org/#13.1/37.46975/-122.44309"&gt;Overture Explorer tool&lt;/a&gt; and DuckDB, and talks about Overture's GERS IDs - reminiscent of &lt;a href="https://whosonfirst.org/"&gt;Who's On First&lt;/a&gt; IDs - which provide stable IDs for all kinds of geographic places.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/geospatial"&gt;geospatial&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/whosonfirst"&gt;whosonfirst&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/drew-breunig"&gt;drew-breunig&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/overture"&gt;overture&lt;/a&gt;&lt;/p&gt;



</summary><category term="geospatial"/><category term="whosonfirst"/><category term="drew-breunig"/><category term="overture"/></entry><entry><title>How I made a Who's On First subset database</title><link href="https://simonwillison.net/2018/Feb/3/whosonfirst/#atom-tag" rel="alternate"/><published>2018-02-03T05:25:25+00:00</published><updated>2018-02-03T05:25:25+00:00</updated><id>https://simonwillison.net/2018/Feb/3/whosonfirst/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://gist.github.com/simonw/425ede4e8453b89aef00e095dee4f3d3"&gt;How I made a Who&amp;#x27;s On First subset database&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Inspired by Paul Ford on Twitter, I tried out a new trick with SQLite: connect to a database containing JSON, attach a brand new empty database file using “attach database”, then populate it using INSERT INTO ... SELECT plus the json_extract() function to extract out a subset of the JSON properties into a new table in the new database.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/json"&gt;json&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/paul-ford"&gt;paul-ford&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/sqlite"&gt;sqlite&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/whosonfirst"&gt;whosonfirst&lt;/a&gt;&lt;/p&gt;



</summary><category term="json"/><category term="paul-ford"/><category term="sqlite"/><category term="whosonfirst"/></entry><entry><title>Feature request: a batch version of mapzen.places.getHierarchiesByLatLon</title><link href="https://simonwillison.net/2017/Oct/4/whosonfirst/#atom-tag" rel="alternate"/><published>2017-10-04T23:51:20+00:00</published><updated>2017-10-04T23:51:20+00:00</updated><id>https://simonwillison.net/2017/Oct/4/whosonfirst/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="https://github.com/whosonfirst/whosonfirst-www-api/issues/99"&gt;Feature request: a batch version of mapzen.places.getHierarchiesByLatLon&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
I’ve been having a lot of fun filing issues against various Mapzen / Who’s On First repositories recently—mainly because the team there are incredibly responsive to suggestions and feature requests. Here’s a fun thread where Aaron Straup Cope and myself have been bouncing around some ideas around batch API design.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/aaron-straup-cope"&gt;aaron-straup-cope&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/geospatial"&gt;geospatial&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/mapzen"&gt;mapzen&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/whosonfirst"&gt;whosonfirst&lt;/a&gt;&lt;/p&gt;



</summary><category term="aaron-straup-cope"/><category term="geospatial"/><category term="mapzen"/><category term="whosonfirst"/></entry></feed>