As a community leader, I want to see resources near the location of my community

[meiqimichelle]

Pending: 18F team will get access to basin-based map made in Esri Storymap platform at ONRR and investigate best way to work with that data. cc/ @shawnbot

Possibilities:

• build everything in Esri and iframe or similar into our site
• just use the data and rebuild on our own
• let ONRR team maintain data on their end, and we can access the data through APIs so that data comes straight from the source, but we can use however we like on our end

Considerations:

• 508/accessibility
• responsiveness
• portability

[meiqimichelle]

Update: received open data version of ONRR maps made with MARS data. @shawnbot and @nickbristow to investigate possibilities.

[meiqimichelle]

Brainstormed/organized full scope of questions/content that could go into maps. We have some direction now, and will be mocking up ideas.

[meiqimichelle]

Chatted with @shawnbot @nickbristow on next steps given the scope of content and priorities we're working with. Readout:

• We will continue to focus on our first priority user, the non-specialist interested citizen.
• This means we will focus on providing location-based, community information -- the user should be able to start at a national level and drill down to the area that they're interested in.

Next steps

• [x] @shawnbot to research Mapbox and other solutions for providing a map baselayer of land jurisdiction (need to be able to show what is Federal, state and private land, since so much of our data is only about Federal land)
• [x] @meiqimichelle and @shawnbot to search out Fed/non-Fed shapefiles

Notes on direction after next steps

• Explore how to display Fed/non-Fed land
• Explore how to provide commodity-based contextual info (ie, basins for oil/gas). There will likely be commodity-specific views
• Perhaps future zoom-to-local area functionality
• Will have revenue and production information by commodity by county over time data. Explore how to take advantage of this

[shawnbot]

OK, here's what I've got on Mapbox so far:

1. Plans break down on "map view" boundaries. Every 15 tiles is counted as a map view, and the costs are:
   • $5/month for 50k views (Basic)
   • $49/month for 100k views (Standard)
   • $499/month for 1m views (Premium)
2. Their satellite imagery is gorgeous. This would be a really nice way to emphasize that we're talking about natural resources here, and not (necessarily) political features.

[meiqimichelle]

@shawnbot is the pricing the same to use the satellite imagery? I remember when they were starting to role that out, so beautiful that it is here now! I see that they're marketing it as part of Mapbox Data -- do you know if that's an additional app/fee or something?

[shawnbot]

@meiqimichelle yeah, I'm pretty sure that you can just include satellite imagery as or in one of your styles. For reference:

• Basic: 3 styles
• Standard: 10 styles
• Premium: 30 styles

If we could only do basic then we'll need to consider either:

1. Generating and hosting some overlay tiles on our own, or
2. Rendering all of the overlays as vectors (which we'll need to do if they're going to be interactive)

[shawnbot]

So, the possibility that I'm exploring now is:

1. Prototyping with Mapbox Studio (formerly TileMill)
2. Hosting 1-3 examples on Mapbox for now (so as not to incur the Wrath of DevOps)
3. Self-hosting tiles exported from Mapbox Studio with tilelive or similar

I like the option of self-hosting because we can do stuff like compositing on the fly with tilelive-blend, and we wouldn't need a database: we could mix and match tile sources in different formats and from different places (one in TileJSON, another stored in mbtiles locally, etc.). The only infrastructure that I'd need some help with is actually provisioning servers and configuring caching appropriately.

[meiqimichelle]

Sounds good to me, although I'm not qualified to assess whether Part 3 makes sense -- I trust you! Let's test it :) My request: let's also take really good notes on our decisions as we go along and plan to write blog post at the end about mapping for gov (or similar). I think we'll learn/can teach a lot here.

[nsinai]

+1! I know it takes extra work to take notes and blog about decisions, but a lot of other federal (and non-federal) agencies will learn from it.

[shawnbot]

Thanks for the nudge, @nsinai! @meiqimichelle, I think we should also consider what data we have access to before we get too far down the tools rabbit hole. Should we start listing our data sources here?

[meiqimichelle]

Sure! This is what we have that is already geo-related (I don't know if it is geo'd in a useful way for our map, but I mean that it is related to a geopoint or shape):

Numbers data we have

These might be available over time, not sure

