ChangeLog

+2018-08-11 09:22  Regina Obe <lr@pcorp.us>
+
+	* [r16688] raster/test/regress/rt_gdalwarp.sql,
+	  raster/test/regress/rt_gdalwarp_expected: disable tests that give
+	  different answer on Proj.5 vs. Proj.4
+	  References #4104 for PostGIS 2.5.0
+
+2018-08-11 09:07  Regina Obe <lr@pcorp.us>
+
+	* [r16687] doc/reference_editor.xml: Fix typo in last commit
+	  References #3317 for PostGIS 2.5.0
+
+2018-08-11 08:58  Regina Obe <lr@pcorp.us>
+
+	* [r16686] doc/reference_editor.xml: Put a note that ST_LineMerge
+	  strips M dimension. Provide an example of Z-dimension linestrings
+	  Closes #3317
+
+2018-08-10 15:57  Raúl Marín Rodríguez <rmrodriguez@carto.com>
+
+	* [r16685] NEWS, postgis/mvt.c, postgis/mvt.h, regress/mvt.sql,
+	  regress/mvt_expected, regress/mvt_jsonb.sql,
+	  regress/mvt_jsonb_expected: Speedup MVT column parsing
+	  
+	  Closes #4145
+	  Closes https://github.com/postgis/postgis/pull/286
+
+2018-08-10 11:33  Raúl Marín Rodríguez <rmrodriguez@carto.com>
+
+	* [r16684] postgis/mvt.c, postgis/mvt.h: MVT: Uniformize style and
+	  rename mvt_agg_context 'c'
+	  
+	  References #4145
+	  Closes https://github.com/postgis/postgis/pull/285
+
+2018-08-08 00:57  Daniel Baston <dbaston@gmail.com>
+
+	* [r16683] NEWS, liblwgeom/cunit/cu_geos.c,
+	  liblwgeom/lwgeom_geos.c: Fix backend crash on ST_OffsetCurve
+	  failure
+	  
+	  Closes #4143
+
+2018-08-07 10:34  Regina Obe <lr@pcorp.us>
+
+	* [r16682] raster/test/regress/rt_gdalwarp.sql: Change srid test
+	  for 993309 to be the same as 3309 in spatial_ref_sys table.
+	  References #4104
+
+2018-08-02 10:07  Raúl Marín Rodríguez <rmrodriguez@carto.com>
+
+	* [r16681] configure.ac, liblwgeom/cunit/cu_triangulate.c,
+	  regress/Makefile.in: Remove Geos 3.4 guards
+	  
+	  References #4069
+	  Closes #4142
+	  Closes https://github.com/postgis/postgis/pull/284
+
+2018-08-01 18:32  Paul Ramsey <pramsey@cleverelephant.ca>
+
+	* [r16680] postgis/postgis_drop_after.sql: Add rectfuncts to drop
+	  file so existing installs will get cleaned up
+
+2018-08-01 15:37  Daniel Baston <dbaston@gmail.com>
+
+	* [r16679] NEWS, doc/reference_processing.xml,
+	  liblwgeom/lwgeom_geos.c, regress/clipbybox2d_expected,
+	  regress/mvt_expected: Revert lwgeom_clip_by_rect to use
+	  GEOSClipByRect
+	  
+	  This commit reverts lwgeom_clip_by_rect to its implementation in
+	  PostGIS 2.2 -
+	  2.4.
+	  
+	  It makes trivial modifications to the MVT tests to reflect the
+	  different results
+	  returned by GEOSClipByRect instead of GEOSIntersection. The
+	  changed results are
+	  topologically equivalent to the previous results, and their
+	  orientation is
+	  unchanged.
+	  
+	  No tests have been commented out or made version-dependent.
+	  
+	  Closes #4134
+	  Closes #4135
+	  References #4038
+	  Closes https://github.com/postgis/postgis/pull/282
+
+2018-08-01 15:21  Paul Ramsey <pramsey@cleverelephant.ca>
+
+	* [r16678] postgis/postgis.sql.in: Comment out rect-tree testing
+	  functions for now
+
+2018-08-01 09:49  Raúl Marín Rodríguez <rmrodriguez@carto.com>
+
+	* [r16677] extensions/address_standardizer/analyze.c: Address
+	  standardizer warning
+	  
+	  References #4140
+
+2018-08-01 00:45  Daniel Baston <dbaston@gmail.com>
+
+	* [r16676] liblwgeom/lwgeom.c: Make lwgeom_subdivide use
+	  lwgeom_intersection for clipping
+	  
+	  lwgeom_clip_by_rect describes itself as clipping in a "fast but
+	  possibly
+	  dirty way." This is not a good fit for lwgeom_subdivide, a
+	  primary use of
+	  which is the optimization of point-in-polygon processes. That
+	  application
+	  requires that the area covered by the subdivided geometry be the
+	  same as
+	  the area covered by the original geometry, which in turn requires
+	  that a
+	  robust intersection routine be used.
+	  
+	  References #4038
+	  Closes https://github.com/postgis/postgis/pull/281
+
+2018-07-30 16:38  Regina Obe <lr@pcorp.us>
+
+	* [r16675] doc/po/de/extras_topology.xml.po, doc/po/de/faq.xml.po,
+	  doc/po/de/faq_raster.xml.po, doc/po/de/installation.xml.po,
+	  doc/po/de/introduction.xml.po,
+	  doc/po/de_DE/extras_tigergeocoder.xml.po,
+	  doc/po/de_DE/extras_topology.xml.po, doc/po/de_DE/faq.xml.po,
+	  doc/po/de_DE/faq_raster.xml.po, doc/po/de_DE/installation.xml.po,
+	  doc/po/de_DE/introduction.xml.po,
+	  doc/po/de_DE/reference_accessor.xml.po,
+	  doc/po/de_DE/reference_constructor.xml.po,
+	  doc/po/de_DE/reference_editor.xml.po,
+	  doc/po/de_DE/reference_lrs.xml.po,
+	  doc/po/de_DE/reference_management.xml.po,
+	  doc/po/de_DE/reference_measure.xml.po,
+	  doc/po/de_DE/reference_misc.xml.po,
+	  doc/po/de_DE/reference_output.xml.po,
+	  doc/po/de_DE/reference_processing.xml.po,
+	  doc/po/de_DE/reference_raster.xml.po,
+	  doc/po/de_DE/reference_type.xml.po,
+	  doc/po/de_DE/release_notes.xml.po,
+	  doc/po/de_DE/using_postgis_dataman.xml.po,
+	  doc/po/es/extras_historytable.xml.po,
+	  doc/po/es/extras_tigergeocoder.xml.po,
+	  doc/po/es/extras_topology.xml.po, doc/po/es/faq.xml.po,
+	  doc/po/es/faq_raster.xml.po, doc/po/es/installation.xml.po,
+	  doc/po/es/introduction.xml.po,
+	  doc/po/es/reference_accessor.xml.po,
+	  doc/po/es/reference_constructor.xml.po,
+	  doc/po/es/reference_editor.xml.po,
+	  doc/po/es/reference_lrs.xml.po,
+	  doc/po/es/reference_management.xml.po,
+	  doc/po/es/reference_measure.xml.po,
+	  doc/po/es/reference_misc.xml.po,
+	  doc/po/es/reference_operator.xml.po,
+	  doc/po/es/reference_output.xml.po,
+	  doc/po/es/reference_processing.xml.po,
+	  doc/po/es/reference_raster.xml.po,
+	  doc/po/es/reference_type.xml.po, doc/po/es/release_notes.xml.po,
+	  doc/po/es/using_postgis_dataman.xml.po,
+	  doc/po/fr/extras_address_standardizer.xml.po,
+	  doc/po/fr/extras_historytable.xml.po,
+	  doc/po/fr/extras_tigergeocoder.xml.po,
+	  doc/po/fr/extras_topology.xml.po, doc/po/fr/faq.xml.po,
+	  doc/po/fr/faq_raster.xml.po, doc/po/fr/installation.xml.po,
+	  doc/po/fr/introduction.xml.po,
+	  doc/po/fr/reference_accessor.xml.po,
+	  doc/po/fr/reference_constructor.xml.po,
+	  doc/po/fr/reference_editor.xml.po,
+	  doc/po/fr/reference_lrs.xml.po,
+	  doc/po/fr/reference_management.xml.po,
+	  doc/po/fr/reference_measure.xml.po,
+	  doc/po/fr/reference_misc.xml.po,
+	  doc/po/fr/reference_output.xml.po,
+	  doc/po/fr/reference_processing.xml.po,
+	  doc/po/fr/reference_raster.xml.po,
+	  doc/po/fr/reference_type.xml.po, doc/po/fr/release_notes.xml.po,
+	  doc/po/fr/using_postgis_dataman.xml.po,
+	  doc/po/it_IT/extras_address_standardizer.xml.po,
+	  doc/po/it_IT/extras_historytable.xml.po,
+	  doc/po/it_IT/extras_tigergeocoder.xml.po,
+	  doc/po/it_IT/extras_topology.xml.po, doc/po/it_IT/faq.xml.po,
+	  doc/po/it_IT/faq_raster.xml.po, doc/po/it_IT/installation.xml.po,
+	  doc/po/it_IT/introduction.xml.po,
+	  doc/po/it_IT/reference_accessor.xml.po,
+	  doc/po/it_IT/reference_constructor.xml.po,
+	  doc/po/it_IT/reference_editor.xml.po,
+	  doc/po/it_IT/reference_guc.xml.po,
+	  doc/po/it_IT/reference_lrs.xml.po,
+	  doc/po/it_IT/reference_management.xml.po,
+	  doc/po/it_IT/reference_measure.xml.po,
+	  doc/po/it_IT/reference_misc.xml.po,
+	  doc/po/it_IT/reference_output.xml.po,
+	  doc/po/it_IT/reference_processing.xml.po,
+	  doc/po/it_IT/reference_raster.xml.po,
+	  doc/po/it_IT/reference_type.xml.po,
+	  doc/po/it_IT/release_notes.xml.po,
+	  doc/po/it_IT/using_postgis_dataman.xml.po,
+	  doc/po/ja/extras_tigergeocoder.xml.po, doc/po/ja/faq.xml.po,
+	  doc/po/ja/faq_raster.xml.po, doc/po/ja/installation.xml.po,
+	  doc/po/ja/introduction.xml.po,
+	  doc/po/ja/reference_accessor.xml.po,
+	  doc/po/ja/reference_constructor.xml.po,
+	  doc/po/ja/reference_editor.xml.po,
+	  doc/po/ja/reference_guc.xml.po, doc/po/ja/reference_lrs.xml.po,
+	  doc/po/ja/reference_management.xml.po,
+	  doc/po/ja/reference_measure.xml.po,
+	  doc/po/ja/reference_misc.xml.po,
+	  doc/po/ja/reference_output.xml.po,
+	  doc/po/ja/reference_processing.xml.po,
+	  doc/po/ja/reference_raster.xml.po,
+	  doc/po/ja/reference_sfcgal.xml.po,
+	  doc/po/ja/reference_type.xml.po, doc/po/ja/release_notes.xml.po,
+	  doc/po/ja/using_postgis_dataman.xml.po,
+	  doc/po/ko_KR/extras_address_standardizer.xml.po,
+	  doc/po/ko_KR/extras_historytable.xml.po,
+	  doc/po/ko_KR/extras_tigergeocoder.xml.po,
+	  doc/po/ko_KR/extras_topology.xml.po, doc/po/ko_KR/faq.xml.po,
+	  doc/po/ko_KR/faq_raster.xml.po, doc/po/ko_KR/installation.xml.po,
+	  doc/po/ko_KR/introduction.xml.po,
+	  doc/po/ko_KR/reference_accessor.xml.po,
+	  doc/po/ko_KR/reference_constructor.xml.po,
+	  doc/po/ko_KR/reference_editor.xml.po,
+	  doc/po/ko_KR/reference_exception.xml.po,
+	  doc/po/ko_KR/reference_guc.xml.po,
+	  doc/po/ko_KR/reference_lrs.xml.po,
+	  doc/po/ko_KR/reference_management.xml.po,
+	  doc/po/ko_KR/reference_measure.xml.po,
+	  doc/po/ko_KR/reference_misc.xml.po,
+	  doc/po/ko_KR/reference_operator.xml.po,
+	  doc/po/ko_KR/reference_output.xml.po,
+	  doc/po/ko_KR/reference_processing.xml.po,
+	  doc/po/ko_KR/reference_raster.xml.po,
+	  doc/po/ko_KR/reference_sfcgal.xml.po,
+	  doc/po/ko_KR/reference_transaction.xml.po,
+	  doc/po/ko_KR/reference_type.xml.po,
+	  doc/po/ko_KR/release_notes.xml.po,
+	  doc/po/ko_KR/using_postgis_dataman.xml.po,
+	  doc/po/pl/extras_address_standardizer.xml.po,
+	  doc/po/pl/extras_historytable.xml.po,
+	  doc/po/pl/extras_tigergeocoder.xml.po,
+	  doc/po/pl/extras_topology.xml.po, doc/po/pl/faq.xml.po,
+	  doc/po/pl/faq_raster.xml.po, doc/po/pl/installation.xml.po,
+	  doc/po/pl/introduction.xml.po,
+	  doc/po/pl/reference_accessor.xml.po,
+	  doc/po/pl/reference_constructor.xml.po,
+	  doc/po/pl/reference_editor.xml.po,
+	  doc/po/pl/reference_guc.xml.po, doc/po/pl/reference_lrs.xml.po,
+	  doc/po/pl/reference_management.xml.po,
+	  doc/po/pl/reference_measure.xml.po,
+	  doc/po/pl/reference_misc.xml.po,
+	  doc/po/pl/reference_output.xml.po,
+	  doc/po/pl/reference_processing.xml.po,
+	  doc/po/pl/reference_raster.xml.po,
+	  doc/po/pl/reference_sfcgal.xml.po,
+	  doc/po/pl/reference_transaction.xml.po,
+	  doc/po/pl/reference_type.xml.po, doc/po/pl/release_notes.xml.po,
+	  doc/po/pl/using_postgis_app.xml.po,
+	  doc/po/pt_BR/extras_address_standardizer.xml.po,
+	  doc/po/pt_BR/extras_tigergeocoder.xml.po,
+	  doc/po/pt_BR/extras_topology.xml.po, doc/po/pt_BR/faq.xml.po,
+	  doc/po/pt_BR/faq_raster.xml.po, doc/po/pt_BR/installation.xml.po,
+	  doc/po/pt_BR/introduction.xml.po,
+	  doc/po/pt_BR/reference_accessor.xml.po,
+	  doc/po/pt_BR/reference_constructor.xml.po,
+	  doc/po/pt_BR/reference_editor.xml.po,
+	  doc/po/pt_BR/reference_exception.xml.po,
+	  doc/po/pt_BR/reference_lrs.xml.po,
+	  doc/po/pt_BR/reference_management.xml.po,
+	  doc/po/pt_BR/reference_measure.xml.po,
+	  doc/po/pt_BR/reference_misc.xml.po,
+	  doc/po/pt_BR/reference_operator.xml.po,
+	  doc/po/pt_BR/reference_output.xml.po,
+	  doc/po/pt_BR/reference_raster.xml.po,
+	  doc/po/pt_BR/reference_sfcgal.xml.po,
+	  doc/po/pt_BR/reference_type.xml.po,
+	  doc/po/pt_BR/release_notes.xml.po,
+	  doc/po/pt_BR/using_postgis_dataman.xml.po: Update files from
+	  transifex
+
+2018-07-30 16:29  Raúl Marín Rodríguez <rmrodriguez@carto.com>
+
+	* [r16674] NEWS, extensions/address_standardizer/Makefile.in,
+	  extensions/address_standardizer/parseaddress-api.c: Use user
+	  provided CFLAGS in the address standardizer
+	  
+	  Closes https://github.com/postgis/postgis/pull/280
+	  Closes #4140
+
+2018-07-30 16:26  Raúl Marín Rodríguez <rmrodriguez@carto.com>
+
+	* [r16673] NEWS, liblwgeom/liblwgeom_topo.h, topology/Makefile.in,
+	  topology/postgis_topology.c: Use user-provided CFLAGS in the
+	  topology module
+	  
+	  References #4140
+
+2018-07-27 11:28  Raúl Marín Rodríguez <rmrodriguez@carto.com>
+
+	* [r16672] liblwgeom/cunit/cu_in_wkt.c: cu_in_wkt: Fix memory leaks
+	  in tests
+	  
+	  Introduced in #4109
+
+2018-07-25 20:34  Daniel Baston <dbaston@gmail.com>
+
+	* [r16671] NEWS, doc/reference_processing.xml,
+	  liblwgeom/lwgeom_geos.c, regress/clipbybox2d_expected,
+	  regress/tickets_expected: Remove geometry autofix behavior
+	  
+	  References #4040
+	  Closes https://github.com/postgis/postgis/pull/268
+
+2018-07-25 20:15  Daniel Baston <dbaston@gmail.com>
+
+	* [r16670] liblwgeom/lwgeom_geos.c: Clarify retry logic in
+	  lwgeom_offsetcurve
+	  
+	  Closes https://github.com/postgis/postgis/pull/273
+
+2018-07-24 20:50  Paul Ramsey <pramsey@cleverelephant.ca>
+
+	* [r16668] postgis/geography_measurement.c, regress/tickets.sql,
+	  regress/tickets_expected: Ensure index filters on expanded boxes
+	  are large enough to encompass
+	  the radii they are searching, closes #4081
+
+2018-07-24 13:46  Paul Ramsey <pramsey@cleverelephant.ca>
+
+	* [r16667] extensions/address_standardizer/Makefile.in,
+	  extensions/postgis/Makefile.in,
+	  extensions/postgis_tiger_geocoder/Makefile.in: Better parallel
+	  build (references #4105)
+
+2018-07-24 13:10  Paul Ramsey <pramsey@cleverelephant.ca>
+
+	* [r16663] doc/reference_accessor.xml: Harmonize doco with existing
+	  behaviour, closes #4127
+
+2018-07-23 15:42  Raúl Marín Rodríguez <rmrodriguez@carto.com>
+
+	* [r16662] NEWS, liblwgeom/cunit/cu_in_wkt.c,
+	  liblwgeom/lwin_wkt_lex.c, liblwgeom/lwin_wkt_lex.l: Fix WKT
+	  parser accepting numbers with multiple dots
+	  
+	  Closes #4109
+	  Closes https://github.com/postgis/postgis/pull/277
+
+2018-07-23 00:17  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16661] raster/rt_core/rt_pixel.c,
+	  raster/rt_core/rt_serialize.c, raster/rt_core/rt_wkb.c,
+	  raster/test/regress/tickets.sql,
+	  raster/test/regress/tickets_expected: Fix raster regression on
+	  Raspberry Pi.
+	  
+	  A signed NODATA value was assigned to unsigned variable.
+	  On Intel that was reversible, on ARM and PPC it replaced all
+	  negatives with 0.
+	  
+	  Thanks to Alina Dolgikh for supporting me:
+	  https://www.patreon.com/komzpa
+	  
+	  Closes #4102
+	  Closes https://github.com/postgis/postgis/pull/276
+
+2018-07-22 12:22  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16660] NEWS, raster/rt_pg/rtpostgis.sql.in: Fix
+	  TopologyException in Raster Instersection
+	  
+	  Raster _st_intersects was doing ST_Collect of polygons building
+	  each pixel,
+	  which led to invalid geometry and TopologyException.
+	  
+	  Thanks Vinícius A.B. Schmidt for reporting and testing solutions.
+	  
+	  Closes #4132
+
+2018-07-22 05:00  Regina Obe <lr@pcorp.us>
+
+	* [r16659] postgis/postgis.sql.in, regress/Makefile.in,
+	  regress/concave_hull.sql, regress/concave_hull_expected,
+	  regress/concave_hull_hard.sql,
+	  regress/concave_hull_hard_expected,
+	  regress/sfcgal/concave_hull.sql,
+	  regress/sfcgal/concave_hull_expected: put back old sfcgal test
+	  (except use \i, and have the query be what was in sfcgal one),
+	  the sfcgal one was different
+	  Closes #4131
+	  Revise ST_ConcaveHull to use ST_UnaryUnion(ST_Collect..) (cause I
+	  know sfcgal doesn't replace with it's own implementation / a bit
+	  of a cheat)
+	  Take out some ST_Union calls I think are over compensating.
+	  References #3638
+
+2018-07-21 22:42  Regina Obe <lr@pcorp.us>
+
+	* [r16658] doc/reference_raster.xml: Put in refname what kind of
+	  ST_MapAlgebra (expression or callback function)
+	  Closes #2806 for PostGIS 2.5.0
+
+2018-07-21 17:53  Regina Obe <lr@pcorp.us>
+
+	* [r16657] extras/tiger_geocoder/COPYING: Add license info to
+	  tiger_geocoder code
+	  Closes #3287 for PostGIS 2.5.0
+
+2018-07-21 17:38  Regina Obe <lr@pcorp.us>
+
+	* [r16656] doc/po/templates/extras_tigergeocoder.xml.pot,
+	  doc/po/templates/faq.xml.pot,
+	  doc/po/templates/faq_raster.xml.pot,
+	  doc/po/templates/installation.xml.pot,
+	  doc/po/templates/introduction.xml.pot,
+	  doc/po/templates/reference_accessor.xml.pot,
+	  doc/po/templates/reference_constructor.xml.pot,
+	  doc/po/templates/reference_editor.xml.pot,
+	  doc/po/templates/reference_lrs.xml.pot,
+	  doc/po/templates/reference_management.xml.pot,
+	  doc/po/templates/reference_measure.xml.pot,
+	  doc/po/templates/reference_misc.xml.pot,
+	  doc/po/templates/reference_output.xml.pot,
+	  doc/po/templates/reference_processing.xml.pot,
+	  doc/po/templates/reference_raster.xml.pot,
+	  doc/po/templates/reference_type.xml.pot,
+	  doc/po/templates/release_notes.xml.pot,
+	  doc/po/templates/using_postgis_dataman.xml.pot: Update templates
+
+2018-07-21 16:35  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16655] doc/reference_measure.xml, doc/reference_type.xml:
+	  Clarify eps units on DBSCAN. Add ST_Distance examples.
+	  
+	  Closes https://github.com/postgis/postgis/pull/261
+
+2018-07-21 14:20  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16654] raster/rt_core/rt_serialize.c: 32bit allocations are
+	  4-byte aligned, not 8-byte aligned.
+	  
+	  Fix 8-bit alignment assumption in padding to match assert.
+	  
+	  Passes tests on 32bit Ubuntu Artful.
+	  
+	  References #3994
+
+2018-07-21 13:03  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16653] doc/reference_raster.xml: Fix return type doc for
+	  ST_PixelAsPoints, ST_PixelAsPolygons, and ST_PixelAsCentroids
+	  
+	  Closes #2971
+
+2018-07-21 12:22  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16652] doc/extras_tigergeocoder.xml: Clarify that PG* variables
+	  are used by psql directly.
+	  
+	  Closes #2628
+
+2018-07-21 12:16  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16651] doc/reference_constructor.xml, doc/reference_output.xml:
+	  Document precision in EncodedPolyline.
+	  
+	  Closes #3631
+
+2018-07-21 11:56  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16650] doc/faq_raster.xml, doc/postgis.xml: Bump versions in
+	  Raster doc.
+	  
+	  Closes 4124.
+
+2018-07-18 22:10  Regina Obe <lr@pcorp.us>
+
+	* [r16649] regress/sfcgal/concave_hull.sql,
+	  regress/sfcgal/concave_hull_expected: Committ same changes to
+	  concave hull tests to sfcgal as was done for regular
+
+2018-07-17 09:02  Raúl Marín Rodríguez <rmrodriguez@carto.com>
+
+	* [r16648] postgis/mvt.c, regress/mvt.sql, regress/mvt_expected:
+	  ST_AsMVTGeom: Clip using tile coordinates also for buffer 0
+	  
+	  Closes https://github.com/postgis/postgis/pull/272
+	  References #4120
+
+2018-07-16 20:32  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16647] postgis/postgis.sql.in, regress/concave_hull.sql,
+	  regress/concave_hull_expected, regress/ticket_3697.wkt: Make
+	  ST_ConcaveHull always cover original geometry.
+	  
+	  Merge whatever current implementation generates with input before
+	  returinig to user.
+	  Add currently known problematic geometries as test cases for
+	  further rewrites.
+	  
+	  Closes #3638
+	  Closes #3697
+
+2018-07-15 19:15  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16646] doc/html/image_src/Makefile.in: Disable parallel doc
+	  image generation
+	  
+	  generator.c reuses same tmp[0-9].png intermediate files and
+	  corrupts images in debian packaged documentation.
+	  
+	  Reported on #postgresql-apt@freenode by Myon (Christoph Berg).
+
+2018-07-14 22:00  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16645] raster/rt_core/rt_mapalgebra.c,
+	  raster/rt_core/rt_raster.c,
+	  raster/rt_core/rt_spatial_relationship.c,
+	  raster/rt_pg/rtpg_create.c, raster/rt_pg/rtpg_gdal.c,
+	  raster/rt_pg/rtpg_geometry.c, raster/rt_pg/rtpg_mapalgebra.c,
+	  raster/rt_pg/rtpg_statistics.c,
+	  raster/test/cunit/cu_mapalgebra.c: Fix raster notices.
+	  
+	  References #3994
+	  Closes https://github.com/postgis/postgis/pull/271
+
+2018-07-13 23:30  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16644] configure.ac: Fix postgis_tiger_geocoder.control
+	  generation
+	  
+	  Patch by Christoph Berg
+	  
+	  Commit 639308e moved the postgis_tiger_geocoder.control into the
+	  Makefile, but forgot to remove the file from configure.ac, which
+	  still
+	  generates the file, so the Makefile rule is not effective and the
+	  resulting .control file has the raw @EXTVERSION@ line from the
+	  .in file.
+	  
+	  Closes #4123
+	  Closes https://github.com/postgis/postgis/pull/270
+
+2018-07-13 21:20  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16643] doc/faq.xml: Sync column names in example.
+	  
+	  Closes #4121
+
+2018-07-13 21:07  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16642] doc/using_postgis_dataman.xml: SP-GiST documentation.
+	  
+	  Patch provided by Esteban Zimanyi.
+	  
+	  Closes #1847
+
+2018-07-13 20:06  Darafei Praliaskouski <me@komzpa.net>
+
+	* [r16641] postgis/gserialized_spgist_2d.c,
+	  postgis/gserialized_spgist_3d.c, postgis/gserialized_spgist_3d.h,
+	  postgis/lwgeom_box3d.c, postgis/lwgeom_box3d.h: SP-GiST
+	  implementation polishing
+	  
+	  Added copyrights to headers, moved BOX3D function declarations
+	  from SP-GiST to box3d headers to suppress warnings.
+	  
+	  
+	  References #1847
+	  Closes https://github.com/postgis/postgis/pull/269
+
+2018-07-10 14:25  Raúl Marín Rodríguez <rmrodriguez@carto.com>
+
+	* [r16640] NEWS, postgis/mvt.c, regress/mvt.sql,
+	  regress/mvt_expected: ST_AsMVTGeom: Clip using tile coordinates
+	  
+	  Closes #4120
+	  Closes https://github.com/postgis/postgis/pull/267
+
+2018-07-10 13:42  Daniel Baston <dbaston@gmail.com>
+
+	* [r16639] NEWS, liblwgeom/lwgeom_geos.c: Improve lwgeom_geos
+	  clarity
+	  
+	  References #4027
+	  Closes https://github.com/postgis/postgis/pull/264
+
+2018-07-06 14:49  Raúl Marín Rodríguez <rmrodriguez@carto.com>
+
+	* [r16638] liblwgeom/lwgeom_geos.c, liblwgeom/lwgeom_geos_clean.c,
+	  liblwgeom/lwprint.c, liblwgeom/lwspheroid.c: Clean memory
+	  sanitizer warnings
+	  
+	  References #4118
+	  Closes https://github.com/postgis/postgis/pull/265
+
+2018-07-06 13:14  Raúl Marín Rodríguez <rmrodriguez@carto.com>
+
+	* [r16637] raster/test/regress/rt_gdalwarp.sql,
+	  raster/test/regress/rt_setvalues_geomval.sql, regress/twkb.sql,
+	  topology/test/regress/st_remedgemodface.sql,
+	  topology/test/regress/st_remedgemodface_expected,
+	  topology/test/regress/st_remedgenewface.sql,
+	  topology/test/regress/st_remedgenewface_expected: Adapt regress
+	  tests for parallel plans
+	  
+	  Closes #4117
+	  Closes https://github.com/postgis/postgis/pull/266
+
+2018-07-06 11:21  Raúl Marín Rodríguez <rmrodriguez@carto.com>
+
+	* [r16636] NEWS, postgis/mvt.c: MVT combine: Fix bug with invalid
+	  property values
+	  
+	  Closes #4115
+	  Closes https://github.com/postgis/postgis/pull/263
+
+2018-07-04 20:41  Regina Obe <lr@pcorp.us>
+
+	* [r16634] ci/debbie/postgis_regress.sh: Reenable debbie's SFCGAL
+	  References #4068
+
+2018-07-03 21:45  Regina Obe <lr@pcorp.us>
+
+	* [r16633] Version.config, extensions/upgradeable_versions.mk: Flip
+	  to 2.5.0beta2dev
+
+2018-07-03 20:04  Regina Obe <lr@pcorp.us>
+
+	* [r16631] doc/release_notes.xml: update doc release notes in prep
+	  for 2.5.0beta1 release
+
+2018-07-03 18:04  Regina Obe <lr@pcorp.us>
+
+	* [r16630] ChangeLog, NEWS, Version.config: Prepping for 2.5.0beta1
+	  release
+
 2018-07-01 16:30  Regina Obe <lr@pcorp.us>
 	* [r16629] libpgcommon/gserialized_gist.h: Get rid of the ifdefs

