Bestand wählen
Merken

Using OpenStreetMap Infrastructure to Collect Data for our National Parks

Zitierlink des Filmsegments
Embed Code

Automatisierte Medienanalyse

Beta
Erkannte Entitäten
Sprachtranskript
to bring together so the idea is we had 7 that that we pull together using a lot of different tools and just kind of go through how we use those tools so I'm sure most people here
know the National Park Service's they have a lot of iconic places so this's the arches and no um I guess or purchase National Park says Yellowstone going gate and kidnap your words and this is about why mall the National motion so we iconic map style that when you go to the parks you pick up these maps out prayer
the that pretty much give you a good idea of the part they are just on paper so there single scale so all pretty detailed there only useful the for just overview the park and we've had a lot of them are are
pretty nice and the colors that together well so our common and command
team and yet team's goal was to create web maps and we take these original paper maps and figure out ways to put them onto the web so our mission is basically to make it easy to build and deploy these beautiful maps so we have for internal tools that we use to do that we have something called builder which
is all-encompassing tool that you just go in and you can for your permission directly in there and create an is not 1 example that we have
is the bears box maps and if you wanna get more creative we have a back end tool called map JS it's kind of mimicking out not boxes JS library about but they're library is really good and we want to extend it a little bit to do are specific goals and that is
all driven in the back end by we have time this part tells project and this is really what we do to pull those
all part maps into tiles that we're using the and this is all built off of map OX vector tells right now we have the terrain the background and we draw our own Park polygons around it with them a lot of work to get is telling us a look these fairly decent we're still working with the parks to try to get better polygons and it just as
examples of of the different scales that we use and this is really what's important when you're doing web mappers oppose footprint map so think pretty time in to matter
agency the detail that we have of the different icons in the box you can see the picnic areas and it is at the beginning of a hiking trail and you can see the same
thing with Acadia so you really wanna get all this information in there is through a project that we call places and we created this problem just to make it very easy for anybody coming to the map and work and the real problem is that a lot of projects watermark parts of there have some really really good information you give a look anywhere in the parking you talk to the GS staff and they know exactly where things are but smaller parks they just
say 0 we have stuff Bracha where it is but is in this general area generally know the have trailheads and they know where they are as far as walking but as far as putting map they don't have the technology to do that
so it what really want to do is places project was motivate people to go in and edit that's really kind of of a hard thing to do when you have a lot of people who are really familiar with technology or have been doing being park rangers fur a long time and really just spend all the time out the park there really know much about how they're going to go into the systems so we have identified 5 idea that we were looking for we're building this we wanted 1st in years a great interface so people could come in and really does build this off that if the the to build up that information and creator good map just by looking at tools literary out there we want a data structure that you could really go in and modified to everyone but still has some structure that we already exists we also wanted good back and API that fail on us so we can have 1 or 2 people editing a time we did have a hundred people at a time and we know that it's proven to work I would like to have a good eco-system of tools so that we can really build off of this data you can break it up into different extracts by party can break it up by and just you what kept sites which is something that's pretty popular and another thing that we really want was a good feedback system so you could go on and you can really say OK this change SKOS looks like on the map and you would be able to see that within a short period of time the so the next thing
we're going to to to do is we're looking at different systems and we saw that OpenStreetMap was out there with the great ID editor which if earlier about earlier today of the over she met data structures the key values so its extendable to pretty much anything you want to be but there are is a defined Wikia that people generally used to come up with most of the tagging and we tried to map our ideas of tags to what's going on OpenStreetMap so we can go in between the 2 systems which you map has API that is pretty substantial it works pretty well there are costly upgrades on it and it's it's pretty cool and we use a lot of these of tools of particularly Johnson is how we get all of information into our system but but you can use the other tools to do different kinds of extracts adjusting manipulation and wanting really liked about OpenStreetMap is the the feed back where it comes back within a few minutes when you put it in there you can see and serene so we decided to have fork the ID editor and we came in we change and icons this over there on the left side with our own National Park Service icons and we change the tag that going behind it to only show tags that we really want to show on the map we left all the tags in the idea is so anybody could go in there if they had something from OpenStreetMap it will show up with the proper name but we disable search functionality for those so people are going to actually add things that are really requirements of the great thing about ideas you need to know what the tagging is behind the scenes that tell little window their measure how easy that is the sea but at 2 really confusing to users to go when they're just look at this list of tags and say 0 this is what you mean by so the idea makes it really easy to just click a button and say ranger station you don't have to go through this whole mess tags and we also had a unique identifier at the bottom there each time someone add something which is very useful for internal tracking and we need to create something for this database of we went out and had so interns a while ago go out to each of those printed out maps and figure out where each point was put and this was created a while ago and it's not the best source of data but it's a good starting point and once people go in there and they see that that there is something there but it's not completely correct they get motivated to start moving things around saying I know that this is really over here and we found that just by putting a little bit of information there it really helps get people motivated and interested so to explain the rest of how it works this going to go through some
steps so the 1st thing that you do when you add to this editor is you have the log in right now we actually using OpenStreetMap as our login platform just send them the request the is back saying the person is valid or not and we decided to do that because it's is really great to be able to say this is the user who contributed this them we wanna write back and OpenStreetMap it's really great to have that full history of who did each edit we are looking at all so working with Active Directory internally as as something that the government really has inside 2 years so it's great to be able to use OpenStreetMap but we're looking at other methods of lying in as well and just kind of tools too keep track of everybody's contributions so this when they save the contribution can we do a kind of a three-step process were openstreetmap has a pretty simple database called API is 0 . 6 it's really just keeps track of the latitude and longitude of each point that has no idea what geometry is it doesn't even have latitude longitude or not even floating point numbers to just big numbers out there and everything is linked all the all of the ties are linked through a separate table so we go through and the transform that into something that as our similar to the schema called PD snapshot which is just 1 of the tools that Overstream met users to render its data and we use that for all of our queries just because that is a spatially enabled databases and we can creatures bounding box and pull it out which is a lot quicker than querying just based on raw numbers and we can also do spatial indexing on which makes a lot quicker and we also throw it into the last step which is the rendering step and that is almost ready displayed on the map the so just I mentioned for about the API 6 the latitude and longitude feels they're just very large numbers and there's nothing really spatial about this other than those could line up to so that is 84 Corinth so we bring that and this piece
snapshot database the other the interesting thing about this they use each stores as the of the field store all of their tags so if have access everything without linking the table which makes it a lot easier for rendering tools to really pick it up so make it to rendering maps which is probably the most fun part i think it requires a little bit of working with all the tools how we match up those tags to what we had originally called them we just have a single script the goes up the polls what tags that listed and it matches them to the name that we had set up for that for and we rank things in order by which the but the importance is and how we wanna display them so when you 1st look at a apart you're going to see something like visitor centers but as you zoom in further you'll see more things like picnic sites waysides and for this rendering we us keep time stamps and that's just so when we run a script that updates are databases externally we know when the last time we ran that was and we can go from there the so that's what step 3 is this is a process that we're currently running every 15 minutes and we can write out to our maps immediately because we're using map but studio decree vector tiles and we also were running out some of our points just to Connie be because it's a very great waiter look at vector information out there so we run into this program called tire life which builds just tiles that you request so we just give a list of positive been update in the last 15 minutes a since the last time the process ran entire liable run map box studio and just those that small list of tiles and then once that's all done we uploaded to the mailbox servers and map boxes serving up over tiles and nice easy to use formats but we found that it takes about 24 hours for everything to update and we're in working to see what we can do to get to be faster but just because a cashing in and a CD and stuff it takes a little while so this thing that we do with them as we bring that to Cardie B which is a lot quicker getting information out but if is not baked into Artiles all there is no difference in light years so only through these on top of our maps they obscure all labels and it is because very they're not knowledgeable of what's in the rest of the now and there separate the datasource entirely the they are really useful for putting on a quick maps of people create especially if they wanna use something like the builder to create a map of all the campground park the 1 other thing that we check for is the when we render these we figure out which pockets and using the outputs Chris and we use St contains feature to find what part the and we connect that to map so In the future we really want at
buildings were process the the usually supports areas of and is a great editor to add things to do it's really easy to work with them they made it really easy to extend and internally as more problems of buildings because this is data management issues with different parts we have a lot of information and it's really just a matter of who's information we going to use and how are we going to create a crosswalk between the traditional GIS information that we have hand what we wanna put out on a public-facing maps and how we want people to contribute
so 1 of the things that were really interested in is connecting our stuff with the every feature services and we talked with every about the coop project which is really cool tool they have that allows you to access and allows access all kinds of stuff through every Feature service and you can use these In the last open-source tools with your open source information from a get hub is probably when the calls once you can do you can just send it to a get have repository and open it up in your proprietary software and well a lot of our study is open
source we do have a tradition of JS department that does work with these tools and we want to make sure that everybody is included in the community and that they can use their own tools as well as the tools that we've created and we think that's a really good way to get everybody really motivated to work with it because they don't have to relearn something they can use their existing tools 2 and 1 of the things that I'm really interested in doing is getting this information back and over she maps an over she met community is not like you just taking information over I was already in OpenStreetMap have a just cause problems where you're information may not be more correct than what's already there or you you really should be deleting other people's work without these going through and verifying so it created a tool called Mabry let which is really was originally just used for fixing errors but they are using it for some small conflation tax tasks there was a or symbolize another project I in this house maybe 0 assembly the vertebrates of when the project is about adding parks in Los Angeles and inflating than to what's and both these projects work really well and they've really show that people are able to take these small tasks of just 1 or 2 bits of completion work on it slowly and get the whole thing into them
so i'm SUCH go over what our mission was again we really want to build and deploy these beautiful maps and we have these tools like the builder and ah Internet JS library to create them and then we can make that the beautiful maps through or part tiles and then we use places as just our data source and we use a lot of open source tools in the back and to really get this to come together we use a lot of stuff from a box where using a map box studio were using overshoot maps whole API which we mostly use in no JS now and we have I am opposed just think it's 9 . 4 database now with dead Jason How support and it's really pretty great for what it's doing so that's pretty much all I want to touch he has been and what if any questions or anything but I got a lot of cool stuff of legends thanks to the it is so are because the internal tools the builder and and the map Js are really built to create maps in the National Park Service style but what is pretty applicable to other people in this release at groups outside of that is just how we are using OpenStreetMap as an interface and I really think that Oprah she map has a greater ability to be used in just in 1 Roger mens on and that the tagging scheme and the tools that are built around it are pretty interesting and they can do a whole lot and someone's got a lot of time developing these tools and they're still very well supported and also we use about studio which does a lot of just data rendering and that that's pretty cool to and here's how how much did each week or modify of I it was at most if you have to figure out from there was a lot of change there is not a lot of could change at all it's really easy to reconfigure idea the main thing that we have to do is really get rid of anything but points that our buildings added you have the option of adding polygons and we still haven't gotten to adding trails which would be to the lines at I we have to make a few changes to so just small things to make sure that we after at a tag in there we want that is a link back to or other information but we want to be able to disable field so people can go in they're using ID end and change these things because so going using something like Jocelyn do that but we don't wanna give all the users the ability to change the the ID field that's currently identifier feel that was just something that we pulled out of there and I guess so the big thing we had a changes how the login process works because it goes to our server that are server goes out OpenStreetMap bring something back to ID to say this is a log in things did is due is a form of it on Iraq in New before it is public gonna get upside and try to keep it as up-to-date as possible but they do a lot of edits on ideas so I might be about 340 before the to 180 questions 1 of so all so this is the so but we really want this to be open to the public but as of right now we don't have a out of full validation phase going through so we can't we we can use a set on are maps but we can validate external and we'd really like to get the public involved but right now it's still an internal project as far as the availability of the data there's no reason why it shouldn't be publicly available well we just use it on on maps right now this and if you really need the information behind it it's probably not very good right now so we kind of don't want to release it were still trying to get internal people updated but I think as soon as we have something that we can we say this is pretty good then we can start releasing it but were still working with a lot of the Departments of lot of the different parts in getting better contributions in each part and I just don't think it's the right time to release it and so we have to live a better idea of what's in the the word and the this the the is so the Rangers are pretty interested in sharing what they know and it something that they see wrong on the map the usually pretty interested in updating it but there are some kind of problems with talking these ranges where there's a lot of stuff in which you met now like trails and things are through protected areas are closed areas or the roads that lead to an area that is protected end these ranges do not want that stuff to show up on the map they don't want people even know there's a road there and they go off there have been known to go OpenStreetMap and bring those things and that's kind of a hard point for us to look at because I 1 1 idea we want to draw these rows there they do exist they are something that you can use to help locate you especially fear walking down the road and you're looking for someplace to meet somebody or something be great if she knew there was a road there but at the same time if the road lead somewhere that do not allowed to go we don't really want people to go into the matter ahead of time as they all this this road that goes right back to this place and while I don't really feel we should restrict information I think that's it is kind of a little bit more of an official map that maybe it shouldn't be on the official map but we should still keep track of it just so we know it's there and we can render in ways that show that you can go here but it does exist of so so the of the the of well so I have a look at this from a number of ways USG is also as a fork of that they use for our the GIS collection and that information is really good now because they have stewards in each of the areas that keep track of it and contribute back to that map and that information is publicly available anybody can just go get and put it back in OpenStreetMap of a that was created with her when the import was done through from GIS they kept the information that link it back so you know exactly what point was moving you can really keep track of that and are a tool that would do just the GIS data and I think that it's kind of cool that you can do that but we the there really isn't a lot of linkage right now between these other projects and I personally but like just have 1 big project that you could put everything in and everything the great but the big problem we have with OpenStreetMap is licensing and other liability if we just use OpenStreetMap as a backend for our maps for everything which we do show roads from extreme before freezer for everything we would have the problem of liability where some of the draw something on there that doesn't exist they could help that there's been issues were they move apart boundary years someone has a map that shows a apart spot and there's hunting laws that are different in different areas of and the licensing is a big deal with us because we have to put everything that we make into public domain is just how Our system set up and we can contribute wreaking contribute into OpenStreetMap a once it's in there the it gets tangled with other but human contributions and it becomes license through OpenStreetMap and we can't we can take the information back and displayed on a map so we can never re release it because now has a license and were not allowed to release license data so it has to be carried problem that we're trying to get and there's that you're trying to solve in there's some good tools out there now like mapper let's really working on completing these different systems together in trying to create a which you map as a base map of all this information is collected elsewhere and I think that's really the goal and that it's OK to have some forks of it as long as they know that they are contributing to this mean map and they have slightly different information that fits their needs but think of
Mapping <Computergraphik>
Subtraktion
Elektronischer Fingerabdruck
Wort <Informatik>
Oval
Bildschirmsymbol
Computeranimation
Zentrische Streckung
Mereologie
Kantenfärbung
Computeranimation
Mapping <Computergraphik>
Benutzerbeteiligung
Gebäude <Mathematik>
Dienst <Informatik>
Figurierte Zahl
Chi-Quadrat-Verteilung
Computeranimation
Mapping <Computergraphik>
Bit
Quader
Front-End <Software>
Mereologie
Programmbibliothek
Projektive Ebene
Computeranimation
Mapping <Computergraphik>
Zentrische Streckung
Benutzerbeteiligung
Maßstab
Parkettierung
Mereologie
Vektorraum
Polygon
Computeranimation
Mapping <Computergraphik>
Weg <Topologie>
Maßstab
Flächeninhalt
Quader
Stab
Mereologie
Projektive Ebene
Information
Bildschirmsymbol
Computeranimation
Rückkopplung
Web Site
Subtraktion
Mathematisierung
Güte der Anpassung
Gebäude <Mathematik>
Stichprobe
Physikalisches System
Frequenz
Computeranimation
Mapping <Computergraphik>
Physikalisches System
Flächeninhalt
Projektive Ebene
Information
Datenstruktur
Schnittstelle
Retrievalsprache
Bit
Subtraktion
Prozess <Physik>
Punkt
Texteditor
Beschreibungssprache
Zahlenbereich
Räumliche Anordnung
Systemplattform
Login
Computeranimation
Datenhaltung
Demoszene <Programmierung>
Physikalisches System
Weg <Topologie>
Arbeitsplatzcomputer
Bildschirmfenster
Minimum
Datenstruktur
Figurierte Zahl
Einflussgröße
Lineares Funktional
Datenhaltung
Abfrage
Mailing-Liste
Quellcode
Physikalisches System
Bildschirmsymbol
Dateiformat
Web log
Mapping <Computergraphik>
Texteditor
Datenstruktur
Automatische Indexierung
Identifizierbarkeit
Information
Tabelle <Informatik>
Objekt <Kategorie>
Bit
Subtraktion
Web Site
Prozess <Physik>
Punkt
Quader
Datensichtgerät
Vektorraum
Computeranimation
Zeitstempel
Datenmanagement
Rendering
Skript <Programm>
Zeitstempel
Speicher <Informatik>
Optimierung
Ganze Funktion
Funktion <Mathematik>
Videospiel
Datenhaltung
Gebäude <Mathematik>
Mailing-Liste
Vektorraum
Rendering
Mapping <Computergraphik>
Texteditor
Datenfeld
Parkettierung
Mereologie
Server
Dateiformat
Information
Ordnung <Mathematik>
Tabelle <Informatik>
Beobachtungsstudie
Bit
Vervollständigung <Mathematik>
Physikalischer Effekt
Desintegration <Mathematik>
Open Source
Systemaufruf
Quellcode
Computeranimation
Task
Mapping <Computergraphik>
Dienst <Informatik>
Task
Software
Projektive Ebene
Information
Fehlermeldung
Bit
Prozess <Physik>
Punkt
Quader
Mathematisierung
Gruppenkeim
Zahlenbereich
Gesetz <Physik>
Login
Polygon
Computeranimation
Internetworking
Bildschirmmaske
Weg <Topologie>
Datensatz
Spannweite <Stochastik>
Front-End <Software>
Programmbibliothek
Public-domain-Software
Phasenumwandlung
Gerade
Schnittstelle
Open Source
Datenhaltung
Gebäude <Mathematik>
Validität
Nummerung
Quellcode
Physikalisches System
Binder <Informatik>
Konfiguration <Informatik>
Mapping <Computergraphik>
Randwert
Datenfeld
Verbandstheorie
Flächeninhalt
Parkettierung
Mereologie
Server
Projektive Ebene
Wort <Informatik>
Information
Extreme programming

