[mapserver-users] OSGeo Local Chapter (aka TCMUG) Meeting

[Basques, Bob (CI-StPaul)]

All,

I’m mailing out an early reminder on the next OSGeo Chapter (TCMUG) Meeting.  
I’ll send another out the week of, as usual.

This presentation by Howard is looking like something that is applicable to a 
lot of new data collecting that is going on in the area related to LIDAR 
presentation and storage.  There is limited space available so let me know via 
email (RSVP) if you plan on attending or want to bring someone along so we can 
plan for a larger space if needed.

Thanks

bobb


—

Meeting announce follows.:



OSGeo Local Chaptr (aka TCMUG) Meeting

Scheduled: Mar 13, 2019 at 4:30 PM to 6:00 PM

Location: DNR

500 Lafayette Rd

St Paul MN 55155-4025

All,


Had a nice meet up at Flat Earth last evening, new and old faces turned up.


https://www.dropbox.com/s/lghzs0qydt3swrw/20190213_180210.flatearth.jpg?dl=0


Next meeting  . . . at the DNR offices . . .


https://www.google.com/maps/d/u/0/viewer?mid=1mqasu9xzmjyQ7E9xhrJ_aaZqUBw=44.955733543794466%2C-93.08540166931152=19


. . . for a LIDAR presentation by Howard Bulter . . . then over to the Bulldog 
at 5:30 in Lowertown afterwards.


https://goo.gl/maps/v9PPjqjYL2U2


https://www.thebulldogmn.com/








BEGIN:VCALENDAR
CALSCALE:GREGORIAN
VERSION:2.0
X-WR-CALNAME:OSGeo Local Chaptr (aka TCMUG) Meeting
METHOD:PUBLISH
PRODID:-//Apple Inc.//Mac OS X 10.14//EN
BEGIN:VTIMEZONE
TZID:America/Chicago
BEGIN:DAYLIGHT
TZOFFSETFROM:-0600
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
DTSTART:20070311T02
TZNAME:CDT
TZOFFSETTO:-0500
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0500
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
DTSTART:20071104T02
TZNAME:CST
TZOFFSETTO:-0600
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
TRANSP:OPAQUE
DTEND;TZID=America/Chicago:20190313T18
X-APPLE-STRUCTURED-LOCATION;VALUE=URI;X-APPLE-RADIUS=55.78112916756053;X
 -TITLE=DNR\\n500 Lafayette Rd\\nSt Paul MN 55155-4025:geo:44.956138,-93.
 084209
UID:8CBE5B07-040B-4802-8655-32AC358106A6
DTSTAMP:20190216T031519Z
LOCATION:DNR\n500 Lafayette Rd\nSt Paul MN 55155-4025
DESCRIPTION:All\,\n\nHad a nice meet up at Flat Earth last evening\, new
  and old faces turned up.\n\nhttps://www.dropbox.com/s/lghzs0qydt3swrw/2
 0190213_180210.flatearth.jpg?dl=0\n\nNext meeting  . . . at the DNR offi
 ces . . .\n\nhttps://www.google.com/maps/d/u/0/viewer?mid=1mqasu9xzmjyQ7
 E9xhrJ_aaZqUBw=44.955733543794466%2C-93.08540166931152=19\n\nfor a 
 LIDAR presentation by Howard Bulter . . . then over to the Bulldog at 5:
 30 in Lowertown afterwards.\n\nhttps://goo.gl/maps/v9PPjqjYL2U2\n\nhttps
 ://www.thebulldogmn.com/\n\n\n
SEQUENCE:0
X-APPLE-TRAVEL-ADVISORY-BEHAVIOR:AUTOMATIC
SUMMARY:OSGeo Local Chaptr (aka TCMUG) Meeting
LAST-MODIFIED:20190214T192829Z
CREATED:20190214T191916Z
DTSTART;TZID=America/Chicago:20190313T163000
END:VEVENT
END:VCALENDAR
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] Is it possible to have a different width for a polygon outline in the legend than what is on the map?

[Mark Volz]

Hello,

Is it possible to have a different width for a polygon outline in the legend 
than what is on the map?  On a particular layer I am working on the polygon 
width on the map looks fine, however it is much too thick on the legend.  As a 
result I cannot see the color of the polygon in the legend.

[cid:image001.png@01D4D42C.39A0B530]


Thank You!

Sincerely,
Mark Volz, GISP
Lyon County GIS Coordinator

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Arc symbol.

[lars . schylberg]

Hi Marek,

This is a way of making arcs in Mapserver that is based on using VRTs and sql
The data source doesn't need to be in spatialite though. It can be a shapefile
or a CSV file or anything that gdal can handle.

Simon Mercier at Mapgears and I developed this for making litehouse circles
for Sea charts a couple of years ago. In the current version of the
SMAC-M project this is done with preprocessing in another way.

But I still like the idea that You can draw anything with sql.

I was going to make a small separate example this morning.
But I ran into some problems. It seems like my current gdal is not
compiled with a version of libspatialite that should use
librttopo instead of the lwgeom. In the version I used before I had the
sql function ST_project. In the version I had today on my machine and in some 
docker
containers I didn't. I guess I have to build a gdal-mapserver with
the right libspatialite and librttopo versions where I can do
these trix again some time.

Anyway this is the VRT file that can draw an arc in Mapserver.
The data source contains points in EPSG 4326 and we are drawing the arc
in EPSG 3857 in this case. valnmr is the radius and sectr1 and sectr2 are
starting and ending angles of the arc.

To use the vrt in mapserver you use:

 CONNECTION "arc.vrt"
 CONNECTIONTYPE OGR
 DATA "arc"

## arc.vrt #

 coastal.sqlite
 
 SELECT rcid,fidn,valnmr,sectr1,sectr2,colour,SIGGRP,SIGPER,HEIGHT,
 MakeArc(ST_X(Transform(Geometry,3857)),ST_Y(Transform(Geometry,3857)),
 GLength(Transform(MakeLine( MakePoint( X(Geometry), Y(Geometry),4326),
 ST_Project( MakePoint( X(Geometry), Y(Geometry), 4326 ),
 valnmr*1852/10, Radians( sectr1-180 ))),3857)),
 (180-(sectr2-90)),(180-(sectr1-90)),3857,2) AS geometry
 FROM lights_point
 WHERE sectr1 NOT NULL AND sectr2 NOT NULL AND sectr1!=0 AND sectr2!=360
 

###

If You would like to check what version of various libraries that You
have, You can use this VRT and run ogrinfo on it. E.g ogrinfo debug.vrt debug

# debug.vrt #
 
 
 coastal.sqlite
 
 select
 sqlite_version(),
 spatialite_version(),
 lwgeom_version(),
 geos_version(),
 proj4_version()
 FROM lights_point
 
 
# 

Have fun !

Lars Schylberg
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Help debugging PostGIS raster connection

[Jeff McKenna]

Great work Thomas!  thank you!  -jeff



On 2019-03-06 1:08 PM, Thomas Horner wrote:
These findings, along with my entire solution for querying rows of a 
table with a raster column based on timestamp in the WMS GET parameter, 
has been added to the MapServer wiki Tips and Tricks section which links 
to this page:


https://github.com/mapserver/mapserver/wiki/Raster-Layers:-GDAL-PostGISRaster-Tricks

Cheers
Thomas

On Wed, Mar 6, 2019 at 6:29 AM Jeff McKenna 
mailto:jmcke...@gatewaygeomatics.com>> 
wrote:


Great news Thomas.  I also think (for good karma) all of your steps and
hints for PGraster could be added to a new wiki page in the "Tricks,
Tips, and HowTos" section of https://github.com/mapserver/mapserver/wiki

(that way people don't have to troll through thousands of email
messages
to find your important tip)

thanks!

-jeff



On 2019-03-05 7:02 PM, Thomas Horner wrote:
 > Great!  Thanks Jeff.  Turns out it was the single quotes in other
parts
 > of the connection string...  Not sure why.  Possibly special
characters
 > in the password or username?  After removing them, I no longer have
 > connection issues.  With that being solved, removing the WHERE
clause at
 > least returns a blank image instead of an error.
 >
 > I then brought back the WHERE clause, which returned an error
despite
 > working in GDAL.
 > This WHERE clause returns a single raster result in GDAL with the
exact
 > same connection string as above:
 > gdalinfo "PG:.. where='timestamp=\'2019-03-05 00:00:00\''"
 >
 > However, no matter the combination of string literals, escape
 > characters, and whatnot, I could not get MapServer to handle this
clause
 > without error.
 >
 > But wait!  Enter Postgres's dollar-quoted string constants:
 > where='timestamp=$$2019-03-05 00:00:00$$'
 >
 > The DATA connection string now works.  Hope this helps anyone in
the future.
 >
 > Regards,
 > Thomas
 >
 > On Tue, Mar 5, 2019 at 3:24 PM Jeff McKenna
 > mailto:jmcke...@gatewaygeomatics.com>
>>
 > wrote:
 >
 >     Hi Thomas,
 >
 >     I would try the following:
 >
 >     - remove all single quotes from your DATA statement (most
times they
 >     are
 >     unnecessary for my use, and cause me problems)
 >     - remove the WHERE clause
 >     - also try to access another table from your database, but
