search

agrc / porter

UGRC tracks the additions, replacements, and deletions of SGID items (in the broadest sense of add, replace, or delete) through issues in this repository.
https://gis.utah.gov/documentation/policy/
MIT License
2 stars 0 forks source link

Add H3 hexes for the state #214

Closed jacobdadams closed 1 year ago

jacobdadams commented 1 year ago

Summary

These are five datasets, one for each H3 hex zoom levels 5-9. They were created using the method described in my blog post. I had to buffer the state boundary to make sure I got all the hexes that cover the state (the h3.polyfill method just searches if the centroid of a hex is within a polygon), so there are some hexes that are outside the state boundary.

The data should be available in

1 Check [x] all the areas where you expect the data to show up.

The data is of high quality

Where is the data source

Choose one.

Action items

  1. Assign a person who should complete the task by replacing name with their github @name.
  2. Check [x] the box when the task is completed and add the date of completion.
  3. ~Strike~ out all items that do not apply.

:robot: Automation validation

  1. Assign yourself or someone to check the item by replacing name with their github @name.
  2. Check [x] the box and add the date of verification 2020/01/01 when the task is verified.
  3. ~Strike~ out all items that do not apply.

Notification

Group Task Assignments

  1. Check [x] the box when you have assigned all the tasks relevant to your group.
steveoh commented 1 year ago

Does everyone agree that this is a layer they want in the SGID?

Looking at our qualifications doc I wonder about this layer being a core and vital gis layer for the state and if it is useful to multiple agencies or organizations' daily activities or decision-making.

gregbunce commented 1 year ago

i agree. I think it's super useful for comparative analysis and having these spatial pieces (the geom) readily available will be a huge time saver and also make the system easier to work with. i think if it's in the sgid, other folks will take advantage of it as well.

i would say if an official source decides to serve it in the future then we point to that layer, but in the meantime, we serve it for ease of use.

that's my opinion. others?

jacobdadams commented 1 year ago

Yeah, what Greg said. It provides a standardized grid that other agencies can use in their analyses. I see it as a functional/foundational layer.

steveoh commented 1 year ago

We'll need to update the proposed names. / in a table name is not a great idea. If we follow the political boundary convention it would be something like h3_hexes_5_to_9.

jacobdadams commented 1 year ago

There are five different layers- 5, 6, 7, 8, and 9.

stdavis commented 1 year ago

It seems like a good fit for the SGID to me as well. Just because it allows for a common standard for analysis across the state.

jacobdadams commented 1 year ago

For sweeper, should I do that before I load into SGID internal or wait until its in there and let the main sweeper check get it?

eneemann commented 1 year ago

You could probably let sweeper get it after loading to internal.

jacobdadams commented 1 year ago

Ok, here's an interesting licensing thought. The H3 system itself is licensed under Apache 2.0 (an open-source, preserve-copyright license). However, the polygons are generated by the H3 system but are not necessarily part of the system or the code (you don't download the polygons, you generate them).

Does this mean the polygons are still under the Apache 2.0 license? Or can we put them under our CC license?

And if it's under Apache, is there anything special we need to do to tell sweeper?

For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

steveoh commented 1 year ago

Does that imply we shouldn't use h3 in the table name?

agrc-conductor commented 1 year ago

conductor results for tasks - 214

check status
@jacobdadams has completed 0 out of 7 tasks :no_entry:
@steveoh has completed 1 out of 4 tasks :no_entry:
@stdavis has completed 0 out of 1 tasks :no_entry:
gregbunce has completed 1 out of 1 tasks :+1:
eneemann commented 1 year ago

And if it's under Apache, is there anything special we need to do to tell sweeper?

We can just add the table name(s) in the Sweeper code to have it skip license checks. That way we can input the proper license and it will be preserved.

steveoh commented 1 year ago

@eneemann or someone, will you create a draft pr referencing this issue as a part of the introduction steps please.

jacobdadams commented 1 year ago

I've got a branch ready for sweeper; @steveoh or @eneemann, can you give me write access to the repo so I can push?

agrc-conductor commented 1 year ago

conductor results for tasks - 214

check status
@jacobdadams has completed 3 out of 9 tasks :no_entry:
@steveoh has completed 1 out of 4 tasks :no_entry:
@stdavis has completed 0 out of 1 tasks :no_entry:
gregbunce has completed 1 out of 1 tasks :+1:
steveoh commented 1 year ago

I've got a branch ready for sweeper; @steveoh or @eneemann, can you give me write access to the repo so I can push?

You should be good to go.

agrc-conductor commented 1 year ago

conductor results for tasks - 214

check status
@jacobdadams has completed 3 out of 9 tasks :no_entry:
@steveoh has completed 1 out of 4 tasks :no_entry:
@stdavis has completed 0 out of 1 tasks :no_entry:
gregbunce has completed 1 out of 1 tasks :+1:
agrc-conductor commented 1 year ago

conductor results for tasks - 214

check status
@jacobdadams has completed 3 out of 10 tasks :no_entry:
@steveoh has completed 1 out of 4 tasks :no_entry:
@stdavis has completed 0 out of 1 tasks :no_entry:
gregbunce has completed 1 out of 1 tasks :+1:
agrc-conductor commented 1 year ago

conductor results for indices.h3_hexes_z5

check status
internal sgid :no_entry:
meta table
- item id :no_entry:
- item name :no_entry:
- geometry type :no_entry:
stewardship :no_entry: Did not find indices.h3_hexes_z5 in the worksheet
agrc-conductor commented 1 year ago

conductor results for tasks - 214

check status
@jacobdadams has completed 3 out of 10 tasks :no_entry:
@steveoh has completed 1 out of 4 tasks :no_entry:
@stdavis has completed 0 out of 1 tasks :no_entry:
gregbunce has completed 1 out of 1 tasks :+1:
agrc-conductor commented 1 year ago

conductor results for indices.h3_hexes_z5

check status
internal sgid :no_entry:
meta table
- item id :no_entry:
- item name :no_entry:
- geometry type :no_entry:
stewardship :no_entry: Did not find indices.h3_hexes_z5 in the worksheet
jacobdadams commented 1 year ago

Ok, sweeper has been updated with the h3 license info, along with some dependency updating. @eneemann, what do we need to do to get that updated on the main sweeper instance?

steveoh commented 1 year ago

I'll update the package in production

agrc-conductor commented 1 year ago

conductor results for tasks - 214

check status
@jacobdadams has completed 8 out of 11 tasks :no_entry:
@steveoh has completed 1 out of 4 tasks :no_entry:
gregbunce has completed 1 out of 1 tasks :+1:
agrc-conductor commented 1 year ago

conductor results for indices.h3_hexes_z5

check status
internal sgid :+1:
meta table
- item id :+1:
- item name :+1:
- geometry type :+1:
open sgid :+1:
open data :+1:
arcgis online :+1:
stewardship
- Website URL :no_entry:
- Endpoint :no_entry:
- Description :+1:
- Data Source :+1:
- Data Type :+1:
jacobdadams commented 1 year ago

Ok, I think I've got all my stuff done. I'm marking Open Data as verified because they work if you link directly to them in open data. They don't show up if you search, but that's the broader Index Group issue and not specifically these layers.

steveoh commented 1 year ago

🌳