MapServer Status Report
CC Attribution 3.0 Germany:
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.
Bonfort, Thomas
Morissette, Daniel
Meißl, Stephan
Lime, Stephen
2015 was a big year for the MapServer project with the release of the 7.0 major version. This presentation highlights the new features included in this version, like WFS 2.0 for Inspire, UTFGrids, or heatmaps, as well as a recap of the main features added in recent releases. It further shows the current and future directions of the project and discusses contribution opportunities for interested developers and users. After the status report of the MapServer project there will be the opportunity for users to interact with members of the MapServer project team in an open question/answer session. Don’t miss this chance to meet and chat face-to-face with members of the MapServer project team!
 Good afternoon, everybody. Welcome to the afternoon session. My name is Anthony Scott. I'm chairing these three talks. So without further ado, I'd like to hand over to some developers from the app server team, Thomas and Daniel. Hi, everyone. Thank you for coming. So this talk is going to be about status reports about the app server, what's been happening in the past year and the past couple of years before that. I'll give a short overview of the project statistics, then go over some of the main new features we introduced with our 7.0 release last year. Then some insights about what's coming in for the next major version. And Daniel will take over then and give us an overview of the existing client applications that gravitate around the app server and help you to do other things in text editing map files. So just a brief history for context. The app server is getting rather old. So 1994 was the birth of it. And in the years after that, many known people come to the project, 95 franc. The first official release was in 1997. Paul joined and then added post-release support in 2001. There were the first user conferences in the beginning of the 2000s. And in 2006, the creation of OSGO itself, the app server was one of the founding projects. We've been presenting in all the major phosphor Gs that's happened since 2006. We also meet up as a development team to sprint for one week, once every year. So we've been to Toronto, New York. Last one was Paris in this winter. We're in the planning phases for the next one to happen in 2017. For more recent history, we had our previous major release in 2011. Some intermediate releases, once every one or two years, depending on the speed of development. Our last major release was version 7.0 in July last year. And since then, we had maintenance releases at the beginning of this year and another one to come soon. Concerning the statistics of the project, so it's 200,000 lines of code, 13,000 commits, roughly 120 contributors in total. Mailing lists which are supplied to 1,800 people for the user list, which is user-oriented. And 400 people on the dev list, which is more where the architecture discussions go on. Map server is directed by international PSC. We currently have 14 members on it. Nine people from the US and Canada. And five people from Europe. The major developments and changes go through RFC processes. And we are up to 116 RFCs last one with a couple of months ago. Statistics for the past year, the current activity is 350 commits with contributions coming from 30 people. Just a reminder, we are OTC compliant and we are actually certified for WMS 1.3 and WCCS 2.0. WCCS 2.0 is actually the map server, the reference implementation for NEOGC. I suspect that we could be WFS 2.0 certified. It just needs a champion to get the ball rolling and start the process. So last year we released map server 7.0. Maybe something like a year later than we would have wanted to. That happens. Major new features in that 7.0 version were support for UTF grids, support for 2.0 WFS, support for heat maps, styling done via JavaScript and V8 directly from the map file. And a big overhaul of the filtering happening and the syntax used to filter attributes and do geometric filtering. That was the addition of layer level compositing and blending modes and other less prominent stuff. All the refactoring of the text rendering pipeline supports all languages of the world. Remove the ancient GD renderer, bitmap labels, worked on encoding using different GD encoded data sources inside the same map file and there was work on becoming WCCS 2.0 compliant. WFS 2.0, I won't talk much about it because I don't know much about it but basically here it is, we support WFS 2.0 and we should be certified. JavaScript V8 is supporting JavaScript language to create complex style on the run. Basically through JavaScript code analyzing each feature attributes and creating styles on the fly for that attribute, used basically for a very complex symbology. Big thing was rework on the attribute in geometry filtering. Previously for most WFS requests, Mapserver would pull in all of the data for the given bounding box and then do the filtering on its own. Now those filters were applicable, pushed up to the underlying database drivers and so the amount of data transfer between those and Mapserver is much less important and speeds up WFS queries quite a lot. So somewhat simpler to use because all the filtering is done with the Mapserver syntax and translated to postures or Oracle spatial on the fly. Also added support for heat maps, so it's a vector to raster processing vector input source and raster outputs quite configurable depending on the color space you want to interpolate and the scaling of the data you want to use, how each feature is weighted using Mapserver expressions and supporting tile modes for seamless tiling of heat maps. Just a couple of examples, same data sets with different filtering and weighing parameters added. We added layer blending and compositing modes, so this is very useful for people doing health shading and playing rasters on top of vector data. Here's an example where the health shaded raster is applied with a multiply effect which gives much, usually much nicer rendering than default compositing modes. For the text rendering we rely on the half bus library which has become the de facto library for handling international text. The image shows you basically the steps happening for an Arabic example. So the first line is the set of characters coming in one by one and inversing them for right to left parts of the Arabic text. And then the actual shaping which as you see drastically transforms what the text should look like compared to the individual glyphs that are used inside of it. Also have the ability to specify finally which fonts you want to be using for each languages. There's still no real fonts out there covering all the languages of the world, so allowing you to mix those. That came with also quite a nice performance improvement. So it's the time taken by the label cache to do decluttering of labels for a given map. So the new speeds, notice the log scales, so where the new version is at one second, where all the one was a thousand seconds. You shouldn't be using that many labels on your map, but it's nice to have anyway. So this is an example of another complex script for the Tibetan. Now features coming for the upcoming 7.2 release, we don't have an ETA yet. First one is choosing better positions for labels on, I don't know how you see it on the screen here. The left one is the previous version, so you see if you place the labels on sharp road corners you end up with overlapping characters and or labels that wouldn't be rendered because they have too much overlap on them. 7.2 version, we're trying to detect where the sharp, those sharp angles are and trying to offset the labels so those places fall on character breaks in the text for nice outputs. 7.2 also supports layer filters, basically blurring in shadows. So here you see there's an inner glow inside the rivers with a blurring effect on them and shadows you see also around the buildings with basically taking the original shape blurring it, applying some opacity to it, supplying a translation to it. It could also be used to other things to apply color adjustments on the fly to a given layer to do a black and white output for raster layer for example, stuff like that. We're still exploring the possibilities of what additional filters could be added, but that's those that are available for the time being. We also want to support vector tiles, we have an initial implementation that's not integrated into the master branch yet, but more or less ready. Not limited to XYZ addressing and MacaTOP projection, we're reusing the WFS interface to access those tiles from Mapserver which allows you to do stuff like renaming attributes, selecting which layers you want, whatever. With this, we have a few open issues that are waiting for champions to either fund or develop or take over. So we have PHP Maps Script that's not supported with the new PHP 7 releases. Vector tile driver needs a bit of love to become completely integrated with the sufficient configuration options. We'd like to have the JavaScript V8 stuff needs upgrading for the new releases of V8. There's also been work happening on the documentation side. So a few years ago, Tom Agatier switched the translation stuff over to TransFX for crowdsourced translation of the Mapserver text, that's an ongoing task. And in the cold sprint in Paris last winter, we had a team of Mapserver users who took over the task of modernizing the Mapserver tutorial we were previously using. We set up continuous integration of quality assessment, so each commit is tested with the roughly 2,000 functional tests we have on Linux and on Windows. And we had a big, closing big number of tickets thanks to Stefan also, this winter with 700 issues that were closed in just a few hours, very efficient. We decided to close tickets that didn't have an inactivity for more than one year, over the next year, so close bugs going back up to 2,000, I think, 2002 maybe. And now I'll hand the microphone to Daniel who's taking the rest of the parts. Thank you, Thomas. Is my mic, yep, okay, good. So I'm going to talk about two common questions that we've heard over the years from users and that we're going to address here. First one is the request for having a list of service providers and having a place where service providers can actually list themselves. So that's something that we've addressed this year. There's a new service provider page that's been added to the website. There's three categories of providers, core contributors, that's the people who are members of the PSC or actually have commit rights, so those are the people who can actually integrate your stuff into the software. But then there's also contributors who are active people, many of you are in the room, who are able to support other users in the use of Maps Elver, so you could be listed there if you want. And then there's another service provider section which is a place where companies could list themselves if they provide a complementary product as long as it's open source and it's related to Maps Elver. So if you want to add yourself, we made it so that you have to prove that you are kind of technical, so read RFC 116, the instructions are there. If you cannot make sense of it, you may not fit in the provider's directory. Another question that we hear often is, well, where's the GUI? How do I edit those map files? I'm tired of using a text editor for editing map files, so that's been a question that came up over and over over the years. And I mean, there's a GUI, it's called VI or Emacs or Sublim Text. It's been around forever and everybody's got their own flavor of it and it's stable, it's well tested, so what's the problem, right? Well if you look at, it's actually a good thing that Maps Elver didn't come with the GUI because there's actually, when I prepared this, there's about a dozen products, open source products, and I'm not even talking about non-open source ones, that are built on top of Maps Elver or built around Maps Elver and actually make your life easier in using the software. So Maps Elver remains the core engine that renders the map for those products, but then they help you do your job. So let's go over them relatively quickly because I think I have like five minutes left, less than five, it's gonna be five. So I'm not gonna stick strictly to map file editors, but I'm gonna also include in that because there's a gray area between application frameworks and map file editors. There's a gray zone in between, so I've included some of them that are not strictly map file editors in the list. And since it's a list, any list is likely to miss some important players or important items, so don't blame me, don't blame me if I missed your favorite product, just go to the wiki, and this is intentionally small and long so that you don't read it now, go to the wiki, you can list yourself if you have an open source product that's not listed already. So the first one, and they're listed by the way in Alphabet Scala Order, and I started with the ones that are officially OS Geo Project. So Geo Moose is built on top of Maps Elver. It's a framework for building applications. It's an HTML, JavaScript on the client side and PHP using PHP Maps Script on the server side. So that's the first one. It's really a framework for building applications, and it's built on top of Maps Elver. The Zoo Project is not necessarily about editing map files, but it actually provides a web processing service on top of Maps Elver, so it implements the web processing service spec. It provides services, APIs, a bunch of operators, so if you need the web processing service, that's a good one to look at. Chrome app probably wins my personal prize for simplicity. It's a bit of HTML and JavaScript that you just download. You do file open in your web browser, and you're going, nothing to install. Open your map files, and it gives you a hierarchical view of the objects in your map, and then you click on them, and it gives you a dialog to set the parameters, so it's as simple as it gets. EOX server, this one is a bit like Zoo, which implements a web processing service. EOX implements the Earth observation standards for WCS and WMS on top of Maps Elver, so if you need inspire and that kind of stuff, Stefan would be one person to talk about that. Magna Cartel implements the Cartel CSS standard, and it's a converter to turn the Cartel CSS into Maps Elver map files and map nick configurations. It does not come with a GUI, an editor, so the way Oliver calls it, he calls it a BYOE, so it's bring your own editor, but it does provide a viewer. I saw Oliver's presentation, it's actually quite interesting, the Cartel CSS, it's a good mechanism for styling. There's another one called Map File Generator, I don't know too much about it, it was listed by its developer on the website. It's listed as still being under development, but it's also providing mechanisms for reading and editing map files. Map Manager is a desktop application that runs on Windows that allows you to, it provides you a WYSIWYG environment for editing your maps and previewing your changes. Map Mint is a cloud-based service initially which has been released open source recently, so it provides a bunch of, it's more than just a map file editor, it's actually a complete application development framework. I believe it's built on top of the Zoo project as well. So you could have a look if you want a complete application development environment, including building maps. Scribe UI is another option for editing map files, it's really, it's got the map view on one side and your, the map editor on one side and a map view on the other side. Similar to Magna Cartel which has the Cartel CSS method for styling, Scribe has another syntax which is called a Scribe syntax. As of you have seen Cartel CSS, Scribe is kind of the same mechanisms and same concepts, variables, and automated scale management but in a more map-saver-like syntax. It supports both the Scribe syntax and the map-saver-map file syntax. Then there's two export plugins, one in GVSig. So a plugin, if you're using, if you're a user of GVSig, there's an export plugin you can use to publish your project in maps.ver and same with QGIS. It's called the RT maps.ver exporter, look for it in the list of plugins. I was told that it requires mapscript for installing so it's not necessarily easy to install but once you've installed it, it's going to work well to take your QGIS projects and publish them with maps.ver. So that list, we've gone over 11 products that can help you in your work with maps.ver so there are some GUIs. So that's it for my quick walkthrough of those products so we wanted to keep some time to have interaction. We have several of the developers of those products that I just mentioned in the room because I suspected that some of you may have questions like does this product really do that? It's time to ask it. If you want to ask questions, tell us about the developments. It's time for that too or bring up concerns, ideas. Quick question regarding the vector tile support you shortly mentioned. Are you adhering to any standards regarding vector tile? So the mapbox standard or what kind of standard are you using for that? Yeah, it's the mapbox, it's the mapbox type specification except that it's more than just a web mac at all projection. And you also provide the styling based on the styling you have configured with the map server or how do you do that? There's no styling in the vector tiles. So the styling is pushed over and then it's up to your client to do the styling. Okay, thanks. How's the window support in the map server at the moment? I believe the MS4W package has been upgraded recently because it was lagging a little bit. So I'm not the, you know, Jeff McKenna is the guy who's maintaining MS4W so I'm not the right person to answer about it. You might know more about it. Do you use it? It's active releases that are going on right now so yeah, it's very active. And there is also, Jürgen, do you still do builds in the... There was TAM. No, but there's TAM has builds but there were some as part of OSDU. TAM also did the OSDU for W builds. Okay, because there's the OSDU for W builds but I'm not sure how accurate those ones are. And Mike is providing some dockers for those who are on Linux and using dockers. Are they listed on the downloads page, the dockers? I don't know. They should, yeah. We could ask you for making sure they are listed. Thanks Mike. Thank you. And TAMS. TAMS provides also automated builds either for the releases or I think as a daily build chain, building daily releases of MAP server and Google and maybe others, I don't know. Time for one more quick question. No, okay. Thanks very much. Oh, pick up on. Thank you. Any plans on supporting the WFST transactional? With tiny AWS, do we not do transactional? So tiny AWS does the transactional WFST but it's... Some people complain that it's not exactly like the full, it doesn't support everything that a MAP file supports but our answer to the WFST question has been to integrate with tiny AWS a few years ago because that would require too much changes in the core. The core of MAP server is really optimized for rendering and WFST is going both ways and it's not necessarily... It would be technically possible but that's not the ideal thing to do. Do you have something to add on there? No. Okay. Thank you very much guys. Thank you. Thank you.
 Good afternoon, everybody. Welcome to the afternoon session. My name is Anthony Scott.  I'm chairing these three talks. So without further ado, I'd like to hand over to some  developers from the app server team, Thomas and Daniel.  Hi, everyone. Thank you for coming. So this talk is going to be about status reports about  the app server, what's been happening in the past year and the past couple of years before  that. I'll give a short overview of the project statistics, then go over some of the main  new features we introduced with our 7.0 release last year.  Then some insights about what's coming in for the next major version.  And Daniel will take over then and give us an overview of the existing client applications  that gravitate around the app server and help you to do other things in text editing map  files.  So just a brief history for context. The app server is getting rather old. So 1994 was  the birth of it. And in the years after that, many known people come to the project, 95  franc. The first official release was in 1997. Paul joined and then added post-release support  in 2001. There were the first user conferences in the beginning of the 2000s. And in 2006,  the creation of OSGO itself, the app server was one of the founding projects.  We've been presenting in all the major phosphor Gs that's happened since 2006. We also meet  up as a development team to sprint for one week, once every year. So we've been to Toronto,  New York. Last one was Paris in this winter. We're in the planning phases for the next  one to happen in 2017.  For more recent history, we had our previous major release in 2011. Some intermediate releases,  once every one or two years, depending on the speed of development. Our last major release  was version 7.0 in July last year. And since then, we had maintenance releases at the beginning  of this year and another one to come soon.  Concerning the statistics of the project, so it's 200,000 lines of code, 13,000 commits,  roughly 120 contributors in total. Mailing lists which are supplied to 1,800 people for  the user list, which is user-oriented. And 400 people on the dev list, which is more  where the architecture discussions go on.  Map server is directed by international PSC. We currently have 14 members on it. Nine people  from the US and Canada. And five people from Europe. The major developments and changes  go through RFC processes. And we are up to 116 RFCs last one with a couple of months  ago.  Statistics for the past year, the current activity is 350 commits with contributions  coming from 30 people.  Just a reminder, we are OTC compliant and we are actually certified for WMS 1.3 and WCCS  2.0. WCCS 2.0 is actually the map server, the reference implementation for NEOGC. I suspect  that we could be WFS 2.0 certified. It just needs a champion to get the ball rolling and  start the process.  So last year we released map server 7.0. Maybe something like a year later than we would  have wanted to. That happens. Major new features in that 7.0 version were support for UTF  grids, support for 2.0 WFS, support for heat maps, styling done via JavaScript and V8 directly  from the map file.  And a big overhaul of the filtering happening and the syntax used to filter attributes and  do geometric filtering.  That was the addition of layer level compositing and blending modes and other less prominent  stuff.  All the refactoring of the text rendering pipeline supports all languages of the world.  Remove the ancient GD renderer, bitmap labels, worked on encoding using different GD encoded  data sources inside the same map file and there was work on becoming WCCS 2.0 compliant.  WFS 2.0, I won't talk much about it because I don't know much about it but basically here  it is, we support WFS 2.0 and we should be certified.  JavaScript V8 is supporting JavaScript language to create complex style on the run.  Basically through JavaScript code analyzing each feature attributes and creating styles  on the fly for that attribute, used basically for a very complex symbology.  Big thing was rework on the attribute in geometry filtering.  Previously for most WFS requests, Mapserver would pull in all of the data for the given  bounding box and then do the filtering on its own.  Now those filters were applicable, pushed up to the underlying database drivers and  so the amount of data transfer between those and Mapserver is much less important and speeds  up WFS queries quite a lot.  So somewhat simpler to use because all the filtering is done with the Mapserver syntax  and translated to postures or Oracle spatial on the fly.  Also added support for heat maps, so it's a vector to raster processing vector input  source and raster outputs quite configurable depending on the color space you want to interpolate  and the scaling of the data you want to use, how each feature is weighted using Mapserver  expressions and supporting tile modes for seamless tiling of heat maps.  Just a couple of examples, same data sets with different filtering and weighing parameters  added.  We added layer blending and compositing modes, so this is very useful for people doing health  shading and playing rasters on top of vector data.  Here's an example where the health shaded raster is applied with a multiply effect which  gives much, usually much nicer rendering than default compositing modes.  For the text rendering we rely on the half bus library which has become the de facto  library for handling international text.  The image shows you basically the steps happening for an Arabic example.  So the first line is the set of characters coming in one by one and inversing them for  right to left parts of the Arabic text.  And then the actual shaping which as you see drastically transforms what the text should  look like compared to the individual glyphs that are used inside of it.  Also have the ability to specify finally which fonts you want to be using for each languages.  There's still no real fonts out there covering all the languages of the world, so allowing  you to mix those.  That came with also quite a nice performance improvement.  So it's the time taken by the label cache to do decluttering of labels for a given map.  So the new speeds, notice the log scales, so where the new version is at one second, where  all the one was a thousand seconds.  You shouldn't be using that many labels on your map, but it's nice to have anyway.  So this is an example of another complex script for the Tibetan.  Now features coming for the upcoming 7.2 release, we don't have an ETA yet.  First one is choosing better positions for labels on, I don't know how you see it on  the screen here.  The left one is the previous version, so you see if you place the labels on sharp road  corners you end up with overlapping characters and or labels that wouldn't be rendered because  they have too much overlap on them.  7.2 version, we're trying to detect where the sharp, those sharp angles are and trying  to offset the labels so those places fall on character breaks in the text for nice outputs.  7.2 also supports layer filters, basically blurring in shadows.  So here you see there's an inner glow inside the rivers with a blurring effect on them  and shadows you see also around the buildings with basically taking the original shape blurring  it, applying some opacity to it, supplying a translation to it.  It could also be used to other things to apply color adjustments on the fly to a given layer  to do a black and white output for raster layer for example, stuff like that.  We're still exploring the possibilities of what additional filters could be added, but  that's those that are available for the time being.  We also want to support vector tiles, we have an initial implementation that's not integrated  into the master branch yet, but more or less ready.  Not limited to XYZ addressing and MacaTOP projection, we're reusing the WFS interface  to access those tiles from Mapserver which allows you to do stuff like renaming attributes,  selecting which layers you want, whatever.  With this, we have a few open issues that are waiting for champions to either fund or  develop or take over.  So we have PHP Maps Script that's not supported with the new PHP 7 releases.  Vector tile driver needs a bit of love to become completely integrated with the sufficient  configuration options.  We'd like to have the JavaScript V8 stuff needs upgrading for the new releases of V8.  There's also been work happening on the documentation side.  So a few years ago, Tom Agatier switched the translation stuff over to TransFX for crowdsourced  translation of the Mapserver text, that's an ongoing task.  And in the cold sprint in Paris last winter, we had a team of Mapserver users who took  over the task of modernizing the Mapserver tutorial we were previously using.  We set up continuous integration of quality assessment, so each commit is tested with the  roughly 2,000 functional tests we have on Linux and on Windows.  And we had a big, closing big number of tickets thanks to Stefan also, this winter with 700  issues that were closed in just a few hours, very efficient.  We decided to close tickets that didn't have an inactivity for more than one year, over  the next year, so close bugs going back up to 2,000, I think, 2002 maybe.  And now I'll hand the microphone to Daniel who's taking the rest of the parts.  Thank you, Thomas.  Is my mic, yep, okay, good.  So I'm going to talk about two common questions that we've heard over the years from users  and that we're going to address here.  First one is the request for having a list of service providers and having a place where  service providers can actually list themselves.  So that's something that we've addressed this year.  There's a new service provider page that's been added to the website.  There's three categories of providers, core contributors, that's the people who are members  of the PSC or actually have commit rights, so those are the people who can actually integrate  your stuff into the software.  But then there's also contributors who are active people, many of you are in the room,  who are able to support other users in the use of Maps Elver, so you could be listed  there if you want.  And then there's another service provider section which is a place where companies could  list themselves if they provide a complementary product as long as it's open source and it's  related to Maps Elver.  So if you want to add yourself, we made it so that you have to prove that you are kind  of technical, so read RFC 116, the instructions are there.  If you cannot make sense of it, you may not fit in the provider's directory.  Another question that we hear often is, well, where's the GUI?  How do I edit those map files?  I'm tired of using a text editor for editing map files, so that's been a question that  came up over and over over the years.  And I mean, there's a GUI, it's called VI or Emacs or Sublim Text.  It's been around forever and everybody's got their own flavor of it and it's stable, it's  well tested, so what's the problem, right?  Well if you look at, it's actually a good thing that Maps Elver didn't come with the  GUI because there's actually, when I prepared this, there's about a dozen products, open  source products, and I'm not even talking about non-open source ones, that are built  on top of Maps Elver or built around Maps Elver and actually make your life easier in  using the software.  So Maps Elver remains the core engine that renders the map for those products, but then  they help you do your job.  So let's go over them relatively quickly because I think I have like five minutes left, less  than five, it's gonna be five.  So I'm not gonna stick strictly to map file editors, but I'm gonna also include in that  because there's a gray area between application frameworks and map file editors.  There's a gray zone in between, so I've included some of them that are not strictly map file  editors in the list.  And since it's a list, any list is likely to miss some important players or important  items, so don't blame me, don't blame me if I missed your favorite product, just go to  the wiki, and this is intentionally small and long so that you don't read it now, go  to the wiki, you can list yourself if you have an open source product that's not listed  already.  So the first one, and they're listed by the way in Alphabet Scala Order, and I started  with the ones that are officially OS Geo Project.  So Geo Moose is built on top of Maps Elver.  It's a framework for building applications.  It's an HTML, JavaScript on the client side and PHP using PHP Maps Script on the server  side.  So that's the first one.  It's really a framework for building applications, and it's built on top of Maps Elver.  The Zoo Project is not necessarily about editing map files, but it actually provides a web  processing service on top of Maps Elver, so it implements the web processing service  spec.  It provides services, APIs, a bunch of operators, so if you need the web processing service,  that's a good one to look at.  Chrome app probably wins my personal prize for simplicity.  It's a bit of HTML and JavaScript that you just download.  You do file open in your web browser, and you're going, nothing to install.  Open your map files, and it gives you a hierarchical view of the objects in your map, and then  you click on them, and it gives you a dialog to set the parameters, so it's as simple as  it gets.  EOX server, this one is a bit like Zoo, which implements a web processing service.  EOX implements the Earth observation standards for WCS and WMS on top of Maps Elver, so if  you need inspire and that kind of stuff, Stefan would be one person to talk about that.  Magna Cartel implements the Cartel CSS standard, and it's a converter to turn the Cartel CSS  into Maps Elver map files and map nick configurations.  It does not come with a GUI, an editor, so the way Oliver calls it, he calls it a BYOE,  so it's bring your own editor, but it does provide a viewer.  I saw Oliver's presentation, it's actually quite interesting, the Cartel CSS, it's a  good mechanism for styling.  There's another one called Map File Generator, I don't know too much about it, it was listed  by its developer on the website.  It's listed as still being under development, but it's also providing mechanisms for reading  and editing map files.  Map Manager is a desktop application that runs on Windows that allows you to, it provides  you a WYSIWYG environment for editing your maps and previewing your changes.  Map Mint is a cloud-based service initially which has been released open source recently,  so it provides a bunch of, it's more than just a map file editor, it's actually a complete  application development framework.  I believe it's built on top of the Zoo project as well.  So you could have a look if you want a complete application development environment, including  building maps.  Scribe UI is another option for editing map files, it's really, it's got the map view  on one side and your, the map editor on one side and a map view on the other side.  Similar to Magna Cartel which has the Cartel CSS method for styling, Scribe has another  syntax which is called a Scribe syntax.  As of you have seen Cartel CSS, Scribe is kind of the same mechanisms and same concepts,  variables, and automated scale management but in a more map-saver-like syntax.  It supports both the Scribe syntax and the map-saver-map file syntax.  Then there's two export plugins, one in GVSig.  So a plugin, if you're using, if you're a user of GVSig, there's an export plugin you  can use to publish your project in maps.ver and same with QGIS.  It's called the RT maps.ver exporter, look for it in the list of plugins.  I was told that it requires mapscript for installing so it's not necessarily easy to  install but once you've installed it, it's going to work well to take your QGIS projects  and publish them with maps.ver.  So that list, we've gone over 11 products that can help you in your work with maps.ver  so there are some GUIs.  So that's it for my quick walkthrough of those products so we wanted to keep some time to  have interaction.  We have several of the developers of those products that I just mentioned in the room  because I suspected that some of you may have questions like does this product really do  that?  It's time to ask it.  If you want to ask questions, tell us about the developments.  It's time for that too or bring up concerns, ideas.  Quick question regarding the vector tile support you shortly mentioned.  Are you adhering to any standards regarding vector tile?  So the mapbox standard or what kind of standard are you using for that?  Yeah, it's the mapbox, it's the mapbox type specification except that it's more than  just a web mac at all projection.  And you also provide the styling based on the styling you have configured with the map  server or how do you do that?  There's no styling in the vector tiles.  So the styling is pushed over and then it's up to your client to do the styling.  Okay, thanks.  How's the window support in the map server at the moment?  I believe the MS4W package has been upgraded recently because it was lagging a little bit.  So I'm not the, you know, Jeff McKenna is the guy who's maintaining MS4W so I'm not  the right person to answer about it.  You might know more about it.  Do you use it?  It's active releases that are going on right now so yeah, it's very active.  And there is also, Jürgen, do you still do builds in the...  There was TAM.  No, but there's TAM has builds but there were some as part of OSDU.  TAM also did the OSDU for W builds.  Okay, because there's the OSDU for W builds but I'm not sure how accurate those ones are.  And Mike is providing some dockers for those who are on Linux and using dockers.  Are they listed on the downloads page, the dockers?  I don't know.  They should, yeah.  We could ask you for making sure they are listed.  Thanks Mike.  Thank you.  And TAMS.  TAMS provides also automated builds either for the releases or I think as a daily build  chain, building daily releases of MAP server and Google and maybe others, I don't know.  Time for one more quick question.  No, okay.  Thanks very much.  Oh, pick up on.  Thank you.  Any plans on supporting the WFST transactional?  With tiny AWS, do we not do transactional?  So tiny AWS does the transactional WFST but it's...  Some people complain that it's not exactly like the full, it doesn't support everything  that a MAP file supports but our answer to the WFST question has been to integrate with  tiny AWS a few years ago because that would require too much changes in the core.  The core of MAP server is really optimized for rendering and WFST is going both ways  and it's not necessarily...  It would be technically possible but that's not the ideal thing to do.  Do you have something to add on there?  No.  Okay.  Thank you very much guys.  Thank you.  Thank you.
