Custom query (1091 matches)

Filters
 
or
 
  
 
Columns

Show under each result:


Results (85 - 87 of 1091)

Ticket Resolution Summary Owner Reporter
#1000 fixed Accented characters missing on doc web site live-demo@… barryrowlingson
Description

On the sponsors page, some names seems to have dropped accented characters:

http://live.osgeo.org/en/sponsors.html

Eike Hinderk Jrrens

  • should have a u-umlaut in surname.

Grald Fenoy

  • should be Gerald with an acute accent "/"

maybe there are others, but there are plenty of names with correct accents.

#2126 fixed User "user" not in group "users" on OSGeoLive vmdk osgeolive@… Ben Caradoc-Davies
Description

The user "user" is not a member of the "users" group on the OSGeoLive 12.0 vmdk. This prevents GeoServer from writing to its data directory and causes GeoServer to fail to start. The iso image is not affected by this problem.

Workaround is to fix the vmdk with the following one-time procedure:

(1) Start a terminal.

(2) Run "sudo adduser user users".

(3) Apply this change by starting a new desktop session: either restart the virtual machine or log out and log back in (username "user", password "user").

GeoServer should now start normally.

OSGeoLive mailing list discussion:
https://lists.osgeo.org/pipermail/osgeolive/2018-September/013581.html

#1972 wontfix Remove "planet" prefix from OSM data in PostGIS live-demo@… bufferclip
Description

The tables of the OSM data in PostGIS are called like: "planet_osm_line", "planet_osm_point" ...

I find this very confusing, because the tables only contain the data for the feature city. (and obviously not of the planet)

I suggest to rename these tables. This can easily be done by using the "--prefix" flag from osm2pgsql . This is the corresponding text file in OSGeo-live.

I see two possibilities for renaming:

  • a static prefix like "feature_city_line", "feature_city_point", ...

OR

  • a dynamic prefix like "bonn_line", "bonn_point", ...
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.