Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deer encoding challenges #39

Open
3 of 8 tasks
waldoj opened this issue Jul 10, 2014 · 3 comments
Open
3 of 8 tasks

Deer encoding challenges #39

waldoj opened this issue Jul 10, 2014 · 3 comments

Comments

@waldoj
Copy link
Member

waldoj commented Jul 10, 2014

These are a bunch of issues that will need to be broken up into a series of tickets—I'm just putting them here for the time being.

  • How do we indicate bag limits?
  • How do we indicate restrictions based on sex?
  • How do we indicate restrictions based on antlers?
  • Can we use a shorthand for “west of the Blue Ridge” and “west of the Blue Ridge”? Re-specifying this list over and over again seems wasteful. OTOH, it’s just copy-and-paste, so maybe this isn’t really a problem.
  • How do we indicate “state forest lands,” “state park lands,” “department-owned lands,” “public access lands,” and “national forests”?
  • How do we indicate “private lands”?
  • How do we mark “Earn-a-Buck” counties?
  • How do we indicate when all towns and cities within a county are included? (e.g., " In the counties (including the cities and towns within) of Floyd, Franklin, Henry, and Patrick.")

Note that we don’t have to do all of these things. It’s totally reasonable not to atomize all of this. But we'll need to figure out which of these get done.

waldoj added a commit that referenced this issue Aug 13, 2014
Per #39. This raised more problems than it solved, but it’s a start.
@waldoj
Copy link
Member Author

waldoj commented Aug 14, 2014

I'm dubious that we need to atomize bag limits or Earn-a-Buck counties. That seems reasonable to include in textual content.

@waldoj
Copy link
Member Author

waldoj commented Aug 14, 2014

I think the easiest way to indicate "state forest lands," "private lands," etc. is—when they are subsets of counties—to simply include that as a restriction element, e.g.:

"Montgomery": {
    "gnis_id": 1674630,
    "fips_code": "TK",
    "restriction": "state forest lands"
}

@waldoj waldoj added the hunting label Sep 5, 2014
@waldoj
Copy link
Member Author

waldoj commented Oct 28, 2014

West of the Blue Ridge:

"Alleghany": {
    "gnis_id": 1673675,
    "fips_code": "99005"
},
"Augusta": {
    "gnis_id": 1480098,
    "fips_code": "99015"
},
"Bath": {
    "gnis_id": 1673638,
    "fips_code": "99017"
},
"Bland": {
    "gnis_id": 1494613,
    "fips_code": "99021"
},
"Botetourt": {
    "gnis_id": 1674418,
    "fips_code": "99023"
},
"Bristol": {
    "gnis_id": 1498416,
    "fips_code": "09816"
},
"Buchanan": {
    "gnis_id": 1497431,
    "fips_code": "99027"
},
"Carroll": {
    "gnis_id": 1480108,
    "fips_code": "99035"
},
"Clarke": {
    "gnis_id": 1690562,
    "fips_code": "99043"
},
"Clifton Forge": {
    "gnis_id": 1492780,
    "fips_code": "17440"
},
"Covington": {
    "gnis_id": 1789069,
    "fips_code": "19728"
},
"Craig": {
    "gnis_id": 1673664,
    "fips_code": "99045"
},
"Dickenson": {
    "gnis_id": 1497376,
    "fips_code": "99051"
},
"Floyd": {
    "gnis_id": 1494354,
    "fips_code": "99063"
},
"Frederick": {
    "gnis_id": 1480124,
    "fips_code": "99069"
},
"Galax": {
    "gnis_id": 1498426,
    "fips_code": "30208"
},
"Giles": {
    "gnis_id": 1494551,
    "fips_code": "99071"
},
"Grayson": {
    "gnis_id": 1501196,
    "fips_code": "99077"
},
"Harrisonburg": {
    "gnis_id": 1498563,
    "fips_code": "35624"
},
"Highland": {
    "gnis_id": 1673774,
    "fips_code": "99091"
},
"Lee": {
    "gnis_id": 1496538,
    "fips_code": "99105"
},
"Lexington": {
    "gnis_id": 1789071,
    "fips_code": "45512"
},
"Montgomery": {
    "gnis_id": 1674630,
    "fips_code": "99121"
},
"Norton": {
    "gnis_id": 1498434,
    "fips_code": "57688"
},
"Page": {
    "gnis_id": 1500440,
    "fips_code": "99139"
},
"Pulaski": {
    "gnis_id": 1501465,
    "fips_code": "99155"
},
"Radford": {
    "gnis_id": 1498438,
    "fips_code": "65392"
},
"Roanoke": {
    "gnis_id": 1480165,
    "fips_code": "99161"
},
"Roanoke (city)": {
    "gnis_id": "1499971",
    "fips_code": "68000"
},
"Rockbridge": {
    "gnis_id": 1480166,
    "fips_code": "99163"
},
"Rockingham": {
    "gnis_id": 1488970,
    "fips_code": "99165"
},
"Russell": {
    "gnis_id": 1497573,
    "fips_code": "99167"
},
"Salem": {
    "gnis_id": 1789074,
    "fips_code": "70000"
},
"Scott": {
    "gnis_id": 1498172,
    "fips_code": "99169"
},
"Shenandoah": {
    "gnis_id": 1673918,
    "fips_code": "99171"
},
"Smyth": {
    "gnis_id": 1500545,
    "fips_code": "99173"
},
"Staunton": {
    "gnis_id": 1789075,
    "fips_code": "75216"
},
"Tazewell": {
    "gnis_id": 1497748,
    "fips_code": "99185"
},
"Warren": {
    "gnis_id": 1674058,
    "fips_code": "99187"
},
"Washington": {
    "gnis_id": 1498359,
    "fips_code": "99191"
},
"Waynesboro": {
    "gnis_id": 1498443,
    "fips_code": "83680"
},
"Winchester": {
    "gnis_id": 1789077,
    "fips_code": "86720"
},
"Wise": {
    "gnis_id": 1496656,
    "fips_code": "99195"
},
"Wythe": {
    "gnis_id": 1501379,
    "fips_code": "99197"
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant