from Croatia. It's part of IN2 group. I won't bother you too much with the numbers, but we are the largest software development company in Croatia. We have offices across Eastern and South Europe, and maybe to say that IGEA is a

competent center for GIS. So we do a GIS development. Today's presentation and a solution is part of Kosovo Cadastral Agency Spatial Data Infrastructure that we have implemented recently. It is an ongoing project, so we have about two or three months of

development left. It is an integrated web GIS solution for spatial data definition and maintenance, and it consists of several functional software modules that were separate projects. GeoPortal, Cadastral and Land Information System, and Adverse Registry for

Adverse Data, Data Maintenance and Definition. One of the specialities of this project was that we were forced to use Microsoft software for database management system and for operational system because of contract of Republic of Kosovo and Microsoft. So

we couldn't choose that, of course. If we could, we would go with post GIS, but that was not in the question. And the other thing that modules that would be developed in this project

would facilitate the next sort of big software projects that we are part of. So this diagram shows the component architecture of the whole system. So from the user's perspective, we have a GeoPortal as a data dissemination point. You will recognize a couple

of those logos there. We use that all. So this is the, this down there is an internal system. It's an internet application for KCA users where they define and maintain the data.

This module deals with address register data and this module deals with cadastral data. So this is the central part of the whole system. It offers viewing and editing

capabilities for the data. So that's the point of the system that consumed most of our development time. This is the short overview of KCLS graphical component. We call it KG,

of course. It's integrated solution for definition and maintenance of KCA's data spatial data sets, both address register and cadastral. And it's a basis for development of other modules that would work with other KCA's information system.

Of course, we use the GeoPortal to disseminate the data toward the public. Its architecture is classic, classical three-tier architecture on a database level. We have a SQL server at 2008. On the middle tier, we have a Geo server with Geo web cache and .NET MVC3

business application. Client side is developed in open layers GeoX and XJS standard solution and the components, of course, base to SOA principles, communicate via services,

WMS and WFS and JSON. A couple of functions that our KG application offers. It's, of course, the main component is a viewer editor. It's a main point for the spatial data viewing

and editing. Then the feature class tool that enables us to define other feature classes and import data into our system later. GeoServer rests up before for publishing new feature classes on GeoServer once they are collected. Then we have import tool that we use for

importing the data into our system. Currently, we support GML shape, DWG, interlice and GeoTiff for raster data. And then there is styling tool which we use to dynamically style our geometries on a client side. It's client side. This is a short GeoPortal overview.

Of course, as I said before, this is a central public oriented software for dissemination of spatial data sets. And you can see the user interface here on this picture.

This is architecture of GeoPortal. It's very similar to KG application, except you will notice we have library portal enterprise here that wraps client side functionality and access proxy on middle layer for proxying WFS and JSON requests to business application. GeoPortal

enables us to view spatial and related open numeric data. It offers search and discovery services, ordering and download of data sets and products and upload of data sets by data providers and enables users to give feedback on data quality. So that can be checked.

This is the URL for GeoPortal. So check it out. So the next part of the presentation is about challenges that we have met during the development process. I have listed

308 challenges. So we'll go one by one until the end. So they better hurry. Okay. The first challenge that we knew it will be a big problem. This is very bad joke. So it's okay if you're not laughing. It's called bad joke. So we had to make a tool for curve digitization.

So what we did, we implemented quadratic curve handler. So that's open-ended development based on quadratic Bezier curve parametric equation. So we in the end approximated with line geometry and this is how it works in practice. So you digitize the first point,

the last point and then you use the apex to reshape the curve. This is the next cool handler that we did. This is a line curve, curve switcher handler that enables us to seamlessly switch between arc digitization and linear segment digitization. So it

enables fast digitizing for this is 4G. So when it comes to polygons digitization, we also implement several cool features. We basically what we did of course was to extend open layers

draw feature control. We use JSTS on a client side for geometry validity and topology checks and all operations. So the first tool that I will show you is a polygon splitting tool.

The second I remove polygon area and then adjacent polygon digitization. So this is a demonstration of polygon splitting tool. It's done client side. So it uses JSTS for splitting the polygon and we can see here the multiple, the one multi-polygon

has appeared in this configuration. It supports polygons with holes, so it's quite cool and it's done client side. This is a tool that we can use to draw multi-polygon. So on a client side with open layers, so we just add geometry while tool is active and it will add to existing

geometry. We can also subtract the geometry from a polygon and get a cool looking robot. This is a very cool feature. It's inspired on GIS, desktop GIS software and what we have

here is a first polygon and then we digitize a line around it and it just finishes a polygon automatically to close the minimal surface with the first polygon. You get the idea.

These are CAD-like tools for perpendicular and parallel construction. What they do first is they segment the line from point to point so that perpendicular and parallel construction would even make sense. Then when we select the segment that we want, they just programmatically

draw a parallel and perpendicular line and then you can reshape it by dragging. This is the nice example of a tool that guides the user how to use the application. It has

