<div dir="ltr"><div><br></div><div>Thank you for your suggestions.</div><div><br></div><div>I have added the functionality to show the whole result as well as feature's properties in a new version and will send the patch soon. Here are the new screenshots: <a href="https://photos.app.goo.gl/HwKHMHfzuRMhGC5C6">https://photos.app.goo.gl/HwKHMHfzuRMhGC5C6</a></div><div><br></div><div>As for the OSM tile layer, currently it would be added to the map only if the geometry's SRID is 4326. There would be no tile layer for geometries with other SRIDs because the viewer can't do coordinate transformations. I think it' a good idea to disable the tile layer by default and add more tile layer options for users :). Since this is the last week for GSOC, I will submit the current version(with map view) and update the tile layer after GSOC.</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">Regina Obe <<a href="mailto:lr@pcorp.us">lr@pcorp.us</a>> 于2018年7月31日周二 上午2:17写道：<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Would be nicer if it were a configurable setting or maybe it is already so as part of the setting panel you can specify the tile url.<br>
For example I'd rather use my own tiles than any of these since I have custom stuff showing on mine.<br>
<br>
Might even be better for the default to be no tile at all. When I look at my data, especially data that is not earthly bound, I don't want it overlaid against anything.<br>
<br>
robe waiting for strk to scream at pramsey's blasphemy :)<br>
<br>
<br>
> -----Original Message-----<br>
> From: postgis-devel [mailto:<a href="mailto:postgis-devel-bounces@lists.osgeo.org" target="_blank">postgis-devel-bounces@lists.osgeo.org</a>] On<br>
> Behalf Of Paul Ramsey<br>
> Sent: Monday, July 30, 2018 2:09 PM<br>
> To: PostGIS Development Discussion <<a href="mailto:postgis-devel@lists.osgeo.org" target="_blank">postgis-devel@lists.osgeo.org</a>><br>
> Subject: Re: [postgis-devel] [SoC]Week 10 Report - Implement Geospatial<br>
> Data Viewer in pgAdmin4 for PostGIS<br>
> <br>
> Also, do you find the OSM tileserver slow? I find it's incredibly slow. Maybe<br>
> using bing or some other public-but-available tile set would be good?<br>
> P<br>
> <br>
> On Mon, Jul 30, 2018 at 11:01 AM, Paul Ramsey<br>
> <<a href="mailto:pramsey@cleverelephant.ca" target="_blank">pramsey@cleverelephant.ca</a>> wrote:<br>
> > OK, that branch builds... there's just functionality for looking at<br>
> > geometries one-at-a-time, is there a plan for a map view that shows<br>
> > the whole result set?<br>
> ><br>
> > P.<br>
> ><br>
> > On Fri, Jul 27, 2018 at 6:23 PM, Xuri Gong <<a href="mailto:xurigoong@gmail.com" target="_blank">xurigoong@gmail.com</a>> wrote:<br>
> >> Hi Paul,<br>
> >><br>
> >> Since there are some bugs using openlayers in pgadmin4, I have<br>
> >> replaced it with leafletjs in 'geometry_visualiser' branch. Please<br>
> >> use 'geometry_visualiser' branch to build:<br>
> >> <a href="https://github.com/Gooong/pgadmin4/tree/geometry_visualiser" rel="noreferrer" target="_blank">https://github.com/Gooong/pgadmin4/tree/geometry_visualiser</a><br>
> >><br>
> >> Thank you:)<br>
> >><br>
> >> Paul Ramsey <<a href="mailto:pramsey@cleverelephant.ca" target="_blank">pramsey@cleverelephant.ca</a>> ?2018?7?28??? ??5:26??:<br>
> >>><br>
> >>> Trying out the geoviewer branch,<br>
> >>><br>
> >>> I can run 'make bundle' fine in the master branch. In your branch it<br>
> >>> errors out like this:<br>
> >>><br>
> >>> ERROR in ./pgadmin/static/jsx/map_view/map_view.jsx<br>
> >>> Module not found: Error: Can't resolve 'ol/dist/ol.js' in<br>
> >>> '/Users/pramsey/Code/pgadmin4/web/pgadmin/static/jsx/map_view'<br>
> >>> @ ./pgadmin/static/jsx/map_view/map_view.jsx 60:9-33 @<br>
> >>> ./pgadmin/tools/sqleditor/static/js/sqleditor.js<br>
> >>><br>
> >>> ERROR in ./pgadmin/static/jsx/map_view/map_view_map.jsx<br>
> >>> Module not found: Error: Can't resolve 'ol/dist/ol.js' in<br>
> >>> '/Users/pramsey/Code/pgadmin4/web/pgadmin/static/jsx/map_view'<br>
> >>> @ ./pgadmin/static/jsx/map_view/map_view_map.jsx 37:9-33 @<br>
> >>> ./pgadmin/static/jsx/map_view/map_view.jsx<br>
> >>> @ ./pgadmin/tools/sqleditor/static/js/sqleditor.js<br>
> >>> error Command failed with exit code 2.<br>
> >>> info Visit <a href="https://yarnpkg.com/en/docs/cli/run" rel="noreferrer" target="_blank">https://yarnpkg.com/en/docs/cli/run</a> for documentation<br>
> >>> about this command.<br>
> >>><br>
> >>> I assume there's a small piece of configuration not checked in<br>
> somewhere?<br>
> >>><br>
> >>> On Sun, Jul 22, 2018 at 7:00 PM, Xuri Gong <<a href="mailto:xurigoong@gmail.com" target="_blank">xurigoong@gmail.com</a>><br>
> wrote:<br>
> >>> > Hi,<br>
> >>> > I am Xuri Gong. This is my report for week 10(July 16 - 22).<br>
> >>> ><br>
> >>> > What did you get done this period?<br>
> >>> ><br>
> >>> > Create visualiser for individual geometry in datagrid. [1] Fix<br>
> >>> > image url errors in leaflet. [2]<br>
> >>> ><br>
> >>> > This visualiser is independent from the geoviewer and is in the<br>
> >>> > geometry_visualiser branch[3]. Here is the screen shot:<br>
> >>> ><br>
> >>> > Screenshot 1 [4]<br>
> >>> > Screenshot 2 [5]<br>
> >>> ><br>
> >>> > What do you plan on doing next week?<br>
> >>> ><br>
> >>> > Create test for both geometry_visualiser and geoviewer.<br>
> >>> > Check the code style to meet the pgAdmin coding standards[6].<br>
> >>> ><br>
> >>> > Are you blocked on anything?<br>
> >>> > No, I am not blocked.<br>
> >>> ><br>
> >>> > Wiki page: [7]<br>
> >>> > Public repository: [8]<br>
> >>> ><br>
> >>> > [1]<br>
> >>> ><br>
> >>> ><br>
> <a href="https://github.com/Gooong/pgadmin4/commit/d6407baa3a0a96adac169d18" rel="noreferrer" target="_blank">https://github.com/Gooong/pgadmin4/commit/d6407baa3a0a96adac169d18</a><br>
> >>> > 3bed8bc044dbb8f5<br>
> >>> > [2]<br>
> >>> ><br>
> >>> ><br>
> <a href="https://github.com/Gooong/pgadmin4/commit/3b160b668c4f9b5867b4b218" rel="noreferrer" target="_blank">https://github.com/Gooong/pgadmin4/commit/3b160b668c4f9b5867b4b218</a><br>
> >>> > 9714c934a5de85c6 [3]<br>
> >>> > <a href="https://github.com/Gooong/pgadmin4/tree/geometry_visualiser" rel="noreferrer" target="_blank">https://github.com/Gooong/pgadmin4/tree/geometry_visualiser</a><br>
> >>> > [4] <a href="https://photos.app.goo.gl/kH58WDbZeKAtRvNi8" rel="noreferrer" target="_blank">https://photos.app.goo.gl/kH58WDbZeKAtRvNi8</a><br>
> >>> > [5] <a href="https://photos.app.goo.gl/AnQMZndMQ62HGLmbA" rel="noreferrer" target="_blank">https://photos.app.goo.gl/AnQMZndMQ62HGLmbA</a><br>
> >>> > [6] <a href="https://pgadmin.org/docs/pgadmin4/dev/coding_standards.html" rel="noreferrer" target="_blank">https://pgadmin.org/docs/pgadmin4/dev/coding_standards.html</a><br>
> >>> > [7]<br>
> >>> ><br>
> >>> > <a href="https://trac.osgeo.org/postgis/wiki/GeospatialDataViewerInPgAdmin4" rel="noreferrer" target="_blank">https://trac.osgeo.org/postgis/wiki/GeospatialDataViewerInPgAdmin4</a><br>
> >>> > ForPostGIS [8] <a href="https://github.com/Gooong/pgadmin4/tree/geoviewer" rel="noreferrer" target="_blank">https://github.com/Gooong/pgadmin4/tree/geoviewer</a><br>
> >>> ><br>
> >>> > _______________________________________________<br>
> >>> > postgis-devel mailing list<br>
> >>> > <a href="mailto:postgis-devel@lists.osgeo.org" target="_blank">postgis-devel@lists.osgeo.org</a><br>
> >>> > <a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a><br>
> >>> _______________________________________________<br>
> >>> postgis-devel mailing list<br>
> >>> <a href="mailto:postgis-devel@lists.osgeo.org" target="_blank">postgis-devel@lists.osgeo.org</a><br>
> >>> <a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a><br>
> >><br>
> >><br>
> >> _______________________________________________<br>
> >> postgis-devel mailing list<br>
> >> <a href="mailto:postgis-devel@lists.osgeo.org" target="_blank">postgis-devel@lists.osgeo.org</a><br>
> >> <a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a><br>
> _______________________________________________<br>
> postgis-devel mailing list<br>
> <a href="mailto:postgis-devel@lists.osgeo.org" target="_blank">postgis-devel@lists.osgeo.org</a><br>
> <a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a><br>
<br>
_______________________________________________<br>
postgis-devel mailing list<br>
<a href="mailto:postgis-devel@lists.osgeo.org" target="_blank">postgis-devel@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/postgis-devel" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/postgis-devel</a></blockquote></div>