not raster,
 >     using that same DATA connection statement (I bet the problem has
 >     nothing
 >     to do with the raster table, but instead is your connection
parameters)
 >     - verify that remote connections can access your database
(check your
 >     file pg_hba.conf)
 >
 >     hope that brings ideas and opens doors...
 >
 >     -jeff
 >
 >
 >
 >     --
 >     Jeff McKenna
 >     MapServer Consulting and Training Services
 > https://gatewaygeomatics.com/
 >
 >
 >     On 2019-03-04 2:38 PM, Thomas Horner wrote:
 >      > I have a PostGIS connection string that works fine in
GDAL, as I
 >     get a
 >      > raster response when running
 >      > ---
 >      > gdalinfo "PG:host=... port=5432 user='...' password='...'
 >      > dbname='weather_models' schema='rasters'
 >      > table='wpc_snow_50pct_1551268800' column='rast' mode=1
 >      > where='timestamp=\'2019-03-02 00:00:00\''"
 >      > ---
 >      >
 >      > On this very same server, I have cgi-mapserver running,
and the
 >     output
 >      > from /usr/lib/cgi-bin/mapserv/ -v is
 >      > ---
 >      > MapServer version 7.2.1 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML
 >     SUPPORTS=PROJ
 >      > SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO
SUPPORTS=SVG_SYMBOLS
 >      > SUPPORTS=RSVG SUPPORTS=ICONV SUPPORTS=FRIBIDI
SUPPORTS=WMS_SERVER
 >      > SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT
 >      > SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=FASTCGI
 >      > SUPPORTS=THREADS SUPPORTS=GEOS SUPPORTS=PBF INPUT=JPEG
INPUT=POSTGIS
 >      > INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE
 >      > ---
 >      >
 >      > The problem is, when I use that same PG:... connection
string as the
 >      > DATA for a LAYER in MapServer, I get an unhelpful error:
Unable to
 >      > access file. Corrupt, empty or missing file '      > string>' Couldn't establish a database connection.
 >      >
 >      > Despite turning DEBUG level to 5, and CPL_DEBUG to ON in
the MAP
 >     block
 >      > of my mapfile, I don't get any helpful debug information
 >     whatsoever in
 >      > my error log -- just the connection string and "Couldn't
establish a

Re: [mapserver-users] Help debugging PostGIS raster connection

[Thomas Horner]

These findings, along with my entire solution for querying rows of a table
with a raster column based on timestamp in the WMS GET parameter, has been
added to the MapServer wiki Tips and Tricks section which links to this
page:

https://github.com/mapserver/mapserver/wiki/Raster-Layers:-GDAL-PostGISRaster-Tricks

Cheers
Thomas

On Wed, Mar 6, 2019 at 6:29 AM Jeff McKenna 
wrote:

> Great news Thomas.  I also think (for good karma) all of your steps and
> hints for PGraster could be added to a new wiki page in the "Tricks,
> Tips, and HowTos" section of https://github.com/mapserver/mapserver/wiki
>
> (that way people don't have to troll through thousands of email messages
> to find your important tip)
>
> thanks!
>
> -jeff
>
>
>
> On 2019-03-05 7:02 PM, Thomas Horner wrote:
> > Great!  Thanks Jeff.  Turns out it was the single quotes in other parts
> > of the connection string...  Not sure why.  Possibly special characters
> > in the password or username?  After removing them, I no longer have
> > connection issues.  With that being solved, removing the WHERE clause at
> > least returns a blank image instead of an error.
> >
> > I then brought back the WHERE clause, which returned an error despite
> > working in GDAL.
> > This WHERE clause returns a single raster result in GDAL with the exact
> > same connection string as above:
> > gdalinfo "PG:.. where='timestamp=\'2019-03-05 00:00:00\''"
> >
> > However, no matter the combination of string literals, escape
> > characters, and whatnot, I could not get MapServer to handle this clause
> > without error.
> >
> > But wait!  Enter Postgres's dollar-quoted string constants:
> > where='timestamp=$$2019-03-05 00:00:00$$'
> >
> > The DATA connection string now works.  Hope this helps anyone in the
> future.
> >
> > Regards,
> > Thomas
> >
> > On Tue, Mar 5, 2019 at 3:24 PM Jeff McKenna
> > mailto:jmcke...@gatewaygeomatics.com>>
> > wrote:
> >
> > Hi Thomas,
> >
> > I would try the following:
> >
> > - remove all single quotes from your DATA statement (most times they
> > are
> > unnecessary for my use, and cause me problems)
> > - remove the WHERE clause
> > - also try to access another table from your database, but not
> raster,
> > using that same DATA connection statement (I bet the problem has
> > nothing
> > to do with the raster table, but instead is your connection
> parameters)
> > - verify that remote connections can access your database (check your
> > file pg_hba.conf)
> >
> > hope that brings ideas and opens doors...
> >
> > -jeff
> >
> >
> >
> > --
> > Jeff McKenna
> > MapServer Consulting and Training Services
> > https://gatewaygeomatics.com/
> >
> >
> > On 2019-03-04 2:38 PM, Thomas Horner wrote:
> >  > I have a PostGIS connection string that works fine in GDAL, as I
> > get a
> >  > raster response when running
> >  > ---
> >  > gdalinfo "PG:host=... port=5432 user='...' password='...'
> >  > dbname='weather_models' schema='rasters'
> >  > table='wpc_snow_50pct_1551268800' column='rast' mode=1
> >  > where='timestamp=\'2019-03-02 00:00:00\''"
> >  > ---
> >  >
> >  > On this very same server, I have cgi-mapserver running, and the
> > output
> >  > from /usr/lib/cgi-bin/mapserv/ -v is
> >  > ---
> >  > MapServer version 7.2.1 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML
> > SUPPORTS=PROJ
> >  > SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=SVG_SYMBOLS
> >  > SUPPORTS=RSVG SUPPORTS=ICONV SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER
> >  > SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT
> >  > SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=FASTCGI
> >  > SUPPORTS=THREADS SUPPORTS=GEOS SUPPORTS=PBF INPUT=JPEG
> INPUT=POSTGIS
> >  > INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE
> >  > ---
> >  >
> >  > The problem is, when I use that same PG:... connection string as
> the
> >  > DATA for a LAYER in MapServer, I get an unhelpful error: Unable to
> >  > access file. Corrupt, empty or missing file ' connection
> >  > string>' Couldn't establish a database connection.
> >  >
> >  > Despite turning DEBUG level to 5, and CPL_DEBUG to ON in the MAP
> > block
> >  > of my mapfile, I don't get any helpful debug information
> > whatsoever in
> >  > my error log -- just the connection string and "Couldn't
> establish a
> >  > database connection." I have tried a variety of where clauses and
> > other
> >  > tables and get the same result. I have no idea if the actual
> > error is
> >  > coming from GDAL or MapServer, despite all those strings working
> > fine
> >  > when running them directly via GDAL.
> >  >
> >  > By the way, it's the same error whether I use 'timestamp'= or
> > timestamp=.
> >  >
> >  > Here is the mapfile:
> >  > ---
> >  > MAP
> >  >   CONFIG "MS_ERRORFILE" "/map/error.txt"
> >  

Re: [mapserver-users] Arc symbol.

[Basques, Bob (CI-StPaul)]

Marek,

Landing your data into Postgres/PostGIS enables a bunch of capabilities.  
Combined with MapServer as an output/convertor, you can essentially filter to 
your hearts content as well as reproject to just about any EPSG code with Ease. 
 We’ve even added to the EPSG lists in PostGIS for our own, custom local 
coordinate system.

The benefits of using Postgis as a data staging (caching) area far outweigh the 
extra effort of adding the data in.

bobb



On Mar 5, 2019, at 2:30 PM, Marek Bąk 
mailto:rai...@poczta.onet.pl>> wrote:

Hello Bob,

It is not about data (the customer delivered data). It is about visualization. 
I have object to visualize - point (lat, lon) with degree range (min degree, 
max degree). The end user should see that object as an arc. There is support 
for ellipse/circle in mapserver SYMBOL but I did not found simply way to draw 
just part of cirle.

Regards,
Marek


