We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Public Domain Map

00:00

Formal Metadata

Title
Public Domain Map
Title of Series
Number of Parts
41
Author
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
Imports, licenses, and separate databases: These topics always seem to strike controversy in the OpenStreetMap community. Public Domain Map aims to resolve (some of) these tensions by providing a system that allows contributions to be used in both OpenStreetMap and public domain US Government databases. Join us to hear about the first phase of our project which involves railway tunnels, public domain imagery, and the Tasking Manager! This talk was presented at State of the Map US 2022. To learn more about State of the Map US 2022, visit https://2022.stateofthemap.us/ Learn more about OpenStreetMap US at https://www.openstreetmap.us/
21
Public domainSource codeInternet service providerExpected valueData typeData structureBridging (networking)Level (video gaming)DatabaseProcess (computing)Set (mathematics)Projective planePoint (geometry)Open setShared memoryProduct (business)Group actionTask (computing)Multiplication signService (economics)Standard deviationDifferent (Kate Ryan album)Computing platformBoundary value problemMereologyFöderiertes DatenbanksystemTrailBitScheduling (computing)Data qualityLine (geometry)MappingInformationSystem callPublic domainLattice (order)WebsiteData managementGoodness of fitLatent heatState of matterException handlingField (computer science)Wind tunnelRight angleDirection (geometry)Object-oriented programmingTopostheorie1 (number)Core dumpMathematicsStreaming mediaComputer animation
Transcript: English(auto-generated)
All right, so I'm sure everybody is well a lot of people came from the East Coast So it's probably like lunchtime, but first thing in the morning. We're gonna be talking about Licensing which is always like a fun thing to start these conferences with these are just pictures of different kinds of licenses, I guess
So Over Street Map is in ODBL It used to be in Creative Commons at one point they switched it over because Creative Commons didn't work very well with databases, but ODBL is supposed to be better
There was a push I think this is 2012 to get rid of ODBL and move at least some stuff to public domain or at least Get rid of the share alike and that kind of failed because
well There were some some benefits to having this share alike involved so people can't just take OpenStreetMap data and Put in their own products but in the end it turned out that OpenStreetMap's license is actually pretty good for what OpenStreetMap does
I think that the companies that were really interested in this kind of moved on to different products different ways of doing things and we didn't really need an open license change, but There are other kinds of licenses like public domain is very important for the government everything that the government is
Releasing at least should be in public domain. This is a little quote that I found on it from Wikipedia, but The the main thing or main point is that most things should be in public domain there are some exceptions and you can trademark data and trademark pictures and stuff
But for the most part it should be in public domain. So that kind of creates a situation where We can't just use OpenStreetMap data within government and passing data back to OpenStreetMap is kind of a one-way street I wrote a thing on this a while ago
2013 I think that just kind of goes over the specifics and it gets really into like topography I try to put a picture here of topography and linking but once a node in one of the ways connects to a different way that way becomes
licensed by ODDL So if you just connect your road to the one next to it That could be a problem and I work for the National Park Service and we have this problem a lot at our boundaries of the parks because We use OpenStreetMap data on all of our maps outside the parks But inside the parks we use our own government data and there's alignment issues
and we can't take our point and just line it up to OpenStreetMap because then our data becomes licensed and We really shouldn't be taking OpenStreetMap data and moving it to government data Because there's some reason OpenStreetMap put it there our data could have different data quality standards
But we shouldn't be editing their data just to match ours unless we're really making a focused effort To do that as a wholesale thing So The other thing with government data support is it needs to be or at least is expected to be authoritative so that means that someone comes to look at a park service boundary and
Especially in the park service, we don't allow hunting in the parks So people use those maps as legal definitions or try to use them as legal definitions of where the Boundary is so they can decide where to hunt and where not to hunt. These have come up in legal issues
But because of that they're very afraid of allowing just Someone to come in and move a point somewhere because for legal reasons somebody can move the boundary over and say hey Now I can use this land for whatever I want to use it for so We can't just take an OpenStreetMap data into the government anyway, despite the license
and here's something that Great, if you're not I think Greg may have made this at one point 12 years ago, but So the USGS has been working on this probably since the 70s the whole
Taking information setting up maps to Municipalities having them send the data back as Marked up maps bring it in having it get validated having it go through this whole process And showing up eventually in the US Topo products this process has been refined and refined over years and has kind of gotten to the point where it's a
Little bit easier to automate there's still a lot of steps involved, but they have moved through various platforms I think they're using an Esri based platform right now, but the idea is you take a Volunteer contributions you go through a process of vetting. I think this one is currently three-tiered
you have the The people in the field that are collecting you have the like states and then you have the federal level And there's data stewardship levels like that and and it's a really good process and here's me talking about this like
Ten years ago And it's pretty much the same thing as now I just wanted to put that in there you're like this isn't anything new so I Found a public domain image of forks from museums. So that's what this is So I want to talk a little bit about forks and why I actually don't like forks. I wrote a paper on why not very good
Also ten years ago because everything's old now But when you fork a database What you're basically doing is taking everything in it and saying okay, this is mine now and then this is the other so anything you add to this one doesn't show up on this side and
If you want to keep it going back and forth, that's really cool, but that's really hard to do and A good example that I was thinking of for this was In the park service we have campgrounds and we have a point in the middle of the campgrounds But some parts would like to camp individual campsites
Instead of just the campground or others will put one pin and say there are ten sites here So when you're trying to conflate data like that, it's really it's not just a difference of opinion. It's a difference of ways of Representing the same thing and that really becomes a lot harder
So there are other forks out there I could not actually find this Creative Commons fork that back when the OEDL license came in There were the group that split off and said we're going to stay Creative Commons. I Don't know if that still is around The National Map Corps, which I talked about for the USGS There was a project that I worked on at NPS called places. We kind of rolled that together with some other products
It's still we saw the data, but we were able to merge that back into our bigger data set Which is actually a cool process, I think and Open historical map has a lot of sessions going on this week and Their stuff's really cool and they have their own fork. There are other ones. I
Did look them all up Anyway, so I want to present a new fork after I mentioned I don't like them, right? So the point of this is that everything will be in the public domain
License so anybody can just put whatever they want anybody to take whatever they want It's it's five point here The final data set can can be used for federal databases and OpenStreetMap And this is something else Greg worked on. He's the workflow guy
This really just kind of goes through the steps I'm not really sure how much this is readable But it goes through the steps that everything goes in we collect data It goes through a vetting process the authoritative review that can go out to the government database directly or we can use something like Map roulette is is a tool that we've used a lot
Just in the past and we really like that but we have been looking at everything else that we can use So our pilot project is a railroad tunnels. This is actually an old highway tunnel I was a time like a find that I had a picture I took so yeah
So this is using railroad data, and we already have the railroad segments I'm going to slow I guess this alright, so this has we already have railroad segments, but we want to add tunnels to it So let's see this is the process basically I'm going to go through these fast
So you find your tunnel? You I'm sure everybody here is familiar with ID you split the way and You create a new segment, and then you take it as a time So Next steps we really want to get this pilot. This is just in Colorado right now. We want to expand it
We're still going through the tasking manager trying to figure out the best way to keep people involved keep people knowing what's going on With with which step, and it's a little confusing in there, and I think that is kind of a hold up for us Let's see what else I said here. Oh, yeah, we want to go into trail day at some point
That is something that I'm really interested in because I'm sure you look at the schedule you see there's a trails working group Which is a big project that? I'm working on for a while I've just been part for a while Everybody here a lot of people here been working on it, and that's really cool And I would love to see this getting our trail data out there
I Threw another thing here of a conflation project I did with map roulette probably 2015 it's only seven years But we've been working on this stuff for a while trying to come up with ways to get this stuff back into Open Street map and try to
keep the government and the Open Street map community together This is mostly Kind of a volunteer project like we get a little bit of funding from government agencies, but a lot of its volunteered There's a lot of cool stuff that we need help with but we mostly just need people to help map
Alright, and that's all I have I have thanks to a lot of people who've been working on these and meeting with us every week or every other week at least on calls so thanks everybody who helped out and I'll answer questions and Darryl's gonna get up here and answer any questions too