WalkLite in Mobile GIS: A Schema to Extend and Symbolize SpatiaLite
This is a modal window.
Das Video konnte nicht geladen werden, da entweder ein Server- oder Netzwerkfehler auftrat oder das Format nicht unterstützt wird.
Formale Metadaten
| Titel |
| |
| Serientitel | ||
| Anzahl der Teile | 183 | |
| Autor | ||
| Lizenz | CC-Namensnennung - keine kommerzielle Nutzung - Weitergabe unter gleichen Bedingungen 3.0 Deutschland: Sie dürfen das Werk bzw. den Inhalt zu jedem legalen und nicht-kommerziellen 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 und das Werk bzw. diesen Inhalt auch in veränderter Form nur unter den Bedingungen dieser Lizenz weitergeben. | |
| Identifikatoren | 10.5446/32148 (DOI) | |
| Herausgeber | ||
| Erscheinungsjahr | ||
| Sprache | ||
| Produzent | ||
| Produktionsjahr | 2015 | |
| Produktionsort | Seoul, South Korea |
Inhaltliche Metadaten
| Fachgebiet | ||
| Genre | ||
| Abstract |
|
FOSS4G Seoul 2015115 / 183
7
8
47
53
54
65
73
74
79
82
84
92
102
103
105
124
126
127
130
141
142
143
156
161
162
170
176
178
181
183
00:00
Mobiles InternetCoxeter-GruppeAbstandPhysikalisches SystemAussage <Mathematik>Figurierte ZahlKartesische KoordinatenLesezeichen <Internet>Produkt <Mathematik>TransportproblemKategorie <Mathematik>HalbleiterspeicherFormale SpracheMetadatenEinfache GenauigkeitVektorraumFaktor <Algebra>SymboltabelleTabelle <Informatik>Nichtlineares GleichungssystemMultiplikationsoperatorMaßerweiterungAutomatische IndexierungEuler-WinkelAudiodateiProzess <Informatik>DateiAdressraumOrdnung <Mathematik>PortabilitätAdditionApp <Programm>ProgrammbibliothekPunktTesselationMigration <Informatik>MereologieBildschirmmaskeBildschirmfensterInhalt <Mathematik>SystemplattformElementargeometrieGrundsätze ordnungsmäßiger DatenverarbeitungFlächeninhaltInformationsspeicherungOrdnungsreduktionCASE <Informatik>URLMAPDigitalisierungStandardabweichungBaumechanikOpen SourceTreiber <Programm>BitSoftwareentwicklerFormation <Mathematik>Elastische DeformationNummernsystemResultanteSoundverarbeitungDatenfeldMapping <Computergraphik>WinkelTranslation <Mathematik>PolygonFamilie <Mathematik>ZweiSkriptspracheSondierungInformationServerHumanoider RoboterProjektive GeometrieAttributierte GrammatikElement <Gruppentheorie>Bitmap-GraphikComputeranimation
08:08
Open SourceTreiber <Programm>ProgrammierumgebungVersionsverwaltungServerVektorraumMereologieKartesische KoordinatenAutomatische HandlungsplanungWasserdampftafelResultanteMinimumTabelle <Informatik>App <Programm>Ein-AusgabeMaßerweiterungHumanoider RoboterPortabilitätSoftwareentwicklerImplementierungSymboltabelleMobiles InternetAnalysisSkriptspracheBildschirmfensterGraphiktablettMAPBitmap-GraphikHyperbelverfahrenE-MailSerielle SchnittstelleRegulärer GraphReelle ZahlBildgebendes VerfahrenAlgorithmische GeometrieBildverstehenTranslation <Mathematik>Formale SemantikComputerspielStabFront-End <Software>Inelastischer StoßAutorisierungMathematikBildschirmmaskeInternetworkingProzess <Informatik>Formale SpracheSystemplattformGewicht <Ausgleichsrechnung>Verzweigendes ProgrammEinfach zusammenhängender RaumWeb SitePhysikalische TheorieFlächeninhaltFitnessfunktionRechter WinkelAggregatzustandArithmetisches MittelFehlermeldungTermSchätzfunktionFokalpunktWiederkehrender ZustandBrowserAutomatische IndexierungEinflussgrößeQuick-SortComputeranimation
16:13
Computeranimation
Transkript: Englisch(automatisch erzeugt)
00:04
So, today my presentation about walk light in mobile. Sorry, I had a little bit cold today. So, that's fine. I just want to share with you a kind of Gist experience and we did in China and we tried to migrate
00:22
a traditional desktop data schema to mobile application. So here is kind of some experience sharing. So, I'm Chen, I'm working for a tech corporation based in China and we have some kind of
00:43
in Chinese, many Chinese provinces and we did this kind of land use planning and also land use based Gist application development. So, some kind of background, a brief introduction
01:00
about our own Gist application is called the walk Gist. Originally means walk to the digital towns in China. So, it's kind of a Gist platform as of 1998. It's kind of a 17 year project. It's not open source project,
01:21
but it has a lot of open source elements. So, originally it's complying with OGC standard and representing vector and the rest of data by kind of work schema. And it also provides a C++ like script language
01:41
for customization and it has contained a family of Gist products. Walk survey, walk kind survey, office, walk flow, walk check, and so on. Originally designed for land use survey in China, now widely used for investigation, house property,
02:02
transportation, population, et cetera. So, but we had some problems in 2013 that was two years ago. So, traditional desktop based system, it's kind of outdated. So, then we had no application
02:23
that can be run on mobile devices and end users are limited in specific areas. Also, we had some difficulties encountered when we tried to translate data across platform, also translate various geospatial data.
02:43
So, what's the solution then? So, we tried to migrate the Gist platform from Windows to the cross platform. So, that was before 2013, the platform only run on Windows.
03:06
And after 2013, it runs on Windows, Linux, and especially Android devices. So, like these devices and also other mobile phone. Also, the device from, so,
03:21
microphone desktop to mobile. And the base library was work library only and now we included GDL, OGR library as part of the base library. A graphical UI migrate from GDI plus to GDI plus gear.
03:40
Gear was just kind of graphical UI libraries in Android. And so, we had built-in data formats before 2013 only work MDB, it's Microsoft Access MDB format. Also, SQL Server Spatial only run on Windows. Now, we create work schema, work SQLite,
04:03
it's called work light. And also, the traditional work MDB, et cetera. And vector data supported by 2013 was shapefile and also AutoCAD DXF and a map info. Now, we had supported all the data formats
04:21
as long as it's supported by GDL. So, what did we do? We just tried to apply our traditional work schema, it's kind of data schema defined in WorkTees platform. So, we applied the schema in SQLite, Spatialite. And first one, we just tried to adapt in OGR,
04:45
the SQLite driver. As I said before, we had all the OGR drivers supported in our platform. So, we then tried to adapt it and also extend the OGR SQLite driver
05:03
as kind of a work light data schema. We defined four metadata, especially for work schema. As long as you have these four tables, it's defined as a work schema. Work layers contains kind of metadata for layers
05:21
and a symbol factory for symbols. And also, a metadata and a metadata defined for other metadata defined in the system. And we had each work light layer corresponding to three SQLite tables. One table for features, one table for symbols,
05:43
and the third one for annotations. Annotations represents text annotations as well as raster and vector tiles also. So, then you can support vector and raster both.
06:02
So, first, work light features. One feature is actually an extension of OGR SQLite layer containing the OGC geometry and OGC feature ID. Also, work feature ID in order to try to migrate traditional work data
06:22
into the new work light data. And we have create time for feature creation, style ID represents symbol ID, style ID for feature style, also the feature attributes. So, spatial light here is also used for spatial index
06:41
because we are using SQLite driver, OGR SQLite driver, so it's kind of a spatial light. Second of all, work light annotations is OGR SQLite layer also. It contains OGC, SRS geometry,
07:04
but only two, there are two cases. One, points represents the location of text annotations, like the text. And then polygons represents the location of vector
07:21
and the raster tiles. So, you just use maybe four points of the tiles and then represent the polygon. So, we have OGC features ID and work annotation ID, once again, for the migration from the traditional data.
07:42
And then annotation field represents text that stores content of annotation, or in some case, representing the tiles, we just store the file paths of the tile. All the formats supported by JIDO are supported here as part of our annotations.
08:04
And style ID, once again, it represents the symbol ID for annotation style. Once again, spatial light is used for the spatial index. So, the third table, work light symbols.
08:22
So, it's actually just a regular SQLite table. It's an extension of the SQLite driver, so we use style ID representing the style, and it will be referred by the features and annotations defined in this layer. And style, actually, is kind of a serialization
08:44
of the symbol style. Also, we store the style name and the note. So, by this way, we not only try to extend SQLite to the vector and the raster both, also we do the map styling for the features and annotations.
09:06
So, what's the advantages of work light? So, first of all, it's now cross-platform. So, when we migrate from the traditional window desktop application to the cross-platform,
09:23
especially on mobile devices, such as the pad and the mobile phone, no data required now, required to translate from the mobile application data to the desktop application.
09:41
So, now the mobile application is basically used for data collection when you do the fieldwork, and then when you come back to the lab or indoor environment, you just try to import the data collected outside into a desktop,
10:01
and then you can just read and process the data on your desktop computer. And we have one schema for both, vector and raster data, because we had actually the features for the pure vector, and annotations for annotations, and also vector and raster tiles.
10:21
Also, we have symbols defined as kind of SQLite tables. So, it's also used for map styling. It's because we use spatial light index, so it's comparatively faster by using spatial light.
10:40
So, that's kind of our applications, both on tablet or phone. So, we have now, right now, we have the work-line applications in many aspects in China. So, most of them are proprietary software,
11:03
but a small part of them is free or open source. And all these mobile GIS applications are just work-line based, and they are used for land investigation, land use planning,
11:21
cadastral inventory, and the real estate analysis, and other routing navigation, as well as other applications. So, these are two screenshots of the different kind of scenario. The first one compare the different things of using.
11:44
So, first, the left side is the land use planning, and the right-hand side is satellite images. You can see the future, it's kind of a water area, and the future planning for the area, and then you can see its current situation.
12:01
And the bottom one shows some analysis results that can be collected by the implant building some kind of work-line data. You use this vector data, and do analysis offline. You don't need any server running behind.
12:23
So, it shows some analysis results. So, that's the work-line application right now. So, finally, the future work. We are actually part of JIDO also already.
12:44
WorkDriver, it's called WorkDriver based on ODBC. It's already supported in JIDO version over 1.10. And now we are planning to extend it,
13:01
because we need cross-platform applications. So, we probably want to extend this WorkDriver to WorkLight driver, because WorkDriver can be only run on desktop environment. So, WorkLight driver will be run more cross-platform, both on desktop and mobile environment.
13:22
So, we are planning to implement the WorkLight driver in JIDO. Actually, JIDO now has two branches, one for 2.0, so it's already merged JIDO and OGR. 1.11 is now still separate these two.
13:42
But, okay, anyway, we're just trying to extend our traditional desktop driver. And then we need a kind of big cross-platform, actually lightweight cross-platform SDK. We, I mentioned that we used, originally we used the kind of script,
14:01
C++-like script language for customization. And it's kind of close to C++, because in China, many developers, they want to just extend their experience by using C++, there are many, still many C++ developers there.
14:23
So, we just tried that script language. Now, for the customization. But then we need more end developers to develop our applications, both on desktop and mobile devices. So, we need to probably implement
14:42
kind of cross-platform SDK. And then we, right now we only support Android devices, so we need kind of a supporting iOS. So, we need to further improve and optimize the performance of our data, so for further using.
15:03
Especially for the online scenarios in on, say, this mobile applications. So, you can just access me, the first one.
15:22
This is my, our website. And this is my email. And if you're interested, really interested in WorkGeez, and also WorkGeez in mobile, I can show you some mobile application later.
15:40
But this one is just part of the devices, application on this one, devices. I have no connectors. So, I can show you after this. Thank you.