W dniu 2019-03-05 o 20:49, Basques, Bob (CI-StPaul) pisze:
This is related more to what type of data you want/need to save the data in.  
Not all data formats understand Arc definitions.  Postgres for example does, as 
does AutoCAD (DXF).  The ESRI Rest services can (but I think it needs to be 
turned on from the server side.

bobb



On Mar 5, 2019, at 1:26 PM, Marek Bąk 
mailto:rai...@poczta.onet.pl>> wrote:


Hello All,

Is it possible to create an arc symbol im mapserver? For example I have two 
lines constructed over some angle (ex. 30 degree) and I want to draw an arc 
between them.

Regards,

Marek


___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users



Work like you don’t need money, love like you’ve never been hurt, and dance 
like no one’s watching
—Unknown Author





"A rocket will never be able to leave the earth's atmosphere."  --The New York 
Times, 1936

___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Error While Generating Tiles

[parsis presswala]

I have improve Postgresql configuration shared_buffer = 2 MB and
work_mem = 500 MB.
Is this configuration fine or I need to improve more?

On Wed, Mar 6, 2019 at 7:53 PM parsis presswala 
wrote:

> No, not yet.
>
> On Wed, Mar 6, 2019 at 7:49 PM Yves Jacolin 
> wrote:
>
>> Did you improve Postgresql configuration (shared_buffer and work_mem
>> parameters) ?
>>
>> Y.
>>
>> Le mer. 6 mars 2019 à 15:15, parsis presswala 
>> a écrit :
>>
>>> Hello,
>>>
>>> I have already created indexing on some fields. Here is my indexed
>>> fields.
>>> CREATE INDEX planet_osm_polygon_idx
>>>   ON public.planet_osm_polygon
>>>   USING btree
>>>   (waterway COLLATE pg_catalog."default", "natural" COLLATE
>>> pg_catalog."default", landuse COLLATE pg_catalog."default", building
>>> COLLATE pg_catalog."default", aeroway COLLATE pg_catalog."default", leisure
>>> COLLATE pg_catalog."default", amenity COLLATE pg_catalog."default");
>>>
>>> Even I have experiment with r4.8xlarge with 32 CPU and 244 GB RAM. But
>>> got same result.
>>> What should I do?
>>>
>>> On Wed, Mar 6, 2019 at 7:31 PM Yves Jacolin 
>>> wrote:
>>>
 You probablty needs to create index(es) on leisure, landuse and
 amenity. Probably both of all but you need to do some test.

 Second, you probably needs to improve PostgreSQL configuration to let
 PostgreSQL use your 61 GB of RAM :) shared_buffers and work_mem are good
 parameters to look for.

 Y.

 Le mer. 6 mars 2019 à 14:56, parsis presswala <
 parsispressw...@gmail.com> a écrit :

> Hello,
>
> Yes I am using OSM data.
> I have imported it using osm2pgsql. Database: asiadb and tables
> are planet_osm_line, planet_osm_point, planet_osm_polygon, 
> planet_osm_roads.
> I have imported data of whole planet using 40 GB .osm.pbf file.
> First I have only imported data of Asia and created map using
> map-server, which is working fine but as soon as import data of whole
> world, this problem occurred.
> I have 61 GB RAM and 8 Core processor as i am working on Amazon
> Elastic Compute Cloud (Amazon EC2) type r4.2xlarge.
>
> Here is my mapfile.
>  http://13.126.201.198/asiamap.map
>
> I have run EXPLAIN  and got following result:
> "Seq Scan on planet_osm_polygon  (cost=0.00..18878787.88 rows=36617920
> width=277)"
> "  Filter: ((leisure IS NOT NULL) OR (landuse IS NOT NULL) OR (amenity
> IS NOT NULL))"
>
>
> On Wed, Mar 6, 2019 at 7:04 PM Yves Jacolin <
> yves.jaco...@camptocamp.com> wrote:
>
>> Some questions that can help you :)
>>
>> is it OSM data? How do you import them?
>> What is the extent of the data? Could you check if spatial indexes
>> exist? Could you run EXPLAIN  and analyze it?
>>
>> Y.
>>
>> Le mer. 6 mars 2019 à 14:29, parsis presswala <
>> parsispressw...@gmail.com> a écrit :
>>
>>> Hello,
>>>
>>> Here is a log of PostgreSQL. I consider that PostgreSQL takes very
>>> long time to execute query on polygon. What should I do fot it?
>>>
>>> 2019-03-06 11:23:49.620 UTC [2302] parsis@asiadb STATEMENT:  select
>>> "highway"::text,"name"::text,"reflen"::text,"ref"::text,ST_AsBinary(ST_Force2D("way"),'NDR')
>>> as geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way,
>>> highway, name, ref, oneway, CHAR_LENGTH(ref) AS reflen FROM 
>>> planet_osm_line
>>> WHERE highway IN ('motorway', 'trunk','motorway_link','trunk_link') AND
>>> (name IS NOT NULL OR ref IS NOT NULL)) AS data) as nullidq where "way" 
>>> &&
>>> ST_GeomFromText('POLYGON((-9473834.25396072
>>> 2853929.66787328,-9473834.25396072 3446928.13330971,-8880835.78852428
>>> 3446928.13330971,-8880835.78852428 2853929.66787328,-9473834.25396072
>>> 2853929.66787328))',900913)
>>> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb LOG:  could not
>>> send data to client: Broken pipe
>>> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb STATEMENT:  select
>>> "stylegroup"::text,ST_AsBinary(ST_Force2D("way"),'NDR') as
>>> geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way, 
>>> CASE
>>> WHEN leisure in
>>> ('park','garden','playground','golf_course','sports_centre','pitch','stadium','nature_reserve','common')
>>> THEN 'leisuree' WHEN landuse
>>> IN('park','forest','grass','farmyard','farm','farmland','wood','meadow','village_green','recreation_ground')
>>> THEN 'landusee' WHEN amenity in
>>> ('university','school','college','library','fuel','parking','cinema','theatre','place_of_worship','hospital')
>>> THEN 'amenityy' END AS stylegroup FROM planet_osm_polygon where 
>>> (leisure is
>>> not null) or (landuse is not null) or (amenity is not null)) AS data) as
>>> nullidq where "way" && ST_GeomFromText('POLYGON((8116389.7548
>>> -1276192.28146022,8116389.7548 3467795.44203122,12860377.4777137

Re: [mapserver-users] Error While Generating Tiles

[parsis presswala]

No, not yet.

On Wed, Mar 6, 2019 at 7:49 PM Yves Jacolin 
wrote:

> Did you improve Postgresql configuration (shared_buffer and work_mem
> parameters) ?
>
> Y.
>
> Le mer. 6 mars 2019 à 15:15, parsis presswala 
> a écrit :
>
>> Hello,
>>
>> I have already created indexing on some fields. Here is my indexed fields.
>> CREATE INDEX planet_osm_polygon_idx
>>   ON public.planet_osm_polygon
>>   USING btree
>>   (waterway COLLATE pg_catalog."default", "natural" COLLATE
>> pg_catalog."default", landuse COLLATE pg_catalog."default", building
>> COLLATE pg_catalog."default", aeroway COLLATE pg_catalog."default", leisure
>> COLLATE pg_catalog."default", amenity COLLATE pg_catalog."default");
>>
>> Even I have experiment with r4.8xlarge with 32 CPU and 244 GB RAM. But
>> got same result.
>> What should I do?
>>
>> On Wed, Mar 6, 2019 at 7:31 PM Yves Jacolin 
>> wrote:
>>
>>> You probablty needs to create index(es) on leisure, landuse and amenity.
>>> Probably both of all but you need to do some test.
>>>
>>> Second, you probably needs to improve PostgreSQL configuration to let
>>> PostgreSQL use your 61 GB of RAM :) shared_buffers and work_mem are good
>>> parameters to look for.
>>>
>>> Y.
>>>
>>> Le mer. 6 mars 2019 à 14:56, parsis presswala 
>>> a écrit :
>>>
 Hello,

 Yes I am using OSM data.
 I have imported it using osm2pgsql. Database: asiadb and tables
 are planet_osm_line, planet_osm_point, planet_osm_polygon, 
 planet_osm_roads.
 I have imported data of whole planet using 40 GB .osm.pbf file.
 First I have only imported data of Asia and created map using
 map-server, which is working fine but as soon as import data of whole
 world, this problem occurred.
 I have 61 GB RAM and 8 Core processor as i am working on Amazon
 Elastic Compute Cloud (Amazon EC2) type r4.2xlarge.

 Here is my mapfile.
  http://13.126.201.198/asiamap.map

 I have run EXPLAIN  and got following result:
 "Seq Scan on planet_osm_polygon  (cost=0.00..18878787.88 rows=36617920
 width=277)"
 "  Filter: ((leisure IS NOT NULL) OR (landuse IS NOT NULL) OR (amenity
 IS NOT NULL))"


 On Wed, Mar 6, 2019 at 7:04 PM Yves Jacolin <
 yves.jaco...@camptocamp.com> wrote:

> Some questions that can help you :)
>
> is it OSM data? How do you import them?
> What is the extent of the data? Could you check if spatial indexes
> exist? Could you run EXPLAIN  and analyze it?
>
> Y.
>
> Le mer. 6 mars 2019 à 14:29, parsis presswala <
> parsispressw...@gmail.com> a écrit :
>
>> Hello,
>>
>> Here is a log of PostgreSQL. I consider that PostgreSQL takes very
>> long time to execute query on polygon. What should I do fot it?
>>
>> 2019-03-06 11:23:49.620 UTC [2302] parsis@asiadb STATEMENT:  select
>> "highway"::text,"name"::text,"reflen"::text,"ref"::text,ST_AsBinary(ST_Force2D("way"),'NDR')
>> as geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way,
>> highway, name, ref, oneway, CHAR_LENGTH(ref) AS reflen FROM 
>> planet_osm_line
>> WHERE highway IN ('motorway', 'trunk','motorway_link','trunk_link') AND
>> (name IS NOT NULL OR ref IS NOT NULL)) AS data) as nullidq where "way" &&
>> ST_GeomFromText('POLYGON((-9473834.25396072
>> 2853929.66787328,-9473834.25396072 3446928.13330971,-8880835.78852428
>> 3446928.13330971,-8880835.78852428 2853929.66787328,-9473834.25396072
>> 2853929.66787328))',900913)
>> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb LOG:  could not
>> send data to client: Broken pipe
>> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb STATEMENT:  select
>> "stylegroup"::text,ST_AsBinary(ST_Force2D("way"),'NDR') as
>> geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way, 
>> CASE
>> WHEN leisure in
>> ('park','garden','playground','golf_course','sports_centre','pitch','stadium','nature_reserve','common')
>> THEN 'leisuree' WHEN landuse
>> IN('park','forest','grass','farmyard','farm','farmland','wood','meadow','village_green','recreation_ground')
>> THEN 'landusee' WHEN amenity in
>> ('university','school','college','library','fuel','parking','cinema','theatre','place_of_worship','hospital')
>> THEN 'amenityy' END AS stylegroup FROM planet_osm_polygon where (leisure 
>> is
>> not null) or (landuse is not null) or (amenity is not null)) AS data) as
>> nullidq where "way" && ST_GeomFromText('POLYGON((8116389.7548
>> -1276192.28146022,8116389.7548 3467795.44203122,12860377.4777137
>> 3467795.44203122,12860377.4777137 -1276192.28146022,8116389.7548
>> -1276192.28146022))',900913)
>> 2019-03-06 11:24:14.911 UTC [2617] parsis@asiadb LOG:  could not
>> send data to client: Broken pipe
>> 2019-03-06 11:24:14.911 UTC [2617] parsis@asiadb STATEMENT:  select
>> 

Re: [mapserver-users] Error While Generating Tiles

[Yves Jacolin]

Did you improve Postgresql configuration (shared_buffer and work_mem
parameters) ?

Y.

Le mer. 6 mars 2019 à 15:15, parsis presswala  a
écrit :

> Hello,
>
> I have already created indexing on some fields. Here is my indexed fields.
> CREATE INDEX planet_osm_polygon_idx
>   ON public.planet_osm_polygon
>   USING btree
>   (waterway COLLATE pg_catalog."default", "natural" COLLATE
> pg_catalog."default", landuse COLLATE pg_catalog."default", building
> COLLATE pg_catalog."default", aeroway COLLATE pg_catalog."default", leisure
> COLLATE pg_catalog."default", amenity COLLATE pg_catalog."default");
>
> Even I have experiment with r4.8xlarge with 32 CPU and 244 GB RAM. But
> got same result.
> What should I do?
>
> On Wed, Mar 6, 2019 at 7:31 PM Yves Jacolin 
> wrote:
>
>> You probablty needs to create index(es) on leisure, landuse and amenity.
>> Probably both of all but you need to do some test.
>>
>> Second, you probably needs to improve PostgreSQL configuration to let
>> PostgreSQL use your 61 GB of RAM :) shared_buffers and work_mem are good
>> parameters to look for.
>>
>> Y.
>>
>> Le mer. 6 mars 2019 à 14:56, parsis presswala 
>> a écrit :
>>
>>> Hello,
>>>
>>> Yes I am using OSM data.
>>> I have imported it using osm2pgsql. Database: asiadb and tables
>>> are planet_osm_line, planet_osm_point, planet_osm_polygon, planet_osm_roads.
>>> I have imported data of whole planet using 40 GB .osm.pbf file.
>>> First I have only imported data of Asia and created map using
>>> map-server, which is working fine but as soon as import data of whole
>>> world, this problem occurred.
>>> I have 61 GB RAM and 8 Core processor as i am working on Amazon Elastic
>>> Compute Cloud (Amazon EC2) type r4.2xlarge.
>>>
>>> Here is my mapfile.
>>>  http://13.126.201.198/asiamap.map
>>>
>>> I have run EXPLAIN  and got following result:
>>> "Seq Scan on planet_osm_polygon  (cost=0.00..18878787.88 rows=36617920
>>> width=277)"
>>> "  Filter: ((leisure IS NOT NULL) OR (landuse IS NOT NULL) OR (amenity
>>> IS NOT NULL))"
>>>
>>>
>>> On Wed, Mar 6, 2019 at 7:04 PM Yves Jacolin 
>>> wrote:
>>>
 Some questions that can help you :)

 is it OSM data? How do you import them?
 What is the extent of the data? Could you check if spatial indexes
 exist? Could you run EXPLAIN  and analyze it?

 Y.

 Le mer. 6 mars 2019 à 14:29, parsis presswala <
 parsispressw...@gmail.com> a écrit :

> Hello,
>
> Here is a log of PostgreSQL. I consider that PostgreSQL takes very
> long time to execute query on polygon. What should I do fot it?
>
> 2019-03-06 11:23:49.620 UTC [2302] parsis@asiadb STATEMENT:  select
> "highway"::text,"name"::text,"reflen"::text,"ref"::text,ST_AsBinary(ST_Force2D("way"),'NDR')
> as geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way,
> highway, name, ref, oneway, CHAR_LENGTH(ref) AS reflen FROM 
> planet_osm_line
> WHERE highway IN ('motorway', 'trunk','motorway_link','trunk_link') AND
> (name IS NOT NULL OR ref IS NOT NULL)) AS data) as nullidq where "way" &&
> ST_GeomFromText('POLYGON((-9473834.25396072
> 2853929.66787328,-9473834.25396072 3446928.13330971,-8880835.78852428
> 3446928.13330971,-8880835.78852428 2853929.66787328,-9473834.25396072
> 2853929.66787328))',900913)
> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb LOG:  could not send
> data to client: Broken pipe
> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb STATEMENT:  select
> "stylegroup"::text,ST_AsBinary(ST_Force2D("way"),'NDR') as
> geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way, CASE
> WHEN leisure in
> ('park','garden','playground','golf_course','sports_centre','pitch','stadium','nature_reserve','common')
> THEN 'leisuree' WHEN landuse
> IN('park','forest','grass','farmyard','farm','farmland','wood','meadow','village_green','recreation_ground')
> THEN 'landusee' WHEN amenity in
> ('university','school','college','library','fuel','parking','cinema','theatre','place_of_worship','hospital')
> THEN 'amenityy' END AS stylegroup FROM planet_osm_polygon where (leisure 
> is
> not null) or (landuse is not null) or (amenity is not null)) AS data) as
> nullidq where "way" && ST_GeomFromText('POLYGON((8116389.7548
> -1276192.28146022,8116389.7548 3467795.44203122,12860377.4777137
> 3467795.44203122,12860377.4777137 -1276192.28146022,8116389.7548
> -1276192.28146022))',900913)
> 2019-03-06 11:24:14.911 UTC [2617] parsis@asiadb LOG:  could not send
> data to client: Broken pipe
> 2019-03-06 11:24:14.911 UTC [2617] parsis@asiadb STATEMENT:  select
> "stylegroup"::text,ST_AsBinary(ST_Force2D("way"),'NDR') as
> geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way, CASE
> WHEN leisure in
> ('park','garden','playground','golf_course','sports_centre','pitch','stadium','nature_reserve','common')
> 

Re: [mapserver-users] Arc symbol.

[Seth G]

Hi Marek,

I had a similar question last year - 
http://osgeo-org.1560.x6.nabble.com/Curves-in-MapServer-td5377180.html

You can add/draw CIRCULARSTRING geometries to MapServer using OGR - see the 
sample rainbow image at https://github.com/geographika/mappyfile-colors

The sample map file is: 
https://raw.githubusercontent.com/geographika/mappyfile-colors/master/example.map
This loads the following curved arcs from 
https://github.com/geographika/mappyfile-colors/blob/master/curves.csv

CONNECTIONTYPE OGR has to be used rather than using inline features as this 
approach defaults to using GEOS which doesn't support curves, whereas as 
forcing OGR does. 

Seth

--
web:http://geographika.co.uk
twitter: @geographika


On Wed, Mar 6, 2019, at 12:31 AM, Lime, Steve D (MNIT) wrote:
> Not within MapServer directly, at least not at first glance. There are circle 
> layers but there’s no way to limit drawing to just a specific arc on that 
> circle. Here are some other ideas:

> 

> 1) Perhaps it could be done externally in OGR or PostGIS and then rendered in 
> MapServer as a polygon or a line…

> 2) You could also take a look at using javascript geotransformations:  
> https://mapserver.org/mapfile/geomtransform.html#javascript-transformation 
> Support was added a while back and isn’t widely used but this is the sort of 
> thing it was added for. In theory you should be able to compute the arc 
> yourself and return it for rendering. So you pass in the 2 lines and then 
> return the arc as a line shape or a pie slice as a polygon shape. (maybe this 
> helps… 
> https://stackoverflow.com/questions/45009327/draw-arc-between-two-lines-i-need-to-calculate-points)

> 

> If option 2 works this would be a great thing to archive – a library of 
> geomtranforms. I might tinker with this tonight… ;-)

> 

> --Steve

> 

