[Geomoose-users] RFC #5

[Dan Little]

I should update this thread as well as blowing up people's individual
inboxes!

1. There is now caching support for the new service.php / RFC#5
functionality. It uses JSON instead of SQLite.

2. I've settled on a (for now) grid rendering solution: dojo's DataGrid.
Mostly because that's the best option for our current version of dojo (1.6).

3. There's additional support for a GeoJSON layer type in GeoMOOSE that
allows for doing some interesting dynamic (but simple) vector work.
Specifically, we are using it as a replacement for the old highlight layer.
More to come!

On Wed, Dec 2, 2015 at 7:30 PM, Eli Adam <eadam at co.lincoln.or.us> wrote:

> Hi Dan,
>
> On Mon, Oct 19, 2015 at 9:49 AM, Dan Little <theduckylittle at gmail.com>
> wrote:
> > For those feeling TL;DR or "Too much developer chatter":
> >
> > We are folding all of the various geomoose query services
> > (specifically, select, identify and query) into a single service that
> > is based around a single "Service" class from which all new services
> > can inherit.  Also, after that transition is complete, we will be
> > adding additional support for a table and vector results view of the
> > data.  The latter of which has been available only in customized
> > versions of GeoMOOSE to this point.
> >
> > For reference:
> > - http://www.geomoose.org/rfc/rfc-5.html
> >
> > This has been a long time coming and has made some substantial
> > progress in the last couple of weeks.  For those that are interested
> > in the nitty-gritty of the implementation you can see the progress
> > here:
> >
> > - https://github.com/geomoose/geomoose-services/tree/rfc5
>
> Nice to see all the progress here!  It has been very informative to
> read up on some of the commits.
>
> Thanks, Eli
>
> >
> > The documentation for the initial code pushes are being placed here:
> >
> > - https://github.com/geomoose/geomoose/issues/60
> >
> > My hope is to put more of this into separate tickets.  I did want to
> > get all of the old tests passing before I started moving to expanding
> > functionality.  There is also some notable missing bits:
> > 1. Custom header/footer template support is not there. Query.php
> > didn't support that functionality but select did.  I will be adding
> > that.
> > 2. "saving results" ala select.php is not supported yet. Results
> > return and a highlight layer functions but it will be constantly
> > requerying the data.  Caching data in the SQLite database allowed for
> > less overhead on servers.  Is this still a thing we need? Or can we
> > assume modern servers can handle a parcel query fast enough to just
> > requery the data when redrawing the map?
> > 3. Table rendering still doesn't have a UI component solution.
> > Neither does a Table/Map relational model (IE, highlight something on
> > the map and get something on the table to show up).  This isn't rocket
> > science to figure out but the application as of now is missing all of
> > those interactions.
> >
> > Thanks everyone!
> > _______________________________________________
> > Geomoose-users mailing list
> > Geomoose-users at lists.osgeo.org
> > http://lists.osgeo.org/mailman/listinfo/geomoose-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/geomoose-users/attachments/20151202/fc2c9dd1/attachment.html>