NEWS

+PostGIS 2.5.0beta2
+2018/08/11
+New since PostGIS 2.5.0beta1
+  - #4115, Fix a bug that created MVTs with incorrect property values under
+    parallel plans (Raúl Marín).
+  - #4120, ST_AsMVTGeom: Clip using tile coordinates (Raúl Marín).
+  - #4132, ST_Intersection on Raster now works without throwing TopologyException
+    (Vinícius A.B. Schmidt, Darafei Praliaskouski)
+  - #4109, Fix WKT parser accepting and interpreting numbers with
+    multiple dots (Raúl Marín, Paul Ramsey)
+  - #4140, Use user-provided CFLAGS in address standardizer and the
+    topology module (Raúl Marín)
+  - #4143, Fix backend crash when ST_OffsetCurve fails (Dan Baston)
+  - #4145, Speedup MVT column parsing (Raúl Marín)
+
+  See PostGIS 2.5.0 section for full details
+
+
 PostGIS 2.5.0beta1
 2018/07/03
 New since PostGIS 2.5.0alpha
@@ -76,12 +94,8 @@ PostGIS 2.5.0
   - #2508, ST_OffsetCurve now works with collections (Darafei Praliaskouski)
   - #4006, ST_GeomFromGeoJSON support for json and jsonb as input
            (Paul Ramsey, Regina Obe)