> *From:* mapserver-users [mailto:mapserver-users-boun...@lists.osgeo.org] *On 
> Behalf Of *Marek Bak
> *Sent:* Tuesday, March 05, 2019 1:27 PM
> *To:* mapserver-users@lists.osgeo.org
> *Subject:* [mapserver-users] Arc symbol.

> 

> Hello All,

> Is it possible to create an arc symbol im mapserver? For example I have two 
> lines constructed over some angle (ex. 30 degree) and I want to draw an arc 
> between them.

> Regards,

> Marek

> 

> ___
> mapserver-users mailing list
> mapserver-users@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Error While Generating Tiles

[parsis presswala]

Hello,

I have already created indexing on some fields. Here is my indexed fields.
CREATE INDEX planet_osm_polygon_idx
  ON public.planet_osm_polygon
  USING btree
  (waterway COLLATE pg_catalog."default", "natural" COLLATE
pg_catalog."default", landuse COLLATE pg_catalog."default", building
COLLATE pg_catalog."default", aeroway COLLATE pg_catalog."default", leisure
COLLATE pg_catalog."default", amenity COLLATE pg_catalog."default");

Even I have experiment with r4.8xlarge with 32 CPU and 244 GB RAM. But got
same result.
What should I do?

On Wed, Mar 6, 2019 at 7:31 PM Yves Jacolin 
wrote:

> You probablty needs to create index(es) on leisure, landuse and amenity.
> Probably both of all but you need to do some test.
>
> Second, you probably needs to improve PostgreSQL configuration to let
> PostgreSQL use your 61 GB of RAM :) shared_buffers and work_mem are good
> parameters to look for.
>
> Y.
>
> Le mer. 6 mars 2019 à 14:56, parsis presswala 
> a écrit :
>
>> Hello,
>>
>> Yes I am using OSM data.
>> I have imported it using osm2pgsql. Database: asiadb and tables
>> are planet_osm_line, planet_osm_point, planet_osm_polygon, planet_osm_roads.
>> I have imported data of whole planet using 40 GB .osm.pbf file.
>> First I have only imported data of Asia and created map using map-server,
>> which is working fine but as soon as import data of whole world, this
>> problem occurred.
>> I have 61 GB RAM and 8 Core processor as i am working on Amazon Elastic
>> Compute Cloud (Amazon EC2) type r4.2xlarge.
>>
>> Here is my mapfile.
>>  http://13.126.201.198/asiamap.map
>>
>> I have run EXPLAIN  and got following result:
>> "Seq Scan on planet_osm_polygon  (cost=0.00..18878787.88 rows=36617920
>> width=277)"
>> "  Filter: ((leisure IS NOT NULL) OR (landuse IS NOT NULL) OR (amenity IS
>> NOT NULL))"
>>
>>
>> On Wed, Mar 6, 2019 at 7:04 PM Yves Jacolin 
>> wrote:
>>
>>> Some questions that can help you :)
>>>
>>> is it OSM data? How do you import them?
>>> What is the extent of the data? Could you check if spatial indexes
>>> exist? Could you run EXPLAIN  and analyze it?
>>>
>>> Y.
>>>
>>> Le mer. 6 mars 2019 à 14:29, parsis presswala 
>>> a écrit :
>>>
 Hello,

 Here is a log of PostgreSQL. I consider that PostgreSQL takes very long
 time to execute query on polygon. What should I do fot it?

 2019-03-06 11:23:49.620 UTC [2302] parsis@asiadb STATEMENT:  select
 "highway"::text,"name"::text,"reflen"::text,"ref"::text,ST_AsBinary(ST_Force2D("way"),'NDR')
 as geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way,
 highway, name, ref, oneway, CHAR_LENGTH(ref) AS reflen FROM planet_osm_line
 WHERE highway IN ('motorway', 'trunk','motorway_link','trunk_link') AND
 (name IS NOT NULL OR ref IS NOT NULL)) AS data) as nullidq where "way" &&
 ST_GeomFromText('POLYGON((-9473834.25396072
 2853929.66787328,-9473834.25396072 3446928.13330971,-8880835.78852428
 3446928.13330971,-8880835.78852428 2853929.66787328,-9473834.25396072
 2853929.66787328))',900913)
 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb LOG:  could not send
 data to client: Broken pipe
 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb STATEMENT:  select
 "stylegroup"::text,ST_AsBinary(ST_Force2D("way"),'NDR') as
 geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way, CASE
 WHEN leisure in
 ('park','garden','playground','golf_course','sports_centre','pitch','stadium','nature_reserve','common')
 THEN 'leisuree' WHEN landuse
 IN('park','forest','grass','farmyard','farm','farmland','wood','meadow','village_green','recreation_ground')
 THEN 'landusee' WHEN amenity in
 ('university','school','college','library','fuel','parking','cinema','theatre','place_of_worship','hospital')
 THEN 'amenityy' END AS stylegroup FROM planet_osm_polygon where (leisure is
 not null) or (landuse is not null) or (amenity is not null)) AS data) as
 nullidq where "way" && ST_GeomFromText('POLYGON((8116389.7548
 -1276192.28146022,8116389.7548 3467795.44203122,12860377.4777137
 3467795.44203122,12860377.4777137 -1276192.28146022,8116389.7548
 -1276192.28146022))',900913)
 2019-03-06 11:24:14.911 UTC [2617] parsis@asiadb LOG:  could not send
 data to client: Broken pipe
 2019-03-06 11:24:14.911 UTC [2617] parsis@asiadb STATEMENT:  select
 "stylegroup"::text,ST_AsBinary(ST_Force2D("way"),'NDR') as
 geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way, CASE
 WHEN leisure in
 ('park','garden','playground','golf_course','sports_centre','pitch','stadium','nature_reserve','common')
 THEN 'leisuree' WHEN landuse
 IN('park','forest','grass','farmyard','farm','farmland','wood','meadow','village_green','recreation_ground')
 THEN 'landusee' WHEN amenity in
 ('university','school','college','library','fuel','parking','cinema','theatre','place_of_worship','hospital')
 THEN 

Re: [mapserver-users] Error While Generating Tiles

[Yves Jacolin]

You probablty needs to create index(es) on leisure, landuse and amenity.
Probably both of all but you need to do some test.

Second, you probably needs to improve PostgreSQL configuration to let
PostgreSQL use your 61 GB of RAM :) shared_buffers and work_mem are good
parameters to look for.

Y.

Le mer. 6 mars 2019 à 14:56, parsis presswala  a
écrit :

