[postgis-users] Request for ideas to enhance the geometry viewer - GSoC

Martin Davis mtnclimb at gmail.com
Tue Jan 29 18:24:35 PST 2019

Oh, i wasn't suggesting render-in-the-DB.  Just throwing out an idea about
how styling metadata could be supplied to pgAdmin.

I guess I wasn't totally clear. The suggestion is to supply dynamic queries
with styling metadata on-the-fly within pgAdmin.  The metadata would *not*
be persisted in the DB (well, it could be, but up to the user).  Putting
the metadata right in SQL allows using all those SQL/Postgres functions we
all know and love.already.

As for Paolo's objection, I can see his point.  But two rebuttles:
- Since it's free, why not put useful functionality everywhere?  :)
- actually it's not free - the cost occurs in having to learn an entirely
new tool.  So if some useful extra functionality pops up in your tool of
choice, that's a win

On Tue, Jan 29, 2019 at 6:11 PM Paul Ramsey <pramsey at cleverelephant.ca>

> Yeah, every time I’ve thought about renderer-in-the-db I’ve come back to
> this. There’s nothing especially privileged about the db that makes a lot
> of sense for bringing rendering in-process. And boy it’s a rat hole… once
> you go down, you’re never coming back out.
> P
> On Jan 29, 2019, at 5:36 PM, Paolo Cavallini <cavallini at faunalia.it>
> wrote:
> Are you sure you want to reimplement what a GIS does already? Doing
> proper, powerful styling it's a really big task.
> Sorry to jump in like this, I'm a strong advocate of open source tools
> also because you can reuse what is available, avoiding duplication of
> efforts.
> Cheers.
> Il 30 gennaio 2019 02:13:50 CET, Martin Davis <mtnclimb at gmail.com> ha
> scritto:
>> Here's an idea which might be a bit out there...
>> Allow styling/labelling to be driven by columns in the displayed query.
>> The styling columns would have well-known names which are unlikely to
>> conflict with data columns.  A nice pattern to follow is the SVG style
>> names.  So e.g. styleStroke = line color, styleFill - fill color,
>> styleStrokeWidth = line width, etc etc etc.  styleLabel would be the string
>> to label with.
>> This allows styling to be data-driven and easily captured and shared.
>> On Mon, Jan 28, 2019 at 8:16 PM Victoria Rautenbach <
>> victoria.rautenbach at gmail.com> wrote:
>>> Dear PostGIS devs and users
>>> Firstly, we (Frikan, Xuri and I) would like to thank the PostGIS
>>> community again for the support you provided us in 2018 during Google
>>> Summer of Code (GSoC). We truly appreciate your time and effort.
>>> The call for OSGeo GSoC ideas is now out [1]. Frikan and I would like
>>> to suggest a project to address some of the issues left in the
>>> geometry viewer (available in pgAdmin4), but also include some new
>>> functionality.
>>> Are there any ideas or suggestions from you, the PostGIS community,
>>> for extra functionalities that would improve the usefulness of the
>>> geometry viewer?
>>> Thank you in advance.
>>> Regards
>>> Victoria
>>> [1] https://lists.osgeo.org/pipermail/soc/2019-January/004200.html
>>> _______________________________________________
>>> postgis-users mailing list
>>> postgis-users at lists.osgeo.org
>>> https://lists.osgeo.org/mailman/listinfo/postgis-users
> --
> Sorry for being short_______________________________________________
> postgis-users mailing list
> postgis-users at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/postgis-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20190129/f7b54465/attachment.html>

More information about the postgis-users mailing list