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

Synchronising data updates with Kart version control

00:00

Formale Metadaten

Titel
Synchronising data updates with Kart version control
Serientitel
Anzahl der Teile
266
Autor
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.
Identifikatoren
Herausgeber
Erscheinungsjahr
Sprache

Inhaltliche Metadaten

Fachgebiet
Genre
Abstract
FOSS4G 2023 Prizren Do you get regular data-drops from suppliers, and struggle with viewing changes between releases and keeping everything synchronised? In this talk it will be explained how from both a consumer and a publisher point of view you can use Kart to make your life easier. — We’re drowning in data, but the geospatial world lags badly behind in versioning tools compared to our software counterparts. Kart (https://kartproject.org) is solving this with a practical open tool for versioning datasets, enabling you to work more efficiently and collaborate better. Kart allows you to quickly and easily manage history, branches, data schemas, and synchronisation for large & small datasets between different working copy formats, operating systems, and software ecosystems. Modern version control unlocks efficient collaboration, both within teams and across organisations meaning everyone stays on the same page, you can review and trace changes easily: ultimately using your time more efficiently.
EntscheidungsmodellCASE <Informatik>Computeranimation
TaupunktMereologieDatenverwaltungHilfesystemSystemplattformSelbst organisierendes SystemProzess <Informatik>VersionsverwaltungEntscheidungsmodellComputeranimation
E-MailZahlenbereichSelbst organisierendes SystemCodeSoftwareSchnittmengeMultiplikationsoperatorElektronische PublikationMessage-PassingAttributierte GrammatikClientPhysikalisches SystemFormation <Mathematik>WärmeübergangShape <Informatik>Rechter WinkelEin-AusgabeDifferenteMathematikTabelleBitHilfesystemWeb-SeiteDateiformatCASE <Informatik>VersionsverwaltungEntscheidungsmodellMarketinginformationssystemMultiplikationE-MailSchnitt <Mathematik>Computeranimation
Transkript: Englisch(automatisch erzeugt)
So one of the other things you can do with CART is look at synchronizing data updates and so our use case here, I come from coordinates, we build a data
publishing and data management platform and part of what we do is help organizations who publish data get it out to people who need to work with it and help them get on with their jobs which usually isn't trying to find data and muck around doing it. So as I say, CART is version control from geospatial data and we can trivially move through data history and the idea
is that we can share that stuff with other organizations and so maybe you get an email every month from your data supplier and it says here's the latest data and you're meant to load this into your system and work with it this is not uncommon right and inside the zip file is a shapefile and you get a
shapefile you get one of these every month and you're kind of diligent but you want to know what changed since last time. Oops, yeah that's right. What changed since last time and did they accidentally delete half of it? Did they add new attributes to their tables?
Who really knows? We don't really know from just the shapefile and so how could CART help you with this? So we have this thing we looked at importing data before and so we can import data remember from lots of different formats but in this case from our shapefile and we can replace it into our data set and so we can add a new commit to our history and CART will
figure out exactly what has changed since last time. So over time we can build up this history which we can see through like a log of here's June's data, here's May's data, here's April's and March's in February and this is where they figured out they made a mistake and they sent me some more data and so we can go back in time through these histories and if you
decide that the version is bad, is no good you can trivially switch back to what you had before and get on with your day. Your supplier never needs to know that you're working with CART they just keep sending you the emails every month and you're just super organized. CART can also help with
publishing data so we can do things like add tags to data where we say this particular commit and so that's a particular set of changes across potentially multiple data sets has this big long letter number code thing
and that refers to that data and only that data but we could have nicer names than that right we could have like 2023 July the good stuff and so we can add these tags and we can add these useful labels and we can add messages as well and again that's preserved through history and the people
downstream from us can use it and so your clients can fetch data from their awesome publisher and it doesn't matter if their network falls over in the middle they don't have to like call API's again and again and page through data fight WFS whatever they'll get it all reliably every time
if it breaks they just run it again they'll always get it it's not a problem and when they check out that tag that we said they get exactly that data and as they can easily review what you've changed we just saw that before and if they find a problem they can switch back to the previous version they can switch forward they can figure out what's going on they
haven't like hosed their database because they've bought in some bad data and so it makes it easy for them to do it this network transfer is really efficient it only transfers what's changed since last time so if you have a really big data set it's not going to they have to download it over and over again just pitches a little bit it's really fast