> Hello,
>
> Yes I am using OSM data.
> I have imported it using osm2pgsql. Database: asiadb and tables
> are planet_osm_line, planet_osm_point, planet_osm_polygon, planet_osm_roads.
> I have imported data of whole planet using 40 GB .osm.pbf file.
> First I have only imported data of Asia and created map using map-server,
> which is working fine but as soon as import data of whole world, this
> problem occurred.
> I have 61 GB RAM and 8 Core processor as i am working on Amazon Elastic
> Compute Cloud (Amazon EC2) type r4.2xlarge.
>
> Here is my mapfile.
>  http://13.126.201.198/asiamap.map
>
> I have run EXPLAIN  and got following result:
> "Seq Scan on planet_osm_polygon  (cost=0.00..18878787.88 rows=36617920
> width=277)"
> "  Filter: ((leisure IS NOT NULL) OR (landuse IS NOT NULL) OR (amenity IS
> NOT NULL))"
>
>
> On Wed, Mar 6, 2019 at 7:04 PM Yves Jacolin 
> wrote:
>
>> Some questions that can help you :)
>>
>> is it OSM data? How do you import them?
>> What is the extent of the data? Could you check if spatial indexes exist?
>> Could you run EXPLAIN  and analyze it?
>>
>> Y.
>>
>> Le mer. 6 mars 2019 à 14:29, parsis presswala 
>> a écrit :
>>
>>> Hello,
>>>
>>> Here is a log of PostgreSQL. I consider that PostgreSQL takes very long
>>> time to execute query on polygon. What should I do fot it?
>>>
>>> 2019-03-06 11:23:49.620 UTC [2302] parsis@asiadb STATEMENT:  select
>>> "highway"::text,"name"::text,"reflen"::text,"ref"::text,ST_AsBinary(ST_Force2D("way"),'NDR')
>>> as geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way,
>>> highway, name, ref, oneway, CHAR_LENGTH(ref) AS reflen FROM planet_osm_line
>>> WHERE highway IN ('motorway', 'trunk','motorway_link','trunk_link') AND
>>> (name IS NOT NULL OR ref IS NOT NULL)) AS data) as nullidq where "way" &&
>>> ST_GeomFromText('POLYGON((-9473834.25396072
>>> 2853929.66787328,-9473834.25396072 3446928.13330971,-8880835.78852428
>>> 3446928.13330971,-8880835.78852428 2853929.66787328,-9473834.25396072
>>> 2853929.66787328))',900913)
>>> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb LOG:  could not send
>>> data to client: Broken pipe
>>> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb STATEMENT:  select
>>> "stylegroup"::text,ST_AsBinary(ST_Force2D("way"),'NDR') as
>>> geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way, CASE
>>> WHEN leisure in
>>> ('park','garden','playground','golf_course','sports_centre','pitch','stadium','nature_reserve','common')
>>> THEN 'leisuree' WHEN landuse
>>> IN('park','forest','grass','farmyard','farm','farmland','wood','meadow','village_green','recreation_ground')
>>> THEN 'landusee' WHEN amenity in
>>> ('university','school','college','library','fuel','parking','cinema','theatre','place_of_worship','hospital')
>>> THEN 'amenityy' END AS stylegroup FROM planet_osm_polygon where (leisure is
>>> not null) or (landuse is not null) or (amenity is not null)) AS data) as
>>> nullidq where "way" && ST_GeomFromText('POLYGON((8116389.7548
>>> -1276192.28146022,8116389.7548 3467795.44203122,12860377.4777137
>>> 3467795.44203122,12860377.4777137 -1276192.28146022,8116389.7548
>>> -1276192.28146022))',900913)
>>> 2019-03-06 11:24:14.911 UTC [2617] parsis@asiadb LOG:  could not send
>>> data to client: Broken pipe
>>> 2019-03-06 11:24:14.911 UTC [2617] parsis@asiadb STATEMENT:  select
>>> "stylegroup"::text,ST_AsBinary(ST_Force2D("way"),'NDR') as
>>> geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way, CASE
>>> WHEN leisure in
>>> ('park','garden','playground','golf_course','sports_centre','pitch','stadium','nature_reserve','common')
>>> THEN 'leisuree' WHEN landuse
>>> IN('park','forest','grass','farmyard','farm','farmland','wood','meadow','village_green','recreation_ground')
>>> THEN 'landusee' WHEN amenity in
>>> ('university','school','college','library','fuel','parking','cinema','theatre','place_of_worship','hospital')
>>> THEN 'amenityy' END AS stylegroup FROM planet_osm_polygon where (leisure is
>>> not null) or (landuse is not null) or (amenity is not null)) AS data) as
>>> nullidq where "way" && ST_GeomFromText('POLYGON((8116389.7548
>>> -1276192.28146022,8116389.7548 3467795.44203122,12860377.4777137
>>> 3467795.44203122,12860377.4777137 -1276192.28146022,8116389.7548
>>> -1276192.28146022))',900913)
>>> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb FATAL:  connection to
>>> client lost
>>> 2019-03-06 12:08:25.564 UTC [3362] parsis@asiadb STATEMENT:  select
>>> ST_AsBinary(ST_Force2D("way"),'NDR') as geom,"nullid"::text from (select *,
>>> NULL as nullid from ( SELECT way FROM planet_osm_polygon 

Re: [mapserver-users] Error While Generating Tiles

[parsis presswala]

Hello,

Yes I am using OSM data.
I have imported it using osm2pgsql. Database: asiadb and tables
are planet_osm_line, planet_osm_point, planet_osm_polygon, planet_osm_roads.
I have imported data of whole planet using 40 GB .osm.pbf file.
First I have only imported data of Asia and created map using map-server,
which is working fine but as soon as import data of whole world, this
problem occurred.
I have 61 GB RAM and 8 Core processor as i am working on Amazon Elastic
Compute Cloud (Amazon EC2) type r4.2xlarge.

Here is my mapfile.
 http://13.126.201.198/asiamap.map

I have run EXPLAIN  and got following result:
"Seq Scan on planet_osm_polygon  (cost=0.00..18878787.88 rows=36617920
width=277)"
"  Filter: ((leisure IS NOT NULL) OR (landuse IS NOT NULL) OR (amenity IS
NOT NULL))"


On Wed, Mar 6, 2019 at 7:04 PM Yves Jacolin 
wrote:

> Some questions that can help you :)
>
> is it OSM data? How do you import them?
> What is the extent of the data? Could you check if spatial indexes exist?
> Could you run EXPLAIN  and analyze it?
>
> Y.
>
> Le mer. 6 mars 2019 à 14:29, parsis presswala 
> a écrit :
>
>> Hello,
>>
>> Here is a log of PostgreSQL. I consider that PostgreSQL takes very long
>> time to execute query on polygon. What should I do fot it?
>>
>> 2019-03-06 11:23:49.620 UTC [2302] parsis@asiadb STATEMENT:  select
>> "highway"::text,"name"::text,"reflen"::text,"ref"::text,ST_AsBinary(ST_Force2D("way"),'NDR')
>> as geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way,
>> highway, name, ref, oneway, CHAR_LENGTH(ref) AS reflen FROM planet_osm_line
>> WHERE highway IN ('motorway', 'trunk','motorway_link','trunk_link') AND
>> (name IS NOT NULL OR ref IS NOT NULL)) AS data) as nullidq where "way" &&
>> ST_GeomFromText('POLYGON((-9473834.25396072
>> 2853929.66787328,-9473834.25396072 3446928.13330971,-8880835.78852428
>> 3446928.13330971,-8880835.78852428 2853929.66787328,-9473834.25396072
>> 2853929.66787328))',900913)
>> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb LOG:  could not send
>> data to client: Broken pipe
>> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb STATEMENT:  select
>> "stylegroup"::text,ST_AsBinary(ST_Force2D("way"),'NDR') as
>> geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way, CASE
>> WHEN leisure in
>> ('park','garden','playground','golf_course','sports_centre','pitch','stadium','nature_reserve','common')
>> THEN 'leisuree' WHEN landuse
>> IN('park','forest','grass','farmyard','farm','farmland','wood','meadow','village_green','recreation_ground')
>> THEN 'landusee' WHEN amenity in
>> ('university','school','college','library','fuel','parking','cinema','theatre','place_of_worship','hospital')
>> THEN 'amenityy' END AS stylegroup FROM planet_osm_polygon where (leisure is
>> not null) or (landuse is not null) or (amenity is not null)) AS data) as
>> nullidq where "way" && ST_GeomFromText('POLYGON((8116389.7548
>> -1276192.28146022,8116389.7548 3467795.44203122,12860377.4777137
>> 3467795.44203122,12860377.4777137 -1276192.28146022,8116389.7548
>> -1276192.28146022))',900913)
>> 2019-03-06 11:24:14.911 UTC [2617] parsis@asiadb LOG:  could not send
>> data to client: Broken pipe
>> 2019-03-06 11:24:14.911 UTC [2617] parsis@asiadb STATEMENT:  select
>> "stylegroup"::text,ST_AsBinary(ST_Force2D("way"),'NDR') as
>> geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way, CASE
>> WHEN leisure in
>> ('park','garden','playground','golf_course','sports_centre','pitch','stadium','nature_reserve','common')
>> THEN 'leisuree' WHEN landuse
>> IN('park','forest','grass','farmyard','farm','farmland','wood','meadow','village_green','recreation_ground')
>> THEN 'landusee' WHEN amenity in
>> ('university','school','college','library','fuel','parking','cinema','theatre','place_of_worship','hospital')
>> THEN 'amenityy' END AS stylegroup FROM planet_osm_polygon where (leisure is
>> not null) or (landuse is not null) or (amenity is not null)) AS data) as
>> nullidq where "way" && ST_GeomFromText('POLYGON((8116389.7548
>> -1276192.28146022,8116389.7548 3467795.44203122,12860377.4777137
>> 3467795.44203122,12860377.4777137 -1276192.28146022,8116389.7548
>> -1276192.28146022))',900913)
>> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb FATAL:  connection to
>> client lost
>> 2019-03-06 12:08:25.564 UTC [3362] parsis@asiadb STATEMENT:  select
>> ST_AsBinary(ST_Force2D("way"),'NDR') as geom,"nullid"::text from (select *,
>> NULL as nullid from ( SELECT way FROM planet_osm_polygon WHERE (waterway IN
>> ('riverbank')) OR ("natural" IN ('water')) OR (landuse IN ('basin',
>> 'reservoir')) ) AS data) as nullidq where "way" &&
>> ST_GeomFromText('POLYGON((-20228294.8225998
>> -20228294.8225998,-20228294.8225998 17723606.9653297,17723606.9653297
>> 17723606.9653297,17723606.9653297 -20228294.8225998,-20228294.8225998
>> -20228294.8225998))',900913)
>> 2019-03-06 12:08:25.564 UTC [3260] FATAL:  terminating connection due to
>> administrator 

Re: [mapserver-users] Error While Generating Tiles

[Yves Jacolin]

Some questions that can help you :)

is it OSM data? How do you import them?
What is the extent of the data? Could you check if spatial indexes exist?
Could you run EXPLAIN  and analyze it?

Y.

Le mer. 6 mars 2019 à 14:29, parsis presswala  a
écrit :

> Hello,
>
> Here is a log of PostgreSQL. I consider that PostgreSQL takes very long
> time to execute query on polygon. What should I do fot it?
>
> 2019-03-06 11:23:49.620 UTC [2302] parsis@asiadb STATEMENT:  select
> "highway"::text,"name"::text,"reflen"::text,"ref"::text,ST_AsBinary(ST_Force2D("way"),'NDR')
> as geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way,
> highway, name, ref, oneway, CHAR_LENGTH(ref) AS reflen FROM planet_osm_line
> WHERE highway IN ('motorway', 'trunk','motorway_link','trunk_link') AND
> (name IS NOT NULL OR ref IS NOT NULL)) AS data) as nullidq where "way" &&
> ST_GeomFromText('POLYGON((-9473834.25396072
> 2853929.66787328,-9473834.25396072 3446928.13330971,-8880835.78852428
> 3446928.13330971,-8880835.78852428 2853929.66787328,-9473834.25396072
> 2853929.66787328))',900913)
> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb LOG:  could not send
> data to client: Broken pipe
> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb STATEMENT:  select
> "stylegroup"::text,ST_AsBinary(ST_Force2D("way"),'NDR') as
> geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way, CASE
> WHEN leisure in
> ('park','garden','playground','golf_course','sports_centre','pitch','stadium','nature_reserve','common')
> THEN 'leisuree' WHEN landuse
> IN('park','forest','grass','farmyard','farm','farmland','wood','meadow','village_green','recreation_ground')
> THEN 'landusee' WHEN amenity in
> ('university','school','college','library','fuel','parking','cinema','theatre','place_of_worship','hospital')
> THEN 'amenityy' END AS stylegroup FROM planet_osm_polygon where (leisure is
> not null) or (landuse is not null) or (amenity is not null)) AS data) as
> nullidq where "way" && ST_GeomFromText('POLYGON((8116389.7548
> -1276192.28146022,8116389.7548 3467795.44203122,12860377.4777137
> 3467795.44203122,12860377.4777137 -1276192.28146022,8116389.7548
> -1276192.28146022))',900913)
> 2019-03-06 11:24:14.911 UTC [2617] parsis@asiadb LOG:  could not send
> data to client: Broken pipe
> 2019-03-06 11:24:14.911 UTC [2617] parsis@asiadb STATEMENT:  select
> "stylegroup"::text,ST_AsBinary(ST_Force2D("way"),'NDR') as
> geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way, CASE
> WHEN leisure in
> ('park','garden','playground','golf_course','sports_centre','pitch','stadium','nature_reserve','common')
> THEN 'leisuree' WHEN landuse
> IN('park','forest','grass','farmyard','farm','farmland','wood','meadow','village_green','recreation_ground')
> THEN 'landusee' WHEN amenity in
> ('university','school','college','library','fuel','parking','cinema','theatre','place_of_worship','hospital')
> THEN 'amenityy' END AS stylegroup FROM planet_osm_polygon where (leisure is
> not null) or (landuse is not null) or (amenity is not null)) AS data) as
> nullidq where "way" && ST_GeomFromText('POLYGON((8116389.7548
> -1276192.28146022,8116389.7548 3467795.44203122,12860377.4777137
> 3467795.44203122,12860377.4777137 -1276192.28146022,8116389.7548
> -1276192.28146022))',900913)
> 2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb FATAL:  connection to
> client lost
> 2019-03-06 12:08:25.564 UTC [3362] parsis@asiadb STATEMENT:  select
> ST_AsBinary(ST_Force2D("way"),'NDR') as geom,"nullid"::text from (select *,
> NULL as nullid from ( SELECT way FROM planet_osm_polygon WHERE (waterway IN
> ('riverbank')) OR ("natural" IN ('water')) OR (landuse IN ('basin',
> 'reservoir')) ) AS data) as nullidq where "way" &&
> ST_GeomFromText('POLYGON((-20228294.8225998
> -20228294.8225998,-20228294.8225998 17723606.9653297,17723606.9653297
> 17723606.9653297,17723606.9653297 -20228294.8225998,-20228294.8225998
> -20228294.8225998))',900913)
> 2019-03-06 12:08:25.564 UTC [3260] FATAL:  terminating connection due to
> administrator command
> 2019-03-06 12:08:25.564 UTC [3260] STATEMENT:  select
> ST_AsBinary(ST_Force2D("way"),'NDR') as geom,"nullid"::text from (select *,
> NULL as nullid from ( SELECT way FROM planet_osm_polygon WHERE (waterway IN
> ('riverbank')) OR ("natural" IN ('water')) OR (landuse IN ('basin',
> 'reservoir')) ) AS data) as nullidq where "way" &&
> ST_GeomFromText('POLYGON((-20228294.8225998
> -20228294.8225998,-20228294.8225998 17723606.9653297,17723606.9653297
> 17723606.9653297,17723606.9653297 -20228294.8225998,-20228294.8225998
> -20228294.8225998))',900913)
> 2019-03-06 12:08:25.564 UTC [3261] FATAL:  terminating connection due to
> administrator command
> 2019-03-06 12:08:25.564 UTC [3261] STATEMENT:  select
> ST_AsBinary(ST_Force2D("way"),'NDR') as geom,"nullid"::text from (select *,
> NULL as nullid from ( SELECT way FROM planet_osm_polygon WHERE (waterway IN
> ('riverbank')) OR ("natural" IN ('water')) OR 

Re: [mapserver-users] Error While Generating Tiles

[parsis presswala]

Hello,

Here is a log of PostgreSQL. I consider that PostgreSQL takes very long
time to execute query on polygon. What should I do fot it?

2019-03-06 11:23:49.620 UTC [2302] parsis@asiadb STATEMENT:  select
"highway"::text,"name"::text,"reflen"::text,"ref"::text,ST_AsBinary(ST_Force2D("way"),'NDR')
as geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way,
highway, name, ref, oneway, CHAR_LENGTH(ref) AS reflen FROM planet_osm_line
WHERE highway IN ('motorway', 'trunk','motorway_link','trunk_link') AND
(name IS NOT NULL OR ref IS NOT NULL)) AS data) as nullidq where "way" &&
ST_GeomFromText('POLYGON((-9473834.25396072
2853929.66787328,-9473834.25396072 3446928.13330971,-8880835.78852428
3446928.13330971,-8880835.78852428 2853929.66787328,-9473834.25396072
2853929.66787328))',900913)
2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb LOG:  could not send data
to client: Broken pipe
2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb STATEMENT:  select
"stylegroup"::text,ST_AsBinary(ST_Force2D("way"),'NDR') as
geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way, CASE
WHEN leisure in
('park','garden','playground','golf_course','sports_centre','pitch','stadium','nature_reserve','common')
THEN 'leisuree' WHEN landuse
IN('park','forest','grass','farmyard','farm','farmland','wood','meadow','village_green','recreation_ground')
THEN 'landusee' WHEN amenity in
('university','school','college','library','fuel','parking','cinema','theatre','place_of_worship','hospital')
THEN 'amenityy' END AS stylegroup FROM planet_osm_polygon where (leisure is
not null) or (landuse is not null) or (amenity is not null)) AS data) as
nullidq where "way" && ST_GeomFromText('POLYGON((8116389.7548
-1276192.28146022,8116389.7548 3467795.44203122,12860377.4777137
3467795.44203122,12860377.4777137 -1276192.28146022,8116389.7548
-1276192.28146022))',900913)
2019-03-06 11:24:14.911 UTC [2617] parsis@asiadb LOG:  could not send data
to client: Broken pipe
2019-03-06 11:24:14.911 UTC [2617] parsis@asiadb STATEMENT:  select
"stylegroup"::text,ST_AsBinary(ST_Force2D("way"),'NDR') as
geom,"nullid"::text from (select *, NULL as nullid from ( SELECT way, CASE
WHEN leisure in
('park','garden','playground','golf_course','sports_centre','pitch','stadium','nature_reserve','common')
THEN 'leisuree' WHEN landuse
IN('park','forest','grass','farmyard','farm','farmland','wood','meadow','village_green','recreation_ground')
THEN 'landusee' WHEN amenity in
('university','school','college','library','fuel','parking','cinema','theatre','place_of_worship','hospital')
THEN 'amenityy' END AS stylegroup FROM planet_osm_polygon where (leisure is
not null) or (landuse is not null) or (amenity is not null)) AS data) as
nullidq where "way" && ST_GeomFromText('POLYGON((8116389.7548
-1276192.28146022,8116389.7548 3467795.44203122,12860377.4777137
3467795.44203122,12860377.4777137 -1276192.28146022,8116389.7548
-1276192.28146022))',900913)
2019-03-06 11:24:14.911 UTC [2592] parsis@asiadb FATAL:  connection to
client lost
2019-03-06 12:08:25.564 UTC [3362] parsis@asiadb STATEMENT:  select
ST_AsBinary(ST_Force2D("way"),'NDR') as geom,"nullid"::text from (select *,
NULL as nullid from ( SELECT way FROM planet_osm_polygon WHERE (waterway IN
('riverbank')) OR ("natural" IN ('water')) OR (landuse IN ('basin',
'reservoir')) ) AS data) as nullidq where "way" &&
ST_GeomFromText('POLYGON((-20228294.8225998
-20228294.8225998,-20228294.8225998 17723606.9653297,17723606.9653297
17723606.9653297,17723606.9653297 -20228294.8225998,-20228294.8225998
-20228294.8225998))',900913)
2019-03-06 12:08:25.564 UTC [3260] FATAL:  terminating connection due to
administrator command
2019-03-06 12:08:25.564 UTC [3260] STATEMENT:  select
ST_AsBinary(ST_Force2D("way"),'NDR') as geom,"nullid"::text from (select *,
NULL as nullid from ( SELECT way FROM planet_osm_polygon WHERE (waterway IN
('riverbank')) OR ("natural" IN ('water')) OR (landuse IN ('basin',
'reservoir')) ) AS data) as nullidq where "way" &&
ST_GeomFromText('POLYGON((-20228294.8225998
-20228294.8225998,-20228294.8225998 17723606.9653297,17723606.9653297
17723606.9653297,17723606.9653297 -20228294.8225998,-20228294.8225998
-20228294.8225998))',900913)
2019-03-06 12:08:25.564 UTC [3261] FATAL:  terminating connection due to
administrator command
2019-03-06 12:08:25.564 UTC [3261] STATEMENT:  select
ST_AsBinary(ST_Force2D("way"),'NDR') as geom,"nullid"::text from (select *,
NULL as nullid from ( SELECT way FROM planet_osm_polygon WHERE (waterway IN
('riverbank')) OR ("natural" IN ('water')) OR (landuse IN ('basin',
'reservoir')) ) AS data) as nullidq where "way" &&
ST_GeomFromText('POLYGON((-20228294.8225998
-20228294.8225998,-20228294.8225998 17723606.9653297,17723606.9653297
17723606.9653297,17723606.9653297 -20228294.8225998,-20228294.8225998
-20228294.8225998))',900913)
2019-03-06 12:08:25.564 UTC [3363] FATAL:  terminating connection due to
administrator command
2019-03-06 12:08:25.564 UTC 

