<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Sky Bristol on Medium]]></title>
        <description><![CDATA[Stories by Sky Bristol on Medium]]></description>
        <link>https://medium.com/@skybristol?source=rss-b947a36d30f2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*k3RGIK0I1zl5oiop</url>
            <title>Stories by Sky Bristol on Medium</title>
            <link>https://medium.com/@skybristol?source=rss-b947a36d30f2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 12:04:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@skybristol/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Further figuring out camp hosting]]></title>
            <link>https://medium.com/@skybristol/further-figuring-out-camp-hosting-e5954bdc968f?source=rss-b947a36d30f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/e5954bdc968f</guid>
            <category><![CDATA[national-park-service]]></category>
            <category><![CDATA[public-lands]]></category>
            <category><![CDATA[campgrounds]]></category>
            <dc:creator><![CDATA[Sky Bristol]]></dc:creator>
            <pubDate>Mon, 09 Jun 2025 17:32:12 GMT</pubDate>
            <atom:updated>2025-06-09T17:32:12.475Z</atom:updated>
            <content:encoded><![CDATA[<p>Following up on my previous article written with my wife, Katrina, laying out our developing philosophy on camp hosting, this article describes some of the more practical aspects of the job and discusses some technical work I’ve been doing. We’ve now moved down to the South Rim Campground (SRCG) at the Black Canyon of the Gunnison National Park (BLCA) for the summer months. It’s a few thousand feet higher and far cooler here to spend the hot part of the year.</p><figure><img alt="View of the Black Canyon of the Gunnison and Gunnison River" src="https://cdn-images-1.medium.com/max/480/1*ol5NK-SGW6zAX6oHhi9ARg.jpeg" /></figure><p>We love the host site the BLCA folks set up here. It faces east, so we get some lovely sun in the early morning when it’s still quite cool and great shade in the afternoon as things are starting to heat up. We got here in time to see the leaves just starting to come out on the scrub oak, and they’re now filling out nicely. This is a birders paradise right now with over a dozen songbird species making us feel like we’re living in an aviary. They start “screaming for sex” around 04:30 and don’t stop till well after dark. It’s lovely!</p><figure><img alt="View of the Black Canyon of the Gunnison at sunset" src="https://cdn-images-1.medium.com/max/1024/1*x-27ixuoVj7_egL0UCTfCA.jpeg" /></figure><p>There’s a totally different vibe down at this park that is somewhat surprisingly much more laid back. We never felt like things were overly bureaucratic at the Colorado National Monument (COLM), but it’s just a bit more chill here, likely reflecting some of the general attitude in this slightly different part of Colorado.</p><p>There are some other differences too in the way the campground is operated that we’ve found interesting. There are no first come/day of sites at SRCG with all sites available for reservations many months out. Looking out over the summer we are nearly 100% full all the time, and we’ve certainly seen that so far.</p><p>There are 80 total sites in 3 loops here like we had at COLM, but there are 4 sites set aside for discretionary use (we’ve dubbed this the “D loop”) plus the host site, so 75 sites are filled most of the time. These can be for search and rescue cases when someone gets pulled out of the canyon late and needs a place to stay, for special Park Service employee use, or for our discretionary use as hosts. We have a somewhat more straightforward process for late-night arrivals paying their reservation fee the next day just down the road at the entrance station (also their only way out).</p><p>We have major turnover every day plus quite a few guests staying multiple nights. One of the coolest things the team implemented here that we’ve grown to really like is a placard system for arrivals. Having that little physical tag on the sites seems to work really well for guests, and we’ve come to rely on the process of swapping tags as we clean and check sites each day.</p><p>The Fees staff here had been printing the placards from a standard report in “The Hub” (manage.recreation.gov) but then giving them some “sharpie treatment” to make the departure date large enough to read from a distance. Coupled with some other things I’ve been noticing about the rec.gov system, I finally decided to do some technical work to make up for some of the shortcomings. I’ve started a <a href="https://github.com/sky-builds/pyfedcamp">Python project</a> with some core logic for working with the major data dump that can be downloaded as an Excel file. I put in a feature to build custom placards that are mostly like the rec.gov originals but with our own labeling and larger texts where they matter.</p><figure><img alt="Sample custom placard produced by pyFedCamp" src="https://cdn-images-1.medium.com/max/1024/1*5IbgCZu9rQmrE5TTOY0C5Q.png" /></figure><p>Like the standard report, we use the obfuscated information about visitors, but it’s been interesting to see just how many guests actually pay attention to the placards to verify that they are in the right place. Nominally, this is all stuff that rec.gov should really handle officially, along with a whole raft of other issues. But I’ve been posting ideas to their ideas portal since we started this gig, and I have yet to see any action taken on any of the good ideas that staff from across government agencies have shared. If DOGE was actually an effort toward improving government efficiency instead of a not so thinly veiled wrecking ball, they could work on forcing the Booz Allen Hamilton’s of the world to get their shit together.</p><p>To support use, I also built a simple <a href="https://github.com/skybristol/fed-camp-host">web app</a> that provides an interface to upload a downloaded “non-PII” Camping Reservation Detail Report Excel file, produce a custom placards PDF, and build other reports. I’ll keep improving both of these with things like visual identity for other agencies to make them more extensible in case other sites have some of the same needs.</p><p>I’ve also been chatting some with staff here on reporting needs, working toward leveraging the investment made in “outsourcing” campground (and other) fees processing to the recreation.gov system. There’s actually a fair bit of data available as thousands of people are out here recreating and mostly paying the associated fees the government is authorized to collect (and that we’ve somehow allowed BAH to skim). Prior to us coming into the gig here at SRCG, staff and previous hosts had been collecting and reporting very simple stats on the number of sites/night occupied by tents/RVs. That left a lot of things to chance, depending on when and how those observations were being made.</p><p>I’ve built a few features into pyFedCamp so far to aid in creating the kinds of reports folks here at BLCA find most useful. We are considering all reservations that are not voided or cancelled in the monthly stats now, distinguishing between “observed” vs. “not observed” reservations — meaning that a host or staff member checked someone in (observed them or their stuff on site) at some point in their stay. This is likely over reporting to some extent in that we know we have some number of no-shows or reservations that only occupy their sites for some of the reserved overnights. With enough data, we can likely develop a statistical error calculation we can factor in to get more accurate numbers.</p><p>An interesting dynamic for me is exploring where and how the numbers reported are actually used in decision analysis. I’m gathering so far that at least this aspect of NPS operations in the two units we’ve worked is not really a data-driven decision space. In looking into how we might use the reservations data, I noted a dashboard the rec.gov folks have that shows things like monthly stats on occupant overnights, using the total number of occupants in reservations and splitting out “tent” vs. “RV” sites. The basic stat that the BLCA folks want is not occupant overnights but site overnights, still split out by tent and RV. Both of these are potentially interesting, but it really depends on how the information will be used.</p><p>I’ve set up pyFedCamp to report both — occupant overnights and site overnights — using similar logic to distinguish between tent and RV plus factoring in observed vs. not observed reservations.</p><figure><img alt="Example basic occupancy stats report for the month of May 2025" src="https://cdn-images-1.medium.com/max/1024/1*MC-qKyrKzS5bG1XzRkSaqg.png" /><figcaption>Monthly stats for May 2025 showing site and occupant overnights in RV and tent sites, including numbers for sites where an observation was made by staff</figcaption></figure><p>We know there is error in the data from what we’ve observed, but we do make a cursory examination of the reservation data when we check in campers. We specifically look at the listed equipment and the number of occupants, checking to see if things generally line up between what we see at the time of observation and the reservation details. With the exception of vehicle length, which many people seem to “under-estimate,” the reservation data aligns pretty well with on-the-ground reality. We don’t have any capability to modify anything entered by users or report different details without some other system in place and a whole lot more work on our part. We really have to go with the data in the system the government is paying for regardless of its shortcomings.</p><p>There are all kinds of interesting things I can imagine doing with the available data, particularly if coupled with observations and measurements on impacts to the ecosystem and built infrastructure. When a giant tag-axle RV comes in when we have a bunch of rain, impacts to the parking service can be significant.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*apu0V_ikv7rw0TWaeZMsnw.jpeg" /><figcaption>One of the larger RVs in one of the larger sites with electrical hookups after a recent period of heavy rain showing ruts in the parking servcice impacts to built infrastructure in the South Rim Campground at BLCA</figcaption></figure><p>But are those impacts more or less costly than other uses if RV users tend to stay in their rigs and not interact as much with the rest of the site? Does a higher number of occupants lead toward more impacts, what other factors are involved, and how do we measure this? If we can measure impacts from various types of usage, where and how is this information used in decision analysis?</p><p>I have much more to research and learn in this space, and I’ll have to spend some quality time with various agency documents in coming weeks. I found an interesting <a href="https://parkplanning.nps.gov/showFile.cfm?projectID=97629&amp;filename=CBRE%5FCampground%5FTrends%5FReport%5F3%2E16%2E20%2Epdf&amp;sfid=441479">report</a> comissioned by the National Park Service and published in 2019 on campground utilization trends and projections. It used recreation.gov data extensively to characterize campground use. This report was one input into an NPS Facility Investment Strategy published in 2023 that I’ll also spend more time with in coming days. It will be particularly interesting to learn how these types of broad agency-level planning documents end up playing out when it comes to local decision-making at an individual NPS unit.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YQZiUi_mi1YF8uD8i49Isw.png" /><figcaption>The NPS Capital Investment Process as depicted in the 2023 <a href="https://home.nps.gov/subjects/partnerships/upload/2023-NPS-Facility-Investment-Strategy_508_2023-1030.pdf">Facility Investment Strategy</a></figcaption></figure><p>Having spent much of my career studying and building these types of high-level strategies and processes, it is now very interesting to be on the complete opposite end of the spectrum — the lowest of the low volunteer field grunt. We look around while doing our simple job cleaning up campsites, handling mild maintenance chores, and interacting with the public using the facilities, and we see various things starting to build up in the deferred maintenance realm. In both campgrounds, we have noted things like the rutting and erosion of parking surfaces, bear box latches getting work out, charcoal grills rusting out, tent pads needing repair — all issues that will only get worse and cause downstream and more expensive problems over time. We pass these along up the chain, but we’ve gotten to know the maintenance crews and see at least part of the full backlog they are already up against.</p><p>I suspect that quite a number of things that could ideally be part of a regular maintenance process end up festering for years until they “suddenly” become such a large issue that they need to start with an “investment concept” and go through the whole Capital Investment Process to be addressed. One thing that strikes me right out of the gate with the CIP outline is that there is no step here laying out how a completed project enters into a regularized process for long-term sustainable maintenance. What are the ongoing lifecycle costs for the infrastructure or service developed under the CIP and how will those be covered over time such that the investment continues to provide a viable return?</p><p>Most of the hours and minutes we are spending here at the Black Canyon NP this summer are filled with tranquility and wonder at the beauty and serenity of this place. We’re still enjoying meeting interesting people from around the world, trying to be a bright spot in their journey. I spend my time in the news of the day and the political turmoil in our country, judiciously concentrating on those things I might do something about — mostly writing letters to representatives and supporting organizations who are doing good and hard things. In many ways, it’s great to not be a Federal employee anymore, constantly villified by the pundits and other bloviators and subjected to the internal rhetoric from the current toxic administration flooding .gov mailboxes every day.</p><p>But all of that current mess on top of many decades of domestic interior governance playing a distant second fiddle to massively bloated defense spending has me feeling like the Park operations we’ve experienced so far are struggling to keep the wheels on. I suspect that the larger, more popular parks (Yellowstone, Yosemite, etc.) and those near large population centers tend to fare better in the funding arena. “Friends” organizations like the Colorado National Monument Association often provide both community mobilization and direct funding support to partially supplement areas where Government appropriations are not being allocated.</p><p>The bottom line is there’s a cost to accomplishing the mission laid out for National Parks and other public lands. These lands and resources are held in trust by the federal government for the benefit of the nation’s citizens and guests. Many of them are also held in specific trust for the indigenous tribal governments and their citizens that made treaties with the U.S. through the wars and conflicts of the earlier colonial settler times. Those trust responsibilities come with an associated cost of doing business. If we want our government to keep its end of the bargain, we have to provide the resources so that they can do the job. There will always be areas for improvement and as long as the dedicated public servants who act as stewards of the trust are identifying and working toward those improvements, they’re on the right track.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e5954bdc968f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Campground Hosting in National Park Service Campgrounds]]></title>
            <link>https://medium.com/@skybristol/campground-hosting-in-national-park-service-campgrounds-20fbff03f406?source=rss-b947a36d30f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/20fbff03f406</guid>
            <category><![CDATA[u-s-national-park-service]]></category>
            <category><![CDATA[campgrounds]]></category>
            <category><![CDATA[campground-manager]]></category>
            <category><![CDATA[natural-resources]]></category>
            <category><![CDATA[national-parks]]></category>
            <dc:creator><![CDATA[Sky Bristol]]></dc:creator>
            <pubDate>Mon, 19 May 2025 21:35:14 GMT</pubDate>
            <atom:updated>2025-05-19T21:35:14.978Z</atom:updated>
            <content:encoded><![CDATA[<h3>Campground Hosting in National Park Service Campgrounds: A Practical Guide</h3><p><em>Sky Bristol and Katrina Bristol</em></p><h3>Introduction</h3><p>In the fall of 2024, we had an opportunity to try out campground hosting for the Saddlehorn Campground at the Colorado National Monument, only a short drive from our house in Grand Junction. The long-time host needed to take some time away at the end of the busy season, so we volunteered to fill in for about two months. We had long considered the idea of camp hosting, having chatted with many hosts over the years. This gave us an opportunity to test the waters and see whether the job suited us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rm_dJvp5ijPONVAZ" /><figcaption>View from the “Saddlehorn” looking down to the campground on a rare shorts-wearing day in April</figcaption></figure><p>Like any new job, we started with a good deal of trepidation as we learned about what all we would be expected to do. First and foremost, neither one of us had spent much time in what is primarily a customer service role. National Parks are set up to be visited and enjoyed by the public; that is their purpose. As campground hosts, our primary job is to interface with guests coming in to camp, resolving any problems that arise and helping to ensure that they have a pleasant and enjoyable experience. This took a little getting used to as we both consider our life mission to be more about caring for and conserving the natural resources the human guests are here to interact with. Over time, we have come to see our role as mitigating the more disruptive aspects of human behavior through acts of service for both those same humans and the non-human inhabitants of this place.</p><p>The National Park Service expects each of us to work 32 hours a week, which is a significant commitment. It was particularly that way when we first started as Sky was already working 20 hours a week as part of winding down a long career as a scientist in another agency. Katrina was retired from her long-time career in healthcare but also had other regular volunteer commitments to balance. It turned out that we could make it work given the mostly early and late in the day commitments of working the campground, but it is still an almost full time job when taken seriously.</p><p>Now into our second stint where we’ve committed to a full seven months hosting at two different NPS units in Western Colorado, we have learned a lot about what it is really like to do this job. All in all, most days we look at each other when we’re walking or riding our little maintenance cart along the canyon rim, admiring the splendor of Wedding and Monument Canyons in all the different light conditions, morning and night, and say, “this is the greatest job ever!”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ErvqYtusVJwMrQLM" /></figure><p>To help others learn about what we do, this informal “handbook” is intended to help future or prospective hosts learn about the job and its duties. We share both a practical organization to the work as we’ve developed it as well as some specific experiences we’ve had along the way that may help others find their own path.</p><h3>Major Duties of Campground Hosts</h3><p>All told, there are the major services we provide as campground hosts.</p><ol><li>We make ourselves available to guests who have questions or need help in some way.</li><li>We develop an understanding of the rules that campers are expected to abide by and encourage compliance with those rules.</li><li>We do some amount of physical labor to help maintain the campground in good condition, keep it clean, and keep all the facilities in working order.</li><li>Being a good teammate.</li></ol><p>Park managers have long considered the management of visitors and the impacts they cause among their primary responsibilities (Cole, 2021). All three of these duties are vital for creating an environment where visitors can connect with the natural and cultural resources preserved within the parks (Cadwell, 2017; SCHARF, 1942). Campsite management necessitates a nuanced understanding of ecological impact, visitor behavior, and the delicate balance between recreational access and resource preservation (Ferguson et al., 2022). In the following sections, we provide more detail on each of the specific activities and share the philosophy of service we have developed thus far.</p><h3>Customer Experience</h3><p>Customer service is a crucial aspect of the campground host role, where hosts act as the face of the National Park Service, embodying its commitment to positive visitor encounters with our National treasures. Our main goal is to create a welcoming environment, answering questions, providing direction, and offering assistance to ensure a positive visitor experience.</p><p>Partly by our own propensities and through “reading the room,” we’ve developed a philosophy and approach to customer service where we work to make ourselves accessible while not being overly intrusive. We try to be a visible and welcoming presence, especially during arrival times in the late afternoon and evening. But we also don’t want to hover over the campers or be nosy about their activities. So we try to strike a balance between being available and giving people their space. We wear uniform shirts, jackets, and hats to facilitate ready recognition by guests. We get around the campground regularly, whether it be on foot or in our government golf cart.</p><p>If guests stop by to talk or ask questions or stop us as we are going about other business, we endeavor to spend as much time as needed to answer questions thoroughly and resolve problems. We’re fortunate in that we are a small part of a much bigger and well established operation. The Monument has staffing at a Visitor Center just up the road, 9–5 every day, with people well trained to provide visitors with information about the Monument’s natural and cultural history, hiking trails, scenic drives, and other attractions. We have a great maintenance team that handles restroom and facility cleaning, trash collection, and more complex maintenance issues. We have law enforcement rangers who also come through routinely to add to the official presence on site and are available for the occasions where we have a more critical health and safety issue arise. So we can focus on interacting with campers, answering their immediate questions, and helping them get settled in (Sharmin et al., 2020).</p><h3>Rule Compliance</h3><p>Hosts play a key role in ensuring visitors adhere to the park’s rules and regulations, contributing to the preservation of resources and the safety and positive experiences for all guests. This includes addressing noise complaints, enforcing campfire restrictions, and gently reminding visitors of quiet hours or pet policies.</p><p>One of the major areas we check for is through the camper registration system in recreation.gov. The Saddlehorn Campground moved to an all online registration policy the year we started, meaning that all guests are supposed to use the online system to reserve and pay for their campsites in advance. We no longer have an “iron ranger” at the registration kiosk coming into the campground.</p><p>At the same time, the move to using the app or website to reserve sites has not been without challenges. Approximately 98% of guests have no problem with this method, and in many cases, people get their reservations online, have a lovely time camping, and we never really interact with them other than noting their presence. In rare cases, guests are either unable or unwilling to navigate the technology, and they have an option of working with our patient Visitor Center staff to help them book a site. In just a few cases, we have guests unable to navigate the online system, arrive without a reservation, and have no ability to use a credit card or phone to complete the transaction. We provide them with a pay envelope and instruct them to either pay at the Visitor Center in the morning or provide their credit card information and drop the envelope at one of the self-service pay stations at an entrance on their way out.</p><p>Beyond registration compliance, we also monitor other aspects of proper campground use. We check to make sure tents are set up on the tent pads or at least in areas that do not damage the “resource” (vegetation and other aspects of the landscape), that all vehicles are parked on parking surfaces, and that all equipment fits within the designated area for the campsite. In our particular campground, we also make sure everyone is either using a camp stove or the provided charcoal grills for cooking — no campfires are allowed. We check to make sure no one has hung a hammock or anything else from our precious and ancient junipers. We check for dogs being on leashes and in control. We remind campers of the 8am-8pm time allowed for generator use in some sites and of the 10pm to 6am quiet hours as needed.</p><p>We try not to be absolute sticklers on the rules. We are not at all in the role of enforcement personnel; that is the job of the law enforcement rangers when necessary. Rather, our job is to help educate guests about why the rules are in place. We’ll talk about how magnificent, old and fragile the trees are in this area and why it’s important to treat them with respect as non-human residents of this land. For noisy campers, we’ll talk about quiet hours and how sound carries across this landscape and the need to consider other campers’ experiences. Most guests are more than happy to comply when they understand the rationale behind the rules, and we are very appreciative of this cooperation.</p><p>We also let a few things go without an intervention depending on the circumstances. If campers have a small string of lights up, even leveraging a tree branch or two, but are otherwise respectful and quiet, we look closely for how they’ve done things and whether we see any visible damage. If they are taking care of their site and minimizing their impact, we generally let things be. If they are quiet and have a dog that is generally leashed but has come loose for a minute without bothering anyone, we’ll just smile and wave as they get the dog back on the leash.</p><h3>Resource Maintenance</h3><p>Campground hosts play an important role in maintaining the natural integrity and cleanliness of the campground, ensuring a positive experience for all visitors and the preservation of resources for future generations. In our case, this involves cleaning out charcoal grills, picking up litter around campsites, and tidying up after campers that move picnic tables or otherwise rearrange a site. We’ve become quite adept at picking out the little bits of micro trash that escape the notice of guests who often breeze through their time with us or that get strewn about when we have a different kind of heavy breeze.</p><p>Mitigating as much of the human impact around the campground is often the most fulfilling aspect of our jobs. We have developed a deep love and respect for this incredible landscape and its native inhabitants. Being able to contribute to its health and longevity in a small way is incredibly satisfying, and we take it seriously (Wallace, 1990). The accumulation of small impacts, such as littering or trampling vegetation, can lead to significant degradation of the environment for both those who call this home and those who visit for a brief moment (Cole, 1990). Actively contributing to resource maintenance not only helps in the immediate upkeep of the campground but also sets a positive example for visitors, encouraging them to adopt more responsible behaviors during their stay and beyond (Rebuya &amp; Menez, 2024).</p><p>In our role as campground hosts, we do not handle larger maintenance tasks, but we are often the first staff on site to identify the needs. For instance, the Park Service here at the Colorado National Monument maintains some very old infrastructure such as plumbing for water supplies to the restrooms and drinking water spiggots. With our constant roaming through the campground, we are often the first to spot problems that we investigate, document, and report to maintenance staff for resolution. Over time, we’ve developed a trusting relationship such that we know where important features, such as shutoff valves, are located and can take immediate action while waiting for larger repairs to be conducted.</p><h3>Being a good teammate</h3><p>As campground hosts, we do this job as a small part of a big team. The Colorado National Monument is small in comparison to larger National Park units. It has a modest budget and a pretty small staff, with most folks being seasonal and/or part-time. It is fortunate in being close to a larger city and having a great local non-profit “friends-of” organization in the Colorado National Monument Association. There are over 90 regular volunteers who do everything from staffing the Visitor Center to working as trail ambassadors and many other jobs.</p><p>Campground hosting here is somewhat unique for volunteers in that we get to work closely with other “divisions” in the organizational structure. We are officially a part of the “Fees” division and report to the supervisor in that division. We work with maintenance staff regularly as they handle everything from bathroom cleaning to major plumbing repairs. We also interface regularly with the Interpretive group that runs the Visitor Center, oversees all “Volunteers in Parks” (VIPs) for the area, and organizes ranger talks and other activities. We also interact with the Law Enforcement rangers pretty often as we see issues that need to be reported. The rangers also work diligently to drive through the campground on a regular basis, checking for issues and being an official presence.</p><p>So, a big part of our job is working to be good teammates with this great, dedicated crew. Even though these are some incredibly trying times for U.S. Federal employees, we have felt incredibly welcomed and honored to be part of this group. And we feel honored in turn to do our part to support and bolster the folks who are doing this work for a modest living as well as a life passion. This means getting to know our workmates, spending time talking with them about their experiences, filling in the blanks within our purview, and trying to not be too much of a pain.</p><h3>Rhythm and Process</h3><p>There are any number of ways that campground hosting duties can be carried out. What works for us may not be the same for everyone. But after a few months of trying different things, we’ve worked out a basic 4-phase approach.</p><ol><li>Afternoon/evening check-in</li><li>Late evening “compliance check”</li><li>Morning rounds</li><li>Check out and mid-day cleanup</li></ol><h3>Afternoon/evening check-in</h3><p>The busiest time of day for us is in the late afternoon/evening hours when guests are arriving for the first time. This is when we have the majority of our customer interactions. We try to be readily available in or around the host site from about 3–4pm until 8–9pm, especially on weekends. We see the most issues to work through when we are filled to near capacity. The campground at the Colorado National Monument is a stop-over spot for many folks on their way through to or from Moab or other destinations, so we sometimes see guests looking for a last-minute camping spot in our pool of day-of reservations. While many folks successfully use the mobile app or web site to see what’s available, complete a reservation, get to their site and get settled, others come up on a hope and a prayer that we can find some space for them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AXPqMIuKecHbq01t" /><figcaption><em>Like many campgrounds, the Saddlehorn Campground at the Colorado National Monument once used the standard placards indicating that a site was reserved for a certain number of days or available for use. Many guests still expect to find that here and sometimes don’t know how to interpret a site being empty when they happen by. We worked with NPS staff on the design of a simple notice indicating that visitors need to check for availability and reserve a site if they want to stay. It includes a QR code to the </em><a href="http://recreation.gov/"><em>recreation.gov</em></a><em> app/website for the campground as well as a phone number. These are placed on each site, but we do have issues with them blowing off occasionally so something more permanent will be needed eventually. We also have a few guests who come in with a surprising array of their own options for posting an “occupied” notice on their own site.</em></figcaption></figure><p>We keep track of how we are filling up so we can notify the entrance stations to put out the “all full” sign if necessary (and we catch them in time before the entrance stations close). This saves potential campers the trip up the winding road to the campground only to be turned around, disappointed, and without a camping spot.</p><p>We encourage folks to try the app if they can get decent cell signal with their carrier because we don’t handle any payments here at the campground. We’ve occasionally been able to walk someone through the whole process from downloading and installing the app to setting up an account and reserving a site for the first time. In the vast majority of cases, guests are able to work out using the system with no need for any help. In a few cases, particularly over busy weekends, we have 2–3 guests who are unable to work out the tech or arrive too frustrated and flustered to deal with it. In these cases, we identify available sites, close the site administratively, and give the guests the options of paying at the Visitor Center in the morning (if departing after 09:00) or dropping off payment with a provided envelope at one of the self-pay stations still available at the entrance stations.</p><p><strong><em>Note on finding and closing available sites -</em></strong></p><p><em>We have found that it is best to use the public recreation.gov mobile app to identify available sites vs. the “available” filter in the R1S Ranger app. This is exactly what a guest should see if trying to book a site for themselves, so we can show them what they would see. Available sites on the R1S app does not usually show what are actually available publicly.</em></p><p><em>We then use “The Hub” (manage.recreation.gov) to administratively close a site. In closing a site for just a single night (generally the case), we set the date range to the previous day through to the current day. Otherwise, the site will effectively remain closed for the current and following dates.</em></p><p><em>This is the same process used by the Visitor Center staff. The unfortunate byproduct is that the sites handled this way do not show up in the app or the management web site as reserved — they are instead “closed.” This interferes with effective reporting over time and causes some consternation when we go to conduct check-outs as we have to keep track of them a different way. There should be an option to put these in as regular reservations though perhaps with less or no personal information about the guest.</em></p><h3>Late evening “compliance check”</h3><p>The manual for campground hosting describes the process of “compliance checks” to include verifying that the guests who reserved sites are in those sites, that no one is in a non-reserved site, and that guests are complying with all of the campground rules (e.g., no wood fires, nothing hanging from trees, etc.). Not having any enforcement authority as camp hosts, our role is primarily one of education and communication to ensure compliance with campground rules and regulations. The focus is making sure all guests are safe and having an enjoyable time.</p><p>After most campers are in and settled is the best time to make a compliance round through the campground. Depending on how busy we are and how many late arrivals we have, we may make an initial round at about 20:00 and another later round (often on foot so as to cause less disturbance). We mark check-ins using the R1S Ranger app on our phones which keeps the information updated on the Recreation.gov system for Law Enforcement Rangers and others to keep up to date on who is on site.</p><p>In our particular case, we are not checking each individual reservation in terms of the name and details like the use of a Senior Pass; we simply verify that each reserved site has someone in it and that no non-reserved sites are occupied. We do make a cursory check of the equipment and the total number of guests, but this information on the reservations is not all that reliable. We do check to see that the total number of guests in a given site does not exceed the maximum allowed (7 in our case).</p><p>We check to see that the vehicles are all parked on the provided parking surfaces and not in the road or harming vegetation. While there is a stated limit of 2 vehicles per site (including trailers as a vehicle), this is not strictly enforced. As long as guests are able to get their vehicles fully within the provided parking area and do not harm the “resource,” we let it pass.</p><p>We do also check for compliance with the “no wood fires” rule, which is strictly enforced and something we can call law enforcement about if necessary. We do allow propane “fire pits” but not other options people sometimes try to use such as “Solo Stoves.” We also check to make sure generators are not running after allowed hours (08:00 to 20:00 in our case), that all dogs are on leashes, and that no one has hammocks or other things hanging from or tied to trees.</p><h3>Morning rounds</h3><p>Morning rounds are dependent on the number of check-ins that we missed from the previous evening (e.g., late arrivals) and on “can’t miss” sunrises. There is no enforcement here on no-show reservations, which would trigger a penalty fee assessed to the reserving party. In the case of the Saddlehorn Campground at the Colorado National Monument as something of a stopover for many folks on their way to somewhere else, it is not uncommon for a certain percentage of folks to simply not show up or come in so late and leave so early that we never see them.</p><p>So, depending on when we get up and how early we see folks start packing up, we may or may not do another round to verify check-ins. We do see things in the early morning that we wouldn’t otherwise observe such as hammocks in trees or evidence of wood fires. It’s also a time we might be able to answer questions for guests as they are preparing to go about their activities for the day. We also occasionally do find sites occupied that had no reservation. These are primarily the cases where we write up and issue a written warning if we don’t happen to see someone in person to talk with.</p><p><strong><em>Note on written warnings -</em></strong></p><p><em>The National Park Service provides a yellow warning card with a number of options such as “clarifying” the camping fee or having a dog off leash. We have primarily used these in cases where we have someone parked in a site that has no reservation. Whenever we write up a warning, we take a picture of the vehicle or other subject of the warning (including license plate and site number) and take a picture of the written warning itself. In the case of a non-reserved site occupant, we include a payment envelope with the written warning left under the wiper blade.</em></p><p><em>It is important to note that the written warnings we leave as camp hosts are in no way an enforceable legal action. They are simply an educational warning. We have occasionally had people react strongly to having us place a warning note, particularly when they felt that they did everything in their power to comply. It’s important to be available to talk through any issues with folks, and we generally prioritize in-person discussions when possible.</em></p><h3>Check out and mid-day cleanup</h3><p>We work through cleaning up campsites and preparing for the next guests sometime around mid-day. We may start a little early before official check-out (11:00 in our case) on busier weekends as our check-in and check-out times are the same. The guests usually vacate the sites more or less on time, but we will sometimes give them a reminder if we see them lingering well beyond check-out time and we see that we have another reservation coming in. We do also have guests that are able to make a new reservation for an additional night in our day-of sites, so we check the R1S Ranger app for cases where we see a checking out site still occupied (or earlier occupied sites that need a “check-in” action in the app).</p><p>In checking out sites, we are generally looking for three things:</p><ol><li>How did the previous guests behave and treat the site?</li><li>Is the site prepped and “reset” for the next guests?</li><li>Is there anything major going on for which we need to engage the maintenance crew?</li></ol><p>We spend a bit of time in each site looking for recent trash or even older “micro-trash” that shows up all too regularly. We clean out charcoal grills and check to see if guests were burning wood or something else they shouldn’t have been. We look through the vegetation to see if all the non-human inhabitants are doing okay and remain unharmed by visiting humans. We look for any left items and will either hold those for a time in our lost-items pile at the host site or contact a guest for something like prescription eyeglasses or expensive equipment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zRgcA80x0R5ilSVK" /><figcaption><em>We’ve become quite adept at spotting microtrash — those tiny little bits of plastic, foil, paper and other signs of human habitation that are the bane of any natural area manager. While we focus on it as a task, the vast majority of our visitors do an excellent job at policing their site. We particularly love it when we see parents teaching their children about going over the ground carefully picking up any refuse before they leave. This is one area where it would be great to give camp hosts at public lands campgrounds the ability to provide a rating or comments for guests. Guests get to comment about the cleanliness of restrooms or other amenities, and it would be great to provide some of that same type of feedback for the customers.</em></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*4y2ikBxDm0OuUuiB" /><figcaption><em>Cleaning out the charcoal grills is one of the services we provide as camp hosts. Surprisingly enough, we have had a handful of guest clean up their own grills, which we try to note and encourage with a positive word when we see it. We do also find odd things left in grills over time from cigars and cigarettes to the other things people tend to smoke in our state. Dental floss seems to be a regular leaving. One technique we’ve adopted is to always leave the grate for these grills in the top position. It gives us a quick visual clue that the amenity might have been used and needs checking.</em></figcaption></figure><p>In the case of more harmful or disrespectful behavior, there is no real action that we can take other than to note it for our own purposes and potentially take some mitigating action such as moving rocks or barriers around to help future guests become more aware. We have requested a “camp host feedback” feature on <a href="http://recreation.gov/">recreation.gov</a> that we feel would be helpful in providing gentle education for guests on more respectful behavior at campgrounds, but no action has been taken on this yet. When we have seen a preponderance of more risky thing like wood fires, we provided feedback to the paid staff toward actions they might take in terms of additional signage.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*08ana-tEj_7GVtWP" /><figcaption><em>One of the things we’ve done a fair bit of work on at the Saddlehorn Campground is placing rocks around the trees and shrubs that we would really like to remain intact as the beautiful natural landscape they are a part of. We regularly see guests that have come in driving or sometimes walking over vegetation as they get themselves settled and using the site. If we see that happening, we offer a gentle admonishment about the fragility of the high-desert ecosystem and point out ways they can be more careful to avoid damaging the trees and shrubs around them. We place rocks around the vegetation adjacent to parking areas as a visual clue that there’s something there to pay attention to when using the site.</em></figcaption></figure><p>We also look to see what guests do with their sites to modify amenities such as picnic table placement or tent pad use. These can be problematic such as a guest opting to move a picnic table right in the middle of a tent pad that the next guest may wish to use in a different way. In these cases, we may take some action to reset the site for more general use. We might also note cases where a maintenance action could be taken to better manage the site for all guests (e.g., chaining a picnic table in place). We also look for acute or more chronic issues developing such as water leaks or insect habitat that may need to be mitigated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DaIcFM83NSU38Keq" /><figcaption><em>Because many of our sites are fairly rustic, guests do all kinds of interesting things to try and level their campervans, cars, and trailers. They quite often use the rocks we have in the area in this pursuit, most often leaving them where they used them when they drive off in the morning. This can be a bit of a pain as the next guests may not need or want them in the same configuration. We generally tend to pick them up and move them back to a location where they are demarking vegetation we want folks to be mindful of.</em></figcaption></figure><p>One other minor thing we take care of during the mid-day is placement of programming signs and any other notices on the billboards (e.g., weather forecasts) located in each camp loop. The interpretive staff print these out for us, we pick them up before our rounds, and then get them in place. This also helps us keep up on “ranger talks” and other activities that we can share with guests as we interact.</p><p><strong><em>Note on technology use for check-outs -</em></strong></p><p><em>For a time, we used the R1S Ranger app directly in conducting check-out operations. It shows the check-outs for the day and has a feature to flag each site as checked as we go. However, over time, we found it easier to use manage.recreation.gov to write out a quick checklist of sites to check out on paper and then do a bulk operation once completed. The let us jot down notes about things we observed requiring follow-up action and conduct the physical labor of the work without jumping back and forth to our phones. It is still important to have the app available to handle to check through occupied sites for someone making a new reservation in the same site.</em></p><p><em>We also found one truly annoying thing in the R1S Ranger app where checking out a site does not result in some type of visual indication that this has been done (e.g., change in color or simply having the check-out notice disappear). This makes it easier to simply use a scrap of paper to keep track of the process.</em></p><h3>Conclusion</h3><p>All in all, the campground hosting experience has been great for us. We are able to help fill an important role as volunteers at a truly magnificent location. We feel like we have a small beneficial impact on helping to ensure that the monument remains a high-quality location for visitors and for the native flora and fauna that were here long before us and will hopefully outlast us as a species. We’ve received some direct and indirect feedback from guests who have appreciated our approach and the small things we’ve been able to do to help them have an enjoyable time.</p><p>The work has kept us busy and in better shape. It’s given us an opportunity to learn how to work together at a job as a married couple; something that our equally strong personalities sometimes makes rather “spicy.” It has also helped to cement our understanding and appreciation of the drive and dedication of the National Park Service staff with whom we interact, both paid employees and other volunteers.</p><p>We get frustrated occasionally when visitors treat the area disrespectfully, damaging the resources or creating a less-than-ideal experience for other visitors. However, in the grand scheme of things, those are rare cases with the vast majority of guests leaving virtually no trace or even making their own small improvements. While we may occasionally grumble about the small number of outliers, the many interactions we have had with truly lovely people who love and respect this landscape as much as we do have made this a very fulfilling adventure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*amDWajk703pH1qz5" /><figcaption><strong>This truly is the greatest job ever!</strong></figcaption></figure><h3>References</h3><p>Cadwell, C. (2017). New Employee Orientation. In The SAGE Encyclopedia of Industrial and Organizational Psychology, 2nd edition. <a href="https://doi.org/10.4135/9781483386874.n351">https://doi.org/10.4135/9781483386874.n351</a> <br>Cole, D. N. (1990). Some principles to guide wilderness campsite management. 181. <a href="https://www.fs.fed.us/rm/pubs_journals/1990/rmrs_1990_cole_d001.pdf">https://www.fs.fed.us/rm/pubs_journals/1990/rmrs_1990_cole_d001.pdf</a> <br>Cole, D. N. (2021). Reflections on the early history of recreation ecology. Parks Stewardship Forum, 37(2). <a href="https://doi.org/10.5070/p537253243">https://doi.org/10.5070/p537253243</a> <br>Ferguson, M. D., Caraynoff, A. R., Ferguson, L. A., Barcelona, R. J., Evensen, D., Knox, H., Pytlik, S., &amp; Grosz, D. (2022). Whether They Return: Modeling Outdoor Recreation Behaviors, Decision Making, and Intention-to-Return in Congressionally Designated Wilderness. Forests, 13(7), 1018. <a href="https://doi.org/10.3390/f13071018">https://doi.org/10.3390/f13071018</a> <br>Rebuya, N. R., &amp; Menez, M. (2024). Resource Conservation Strategies, Visitor Experience, and Satisfaction at Natural Parks in Bicol Region, Philippines. OALib, 11(7), 1. <a href="https://doi.org/10.4236/oalib.1111863">https://doi.org/10.4236/oalib.1111863</a> <br>SCHARF, P. L. (1942). Opportunities for Counselors in Summer Camps. Occupations The Vocational Guidance Journal, 20(6), 407. <a href="https://doi.org/10.1002/j.2164-5892.1942.tb01192.x">https://doi.org/10.1002/j.2164-5892.1942.tb01192.x</a> <br>Sharmin, F., Sultan, M. T., Bădulescu, A., Bâc, D., &amp; Li, B. (2020). Millennial Tourists’ Environmentally Sustainable Behavior Towards a Natural Protected Area: An Integrative Framework. Sustainability, 12(20), 8545. <a href="https://doi.org/10.3390/su12208545">https://doi.org/10.3390/su12208545</a> <br>Wallace, G. N. (1990). Law Enforcement and the “Authority of the Resource.” <a href="https://www-static.bouldercolorado.gov/docs/authority-of-the-resource-article-1-201305221020.pdf">https://www-static.bouldercolorado.gov/docs/authority-of-the-resource-article-1-201305221020.pdf</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20fbff03f406" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to keep the global knowledge commons healthy]]></title>
            <link>https://medium.com/@skybristol/how-to-keep-the-global-knowledge-commons-healthy-a7e73561a7d0?source=rss-b947a36d30f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7e73561a7d0</guid>
            <category><![CDATA[linked-open-data]]></category>
            <category><![CDATA[digital-object-identifier]]></category>
            <category><![CDATA[wikidata]]></category>
            <category><![CDATA[global-knowledge]]></category>
            <dc:creator><![CDATA[Sky Bristol]]></dc:creator>
            <pubDate>Sat, 08 Jun 2024 21:27:41 GMT</pubDate>
            <atom:updated>2024-06-08T21:27:41.159Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve started back into doing some work in Wikidata after spending the last year or so, in my professional capacity, working on a separate Wikibase instance with domain-specific content. As I found the last time I headed down this path, the Wikidata ontology is often a real mess to try and work with. With thousands of active users from many cultures and walks of life making contributions, there are bound to be interesting semantic collisions.</p><figure><img alt="“Data Wrangling” in a steampunk motif" src="https://cdn-images-1.medium.com/max/1024/1*-Btd5O-4plKO73w9YmLzxA.jpeg" /><figcaption>“Data Wrangling” in a steampunk motif — generated by DALL-E 3 (“Generate an image for me that represents data wrangling. Include someone on a horse with a lasso and have them trying to toss it for a catch of something that looks like a spreadsheet with rows and columns. See if you can do that in a steampunk type of motif.”)</figcaption></figure><p>What’s frustrating is that every time I head into doing some specific thing, I find 6 or 8 other things that really ought to be done first. I suspect that much of the messiness we find in Wikidata comes from many of the people contributing not doing those 6 or 8 other things first. This is actually a bit scary to me when I think about current practice in training Large Language Models (LLM) and even the longstanding use of Wikidata as structured content to help improve public search engines. How are the engineers developing training algorithms determining what to trust and not trust at the level of claims, qualifiers, and references (or are they looking that deeply at all)?</p><p>My most recent example came about while trying to build a process that will more comprehensively deal with the <a href="https://www.wikidata.org/wiki/Property:P1662">DOI prefix</a> property in Wikidata. In working with DataCite as one of the DOI registrars, we have Research Organization Registry identifiers that help, in some cases, to more unambiguously identify the organization that owns a “DOI repository” and issues identifiers under that prefix. Looking at Wikidata, there are <a href="https://w.wiki/AKnj">over 108K ROR identifier claims</a> with a bot process handling some level of synchronization. At first glance, it seems like this might be a good way to identify the WD items that would represent the DataCite “provider” organizations where DOI prefix claims from that system should land.</p><blockquote><em>CrossRef is another matter in that we don’t have something nice and handy like a ROR identifier to work with. I’ll write more on that one later.</em></blockquote><p>If we’re going to assume that a ROR ID is assigned to the correct item in Wikidata that we would want to use, we need to do at least some basic integrity checks to validate any assumptions we might be making. The <a href="https://www.wikidata.org/wiki/Property:P6782">ROR ID property</a> has a distinct-values constraint, but when I initially pulled and checked the data, I found 64 violations of this constraint where the same ROR ID was assigned as an ExternalID on more than one Wikidata item. The notebook I linked to above ran through these, pulled the ROR records, and was able to find a number of cases where one of the “duplicate assignees” had a Wikidata label that matched a label in the ROR registry. In those cases, I removed the ROR ID claim from the item whose label didn’t match up with something in the ROR record.</p><p>However, there are some others where things aren’t as straightforward, and even for those that were, we might still have other issues. There are at least some of these that look a lot like duplicative items — multiple Wikidata items representing the same real organizational entity. For instance…</p><ul><li><a href="http://www.wikidata.org/entity/Q123951831">Arc Research Institute</a></li><li><a href="http://www.wikidata.org/entity/Q125705411">Arc Institute</a></li></ul><p>These are quite likely the same entity, each with different information content, all of which might be valuable. They were created at different times by different users, one of whom doesn’t seem to have an extant user account. There is a process for merging records in Wikidata that handles some of the mechanics, but I’d argue that process needs some degree of sophistication. When something like this happens in the “global knowledge commons” it is perhaps a signal that the system is less than healthy and all of the information content surrounding the “unhealthy growth” needs to be examined and treated.</p><p>As I start delving deeper into areas of linked open data that I want to work on and contribute to the global knowledge commons, I’m thinking I need to develop some type of generalized health analysis algorithm. I don’t want to rebuild this every time I have to work through another set of content. The algorithm needs to be fairly deep in that we should look at not only the content as it exists but into the history of how that content came about. Fortunately, with all of the history logging inherent in Wikimedia, much of this is captured and accessible via API in Wikidata (or any Wikibase instance). I will likely start building this functionality into the nascent <a href="https://github.com/skybristol/wbmaker">wbmaker package</a> I’ve started working up. Whether or not I can generalize enough useful health checks for a set of functional code remains to be seen, but I should at least be able to abstract things enough to be a useful aid in identifying the 6 or 8 things.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7e73561a7d0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Indian Country needs authentic representation in the Global Knowledge Commons]]></title>
            <link>https://medium.com/@skybristol/why-indian-country-needs-authentic-representation-in-the-global-knowledge-commons-1162ce42c465?source=rss-b947a36d30f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1162ce42c465</guid>
            <category><![CDATA[cherokee-nation]]></category>
            <category><![CDATA[indian-country]]></category>
            <category><![CDATA[indigenous-knowledge]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[wikidata]]></category>
            <dc:creator><![CDATA[Sky Bristol]]></dc:creator>
            <pubDate>Fri, 04 Aug 2023 23:01:04 GMT</pubDate>
            <atom:updated>2023-08-04T23:01:04.888Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*lAgmnI1D5XfTDApq.jpg" /><figcaption><strong><em>Shadow of the Owl </em></strong>— This painting by Cherokee artist, John Guthrie, inspires my vision and thinking presented in this article. For me, it represents great harm committed and travesties suffered while still looking forward to today and tomorrow and what can be impacted for the greater good. I encourage you to check out Osiyo.tv for a great profile on John and his work — both art and equine therapy.</figcaption></figure><p>In this article, I make an argument for the Global Knowledge Commons as a worldwide enterprise where all peoples, cultures, and ways of knowing can continually work toward synthesis and greater understanding of each other and the world we inhabit. The Commons, which I define and describe in the article, is inevitably messy and imperfect at all times because it is an encoded reflection of the messiness and imperfection of humanity. It will go through periods of seeming to bring better clarity to how human and artificial intelligences navigate the complexities of the our earth only to incorporate some new way of knowing that challenges things we thought we knew. It is, in essence, becoming the shared memory of AI models, and we will be wise to pay attention to its upkeep as we continue to advance that technology.</p><p>My research focus is on Native American Tribes and interests specifically, but many of the concepts and principles described apply beyond Indian Country in the U.S. to other communities around the world who are currently not well represented in the Global Knowledge Commons. I concentrate on an area I’m passionate about and am putting personal time and energy into addressing. The article presents background and thinking for a line of research and development I’ve initiated. It’s a way of laying out my thoughts and motivation, and I include a link to a working codebase and opportunity to collaborate for anyone interested.</p><h3>What I mean by Indian Country</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rl56NOq34CUbWALY98RxOg.png" /><figcaption>Levi Rickert (Potawatomi) discussing work by Mark Charles (Diné) in Native News Online’s Native Bidaské from July 7, 2023, describing Abraham Lincoln in his own words, challenging much of what we were taught in school. I’ve been consistently inspired and informed by Levi’s journalism, and I’m incredibly grateful for what he and his team have done in bringing Native News Online to the world. If you don’t (or do for that matter) live in Indian Country and want to learn more, NNO is a great place to start and come back to every day.</figcaption></figure><p>Indian Country is a term that serves when we want to talk about indigenous nations and peoples in the United States. There are many distinctions and groupings within this from American Indian, Alaska Native, Native Hawaiian, and many others. It sometimes extends beyond U.S. borders into Canada’s First Nations and certainly encompasses at least the seven cross-border Tribes between the U.S. and Mexico. While each Indigenous Nation is sovereign in its own right, struggling through government-to-government relationships with the United States, the Tribes find much common ground in shared history and collaborate together through numerous organizations and federations.</p><p>My own place in Indian Country is small and late in life. I’ve been a registered citizen of the Cherokee Nation since 1991 when my grandmother, mother, and aunts traced our roots through Maybell Cobb (my great-grandmother), her father William McDade Cobb on the Dawes Roll, and Polly Fivekiller who came west from our homeland on the Trail of Tears. I’ve only recently started becoming more engaged as an at-large citizen of the Tribe and certainly do not share the lived experience with many citizens on the reservation.</p><p>I have, however, started finding a greater emotional and spiritual connection with the Cherokee community, values, and lifeways than I have with anything else in my life. There may be something to the story that a land and a people and a heritage of ancestors call out for connection across the years. There’s something about the Cherokee story that is incredibly compelling to me and is helping guide my journey toward the next things I want to do in life. Gadugi, the deep sense of responsibility to community, is not the sort of platitude or simplistic aspiration I’ve seen in other things I’ve been part of over the years. It is a fundamental driver that the Cherokee Nation government and people always seem to have at the forefront of decision making.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X7w1daVNrGE0dWsy86yfqQ.jpeg" /><figcaption>Poster form of the Cherokee Values with English translations from cherokeesatlarge.org</figcaption></figure><p>Cherokee community values or <a href="https://cherokeesatlarge.org/wp-content/uploads/2022/02/Cherokee-Values-Poster-1.pdf">sgadugi dikanowadvsdi</a> are constantly being reinforced through the Cherokee stories that I’m learning. At the same time, Cherokee history is full of contrasts, equally sharing places where we have fallen short of the ideal. John Ross, the celebrated Principal Chief who navigated the Cherokees through the removal to Indian Territory and reconstitution of a shattered society, was a slave owner along with other Cherokee leaders of that time. The Cherokee have their own struggles through emancipation of enslaved peoples and granting full citizenship to the <a href="https://en.wikipedia.org/wiki/Cherokee_freedmen_controversy">freedmen</a> following the U.S. Civil War. In that struggle are also compelling stories like that of <a href="https://www.youtube.com/watch?v=lNmaFaLWoLQ">Joseph Stick-Ross</a> who was enslaved by John Ross (leading to his very name) but was elected to the Tribal Council and worked as a civic leader to reconstruct the Cherokee Nation after the devastation wrought by the Civil War.</p><p>It’s these contrasts and the struggle toward balance that are inspiring a line of research and development I’m working toward and about which this article is a start.</p><h3>What I mean by the Global Knowledge Commons</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TdqDZm_b-N49OSlptSexLw.png" /><figcaption>Map of the five nations making up the Haudenosaunee (Iroquois Confederacy). There’s some evidence that our system of government and the U.S. Constitution, which the history written by the conquerors ascribes to the brilliance of the “Founding Fathers,” was largely coopted from the Iroquois Confederacy. The overall basis for governance through much of early America was based on everyone being involved and contributing their voices and unique perspectives and talents to the community whole. That same ethos infuses many current Tribal governments today, and it’s at the heart of the American experiment that teeeters back and forth between success and failure.</figcaption></figure><p>The term, Global Knowledge Commons, has mostly arisen within the scholarly publications community. It is the central principle underlying the <a href="https://www.coar-repositories.org/">Confederation of Open Access Repositories</a> organization and has been a concept much discussed in the Open Science movement. The openDemocracy media organization has <a href="https://www.opendemocracy.net/en/defending-global-knowledge-commons/">discussed the concept</a> in somewhat broader terms with a focus on growing an educated and engaged polity. While it is on the one hand an abstract concept, it is increasingly becoming more concrete and in need of significant research and development focus.</p><p>I first started using the Global Knowledge Commons term as I got <a href="https://www.wikidata.org/wiki/Special:Contributions/Skybristol">involved in Wikidata</a> and through recent work with the <a href="https://wikibase.cloud/">wikibase.cloud</a> project, referencing the more concrete environment built by the Wikimedia Foundation. This includes the well established Wikipedia, the knowledge graph in Wikidata, Semantic Mediawiki, Wikimedia Commons, and the other projects making up the “Wikiverse.” Together, this platform comprises the most robust and comprehensive venue where we currently have the greatest diversity of cultures and languages coming together to record knowledge about all things that humans know anything about.</p><p>I remember a time in the mid-2000s when certain articles in Wikipedia started to become comprehensive, accurate, and sufficiently referenced that a few scientists attempted to use them as cited references for some basic types of things in scientific articles. This triggered some debate for a time as to the viability of Wikipedia as a resource, with many passing it off as an ephemeral thing that we could never count on in any serious way. In science, we are trained to always go back to an original source for citation purposes. We increasingly do work in the knowledge synthesis space, but science is sticking to the norm of publishing our syntheses in individual peer reviewed papers and occasional domain specific compilations.</p><p>The burst of Large Language Models (LLM) onto the public stage and the massive technological “arms race” that has sparked, bring the Global Knowledge Commons concept into stark focus. What does open knowledge truly mean? What exactly are the labeled corpora that OpenAI and the other big proprietary players in the game are using to train models containing billions of vectors? Have they crossed the line and not respected license terms, taking the attitude that accessibility and readability online means that the cat’s out of the bag anyway?</p><p>Ethical and non-ethical tech development, like all human enterprises, will keep going, and we’ll be working our way through the messiness of this period of acceleration for some time to come. However, there’s one thing that’s certain:</p><blockquote>If we don’t make intentional and sustained efforts to continually bring more of the world’s ways of knowing into a form that is accessible to train AI, AI will continue to reflect (and potentially accelerate) systemic marginalization of real people who live and breath those systems of knowledge in everything we apply it to.</blockquote><h3>A perspective on Indigenous Data Sovereignty</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nBGX6-q6ZyM576BwbsoHGg.png" /><figcaption>I first really started thinking about the issue of indigenous data sovereignty, at least in those terms, through this plenary talk from Dr. Carroll with the Native Nations Institute at the ESIP Winter Meeting in 2022. It was inspiring, sobering, and challenging all at the same time — exactly what ESIP is designed to do.</figcaption></figure><p>In the recent <a href="https://2023julyesipmeeting.sched.com/">summer meeting</a> of the <a href="https://www.esipfed.org/">Earth Science Information Partners</a> (ESIP) I had a conversation with a colleague from Alaska where we struggled a bit through the tension between open science/open data and indigenous data sovereignty. On the one hand, we both deeply value and have worked diligently toward much more openness and transparency in data, information, and knowledge; observed, measured, and interpreted about all things on earth and in the universe. On the other hand, we recognize the sovereignty of indigenous Nations and the government-to-government relationships that guide how we go about this work as it relates to Tribal interests.</p><p>Those interests and governing mechanisms guide how we think about digital representations of the earth system on reservation lands directly owned by Tribes, lands held in trust for the Tribes by the U.S. government, and other areas for which the Tribes have stewardship rights under treaty (most often with ecological vs. cadastral boundaries). We also recognize the systemic injustices that continue to perpetuate the marginalization and exclusion of indigenous nations and peoples in the decision-making process. We recognize the generational trauma impacting indigenous communities wrought through broken treaties, often perpetuated through egregious misuse of data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TTTE2R49_S_JdY7wo3QDjw.png" /><figcaption>The State of Alaska’s Salmon and People (SASAP) project is one case of indigenous and non-indigenous researchers and community leaders working together from the start to design and operate a scientific observation and research program that seems to be achieving a balance between indigenous data sovereignty and open science principles and practice.</figcaption></figure><p>The tension between open science and indigenous data sovereignty is dramatically reduced when science is a joint enterprise between indigenous and non-indigenous scientists. We figure out together what we’re going to observe and measure and how we will manage the data, information, and knowledge that comes from the work. When we don’t develop the relationships and work together, the tensions escalate and injustices perpetuate. What actually happens in those relationships is a blending of systems of knowledge into a shared way of knowing that guides the development of observing systems and the research that continues.</p><h3>Harmony in the Global Knowledge Commons</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*uzQAatZP257eUKw3.jpg" /><figcaption>Image by Scott Reinhard, New York Times, 2020 — Scott provided a <a href="https://2023julyesipmeeting.sched.com/event/1KoHG/esip-lab-plenary">plenary presentation</a> at the ESIP Summer Meeting 2023, a recent point where I laughed and cried within the same short period of time. More than the amazing and impressive data-driven artwork, it was Scott’s storytelling that was most compelling, both in style and content. Perhaps it was the regular contrast of harmonies creating both consonance and dissonance, like this one even — thousands of people dying over here, but “play the crossword.”</figcaption></figure><p>Harmonies in music are when multiple, diverse sounds or voices come together and coincide to create something new from the whole. In musical compositions, harmonies create both consonance (a coming together) and dissonance (period of tension or pulling apart), often telling a story or taking the listener on a journey that is a blend of composer and listener interpretation. Balance, both emotional and physical, can refer to a state of being in harmony, meaning that both consonance and dissonance need to coexist and be held in focus at the same time.</p><p>This is precisely what we are struggling with on our way toward the Global Knowledge Commons, which is part of creating digital representations of reality such as <a href="https://en.wikipedia.org/wiki/Digital_twin">digital twins</a>. I feel most alive and in harmony with the universe when I laugh and cry within the same span of time. The stories and metaphors that catch us up and teach the most poignant lessons are those that take us through that emotional journey. Ecological systems, of which we humans are a part, operate the same way; life and death, senescence and renewal are how the planet’s harmonies strive for balance. As the dominant force on the planet in what is now (arguably for some) the <a href="https://en.wikipedia.org/wiki/Anthropocene">Anthropocene</a>, humans have developed the power to create more dissonance over consonance, at least within the as yet to be determined timespan of our existence.</p><p>It is our knowledge and reasoning as humans that has allowed us to become the most dominant force. We have the power to destroy ourselves as well as so many other of our fellow earthlings, but we also have the ability to thrive, compose our future with the full range of diverse harmonies in our species, and find balance. With so many of us humans and the rapid (on geologic timescale) change we’ve set in motion, it won’t be the earth system we know now. We can’t truly go back to any state that the earth has been in before. But we can create a world that is more rich with life and lifeways, coexisting and harmonizing better than we are today.</p><h3>Why Native American lifeways are so vital</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TYbAsIbTRg_u97usPyEPUA.png" /><figcaption>Part of the Cherokee origin story behind Juduculla Rock in present day North Carolina teaches us that the instructive inscriptions on the rock were left by a giant who knew all languages and spoke to all the creatures of the earth. He lived among us for a time, instructing us on proper lifeways and how to care for the earth, before leaving to his homeland. When he learned that certain people were over-hunting and taking too much from the land he leapt over the mountain, landing on the rock and grounding himself there so that he might return, and then inscribed the knowledge we needed in order to live in balance on the earth so that we wouldn’t lose sight of our responsibility again.</figcaption></figure><p>There was a time when I struggled with how indigenous values were coopted and romanticized if not fetishized by some parts of western culture. I looked with skepticism on just how much balance with nature and thoughtful stewardship of resources the spiritualists claimed to be borrowing from Native culture. It’s taken my own journey through the Cherokee history and more importantly the Cherokee story of today to understand my Native heritage beyond the romance. I’m continuing to seek out and learn more from the Puebloan ancestors and descendants close to me in the Southwest or the Nimiipuu (Nez Perce) and Shoshone-Bannock I learned stories from while visiting Idaho this summer.</p><p>All of these stories are full of harmonies creating both consonance and dissonance. They are not simplistic and must be experienced across the sweep of time into the present moment and the realities in Indian Country on the ground today. Weaving through all of what I’ve learned so far is a common thread of striving to live as a co-equal species on the planet that must necessarily dominate in some areas to survive but must also give back as much or more than we take.</p><p>A principle I’ve read from Native basketmakers guiding their gathering practice is to “take what you need and need what you take.” We have a thing to make that we need to survive and thrive, but we need to do it in a way that leaves the resources intact or enhances them for the next thing we need to make. We acknowledge that we’re not the only species that needs to use the resources, that all other species share an equal right to use the resources, and that we all rely on each other — the habitat creators and the habitat users — to make a home.</p><p>In too many areas, we have and are violating this basic precept of sustaining our planet. In a recent trip to Idaho, I met a Shoshone-Bannock biologist on the banks of the Yankee Fork where he was working a fish weir that’s part of a salmon reintroduction effort. That’s an area where we dredged miles of riverbed, completely decimating an ecosystem, to yield only $1.2M in gold estimated at just 40% of the potential. How many resources have we extracted from the earth globally, and how much have we actually needed to be in the good places we are vs. the not so good?</p><p>In much of the world and certainly here in the U.S., we are still making decisions and going about life following the <a href="https://www.gilderlehrman.org/history-resources/spotlight-primary-source/doctrine-discovery-1493">Doctrine of Discovery</a> — the notion that if we show up in some place or situation where we can claim a right to dominate and make a profit for ourselves and our descendants, then we have a duty, endowed by “God,” to do so with all our power. There are degrees of this, of course. People are complex and situational. But we fundamentally need more emphasis toward responsible stewardship of the planet and impedance of our worst instincts and the corruption of absolute power.</p><h3>Sharing Native American lifeways in the age of AI</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*aQZxNTOkb0uBDLf_" /><figcaption>This is an image generated by the DALL-E AI from OpenAI/Microsoft in response to a prompt. Part of my prompt with some interpretation and rephrasing is included in the chat response, which I found more interesting in itself. — “I have generated an image that represents Native American influences in Artificial Intelligence. The image depicts traditional ecological knowledge and the incorporation of Native American thinking and lifeways into AI models. I hope you find it interesting and thought-provoking!”</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BDM_TM28A9HiMWSU" /><figcaption>This second image is the result of a followup with the Bing edition of ChatGPT where I suggested that the first set of images contained some things that I found a bit stereotypical of Native American imagery. I prompted with a question about the model’s background on traditional ecological knowledge and particularly the work of the UN Permanent Forum on Indigenous Issues in this regard and asked it to generate a new image with that context. The “eyebrow tree” was my favorite of the lot.</figcaption></figure><p>We need more voices from other communities, particularly indigenous American communities to bring different ways of knowing and wisdom to bear on the problems we face together. It’s up to members of Native American communities to decide what parts of our lifeways to share and how to share them. Having not shared the lived experience myself, much of this is not my purview. What I do have a responsibility for, though, is to bring my talents and perspectives and my own lived experience to the journey.</p><p>One of the technical dynamics I’ve been examining as I’m doing work with LLMs and other aspects of AI in my professional life is the role of the Global Knowledge Commons in guiding how AI learns to reason. The knowledge graph aspects of Wikidata and related graphs that can be federated via persistent resolvable identifiers are a key part of having AI conjecture about the things we don’t already know vs. continually “guessing” about things already known. Knowledge graphs are increasingly becoming the “external memory or brain” of AI — where the things the AI knows and learns (and what we teach it) are encoded for later recall and use.</p><p>This is precisely why I argue that we need to have voices and viewpoints from Indian Country fully represented in the Global Knowledge Commons. We need to enter into the messy world of explaining who we are now as people, communities, governments, and sovereign nations. We need to clarify how we relate to other entities, establishing at least one point of truth within the global knowledge space. The claims and assertions that we make about ourselves can and should point back to other online sources of information and the deeper story.</p><p>We should also seek out and correct things that are flat wrong. Unlike much of the history that has been written by the conquerors, there are Wikipedia articles that do a good job telling real stories not found in many textbooks. But there is much more work to do in setting the record straight, and the structured, encoded knowledge part of the picture in Wikidata still has a long way to go.</p><h3>Anatomy of Wikidata and its implications</h3><p>I provide this short diversion into some relatively technical aspects of one of the main components of the Global Knowledge Commons I’m working with as context for thinking about what contributions from and about Indian Country will entail. It may be a little thick in the tech details for some, and way too high level for others.</p><p>One of the really interesting things about the design of Wikidata that Denny Vrandečić came up with is the notion that every statement about something is a claim or assertion. Each claim can have one or more references pointing to something else in the knowledge graph or some foreign entity that provides the evidence for the assertion. Claims can also have qualifiers that help to clarify the significance of the assertion or information that should be used in concert with the claim. The whole system is further aided by robust history that at least tells us when entities were created, when claims were made, and what user made the contributions. Responsible contributors share sufficient notes about what they did and why, and some even point to software codes that did the work when applicable. Overlaying the architecture are constraints and schemas on every property that continue to evolve as the system is applied. The continuing evolution of <a href="https://www.wikidata.org/wiki/Wikidata:Lexicographical_data">lexicographical information</a> beyond concepts holds promise but demands even more multi-cultural involvement.</p><p>As with everything in the MediaWiki landscape, the whole system is inherently multilingual, and as an open source platform, new languages that can be encoded in standard ways can be incorporated. Wikipedia has individual instances in different languages, each completely independent and only loosely coupled, while Wikidata is designed to be a common global knowledge graph where concepts meet across language and culture. It is a grand experiment in whether such a notion is possible: can all the world’s knowledge come together in one place, make any sense, and not go somehow horribly wrong? And can we sustain it without the corrupting influence of commercial interests?</p><p>I’m starting, in small ways, to explore what the digital footprint of Indian Country is within the “Wikiverse” with a focus on Wikidata and a little bit of the connection to Wikipedia. I’m taking some actions through either code or one-off contributions as I find things that seem reasonable. My <a href="https://github.com/skybristol/indian_country_data">code</a>, which is mainly in Python notebooks, is open and unlicensed on GitHub. I’ll post additional Medium articles as I dig through major details.</p><p>One of the interesting dynamics in the Wikiverse aspect of the Global Knowledge Commons is the interplay with people everywhere contributing. When we come across something that we question, we have to acknowledge that someone somewhere recorded it for a reason. We may question the reason, and it may have resulted in something completely wrong or misleading. But we have to respect the fact that it’s there and it has been there for a while, live and online and available for anyone else to see and work with. It might have even become a dependency in someone’s workflow or an important reference for something someone has done. As such, we don’t want to just arbitrarily change things without some thought. The tech does a good job of keeping history, so we don’t actually lose anything and can always go back, but there can still be downstream implications to any change.</p><p>One of the first interesting cases I came across on this was where someone in France doing work on gender studies decided to make claims/assertions about the gender of scientists represented in Wikidata based on a list of common male and female first names. What a crazy thing to do in this day and age, right! One of my scientific colleagues was so incensed, she said the user should be banned from the Wikiverse for all time. Structurally, the gender claims had no references or qualifiers indicating how they came to be there; I had to track that down by looking at the history for when they showed up, figuring out the user account that had done it, and sleuthing around for information on the bot they wrote to do the work. I then got into a bit of an online argument in the Wikidata discussion space on the efficacy of the action, and it still hasn’t been undone.</p><p>A best practice is to essentially ignore any claim on any entity that does not have a reference. For referenced claims, we need to evaluate the viability of the references and decide whether we trust the source to support the claim. In essence, this is THE best practice for life online in any venue. Ethical use of any knowledge-base and particularly the Global Knowledge Commons as the external memory for AI demands this mindset and practice. If there’s not a clear connection between an assertion and its evidence along with anything interpretive that happened in between, we can’t trust the information.</p><h3>Current development focus</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SYEzZP2cX1p-4SAhkFVVlg.png" /><figcaption>Above and below are snapshots of two distinct entities in Wikidata that were both labeled Cherokee Nation. I modified one of these to try and clarify what it actually represents, though more work is needed to determine its provenance and significance. There’s much work to do for the way all Tribes are currently represented, including work on introducing the Cherokee language and other Native American written language as supported languages in the underlying technology. The examples highlight something from the previous section where you can see that none of the statements (claims) shown visibly provide any reference, a fundamental flaw that renders them essentially untrustworthy.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HPDEqAwvKXX58eljyqOLWA.png" /></figure><p>I’m currently focused on simply laying out a baseline for at least the 574 federally recognized Tribes in the U.S. and gaining an understanding of their overall footprint in the Global Knowledge Commons. I know this is just a start, and there are questions of State recognition and others to think about. I’m thinking mostly about Tribal sovereignty dynamics and the current disparities in things like how a U.S. State is documented and described in their digital representations within Wikipedia articles and structured claims in Wikidata vs. the representations of many Tribes. I look at the semantic dissonance issues where the articles and entities for some tribes conflate the identify of the people with the reservation lands they were confined to and occupy today.</p><p>I’m also guiding my work based on questions I’ve been curious about and tried to answer about Tribes in the U.S. but have been unable to address at scale. These are not historical questions but current things I’m interested in like understanding Tribal politics and business interests. For Tribal sovereignty to become fully realized, the United States has to get serious about the 574 “autonomous” governments operating within the United States. The U.S. Government, the 50 U.S. State governments, and numerous county and other local governments should all be operating on a footing of government-to-government relationships with sovereign Tribes. I think about the negotiations and agreements the Cherokee Nation is making with localities in Northeast Oklahoma on splitting law enforcement revenue from fines levied within the Reservation after the McGirt decision. I think about the recent election in Cherokee Nation, information on ballots cast, absentee voting, and other dynamics I have questions about. I think about language I see in government planning documents like Environmental Impact Statements that clearly indicates that Tribal consultations were not made on the basis of Tribal Sovereignty.</p><p>There are properties in Wikidata designed to capture claims about all kinds of interesting demographic, electorate, legal, and other characteristics. These are used by U.S. States, Territories, and other government/political entities. Tribes are different and should share different perspectives about themselves, but they need to be characterized in ways that are closer to how other government entities are described to help combat the notion that dealing with Tribes is a racial issue. There are racial dynamics involved, but they are not the basis for the relationship. We should challenge some of the notions of what it means to be a community and a sovereign nation at the same time, but we should also establish parity with other governments who we have relationships with such that we have a platform from which to develop shared understanding.</p><h3>Invitation</h3><p>I welcome collaborators from anywhere if you are interested in this work. I especially welcome engagement with Tribal members working on anything to do with data, information, and knowledge and particularly intersections with AI. You’ll find my most current work in <a href="https://github.com/skybristol/indian_country_data">GitHub</a> where you can connect. Feel free to post issues when you see something out of whack.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1162ce42c465" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ESIP Winter Meeting 2023 — remarks]]></title>
            <link>https://medium.com/@skybristol/esip-winter-meeting-2023-remarks-7db456c6aa4e?source=rss-b947a36d30f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/7db456c6aa4e</guid>
            <category><![CDATA[esip]]></category>
            <category><![CDATA[indigenous-knowledge]]></category>
            <category><![CDATA[digital-twin]]></category>
            <category><![CDATA[bears-ears-monument]]></category>
            <dc:creator><![CDATA[Sky Bristol]]></dc:creator>
            <pubDate>Thu, 26 Jan 2023 22:30:43 GMT</pubDate>
            <atom:updated>2023-01-26T23:14:51.291Z</atom:updated>
            <content:encoded><![CDATA[<h3>ESIP Winter Meeting 2023 — remarks</h3><p>The following is the written form of a brief talk I am giving at the <a href="https://2023januaryesipmeeting.sched.com/info">ESIP Winter Meeting</a> this year. I was asked to share some perspectives in the State of the Federation <a href="https://2023januaryesipmeeting.sched.com/event/1EwYU/closing-plenary-state-of-esip-peer-recognition-ceremony">closing plenary</a> at the end of the week, partly from my perspective as a USGS champion for ESIP but my own thoughts. I post those thoughts here, which are my own and written on my own time, to provide a reference point for anyone interested in followup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VmaV6cpa7OgEeVP1036HCQ.jpeg" /><figcaption>View of the Bears Ears</figcaption></figure><p>Thank you for giving me another opportunity to speak at the end of an ESIP Winter Meeting week as we reflect on the “State of the Federation.” I’m grateful no one has ever given me a script to follow or a framework for these talks. I’m not sure I would follow it anyway.</p><p>Nominally, I might share something about the status of USGS and our goings on that may be of interest to the community or possibly announcements about important new initiatives. I could do that, but for the next few minutes, I’d like to share a couple of quick stories, a few perspectives, and some questions to ponder that come from my experiences with USGS and our time together this week. These are my own thoughts and words, but I feel confident in the support of my institution.</p><p>When I moved to USGS from the U.S. Fish and Wildlife Service in 2004, one of my first tasks was to develop a group from across our scientific disciplines and organizations that would help advise on integrated science and associated data and information matters. Being fresh to the organization, I was anxious to strut my stuff and start making my mark. I wrote up a “brilliant” 5-page vision for what this group would look like, how we’d operate, and what influence we would have. I contacted folks from different organizations whom I learned about and thought could represent their particular areas. At our first meeting, an older geologist named <a href="https://www.linkedin.com/in/douglas-stoeser-446626116/">Doug Stoeser</a>, looked at me across the table and over the top of the print-out he’d made of my document and said something to the effect of, “Yep, I figured some kid under 30 wrote this thing.” (Hey, I was 29; that’s almost 30!)</p><p>Some years later, I was part of the process for reorganizing from our long history of balkanized academic disciplines into Mission Areas that were sparked from strategic science planning geared more toward the way we address societal challenges. Part of this involved getting out and talking to researchers and other folks “in the field” about what we were doing, gathering input toward how we needed to be doing things over the next decade. This was several years after the major reorganization and shuffling of the management deck chairs. I was hit several times by essentially the same kind of statement. “Wait, what? I’m not part of the Geology Division anymore? When did that happen?”</p><p>Some years later still, I’m now at a point where I’ve figured out a new job where I’m keeping a lower profile and not paying much attention to all the headquarters folderol. Even though I’m nominally in a pretty high level headquarters position, I’ve been given the latitude to not worry about that stuff so much anymore. I’m now that guy that’s out of touch with all the machinations of running the organization, and I’m also old and experienced enough that I have quite a few Southern style “bless your heart” moments with younger staff.</p><p>I share these stories as a simple way to illustrate the very different ways of knowing that make the USGS and all our organizations tick. It’s a diversity of ways of knowing and different knowledges that I want to share a few thoughts about.</p><p>While reflecting and planning my remarks yesterday, I was thinking about the interesting bracketing of this meeting, with the energizing <a href="https://2023januaryesipmeeting.sched.com/event/1EwX5/opening-plenary">opening plenary</a> from <a href="https://rebeccaheiss.com/">Rebecca Heiss</a> to the panel discussion yesterday on <a href="https://2023januaryesipmeeting.sched.com/event/1EwX8/plenary-digital-twins-for-earth-systems-past-present-and-future">digital twins</a>.</p><p>Rebecca led us through a journey of understanding and acknowledging our evolutionary roots and instinctive reactions, where we conjure tigers chasing us through the forest when facing rejection to our ideas at work or home. We learned to reset our minds and emotions through <strong>activating adventure alternatives</strong>, <strong>breathing</strong>, and <strong>flipping fear to curiosity</strong>.</p><p>My wife has been studying and developing practices around this dynamic for some time, and so we talk about it from time to time. Through her way of knowing, she puts more emphasis on the mystical and metaphysical aspects of human evolution with a greater focus on ceremonies that help us “learn the ABCs.” One of her practices is <a href="https://www.tarabrach.com/rain/">RAIN</a>, a meditative method from Tara Brach, to achieve the same effect as Rebecca’s ABCs in her own mind and body.</p><p>In yesterday’s plenary, there were some sidebar comments, perhaps slightly tongue in cheek, about whether Digital Twins should incorporate sound and smell; why not taste and touch. I would wager that indigenous people here and around the world would simply state, “Of course it must. How can we experience the Earth without our whole selves?”</p><p><strong>I was also pondering the question yesterday — is a digital twin of the earth system a source of information or a source of knowledge?</strong></p><p>It doesn’t have to be either/or, I suppose, but the applied part of the digital twin venture, beyond the purely academic and engineering pursuit, is to be a source of knowledge and insight, hopefully leading toward wiser choices as a species that will be struggling to evolve for many millennia hence (assuming we last that long).</p><p><strong>So then, will digital twins be sources of knowledge or sources of knowledges?</strong></p><p>This seemingly simple change from singular to plural exemplifies a divide that exists between a mostly western, global north, reductionist scientific mindset and indigenous ways of knowing that have striking connections between first nations cultures around the world.</p><p>I would argue that the future health and wellbeing of our planet relies on us embracing the reality that there are many ways of knowing. This means regularly and intentionally stilling our minds and voices, immersing ourselves in knowledges foreign to us with an openness to challenging and expanding our understanding. I suggest that the future of research and development in the pursuit of the digital earth must be about continually improving a source of knowledges.</p><p>Couple this with embracing the inevitable imperfections and uncertainties in a digital twin of the earth that <a href="https://www.geog.ucsb.edu/people/faculty/michael-goodchild">Mike Goodchild</a> talked about. This means a richer rather than a poorer digital twin of the earth. It means living in a sense of wonder and adventure, of exploring or simply sitting in quiet reflection with as much of the whole complex earth system as our minds and bodies can experience. It means reveling in science as the infinite game, how <a href="https://ronininstitute.org/research-scholars/bruce-caron/">Bruce Caron</a> put it in his <a href="https://openscientist.pubpub.org/pub/play/release/2">Open Scientist Handbook</a>, invoking <a href="https://simonsinek.com/">Simon Sinek</a>. It means coming to science with all of our formal training, yes — but also all of our senses open to observation and measurement, all of our emotion, and all that is deeply embedded in our DNA and biochemistry.</p><p><strong>Perhaps even, the digital representation of our intermingled knowledges suggests a fifth dimension to what’s now focused on the 4D digital earth.</strong></p><p>In a very real and tangible way, we have a living laboratory for this type of digital twin right near my own backyard. With the restoration of the full <a href="https://en.wikipedia.org/wiki/Bears_Ears_National_Monument">Bears Ears National Monument</a> and the <a href="https://www.doi.gov/pressreleases/blm-forest-service-and-five-tribes-bears-ears-commission-commit-historic-co-management">historic</a> multi-nations <a href="https://www.blm.gov/sites/blm.gov/files/docs/2022-06/BearsEarsNationalMonumentInter-GovernmentalAgreement2022.pdf">agreement</a> to co-manage the monument between the Hopi Tribe, Navajo Nation, Ute Mountain Ute Tribe, Ute Indian Tribe of the Uintah and Ouray Reservation, the Pueblo of Zuni, and the United States, we are intentionally learning and combining multiple knowledges to affect healing, restoration, and responsible stewardship of the earth. That means setting aside, for a time, but then including again with more understanding, such simplistic characterizations as “1.36 million acres of land surface” as we learn and embrace not only what these lands meant to the indigenous people thousands of years ago but what they mean now in our shared history and what they promise for the future.</p><p><em>I would go so far as to suggest that ethical research and development of the Digital Twin means embracing and working with our indigenous research colleagues in this type of living laboratory first. I say this particularly because we have much to address in decolonization efforts with regard to how data and “science” have been used to fuel institutionalized theft and repression of indigenous peoples and communities globally.</em></p><p>I leave you with a statement from <a href="http://moore2019.blog.anat.org.au/">Dr. Sarah Jane Moore</a> at the University of New South Wales that she included in a 2020 report, coauthored with Yulia Nesterova, to UNESCO on “<a href="https://unesdoc.unesco.org/ark:/48223/pf0000374046">Indigenous knowledges and ways of knowing for a sustainable living</a>.” I also pose a question and a challenge:</p><p><strong>Where and when and how, as we explore the Digital Twin of the Earth, will we experience this way of knowing?</strong></p><blockquote><em>I write from nipaluna, Hobart in lutruwita Tasmania, Australia. I overlook timtumili minanya, River Derwent from a land as ancient as the skies. I tell stories that tap into futures informed by the oldest continuing and living cultures imaginable. My worlding draws on connection to place, space and time. The stories I tell conjure oral histories and told cultures whose murmurings hover in living memory. They shadow the written word and illuminate precious knowledge. I shine light on caves of understanding that are as old as the sun. I hurl my knowledge spears on and through and into 2050. I embrace past, present and future. My spears sense bright futures with high standards of caring for Country and ourselves. My spears sense hearts bursting with curiosity, cultural pride and deep joy. My spears sense reformed, connected communities. I launch in hope.</em></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7db456c6aa4e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Trails and the Conservation Estate]]></title>
            <link>https://medium.com/@skybristol/trails-and-the-conservation-estate-467889ed2f3d?source=rss-b947a36d30f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/467889ed2f3d</guid>
            <category><![CDATA[public-lands]]></category>
            <category><![CDATA[conservation]]></category>
            <category><![CDATA[stewardship-principle]]></category>
            <category><![CDATA[trails]]></category>
            <dc:creator><![CDATA[Sky Bristol]]></dc:creator>
            <pubDate>Fri, 09 Sep 2022 13:54:04 GMT</pubDate>
            <atom:updated>2022-09-09T13:54:04.098Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*w2BPIkva3HMnT6sY" /><figcaption>Part of a trail maintained for ATVs less than 50&quot; in the Grand Mesa National Forest.</figcaption></figure><p>I live in a part of Colorado now where I feel incredibly fortunate and almost infinitely wealthy. After almost 20 years on the Colorado Front Range, we moved to the Western Slope where we are much less crowded and life moves at a slower pace. For me, it’s moving <em>back</em> to this side of the mountains since I spent much of my youth growing up in Durango.</p><p>I feel wealthy here because we live in the middle of an amazing swath of our Nation’s Conservation Estate that is as readily accessible as the now tiny patch of backyard that I own as an individual. Nearly 3/4 of our county is public land, including National Forests and National Conservation Areas managed by the U.S. Federal Government, many parks and wildlife areas managed by the State of Colorado, and many small patches of important habitat owned and managed by nonprofit conservation organizations. That is all land and water rich with natural and cultural heritage resources that is collectively owned by all of us for enjoyment, contemplation, and activism.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nknxea86jVSK9Cm0Hlw84w.png" /><figcaption>Within a very short drive, we can access so much of our big backyard, parts of the Conservation Estate that we can explore, care for, and find balance in our busy lives.</figcaption></figure><p>I’ve spent much of my career thinking about and working on the digital representation of these areas based on scientific observation, monitoring, and study leading toward balanced decision-making on the best ways to manage the diverse resources, uses, and needs of our species and the planet as a whole. I’m still thinking about those things and working toward ways that we can make the digital representation more full, rich, and inclusive such that all people everywhere have a better opportunity to actively engage in our collective stewardship responsibilities as co-owners. I’ll write further about that specific technical exploration in other articles, but I want to first reflect a bit here on human trails through our public lands — what those are and what they mean.</p><p>Over the last couple months this summer, we’ve been out exploring trails in the <a href="https://www.blm.gov/programs/national-conservation-lands/colorado/gunnison-gorge-nca">Gunnison Gorge National Conservation Area</a>, where we’ve been volunteering with the <a href="https://www.coloradocanyonsassociation.org/">Colorado Canyons Association</a>’s <a href="https://www.coloradocanyonsassociation.org/adoptatrail">Adopt-a-Trail</a> program. In late August, we risked the still hot weather to camp for a few days along the Gunnison River in the northern part of the NCA. This gave us an opportunity to spend quality time on several of the NCA’s hiking and motorized trails.</p><p>We used a combination of foot, bike, and ATV power to enjoy all or the majority of 7+ trails over the course of our several days along with floats on the river in our kayaks, fishing in the gold medal waters, and relaxing under the cottonwoods in the hot afternoons. We enjoyed some lovely summer thunder showers a couple of evenings and nights, which was quite a relief from the heat.</p><p>The major draw for humans in the area we camped is the lower part of the <a href="https://coloradogoldmedalwater.tu.org/gold-medal-waters/">Gold Medal Waters</a> section of the Gunnison River. Flyfisher-folk on dories and rafts and all manner of wading gear made up most of the humans we saw and occasionally chatted with. I did a little of my own fishing, though I’m not so skilled in that area, and managed to snag a couple of brown trout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TcckiCKKtqEa0RcM" /><figcaption>Near the top of Crocodile Rock Trail in the Gunnison Gorge National Conservation Area on a beautiful day for hiking with an overnight thunderstorm bringing welcome relief from the late summer heat.</figcaption></figure><p>But the area also gave us ready access to Birthday Canyon, Crocodile Rock, Cool Rock, Sun Cliff, and other trails. On the digital side of things, I took advantage of our Starlink internet connection and ample solar power to continue exploring data and information available now in the public domain for the trails we were exploring (and picking up some trash from). I continued to be impressed by what one fellow hiker from somewhere in our area has done over the years in <a href="https://www.gjhikes.com/">recording trips</a> on so many trails here in the Four Corners. That’s just one example of a passionate explorer recording personal and shared adventures and observations.</p><p>Looking online, I find other examples, around this country and around the world, of people like that, excited about sharing their experiences. Newer platforms make it as simple as can be to record photos or videos, add a caption, and share a snippet of experience. More structured digital environments, like the <a href="https://naturalatlas.com/">Natural Atlas</a> app that I’ve been growing quite fond of or <a href="https://www.inaturalist.org/pages/seek_app">Seek from iNaturalist</a> that I also use, open up all kinds of new possibilities for increasing the richness of how our conservation estate is represented and recorded over time in digital data.</p><p>So, what is the Conservation Estate? It’s a term that shows up in different ways around the world, mostly in legal terms. The term, <em>conservation</em>, in this context, contrasts with <em>preservation</em> and refers to a set of principles that directly relate to management for the sake of humans living in and as part of the “natural world.” We often conserve resources for our use as human populations, such as damming up a river and creating a reservoir for irrigation or potable water supply. We put laws in place to govern these actions and create instruments like Water Conservation Districts to oversee how laws and regulations are carried out in practice.</p><p>Preservation is an ideal that we pursue where we try to cordon off specific areas of our lands and waters in an attempt to maintain some semblance of what those areas might have been like without humans being so impactful. Wilderness designations in terrestrial areas and marine preserves of various kinds are legal instruments we employ for trying to set aside whole parts of ecosystems. We create zoos and wildlife sanctuaries in an attempt to preserve individual species at risk.</p><p>The reality, of course, is that the human species has succeeded so completely, evolutionarily, that we are the dominant force on the planet; in the absolute primary position to <a href="https://www.anthropocenemagazine.org/">drive global change</a>. At the same time, we’ve evolved as a thinking and reasoning species, with an ability to make choices about what we do and how the various societies in which we organize ourselves are going to be governed. Though it sometimes seems chaotic in our short lifespans, with whole parts of our organizational systems seeming to regress back to acting out of base instinct, we are slowly progressing toward a greater level of harmony with ourselves and the other species on our planet.</p><p>So, as the dominant species with a population growing quickly toward 10 billion, which may or may not plateau somewhere in that area, it is really about conservation at this point with some degree of pursuing the preservation ideal. We impact everything and every species on the planet at both big and small scales through the decisions we make, individually and as societies. Perhaps we might reason our way to better decisions if we individually start consistently thinking about and taking seriously our role as co-owners of the Conservation Estate, that part of the world that we decide we want to own together as opposed to individually.</p><p>Joining up with CCA’s adopt-a-trail program and exploring trails in a part of the estate here close to home, I’ve been thinking about the role of trails in that dynamic. Our trails on public lands like the NCAs and National Forests are the pathways for human incursion into the wilderness. They are roads created by us in our various pursuits from mining, logging, and other resource harvesting to specific constructions for recreation. They follow terrain that is accessible for us in our various states of health and capacity and into and through features we find interesting or compelling for one motivation or another. Quite often the trails we follow today within some management jurisdiction and with whatever name or numeric designation someone decided to put on them are the same trails people have followed for thousands of years because they make sense for human travel.</p><p>As humans, we have choices to make about trails. Individually and at small scales, we can decide to <a href="https://lnt.org/why/7-principles/">follow the path or not, pick up after our dogs, and carry out what we carry in</a>. Collectively and at larger scales, we can participate in the governance and management process, influencing laws that regulate policy on where new trails go, where trails need to be removed and reclaimed, and how trails can be used. We can be part of planning and implementation as well because we’ve enacted laws that ensure government agencies we’ve put in place to manage resources in the public trust have to consult with us and open up their internal processes for participation and scrutiny. We can create and participate in non-governmental organizations that also collectively own and care for parts of the conservation estate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SiKfpa1rDj0L73_t" /><figcaption>Part of the Silver Spruce Trail in the Grand Mesa National Forest winding through sections of beautiful aspen and deeply shaded spruce; designated for use by ATVs under 50&quot; and maintained by the Western Slope ATV Association.</figcaption></figure><p>Something I’m thinking about lately is the inevitability of humans treading on and occupying basically every square meter of the planet. If you spend time in the outdoors, you probably have a handful or maybe many places that you consider to be your very own slice of heaven on earth. These are the places where we reconnect with some deep part of our evolutionary history, re-centering and grounding ourselves in our place on the planet. You may jealously guard these secrets, hoping that no one else ever finds out about them so that they can remain yours alone. If you’ve ever been back to one of those after some time has past to find that someone else has been there and left their mark, you may feel violated and that a part of you has been wounded in some way.</p><p>This kind of inevitable dynamic can produce an us vs. them mindset, especially when we find something so egregious and damaging like human feces scattered about, wanton destruction of the landscape, and other things we humans do in our carelessness. As I’m thinking about trying to make data and information about these places, their digital representation, more clear and accessible in the public domain through automated means of curating public and yet obfuscated data sources, I worry sometimes that it may result in more opportunity for thoughtless vs. thoughtful human behavior. But for the most part, I do believe that more complete and better quality information in the public domain will lead to better governance and broader participation in resource stewardship.</p><p>I think we often feel powerless in a world grown so large so quickly where it seems that we can have so little real influence. In a time when it has become so easy to spin tall tales online in ways that seem to make many people believe things that are false or nonexistent, it feels hard and yet vitally important to counterbalance that with more immediately usable organization of the digital representation of reality. Putting some energy into this with data and information about trails to turn that into a knowledge representation is something I think I can do a little bit about, chipping away at a problem that seems tractable. Lots of other people and groups are already working away in this space, so I’ll try to tackle a side of the problem that compliments those efforts but fills in some important gaps. I’ll write about those efforts here in future articles and share technical details about what I’m pursuing.</p><p>In the meantime, get out and enjoy a trail somewhere in your own slice of our big backyard. Use whatever mode of transport makes most sense for you and the designation of the trail, but do it thoughtfully as to your impact on the habitat and your ability to ground yourself in your place on the planet. Note what other people have been there and done, and care for the area as you would your own home — because it is part of your home but one shared with the rest of us.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=467889ed2f3d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Contributing to the global knowledge commons]]></title>
            <link>https://medium.com/@skybristol/contributing-to-the-global-knowledge-commons-2e48ec61e383?source=rss-b947a36d30f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e48ec61e383</guid>
            <category><![CDATA[wikidata]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[public-domain]]></category>
            <category><![CDATA[open-government-data]]></category>
            <category><![CDATA[ice-cream]]></category>
            <dc:creator><![CDATA[Sky Bristol]]></dc:creator>
            <pubDate>Fri, 24 Jun 2022 14:59:33 GMT</pubDate>
            <atom:updated>2022-06-24T14:59:33.020Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*l85nXS0R9CFphmuv" /><figcaption><a href="https://commons.wikimedia.org/wiki/File:A_ludicrous_prohibition_-_geograph.org.uk_-_2035205.jpg">https://commons.wikimedia.org/wiki/File:A_ludicrous_prohibition_-_geograph.org.uk_-_2035205.jpg</a></figcaption></figure><p>Wikidata is the most comprehensive and far-reaching reality of the global <a href="https://en.wikipedia.org/wiki/Knowledge_commons">knowledge commons</a> that we have built so far. It’s not just Wikidata itself but all of the linkages to other components in the Wikiverse and third party partners, like OpenStreetMap that I’ve been exploring in my last couple of articles. While there is likely more quantity and perhaps higher quality information in Google’s Knowledge Graph and other commercial and pseudo-commercial ventures, those are not truly part of the commons. They may be adjacent enterprises and have linkages with the commons, but they are not owned and operated by the public. Rather, they leech information from the public domain and monetize it for their own aims.</p><p>In this article, I further explore modeling data about trails on public lands in Wikidata by delving into some additional properties and how those are structured. I track down a couple of interesting dynamics in how information content comes to be in Wikidata by tracing out the “no ice cream” activity policy. This leads me to some interesting thinking on the ramifications of government data, information, and knowledge in relation to the knowledge commons.</p><h3>Modeling Trail Properties in Wikidata</h3><p>I spent a bit more time working through trail documentation on my quest to determine if we can use Wikidata as a comprehensive public domain database for this kind of information. A little bit of poking around got me to the <a href="https://www.wikidata.org/wiki/Q51728742">activity policy</a> concept and the <a href="https://www.wikidata.org/wiki/Property:P5023">activity policy in this place</a> property. This is what others have used to describe all the authorized (or available) and prohibited activities for a trail or some other feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/412/1*tR50CRwKpivcTh9IWFL-fA.png" /></figure><p>It’s fascinating to dig into what people have done in trying to organize specific information within the Wikidata setting where thousands of contributors coming from many different language and cultural settings are trying to create a semantically explicit global database. How do you properly and comprehensively document something like off-highway vehicle riding as human recreational activity?</p><p>OpenStreetMap is dealing with this dynamic too, of course. I messed around with the <a href="https://www.wikidata.org/wiki/Property:P1282">OpenStreetMap tag or key</a> property a bit to connect some dots in the mapping direction, which brings up a whole other issue of harmonizing between different ways of describing the same basic domain. There are different levels of logical semantic granularity between looking at map feature properties and symbology or information content about the concept of a trail apart from its geospatial reality.</p><p>I also noted again the interesting dynamic of how people contribute content to Wikidata from their particular perspective and specific use case. In further documenting my Chukar Trail test case, I added <a href="https://www.wikidata.org/wiki/Q112685319">horse riding allowed</a> and <a href="https://www.wikidata.org/wiki/Q112685379">horse riding not allowed</a> along with <a href="https://www.wikidata.org/wiki/Q112685517">off-road vehicles allowed</a> and <a href="https://www.wikidata.org/wiki/Q112685492">off-road vehicles not allowed</a>. I still have work to do on all the other activity policies I can confidently cite to a reference.</p><p>Looking at the <a href="https://w.wiki/5LgL">current instances of allowed activities</a> is really quite fascinating. There are some interesting linguistic and locality phenomena like <a href="https://www.wikidata.org/wiki/Q67600253">no trolleys</a>, where having someone put the time into connecting to an icon or image in Wikimedia Commons is super helpful.</p><p>I find the over time evolution of the Wikidata knowledge bank to be truly fascinating. Just dealing so far with horse riding and ATVs on public land, I worked through the dynamic of “what has someone already documented and how should I best fit my own new piece of information?” The most closely associated topic for my horse riding activity policy was <a href="https://www.wikidata.org/wiki/Q179226">equestrianism</a>, so I made my new thing a facet of that and added aliases so there is a linguistic connection as well. Maybe someone in the future would want to use “equestrianism allowed” instead of “horse riding allowed” to convey the same information.</p><p>I made <a href="https://www.wikidata.org/wiki/Q112685517">off-road vehicles allowed</a> and its counterpart both facets of <a href="https://www.wikidata.org/wiki/Q946596">off-road vehicle</a> and <a href="https://www.wikidata.org/wiki/Q210988">all-terrain vehicle</a> (a subclass of off-road vehicle). In my current use case of documenting something specific for a BLM-managed public land unit, these mean slightly different things. I still need to deal with off-road motorcycles as a different type of authorized or not authorized activity. Motocross is logically just a different type of off-road/off-highway vehicle, but listing this “mode of transport” as allowed or not separately from ATVs and other types of off-road vehicles is important in the context of documenting trails.</p><p>We likely need to go even deeper and document the maximum width of recreational conveyances allowed on trails. For some trails there’s also now the dynamic of documenting whether or not electric bikes are allowed. All of these also have temporal dynamics that can be seasonal allowances or things that were once allowed and no longer are but may be again. Wikidata mostly has the model to support these if we want to get that specific, but it will take some experimentation and application in practice to determine the best way to go.</p><h3>The No Ice Cream Policy</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/220/0*m3pWi_6vgO9xhxNz.jpg" /></figure><p>The <a href="https://www.wikidata.org/wiki/Q67601027">no ice cream</a> activity policy makes for an interesting exploration into how things come to be documented in Wikidata. It’s only been applied as a value on one item, the <a href="https://www.wikidata.org/wiki/Q6974517">Nationaal Museum van de Weerstand</a> in Belgium. That activity policy, along with others like <a href="https://www.wikidata.org/wiki/Q66361370">cellphones not allowed</a>, for the museum entity are flagged as having an issue in that they are not referenced.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h1YoPmNVD76Zbswy9sxKZw.png" /></figure><p>Referencing sources in some citable fashion is a huge part of the Wikiverse evolution and a major sticking point for some types of serious usability. It comes down to questions of trust and preponderance of evidence. Is there enough evidence that this statement is true and that its contributor put the time and energy into verifying it that I can count on it for my purpose? Wikidata can potentially be a robust resource to use in building artificial intelligences for entity recognition and particularly explicit or linked entity recognition where we point back to a source of definition and ontology. However, it can also be a source of massive uncertainty if not handled thoughtfully.</p><p>One way to do that is to leverage one of the incredibly powerful aspects of the Wikidata infrastructure in its robust and granular provenance tracking. We can see that the user, <a href="https://www.wikidata.org/wiki/User:Trade">Trade</a>, contributed the information on activity policies at the military museum, including no ice cream.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1A75qEmknwRh54T89utcEQ.png" /></figure><p>We can also see that Trade was the originator of the no ice cream activity policy entity around the same time he was probably documenting the museum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vJQyypsUjHH9H2g4s2LgEg.png" /></figure><p>Trade added a helpful image showing what a No Ice Cream sign looks like when he created the entity, which is cool. Tracking things a little further through the Wikiverse, we see this <a href="https://commons.wikimedia.org/wiki/File:Sch%C3%ABld_um_Resistenzmus%C3%A9e_(cropped,_no_ice_cream).jpg">image in Wikimedia Commons</a>. It was cropped from a larger image showing allowed and not allowed activities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rE4J2oZPuzgvwU7J.jpg" /></figure><p>Looking at the history of the no ice cream image, we see that Trade was the one who cropped it from the image provided by another contributor.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yhFpfyVEA-zarA82Za1xTg.png" /></figure><p>Interestingly enough, the four allowed and prohibited activities shown in the original photograph from which no ice cream was derived aligns with all four of the activity policies from the museum record. Descriptions for both the original photo and derivative provide a further useful piece of information in Luxembourgish, which I had to go run through Google Translate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WxU34zkpkKtKLngHocjs2A.png" /></figure><p>But we also have a link to where that image seems to have originated, a different <a href="https://lb.wikipedia.org/wiki/Nationale_Resistenzmus%C3%A9e">museum</a> in Luxembourg, which also has a <a href="https://www.wikidata.org/wiki/Q6978080">Wikidata entity</a>. The World War II museum in Luxembourg does not have any information about activity policies at this time.</p><p>So, what we have here is almost (but not quite) an interesting chain of evidence leading to a reference backing up Trade’s claim about the activity policies at the Belgian museum. Perhaps the <a href="https://commons.wikimedia.org/wiki/File:Sch%C3%ABld_um_Resistenzmus%C3%A9e.jpg">four-policy</a> symbol that contributor <a href="https://commons.wikimedia.org/wiki/User:Jwh">Jwh</a> added to Wikimedia Commons clear back in 2014 is common signage at museums in that part of Europe. Perhaps taken together it actually means something different than when picked apart —</p><blockquote>We’re okay with you walking your dog on a leash, but we don’t want you holding an ice cream cone in the other hand because you might drop it on something important; at the same time, it’s okay for you to take pictures with a separate camera (if anyone still has one of those), but we don’t want you using your mobile phone.</blockquote><p>In this case, though, we still have no evidence contributed in the form of a reference to let us know that the Nationaal Museum van de Weerstand in Van Lintstraat Anderlecht actually has the activity policies that Trade has claimed. The image is closer to being a reference of activity policies at the National Resistance Museum, Luxembourg. Interestingly enough, if we did put all these pieces together, we also have a temporal qualifier indicating that the policy was perhaps in effect in sometime around 2014–06–07T10:03:51 when Jwh posted it, but we have no idea if it is still in place — or if ice cream in a cup is now allowed but not a cone as long as you’re not walking your dog at the same time.</p><p>Perhaps more deeply though, we might need to examine whether No Ice Cream is indeed an appropriate activity type for a policy. We don’t actually know that the symbol captured from the Luxembourg museum means no ice cream. It could actually mean no food or no food or drink. More careful research and curation in developing the knowledge commons would be useful, though that has to be balanced so as to be a helpful rather than detrimental throttle on quantity. Following a simple rule like, “never create an activity policy entity without considering whether to create its converse” could be a useful thing to apply. Is there such a thing as “food and drink allowed,” or is it “food and drink encouraged?”</p><h3>Making Claims With and Without Evidence</h3><p>That word, claim, is super important in Wikidata. Claim is what statement is called at the API level. That’s what every property on an entity is — a claim that some particular contributor, human or bot, has made about the entity. As a consumer wanting to use the information, you have to decide whether or not you trust the claim to be valid for your particular need.</p><p>Maybe something like “no ice cream” as an activity policy is not that important to all that many uses. After all, it’s only ever been used once so far. But it actually might be important if the no ice cream policy was asserted for enough other museums and you were trying to do some market research to figure out where you might open up an ice cream shop.</p><p>I worked through another one of these cases some time ago when I came across a case where a contributor had written a bot that used a database of typically male and female first names to assign gender claims to thousands of Wikidata entities for people. We had a <a href="https://www.wikidata.org/wiki/Property_talk:P21#Constraints_on_citation">brief debate</a> on the inappropriateness of this type of bot, but no corrective action has yet been taken.</p><p>I can understand the reasoning for that kind of derived coding in data if a researcher is doing something like studying gender discrepancies in professions. Lacking more authoritative sourcing for the gender of identified individuals, someone might use a “typical names” approach as one way to get at this information. Statistically at a large enough sample size, this might yield reasonable information for analysis. However, when taken clear down to the level of assigning a gender claim semi-permanently to individual records is reckless and inappropriate.</p><p>In the gender value assignment case, the contributor was writing bots to try and improve Wikidata information. That’s great, but it needs to be done responsibly and with peer review. One problem is that the peer review process may take a long time in such a large and diverse system as a global knowledge bank. That’s why I see mostly arguments against trying to use Wikidata for something “real” that we want to count on, particularly from government data folks who tend to rely on older modes of determining trustworthiness through somewhat arbitrary and perhaps detrimental modes of assigning authoritativeness.</p><h3>Government in the Knowledge Commons</h3><p>However, as I pointed out in another <a href="https://medium.com/@skybristol/public-lands-data-stewardship-db5e15a89ec8">recent article</a>, just because something comes from a supposedly authoritative source that doesn’t make it correct. Mistakes happen everywhere. Careful review processes that are mandated for most government data and information released publicly do help in quality control, but they don’t catch everything. This is why I think it would be incredibly powerful to have more institutions who are responsible for some slice of information with connections to the “global <a href="https://en.wikipedia.org/wiki/Knowledge_commons">knowledge commons</a>” force themselves to deliberately contribute/donate that content to Wikidata and other components of the commons. The value in the discipline of that as a forcing factor toward greater accuracy and fidelity in our public domain data sources cannot be overstated.</p><p>I’ll do some more research and writing on the dynamic of official institutions, government or otherwise, leveraging Wikidata as both a place to project data, information, and knowledge and use it as a resource. This is being done in a number of cases I know about, mostly tied to academic research. There would be incredible resistance to the idea of most US Government agencies doing anything official with Wikidata and likely a fair bit of resistance from the global Wikidata community in accepting contributions directly from Government, though a whole lot of information sourced from Governments is already there. But I think both of these are things that can and need to be resolved.</p><p>Governments need to not “rest on their laurels” as absolute authorities for certain kinds of information that are logically in the commons. Donation of data into the public domain, which is what happens with US Government agencies that are prohibited from holding US copyright, needs to become an active rather than passive process. Government agencies need to take responsibility for checking their sources of knowledge against other sources of knowledge by actively linking them into the commons. Doing so, will improve government sources and improve the knowledge commons. Not doing so but flooding the “market” with massive amounts of unlinked stuff is continuing to perpetuate the problems of data and information collisions and subsequent erosion of the public trust.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e48ec61e383" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Public Lands Data Stewardship]]></title>
            <link>https://medium.com/@skybristol/public-lands-data-stewardship-db5e15a89ec8?source=rss-b947a36d30f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/db5e15a89ec8</guid>
            <category><![CDATA[public-lands]]></category>
            <category><![CDATA[stewardship-mentality]]></category>
            <category><![CDATA[public-trust-doctrine]]></category>
            <category><![CDATA[open-data]]></category>
            <category><![CDATA[indigenous-data]]></category>
            <dc:creator><![CDATA[Sky Bristol]]></dc:creator>
            <pubDate>Wed, 22 Jun 2022 23:03:20 GMT</pubDate>
            <atom:updated>2022-06-22T23:03:20.295Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M-N2WYSTbL0FDlDfDRcqAA.jpeg" /><figcaption>Late spring wild sunflowers in the San Juans</figcaption></figure><p>Following up from yesterday’s <a href="https://medium.com/@skybristol/public-lands-stewardship-ethic-and-linked-open-data-2f5013acf8d8">story</a>, I decided to spend a little time exploring the linked data situation for a particular test case. My premise here is that a part of public lands stewardship could be data stewardship. We can consider data about our public lands to be a digital representation or manifestation of those lands, and I’ve long felt that data collected from or describing our public lands is equally important as a public trust resource.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*V03w5LtZee_J2Q06.png" /><figcaption>From a Cornell University blog on Public Trust Practice (<a href="https://blogs.cornell.edu/publictrustpractice/public-trust-concepts/">https://blogs.cornell.edu/publictrustpractice/public-trust-concepts/</a>)</figcaption></figure><h3>Public Trust Doctrine</h3><p>Very early in my career as a civil servant, I received a lesson in the Public Trust Doctrine from my boss at the time. I was a young student field tech in the U.S. Fish and Wildlife Service. I was given some responsibility for drafting up sections of reports on our field studies, examining the impacts of environmental contaminants on fish and wildlife resources. I wrote some text where I used the phrase, “trust resources,” but ascribed them to the Bureau within rather than the Agency of the U.S. Department of the Interior. I had a great mentor at the time who took the time to explain how the government was structured, what the public trust was all about, and how we needed to document and report on what we discovered in our work as government scientists. That interaction set me on a particular course for a long and rambling career in doing what I can to uphold that trust.</p><p>The Cornell Legal Information Institute defines the public trust doctrine as:</p><blockquote>The principle that certain natural and cultural resources are preserved for public use, and that the government owns and must protect and maintain these resources for the public’s use.</blockquote><p>In a country and society where one of our highest ideals is that the government is to be “of the people, by the people, and for the people,” we are all stewards operating under the public trust doctrine. We certainly hire and pay people like BLM Range Conservation Officers, Park Rangers, Interpretive Specialists, and others to take on full time dedicated roles in the public trust. But every member of the public can and should play a part as both a user and beneficiary of the public trust but also a contributor. The very least we should strive for is being “net zero users” where we use resources in the trust without destroying or degrading them. But what are all of the ways we can be responsible stewards and trustees, leveraging the resources in the public trust in a way that creates a net gain for the planet and for our societies?</p><h3>Public Domain Data Curation</h3><p>As discussed in my article yesterday, there are quite a number of commercial interests competing for consumers in the data and mapping space. I don’t begrudge any of these interests at all, and I’m perfectly happy as one of those consumers to pay for a good product. Those investments often result in great innovation and powerful capabilities that make our lives better and contribute to human progress.</p><p>But there is also an important place for data in the public domain, meaning data that are completely free from any restrictions on use by anyone, including commercial interests. Government institutions in the U.S. are in a somewhat unique position in the world in that our Federal government (and many State governments) are prohibited from holding copyright. This means that nearly every piece of data and information produced at taxpayer expense in the U.S. is donated into the public domain. This supports a tremendous amount of activity across commercial, academic, nonprofit, and other sectors. Open data policies put in place across the last couple of decades have resulted in massive amounts of new and legacy government data being released “into the wild.”</p><p>The problem we have today though is that there is so much data and information out in the digital wild, that we’ve created an accessibility and usability problem. Raw data often lack sufficient context, semantic depth, or working applications and are basically useless until someone puts the effort into adding those elements. Artificial intelligences can often assist in that work by rapidly wading through massive amounts of data, but they always come along with uncertainties that have to be reduced.</p><p>One of the areas I’ve become very interested in is the digital commons, most notably represented in the “Wikiverse” of platforms, technologies, methods, and community. This also includes specific platforms like OpenStreetMap for geospatial data and information. New contributions pop up over time, some of which morph into the more long-standing digital commons infrastructure.</p><p>To a great extent, the Wikimedia Foundation and others have become Extra Governmental Organizations (EGO) in that they perform a very important role in upholding and building upon the public trust doctrine. Like government, they are dedicated to serving the public good. But they are not part of the nation-state apparatus, and in the digital world, they now transcend all national boundaries. The non-profit organizations that provide digital infrastructure through various funding sources are, of course, subject to all of the vagaries and pitfalls of human institutions and can certainly mess up and go awry. However, like government organizations, there are built in checks and balances when the “of the people” dynamic is continually upheld. If “we the people” are all an active part of maintaining and contributing to the digital commons, we help keep the human proclivities toward malfeasance in check.</p><p>Over the years, as I’ve worked on many types of scientific data in my day job with government, I’ve often thought that government institutions might be much better off contributing to the EGO-based digital commons rather than or in addition to always “rolling our own.” There’s still a solid role for the National Archives and the broader slate of Federal, Tribal, State, and Local government data infrastructure in ensuring the long-term viability of our digital assets. But the reality is that the work that has been done by EGO foundations and the army of volunteers they motivate and enable to build an interoperating and linked open digital infrastructure is often leaps and bounds ahead of governmental organizations.</p><h4>Test Case: Stewarding Trail Data and Information</h4><p>So, enough of the philosophy and onto more geeky stuff. I decided to work through a particular case of trails information with the following questions in mind:</p><blockquote>What if, as part of spending time in and experiencing a part of our public lands as a volunteer steward, I put some effort into curating information about the features of that public land within the global digital commons? How straightforward is this process? Could it be extended to anyone with time and interest? What value would it add?</blockquote><p>I focused initially on a specific hiking trail that I wandered down the other day from the <a href="https://www.blm.gov/programs/national-conservation-lands/colorado/gunnison-gorge-nca">Gunnison Gorge NCA</a> into the <a href="https://www.blm.gov/visit/gunnison-gorge-wilderness">Gunnison Gorge Wilderness</a>. The Chukar Trail is only about a mile (though data on this varies as I’ll talk about in a bit) and is the upper access point into the gorge section of rapids on the Gunnison River. Commercial and private boat trips launch from the access point at the bottom of the trail, with commercial companies mostly using mule trains to haul gear down the 500+ ft descent. It’s a pretty easy to moderate trail on foot, and I hiked it on Monday this week. I only picked up a single piece of micro-trash, so it’s a pretty pristine trail all together.</p><p>It was an interesting journey poking around online this morning to understand the digital footprint of the Chukar Trail and experiment with curating some of that information for public domain use in the commons. Following an excellent example I mentioned yesterday for the <a href="https://www.wikidata.org/wiki/Q97289858">Canyon Rim Trail</a> in the Colorado National Monument, I crafted a new Wikidata entity for the <a href="https://www.wikidata.org/wiki/Q112667890">Chukar Trail</a>. I created crosslinks with the existing <a href="https://www.openstreetmap.org/way/369008805">OSM way</a> for the trail, and I’ll need to follow up with some actual mapping work to make the geospatial data more accurate.</p><p>Along the way, I discovered some new resource pools I hadn’t known about. BLM advertises another commercial mapping app, <a href="https://www.avenzamaps.com/">Avenza Maps</a>, that was new to me. It’s yet another source of mapping data operating in the commercial space that seems to be geared toward business-to-business relationships with map makers. There’s an app and a free tier, so I’ll check it out further. By running a search in Google Maps, I came across <a href="https://www.gjhikes.com/">gjhikes.com</a>, a very information rich site for certain trails in my area that I strangely hadn’t yet encountered.</p><p>I put some of the information I gathered into the Wikidata entity, but I can see some additional work on this in future. Here are some observations and thoughts about the digital footprint situation for this trail that I suspect will extend into other cases.</p><p>More work will need to be done within the Wikidata schema and conventions if it is to be useful as THE database foundation for driving apps. Properties are sometimes a conundrum in Wikidata. They are often created with a particular context in mind and may not always extend into slightly tangential circumstances. For instance, following <a href="https://www.wikidata.org/wiki/User:Thierry_Caro">Thierry Caro’s</a> lead, I used the <a href="https://www.wikidata.org/wiki/Property:P7252">degree of difficulty</a> to flag the Chukar Trail as <a href="https://www.wikidata.org/wiki/Q66741664">moderate</a>. I referenced this to the <a href="https://www.alltrails.com/trail/us/colorado/chukar">AllTrails source</a>, which uses the same word. My own experience would make it mild to moderate, though the <a href="https://www.gjhikes.com/2014/04/chukar-trail.html">GJHikes source</a> lists it as “strenuous,” which is not yet contained in Wikidata, with a need to pull this <a href="https://en.wikipedia.org/wiki/Grade_(climbing)">concept</a> in from Wikipedia. Ideally, the curation for something like this would include both “moderate” and “strenuous” with different references and perhaps qualifiers for each entry, allowing a consuming application to determine which sources/circumstances best meet its purposes.</p><p>Some of the other semantics in Wikidata are even more challenging, pointing to one of the big arguments I’ve heard against trying to leverage the platform for “serious” uses. The Wikiverse is a wild and wooly place where stuff comes in from everywhere with not always rigorous oversight and peer review. But then, there’s also the issue of constraints that the meritocratic system at play within Wikidata have imposed. For instance, one of the really important pieces of information we’d want to include in the schema for trails is the type of activity supported/allowed for that feature. I initially classed the new Wikidata entity as a <a href="https://www.wikidata.org/wiki/Q2143825">hiking trail</a> but ended up moving it to the higher class of <a href="https://www.wikidata.org/wiki/Q628179">trail</a>, which is itself a subclass of <a href="https://www.wikidata.org/wiki/Q5004679">path</a>. The semantics here get really messy, and different understanding of terms means that the folks who apply constraints within the system sometimes make mistakes that inhibit the curation of knowledge. There’s a current constraint that means I cannot add <a href="https://www.wikidata.org/wiki/Q1914636">activity</a> or <a href="https://www.wikidata.org/wiki/Q61788060">human activity</a> statements to the trail entity like hiking and horseback riding, the two major activities authorized for that trail into a wilderness area, or ATV riding, drone flying, and other unauthorized activities. To accomplish properly organized and well curated information for this use case, we would need to do some additional work like adding subclasses for authorized and unauthorized human activities and fine-tuning the constraints to allow these statements to be captured.</p><p>The fundamental Wikidata model of statements with references and qualifiers is incredibly powerful and could allow for much richer information than is often captured in purpose-build platforms like AllTrails. For instance, if we resolve the activity statement problem, we could include fishing as an activity associated with this trail with the qualifier that it occurs at the lower terminus of the trail. Slightly tongue in cheek (but maybe not), we could include <a href="https://www.wikidata.org/wiki/Q105726">urination</a> and <a href="https://www.wikidata.org/wiki/Q204015">defecation</a> as human activities supported by the <a href="https://www.wikidata.org/wiki/Q3097999">pit toilets</a> at either terminus of the trail. This kind of fundamental, well-organized and attributed data could provide a powerful foundation for many types of applications.</p><p>The geospatial part of the data picture is interesting. The OSM source for the Chukar Trail is not accurate as the trail stops well before intersecting with the Gunnison River, which is the actual lower terminus of this out-and-back trail. AllTrails, COTrex, and other sources have more accurate line data. More exploration is needed to work through the Wikidata part of curating information in relation to the node/way structure of OSM. We have concepts in Wikidata for <a href="https://www.wikidata.org/wiki/Q7832815">trailhead</a> and <a href="https://www.wikidata.org/wiki/Q20820202">boat ramp</a> that could be used in the Chukar Trail case to describe the upper and lower termini/nodes of the trail, but there’s additional work to be done in the classification and descriptive semantics for these concepts (e.g., “river put in” might need to be a subclass of boat ramp or a separate type of feature).</p><p>I found it interesting that the GJHikes source was one of the “Web Results” provided by Google Maps for the <a href="https://www.google.com/maps/place/Chukar+Trailhead/@38.6140834,-107.85782,13.71z/data=!4m5!3m4!1s0x873f51f01b0c6ed5:0x823f61c6f47bfe61!8m2!3d38.6129583!4d-107.8360813">Chukar Trailhead</a>, with the trail itself not part of the Google dataset. This might have come about because GJHikes uses custom Google Maps as its map data component or they did some decent SEO work. The different representations and derivations of the geospatial feature itself does bring up some interesting things to think about in terms of synthesis and integration of these through time. Platforms like <a href="https://www.trailforks.com/">TrailForks</a>, <a href="https://trails.colorado.gov/">COTrex</a>, and others that provide for actual user-contributed recorded GPS tracks to be contributed could create an avenue for iterative data improvements and even interesting signal detection (e.g., consistent routing around deadfalls and other obstacles, authorized or not).</p><h3>Ethical and Practical Considerations</h3><p>With platforms like AllTrails, REI’s HikingProject (that interestingly does not include my test case trail), and others working in this space, we might be hard pressed to find volunteers willing to put time and effort into public domain data curation like I explored here. I submitted some suggested attribution additions to AllTrails for the Chukar Trail, and it’s certainly a whole lot simpler to do things in that context than it is struggling through the semantics and other issues in Wikidata to capture the same information.</p><h4>Role of Government</h4><p>Rich information about the resources on our public lands should be in the public domain, unencumbered by use restrictions and fully accessible to anyone, including commercial and noncommercial innovators who want to build on that foundation. Government organizations should make every effort to put the data and information that they are most directly responsible for out into the commons in a way that it can best be combined with other public domain information contributed from other sources. While I applaud the USGS effort to assemble an integrated <a href="https://www.usgs.gov/national-digital-trails/seven-ways-access-or-view-usgs-trails-dataset">public domain trails dataset</a>, I’m frustrated with how the dataset has evolved. The major focus of that effort has been to develop analytical tools on connectivity between jurisdictions and <a href="https://www.usgs.gov/national-digital-trails/news/parkserver-and-usgs-national-digital-trails-dataset">access to parks and public lands</a>. That’s all well and good, but there are some significant problems in the current implementation.</p><p>The provenance trace from the released National Digital Trails Dataset to original source data is sorely lacking with no record carried through for source identifiers that would allow for backtracking or alternate derivative pathways. This problem is evidenced in my test case with the USGS dataset having a “Chuckar Trail” in the same track as everyone else has the “Chukar Trail.” We have to look at the “raw” data and metadata from the USGS data product to try and figure out how this error came to be in the data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LaJMuXjPxuymHEJ-Fj2blA.png" /></figure><p>The data record available in the <a href="http://prd-tnm.s3.amazonaws.com/index.html?prefix=StagedProducts/Tran/">staged product download</a> for the National Map’s Transportation Layer (I honed in on just the Colorado subset) gives us an obscure UUID value for “sourcedata” along with a text string indicating “BLM Trails 09/2021.” Reading between the lines, it seems that USGS considers the BLM source for trails data on BLM managed lands to be the “predominantly authoritative source” in this case. We also have a date clue in a text string, which might help us narrow in on what we’re looking for.</p><p>I had to do quite a bit of digging to track down a source, which I still have no way of determining as the actual source material USGS is using. BLM operates what they call their <a href="https://gbp-blm-egis.hub.arcgis.com/">Geospatial Business Platform Hub</a> via Esri’s ArcGIS Online platform. A little digging around through “transportation,” which isn’t entirely intuitive, finally led me to one of quite a few datasets that have trails information, all organized into various line-of-business type of packages that likely reflect how BLM distributes responsibilities. I explored the “<a href="https://gbp-blm-egis.hub.arcgis.com/maps/blm-natl-gtlf-public-managed-trails">BLM Natl GTLF Public Managed Trails</a>,” which I gather is a derivative/subset from some master dataset for “BLM Ground Transportation Linear Features” (total GIS speak!). After orienteering through the map because the search is just a basic geolocate deal, I tracked down a source for the errant spelling of my trail name. The actual “cited” source from BLM in the metadata records for the USGS products points to BLM’s “<a href="https://landscape.blm.gov/geoportal/catalog/BLMNational/BLMNational.page">Landscape Approach Data Portal</a>,” where you can trace through to pretty much the same products with a slightly different representation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J_8knC8RKPQfxTgYTOU9Bg.png" /></figure><p>So, here’s where the real problem is. I certainly applaud the USGS effort to make sense of what is obviously a currently messy “authoritative” data problem where organizations like the BLM have their own particular context and drivers for producing and managing data the way they do. We need different syntheses across all of those to produce useful amalgamations that can be repurposed into new contexts. However, in doing that, we really need to record and make available full provenance traces without ambiguity. We need to know how BLM’s “ROUTE_PRMRY_NM” attribute from some specific dataset came to be USGS’ “name” attribute in a downstream integrated derivative. Exactly how and from where and when was that information derived?</p><p>Perhaps, the provenance trace and processing steps need to become more the point of what USGS and any other government agency producing data products is putting out. The dataset end products may be the primary point of use and interface, but the product itself should be the robustly documented and preferably executable process to get to that point. For a product like a national trails dataset, it might also be wise to consider “authoritativeness” as a factor of proven use and demand over logical source. Is it a massive problem that the BLM and now USGS have a misspelled trail name in their databases? No. Is it still a problem and indicative of what is perhaps a systemic point of failure? I would argue, yes.</p><p>If the process for producing an integrated/amalgamated product like national trails was equally or more important than the end result, we might logically think about building in some automated consistency and other quality checks. Quite a few US States beyond Colorado have invested significant resources through their outdoor recreation and tourism pursuits to build things like COTrex with pretty robust underlying datasets. AllTrails and other commercial ventures along with some of the not for profit platforms I’ve mentioned have lots of information about the same features. Some of these sources are “programmable” in some way, lending themselves to building at least high level processing (e.g., name/proximity checks). It would be fairly straightforward to identify a possible/probable misspelling like Chukar (the bird) to Chuckar (the I don’t know what).</p><p>If we take things one step further and think about changing mindset to one of projecting usable data and information into the commons vs. asking the commons to come visit the government, that might also result in more accurate and usable information. What I’m contemplating doing here is writing a bot to establish “Wikidata stubs” for all of the named trails that I can reasonably pull together from a data gathering process across accessible sources. By “reasonably,” I mean to a degree of confidence that I am not introducing garbage into the knowledge bank. In the process of looking through OSM and a handful of other public domain or open license datasets, I can already tell I’ll end up with quite a number of “Chuckar-like” situations that will take further human sleuthing. But what if government agencies started doing some of this as a value-adding contribution into the commons?</p><blockquote>Could government produce higher quality products by inviting a level of open public review and scrutiny through pushing their data products into a context that the public owns (.org) more so than what their government owns (.gov)?</blockquote><h4>Role of Volunteer Curators</h4><p>Despite some of the challenges I discussed earlier in the Wikidata semantic inconsistencies and shortfalls, it still is the most powerful and growing platform to rally around in terms of an open knowledge bank founded in the digital <a href="https://en.wikipedia.org/wiki/Commons">commons</a> (not to be confused with the thing that Elsevier appropriated and branded). It’s founding on the linked open data model is extensible and long-lasting. The Wikimedia Foundation’s branches into the Wikimedia Commons and other parts of the Wikiverse along with their mostly collegial relationship with the specialty community in OpenStreetMap is developing a well-rounded suite of interoperating digital infrastructure to manage and provide all manner of curated data, information, and knowledge content. Adherence to open standards and transparent technology will continue to support new innovations in interfaces, alliances with other platforms, and contextual applications.</p><p>My brief foray into curating content around a single trail will be followed by more extensive testing and use case bounding. I’m sure I’ll find some additional challenges beyond those I’ve noted here that will take some work within the Wikidata, OSM, and other communities. I’m quite a ways off from building a bot to lay out some named trail record stubs and start integrating properties, but I can see it on the horizon.</p><p>I plan to start with a recipe and set of guidelines/conventions for describing trails and aggregating data from multiple sources. As with a lot of these kinds of problems, there’s a fair bit of curatorial plumbing that has to be laid down and a coverage of data before anyone can start working up applications. I’ll focus efforts into the three NCAs where I’m connecting with a volunteer community so we can explore local application ideas.</p><p>At some point, I anticipate that we’d want one or many applications that bring everything into a point of use where context is defined and narrows the choices to what’s relevant. Very few people are going to geek out enough to go start creating or editing Wikidata entities, OSM ways/nodes, and whatever else we leverage. I would absolutely love it if AllTrails or someone who’s already built out apps and a user community latched onto the idea of at least a part of their data infrastructure moving to the commons, based in Wikidata or some combination of platforms. I would hope that could be a two-way street, with user contributions fed back to the commons. Commercial companies can obviously decide what they can monetize and deal with that content separately, but it would be great to see a commercial venture put a part of their investment into building the commons knowledge bank.</p><h4>Ethical Guardrails</h4><p>There are a number of ethical considerations with data on our public lands. Making more and better information about features like trails for public use accessible could be considered antithetical to protection. There are certain sacred places for me personally that I would never share, and there are cultural and ecological resources that need care and safeguarding.</p><p>I consider all of our public lands in the U.S. to be co-owned and co-managed with the first peoples of this area. I’m guided by the principles of <a href="https://usindigenousdata.org/">indigenous data sovereignty</a>, considering the digital representation of resources on our public lands to be properly co-owned and co-managed by Native American Tribes. In my test case of the Chukar Trail and its new Wikidata entity, I’m experimenting with adding statements about the area as the ancestral homeland/territory of the Nuchu (Ute) and Diné (Navajo) people based on the <a href="https://native-land.ca/">Native Land</a> mapping work. This is another place where entity classification constraints in Wikidata are currently coming up short.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IrRlkkByTBWRx8jsfNhV3Q.png" /><figcaption>Wikidata entity showing type constraint problems in associated a trail with Native American ancestral homeland</figcaption></figure><p>We have cases of trails throughout the country that have history with the Tribes, some of which has been written down in various “interpretive” materials but much of which is not yet linked. Where appropriate, I would love to develop relationships that help to bring more of this history to light to help deepen our connection with the land and its importance to human development through time. I can imagine all kinds of interesting ways this could play out with data within the Wikidata model. We might record dynamics of temporally bounded human uses/activities for a trail or other feature. We could encode treaty rights into digital representations, indicating things like hunting or herb-gathering activities qualified to the Tribes who hold those rights. How could that information, encoded as knowledge, help to develop applications that improve equity and enhance responsible use?</p><p>I can’t deny, though, that many of us humans go out to our public lands and simply take with no thought to our impact or giving back more than we receive. The area I’m focused on here in the Gunnison Gorge NCA is very popular for motocross with scars all over the Mancos Shale landscape from bikes high-lining the slopes, kicking up more dust to melt snowpacks earlier and eroding selenium-laden soils to cause downstream impacts. While I don’t share in those activities personally, I can understand the appeal, and it’s all part of BLM’s multiple use mandate. I guess it comes down to this question:</p><blockquote>Will making more and higher quality information about features on public lands like trails have a net positive or a net negative impact on the sustainability and long-term ecosystem services from those lands?</blockquote><p>My hope is that it will have a net positive effect. I hope that a platform which enables more people of good will and intent to think critically about and enter into more of a symbiotic relationship with our remaining open and “natural” spaces. I hope that a usable linked open data framework with well-rounded content will enable app builders to help educate and engage public lands users in developing creative solutions and practicing uses that lead to sustainability and positive ecosystem health trends. I hope to foster a deep rooted understanding and sense for more people in the public trust doctrine and our ability to be trustworthy stewards.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=db5e15a89ec8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Public Lands Stewardship Ethic and Linked Open Data]]></title>
            <link>https://medium.com/@skybristol/public-lands-stewardship-ethic-and-linked-open-data-2f5013acf8d8?source=rss-b947a36d30f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f5013acf8d8</guid>
            <category><![CDATA[social-justice]]></category>
            <category><![CDATA[indigenous-people]]></category>
            <category><![CDATA[linked-data]]></category>
            <category><![CDATA[public-lands]]></category>
            <category><![CDATA[stewardship-mentality]]></category>
            <dc:creator><![CDATA[Sky Bristol]]></dc:creator>
            <pubDate>Tue, 21 Jun 2022 23:34:25 GMT</pubDate>
            <atom:updated>2022-06-21T23:34:25.331Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-nc-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sLvCcAJU2PSs1zqpcRNAqw.jpeg" /><figcaption>Chukar Trail in the Gunnison Gorge National Conservation Area — Juneteenth 2022</figcaption></figure><h3>Backstory</h3><p>Over the last few years, my hobbies and interests keep pointing me toward areas where we need to link a whole lot of related but functionally “unlinkable” data together. There are thousands of cases of little pieces of information about the same things scattered across databases and information stores of various kinds. In data and information sciences, these are often considered de-duplication challenges, but they are really more often proximity analysis and dot connecting problems. It’s not so much that we have actual duplicates of records about the same things but that we have many sources of properties or attributes about things that could be combined to create a fuller picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iWzwY5wZy0qYM-ANHGxpxw.jpeg" /></figure><p>My latest challenge underlies a venture I’m pondering on some form of public lands stewardship database. I joined up recently with the <a href="https://www.coloradocanyonsassociation.org/">Colorado Canyons Association’s</a> <a href="https://www.coloradocanyonsassociation.org/adoptatrail">Adopt-a-Trail</a> program and started looking into where I could make contributions across the three National Conservation Areas in Western Colorado. I celebrated Juneteenth by taking my first couple of forays out to the Gunnison Gorge NCA and recording observations along the trails using <a href="https://www.gaiagps.com/">Gaia GPS</a> (my favored mobile mapping solution at the moment) complete with pictures and waypoint notes. Both ATV time and hiking time, picking up garbage/recyclables and pondering on being intentional in actively stewarding our public lands, got me thinking about what all our volunteer time doing this work might entail. Being a data guy, I also started thinking about how various adopt-a-trail volunteers might record and share data from these experiences.</p><p>I thought that two things would probably be true:</p><ol><li>There must be many more adopt-a-trail types of efforts all over the world.</li><li>Someone has probably come up with some pretty cool databases and apps and whatever to capture details about activities like this.</li></ol><p>On the adopt-a-trail idea, there are certainly quite a number of those in play, including <a href="https://coloradotrail.org/volunteer/adopt-a-trail/">one here in Colorado</a> I’ve encountered before. Some of these are operated in the US by our land management agencies or their associated “friends-of” associations, and many of them focus on trail construction and more major maintenance efforts (sometimes in cases where a public agency is underfunded to pay for this work).</p><p>On the data and apps front, there are a couple of specifics for hiking and other trail activities that I already use:</p><ol><li>AllTrails is <a href="https://support.alltrails.com/hc/en-us/articles/360018930652-How-do-I-write-a-review-for-a-trail-">super basic</a> with a rating/comment structure plus options for activity selection and trail conditions. I’ve actually found pointers to trails all over the world with AllTrails, so it’s scope is pretty large.</li><li><a href="https://trails.colorado.gov/">COTrex</a> is specific to Colorado and super nicely done as an app by the Colorado DNR and Parks and Wildlife. They have a more sophisticated “trip report” feature with the ability to record activity type, link an actual recorded route and selections on trail conditions, crowding, bugs, water, and bathrooms along with photos.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*-Tf6_Igo7Fbht3aR956orQ@2x.png" /></figure><p>And I’m sure there are quite a few others as well, some of which might be worth exploring. Being a data guy who has also dedicated much of my career to open data and open science practices, I immediately start looking not just at what a particular app or platform has done but the underlying data situation and especially the openness or lack thereof for the data. AllTrails along with more GPS-centric platforms like Gaia GPS and <a href="https://www.onxmaps.com/">onX</a> are commercial ventures that are going to have a vested interest in protecting their unique underlying data assets. COTrex is a state government funded deal, and I did find a <a href="https://data.colorado.gov/Recreation/Colorado-Trail-Explorer-COTREX-/tsn8-y22x">record</a> in Colorado’s open data catalog that provides a snapshot of the underlying trails (and other) GIS data. This will probably be the same data that are incorporated into the <a href="https://www.usgs.gov/national-digital-trails/seven-ways-access-or-view-usgs-trails-dataset">USGS National Digital Trails Dataset</a> (more on that later). Another outdoor activity mapping app, <a href="https://www.trailforks.com/">TrailForks</a>, has an API that can be accessed with a key (I’ve requested one). Their trip report deal is a little more sophisticated than AllTrails but the focus is on uploaded pics and videos with a bent toward mountain biking at their roots. I don’t yet fully understand the use restrictions on their data.</p><p>None of these platforms or approaches gets at what I started dreaming up on the trail the other day. I was thinking about how an organization like the CCA or managing agencies like BLM could leverage data collected by their volunteers in various ways. As a simple example, there’s actually no way for me as a new volunteer with CCA to check out where other volunteers have already been working in our large coverage area (over 600 square miles between the three NCAs), when they were last there, and trends in overall trail messiness. The training materials for this job were well done, a joint effort between the CCA and BLM, but everything points to making phone calls to report anything in need of law enforcement or other professional attention on public lands. I can also imagine tying in with other platforms like <a href="https://www.inaturalist.org/pages/seek_app">Seek</a> from iNaturalist for volunteers with an interest to record and share important biological observations like the couple areas I recorded invasive knapweed this week on the Chukar Trail. I also think about what a powerful open database this could be on a global scale for all kinds of research and for community momentum building.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YoTWA7YntFV4BAUlx7g4aA.jpeg" /><figcaption>Knapweed at the bottom of the Chukar Trail on the Gunnison River</figcaption></figure><p>The basic idea of the trip report has obviously been implemented in various ways, and I’m sure there are many other cases around the world where specific apps or data platforms have done something like this within their context. But I think we need something bigger and different than what I’ve seen so far. I’m imagining more of an open data framework based on linked data principles and technologies. We need to leverage many different platforms and tools for recording and sharing information, linking into and through them to develop intelligence about our trails and other public lands features. We need to think much more holistically about what it means to experience our public lands and join together in active care and stewardship.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/828/1*3T0CnRA2C9xu_hIyZpgSbg.jpeg" /></figure><p>The COTrex Trip Report is the most robust of those I’ve come across so far. In a slightly different context, <a href="https://freeroam.app/">FreeRoam</a> for campgrounds and related sites is a similar idea with a little bit of a bent toward digital nomads with their social reporting feature. All of these are built within a particular context, collecting information that is specific to the app designers, what they want to use, and what they think users will spend time submitting. But what if we could link anything and have a much more extensible data schema with an ability to expand into limitless dimensions on what people might be willing and interested in sharing and what other people might be interested in learning about or analyzing.</p><h3>Public Lands Stewardship Motivation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1EhZbOVHEH_o01604JaTrw.jpeg" /><figcaption><em>Nelson Holland during a hike on Mount Falcon in Morrison, Colorado (credit Ryan Warner, CPR News)</em></figcaption></figure><p>A Colorado Public Radio <a href="https://www.cpr.org/2022/04/08/how-a-black-hiker-from-aurora-champions-inclusivity-in-the-outdoors-one-tiktok-at-a-time/">story</a> with a guy named Nelson Holland really caught my attention a while back. Nelson talked about the dynamic of being a black hiker in what is still very much a white dominated activity and US State. He spoke in the story about the way he sometimes gets obviously weird (if not hostile) looks from especially older white hikers in the more rural parts of Colorado not used to seeing a black guy out on “their” trails. This struck me partly because I live in one of those parts of the State. I was thinking about that story when I was hiking down the Chukar Trail yesterday, the second officially Federally recognized Juneteenth. I was pondering the social aspects of public lands stewardship and thinking about what responsibilities and opportunities as an ally I might develop in promoting more inclusivity and equity. I was also thinking about the Nuchu (Ute) ancestors who may well have used the same route up from the Gunnison River before the lands and the wealth that came with them were stolen and swindled away. What can I do to promote and bring about more equity and inclusion in our public lands, and what reparations can I help lead toward for the damages wrought through colonization of what are now part of the public trust?</p><p>All of this has me thinking about what intentional and impactful use and stewardship of our public lands and their many natural and cultural resources might entail and how a linked data and information framework might support and be a part of making that more of a reality. Picking up garbage, hauling out recyclables, scooping up dog poop, and reporting on any issues in need of trail maintenance are all the basic jobs for adopting trails through our local association. Telling others about what we find and don’t find on the trails seems like it should be a part of that work. Perhaps spending a little time learning about a trail and its history and synthesizing that information in some way could also be useful. Acknowledging for myself and witnessing for others where opportunities for greater equity might be sought might also be important. I’m not sure how to bring this about, but I’ll be exploring it further.</p><h3>Linked Data Challenge</h3><p>While there are actually a lot of features on our public lands that we could essentially use as rallying points for a linked data framework (mountains, rivers, lakes, etc.), I’ll focus on trails as the problem du jour. The trails data situation basically sucks. As I mentioned, USGS has taken a crack at building a somewhat comprehensive approach to an ongoing data integration exercise with their open database. It’s not horrible, but it’s not that great either. It would be far better if they shifted their focus from building a new database to exposing what goes on in effectively linking or amalgamating multiple disparate sources, sharing the full depth of what is brought together so that other data builders can make their own choices about how to handle the issues and link more effectively back to original sources for different processing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*7wGQoQn_py8aPp4J.jpg" /><figcaption>Krauss, CC0, via Wikimedia Commons</figcaption></figure><p>AllTrails uses OpenStreetMap as at least part of their source material (see this <a href="https://support.alltrails.com/hc/en-us/articles/360019246411-OSM-Derivative-Database-Derivation-Methodology">article</a> on their derivation methodology). The bigger commercial players are opaque on sources, but there’s lots of user chatter indicating better or worse underlying data. I have a personal interest in contributing to and making OSM work better along with related efforts in the “wikiverse,” particularly Wikidata. Being open public data and providing APIs, I’ve started poking around at the intersections between the USGS National Digital Trails Dataset, OSM’s “<a href="https://taginfo.openstreetmap.org/tags/highway=path">highway=path</a>” data, and Wikidata instances of <a href="https://www.wikidata.org/wiki/Q628179">trail</a>. My thinking is that a combination of OSM and Wikidata should provide a fundamental platform upon which to build some type of globally scaled linked data architecture. Initial exploration, however, points to the need for a fair bit of robot and human curation work.</p><p>While geospatial data describing trails, including individual segments between sometimes other meaningful features, is reasonably robust based on the various ways it has been assembled and is maintained, the linkage to and information about the more abstract concept of a named trail is really quite lacking. AllTrails and various other groups have tried to address this issue based on their own requirements and available capital to build usable data, but those are not buildable as open architecture. Wikidata can be a powerful linked open data platform to rally around, including the practice of linking external identifiers together on the same entity. However, there is a current dearth of good records on trails pulled into Wikidata through a handful of bot actions. There are only <a href="https://w.wiki/5KpE">23 named and identified trails tied to Colorado</a>, though there are some others that are just not appropriately attributed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nQoK5wPSxbDpVkuNxU7HJg.png" /><figcaption>Quick look at the 3 OSM named trails in Colorado with links to Wikidata</figcaption></figure><p>On the OSM side, there are 37,392 “paths” in Colorado, of which only 4,676 have unique names (much more work to be done here). Only three of those OSM ways have a wikidata tag pointing to a QID. Of those, the <a href="https://www.openstreetmap.org/way/441970652">Southwest Ridge from Fourmile Creek</a> “trail” on Mount Sherman in OSM links to the Wikidata <a href="https://www.wikidata.org/wiki/Q6923597">entity for Mount Sherman</a>. I would say that’s an inappropriate association recorded in OSM data, but the rules are a little ambiguous.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EjF8Ja_E9vsC2KtC-MkYjw.png" /><figcaption>Wikidata page for the Canyon Rim Trail on the Colorado National Monument</figcaption></figure><p>In my ideal world here, we’d have a Wikidata QID for every named trail to use as a digital lodestone. The Wikidata entity for the <a href="https://www.wikidata.org/wiki/Q97289858">Canyon Rim Trail</a> on the Colorado National Monument is perhaps a great exemplar; a very robust record that contains a wealth of linked information. The Wikiverse infrastructure would help to disambiguate between trails of the same name, and the Wikidata entities would provide a rallying point for any other identifiers for the same logical feature to help us link between disparate sources. But that world doesn’t exist yet, at all. So, the question is, can we start building that foundation? Can we build some bots to start assembling the stuff that can be verified, using the Wikidata conventions toward referencing everything to build a trustworthy platform? I can start to envision a preponderance of evidence approach to data integration that could develop enough clues about enough trails, at least within the US, to get the ball rolling in the right direction. We could then build some useful apps on that foundation and hopefully spark some interested human curation to help connect dots on the less certain stuff.</p><h3>Public Trust Philosophy</h3><p>There’s the geeky part of what I’m working toward that will be fun and challenging as yet another data integration problem to be solved with some creative software and technology. But I’m much more interested in promoting and doing what I can to support an ethic of stewarding and maintaining the lands and other resources in the public trust. I’m interested in providing an open data foundation that can serve as a freely available asset for groups like the CCA or the <a href="https://app.thatch.co/view/profile/4Lm4qJ9ADcSLGOU56vb5xXMLAou2">guide service startup</a> that Nelson Holland has going. I’m interested in providing a focus for anyone who wants to engage with our public lands in whatever responsible and sustainable ways they want, being mindful of who has been there before, who will come after, and always working to leave the resources in the <a href="https://en.wikipedia.org/wiki/Public_trust_doctrine">public trust</a> in better shape than when they started.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qn3wFeKWXDx2l_xuyrA-zg.jpeg" /><figcaption>A sacred canyon in Southeastern Utah that is now thankfully once again part of the Bears Ears National Monument and co-managed with the Tribes through the Bears Ears Commission</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f5013acf8d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>