<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.gmail-m1794381918267705954apple-converted-space
{mso-style-name:gmail-m_1794381918267705954apple-converted-space;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>It's a touchy area the DB tool should have strong DB and light on visualization – so Db work is always front and center and GIS to the side. The GIS should be lighter on DB and stronger on visualization (or at least have visualization up front).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>What is light but not too light is a big fuzzy area. So I think of it in terms of 3 users.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Leo – He likes OpenJump, cause all he wants to do is write SQL statements – hates QGIS. Why he hates QGIS? – the only thing he wants is to be able to write a query and see it and layer queries. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Maybe some styling to distinguish his queries when he overlays. Downside of OpenJump is inability to browse his tables and make structural changes.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>QGIS forces him to open this huge <b>GIS System</b> -> go to DbManager. He finds it cluttered. He is NOT a GIS person so all those goodies are lost on him. He finds them to be an eyesore and weighing him down from his primary objective.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>GIS person or general user – I give them QGIS they love it – they are immersed in the whole visualization thing and just want to filter their data, they go hog wild installing plugins. I try to show them the DbManager piece (the colorcoding of queries, the light intellisense, the ability to browse tables etc) (the feature I like most about QGIS), and they yawn and are totally not interested.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'>Me – I don't often care to visualize anything aside form spot checking my concave hull or convex hull or Geo Median is right, but it's hard to tell if I can't overlay on the original query without the calcs. So that's the only thing I really yearn for overlay and very minimalist styling. So I end up jumping to whatever is closest QGIS or OpenJump. These days I often jump to QGIS cause I have users that feel "SAFE" (by SAFE I mean they are not lost in – what should I type) in it so I have to have a clue how to show them how to do things in it, but otherwise I'm probably more of an OpenJump / pgAdmin user.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri",sans-serif'> postgis-users [mailto:postgis-users-bounces@lists.osgeo.org] <b>On Behalf Of </b>Martin Davis<br><b>Sent:</b> Tuesday, January 29, 2019 9:25 PM<br><b>To:</b> Paul Ramsey <pramsey@cleverelephant.ca><br><b>Cc:</b> PostGIS Users Discussion <postgis-users@lists.osgeo.org><br><b>Subject:</b> Re: [postgis-users] Request for ideas to enhance the geometry viewer - GSoC<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Oh, i wasn't suggesting render-in-the-DB. Just throwing out an idea about how styling metadata could be supplied to pgAdmin. <o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>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.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>As for Paolo's objection, I can see his point. But two rebuttles:<o:p></o:p></p></div><div><p class=MsoNormal>- Since it's free, why not put useful functionality everywhere? :)<o:p></o:p></p></div><div><p class=MsoNormal>- 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<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>On Tue, Jan 29, 2019 at 6:11 PM Paul Ramsey <<a href="mailto:pramsey@cleverelephant.ca">pramsey@cleverelephant.ca</a>> wrote:<o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal>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.<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>P<o:p></o:p></p><div><div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On Jan 29, 2019, at 5:36 PM, Paolo Cavallini <<a href="mailto:cavallini@faunalia.it" target="_blank">cavallini@faunalia.it</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>Are you sure you want to reimplement what a GIS does already? Doing proper, powerful styling it's a really big task.<br>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.<br>Cheers.<br style='font-variant-caps:normal;text-align:start;word-spacing:0px'><br></span><o:p></o:p></p><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>Il 30 gennaio 2019 02:13:50 CET, Martin Davis <</span><a href="mailto:mtnclimb@gmail.com" target="_blank"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>mtnclimb@gmail.com</span></a><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>> ha scritto:<o:p></o:p></span></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>Here's an idea which might be a bit out there... <o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>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.<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>This allows styling to be data-driven and easily captured and shared. <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><o:p> </o:p></span></p></div></div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><o:p> </o:p></span></p><div><div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>On Mon, Jan 28, 2019 at 8:16 PM Victoria Rautenbach <</span><a href="mailto:victoria.rautenbach@gmail.com" target="_blank"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>victoria.rautenbach@gmail.com</span></a><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>> wrote:<o:p></o:p></span></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>Dear PostGIS devs and users<br><br>Firstly, we (Frikan, Xuri and I) would like to thank the PostGIS<br>community again for the support you provided us in 2018 during Google<br>Summer of Code (GSoC). We truly appreciate your time and effort.<br><br>The call for OSGeo GSoC ideas is now out [1]. Frikan and I would like<br>to suggest a project to address some of the issues left in the<br>geometry viewer (available in pgAdmin4), but also include some new<br>functionality.<br><br>Are there any ideas or suggestions from you, the PostGIS community,<br>for extra functionalities that would improve the usefulness of the<br>geometry viewer?<br><br>Thank you in advance.<br><br>Regards<br>Victoria<br><br><br>[1]<span class=gmail-m1794381918267705954apple-converted-space> </span></span><a href="https://lists.osgeo.org/pipermail/soc/2019-January/004200.html" target="_blank"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>https://lists.osgeo.org/pipermail/soc/2019-January/004200.html</span></a><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><br>_______________________________________________<br>postgis-users mailing list<br></span><a href="mailto:postgis-users@lists.osgeo.org" target="_blank"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>postgis-users@lists.osgeo.org</span></a><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><br></span><a href="https://lists.osgeo.org/mailman/listinfo/postgis-users" target="_blank"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>https://lists.osgeo.org/mailman/listinfo/postgis-users</span></a><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><o:p></o:p></span></p></blockquote></div></blockquote></div><p class=MsoNormal><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><br>--<span class=gmail-m1794381918267705954apple-converted-space> </span><br>Sorry for being short_______________________________________________<br>postgis-users mailing list<br></span><a href="mailto:postgis-users@lists.osgeo.org" target="_blank"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>postgis-users@lists.osgeo.org</span></a><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'><br></span><a href="https://lists.osgeo.org/mailman/listinfo/postgis-users" target="_blank"><span style='font-size:9.0pt;font-family:"Helvetica",sans-serif'>https://lists.osgeo.org/mailman/listinfo/postgis-users</span></a><o:p></o:p></p></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></div></blockquote></div></div></div></body></html>