Metadaten

Formale Metadaten

Titel Using OpenStreetMap Infrastructure to Collect Data for our National Parks
Serientitel FOSS4G 2014 Portland
Autor McAndrew, James
Lizenz CC-Namensnennung 3.0 Deutschland:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
DOI 10.5446/31610
Herausgeber FOSS4G, Open Source Geospatial Foundation (OSGeo)
Erscheinungsjahr 2014
Sprache Englisch
Produzent FOSS4G
Open Source Geospatial Foundation (OSGeo)
Produktionsjahr 2014
Produktionsort Portland, Oregon, United States of America

Inhaltliche Metadaten

Fachgebiet Informatik
Abstract The National Park Service has many well-known sites, but many parks do not have the GIS resources to maintain their map data. The Places project aims to solve this problem by empowering non-technical park employees and the public with the ability to make changes to the map. The Places project uses custom versions of existing OpenStreetMap tools for data collection and uses them to create an up-to-date base map for National Park web sites. This presentation will discuss how we plan to motivate mappers, how we deal with data validation, and how we plan to continue working with OpenStreetMap.
Schlagwörter National Park Service
OpenStreetMap
Crowdsourcing
VGI
TileMill
PostGIS
Government
Parks
Contributors
Data
VGI

Ähnliche Filme

Loading...
Feedback