PostGIS Mapviewer - Ability to add custom layers (RM #3646)

[dpage]

Issue migrated from Redmine: https://redmine.postgresql.org/issues/3646
Originally created by Atle Frenvik Sveen at 2018-09-14 07:39:01 UTC.

The current list of available map background layers in the mapviever is hardcoded.

I would like to be able to enter new background-tile-layers in the preferences-setting so that I can use these in the MapViewer.

In addition I would like to be able to re-order the list in order to determine default background layer.

Work to do:

1. Make sqleditor/geometry_viewer.js fetch the list of background layers from the preferences-object

2. Add a preferences-type of "list" so that new layers with name, tile-url, and attribution-text can be added
   2.1 This should also support re-ordering of the list
   2.2 And Deletion of elements
   2.3 And edit of existing elements

3. Add the now hard-coded layers as defaults
   3.1 Possibly make these non-deleteable

4. Figure out where in the preferences-menu to add this
   4.1 I suggest that it is put on a new subitem (Mapviewer?) under "SQL Editor"

I will try to implement this myself, but all input is welcome. I cannot guarantee any timeframe for this.

Sugg

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/3646#note-1
Originally created by Frikan Erwee at 2018-10-20 06:09:09 UTC.

Hi Alte,

Would you mind if we make this a Google Code-in task? I will mentor it with Xuri Goong(Original Contributor) if you give us the go ahead.

Frikan

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/3646#note-2
Originally created by Khushboo Vashi at 2019-06-21 10:54:15 UTC.

Redmine ticket header update:

Name	Old Value	New Value
Sprint changed		Ready

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/3646#note-3
Originally created by Dave Page at 2019-12-19 16:03:07 UTC.

Redmine ticket header update:

Name	Old Value	New Value
Relationship (duplicated) changed		RM #5033

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/3646#note-4
Originally created by Pruss Wan at 2019-12-19 16:21:48 UTC.

This seems straightforward enough, I propose to start with a simpler version of Point 2: just add an option to user preferences for custom tile layer url (which will be added to the default list). As for Point 4, given the current interface, perhaps it should be under Query Tool -> Geometry Viewer?

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/3646#note-5
Originally created by Dave Page at 2019-12-19 16:36:51 UTC.

Sounds like a good start.

[dpage]

Image migrated from Redmine: https://redmine.postgresql.org/attachments/download/5459
Originally created by Robert Hewlett at 2020-11-20 17:34:07 UTC.

Filename: transform_geom_viewer.jpg

[dpage]

Image migrated from Redmine: https://redmine.postgresql.org/attachments/download/5460
Originally created by Robert Hewlett at 2020-11-20 17:36:03 UTC.

Filename: transform_geom_viewer.jpg

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/3646#note-8
Originally created by Robert Hewlett at 2020-11-20 17:41:01 UTC.

Not sure if this is the correct procedure but I would like to make another suggestion.

Low hanging fruit/quick hitter

Update the geometry viewer to:
if geom.SRID != 4326:
st_transform(geom, 4326)

You could have it as a preference that the user could turn on/off.

It would be nice if the current basemap would pop for all geometry_columns columns
The data below is stored in 3005 and if I manually do the transform I can get the basemap to show
!transform_geom_viewer.jpg!

Redmine ticket header update:

Name	Old Value	New Value
Attachment added		transform_geom_viewer.jpg
Attachment added		transform_geom_viewer.jpg

[dpage]

Comment migrated from Redmine: https://redmine.postgresql.org/issues/3646#note-9
Originally created by Fred Escallier at 2021-10-21 15:30:46 UTC.

this could be a great feature

gemetry reprojection (transform)
or adding a srid option in prefernces

I don't know what the easiest solutions is