-  - #4037, Invalid input geometry is fixed with MakeValid for GEOS exceptions in
-           ST_Intersection, ST_Union, ST_Difference, ST_SymDifference (Darafei
-           Praliaskouski)
   - #4038, ST_Subdivide now selects pivot for geometry split that reuses input
-           vertices. ST_ClipByBox2D is stubbed with ST_Intersection because of
-           robustness issues. (Darafei Praliaskouski)
+           vertices. (Darafei Praliaskouski)
   - #4025, #4032 Fixed precision issue in ST_ClosestPointOfApproach,
            ST_DistanceCPA, and ST_CPAWithin (Paul Ramsey, Darafei Praliaskouski)
   - #4076, Reduce use of GEOS in topology implementation (Björn Harrtell)
@@ -91,7 +105,11 @@ PostGIS 2.5.0
   - #4084: Fixed wrong code-comment regarding front/back of BOX3D (Matthias Bay)
   - #4060, #4094, PostgreSQL JIT support (Raúl Marín, Laurenz Albe)
   - #3960, ST_Centroid now uses lwgeom_centroid (Darafei Praliaskouski)
-  - #4103, ST_PointOnSurface can handle invalid (Darafei Praliaskouski)
+  - #4027, Remove duplicated code in lwgeom_geos (Darafei Praliaskouski,
+           Daniel Baston)
+  - #4115, Fix a bug that created MVTs with incorrect property values under
+    parallel plans (Raúl Marín).
+  - #4120, ST_AsMVTGeom: Clip using tile coordinates (Raúl Marín).
 
 PostGIS 2.4.4
 2018/04/08

