search

openaddresses / machine

Scripts for running OpenAddresses on a complete data set and publishing the results.
http://results.openaddresses.io/
ISC License
97 stars 36 forks source link

Support multiple geoid per source #506

Open nvkelso opened 7 years ago

nvkelso commented 7 years ago

Some of our sources cover multiple geographic areas (most cover just one). We should support multiple geoids.

Currently we can specify a GeoJSON polygon geometry so the result choropleth map looks right, but then that causes problems with spreadsheets @iandees maintains and other geoid based lookups.

Two examples:

  1. Detroit area via https://github.com/openaddresses/openaddresses/pull/2295
    • Where this one source covers the following areas:
    • OpenData/Buildings_Detroit (MapServer) – this is actually a city inside Wayne county
    • OpenData/Buildings_Livingston (MapServer) 26093
    • OpenData/Buildings_Macomb (MapServer) 26099
    • OpenData/Buildings_Monroe (MapServer) 26115
    • OpenData/Buildings_Oakland (MapServer) 26125
    • OpenData/Buildings_StClair (MapServer) 26147
    • OpenData/Buildings_Washtenaw (MapServer) 26161
    • OpenData/Buildings_Wayne (MapServer) 26163 – this source is for the parts outside of Detroit city, but collectively both form the geoid of 26163
  2. Oklahoma counties
    • us/ok/acog-counties.json
nvkelso commented 7 years ago

Other examples:

migurski commented 7 years ago

Since Detroit is a city inside Wayne county, the multiple GEOID solution may not exactly fit here. What about supporting an array of coverages instead? The Michigan source above might look like:

{
  "coverage": [
    { "geometry": {"type": "Polygon", … } },
    { "US Census": {"geoid": "26093"} },
    { "US Census": {"geoid": "26099"} },
    …
  ],
  …
nvkelso commented 7 years ago

Yeah, that works for me!

On Wed, Dec 28, 2016 at 2:23 PM, migurski notifications@github.com wrote:

Since Detroit is a city inside Wayne county, the multiple GEOID solution may not exactly fit here. What about supporting an array of coverages instead? The Michigan source above might look like:

{ "coverage": [ { "geometry": {"type": "Polygon", … } }, { "US Census": {"geoid": "26093"} }, { "US Census": {"geoid": "26099"} }, … ], …

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/openaddresses/machine/issues/506#issuecomment-269550781, or mute the thread https://github.com/notifications/unsubscribe-auth/AA0EO4X6CIrr-cl3tQHRT8YMqLwowW8Pks5rMuFjgaJpZM4LXJif .