Glob3 Mobile. A New Approach To Mobile GIS 3d
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 | 95 | |
| Author | ||
| License | CC Attribution - NonCommercial - ShareAlike 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 and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this | |
| Identifiers | 10.5446/15542 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language | ||
| Production Place | Nottingham |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
|
FOSS4G Nottingham 201342 / 95
17
25
29
31
32
34
48
50
56
58
68
69
70
82
89
91
00:00
Metropolitan area networkMappingSoftware development kitGame theorySoftware developerLevel (video gaming)Texture mappingMultiplication signMobile appBuildingXML
00:27
Enterprise architectureFingerprintGroup actionMatching (graph theory)MathematicsGroup actionBuildingComputer animation
00:50
UsabilityCross-platformAndroid (robot)Business modelPoint (geometry)Decision tree learningPoint cloudCross-site scriptingVector graphicsDiscrete element methodRaster graphicsTask (computing)Real numberDigital rights managementEnterprise architectureCore dumpGroup actionHill differential equationFree variables and bound variablesCAN busGame theoryDigital rights managementScaling (geometry)Object (grammar)Machine codePlanningMultiplication signGroup actionField (computer science)Different (Kate Ryan album)Remote procedure callMetropolitan area networkAreaCASE <Informatik>Local ringIntegrated development environmentTouchscreenWeb applicationHypermediaReal-time operating systemPhysical systemSampling (statistics)File formatMappingBusiness modelCartesian coordinate systemMassArchaeological field surveyMathematicsMereologyStructural loadPoint (geometry)Universe (mathematics)Moment (mathematics)DampingSoftware developerDialectStaff (military)Computing platformComputer simulationLevel (video gaming)UsabilityKey (cryptography)Workstation <Musikinstrument>Event horizonoutputPower (physics)Server (computing)Android (robot)Texture mappingTouch typingMobile appEnterprise architectureResultantArtistic renderingPoint cloudTwitterTask (computing)Raster graphicsWeb 2.0Focus (optics)RoutingDigitizingMachine codeCache (computing)Java appletSoftware frameworkComputer animation
08:08
Denial-of-service attack3 (number)EmulationPoint (geometry)Pay televisionPoint cloud
08:23
Asynchronous Transfer ModeLemma (mathematics)SimulationObject (grammar)Moment (mathematics)InformationCartesian coordinate systemTesselationComputer animation
09:12
Metropolitan area networkElectronic visual displayCartesian coordinate systemService (economics)TouchscreenDifferent (Kate Ryan album)Digital rights managementData storage deviceComputing platform
09:58
Wide area networkDemosceneMappingPointer (computer programming)Metropolitan area networkAsynchronous Transfer ModeInformationArtificial neural networkMaxima and minimaLarge eddy simulationSimulationArmInformation managementGoogolVideo game consoleData storage deviceTouchscreenCartesian coordinate systemDemosceneMobile appMoment (mathematics)Overlay-NetzServer (computing)MereologyFreewareQuicksortDifferent (Kate Ryan album)HypermediaMultiplication signRootComputer animation
11:23
DemosceneOpen setDemo (music)Metropolitan area network3 (number)Frame problemMultiplication signMobile appDemosceneReal-time operating systemDescriptive statisticsMoment (mathematics)Computer animation
11:50
DemosceneMetropolitan area networkMappingHand fanComputer fileState of matterPhysical systemMenu (computing)Cartesian coordinate systemMobile app
12:06
Raw image formatDemosceneMetropolitan area networkHand fan3 (number)InformationSoftware engineeringDemosceneState of matterAreaSoftwareMathematicsComputer animation
12:29
DemosceneComputer animation
12:44
DemosceneComputer wormInformationMetropolitan area networkACIDArmInterior (topology)Arithmetic logic unitPointer (computer programming)Moving averageEvent horizonPhysical lawLevel (video gaming)Multiplication signSpeech synthesisCategory of beingDemosceneGraph coloringCartesian coordinate systemGreatest elementMoment (mathematics)Computer animation
13:22
Maß <Mathematik>DemosceneInformationOpen setDemo (music)MappingArmWide area networkPolygon meshCategory of beingAreaMoment (mathematics)SoftwareService (economics)Beta function
13:40
Grand Unified TheoryCASE <Informatik>Revision controlData storage deviceNP-hardoutputCartesian coordinate systemAndroid (robot)Computing platformDatabaseDifferent (Kate Ryan album)Web browserSoftwareRepository (publishing)Cache (computing)File formatWeb 2.0TouchscreenService (economics)Product (business)ImplementationTranslation (relic)FrustrationCASE <Informatik>WhiteboardLibrary (computing)Machine visionState of matterStatement (computer science)QuicksortElectronic mailing listFreewareBusiness modelOrder (biology)Hand fanAuthorization
Transcript: English(auto-generated)
00:00
Hello everybody, you hear me? You want to sleep? You want to talk? Bad time for talking. Here we are. This is G3M. It's an SDK for developers, designed to build mobile native
00:22
map apps for any platform and for any device. You hear me properly? Closer. Whoa, I can see. This is what I'm going to tell you. While we're here, the challenges we have
00:43
faced, the capabilities of our SDK, the architecture, and at the end you're going to see it in action. So, first of all, the origin. We started over NASA whirlwind, building a framework which was called Blob3. We didn't focus then on mobile. But at the same time,
01:06
people from the University of the Canary Island were building a tool for 3D scenarios, also in open source, was called CapAware. And somewhere in the route we meet, we started
01:21
working together, trying to do something for mobility. But we didn't like the results. So a couple of years ago, we decided to throw away and start again with the new development from scratch. And that's what we're going to show you now. The challenges were mobility,
01:47
which is now very, it's an evidence, it's more than a trend. We all are in mobility, but three years ago, four years ago, we wasn't that sure that everybody was going to use it. And it was going to have a strong impact in many industries, like humanitarian
02:03
aid or agriculture, mining, defense, all this stuff. Now it's an evidence. Another challenge was fragmentation. And you see there are some different platforms, Apple and EOS, Android, and others that are going to come now in the future. And this fragmentation
02:27
is about software, about hardware, and it's going to increase in the future because there are many forks escaping from Android. We're going to have new and new devices in
02:43
many of the environments. So when you build applications for mobility, you have to fight against this, or focus on just one single device, one single platform. Performance. We like maps. We like maps that you can pan, you can zoom, you can obtain
03:06
data quickly. So it's very difficult to find the exact performance with the new devices. They give you more power in the device, but also a better screen, more resolution,
03:24
so the power is used for the home, the home device in their work. And your map is still going a bit slowly. That's another thing we wanted to overpass. And usability, of course. We wanted to do it with a screen touch. It's not that simple. When you build
03:47
applications for a PC or web applications, you don't resize them, you don't reduce them to be able to use them on a mobile phone or on an iPad. You have to
04:01
rebuild, redesign everything. And that's what we did. These are the capabilities. We said multi-platform, but it's not exactly like that. We made an SDK to allow developers build very easily and quickly native applications for the
04:26
different platforms. Okay. In 2D, to 5D, and 3D, and also scenario maps. From a Google Earth
04:40
kind of visualization, the whole globe, to a local scenario with the detailed scale and data of a local environment. That's an example you'll see later. We can use it with any kind of data, from raster to digital elevation models, vectorials,
05:06
cloud points, objects, and 3D models. These data are written in the server, and we translate them in a few formats to enhance the rendering. And you can
05:21
also use, developers may use a very rich symbology, with labelings, markers, and also they can use Carto CSS if they want. It's built to be used online and offline, which is very important for people that do field work in remote areas where there's
05:42
no signals. And you have the same data online and offline. You can capture and save all the things you're watching on your screen to work with them when you're out of the signals. Here you can see, well, you'll see that better later because you're
06:05
a lot of people. 3D objects and all the stuff. There are subsystems in the SDK for task management, cache management, and also for animations. And this we offer
06:23
real time, real, real time. So when a developer needs to build an application that is completely connected to the server, maybe this is the SDK because changes in the server are immediately
06:40
received and displayed on the device. A little bit of architecture. To make it stronger and more powerful, we're developing C++ and translate it to Java. So with C++, we're
07:04
very close to objective C for iOS and with Java for Android and HTML5. These two platforms share about 75% of the code. So it's very fast to code for both platforms
07:26
for developers. They don't waste a lot of time. They can share more of the things they code for one for the other. And now, well, this is an example in action.
07:41
This is what you have to code for an Android app. Okay. Press symbol. This is where you can find applications in iTunes and Google Play, our web. And this is an example of
08:12
slider cloud points. I think it's 3 million points. 800,000 points. Yes, a few points
08:24
only. Over the terrain, how is it moving? This is an object flying. It's a simulation of a plane, but the flight is real. So it's following where it is at each moment and
08:52
managing a lot of information, lots of tiles and lots of information linked to the object. And I'm going to show you now how we build applications. My colleague Manolo
09:21
is going to explain it. Manolo sounds very Spanish, isn't he? It's a service built over a digital platform. It's a service of management applications
09:42
on different stores or on the web. You have to do a login. It's the first screen where you can create applications. Every application that you create in the previous screen, finally,
10:08
it's an application on the Apple store or Google Play or wherever. And here is the console where you create the different scenes into the applications. You can create
10:21
applications for events, for whatever. Every application has any scenes that you want. In this case, you have five scenes. Here, I'm creating a new scene. There are other
10:46
scenes. You can set a base layer. You can set a overlay layer. And that's your scene here. It's the same that you want to see on the mobile application. This part
11:03
of the screen is exactly like the mobile. You can create a new scene. In the moment that you create the new scene, thanks to the real-time server done with WebSockets, everything that you do here is in the same moment in all the telephones. This avoid the problem of deployment, for example, on iTunes. You have to wait 10 days, 12
11:32
days, the day that Apple wants. You deploy the apps one time. All the data could be
11:40
changed in the moment that you want. You're compressing in real time. Here is the new scene. You can create. You can work. Here's the new scene. You put the description. And you have to put a screenshot because this is the menu that you find on the
12:03
mobile application. Below is an iPad that is working with the application. That's the new scene. In this moment, I want to change the layer, the base layer. I want to change the base layer. I change the software layer for Macwebs, for the open
12:26
area. I change the layer. I'm changing. On the mobile, it's the same thing without deploying. If you change other things, like color, you can change data
12:51
or other application properties. For example, the color at the bottom of the sky or more things that we are planning in the future. It's changing exactly in the
13:06
moment. I need another screenshot because it's not the same scene now. I have the new screenshot. Now, the menu, when you click on the menu, you can see the new
13:22
application. The idea is that you can publish immediately the data that you need. This is a software service. At the moment, it's not finished. It's in beta.
13:40
But we hope to be in production in a few weeks. For release, simply, you have to go to this screen and select the store where you want to
14:04
publish. Any questions, please, in Spanish, Portuguese, or Russian?
14:25
What's your license? VSD. Your local cache data. What format is it? The cache is an SQL lead. It's the only way to have the data in all
14:48
platforms. It's different implementation, but we have abstract methods to do this. It's in SQLite. We have a piece of software in the repository to translate the data
15:06
to this database. The same database are interchangeable. You can't have the same data in iOS, Android, or actually on the web now because every browser has a different
15:24
implementation of SQLite. We have fighting with the mobile, fighting with the browser. It's hard.
15:42
You call this a platform for mobile. Is there any reason not to use it for webGL? You don't have my strong voice. You have to shout.
16:05
We're using webGL only for the browser because the mobile doesn't run correctly.
16:21
You can use webGL. The first translation is to webGL. It's natively on iOS. It's native on Android. The translation is to webGL. Of course, the webGL version works on Android too, but it doesn't work on iOS
16:44
because Apple doesn't work. The webGL works on the platform. The platform is webGL. The performance is very good.
17:00
Is it possible to have more than one globe on the screen at the same time? More than one globe? It's more complicated than iOS. It's more complicated for different reasons, but it's possible too. You have to think that this is an SDK. You can do what you want.
17:20
You can do from a complicated application like Mebu, the software service that we have built over there. You have a very simple application only with a map, with vector, or what you want. From the most simple globe or application to a very complex application depends on
17:46
your development. Are there any more questions? Thanks again.