README.postgis

 PostGIS - Geographic Information Systems Extensions to PostgreSQL
 =================================================================
 
-:Version: 2.5.0
-:Date: 2018-xx-xx
+:Version: 2.5.0beta2
+:Date: 2018-08-11
 :Website: http://postgis.net
 
 This distribution contains a module which implements GIS simple features, ties

Version.config

@@ -5,7 +5,7 @@
 
 POSTGIS_MAJOR_VERSION=2
 POSTGIS_MINOR_VERSION=5
-POSTGIS_MICRO_VERSION=0beta1
+POSTGIS_MICRO_VERSION=0beta2
 
 # Liblwgeom interface versioning, reset to 0:0:0 (cur:age:rev)
 # when changing POSTGIS_MINOR_VERSION

aclocal.m4

-# generated automatically by aclocal 1.15.1 -*- Autoconf -*-
+# generated automatically by aclocal 1.16.1 -*- Autoconf -*-
 
-# Copyright (C) 1996-2017 Free Software Foundation, Inc.
+# Copyright (C) 1996-2018 Free Software Foundation, Inc.
 
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,
@@ -12,7 +12,7 @@
 # PARTICULAR PURPOSE.
 
 m4_ifndef([AC_CONFIG_MACRO_DIRS], [m4_defun([_AM_CONFIG_MACRO_DIRS], [])m4_defun([AC_CONFIG_MACRO_DIRS], [_AM_CONFIG_MACRO_DIRS($@)])])
-# Copyright (C) 2003-2017 Free Software Foundation, Inc.
+# Copyright (C) 2003-2018 Free Software Foundation, Inc.
 #
 # This file is free software; the Free Software Foundation
 # gives unlimited permission to copy and/or distribute it,

ci/debbie/postgis_regress.sh

@@ -62,7 +62,7 @@ fi
     --with-pgconfig=${PROJECTS}/pg/rel/pg${PG_VER}w${OS_BUILD}/bin/pg_config \
     --with-geosconfig=${PROJECTS}/geos/rel-${GEOS_VER}w${OS_BUILD}/bin/geos-config \
     --with-gdalconfig=${PROJECTS}/gdal/rel-${GDAL_VER}w${OS_BUILD}/bin/gdal-config \
-    --without-interrupt-tests \
+    --with-sfcgal=/usr/bin/sfcgal-config --without-interrupt-tests \
     --prefix=${PROJECTS}/pg/rel/pg${PG_VER}w${OS_BUILD}
 make clean
 make

configure

@@ -17369,9 +17369,6 @@ if test "x$with_topology" != "xno"; then
     TOPOLOGY="topology"
     { $as_echo "$as_me:${as_lineno-$LINENO}: result: TOPOLOGY: Topology support requested" >&5
 $as_echo "TOPOLOGY: Topology support requested" >&6; }
-	if test "$GEOS_NUMERIC_VERSION" -lt 30302; then
-		as_fn_error $? "Topology requires GEOS version >= 3.3.2. Use --without-topology or install a newer GEOS." "$LINENO" 5
-	fi
 else
     { $as_echo "$as_me:${as_lineno-$LINENO}: result: TOPOLOGY: Topology support disabled" >&5
 $as_echo "TOPOLOGY: Topology support disabled" >&6; }
@@ -17864,7 +17861,7 @@ fi
-ac_config_files="$ac_config_files GNUmakefile extensions/Makefile extensions/postgis/Makefile extensions/postgis_sfcgal/Makefile extensions/postgis_topology/Makefile extensions/postgis_tiger_geocoder/Makefile extensions/postgis_tiger_geocoder/postgis_tiger_geocoder.control extensions/address_standardizer/Makefile liblwgeom/Makefile liblwgeom/cunit/Makefile liblwgeom/liblwgeom.h libpgcommon/Makefile libpgcommon/cunit/Makefile postgis/Makefile postgis/sqldefines.h loader/Makefile loader/cunit/Makefile topology/Makefile topology/test/Makefile regress/Makefile doc/Makefile doc/Makefile.comments doc/html/image_src/Makefile utils/Makefile $RT_MAKEFILE_LIST"
+ac_config_files="$ac_config_files GNUmakefile extensions/Makefile extensions/postgis/Makefile extensions/postgis_sfcgal/Makefile extensions/postgis_topology/Makefile extensions/postgis_tiger_geocoder/Makefile extensions/address_standardizer/Makefile liblwgeom/Makefile liblwgeom/cunit/Makefile liblwgeom/liblwgeom.h libpgcommon/Makefile libpgcommon/cunit/Makefile postgis/Makefile postgis/sqldefines.h loader/Makefile loader/cunit/Makefile topology/Makefile topology/test/Makefile regress/Makefile doc/Makefile doc/Makefile.comments doc/html/image_src/Makefile utils/Makefile $RT_MAKEFILE_LIST"
 cat >confcache <<\_ACEOF
 # This file is a shell script that caches the results of configure