• Revenues by state and commodity
• National and state contributions to GDP by industry (NAICS)
  • Absolute terms and as a percentage of GDP
• National, state and county employment by industry (NAICS)
  • Absolute terms and as a percentage of GDP
• Exports data from census, national and state
  • Absolute terms and as a % of total exports; volumes (% of state exports) and value
• Yearly totals for revenue disbursement to various legislated funds for 2012 and 2013 at a national level (the bubble chart on the site), available as csv or json
• Total royalties by commodity for 10 years (the pie chart on the site)

Numbers data we will shortly have

These are the datasets that ONRR is preparing now. The latest is that the sales value dataset is complete, but is in QA, and there is a meeting on this on Thursday. If it is not releasable on Thursday then I've asked for a dummy dataset with anonymized and fake data.

• revenues by county and commodity over 10 years
• sales value (a semi-proxi for production) by county and commodity over 10 years

Other data we have

• Shapes and background info on oil and gas basins
• Boundaries for Fed versus non-Fed land
• Boundaries for offshore regions and related info (for example, the boundary between state coastal jurisdictions and Federal waters)

Other data we might have

• Location information for projects supported by the land and water conservation act (some offshore revenues go to this)
• Location information for projects supported by the reclamation act
• Location information for projects supported by the historic preservation fund

Might be a few other things I'm forgetting, but this should get us started!

[shawnbot]

This is great, @meiqimichelle! Do you have URLs for any of these? I'm curious because I want to take a look and see how big/complicated the data is, which will help us evaluate a solution. Also, I'm curious to just start throwing stuff into Mapbox Studio and seeing what comes out :)

[meiqimichelle]

@shawnbot I updated my comment above to include URLs as I know them. For the boundary info, those would be through Jason's Esri demo for the basins; through nationalmap.gov or similar for the Fed-non-Fed land, and perhaps also the boundaries for offshore regions. The offshore stuff is also available through the BOEM map portal. Some is already on our current map, too.

[shawnbot]

:+1: thanks @meiqimichelle

[meiqimichelle]

I've worked on some initial content structure in this Google doc. Could help inform what you're playing with on your end.

[shawnbot]

For future reference, last week I started work on some of the maps in the eiti-maps repository.

[meiqimichelle]

Moving some of the discussion that happened in the above-referenced Google doc here. In the doc, we organized content blocks by topics that we think we should answer for users on our site. @shawnbot decided to tackle the following topic first in order to start understanding the available geo-referenced data for the data portal:

Topic: Where is extraction happening?

Questions to answer:

• What is Federal and non-Federal land?
• What are the different types of Federal land?
• How does this interact with natural resources?

Potential design solution: Story map

• Pane 1: [View of entire US with boundaries of Fed and non-Fed land] The United States is made up of many land jurisdictions. Some land is held privately, some in trust for Native American nations, some by states, and some by the Federal government.
• Pane 2: [View of entire US with Fed land split into types (NPS, BLM, etc)] Within the Federal jurisdiction, land is further divided in how it is managed. Natural resource extraction is only permitted on certain types of Federal land, and where revenues from the extraction go changes based on the type of land. (More info on US land management as it pertains to resource extraction)
• Pane 3: [View of entire US with oil and gas basins illuminated] Of course natural resources don’t follow political boundaries. Take oil and gas for example. There are X major basins in the U.S. (can explore hover-for-more-info or similar on basins, we have background and stats on those)
• Pane 4: [Zoom to view of complicated land area] Sometimes the story gets very complex because extraction straddles Federal, State and private land.

@shawnbot has started turning data from ONRR and data surfaced by Deloitte through the contextual narrative research process into web-accessible geo formats in the eiti-maps repository. So far, this includes a Federal lands map:

...and a Tribal areas map:

[meiqimichelle]

Re: Mapbox

We are moving to a data display without tiles. We feel that this might better convey the data, and if we need some background for reference (such as the Fed/non-Fed land above), an image (not tiles) might work better for our usecase.

However, after discussion in 18F, we are moving forward with requesting the purchase of one Mapbox account for 18F prototyping use.

Re: Blogpost

@shawnbot has ideas around maps and data, with EITI as a case, and how we're basically redesigning the entire site around geography, what the implications are, etc. It exists in idea form and has gotten :+1: from 18F comms.

Re: Available data

Work --> #493