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

GeoServer Orientation and Demo - Introductions

00:00

Formal Metadata

Title
GeoServer Orientation and Demo - Introductions
Title of Series
Number of Parts
266
Author
License
CC Attribution 3.0 Germany:
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
Welcome to GeoServer, a popular web service for publishing your geospatial data using industry standards for vector, raster and mapping. If the previous sentence made no sense to you, or if you are new to foss4g, or even just new to GeoServer, attend this talk to get pointed in the right direction! This presentation provides a gentle introduction to FOSS4G and we will do our best to say the quiet part out loud: - Demo: We have learned from experience, and will introduce GeoServer using a demo. - Usage: Concepts using both a demo, and diagrams to connect to your data and publish as a spatial service. - Checklist: Preflight check-lists capturing common oversights when deploying GeoServer for the first time. - Value: What role GeoServer plays in your organization and what value the application provides. - Community: How the project is managed, and a discussion of the upcoming activities.
Open sourceComputer-generated imageryEmailOpen setState of matterChemical equationView (database)Expert systemInternationalization and localizationOperator (mathematics)Student's t-testLibrary (computing)Projective planeMusical ensembleSelf-organizationComputer animation
Texture mappingDialectServer (computing)Source codeMachine visionEuler anglesCommunications protocolStandard deviationClient (computing)Content (media)Local GroupSoftware testingComputer-generated imageryVisualization (computer graphics)Extension (kinesiology)Function (mathematics)Entire functionVector spaceQuery languageRange (statistics)File formatDrill commandsScripting languageInformationCollaborationismInteractive televisionLibrary (computing)Open setMeasurementRaster graphicsDirected setFormal languageData modelDigital signalProcess modelingGroup actionLetterpress printingOpen setContent (media)InformationMereologyFile formatSet (mathematics)Standard deviationVector spaceVideoconferencingComputer fileMathematical analysisSoftware developerRange (statistics)Right angleWeb serviceMultiplication signAreaWeb 2.0NeuroinformatikLine (geometry)Ring (mathematics)Client (computing)Data managementQuery languageDrag (physics)SpacetimeFrequencyMusical ensembleOpen sourcePrice indexSoftwareComputer animationLecture/Conference
Configuration spaceLink (knot theory)Web serviceAnnulus (mathematics)MathematicsDemo (music)Time domainVector spaceRaster graphicsRange (statistics)Scale (map)Musical ensembleSpeciesProjective planeAndroid (robot)MappingBlock (periodic table)SoftwareKey (cryptography)MathematicsWeb 2.0Cartesian coordinate systemSoftware developerServer (computing)Web serviceVirtual machineComputer animation
SpacetimeConfiguration spaceWeb serviceContent (media)NamespaceDefault (computer science)Source codeDifferent (Kate Ryan album)User interfaceSource codeAreaProjective planeShared memoryUniform resource locatorConfiguration spaceCartesian coordinate systemMultiplication signNumberProcess (computing)NamespaceInformationMusical ensembleComputer animationLecture/Conference
Configuration spaceInformationDatabaseParameter (computer programming)OracleVector spaceSource codeDirectory serviceNatural numberInformationMusical ensembleComputer fileGroup actionWeb serviceJust-in-Time-CompilerConnected spaceDirectory serviceUniform resource locatorDatabaseCartesian coordinate systemParameter (computer programming)Computer animationLecture/Conference
Communications protocolInformationProduct (business)Physical systemBound stateMusical ensembleInformationJust-in-Time-CompilerDirection (geometry)Computer animationLecture/Conference
Communications protocolProduct (business)InformationPhysical systemBound stateVector spaceOpen setInformationMusical ensembleInformation systemsBitContent (media)Type theoryCommunications protocolPhysical systemVector spaceWorkstation <Musikinstrument>ExistenceDemo (music)Chemical equationComputer fileCountingComputer animationLecture/Conference
Raster graphicsOpen setLocal GroupGroup actionConfiguration spaceOrder (biology)Data structureContent (media)Musical ensembleGroup action1 (number)Web pageInformationBitVector spaceState of matterComputer animationLecture/Conference
Group actionConfiguration spaceProcess (computing)File formatSineCross-site scriptingComputer iconVirtual machineContent (media)PolygonText editorGenetic programmingClique-widthAttribute grammarDefault (computer science)Virtual machineFile formatCASE <Informatik>Musical ensembleMoment (mathematics)RoboticsBitGraph coloringReading (process)CodeFunctional (mathematics)Software repositoryTable (information)Goodness of fitTexture mappingWeb pageDifferent (Kate Ryan album)State of matterTouchscreenDefault (computer science)PolygonCartesian productTranscodierungFormal languageComputer animation
Java appletIntegrated development environmentServer (computing)Open setSpring (hydrology)Directory serviceComputer programFitness functionMusical ensembleCartesian coordinate systemSpring (hydrology)Entire functionSoftware developerRun time (program lifecycle phase)Event horizonStructural loadGreatest elementResource allocationSheaf (mathematics)Process (computing)Server (computing)Computer animation
Java appletMedical imagingArchitectureLibrary (computing)Image processingProcess (computing)Spring (hydrology)Component-based software engineeringSoftware frameworkSoftware developerApache WicketUser interfaceExtension (kinesiology)Axonometric projectionDivisorSource codeModul <Datentyp>Core dumpRevision controlNumberVector spaceOracleData modelInformation securityContent (media)Standard deviationData managementMathematical analysisWeb serviceDatabasePoint cloudVolumeCompilerGradientAerodynamicsLibrary catalogConfiguration spaceEntire functionDirectory serviceMusical ensembleException handlingModule (mathematics)Customer relationship managementIntegrated development environmentRevision controlExpressionWorkstation <Musikinstrument>Extension (kinesiology)Software developerProcess (computing)Configuration spaceBitMathematical analysisStandard deviationStudent's t-testAdditionServer (computing)MappingInformationMereologyVector spaceMultiplication signInformation securityNumberTextsystemFamilyCodeSoftware testingMatching (graph theory)Token ringComputer animationLecture/Conference
Software developerConsistencyVotingOpen sourceCore dumpSource codeAdditionTexture mappingRefractionCollaborationismMusical ensembleProjective planeMereologyGame controllerLattice (order)Computer fileSource codeCollaborationismSoftware developerComputer animation
Computer configurationSoftware testingBinary fileServer (computing)Performance appraisalWeb applicationVolume (thermodynamics)Self-organizationCASE <Informatik>Product (business)Installation artInformationSet (mathematics)Cartesian coordinate systemMereologySoftware developerMusical ensembleComputer animation
InfinityMiniDiscPasswordDefault (computer science)InformationMultiplication signSource codeComputer animation
Transcript: English(auto-generated)
So my name is Joey Marlowe. I work at Pencom. You're going to check that for the last few weeks. You can do that now. I'm a professor at the U.S. University of Michigan.
I'm very proud of my student. My experience is that she's a library professor and I've been working on it since. I volunteer with the Court of Appeals for Social and Social Management and also the First Foundation, working with different projects. I'm going to go to the operating room. I'm going to introduce myself.
Thank you. I'm the executive of the University of Michigan. I'm a 50-year-old. I work in the operating room. I work with the government of Aston, the experts in the house. I mostly deal with local government,
students, houses. We try to sit down. We try to multiply our exercises. I'm a global user of YouTube, and I'm a GIS specialist. So, he's been, he's actually really nice.
He really asks the question on the left. He's quite diverse in the U.S. So, he's one of the kids in the house. He's in the building. He's designed for children. This is what he's doing as well. So, there's a series of tools that we're going to talk about on Monday. So, what is new this year with the project?
So, things we've been working on recently. There's a tool set for future financing, which gives a clearly balanced view of what's cool and exciting and interesting and all the tips and tricks and things like that. And we're going to look at the leaders, what we call tools that are used in common, interesting ways. And that's a chance to see how tools that are used can be used in different organizations,
so small to large, custom solutions and sometimes not. So, yeah, let's start by answering what do you include secrets for? So, Jim Silver is really a web service that's for sharing your information, accomplishing your information.
It's open source, and it's for sharing your information there. So, if you're working out to share a level, Jupyter can do nothing. It doesn't just stop at showing the green picture. It also shows the data, shows the data behind the map, so people can get all the data and access it and get all the analysis.
And it doesn't just stop at sharing the data. It also allows people to remotely edit and, you know, get up to action and things like that. Jupyter can do part of that search. So, the important part about Jupyter is it's time for interoperability.
So, the idea is that I'm going to give you your information right now, so if you've got your data that you know is sexual, you can do it. If you've got it in post, yes, you can do it. If you've got drag rings that you've got, I'm sorry, you can still do some of that. You should present it to the managers at the end of the line. The goal, the goal is to take
the data and bring it together and share it with as many people as possible. So, to do that, we actually make this industry standards. So, rather than defining our own way to do the web and everything, we use one of these industry standards called web microservices to come out of the computer space and get us our data.
But, under the idea here is publishing this to the sector of water-drinking, desktop bodies, and not-good clients and above clients to make use of your information. And we do have more protocols over time. So, we kind of, you know, transition through between these XML standards in your PC to a more modern rest
and interesting standards that will be kind of all around in the years to come. So, this is the opposite of an automatic reality. We don't want to invent anything ourselves. We actually want to go with what we're talking about. So, we teach you all about this. Also, we're going to publish maps.
Each dataset is going to be published as a layer of content. We can actually gather those layers into a layer group. So, you might be doing that to, you know, on a range of areas and things like that that's going to be shared with people. And if you go through the little layer reviews, you can kind of chat with your service or opinion about things. You're right. So, yeah, true service is the only thing
that we're going to be using in this. When you publish your maps, you can also go and shop as a map as a layer of content, or you can actually publish the entire thing as a top set of content. And that's more used for mapping formats and about formats.
You know, keep in mind that the map doesn't always need to look like an image. Things like SVG and the data development will actually come out as a kind of vector that's all already preprocessed inside. And you can also use it for other things like video printing or vector files. For sharing with other data,
it actually lets you access the data by running them, using things like XML formats and EML and so on. And it also lets you do queries against the data sets to select just the data and the information you need. And also lets you do editing.
Do you want me to talk closer? Okay. Now, for those of us who shared last year, okay. So, how do we use it? Do you want me to get this one?
So, the change server started out using this. So, this is a web mapping application, sorry, application that you can use to configure and set up the data. And it's also a resting development with your own machine.
The key to know that this application is here, it's not really a change server. This is just a slot. The reason for that is the work services are being published and you can see those kind of little blocks here by the network services and feature services and so on. The examples I'm using today
are from the Android project. So, I'm going to focus on the process. There will be different kind of issues with configuration. This is kind of set up as a long walk, but I only have access to a DVM solution. This can be shown in some of the configuration space.
If we get some time towards the end, I don't know if it'll show more. So, the first concept that I'm going to talk about is the workspace. The workspace is you can see there's a folder that you publish information in. So, just sort of add a number of different workspaces.
You can choose how long you're using most workspaces for. You might be setting up a workspace for each of the nine applications you're supporting, or each data team or project team that you're supporting that wants to share information with you. For the XML format,
each workspace needs its own XML namespace. So, the name that we gave the workspace is going to be worked. It's going to show up as a prefix on each area published, and then the name is going to be used in the XML documents also.
So, when we go to set up a workspace, we're going to go to the workspace and click New. And we're going to need to fill in a name. In this case, I'm using a name for network, and we're going to need to use some kind of XML namespace. So, each of the web address and project team that
use the web interface. This is going to go really well with this presentation. So, the next step, also about workspace, is we actually connect to the different data sources that are available. So, if you're doing a direct data source, the idea is
in this case, I'm going to take a look at the JIT files. I think one of the advantages of database or postgres is that we don't want database and action parameters. It's really going to be a good idea. So, this data is going to be internally used for you.
So, this allows you to do things like switch from one postgres to postgres, or from a directory to JIT files, JIT package, and anyone else on the application can start. So, in this case,
I'm going to ask me to do some work. In this case, I selected a directory of JIT files, and I provided a name and culture, and for the JIT parameters, it's the final location of this web, and I have all of the JIT files downloaded, and when we get saved, I'm going to comment on that data connection.
It works similarly on the master information. So, in this case, I'm located in a JIT service. You don't really really know what you're going to do.
So, the next step, once we connect it to our data, we're going to go into the steps of publishing the data, and from the improvement, you're really going to need some driving directions, the JIT service, so that you can share your information about this. So,
the information we need, the basic information we need, is we need to provide a name, a gene-neutral name for the content, and then we can also provide a gene-neutral terminal and answer describing information about it. The other information we need is the spatial reference system with the information, what the data is measuring,
whether it's not long, or maybe meters, or local connection, and then we also need the bounding information. So, the goal here is to share the information in enough detail that people can find out where the world is, and what is called
maybe a little bit of information or describing what the information is, so they can decide what they care. So, what we're calling is a different name for the data product. So, when we're publishing a map, it shows us a layer. When we're publishing vector data, it's called a layer, it's called a feature type.
And when we're publishing master information, it's called a coverage, and when we're publishing a file set, it's called a subset. But for JIT, it's the only thing that we publish over there, and it shows us the models and protocols. So, in this case, we'll demo
a whole new layer, and it's listed in the content that's available, and I can choose to publish one of those. I can then go do the data count on the layer screen, and fill in the name and download the outside. I can then go through and
demo check the world references and information, in this case, CPG or HSS, and I can choose to calculate the balance in the front of the HSS or from the station that's sent to the HSS code, and then I can calculate all that
for no other existence. So, here's what I can say. I'm glad, I'm accomplished. We're going to do a little bit of review, but in this case, I can see I should say so. This is our preview, this is our interview, and there's a lot of information, but it's just a chance to see if you just
are on your way there. It's a simple strategy, I'm going to publish a new data. I need to demo check the name and the title and the answer, and make sure that it's in the right system as well.
So, with all the data I've also made this out of knowledge, I can then combine the two and make it seem to be a nice sound for the interview. So, when I go to the layer group page,
there's a little bit of a trick here. The layers in the layer group are defined in the draw layer, so if no one's able to, so if I want the layers to be at the back of it, in this case, I want to draw on the last layer first, and then draw the vector information on the top. And you see that as such, how do we know?
It's not going to be as hard as you can see after that fix. So, in this case, I'm going to the layer group page and click the value of that group, and call me at 8-7. And then I'm going through adding the first disaster there,
and secondly, the state profits there. So you can see that those are all here. I'm not sure if you guys can't see this yet, but I'm sorry. I know that I can go and check that out in the layer group and see that I can combine this information into a simple example.
Okay. So, just seeing the whole data, it's not quite so much fun. If there's any cartographers in the room, do we have any cartographers? Okay. Okay. If you care about making the data are so pretty, just because
it does offer a very good sense of information, and you can define the styles using a format like SLD. This is intended for a machine that uses an XML format. It's not very fun to edit on hand. So we do recommend using a style in language
that's intended for humans. There's what we call CSS, which is very similar to CSS used for our pictures. And there's another one called YSLV, which is a little bit more similar to like a Python way of doing things with very carefully indentation and so on. So there are some built-in styles provided.
But, yeah, you would also very well be able to use a tool like Jeegis to generate these SLD fonts that Jeegis has used. Okay. So for Jeegis we go to the styles page and we add in our style. We can add out some of the specific workspaces like the one we just created.
In this case I may want to call them out probably not yet. Because they want to send out data based on what we actually use. And I chose a format called YSLV, which is a little bit more readable. And I hit generate. I'm sorry, we can't see that, but it's just a few moments
of text showing the style of a polygon. You can see in this case it's now kind of quite orange. And I can edit that in this case to use a function. So I'm using a function called recode to recode
from a map code attribute, and I'm mapping the one to a specific color and so on. So a little bit like the lookup table and when I apply that, I can see that right now it's now styled in a little bit more of a friendly way with a different color and screen texture.
And I can choose to publish that I can choose to name the single style of the default for my state product set. So if I'm going to
add some kind of support, it is a job allocation or job load application. So I can see at the bottom of the page, you have a runtime event and an application server, which is used for applications. The entire program is kind of fit to
a remote log stream, which is familiar to job developers. One of the advantages of a job server is that it's emotional, and so you can actually install one section more and get used to those three different things at the top.
So we've got a number of exceptions, so if you make the children's server an audience of all the exceptions, then these exceptions are known as part of the job server. So each time you make a new release to your server, all of the exceptions are released as well. So it's very easy to make sure that the two things are compatible
and promise they have the same version that they already have. So just an example of some of the exceptions that are available if you're using Oracle extension, there's Oracle Datastore. If you want to do analysis and processing, there's a word processing extension for Jupyter which you can install.
If you want some information on the Spark cluster, there's a Jupyter extension that you can set up. If you have very interesting SQL concerns, you can actually do an external security module for Jupyter's because that's what the running permission is like
based on the area of interest. So the idea is you might give something like data permission but only a little bit in the security. Very much in vector trials, there's a vector trials extension. So there's a very rich ecosystem of additional modules that you can install to teach you how to use them.
We also have some community modules which is more of a research development. So these things are still in the process of being constructed, or maybe they're not very well maintained. You know, this is the initial standard out there, how to work with graduate students and developers.
But it's also being used by consulting teams, taking on challenges to their customers. So this is kind of a bit more music to give you an idea. There's a great playground to see what's available and if there's any interest in sporting. So there's one thing
called GPC 3.0 which is used to set up a cluster of users and gets you really interested in developing your own latency. There's another one that's more important which is called the token configuration testing environment and moving over to a production environment.
There's a code match there that we talked about. There's one called Manifold, which is a document mapping folder. I think that one actually graduated to be an extension. And there are these new families which you see set up, which you see throughout, and I think that will just make our future strong.
It's pretty close to the earlier use. The standard itself is what thought was. Any questions about that? Anything people are looking for? So the producer itself is brought to you by Evil.
This is an object-saver community. And it's set up as a full community of human sources of social damage. So this public-saver community is formed. It's part of the social foundation, you know, to check everything. We've been trying to convince of skills for the project
steering committee, so developers use these technologies and so on. So we've been trying to develop a very nice solution. You can see the collaboration. The project was originally set up by a long public in New York. Other different companies averaged the project over
hundreds around the world. And yeah, so we had a meeting that we'd like to be seen. We'd search files and companies and so on, generating features. So it's all set up as a vendor control.
So just in case you're trying to get out, if you go to the geocentric website, there's a volume in the world that you can get on the wall and you can solve a lot of parts that you can buy. And that's really intended to let you chart things out, see if you like it. So you're totally welcome to use that information.
There's also a lot of product development. And so this is more of a formal workshop where you're sharing the web application. And so if your organization has a standard application set up by Tomcat, you'll be able to get a set of products from IT team and install a geocentric software.
We have a lot of tools installed at the end, but we no longer have enough installing. So, yeah. There is now official Docker features that are available in Docker. And there's a few companies such as Manulay that do all the juice reviews.
So there's wonderful knowledge that you'll see right about here. So thanks! I think I've got my time here in the morning. So if you don't mind, let's take questions.