@@ -18866,7 +18863,6 @@ do
     "extensions/postgis_sfcgal/Makefile") CONFIG_FILES="$CONFIG_FILES extensions/postgis_sfcgal/Makefile" ;;
     "extensions/postgis_topology/Makefile") CONFIG_FILES="$CONFIG_FILES extensions/postgis_topology/Makefile" ;;
     "extensions/postgis_tiger_geocoder/Makefile") CONFIG_FILES="$CONFIG_FILES extensions/postgis_tiger_geocoder/Makefile" ;;
-    "extensions/postgis_tiger_geocoder/postgis_tiger_geocoder.control") CONFIG_FILES="$CONFIG_FILES extensions/postgis_tiger_geocoder/postgis_tiger_geocoder.control" ;;
     "extensions/address_standardizer/Makefile") CONFIG_FILES="$CONFIG_FILES extensions/address_standardizer/Makefile" ;;
     "liblwgeom/Makefile") CONFIG_FILES="$CONFIG_FILES liblwgeom/Makefile" ;;
     "liblwgeom/cunit/Makefile") CONFIG_FILES="$CONFIG_FILES liblwgeom/cunit/Makefile" ;;

configure.ac

@@ -1181,9 +1181,6 @@ if test "x$with_topology" != "xno"; then
 
     TOPOLOGY="topology"
     AC_MSG_RESULT([TOPOLOGY: Topology support requested])
-	if test "$GEOS_NUMERIC_VERSION" -lt 30302; then
-		AC_MSG_ERROR([Topology requires GEOS version >= 3.3.2. Use --without-topology or install a newer GEOS.])
-	fi
 else
     AC_MSG_RESULT([TOPOLOGY: Topology support disabled])
 fi