foss4g-2016-1295-mapserver_status_report-hd_0_215.png foss4g-2016-1295-mapserver_status_report-hd_216_28019.png foss4g-2016-1295-mapserver_status_report-hd_28020_28763.png foss4g-2016-1295-mapserver_status_report-hd_28764_32759.png foss4g-2016-1295-mapserver_status_report-hd_32760_33131.png foss4g-2016-1295-mapserver_status_report-hd_33132_33371.png foss4g-2016-1295-mapserver_status_report-hd_33372_33455.png foss4g-2016-1295-mapserver_status_report-hd_33456_33539.png foss4g-2016-1295-mapserver_status_report-hd_33540_33599.png foss4g-2016-1295-mapserver_status_report-hd_33600_33803.png foss4g-2016-1295-mapserver_status_report-hd_33804_34247.png foss4g-2016-1295-mapserver_status_report-hd_34248_34295.png foss4g-2016-1295-mapserver_status_report-hd_34296_34343.png foss4g-2016-1295-mapserver_status_report-hd_34344_34391.png foss4g-2016-1295-mapserver_status_report-hd_34392_34439.png foss4g-2016-1295-mapserver_status_report-hd_34440_34487.png foss4g-2016-1295-mapserver_status_report-hd_34488_34559.png foss4g-2016-1295-mapserver_status_report-hd_34560_34607.png foss4g-2016-1295-mapserver_status_report-hd_34608_34655.png foss4g-2016-1295-mapserver_status_report-hd_34656_34751.png foss4g-2016-1295-mapserver_status_report-hd_34752_34931.png foss4g-2016-1295-mapserver_status_report-hd_34932_34979.png foss4g-2016-1295-mapserver_status_report-hd_34980_35051.png foss4g-2016-1295-mapserver_status_report-hd_35052_35351.png foss4g-2016-1295-mapserver_status_report-hd_35352_35399.png foss4g-2016-1295-mapserver_status_report-hd_35400_35519.png foss4g-2016-1295-mapserver_status_report-hd_35520_35567.png foss4g-2016-1295-mapserver_status_report-hd_35568_35639.png foss4g-2016-1295-mapserver_status_report-hd_35640_35711.png foss4g-2016-1295-mapserver_status_report-hd_35712_35783.png foss4g-2016-1295-mapserver_status_report-hd_35784_36047.png foss4g-2016-1295-mapserver_status_report-hd_36048_36107.png foss4g-2016-1295-mapserver_status_report-hd_36108_37487.png foss4g-2016-1295-mapserver_status_report-hd_37488_37547.png foss4g-2016-1295-mapserver_status_report-hd_37548_37703.png