[Geoprisma-dev] Tutorial - How to create a GeoPrisma project

[Yves Moisan]

Le lundi 30 novembre 2009 à 21:44 -0600, Bob Basques a écrit :
> Hmmm, 
> 
> All,
> 
> New comer to the list.  This backend stuff is of interest though.  
> Doing essentially the same thing right now with RUBY/Rails and POSTGIS, 
> one thing on the editing, depending on how far you want to take the authenticating.  
> We decided early on (time will tell if we bit off too much here . . ) to use metadata
>  to describe the attribute columns as well as some of the (global) spatial columns.  
> This allows for automated attribute form generation alongside of a text based form for
>  updating the Spatial elements, which may or may not be of interest here.  The key 
> point I'm making though, is that by using a (somewhat) standard (FGDC) metadata scheme,
>  it allowed for quite a bit of automation, including pick lists and the like.

One issue that's been bugging me recently is to have some sort of
central "styles registry" that we could define and reuse in GeoPrisma
widgetry.  "Pick list" registry through a FGDC metadata document sounds
interesting ...

> 
> I think there is possible application with the same sort of approach to styling of maps.  

Right !

> We're building Mapfiles and the forms on the fly right now, nothing static, all DB sourced.  

Any performance penalty doing that ?  I'm asking because most of our
Mapfiles use PostGIS and we found we'll have to run MapServer in
FastCGI, so I was wondering if building the MapFile on the fly from data
stored in the DB caused some performance issues.

>  
> Related to this we also went a bit off the deep end with regard to using SLDs, which are also
>  stored in the database as default views.  Why go to all this trouble, well, we now have a mechanism
>  for storing any sld that's applied to the service as well as possible building out of a user chooser
>  system that is all sourced from the database.
> 
> Just some food for thought as you move forward.

Thank you for telling us about your experience.  That's really
appreciated.

> 
> P.S.  I'm a few steps behind Stephen in looking at GeoPrisma and experimenting with it.

Please, tell us what you think as you go along exploring.  We'll try to
integrate new ideas as we go along and projects allow.

Yves

> 
> bobb
> 
> 
> >>> Stephen Woodbridge <woodbri at swoodbridge.com> 11/30/09 7:49 PM >>>
> Yves,
> 
> Regarding your ideas for easing the creation of maps, I would be 
> interested in hearing about your thoughts on that. I'm assuming that you 
> have had some off list discussions with the dev team. Where does 
> GeoPrisma hang out on IRC?
> 
> I'm making pretty good progress with the perl script to generate 
> config.xml by reading the table/column structure from postgis.
> 
> o datastores are all being generated
> o resources without widgets is being generated
> o should be able to have the editfeature_* widgets for each layer 
> generating shortly
> o featurepanel_form looks straight forward to generate for each layer
> o mapfishlayertree looks straight forward
> 
> I think the big problem will be generating the stylemaps for all the 
> layers and the classes within the layers. I might try reading the 
> mapfile and see if I can generate simple stylemaps for the layers from that.
> 
> But basically I'm taking a fixed layout and widget set and only 
> automating the datastore integration with that. This also implies the 
> dynamic creation of editfeature widgets for all the layers.
> 
> -Steve
> 
> 
> Yves Moisan wrote:
> > Stephen,
> > 
> > Please forgive a quick top-post, but I wanted to thank you for hanging
> > on there as a dedicated docs/code commenter and also to let you know
> > we're still brewing some ideas to ease the creation of maps by an order
> > of magnitude or so we hope!  However, expect another change in the docs,
> > for the better (and hopefully I'll then do my share of docs; me ducks).
> > 
> > Yves
> > 
> >> Yves Moisan wrote:
> >>> L
> >>>> Given enough time and money, then sure, we should add a set of more 
> >>>> hands-on exercise to complement this more abstract tutorial. The 
> >>>> MapServer tutorial is a good example of what we could aim for: 
> >>>> http://biometry.gis.umn.edu/tutorial/sections.html
> >>>>
> >>>> However, until the resources are available to produce this level of docs 
> >>>>   I consider that what you've got is a great start.
> >>>>
> >>>> Thanks for you work on this Alexandre.
> >>> Agreed !  Thanx for doing that work.
> >> Since I raised the question, I would like to give my thanks to Alexandre 
> >> also. The Tutorial has improved significantly since I first looked at it.
> >>
> >> Since I'm new to GeoPrisma and this is my first time through the 
> >> tutorial and the fact that I know a lot about the related technologies, 
> >> I thought it might prove useful with regards to ways to improve the 
> >> "newbie" experience with GeoPrisma. I'll continue to report issues and 
> >> successes with the hope that they might prove useful to the team and/or 
> >> users in the future that might be searching the archives.
> >>
> >> So, Alexandre, in case it was not obvious in my flood of issues to the 
> >> list, you are doing a great job and I appreciate the tutorial and your 
> >> support on and off the list.
> >>
> >> -Steve W
> > 
> 
> _______________________________________________
> Geoprisma-dev mailing list
> Geoprisma-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geoprisma-dev
>