Integrate Spatial Data in your business processes
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 237 | |
| Author | ||
| Contributors | ||
| 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 | 10.5446/57208 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
FOSS4G Argentina 202148 / 237
12
15
16
23
26
36
44
52
53
54
59
72
90
99
114
121
122
123
124
127
129
130
139
154
155
166
203
204
219
223
224
230
00:00
Archaeological field surveyProcess (computing)DiagramMeeting/InterviewComputer animation
00:35
Software developerOpen sourceSineInformationSystem programmingImplementationDisintegrationVirtual realityElectronic GovernmentService (economics)Self-organizationPlanningData managementSystem administratorCartesian coordinate systemElectronic GovernmentComputerComputer fileCASE <Informatik>SynchronizationGoodness of fit40 (number)
01:35
DatabaseState of matterMultiplication signElectronic mailing listDifferent (Kate Ryan album)Projective planeInformationMereologyDigital photographyProcess (computing)Hill differential equationEmailAreaWater vaporMoment (mathematics)Error messageFile formatReal numberThomas BayesComputer animation
03:13
Standard deviationNetwork topologyComputing platformOpen setOpen sourceCartesian coordinate systemLatent heatSoftwareAreaMultiplication signComputer animation
04:26
Kolmogorov complexityDisintegrationStandard deviationMeta elementCurveServer (computing)Process (computing)Cartesian coordinate systemTheoryThomas BayesLevel (video gaming)Digital photographyMoment (mathematics)Multiplication signWater vaporOrientation (vector space)File viewerComputer animation
05:52
Mobile WebCurveCartesian coordinate systemFunctional (mathematics)Multiplication signStack (abstract data type)Program flowchart
06:52
Mashup <Internet>Computer networkMobile WebImage resolutionField (computer science)Mobile appVector spaceLevel (video gaming)
07:42
Latent heatImage resolutionData managementGEDCOMFunctional (mathematics)Power (physics)Image resolutionField (computer science)State of matterMereologySoftware development kitLevel (video gaming)TesselationVector spaceDifferent (Kate Ryan album)Computer animation
08:44
Embedded systemDatabaseOvalVideo gameWater vaporBit rateAreaSlide rulePoint (geometry)Level (video gaming)InformationMultiplication signProduct (business)Client (computing)Event horizonThomas BayesProcedural programmingCommutatorHill differential equationMoment (mathematics)Form (programming)Position operator19 (number)Basis <Mathematik>DataflowDifferent (Kate Ryan album)Cartesian coordinate systemLine (geometry)VideoconferencingMathematicsReal numberGame theoryReverse engineeringINTEGRALLocal ringAddress spaceType theoryComputer animation
13:32
Different (Kate Ryan album)MereologyOrder (biology)Lipschitz-StetigkeitCartesian coordinate systemVotingShared memoryComputer animation
14:34
Markup languageUniform resource locatorForm (programming)NumberEvoluteForestLevel (video gaming)Cartesian coordinate systemGame controllerMappingMatching (graph theory)Computer animation
15:12
Menu (computing)Gamma functionMIDILevel (video gaming)Computer fileExpressionForm (programming)Query languageInformationComputer animationProgram flowchart
15:40
Computer-generated imageryPoint (geometry)Category of beingMereologyInformationForm (programming)Type theoryGastropod shellProgram flowchartComputer animation
16:08
Form (programming)InformationLevel (video gaming)Address spaceType theoryRight angleSystem callVideo gameCASE <Informatik>Point (geometry)Figurate numberComputer animation
17:14
EvoluteCASE <Informatik>Cartesian coordinate systemNumberMereologyReplication (computing)Form (programming)Computer animation
17:36
Real-time operating system1 (number)TouchscreenForm (programming)Point (geometry)Level (video gaming)Type theoryWave packetGreen's functionDataflowAreaMultiplication signComputer animation
18:37
Data managementDatabaseLatent heatPoint (geometry)Stack (abstract data type)CASE <Informatik>Greatest elementComputing platformFunctional (mathematics)Table (information)Projective planeField (computer science)Cartesian coordinate systemVector potentialRow (database)Wave packetTerm (mathematics)Multiplication signOpen sourceWorkloadTurtle graphicsMetropolitan area networkProcess (computing)Annihilator (ring theory)Computer animation
22:29
Computer networkMobile WebServer (computing)Open sourceProjective planeAddress spaceRepository (publishing)Point (geometry)CASE <Informatik>Extreme programmingProcess (computing)Game theoryYouTubeFeedbackWater vaporLogicMereologyOnline chatClient (computing)Perfect groupDifferent (Kate Ryan album)MappingCartesian coordinate systemLevel (video gaming)Server (computing)Task (computing)Interior (topology)AreaTorusNetwork topologyField (computer science)CalculationComputer animation
26:22
Diagram
Transcript: English(auto-generated)
00:16
Can you confirm this? Okay, now I see myself. Okay, so well, I still have commented I'm
00:25
going to make a follow up on how to integrate the spatial data in business processes. First of all, I will go very, very fast to give you some background on the company I work for, not for commercial, but to let you know that we're a company, let's say that
00:43
have different businesses. One of them is the GIS and the other one is e-government services, electronic administration and that kind of things, files and so on. So, sorry,
01:01
I think there are some problems with my mic. Let's see, equal mic volume, better now too. Is it better? Okay, I hope so. I'll try to speak louder in any case. So, the thing
01:25
is that we have a strong background in the GIS and in general purpose for e-government applications. We work worldwide and we have realized that there is a desynchronization
01:42
of spatial and the non-spatial world. Okay. Traditionally, these have been very separated worlds. It's true that in the past 10 to five years, we have tried to integrate GIS in every place that the users are more and more aware of the needs
02:03
of having the GI information updated in the processes, but the real problem that we face everywhere is that still there is a big difference between both worlds. You know, you go to a project and you have in a separate part the non-spatial
02:25
data and then the spatial data. And that's a really big problem for us because the spatial data that you actually have are inventories, which are kind of photos at a certain time. You have a list of licenses or a list of places or a list of
02:44
whatever at a given moment, but they do not remain alive because these entities live in the non-spatial world and from time to time come to the spatial world yearly, mainly. So, we started to think some time ago on the need to
03:03
integrate these both worlds. Well, nothing new to you, but we will tell you our experience here and where we are. So, what we did is to create kind of applications where the spatial data will be very, very, really easy to
03:26
manage. Okay? So, actually, all the users have the opportunity to create their own layers and have them updated. We gave them the abilities to have the
03:45
tools to create layers, to update them, to give them styles, to build some tools specific for their needs. So, they will be able, these non-spatial
04:02
users, they will be able to manage their own spatial data. Of course, everything, and this is very also linked with the other talk, also with only with OGC standards, following the standards and open source software.
04:21
So, we created some platforms that was during time, and they had a lot of tools and capabilities. So, we made a modular orientation where they could easily select what were the basic layers to add in a map and also to add
04:45
the tools that they needed for a moment. So, we reduced, even though it's quite simple to deploy, for us, let's say for GIS people, it's quite simple to deploy a GIS, let's say a GIS server or a WMS or a WFS or whatever
05:05
server, and then a map viewer with tools and so on. For these non-average GIS users, it is a huge learning curve. So, we, in our processes in the
05:20
years, back in the years, we built applications to try to make them publish the spatial data in three clicks, trying to avoid that the spatial data was kind of photographs, as we commented before, so they could live at the same time and they could be updated by the users themselves.
05:46
But, the thing is that even though we tried to do so, still, there was a learning curve for them. To mention all that we provided to manage
06:04
the spatial data, we made an API so the applications could integrate. We gave them lots of functionalities. I'll come to this later. We have a very, let's say, simple or a very classic flavor with all
06:25
these technologies. We can go from, let's say from business to technology, as you prefer. Okay? So, as you desire. So, in any time you can write
06:45
and we can answer. So, we provided this technology stack and built all these functionalities. We made them with this three clicks approach to publish layers, even in WMS or using vector data as PDF, also editing
07:06
data, downloading WFS, editing with WFSD, metadata, mashups, you could embed your map wherever with the layers you wanted to. You can embed
07:21
this. This is HTML with JavaScript at the end and CSS. So, finally, we also gave them mobile apps to field work so they could have a mobile application ready to go. We gave them the chance to publish in social
07:40
networks. And even more functionalities, styling, high resolution printing, search engines, vector tiles I mentioned before, and more than others. But still they were separate worlds. Still they needed to go to the spatial part. Still they needed to get into a map. They
08:04
needed to draw. They needed to edit. They needed to put the pieces together. It improved the situation because it spread the knowledge of the GIS but didn't solve the initial problem, the state of the problem at
08:25
the beginning where these worlds were completely different. Still they had separate lives. And our main goal here and our difference from other approaches was to join them together. And so coming back to the
08:46
initial slide where we said we are a company focused in GIS but also in non-GIS product, we realized that we had the problem and the solution
09:02
inside the house. So we started to work together, not in the clients but in our own products, to offer a different value to the clients by the integration of the spatial data in all the procedures and the workflows
09:27
that the rest of the applications were dealing with. I mean, when I'm referring to non-GIS applications, for example, for local entities,
09:42
licenses for a bar, a restaurant, or let's say a public event, whatever is a workflow, all that has a spatial address, has a street name, has
10:00
very, very specific spatial data which lived in separate worlds. So for our workflows, what we try now is to with all the tools that we have built during time to manage the spatial data, integrate them in our own
10:23
products. So the clients themselves wouldn't have the chance to avoid the GIS world. So we incorporated all the tools, all the layers in these
10:43
tools, specifically in one tool, which is the creation of the forms. This is not GIS related, but we integrated in a general purpose application where you build some formularies to the user so they fill in
11:05
their data, their address, where they want to ask something. So we integrated a map, we integrated straight map reverse geocoding. It may seem simple things, but in the end, in the few years, well, a couple of years
11:23
ago, people were not feeling a normalized address. They did not have a reference street name. So they could type different streets, they could even fail in the spelling. So in the end, well, we realized that the GIS
11:43
was needed and was needed specifically at that point, at that time when you are creating the data, no matter spatial or non-spatial, because it's all the same entity. So finally, we gave them the possibility
12:02
to locate the positions on a map. And then we have noticed, it's a little bit different. Finally, we came with a product that has really like to the customers, because they feel that they have everything
12:24
managed in a single point. And all the information can be changed live. So each time they provide with a restaurant license, the layer of restaurants in the city changes as the license is approved or
12:45
rejected or whatever. So this was the real game changer for us. We had lots of tools, lots of ways to make maps very, very, very, very easy. But in the end, we needed to integrate them and was
13:06
not an actual integration. So I think I'm okay with the time. I'm six minutes left. I'm just going to show you a couple of live things, a small video to let you know. This evolution, so
13:22
you are aware of the changes that we have made, which I insist it may seem very simple, but it has made really, really a difference. So in the past, we gave the users the possibility to build a map. Well, you upload a layer, you connect to a database,
13:44
you add a layer here, you mark or unmark the layer you want. You can put or remove the buttons you want, whatever. Really, really easy to the users. But the thing is what I
14:01
commented before, it didn't work. It didn't work as much as we wanted. It worked very, very well because it was a lip for the users. But it didn't work in the way we wanted. Or we expected to or we were looking for. So what we made
14:23
then was to move it to another application to include it, embed it as a part of a workflow. So in order to avoid
14:41
running out of time, let me move here. This is what I wanted to show you. This is an application where you are building a form, okay, for a specific purpose. No matter what. Then you have a control that you say it's an evolution of the map. Then you have a control where you
15:00
say, okay, I have the location of a restaurant precisely. So then you add it. You put the map that you have also, that you have created here. You have several maps to choose. You put the map there. And then you add it
15:22
here as a component. And you can also interact with the rest of the form by adding expressions on the JSON file or the info of the WFS request that you made. And you can put a query to extract certain
15:43
property from a GeoJSON that is returning it. And then you fill another part of the form with that information. So as you type in or you put a point on the map, non-spatial data, traditionally known as
16:03
it, is filled. So we can see another example. This is how we build the form. Let me show you how the form is then presented. You have the usual license request for restaurant. Then you have it
16:25
there, your map as you configured before. Then you put the name, then you put certain aspects of the license. And finally, what you do is to locate and put the correct address. You look for your
16:45
own address, which previously you had to, what you were doing was to type it free, which was a mess in the end. And then you have this information right from a street map, from an
17:05
airport map. And then you can verify, then you have a lot of info there. So the goal here as I commented, it is a very, very simple use case. It is not rocket science. But believe me,
17:22
that is an evolution for the way that the non-spatial applications behave with spatial data. And finally, you can see how it is integrated. There is a special part in the application, which is called G1 Spatial. And
17:43
then you have all the layers. This was one of the ones that we have been editing with the forms updated on real time. So what you have finally is all the licenses that are being
18:01
on a workflow, correctly positioned on a map with the real data with no mistakes and a layer that is alive in real time and updated by completely non-GIS users. They do not know what is
18:24
behind. They only type the street name or they paint on the screen. They put the point in the place and that's it. So well, this is it. I'm trying to go very, very fast, but I hope
18:41
I explained the point. Okay. So this is how we have integrated spatial data. No very fancy functionalities, but very simple, but very, very, very effective for the use cases that we have, that we have faced with our customers. So this is it. Still on time, I
19:06
think. I cannot hear you. Better to unmute. Thank you very much. Thank you, Enrico. Thank you for your impressive talk, the amazing platform you
19:21
presented to us. And I heard it's also raining in South Africa, but it stopped here. So you probably can better hear me now. There's a question that came up and the question is when integrating GIS and non-GIS workloads, what role do unified
19:43
data management platforms play? Have you considered using a unified database for GIS and non-GIS business data? Yes, we have tried everything. We have tried several approaches there. We have faced that, for example, you can do it,
20:01
maybe the audience is pointing to, for example, it can be as simple as creating a layer in a table in a database with the spatial data and then making the non-spatial application to populate that
20:22
table in the post GIS. It can be as simple as filling all fields in a database and forget about these tools. And I agree, depending on the case, it can be very simple. But the thing is that we, during time, we have evolved these tools
20:40
to provide the users real, well, powerful tools. And the role that this platform to manage all the data has played here is to also engage a little with the customer because we provide them very, very specific tools. Maybe this is
21:01
very, very simple, but once they have the platform for a simple use case, they see the potential of it and they start using it for a general purpose, even for the very, very specific GIS. So I will say that in some cases, we have
21:20
started with bottom to top with very specific use cases, maybe only with a table and then the platform and so on. And in other cases, we have started directly with the platform because the users have that need and in the end they have integrated. So depending on the case, the platform may have a
21:43
different role. But for us, we have always tried to put it there because in the end, it is very, very useful for the users. Okay, thank you. I have another question. You're using a lot of
22:02
open-source stack in your things and you talked about that these are very simple functionality that you offer. But is there any drawback to the projects you have when using the things? How do you manage that? That
22:20
would be really interesting, I think. Yes, indeed. Well, I have not gone into the details, but if you see, for example, we have created a little small open-source project here, which is Mapea 5, which has its own
22:41
GitHub repository under this and you can put it there. When we find any issue or we have any need or when we fix any issue or anything that, well, we are in contact with the respective communities, so we can, well, have that feedback to them or even
23:01
contribute with a commit, respecting all the needs and the timeline of the project. But yes, in one hand, we revert, we try to give it back by contributing to the project as we are able to find some enhancements or we
23:22
produce some enhancements. And in the other hand, we have created on top of this another project for whoever who wants to use it. Okay. So, and one more thing, sorry, all we do in the end is also open source because all we do is for the
23:42
government and here in Spain we have a very good policy, let's say, that you have to provide all the sources and then it becomes open source and is offered to the community. So all that you have seen is in their respective client and it's part of the entity.
24:03
Perfect. I'm happy now with that. Thank you. Another question came up. The question is, when integrating a GIS workflow, do you find that it generally just needs to be simplified or do non-GIS users need completely different workflows?
24:24
Again, it depends on the case. They are very, very complex. For example, for hydrology, they needed extreme processes to give some permissions to extract water from a place,
24:41
calculations, so they needed a lot. So the logic was put in the GIS part and they needed very specific tools and probably they needed also to simplify their approach. But the real deal was in the GIS part. I have seen the other way around
25:01
when the users are not very GIS enthusiastic, they are fine. If they have an address and they have a point and they say, wow, that's what I wanted. But depending on where they are coming from and their business, you can face the extremes. You need really, really
25:23
tough tools to decide on your workflow. You need just to have a point in a place. So we have faced everything, as I guess you have done in life. I'm laughing because I know the game
25:40
and the opposite is when people from non-GIS came over and see and they told me, oh, you're a GIS guy. It's always easy because you have these marvelous pictures on your application, which really helps. I don't have to say it in English, but they say, oh, little maps,
26:01
brochures, YouTube brochures, touristic maps and things like that. Cool. Okay. So get your kudos in the chat. Thank you very much for your presentation and for the listeners. We have three minutes to switch over and then we proceed with the
26:21
next talk.