Re: [mapserver-users] Help debugging PostGIS raster connection

[Jeff McKenna]

Great news Thomas.  I also think (for good karma) all of your steps and 
hints for PGraster could be added to a new wiki page in the "Tricks, 
Tips, and HowTos" section of https://github.com/mapserver/mapserver/wiki


(that way people don't have to troll through thousands of email messages 
to find your important tip)


thanks!

-jeff



On 2019-03-05 7:02 PM, Thomas Horner wrote:
Great!  Thanks Jeff.  Turns out it was the single quotes in other parts 
of the connection string...  Not sure why.  Possibly special characters 
in the password or username?  After removing them, I no longer have 
connection issues.  With that being solved, removing the WHERE clause at 
least returns a blank image instead of an error.


I then brought back the WHERE clause, which returned an error despite 
working in GDAL.
This WHERE clause returns a single raster result in GDAL with the exact 
same connection string as above:

gdalinfo "PG:.. where='timestamp=\'2019-03-05 00:00:00\''"

However, no matter the combination of string literals, escape 
characters, and whatnot, I could not get MapServer to handle this clause 
without error.


But wait!  Enter Postgres's dollar-quoted string constants:
where='timestamp=$$2019-03-05 00:00:00$$'

The DATA connection string now works.  Hope this helps anyone in the future.

Regards,
Thomas

On Tue, Mar 5, 2019 at 3:24 PM Jeff McKenna 
mailto:jmcke...@gatewaygeomatics.com>> 
wrote:


Hi Thomas,

I would try the following:

- remove all single quotes from your DATA statement (most times they
are
unnecessary for my use, and cause me problems)
- remove the WHERE clause
- also try to access another table from your database, but not raster,
using that same DATA connection statement (I bet the problem has
nothing
to do with the raster table, but instead is your connection parameters)
- verify that remote connections can access your database (check your
file pg_hba.conf)

hope that brings ideas and opens doors...

-jeff



-- 
Jeff McKenna

MapServer Consulting and Training Services
https://gatewaygeomatics.com/


On 2019-03-04 2:38 PM, Thomas Horner wrote:
 > I have a PostGIS connection string that works fine in GDAL, as I
get a
 > raster response when running
 > ---
 > gdalinfo "PG:host=... port=5432 user='...' password='...'
 > dbname='weather_models' schema='rasters'
 > table='wpc_snow_50pct_1551268800' column='rast' mode=1
 > where='timestamp=\'2019-03-02 00:00:00\''"
 > ---
 >
 > On this very same server, I have cgi-mapserver running, and the
output
 > from /usr/lib/cgi-bin/mapserv/ -v is
 > ---
 > MapServer version 7.2.1 OUTPUT=PNG OUTPUT=JPEG OUTPUT=KML
SUPPORTS=PROJ
 > SUPPORTS=AGG SUPPORTS=FREETYPE SUPPORTS=CAIRO SUPPORTS=SVG_SYMBOLS
 > SUPPORTS=RSVG SUPPORTS=ICONV SUPPORTS=FRIBIDI SUPPORTS=WMS_SERVER
 > SUPPORTS=WMS_CLIENT SUPPORTS=WFS_SERVER SUPPORTS=WFS_CLIENT
 > SUPPORTS=WCS_SERVER SUPPORTS=SOS_SERVER SUPPORTS=FASTCGI
 > SUPPORTS=THREADS SUPPORTS=GEOS SUPPORTS=PBF INPUT=JPEG INPUT=POSTGIS
 > INPUT=OGR INPUT=GDAL INPUT=SHAPEFILE
 > ---
 >
 > The problem is, when I use that same PG:... connection string as the
 > DATA for a LAYER in MapServer, I get an unhelpful error: Unable to
 > access file. Corrupt, empty or missing file ' string>' Couldn't establish a database connection.
 >
 > Despite turning DEBUG level to 5, and CPL_DEBUG to ON in the MAP
block
 > of my mapfile, I don't get any helpful debug information
whatsoever in
 > my error log -- just the connection string and "Couldn't establish a
 > database connection." I have tried a variety of where clauses and
other
 > tables and get the same result. I have no idea if the actual
error is
 > coming from GDAL or MapServer, despite all those strings working
fine
 > when running them directly via GDAL.
 >
 > By the way, it's the same error whether I use 'timestamp'= or
timestamp=.
 >
 > Here is the mapfile:
 > ---
 > MAP
 >   CONFIG "MS_ERRORFILE" "/map/error.txt"
 >   CONFIG "CPL_DEBUG" "ON"
 >   DEBUG 5
 >   PROJECTION
 >    "init=epsg:4326"
 >   END
 >   LAYER
 >    NAME wpc_snow_50pct
 >    TYPE RASTER
 >    STATUS ON
 >    VALIDATION
 >     "timestamp" ".*"
 >    END
 >    PROJECTION
 >     "init=epsg:4326"
 >    END
 >    METADATA
 >     "wms_title" "wpc_snow_50pct"
 >     "wms_srs"   "EPSG:4326"
 >     "wms_extent" "-108.5 41 -104.5 36"
 >     "wms_enable_request" "*"
 >    END
 >    DATA "PG:host=... port=5432 dbname='weather_models' user='...'
 > password='...' schema='rasters' table='wpc_snow_50pct_1551268800'
 > column='rast' mode=1 where='timestamp=\'2019-03-02 00:00:00\''"
 >    PROCESSING "BANDS=1"
 >   END
 > END
 > ---
 >
 > Any help is 

Re: [mapserver-users] Error While Generating Tiles

[Yves Jacolin]

Hello,

Did you try to curl the request and see what happens: timeout, etc. If so,
try to get some log (mapserver or postgresql log) and see where is the
bottleneck.

Y.

Le mer. 6 mars 2019 à 13:58, parsis presswala  a
écrit :

> Hello,
> I am getting following error while generating tiles. I can't get the
> reason of this error. I an using mapcache to generate tiles.
>
> failed to seed tile z10,x645,y510:
> curl failed to request url
> http://13.126.201.198/cgi-bin/mapserv?VERSION=1.1.1=GetMap=WMS==5201998.739765%2c-81328.655306%2c5795150.079258%2c511822.684187=3880=3880=image%2fpng=EPSG%3a3857=osm_new_admin%2cosm_new_adminocean%2cosm_new_landusages%2cosm_new_water%2cbuildings%2caeroway%2cosm_new_waterways%2cosm_new_railways%2cplanet_osm_roads%2cplanet_osm_roads_line%2cosm_new_railways1%2ccountry_line%2ccountry_line_claim%2cstate_line%2cmotorway_label%2cmainroad_label%2cminorroad_label%2cosm_new_railways_symbol%2cplace-country%2cplace-state%2cplace-city%2cplace-town%2cplace-Suburb%2cplace-village%2cplace-locality%2carea_label%2caerodrome_label%2cwaterway_label%2cwaterarea_label%2cpoi_pointlabel=%2fhome%2fubuntu%2fworldmap%2fasiamap.map
> : Operation timed out after 60 milliseconds with 0 bytes received
>
> aborting seed as 100.0% of the last 1000 requests failed
>
> seeded 225 tiles, now at z10 x660 y510
> seeded 2 metatiles (450 total tiles, 450 non-empty tiles) in 1201.8
> seconds at 0.4 tiles/sec (0.4 non-empty tiles/sec)
>
> If anyone could help me with this, it would be greatly appreciated.
>
> Regards,
> Parsis Presswala
> ___
> mapserver-users mailing list
> mapserver-users@lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/mapserver-users



-- 
Yves Jacolin
Training and support manager - Team Manager
Camptocamp

Tel (France) : +33 4 58 48 20 43
Tel (Switzerland) : +41 21 619 10 43
Mob. : +33 6 18 75 42 21

email : yves.jaco...@camptocamp.com
http://www.camptocamp.com
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/mapserver-users