five steps. So basically what we want to do is to digitize a point that lies on an intersection of a circle and a line. So what the user does first is digitizes start point of the line,

end point of the line, center of the circle enters radius and then selects the appropriate point that he wants to use. This is a very cool feature. It's a topology preserving modified feature. It's basically extended modified feature from open layers and what it does

is when we drag a point that coincides with other points, that point goes with it as well. So the topology of our section is preserved. It also has a validity check. We don't allow

self-intersecting polygons and it has a rollback. So when we do an error on geometry, it just fixes itself to the last valid state. It, as you can see, I think it resides on a

JSTS for all the operations. It could use some modifications like insert of tool that would insert vertex on all coincident geometries and delete tool but that's a work in progress. Okay, basically our application is a full featured web editing application and we knew we

have performance issues when we decided to use open layers because the large number of features will always overburden the browser. It has limited capabilities, limited memory so

we had to think of something that would ease this up. So what we did was to extend open layer strategy bounding box so that implements seamless switching between vector and

WMS layers when based on a zoom level. So on the large scales, you have vector features and on the small scales when you zoom out, you have WMS features. So that means that you can draw on the full extent but you can't select anything. So if you want to select features,

you zoom in to one to 5,000 or whatever you want, whatever you set it and then you can select edit data and the data that is edited and selected that doesn't get unloaded when you zoom out again. So it's a pretty cool feature and the bounding box does everything, keeps track of the

WMS layer so you don't have to worry about anything. Of course, this active layer concept is inspired by edit session on desktop GIS tools and what we did was implemented the

one set of controls that can work on all layers so we don't have to duplicate controls. What was missing in open layers that work out of the box was that some controls don't have implemented set layer. So we added set layer method for every control that we use

and then when user activates edit session for some layer, all controls get rewired to that layer so they can work on it. One of the requirements of project was to enable user to dynamically

style vector and WMS layers so to be able to change the styling information about everything. So for this we use the GeoSolutions style editor component and what we do is when a user edits the SLD through the graphical interface we create vector styles from that SLD, dynamically

reload the icons for each layer node in the layer tree and besides that we have also overridden open layers renderer and open layers formatted SLD classes to add the support for label rotation which we needed as well. Multi-language support was a big issue for us. We implemented

in several layers in the application. On client side we have i18n language files for JavaScript

and then in the database we have multiple attributes for each language we have an attribute in a database but how to style geometries. We asked the GeoSolutions to develop a new function for that cause. It uses environment variables and substitution

and it's called property and you can send in a request the name of the attribute that you want to use for geometry styling that's pretty cool.

It's a very serious and official system so of course we had a lot of demands on spatial data quality control. We have a set of business rules and data naming convention that we have to follow and of course we check geometry validity on the client side that performance is okay so

it's good but for several others complicated topology and especially layer to layer topology checks and hierarchy checks that form hierarchy we use the database special data quality control

via procedures and such. On the middle tier we use a jtsport nts for several other checks so we could say we have a three-way control on our system. So because you remember the

graph from before all those systems are interconnected and so as the GeoPortal disseminates data for internal applications we don't want to overburden our internal infrastructure by

with public access so what we did was to replicate the database and GeoServer catalog from one system to another for that we use the Microsoft SQL server integration services and the GeoServer REST app before reconfiguration of data stores when we move them from one

storage to another. I think this yeah this is the last one so bear with me. Of course as I mentioned in the start we had to use Microsoft software for operating system and for DBMS and also

we use a application server for Microsoft IS7 and the .NET framework for and .NET MVC3 for our business application and for a GeoPortal we use a LiveRay portal enterprise platform

and it wraps our client-side functions in in portlets so that was one of the okay so we have plans for improvement of that system the development of the cadastre component

is still in progress so it's an ongoing project I don't know about a couple of months more and it will be over then we thought it would be cool to to offer some kind of a data preview when importing our data but that is that still needs to some thinking more flexible language and security would be would be nice also for for application which security except especially

and then the native support for curved geometries from from GeoServer and JTS and GeoTools and OpenLayers that that would that would probably need a tremendous amount of time and effort from the community to be implemented but I would I'm sure it will be implemented one day so of

course it is our duty and we would it would be nice that we try to contribute more to open source community so in the end of the project we'll we'll contact some of the developers from

OpenLayers and see if there's any any interest in in modules that we have developed for for this application so in the end to wrap things up we have learned that Phosphor-G is mature enough and flexible enough to to implement even very complex SDI implementations and business

applications so of course the the big plus is a great community very large community that that helped us in every way of that it could in a process of development the software is very versatile flexible scalable all the all the nice things and even if we want to we can easily

integrate it with proprietary software as we had to do of course we can only conclude that it was the the right the right choice for for this particular project and implementation okay so

that's that's it from me I think yeah we have enough time thank you so feel free to to ask something yes sir we've got five minutes for questions

thank you