People are misinterpreting the 0 in the tribal_perc fields as 0 because, well they say 0

[KameronKerger]

Describe the bug When people use the CEJST data, there is one particular issue with the shapefile but the issue persists more broadly, they are interpreting the 0 in the tribal_perc columns as 0 because the field has a 0. This is actually meant to represent less than 1%. Actual 0 is a blank field. This created some confusion and resulted in some errors when people upload it into other platforms, particularly Esri's Living Atlas. People that use that version will have inaccuracies in their analysis.

We may need a spike to figure out the best path forward:

1. We communicate this somewhere?
2. We update the data (I think this is the way it is because we can't easily represent less than 1% in the field

It also looks like the fields are not consistent. This is something that we need to fix regardless of the outcome of the above.

To Reproduce Steps to reproduce the behavior:

1. Go to 'Shapefile or spreadsheets'
2. Scroll over to 'one of the two columns that have percentage of tract that is Federally Recognized Tribal land'
3. See error

Expected behavior Unclear.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

[KameronKerger]

needs discussion