@@ -1459,7 +1456,6 @@ AC_OUTPUT([GNUmakefile
    extensions/postgis_sfcgal/Makefile
    extensions/postgis_topology/Makefile
    extensions/postgis_tiger_geocoder/Makefile
-   extensions/postgis_tiger_geocoder/postgis_tiger_geocoder.control
    extensions/address_standardizer/Makefile
    liblwgeom/Makefile
    liblwgeom/cunit/Makefile

debian/changelog

-postgis (2.5.0~beta1+dfsg-1~exp3) UNRELEASED; urgency=medium
+postgis (2.5.0~beta2+dfsg-1~exp1) experimental; urgency=medium
 
   [ Bas Couwenberg ]
+  * New upstream beta release.
   * Don't quote filter string to fix match of first and last items.
   * Bump Standards-Version to 4.2.0, no changes.
+  * Update copyright years for Paul Ramsey.
+  * Drop rt_gdalwarp.patch, worked around by upstream.
+  * Drop unused override for hardening-no-fortify-functions.
+  * Separate test restrictions with a comma.
 
   [ Christoph Berg ]
   * Re-enable tests on arm64 armel armhf i386 ppc64el, fixed upstream.
@@ -14,7 +19,7 @@ postgis (2.5.0~beta1+dfsg-1~exp3) UNRELEASED; urgency=medium
     was already transitional in stretch, and the PG 10 variant was never in a
     stable release.
 
- -- Bas Couwenberg <sebastic@debian.org>  Tue, 17 Jul 2018 08:32:22 +0200
+ -- Bas Couwenberg <sebastic@debian.org>  Sat, 11 Aug 2018 13:15:01 +0200
 
 postgis (2.5.0~beta1+dfsg-1~exp2) experimental; urgency=medium
 

debian/copyright

@@ -40,7 +40,7 @@ Copyright:                   PostGIS Developers <postgis-devel@lists.osgeo.org>
                   2011-2017, Arrival 3D
                   2016-2017, Björn Harrtell <bjorn@wololo.org>
                        2017, Danny Götte <danny.goette@fem.tu-ilmenau.de>
-      2004, 2008-2016, 2018, Paul Ramsey <pramsey@cleverelephant.ca>
+            2004, 2008-2018, Paul Ramsey <pramsey@cleverelephant.ca>
  2010-2011, 2013-2015, 2018, Nicklas Avén <nicklas.aven@jordogskog.no>
                   2013-2018, Bborie Park <dustymugs@gmail.com>
                   2015-2018, Daniel Baston <dbaston@gmail.com>

debian/patches/rt_gdalwarp.patch

-Description: Fix expected test output with GDAL 2.3.0 & PROJ 5.1.0.
-Author: Bas Couwenberg <sebastic@debian.org>
-Bug: https://trac.osgeo.org/postgis/ticket/4104
-Bug-Debian: https://bugs.debian.org/901158
-
---- a/raster/test/regress/rt_gdalwarp_expected
-+++ b/raster/test/regress/rt_gdalwarp_expected
-@@ -19,8 +19,8 @@ NOTICE:  Values must be provided for bot
- 0.17|993309|243|243|1|50.000|50.000|0.000|0.000|950760.000|1396957.000|t|t|t
- 0.18|992163|10|10|1|1000.000|-1000.000|3.000|3.000|-500030.000|600000.000|t|t|t
- 0.19|993310|12|12|1|1009.894|-1009.894|3.000|3.000|950691.792|1409281.783|t|t|t
--0.2|993309|12|12|1|1009.916|-1009.916|0.000|0.000|950762.305|1409088.896|t|t|t
--0.20|993309|12|12|1|1009.916|-1009.916|1.000|3.000|950742.107|1409088.896|t|t|t
-+0.2|993309|12|12|1|1009.876|-1009.876|0.000|0.000|950808.447|1409091.640|t|t|t
-+0.20|993309|12|12|1|1009.876|-1009.876|1.000|3.000|950788.250|1409091.640|t|t|t
- 0.21|993310|24|24|1|500.000|500.000|3.000|3.000|950657.188|1397356.783|t|t|t
- 0.22|993310|26|26|1|500.000|500.000|0.000|6.000|950452.000|1396632.000|t|t|t
- 0.23|984269|12|8|1|0.012|-0.012|0.000|0.000|-107.029|50.206|t|t|t
-@@ -63,12 +63,12 @@ NOTICE:  Values must be provided for bot
- 1.9|992163|11|10|1|1000.000|-1000.000|0.000|0.000|-500001.000|600000.000|t|t|t
- 2.1|993310|12|12|1|1009.894|-1009.894|0.000|0.000|950732.188|1409281.783|t|t|t
- 2.10|993310|24|24|1|500.000|500.000|0.000|0.000|950732.188|1397281.783|t|t|t
--2.11|993309|121|121|1|100.000|100.000|0.000|0.000|950762.305|1396988.896|t|t|t
-+2.11|993309|121|121|1|100.000|100.000|0.000|0.000|950808.447|1396991.640|t|t|t
- 2.12|993310|6|6|1|2000.000|2000.000|0.000|0.000|950732.188|1397281.783|t|t|t
- 2.13|993310|8|8|1|1500.000|1500.000|0.000|0.000|950732.188|1397281.783|t|t|t
- 2.14|993310|24|24|1|500.000|500.000|0.000|0.000|950732.188|1397281.783|t|t|t
- 2.15|993310|16|16|1|750.000|750.000|0.000|0.000|950732.188|1397281.783|t|t|t
--2.2|993309|12|12|1|1009.916|-1009.916|0.000|0.000|950762.305|1409088.896|t|t|t
-+2.2|993309|12|12|1|1009.876|-1009.876|0.000|0.000|950808.447|1409091.640|t|t|t
- 2.3|994269|12|8|1|0.012|-0.012|0.000|0.000|-107.029|50.206|t|t|t
- 2.4|||||||||||||
- 2.5|993310|12|12|1|1009.894|-1009.894|0.000|0.000|950732.188|1409281.783|t|t|t

debian/patches/series

 link-liblwgeom
 relax-test-timing-constraints.patch
-rt_gdalwarp.patch

debian/postgresql-10-postgis-2.5.lintian-overrides

-# Build uses -D_FORTIFY_SOURCE=2, but hardening-check reports:
-#  Fortify Source functions: no, only unprotected functions found!
-hardening-no-fortify-functions usr/lib/postgresql/*/lib/address_standardizer.so
-

debian/tests/control

 Depends: @, postgresql-server-dev-all, postgresql-all
 Tests: test-extension-creation
-Restrictions: needs-root allow-stderr
+Restrictions: needs-root, allow-stderr

doc/extras_tigergeocoder.xml

@@ -781,6 +781,7 @@ TMPDIR="/gisdata/temp/"
 UNZIPTOOL=unzip
 WGETTOOL="/usr/bin/wget"
 export PGBIN=/usr/lib/postgresql/9.4/bin
+-- variables used by psql: https://www.postgresql.org/docs/current/static/libpq-envars.html
 export PGPORT=5432
 export PGHOST=localhost
 export PGUSER=postgres

doc/faq.xml

@@ -156,8 +156,7 @@ SELECT MAX(ST_NPoints(geom)) FROM sometable;</programlisting>
 		For geometry: Connect to your database with
         <filename>psql</filename> and try the following SQL:</para>
 
-        <programlisting>CREATE TABLE gtest ( gid serial primary key, name varchar(20)
-        , geom geometry(LINESTRING) );</programlisting>
+        <programlisting>CREATE TABLE gtest (id serial primary key, name varchar(20), geom geometry(LINESTRING));</programlisting>
 
         <para>If the geometry column definition fails, you probably have not
         loaded the PostGIS functions and objects into this database or are using a pre-2.0 version of PostGIS. See the

doc/faq_raster.xml

@@ -3,20 +3,6 @@
   <title>PostGIS Raster Frequently Asked Questions</title>
 
   <qandaset>
-
-     <qandaentry id="faq_security_change_1">
-      <question>
-        <para>I'm getting error <code>ERROR: RASTER_fromGDALRaster: Could not open bytea with GDAL. Check that the bytea is of a GDAL supported format.</code>  when using ST_FromGDALRaster
-        or <code>ERROR: rt_raster_to_gdal: Could not load the output GDAL driver</code> when trying to use ST_AsPNG or other raster input functions.</para>
-      </question>
-
-      <answer>
-          <para>As of PostGIS 2.1.3 and 2.0.5, a security change was made to by default disable all GDAL drivers and out of db rasters. The release notes are at <ulink url="http://postgis.net/2014/05/19/postgis-2.0.6_and_2.1.3">PostGIS 2.0.6, 2.1.3 security release</ulink>. In order to reenable specific drivers or all drivers and reenable out of database support, refer to <xref linkend="install_short_version" />.</para>
-      </answer>
-    </qandaentry>
-
-
-
     <qandaentry>
       <question>
         <para>Where can I find out more about the PostGIS Raster Project?</para>
@@ -51,8 +37,7 @@
       </question>
 
       <answer>
-        <para>The easiest is to download binaries for PostGIS and Raster which are currently available for windows and latest versions of Mac OSX.
-	First you need a working PostGIS 2.0.0 or above and be running PostgreSQL 8.4, 9.0, or 9.1. Note in PostGIS 2.0 PostGIS Raster is fully integrated, so it will be compiled when you compile PostGIS.</para>
+        <para>Starting with PostGIS 2.0 PostGIS Raster is fully integrated, so it will be compiled when you compile PostGIS.</para>
 	<para>Instructions for installing and running under windows are available at <ulink url="http://gis4free.wordpress.com/2011/03/10/how-to-install-and-configure-postgis-raster-on-windows/">How to Install and Configure PostGIS raster on windows</ulink></para>
         <para>
 			If you are on windows, you can compile yourself, or use the <ulink
@@ -60,8 +45,7 @@
             PostGIS Raster windows binaries</ulink>.
 			If you are on Mac OSX Leopard or Snow Leopard, there are binaries available at <ulink url="http://www.kyngchaos.com/software/postgres">Kyng Chaos Mac OSX PostgreSQL/GIS binaries</ulink>.
 		</para>
-		<para>Then to enable raster support in your database, run the rtpostgis.sql file in your database.  To upgrade an existing install use rtpostgis_upgrade_minor..sql instead of rtpostgis.sql</para>
-		<para>For other platforms, you generally need to compile yourself. Dependencies are PostGIS and GDAL. For more details about compiling from source, please refer to <ulink url="http://trac.osgeo.org/postgis/wiki/WKTRaster/Documentation01#a2.3-CompilingandInstallingfromSources">Installing PostGIS Raster from source (in prior versions of PostGIS)</ulink></para>
+		<para>For other platforms, install PostGIS from your software repository. For more details about compiling from source, please refer to <ulink url="http://trac.osgeo.org/postgis/wiki/WKTRaster/Documentation01#a2.3-CompilingandInstallingfromSources">Installing PostGIS Raster from source</ulink></para>
       </answer>
     </qandaentry>
 
@@ -85,7 +69,7 @@
       </question>
 
       <answer>
-        <para>The latest version of PostGIS comes packaged with a <varname>raster2pgsql</varname> raster loader executable capable of loading many kinds of rasters and also generating lower resolution overviews without any additional software. Please refer to <xref linkend="RT_Raster_Loader" /> for more details. Pre-2.0 versions came with a <varname>raster2pgsql.py</varname> that required python with numpy and GDAL.  This is no longer needed.</para>
+        <para>The latest version of PostGIS comes packaged with a <varname>raster2pgsql</varname> raster loader executable capable of loading many kinds of rasters and also generating lower resolution overviews without any additional software. Please refer to <xref linkend="RT_Raster_Loader" /> for more details.</para>
       </answer>
     </qandaentry>
 
@@ -108,7 +92,7 @@
 
       <answer>
         <para>Yes</para>
-		<para>GDAL 1.7+ has a PostGIS raster driver, but is only compiled in if you choose to compile with PostgreSQL support. </para>
+		<para>GDAL has a PostGIS raster driver, but is only compiled in if you choose to compile with PostgreSQL support. </para>
 		<para>The driver currently doesn't support irregularly blocked rasters,
 		although you can store irregularly blocked rasters in PostGIS raster data type.</para>
 		<para>If you are compiling from source, you need to include in your configure
@@ -158,7 +142,7 @@
       </question>
 
       <answer>
-        <para>You can use MapServer compiled with GDAL 1.7+ and PostGIS Raster driver support to view Raster data. QuantumGIS (QGIS) now supports viewing of PostGIS Raster if you
+        <para>You can use MapServer compiled with GDAL 1.7+ and PostGIS Raster driver support to view Raster data. QGIS supports viewing of PostGIS Raster if you
         have PostGIS raster driver installed.</para>
         <para>In theory any tool that renders data using GDAL can support PostGIS raster data or
             support it with fairly minimal effort. Again for Windows, Tamas' binaries <ulink url="www.gisinternals.com">http://www.gisinternals.com</ulink> are a good choice if you don't want the hassle of having to setup to compile your own.</para>
@@ -298,5 +282,17 @@ END
       </answer>
   </qandaentry>
 
+     <qandaentry id="faq_security_change_1">
+      <question>
+        <para>I'm getting error <code>ERROR: RASTER_fromGDALRaster: Could not open bytea with GDAL. Check that the bytea is of a GDAL supported format.</code>  when using ST_FromGDALRaster
+        or <code>ERROR: rt_raster_to_gdal: Could not load the output GDAL driver</code> when trying to use ST_AsPNG or other raster input functions.</para>
+      </question>
+
+      <answer>
+          <para>As of PostGIS 2.1.3 and 2.0.5, a security change was made to by default disable all GDAL drivers and out of db rasters. The release notes are at <ulink url="http://postgis.net/2014/05/19/postgis-2.0.6_and_2.1.3">PostGIS 2.0.6, 2.1.3 security release</ulink>. In order to reenable specific drivers or all drivers and reenable out of database support, refer to <xref linkend="install_short_version" />.</para>
+      </answer>
+    </qandaentry>
+
+
  </qandaset>
 </chapter>

doc/html/image_src/Makefile.in

@@ -205,3 +205,4 @@ distclean: clean
 images-clean:
 	rm -f $(IMAGES) $(IMAGES_RESIZED)
 
+.NOTPARALLEL:

doc/po/de/extras_topology.xml.po

@@ -7,8 +7,8 @@ msgstr ""
 "Project-Id-Version: PostGIS\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
 "POT-Creation-Date: 2017-09-14 18:44+0000\n"
-"PO-Revision-Date: 2017-09-14 19:09+0000\n"
-"Last-Translator: Regina Obe\n"
+"PO-Revision-Date: 2018-07-23 18:01+0000\n"
+"Last-Translator: Andreas Schild <andreas.schild@bfw.gv.at>\n"
 "Language-Team: German (http://www.transifex.com/postgis/postgis/language/de/)\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
@@ -412,7 +412,7 @@ msgid ""
 "For any given hierarchical TopoGeometry all child TopoGeometry elements will"
 " come from the same child layer, as specified in the topology.layer record "
 "for the layer of the TopoGeometry being defined."
-msgstr ""
+msgstr "Bei jeder gegebenen hierarchischen TopoGeometry werden alle Kindklassen der TopoGeometrie vom selben Kindlayer abgeleitet, so wie dies in dem Datensatz von \"topology.layer\" für den Layer der TopoGeometry definiert ist."
 
 #. Tag: title
 #: extras_topology.xml:162 extras_topology.xml:190 extras_topology.xml:281
@@ -2368,7 +2368,7 @@ msgstr "-- Einen alleinstehenden Knoten, ohne Masche, entfernen  --\nSELECT topo
 #: extras_topology.xml:1626
 #, no-c-format
 msgid "ST_RemoveIsoEdge"
-msgstr ""
+msgstr "ST_RemoveIsoEdge"
 
 #. Tag: refpurpose
 #: extras_topology.xml:1628
@@ -2376,7 +2376,7 @@ msgstr ""
 msgid ""
 "<refpurpose>Removes an isolated edge and returns description of action. If "
 "the edge is not isolated, then an exception is thrown.</refpurpose>"
-msgstr ""
+msgstr "<refpurpose>Löscht einen isolierten Knoten und gibt eine Beschreibung der getroffenen Maßnahmen aus. Falls der Knoten nicht isoliert ist, wird eine Fehlermeldung ausgegeben.</refpurpose>"
 
 #. Tag: funcprototype
 #: extras_topology.xml:1633
@@ -2385,7 +2385,7 @@ msgid ""
 "<funcdef>text <function>ST_RemoveIsoEdge</function></funcdef> "
 "<paramdef><type>varchar </type> <parameter>atopology</parameter></paramdef> "
 "<paramdef><type>integer </type> <parameter>anedge</parameter></paramdef>"
-msgstr ""
+msgstr "<funcdef>text <function>ST_RemoveIsoEdge</function></funcdef> <paramdef><type>varchar </type> <parameter>atopology</parameter></paramdef> <paramdef><type>integer </type> <parameter>anedge</parameter></paramdef>"
 
 #. Tag: para
 #: extras_topology.xml:1644
@@ -2393,7 +2393,7 @@ msgstr ""
 msgid ""
 "<para>Removes an isolated edge and returns description of action. If the "
 "edge is not isolated, then an exception is thrown.</para>"
-msgstr ""
+msgstr "<para>Löscht einen isolierten Knoten und gibt eine Beschreibung der getroffenen Maßnahmen aus. Falls der Knoten nicht isoliert ist, wird eine Fehlermeldung ausgegeben.</para>"
 
 #. Tag: title
 #: extras_topology.xml:1668
@@ -3040,7 +3040,7 @@ msgid ""
 "value 1. A positive edge starts at the given node. A negative edge ends into"
 " the given node. Closed edges will appear twice (with both signs). Order is "
 "clockwise starting from northbound."
-msgstr ""
+msgstr "Gibt für einen Knoten die sortierte Menge der einfallenden Kanten aus. Jede Ausgabe besteht aus einer Sequenz und einer mit Vorzeichen versehenen ID für die Kante. Die Sequenz beginnt mit dem Wert 1. Eine Kante mit positiver ID beginnt an dem gegebenen Knoten. Eine negative Kante endet in dem gegebenen Knoten. Geschlossene Kanten kommen zweimal vor (mit beiden Vorzeichen). Die Sortierung geschieht von Norden ausgehend im Uhrzeigersinn."
 
 #. Tag: para
 #: extras_topology.xml:2138
@@ -4209,7 +4209,7 @@ msgid ""
 "<varname>element_type</varname> and <varname>element_id</varname>, in that "
 "order. Such index would be created automatically by adding a unique "
 "constraint to the fields. Example:"
-msgstr ""
+msgstr "Wenn der Parameter <varname>visitedTable</varname> angegeben ist, dann wird dieser verwendet um die bereits besuchten Knoten und Kanten über Querverweise (xlink:xref) zu verfolgen, anstatt Definitionen zu vervielfältigen. Die Tabelle muss (zumindest) zwei Integerfelder enthalten: 'element_type' und 'element_id'. Für den Aufruf muss der Anwender sowohl Lese- als auch Schreibrechte auf die Tabelle besitzen. Um die maximale Rechenleistung zu erreichen, sollte ein Index für die Attribute <varname>element_type</varname> und <varname>element_id</varname> - in dieser Reihenfolge -  festgelegt werden. Dieser Index wird automatisch erstellt, wenn auf die Attribute ein Unique Constraint gelegt wird. Beispiel:"
 
 #. Tag: programlisting
 #: extras_topology.xml:2962

doc/po/de/faq.xml.po

 # SOME DESCRIPTIVE TITLE.
 # 
 # Translators:
-# Andreas Schild <andreas.schild@bfw.gv.at>, 2017
+# Andreas Schild <andreas.schild@bfw.gv.at>, 2017-2018
 # Andreas Schild <schildandreas1@gmail.com>, 2015
 # Chris Leick <c.leick@vollbio.de>, 2013
 msgid ""
 msgstr ""
 "Project-Id-Version: PostGIS\n"
 "Report-Msgid-Bugs-To: http://bugs.kde.org\n"
-"POT-Creation-Date: 2017-09-07 07:22+0000\n"
-"PO-Revision-Date: 2017-09-08 09:05+0000\n"
+"POT-Creation-Date: 2018-07-21 17:36+0000\n"
+"PO-Revision-Date: 2018-07-22 08:03+0000\n"
 "Last-Translator: Andreas Schild <andreas.schild@bfw.gv.at>\n"
 "Language-Team: German (http://www.transifex.com/postgis/postgis/language/de/)\n"
 "MIME-Version: 1.0\n"
@@ -57,7 +57,7 @@ msgstr "Außerdem hat BostonGIS ein <ulink url=\"http://www.bostongis.com/Printe
 msgid ""
 "My applications and desktop tools worked with PostGIS 1.5,but they don't "
 "work with PostGIS 2.0. How do I fix this?"
-msgstr "Meine Anwendungen und Arbeitsflächenwerkzeuge funktionierten mit PostGIS 1.5, nicht jedoch mit PostGIS 2.0. Wie kann ich dies beheben?"
+msgstr "Meine Anwendungen und Desktop-Tools funktionierten mit PostGIS 1.5, nicht jedoch mit PostGIS 2.0. Wie kann ich dies beheben?"
 
 #. Tag: para
 #: faq.xml:22
@@ -73,7 +73,7 @@ msgid ""
 "etc. and as a last resort, install the whole of "
 "<varname>legacy.sql</varname> or just the portions of "
 "<varname>legacy.sql</varname> you need."
-msgstr "Viele missbilligte Funktionen wurden aus der Codebasis von PostGIS 2.0 entfernt. Dies betraf Anwendungen sowie Werkzeuge von Drittanbietern wie Geoserver, MapServer, QuantumGIS und OpenJump, um einige zu nennen. Es gibt ein paar Wege, dies zu beheben. Für die Anwendungen von Drittanbietern können Sie versuchen, sie auf die neuste Version zu aktualisieren, bei der viele dieser Probleme behoben wurden. Ihren eigenen Code könne Sie so ändern, dass er die entfernten Funktionen nicht mehr benutzt. Die meisten dieser Funktionen sind Pseudonyme von ST_Union, ST_Length etc. ohne den Präfix \"ST_\". Als letzten Ausweg können Sie die gesamte <varname>legacy.sql</varname>, oder die Teile die Sie benötigen installieren."
+msgstr "Viele überholte Funktionen wurden aus der Codebasis von PostGIS 2.0 entfernt. Dies betraf Anwendungen sowie Werkzeuge von Drittanbietern wie Geoserver, MapServer, QuantumGIS und OpenJump, um nur ein paar zu nennen. Es gibt mehrere Möglichkeiten dieses Problem zu lösen. Bei Anwendungen von Drittanbietern können Sie versuchen diese auf die neuste Version zu aktualisieren, bei der viele dieser Probleme bereits fixiert wurden. Ihren eigenen Code können Sie so ändern, dass er die überholten Funktionen nicht mehr benutzt. Die meisten dieser Funktionen sind Pseudonyme von ST_Union, ST_Length etc. ohne den Präfix \"ST_\". Als letzten Ausweg können Sie die gesamte <varname>legacy.sql</varname> oder die benötigten Teile davon ausführen. "
 
 #. Tag: para
 #: faq.xml:28
@@ -83,7 +83,7 @@ msgid ""
 "postgis.sql. You can install this file after you have installed postgis.sql "
 "and spatial_ref_sys.sql to get back all the 200 some-odd old functions we "
 "removed."
-msgstr "Die Datei <varname>legacy.sql</varname> liegt im selben Verzeichnis wie »postgis.sql«. Sie können diese Datei nach der Installation von »postgis.sql« und »spatial_ref_sys.sql« installieren, um alle etwa 200 alten Funktionen zurückzubekommen, die entfernt wurden."
+msgstr "Die Datei <varname>legacy.sql</varname> liegt im selben Verzeichnis wie »postgis.sql«. Sie können diese Datei nach der Installation von »postgis.sql« und »spatial_ref_sys.sql« installieren, um alle 200 alten Funktionen wieder herzustellen, die entfernt wurden."
 
 #. Tag: para
 #: faq.xml:35
@@ -112,7 +112,7 @@ msgid ""
 "indexes, explicitly referenced the operator class name. This was unnecessary"
 " if you want the default 2D index. So if you manage said good, change index "
 "creation from:"
-msgstr "Einige ältere Anwendungen, die als Teil des Prozesses Tabellen und Indizes erstellen, referenzieren explizit den Operatorklassennamen. Dies war unnötig, falls Sie den Standard-2D-Index wollten. Falls Sie dies also gut hinbekommen möchten, ändern Sie die Indexerstellung von:"
+msgstr "Einige ältere Anwendungen, die als Teil des Prozesses Tabellen und Indizes erstellen, referenzieren explizit den Operatorklassennamen. Dies ist nicht nötig, wenn Sie den Standard-2D-Index wollten. Falls Sie dies erreichen möchten, ändern Sie die Indexerstellung von: "
 
 #. Tag: para
 #: faq.xml:42
@@ -146,7 +146,7 @@ msgstr "CREATE INDEX idx_my_table_geom ON my_table USING gist(geom);"
 msgid ""
 "The only case where you WILL need to specify the operator class is if you "
 "want a 3D spatial index as follows:"
-msgstr "Der einzige Fall, in dem Sie die Operatorklasse angeben MÜSSEN, ist, wenn Sie einen räumlichen 3D-Index wie folgt möchten:"
+msgstr "Der einzige Fall, in dem Sie die Operatorklasse angeben müssen, ist, wenn Sie einen räumlichen 3D-Index wie folgt möchten:"
 
 #. Tag: programlisting
 #: faq.xml:48
@@ -166,7 +166,7 @@ msgid ""
 "However if you use this fix, you are advised to at a later point drop the "
 "index and recreate it without the operator class. This will save you grief "
 "in the future when you need to upgrade again."
-msgstr "Falls Sie unglücklicherweise kompilierten Code, den Sie nicht mehr ändern können, am Hals haben und bei dem , bei dem altes »gist_geometry_ops« hart codiert ist, können Sie die alte Klasse mittels des in PostGIS 2.0.2+ paketierten <filename>legacy_gist.sql</filename> erstellen. Falls Sie jedoch diese Fehlerbehebung verwenden, wird Ihnen dringend empfohlen, zu einem späteren Zeitpunkt den Index zu löschen und ihn ohne die Operatorklasse neu zu erstellen. Dies wird Ihnen in der Zukunft, wenn Sie erneut ein Upgrade durchführen, Kummer ersparen."
+msgstr "Falls Sie unglücklicherweise kompilierten Code, den Sie nicht mehr ändern können, am Hals haben und bei dem altes »gist_geometry_ops« hart codiert ist, können Sie die alte Klasse mittels des in PostGIS 2.0.2+ paketierten <filename>legacy_gist.sql</filename> erstellen. Falls Sie jedoch diese Fehlerbehebung verwenden, wird Ihnen dringend empfohlen, zu einem späteren Zeitpunkt den Index zu löschen und ihn ohne die Operatorklasse neu zu erstellen. Dies wird Ihnen in Zukunft Probleme ersparen, wenn Sie erneut ein Upgrade durchführen müssen."
 
 #. Tag: para
 #: faq.xml:56
@@ -244,7 +244,7 @@ msgstr "PgAdmin zeigt bei großen Geometrien nichts an. Was ist der beste Weg, u
 msgid ""
 "-- this should return no records if all your geom fields are filled in\n"
 "SELECT somefield FROM mytable WHERE geom IS NULL;"
-msgstr "-- Diese Abfrage gibt keine Datenbankeinträge zurück, falls alle Geometriefelder ausgefüllt sind\nSELECT somefield FROM mytable WHERE geom IS NULL;"
+msgstr "-- Wenn alle Geometriefelder ausgefüllt sind, dann sollte diese Abfrage keine Datensätze zurückgeben \nSELECT somefield FROM mytable WHERE geom IS NULL;"
 
 #. Tag: programlisting
 #: faq.xml:87
@@ -253,7 +253,7 @@ msgid ""
 "-- To tell just how large your geometry is do a query of the form\n"
 "--which will tell you the most number of points you have in any of your geometry columns\n"
 "SELECT MAX(ST_NPoints(geom)) FROM sometable;"
-msgstr "-- Um nur mitzuteilen, wie groß Ihre Geometrie ist, führen Sie eine Abfrage in der folgenden Form aus.\n-- Sie wird Ihnen die Höchstzahl von Punkten mitteilen, die Sie in Ihren Geometriespalten haben.\nSELECT MAX(ST_NPoints(geom)) FROM sometable;"
+msgstr "-- Um lediglich die Größe einer Geometrie festzustellen, können Sie eine Abfrage in der folgenden Form ausführen.\n-- Sie wird Ihnen die Höchstzahl von Punkten mitteilen, die Sie in Ihren Geometriespalten haben.\nSELECT MAX(ST_NPoints(geom)) FROM sometable;"
 
 #. Tag: para
 #: faq.xml:93
@@ -282,7 +282,7 @@ msgstr "Sie können Punkte, Linien, Polygone, Objekte aus mehreren Punkten, Lini
 #: faq.xml:110
 #, no-c-format
 msgid "I'm all confused. Which data store should I use geometry or geography?"
-msgstr "Ich bin ganz verwirrt. Welchen Datenspeicher soll ich verwenden, »geometry« oder »geography«?"
+msgstr "Ich bin verwirrt. Welchen Datenspeicher soll ich verwenden, »geometry« oder »geography«?"
 
 #. Tag: para
 #: faq.xml:114
@@ -304,7 +304,7 @@ msgid ""
 "two types to gain the benefits of each. Refer to <xref "
 "linkend=\"PostGIS_TypeFunctionMatrix\"/> to see what is currently supported "
 "and what is not."
-msgstr "Kurze Antwort: »geography« ist ein neuer Datentyp, der große Bereiche von Distanzvermessungen unterstützt, die meisten Berechnungen damit sind derzeit langsamer als bei »geometry«. Falls Sie »geography« benutzen, müssen Sie nicht viel über flache Koordinatensysteme lernen. »geography« ist im Allgemeinen am besten, falls alles, was Sie interessiert, das Vermessen von Entfernungen und Längen ist und Sie Daten von überall in der Welt haben. Der Datentyp »geometry« ist ein alter Datentyp, den viel mehr Funktionen unterstützen, der eine größere Unterstützung von Werkzeugen Dritter genießt und mit dem Transaktionen generell schneller sind, manchmal um bis zum Zehnfachen schneller für große Geometrien. »geometry« ist die beste Wahl, wenn Sie sich in räumlichen Bezugssystemen sicher fühlen oder Sie mit lokalisierten Daten umgehen, bei denen alle Ihre Daten in ein einziges <link linkend=\"spatial_ref_sys\">räumliches Bezugssystem (spatial reference system/SRID)</link> passen oder falls Sie eine große Menge räumlicher Daten verarbeiten wollen. Hinweis: Es ist ziemlich einfach, einmalige Umwandlungen zwischen den zwei Typen vorzunehmen, um von den Vorteilen beider zu profitieren. Was derzeit unterstützt wird und was nicht, erfahren Sie unter <xref linkend=\"PostGIS_TypeFunctionMatrix\"/>."
+msgstr "Kurze Antwort: »geography« ist ein neuer Datentyp, der Distanzmessungen über weite Bereiche hinweg unterstützt; allerdings sind die meisten Berechnungen damit derzeit langsamer als bei »geometry«. Wenn Sie den Datentyp »geography« benutzen, dann müssen Sie nicht viel über ebene Koordinatenreferenzsysteme lernen. Der Datentyp »geography« ist im Allgemeinen dann am besten geeignet, wenn Sie weltweite Daten haben und Sie nur am Messen von Entfernungen und Längen interessiert sind. Der Datentyp »geometry« ist ein alter Datentyp, der von wesentlich mehr Funktionen unterstützt wird, der eine größere Unterstützung von Werkzeugen Dritter genießt und mit dem Transaktionen generell schneller sind; bei einer großen Geometrie manchmal bis zum Zehnfachen schneller. Der Datentyp »geometry« ist die beste Wahl, wenn Sie sich in räumlichen Bezugssystemen sicher fühlen oder Sie mit lokalen Daten arbeiten, bei denen alle Ihre Daten in ein einziges <link linkend=\"spatial_ref_sys\">räumliches Bezugssystem (spatial reference system/SRID)</link> passen oder falls Sie eine große Menge räumlicher Daten verarbeiten wollen. Hinweis: Es ist ziemlich einfach, einmalige Umwandlungen zwischen den zwei Typen vorzunehmen, um von den Vorteilen beider zu profitieren. Was derzeit unterstützt wird und was nicht, erfahren Sie unter <xref linkend=\"PostGIS_TypeFunctionMatrix\"/>."
 
 #. Tag: para
 #: faq.xml:125
@@ -362,9 +362,9 @@ msgstr "Für »geometry«: Verbinden Sie Ihre Datenbank mit <filename>psql</file
 #: faq.xml:156
 #, no-c-format
 msgid ""
-"CREATE TABLE gtest ( gid serial primary key, name varchar(20)\n"
-"        , geom geometry(LINESTRING) );"
-msgstr "CREATE TABLE gtest ( gid serial primary key, name varchar(20)\n        , geom geometry(LINESTRING) );"
+"CREATE TABLE gtest (id serial primary key, name varchar(20), geom "
+"geometry(LINESTRING));"
+msgstr "CREATE TABLE gtest (id serial primary key, name varchar(20), geom geometry(LINESTRING));"
 
 #. Tag: para
 #: faq.xml:158
@@ -733,7 +733,7 @@ msgstr "--zum Prüfen, ob die Anzahl der Geometrien wirklich leer ist\n
 msgid ""
 "When I do an ST_Intersects, it says my two geometries don't intersect when I"
 " KNOW THEY DO. What gives?"
-msgstr "Wenn ich ein ST_Intersects ausführe, sagt es, dass sich meine beiden Geometrien nicht überschneiden, obwohl ICH WEIẞ, DASS SIE DIES TUN. Was ist passiert?"
+msgstr "ST_Intersects ergibt, dass sich meine beiden geometrischen Objekte nicht überschneiden, obwohl ICH WEISS, DASS SIE DIES TUN. Was ist passiert?"
 
 #. Tag: para
 #: faq.xml:371