Do you want to create your own web mapping application ? Do you want to share your geospatial data with others ? Do you want to define your own symbology ? If the answer is yes, then you are probably interested in the administration suite that we are currently developing.
This administration suite is a web 2.0 application and has 3 main goals:
- Allow the administration of data sources like WFS, WMS, GIS database or files, with function like "upload shapefile"
- Allow the definition of symbology for your data with an online MapFile editor.
- Allow the creation of MapFish applications. With this part, it will be possible to configure widgets (map panel, layer tree panel, overview panel for example) inside a web page.
Some of these developments will be part of GeoExt and we will also use nice GeoExt widgets like the styler proposed by OpenGeo.
So if you are interested in the source code, you can have a look here and you are welcome to contribute ;-)
I will post soon more information !
4 comments:
Sounds interesting!
What I'd like to see (and have yet to find one) is the ability for a user to create new layers (WFS / PostGIS) from scratch.
Any relation between that project and GeoAdminSuite ?
Here some answers:
- WMS / WFS service are planned. These can be configured in the MapFile.
- For creation of POSTGIS layer, our target is not to create a pgAdmin. The datastore part will be able to use new tables, but not to create new tables (at least on short term)
- GeoAdminSuite is a java application and we want to offer functionality with python / mapscript / ExtJS / OpenLayers technologies (which is more aligned with MapFish and GeoExt). That is why we decided to create this new application.
... we want to offer functionality with python / mapscript / ExtJS / OpenLayers technologies ... That is why we decided to create this new application.
Good. At one point I saw on the MapFish user list that auth/auth was (going to be ?) handled by AuthKit. Now I see in setup.py that you guys are using repoze.what. Interesting.
We are currently putting together a PHP proxy application the roles of which will be 1) to act as a front-end to a bunch of "backend" servers (MapServer, FeatureServer, GeoServer, MapFish Server, etc) and 2) to get an ACL from some auth system before it goes and fetches the data. We need to talk about this offline ;-)
Post a Comment