[MapServer-users] TinyOWS 1.2.1 released

[Jeff McKenna via MapServer-users]

The MapServer team is pleased to announce the minor release of TinyOWS 
1.2.1, in honor of its visionary, Olivier Courtin.


 - Changelog: 
https://mapserver.org/development/changelog/tinyows/changelog-1-2.html#changelog-tinyows-1-2

 - Download: https://download.osgeo.org/mapserver/tinyows-1.2.1.tar.gz

(TinyOWS 1.2.1 was tested successfully with MS4W 5.0 and PostreSQL 16.3 
/ PostGIS 3.4.2)


Thanks, and thoughts for Olivier...

--
The MapServer / TinyOWS Team




















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

[mapserver-users] TinyOWS 1.2.0 released

[Jeff McKenna via mapserver-users]

The MapServer team is pleased to announce the major release of TinyOWS 
1.2.0, in honor of its visionary, Olivier Courtin.


This release contains many fixes and enhancements that have been in the 
main branch, as well as recent improvements.  The goal will to follow a 
consistent release schedule, with a maintenance release in a few months 
from now.


(TinyOWS runs very well with PostreSQL 13 / PostGIS 3.1.1)

Changelog: 
https://mapserver.org/development/changelog/tinyows/changelog-1-2.html#changelog-tinyows-1-2

Download: https://download.osgeo.org/mapserver/tinyows-1.2.0.tar.gz

Thanks, and thoughts for Olivier...

--
The MapServer / TinyOWS Team










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

Re: [mapserver-users] tinyows does not show vector layer

[Jeff McKenna]

To followup on the other comments and Jukka's recommendation: you can 
set specific parameters for your FastCGI use - in the case of MS4W, we 
use the Apache module named 'mod_fcgi', and you can set its parameters 
in Apache's 'httpd.conf' file: for a list of these parameters see 
http://httpd.apache.org/mod_fcgid/mod/mod_fcgid.html


An example setting to limit the maximum time a process is running/alive 
to 10 seconds:


  FcgidProcessLifeTime 10


-jeff



--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/





On 2016-04-13 4:12 AM, Rahkonen Jukka (MML) wrote:

Hi ,

You could have mentioned that you have asked the same question in
gis.stackexchange
http://gis.stackexchange.com/questions/189102/tinyows-does-not-show-vector-layer
. Reading the comments may help Mapserver users to give you a better
answer and faster.

-Jukka Rahkonen-

vineet singh wrote:

Hi Everyone,

I'm using tinyows server configured with config.xml file. I'm adding
vector layer to config file and for the first time it does not show
newly added layer, but once i have restarted the tinyows server than it
will show the layer.

So i have to restart tinyows after adding new layer. Anyone know how can
I fix this so that it will work without restarting.

I'm runing TinyOWS as fast-cgi.

Here is config.xml :

http://192.168.0.35:19090/maps;
schema_dir="/home/vineet/Project/mygis/data/schema">





mailto:cont...@.com>" name="MyGis
Server" site="http://www.x.com/"/>

http://www.vizexperts.com/;
  name="world_boundaries"

  title="World Borders" />

  

Thanks,

Vineet Singh





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

Re: [mapserver-users] tinyows does not show vector layer

[Rahkonen Jukka (MML)]

Hi ,

You could have mentioned that you have asked the same question in 
gis.stackexchange 
http://gis.stackexchange.com/questions/189102/tinyows-does-not-show-vector-layer
 . Reading the comments may help Mapserver users to give you a better answer 
and faster.

-Jukka Rahkonen-

vineet singh wrote:



Hi Everyone,

I'm using tinyows server configured with config.xml file. I'm adding vector 
layer to config file and for the first time it does not show newly added layer, 
but once i have restarted the tinyows server than it will show the layer.

So i have to restart tinyows after adding new layer. Anyone know how can I fix 
this so that it will work without restarting.

I'm runing TinyOWS as fast-cgi.

Here is config.xml :

http://192.168.0.35:19090/maps; 
schema_dir="/home/vineet/Project/mygis/data/schema">





mailto:cont...@.com>" name="MyGis Server" 
site="http://www.x.com/"/>

http://www.vizexperts.com/;  name="world_boundaries"

 title="World Borders" />

 



Thanks,

Vineet Singh
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] tinyows does not show vector layer

[vineet singh]

Hi Everyone,

I'm using tinyows server configured with config.xml file. I'm adding vector
layer to config file and for the first time it does not show newly added
layer, but once i have restarted the tinyows server than it will show the
layer.

So i have to restart tinyows after adding new layer. Anyone know how can I
fix this so that it will work without restarting.

I'm runing TinyOWS as fast-cgi.

Here is config.xml :

http://192.168.0.35:19090/maps;
schema_dir="/home/vineet/Project/mygis/data/schema">





http://www.x.com/"/>

http://www.vizexperts.com/;  name="world_boundaries"

 title="World Borders" />

 


Thanks,

Vineet Singh
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Tinyows as a WFS-T server - error commiting write

[Jeff McKenna]

Sorry the correct GeoMOOSE discussion is at: 
http://osgeo-org.1560.x6.nabble.com/Geomoose-users-Vector-editing-with-WFS-T-td5255918.html


-jeff


--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/



On 2016-03-29 9:33 AM, Jeff McKenna wrote:

Hi Andrea,

MS4W includes TinyOWS and demo data, and you can follow along how to
configure it at http://www.ms4w.com/README_INSTALL.html#h-tinyows An
OpenLayers client is also included that is pre-configured for MS4W.

Recently the GeoMOOSE developers (http://www.geomoose.org/) were adding
this to their own demo as well (WFS-T using GeoMOOSE, TinyOWS and MS4W)
and they were successfull. You can follow along that discussion here:
http://osgeo-org.1560.x6.nabble.com/Geomoose-users-using-WFS-T-td5256500.html


Also, for your research be sure to examine the ZOO-Project
(http://www.zoo-project.org/), as it is a very powerful WPS instance, as
well as WFS-T (through either MapServer or GeoServer).  I also plan on
adding it into the base of MS4W soon.  ZOO-Project has so many
highlights, including the ability to have your data in any GDAL/OGR
format.  I honestly hope, as a MapServer PSC member, we can again
discuss the ZOO-Project coming inside the MapServer umbrella, as we had
discussed this earlier, but since then I've noticed several other
MapServer PSC members using ZOO - so maybe we/ZOO were ahead of our
time, and the time is better now.  Note that I am on both the
ZOO-Project and MapServer steering committees.

Thanks for bringing up WFS-T for discussion.

-jeff






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

Re: [mapserver-users] Tinyows as a WFS-T server - error commiting write

[Jeff McKenna]

Hi Andrea,

MS4W includes TinyOWS and demo data, and you can follow along how to 
configure it at http://www.ms4w.com/README_INSTALL.html#h-tinyows An 
OpenLayers client is also included that is pre-configured for MS4W.


Recently the GeoMOOSE developers (http://www.geomoose.org/) were adding 
this to their own demo as well (WFS-T using GeoMOOSE, TinyOWS and MS4W) 
and they were successfull. You can follow along that discussion here: 
http://osgeo-org.1560.x6.nabble.com/Geomoose-users-using-WFS-T-td5256500.html


Also, for your research be sure to examine the ZOO-Project 
(http://www.zoo-project.org/), as it is a very powerful WPS instance, as 
well as WFS-T (through either MapServer or GeoServer).  I also plan on 
adding it into the base of MS4W soon.  ZOO-Project has so many 
highlights, including the ability to have your data in any GDAL/OGR 
format.  I honestly hope, as a MapServer PSC member, we can again 
discuss the ZOO-Project coming inside the MapServer umbrella, as we had 
discussed this earlier, but since then I've noticed several other 
MapServer PSC members using ZOO - so maybe we/ZOO were ahead of our 
time, and the time is better now.  Note that I am on both the 
ZOO-Project and MapServer steering committees.


Thanks for bringing up WFS-T for discussion.

-jeff



--
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/




On 2016-03-29 6:52 AM, Andrea Peri wrote:

Hi ,

I'm try-ed to write on a spatial feature user the tinyows as wfs-t and
qgis 2.14 as wfs client.
But is returned an error.

So I open an issue on tinyows.

https://github.com/mapserver/tinyows/issues/86

I like to know if someone have succesfully used tinyows as a wfs-t
service with qgis client.
Or with other clients wfs-t.

Thx,




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

Re: [mapserver-users] Tinyows exchange coords when POST request.

[Rahkonen Jukka (MML)]

Hi,

This is not true "the result will be ALWAYS in reversed format."

The bug seems to be specific for EPSG:3003. See what your own server does with 
EPSG:3067:

http://www502.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs?service=WFS=1.1.0=GetFeature=sita:idstradertline=1=EPSG:3067


http://www502.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs?service=WFS=1.1.0=GetFeature=sita:idstradertline=1=urn:ogc:def:crs:EPSG::3067

No flip which is correct. The place to correct the bug is to find out where 
TinyOWS is analyzing if coordinates must be flipped or not and consider how to 
get EPSG:3003 into the list of no-flip systems.


-Jukka Rahkonen-

Andrea Peri wrote:

> Hi,
I'm evaluting some wfs softwares to start a wfs transactionally with writable 
capabilities.

> After some test sessions using geoserver.

> I start to test the tinyows and notice a strange question about the reversing 
> of axis.

> I send some email and exchange opinion with Olivier and Jukka.
After this I stopthe testing because need to do another urgetn work.
Now I need to restart the question of what wfs use for our service.

> So I restart on tinyows and try to understand better the question of 
> reversing axis.

> So I notice that the tinyows will return the list of srs in URN format in the 
> getcapabilities.
This a very complicated question because the clients will return the values 
listesd in the capabilities.
And if the capabilities report always a reversed format, the result will be 
ALWAYS in reversed format.
:(

I notice infact that when call for a getcapabilities from a tinyows.

http://www502.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs?service=WFS=1.1.0=GetCapabilities

It return always the srs of the layers always using the urn notation:

urn:ogc:def:crs:EPSG::3003urn:ogc:def:crs:EPSG::25832urn:ogc:def:crs:EPSG::4326urn:ogc:def:crs:EPSG::3857urn:ogc:def:crs:EPSG::6707

And this mean that the client will send a request using the same notation.
But these mean also , as reported me from Olivier, thattinyows will return 
always the axis reversed.

This is a sample of a call with a correct axis order:
http://www502.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs?service=WFS=1.1.0=GetFeature=sita:idstradertline=1=EPSG:3003

http://www502.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs?service=WFS=1.1.0=GetFeature=sita:idstradertline=1=urn:ogc:def:crs:EPSG::3003

So I need to understand of the reversing axis in tinyows is a bug patchable or 
a standardized response.
And also I need to understand if is right that the getcapabilites will return 
the srs list always in URN format .

Any hint on this ?

Thx.

A.



--
-
Andrea Peri
. . . . . . . . .
qwerty àèìòù
-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Tinyows exchange coords when POST request.

[Andrea Peri]

Hi,
I'm evaluting some wfs softwares to start a wfs transactionally with
writable capabilities.

After some test sessions using geoserver.

I start to test the tinyows and notice a strange question about the
reversing of axis.

I send some email and exchange opinion with Olivier and Jukka.
After this I stopthe testing because need to do another urgetn work.
Now I need to restart the question of what wfs use for our service.

So I restart on tinyows and try to understand better the question of
reversing axis.

So I notice that the tinyows will return the list of srs in URN format
in the getcapabilities.
This a very complicated question because the clients will return the
values listesd in the capabilities.
And if the capabilities report always a reversed format, the result
will be ALWAYS in reversed format.
:(

I notice infact that when call for a getcapabilities from a tinyows.

http://www502.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs?service=WFS=1.1.0=GetCapabilities

It return always the srs of the layers always using the urn notation:

urn:ogc:def:crs:EPSG::3003urn:ogc:def:crs:EPSG::25832urn:ogc:def:crs:EPSG::4326urn:ogc:def:crs:EPSG::3857urn:ogc:def:crs:EPSG::6707

And this mean that the client will send a request using the same notation.
But these mean also , as reported me from Olivier, thattinyows will
return always the axis reversed.

This is a sample of a call with a correct axis order:
http://www502.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs?service=WFS=1.1.0=GetFeature=sita:idstradertline=1=EPSG:3003

http://www502.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs?service=WFS=1.1.0=GetFeature=sita:idstradertline=1=urn:ogc:def:crs:EPSG::3003

So I need to understand of the reversing axis in tinyows is a bug
patchable or a standardized response.
And also I need to understand if is right that the getcapabilites will
return the srs list always in URN format .

Any hint on this ?

Thx.

A.



-- 
-
Andrea Peri
. . . . . . . . .
qwerty àèìòù
-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Tinyows exchange coords when POST request.

[Rahkonen Jukka (MML)]

Hi,

The documentation of Geoserver is not quite right or clear at this point. 
Geoserver developers did believe some years ago that WFS 1.1.0 means flipping 
the axis always but of course it is not that simple. Currently Geoserver is 
handling axis order with WFS 1.1.0 and higher, with WMS 1.3.0, and with WCS 
1.1.0 and higher as


-  Always longitude-latitude or easting-northing with the short 
EPSG: syntax

-  Axis order as it is defined in the EPSG database when the long urn 
syntax is used


You can test that yourself by using for example EPSG:2393 and EPSG:3067. The 
first one is Gauss-Krüger system with northing-easting axis order but the 
latter is UTM system with easting-northing. Geoserver does not flip the axis of 
srsname=urn:x-ogc:def:crs:EPSG:3067

No flip with the short syntax
http://demo.opengeo.org/geoserver/wfs?service=wfs=1.1.0=GetFeature=topp:states=1=epsg:2393
Flip with the urn syntax
http://demo.opengeo.org/geoserver/wfs?service=wfs=1.1.0=GetFeature=topp:states=1=urn:x-ogc:def:crs:EPSG:2393
No flip despite using the urn syntax because of official easting-northing axis
http://demo.opengeo.org/geoserver/wfs?service=wfs=1.1.0=GetFeature=topp:states=1=urn:x-ogc:def:crs:EPSG:3067

TinyOWS behaves similarly
No-flip with short
http://hip.latuviitta.org/cgi-bin/tinyows?service=wfs=1.1.0=1=getfeature=lv:mml_kunta100k_2011_p=EPSG:2393
Flip with long
http://hip.latuviitta.org/cgi-bin/tinyows?service=wfs=1.1.0=1=getfeature=lv:mml_kunta100k_2011_p=urn:x-ogc:def:crs:EPSG:2393
No flip with long because system is E-N
http://hip.latuviitta.org/cgi-bin/tinyows?service=wfs=1.1.0=1=getfeature=lv:mml_kunta100k_2011_p=urn:x-ogc:def:crs:EPSG:3067

EPSG:2393 and EPSG:3067 are perhaps the most tested coordinate systems for axis 
flipping in both Geoserver and Tinyows (Hi Oliviers and Andrea!) but mostly 
only for simple GetFeature requests. Unfortunately coordinates used inside the 
filters have not been tested so well and strange things can happen. In your 
case you use EPSG:3003 which is E-N system and Tinyows handles it correctly 
when it requires non-flipped coordinates. But you wrote that TinyOWS returns 
EPSG:3003 coordinates in reversed order for you and that is clearly a bug.

-Jukka Rahkonen-


aperi2007 wrote:

Hi Jukka.
I agreed with you that if the srs is epsg it should always repeort the correct 
axis order, but this , as report me from Olivier, seem to be a standard 
"defacto" (a standard coming from bottom).
This is confirmed from this doc from Geoserver:

http://docs.geoserver.org/latest/en/user/services/wfs/basics.html

Where is reported this rule:
Representation

Assumed axis order

EPSG:

longitude/latitude (x/y)

http://www.opengis.net/gml/srs/epsg.xml#

longitude/latitude (x/y)

urn:x-ogc:def:crs:EPSG:

latitude/longitude (y/x)


So established that this is the rule, my second question is:
A request with an srs espressed as a urn should have the coords in reversed 
axis order ?

Actually tinyows need the request coords in not-reversed axis order however.

A.
Il 15/03/2016 22:58, Rahkonen Jukka (MML) ha scritto:

Hi,



With EPSG:3003 the coordinates should never ever be reversed because it is 
officially an Easting-Northing system as you can see from 
http://epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::3003



AXIS["easting (X)",east,ORDER[1]],

AXIS["northing (Y)",north,ORDER[2]],



So if you will find a difference in using WMS 1.1.x vs. 1.3.0 or WFS 1.0 vs. 
1.1 or SRS in short format vs. long format with EPSG:3003 that's a bug.



-Jukka Rahkonen-



Andrea Peri wrote:



Hi,

thx to Olivier. I understand that the TinyOWS has a rule inherited from OGC 
that when the srs is in short version (ie: EPSG:3003) the axis are not reversed.

Instead when the srs is with long form (ie:

urn:x-ogc:def:crs:EPSG:3003) the axis are always reversed.



A last question I have is about the input.

Infact this rule seem to be supported also in input request.

So when the srs is espressed in the request in long form , I guess, the 
cocordinates should be given in reversed order.

But instead tinyows seem to accept instead the coordinate in not reversed axis 
order.


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

Re: [mapserver-users] Tinyows exchange coords when POST request.

[aperi2007]

Hi Jukka.
I agreed with you that if the srs is epsg it should always repeort the 
correct axis order, but this , as report me from Olivier, seem to be a 
standard "defacto" (a standard coming from bottom).

This is confirmed from this doc from Geoserver:

http://docs.geoserver.org/latest/en/user/services/wfs/basics.html

Where is reported this rule:

Representation  Assumed axis order
EPSG:   longitude/latitude (x/y)
http://www.opengis.net/gml/srs/epsg.xml#longitude/latitude (x/y)
urn:x-ogc:def:crs:EPSG: latitude/longitude (y/x)


So established that this is the rule, my second question is:
A request with an srs espressed as a urn should have the coords in 
reversed axis order ?


Actually tinyows need the request coords in not-reversed axis order however.

A.

Il 15/03/2016 22:58, Rahkonen Jukka (MML) ha scritto:

Hi,

With EPSG:3003 the coordinates should never ever be reversed because it is 
officially an Easting-Northing system as you can see from 
http://epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::3003

AXIS["easting (X)",east,ORDER[1]],
AXIS["northing (Y)",north,ORDER[2]],

So if you will find a difference in using WMS 1.1.x vs. 1.3.0 or WFS 1.0 vs. 
1.1 or SRS in short format vs. long format with EPSG:3003 that's a bug.

-Jukka Rahkonen-

Andrea Peri wrote:

Hi,
thx to Olivier. I understand that the TinyOWS has a rule inherited from OGC 
that when the srs is in short version (ie: EPSG:3003) the axis are not reversed.
Instead when the srs is with long form (ie:
urn:x-ogc:def:crs:EPSG:3003) the axis are always reversed.

A last question I have is about the input.
Infact this rule seem to be supported also in input request.
So when the srs is espressed in the request in long form , I guess, the 
cocordinates should be given in reversed order.
But instead tinyows seem to accept instead the coordinate in not reversed axis 
order.

I post a sample :

This is the post example:

http://www.regione.toscana.it/;
xmlns:ogc="http://www.opengis.net/ogc;
xmlns:wfs="http://www.opengis.net/wfs;
xmlns:ows="http://www.opengis.net/ows;
xmlns:xlink="http://www.w3.org/1999/xlink;
xmlns:gml="http://www.opengis.net/gml; handle="GeoTools 11.4 WFS DataStore" 
maxFeatures="10" outputFormat="text/xml; subtype=gml/3.1.1"
resultType="results" service="WFS" version="1.1.0">  
   
 
  geometry
  
   

 1625601.65 4842775.06 1696384.15 4842775.06
1696384.15 4871929.04 1625601.65 4871929.04 1625601.65 4842775.06

   
  
 
   
  



That is callable using this curl call:

curl -H "Content-Type: text/xml" -0 -X POST -d @req2.xml 
"http://www502.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs;

As noticeable.
The request has the coords in not reversed order, the srs is in the long form, 
and the response is with coords in reversed order.
I guess the tinyows should accept the coords in reversed order to be totally 
coherent with the rule that the long srs form will reverse axis.

Any thought ?


2016-03-14 17:00 GMT+01:00 Andrea Peri :

Hi,
I experience this issue.

When asking to the tinyows a getfeature with an intersects with a
polygon and returning in epsg:3003 it return the result with the right
axis order if the request is done with GET method.
Instead it return exchange coords if the request is in POST method.

Is know this issue ?

Thx.

--
-
Andrea Peri
. . . . . . . . .
qwerty àèìòù
-



--
-
Andrea Peri
. . . . . . . . .
qwerty àèìòù
-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users


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

Re: [mapserver-users] Tinyows exchange coords when POST request.

[Rahkonen Jukka (MML)]

Hi,

With EPSG:3003 the coordinates should never ever be reversed because it is 
officially an Easting-Northing system as you can see from 
http://epsg-registry.org/export.htm?wkt=urn:ogc:def:crs:EPSG::3003

AXIS["easting (X)",east,ORDER[1]],
AXIS["northing (Y)",north,ORDER[2]],

So if you will find a difference in using WMS 1.1.x vs. 1.3.0 or WFS 1.0 vs. 
1.1 or SRS in short format vs. long format with EPSG:3003 that's a bug.

-Jukka Rahkonen-

Andrea Peri wrote:

Hi,
thx to Olivier. I understand that the TinyOWS has a rule inherited from OGC 
that when the srs is in short version (ie: EPSG:3003) the axis are not reversed.
Instead when the srs is with long form (ie:
urn:x-ogc:def:crs:EPSG:3003) the axis are always reversed.

A last question I have is about the input.
Infact this rule seem to be supported also in input request.
So when the srs is espressed in the request in long form , I guess, the 
cocordinates should be given in reversed order.
But instead tinyows seem to accept instead the coordinate in not reversed axis 
order.

I post a sample :

This is the post example:

http://www.regione.toscana.it/;
xmlns:ogc="http://www.opengis.net/ogc;
xmlns:wfs="http://www.opengis.net/wfs;
xmlns:ows="http://www.opengis.net/ows;
xmlns:xlink="http://www.w3.org/1999/xlink;
xmlns:gml="http://www.opengis.net/gml; handle="GeoTools 11.4 WFS DataStore" 
maxFeatures="10" outputFormat="text/xml; subtype=gml/3.1.1"
resultType="results" service="WFS" version="1.1.0">  
  

 geometry
 
  
   
1625601.65 4842775.06 1696384.15 4842775.06
1696384.15 4871929.04 1625601.65 4871929.04 1625601.65 4842775.06
   
  
 

  
 



That is callable using this curl call:

curl -H "Content-Type: text/xml" -0 -X POST -d @req2.xml 
"http://www502.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs;

As noticeable.
The request has the coords in not reversed order, the srs is in the long form, 
and the response is with coords in reversed order.
I guess the tinyows should accept the coords in reversed order to be totally 
coherent with the rule that the long srs form will reverse axis.

Any thought ?


2016-03-14 17:00 GMT+01:00 Andrea Peri :
> Hi,
> I experience this issue.
>
> When asking to the tinyows a getfeature with an intersects with a 
> polygon and returning in epsg:3003 it return the result with the right 
> axis order if the request is done with GET method.
> Instead it return exchange coords if the request is in POST method.
>
> Is know this issue ?
>
> Thx.
>
> --
> -
> Andrea Peri
> . . . . . . . . .
> qwerty àèìòù
> -



--
-
Andrea Peri
. . . . . . . . .
qwerty àèìòù
-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] Tinyows exchange coords when POST request.

[Andrea Peri]

Hi,
thx to Olivier. I understand that the TinyOWS has a rule inherited from OGC that
when the srs is in short version (ie: EPSG:3003) the axis are not reversed.
Instead when the srs is with long form (ie:
urn:x-ogc:def:crs:EPSG:3003) the axis are always reversed.

A last question I have is about the input.
Infact this rule seem to be supported also in input request.
So when the srs is espressed in the request in long form , I guess,
the cocordinates should be given in reversed order.
But instead tinyows seem to accept instead the coordinate in not
reversed axis order.

I post a sample :

This is the post example:

http://www.regione.toscana.it/;
xmlns:ogc="http://www.opengis.net/ogc;
xmlns:wfs="http://www.opengis.net/wfs;
xmlns:ows="http://www.opengis.net/ows;
xmlns:xlink="http://www.w3.org/1999/xlink;
xmlns:gml="http://www.opengis.net/gml; handle="GeoTools 11.4 WFS
DataStore" maxFeatures="10" outputFormat="text/xml; subtype=gml/3.1.1"
resultType="results" service="WFS" version="1.1.0">
 
  

 geometry
 
  
   
1625601.65 4842775.06 1696384.15 4842775.06
1696384.15 4871929.04 1625601.65 4871929.04 1625601.65
4842775.06
   
  
 

  
 



That is callable using this curl call:

curl -H "Content-Type: text/xml" -0 -X POST -d @req2.xml
"http://www502.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs;

As noticeable.
The request has the coords in not reversed order, the srs is in the
long form, and the response is with coords in reversed order.
I guess the tinyows should accept the coords in reversed order to be
totally coherent with the rule that the long srs form will reverse
axis.

Any thought ?


2016-03-14 17:00 GMT+01:00 Andrea Peri :
> Hi,
> I experience this issue.
>
> When asking to the tinyows a getfeature with an intersects with a
> polygon and returning in epsg:3003 it return the result with the right
> axis order if the request is done with GET method.
> Instead it return exchange coords if the request is in POST method.
>
> Is know this issue ?
>
> Thx.
>
> --
> -
> Andrea Peri
> . . . . . . . . .
> qwerty àèìòù
> -



-- 
-
Andrea Peri
. . . . . . . . .
qwerty àèìòù
-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] Tinyows exchange coords when POST request.

[Andrea Peri]

Hi,
I experience this issue.

When asking to the tinyows a getfeature with an intersects with a
polygon and returning in epsg:3003 it return the result with the right
axis order if the request is done with GET method.
Instead it return exchange coords if the request is in POST method.

Is know this issue ?

Thx.

-- 
-
Andrea Peri
. . . . . . . . .
qwerty àèìòù
-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] TinyOWS: GetFeature request from a DB view

[Richard Turner]

Hi,

I'm trying to configure TinyOWS using a mapfile, which I'll also use
to configure mapserver. My layers come from DB views, not tables, so
they have no primary keys. For mapserver I specify the gml_featureid
and all works well. If I configure TinyOWS using an XML file instead,
and specify the pkey attribute that all works too.

I can't seem to configure TinyOWS to work using the mapfile though; no
matter how I try to specify the pkey I always get the error:

ServiceException code=NoMatching locator=GetFeature
error : an id_column is required to use featureid/ServiceException
/ServiceExceptionReport

There's a layer definition below. Is this a bug (or missing feature)
or am I just trying to configure the pkey wrong?

Cheers,
 Richard.


LAYER
NAME title_circulation_areas
METADATA
wfs_title Press Title circulation areas
wfs_srs   EPSG:3857
wfs_enable_request*
wfs_getfeature_formatlist json
wfs_geomtype  multipolygon
wfs_typename  title_circulation_areas
gml_featureid id
gml_include_items id,name,wkb_geometry
tinyows_table title_circulation_areas
tinyows_retrievable   1
tinyows_include_items id,name,wkb_geometry

pkey  id
END
TYPE POLYGON
STATUS ON
CONNECTIONTYPE POSTGIS
CONNECTION host=host port=5432 dbname=db user=user password=pass
DATA wkb_geometry FROM title_circulation_areas USING UNIQUE id
DUMP TRUE
END

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

Re: [mapserver-users] TinyOWS: Axis order fix wanted

[Rahkonen Jukka (Tike)]

Olivier Courtin wrote:
 
 On Sat, Jun 28, 2014 at 11:38 PM, Even Rouault even.rouault@mines-
 paris.org wrote:
 
 
  The following pull request should fix Jukka's issue :
 
  https://github.com/mapserver/tinyows/pull/65
 
 I've just commited the pull request.
 Thanks for this one Even,
 
 
 Jukka could you check on your own that everything is fine for you ?

With pleasure but I need some help. I need detailed instructions for how to 
compile the version from github with Ubuntu 14.04. I think that the same 
instructions could  be included also in the TinyOWS documentation.

-Jukka Rahkonen-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] TinyOWS: Axis order fix wanted

[Olivier Courtin]

On Sat, Jun 28, 2014 at 11:38 PM, Even Rouault
even.roua...@mines-paris.org wrote:


 The following pull request should fix Jukka's issue :

 https://github.com/mapserver/tinyows/pull/65

I've just commited the pull request.
Thanks for this one Even,


Jukka could you check on your own that everything is fine for you ?


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

Re: [mapserver-users] TinyOWS: Axis order fix wanted

[Olivier Courtin]

Jukka, Even,

 I've not looked at TinyOWS code recently, but I guess that reusing the
 database of EPSG codes used by MapServer to determine where axis swapping is
 necessary should be doable.

If i remember well it's more than that.
As axis swapping is already handled.

 I may be able to help with
 making it to happen.

 Do you mean funding ?

 I think I've commit rights in TinyOWS since it is hosted at
 https://github.com/mapserver/ and I've commit rights in mapserver
 repositories, but I should perhaps check with Olivier Courtin/Oslandia if
 they're OK with me touching the code.

As long as we communicate before commits,
you're very welcome Even !

 Potentially they could also be
 interested in funded work too.

We could indeed,
I send you an email Jukka.

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

[mapserver-users] TinyOWS: Axis order fix wanted

[Rahkonen Jukka (Tike)]

Hi,

If there is someone who knows how to fix WFS 1.1.0 axis order in TinyOWS with 
some projections, please contact me. I may be able to help with making it to 
happen.

-Jukka Rahkonen-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] TinyOWS: Axis order fix wanted

[Even Rouault]

Le mercredi 18 juin 2014 19:29:39, Rahkonen Jukka (Tike) a écrit :
 Hi,
 
 If there is someone who knows how to fix WFS 1.1.0 axis order in TinyOWS
 with some projections, please contact me.

Hi Jukka,

I've not looked at TinyOWS code recently, but I guess that reusing the 
database of EPSG codes used by MapServer to determine where axis swapping is 
necessary should be doable.

 I may be able to help with
 making it to happen.

Do you mean funding ?

I think I've commit rights in TinyOWS since it is hosted at 
https://github.com/mapserver/ and I've commit rights in mapserver 
repositories, but I should perhaps check with Olivier Courtin/Oslandia if 
they're OK with me touching the code. Potentially they could also be 
interested in funded work too.

Even

 
 -Jukka Rahkonen-
 ___
 mapserver-users mailing list
 mapserver-users@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/mapserver-users

-- 
Geospatial professional services
http://even.rouault.free.fr/services.html
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] TinyOWS insert feature not working

[Jiří Kadlec]

I have installed and set-up TinyOWS for editing features from PostGIS
database on a RHEL6 Linux server.
Displaying features is working OK in QGIS and in Openlayers.
Editing a feature also works correctly.
However, when I try to insert a new feature I get the following error
response:

?xml version='1.0' encoding='UTF-8'?
ows:ExceptionReport
 xmlns='http://www.opengis.net/ows'
 xmlns:ows='http://www.opengis.net/ows'
 xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
 xsi:schemaLocation='http://www.opengis.net/ows
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'
 version='1.1.0' language='en'
 ows:Exception exceptionCode='InvalidParameterValue' locator='request'
  ows:ExceptionTextXML request isn't valid/ows:ExceptionText
 /ows:Exception
/ows:ExceptionReport

Here is the Request payload that gets posted to TinyOWS:

   1. wfs:Transaction xmlns:wfs=http://www.opengis.net/wfs; service=WFS
   version=1.0.0 xsi:schemaLocation=http://www.opengis.net/wfs
   http://schemas.opengis.net/wfs/1.0.0/WFS-transaction.xsd; xmlns:xsi=
   
http://www.w3.org/2001/XMLSchema-instance;wfs:Insertfeature:mk_city_centre
   
xmlns:feature=https://geoinformatics.aalto.fi/;feature:the_geom3857gml:MultiPolygon
   xmlns:gml=http://www.opengis.net/gml;
   
srsName=EPSG:3857gml:polygonMembergml:Polygongml:outerBoundaryIsgml:LinearRinggml:coordinates
   decimal=. cs=, ts= 2852436.2002366,8629373.6312116
   2851633.6114397,8628494.6053864 2850678.1485863,8629067.8830985
   2850563.4930439,8630176.2200085
   
2852436.2002366,8629373.6312116/gml:coordinates/gml:LinearRing/gml:outerBoundaryIs/gml:Polygon/gml:polygonMember/gml:MultiPolygon/feature:the_geom3857/feature:mk_city_centre/wfs:Insert/wfs:Transaction




-- 
My TinyOWS error log shows:


   1.
   2. [Thu Jan 23 04:45:19 2014] [ERROR] Element '{
   http://www.w3.org/2001/XMLSchema}import': Failed to locate a schema at
   location '
   
https://geoinformatics.aalto.fi/kala/tinyows.cgi?service=WFSrequest=DescribeFeatureTypeversion=1.0.0'.
   Skipping the import.
   3.
   4. [Thu Jan 23 04:45:19 2014] [ERROR] Element '{
   https://geoinformatics.aalto.fi/}mk_city_centre': This element is not
   expected. Expected is one of ( {http://www.opengis.net/gml}_Feature, {
   http://www.opengis.net/wfs}FeatureCollection ).
   5.
   6. [Thu Jan 23 04:45:19 2014] [ERROR] XML request isn't valid
   7.




Here's my tinyows.xml configuration file:

tinyows online_resource=https://geoinformatics.aalto.fi/kala/tinyows.cgi;
 schema_dir=/usr/local/share/tinyows/schema/
 log=/tmp/tinyows.log
 log_level=1
  pg host=localhost user=postgres password=* dbname=LAHTI
port=5432/

  metadata name=TinyOWS Server
title=Lahti Urban  WFS Server /

  layer retrievable=1
 writable=1
 ns_prefix=tows
 ns_uri=https://geoinformatics.aalto.fi/;
 name=subwatersheds
 title=subwatersheds /

 layer retrievable=1
 writable=1
 ns_prefix=tows
 ns_uri=https://geoinformatics.aalto.fi/;
 name=mk_city_centre
 title=Lahti City Centre
 exclude_items=the_geom3880 /
/tinyows

And finally, here is my OpenLayers editing client javascript code snippet:

  var saveStrategy = new OpenLayers.Strategy.Save();
  saveStrategy.events.register(success, '', showSuccessMsg);
  saveStrategy.events.register(fail, '', showFailureMsg);
  wfs = new OpenLayers.Layer.Vector(Editable Features, {
  strategies: [new OpenLayers.Strategy.BBOX(), saveStrategy],
  projection: new OpenLayers.Projection(EPSG:3857),
  protocol: new OpenLayers.Protocol.WFS({
  version: 1.0.0,
  srsName: EPSG:3857,
  url: https://geoinformatics.aalto.fi/kala/tinyows.cgi;,
  featureNS :  https://geoinformatics.aalto.fi/;,
  featureType: mk_city_centre,
  geometryName: the_geom3857
  //schema: 
https://geoinformatics.aalto.fi/kala/tinyows.cgi?service=wfsversion=1.0.0request=DescribeFeatureTypetypeName=tows:mk_city_centre

  })
  });


I've never used TinyOWS before. Any Ideas what I'm doing wrong? Especially
the error message
Element '{https://geoinformatics.aalto.fi/}mk_city_centre': This element is
not expected. Expected is one of ( {http://www.opengis.net/gml}_Feature, {
http://www.opengis.net/wfs}FeatureCollection ).

is confusing.

Thanks in advance for any hints or suggestions how to solve the problem.

Jiri Kadlec
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] TinyOWS insert feature not working

[Rahkonen Jukka (Tike)]

Hi,

You can try if you can have success with my server 
http://hip.latuviitta.org/cgi-bin/tinyows
Kosmo GIS which is an excellent open source GIS client for WFS creates the 
following request. Compare and see if you'll find something interesting.

?xml version='1.0' encoding='UTF-8'?
wfs:Transaction version=1.0.0 service=WFS xmlns:lv=http://latuviitta.fi/;
xmlns:gml=http://www.opengis.net/gml;
xmlns:ogc=http://www.opengis.net/ogc;
xmlns:wfs=http://www.opengis.net/wfs;
xmlns:xlink=http://www.w3.org/1999/xlink;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://www.opengis.net/wfs 
http://schemas.opengis.net/wfs/1.0.0/WFS-transaction.xsd 
http://hip.latuviitta.org/cgi-bin/tinyows?SERVICE=WFSamp;REQUEST=DescribeFeatureTypeamp;version=1.0.0amp;TYPENAME=lv:editable_multipolygonsamp;NAMESPACE=xmlns(lv=http://latuviitta.fi/)
 http://latuviitta.fi/;
wfs:Insert handle=insert1 idgen=GenerateNew
lv:editable_multipolygons xmlns:lv=http://latuviitta.fi/;
lv:geomgml:MultiPolygon xmlns:gml=http://www.opengis.net/gml; 
srsName=EPSG:3067
gml:polygonMember
gml:Polygon xmlns:gml=http://www.opengis.net/gml; srsName=EPSG:3067
gml:outerBoundaryIs
gml:LinearRing
gml:coordinates195203.757,7279828.574 225034.737,7307065.556 
262647.711,7278531.575 260053.713,7238324.602 217252.742,7242215.6 
195203.757,7279828.574
/gml:coordinates
/gml:LinearRing
/gml:outerBoundaryIs
/gml:Polygon
/gml:polygonMember
/gml:MultiPolygon
/lv:geom
/lv:editable_multipolygons
/wfs:Insert
/wfs:Transaction

-Jukka Rahkonen-


 Jiří Kadlec wrote:

 I have installed and set-up TinyOWS for editing features from PostGIS 
 database on a RHEL6 Linux server.
 Displaying features is working OK in QGIS and in Openlayers.
 Editing a feature also works correctly.
 However, when I try to insert a new feature I get the following error 
 response:

?xml version='1.0' encoding='UTF-8'?
ows:ExceptionReport
 xmlns='http://www.opengis.net/ows'
 xmlns:ows='http://www.opengis.net/ows'
 xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
 xsi:schemaLocation='http://www.opengis.net/ows 
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'
 version='1.1.0' language='en'
 ows:Exception exceptionCode='InvalidParameterValue' locator='request'
  ows:ExceptionTextXML request isn't valid/ows:ExceptionText
 /ows:Exception
/ows:ExceptionReport

Here is the Request payload that gets posted to TinyOWS:

  1.  wfs:Transaction xmlns:wfs=http://www.opengis.net/wfs; service=WFS 
version=1.0.0 xsi:schemaLocation=http://www.opengis.net/wfs 
http://schemas.opengis.net/wfs/1.0.0/WFS-transaction.xsd; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;wfs:Insertfeature:mk_city_centre
 
xmlns:feature=https://geoinformatics.aalto.fi/;feature:the_geom3857gml:MultiPolygon
 xmlns:gml=http://www.opengis.net/gml; 
srsName=EPSG:3857gml:polygonMembergml:Polygongml:outerBoundaryIsgml:LinearRinggml:coordinates
 decimal=. cs=, ts= 2852436.2002366,8629373.6312116 
2851633.6114397,8628494.6053864 2850678.1485863,8629067.8830985 
2850563.4930439,8630176.2200085 
2852436.2002366,8629373.6312116/gml:coordinates/gml:LinearRing/gml:outerBoundaryIs/gml:Polygon/gml:polygonMember/gml:MultiPolygon/feature:the_geom3857/feature:mk_city_centre/wfs:Insert/wfs:Transaction



--
My TinyOWS error log shows:


  1.
  2.  [Thu Jan 23 04:45:19 2014] [ERROR] Element 
'{http://www.w3.org/2001/XMLSchema}import': Failed to locate a schema at 
location 
'https://geoinformatics.aalto.fi/kala/tinyows.cgi?service=WFSrequest=DescribeFeatureTypeversion=1.0.0'.
 Skipping the import.
  3.
  4.  [Thu Jan 23 04:45:19 2014] [ERROR] Element 
'{https://geoinformatics.aalto.fi/}mk_city_centre': This element is not 
expected. Expected is one of ( {http://www.opengis.net/gml}_Feature, 
{http://www.opengis.net/wfs}FeatureCollection ).
  5.
  6.  [Thu Jan 23 04:45:19 2014] [ERROR] XML request isn't valid
  7.



Here's my tinyows.xml configuration file:

tinyows online_resource=https://geoinformatics.aalto.fi/kala/tinyows.cgi;
 schema_dir=/usr/local/share/tinyows/schema/
 log=/tmp/tinyows.log
 log_level=1
  pg host=localhost user=postgres password=* dbname=LAHTI 
port=5432/

  metadata name=TinyOWS Server
title=Lahti Urban  WFS Server /

  layer retrievable=1
 writable=1
 ns_prefix=tows
 ns_uri=https://geoinformatics.aalto.fi/;
 name=subwatersheds
 title=subwatersheds /

 layer retrievable=1
 writable=1
 ns_prefix=tows
 ns_uri=https://geoinformatics.aalto.fi/;
 name=mk_city_centre
 title=Lahti City Centre
 exclude_items=the_geom3880 /
/tinyows

And finally, here is my OpenLayers editing client javascript code snippet:

  var saveStrategy = new OpenLayers.Strategy.Save();
  saveStrategy.events.register(success, '', showSuccessMsg);
  saveStrategy.events.register(fail, '', showFailureMsg);
  wfs = new OpenLayers.Layer.Vector(Editable Features, {
  strategies: [new 

Re: [mapserver-users] tinyows and postgresql schemas

[Antonio Vico]

I solved the question renaming the schema without capital letter.
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] tinyows and postgresql schemas

[Antonio Vico]

Hi all,

I am testing tinyows in OSGeo Live 7 and get errors when I use a schema 
different at public.


I use a simple XML file for configure tinyows and I started usig the 
default schema public with success (I created my own database and my 
table in public schema), but when I move this table to a new schema, 
tinyows show this error


/usr/lib/cgi-bin/tinyows --check
NOTICE:  Function postgis_topology_scripts_installed() not found. Is 
topology support enabled and topology.sql installed?

Content-Type: application/xml

?xml version='1.0' encoding='UTF-8'?
ows:ExceptionReport
 xmlns='http://www.opengis.net/ows'
 xmlns:ows='http://www.opengis.net/ows'
 xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
 xsi:schemaLocation='http://www.opengis.net/ows 
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'

 version='1.1.0' language='en'
ows:Exception exceptionCode='RequestSqlFailed' locator='pkey_sequence 
retrieve'

ows:ExceptionTextUnable to use pg_get_serial_sequence./ows:ExceptionText
/ows:Exception
/ows:ExceptionReport


It is not a database permission problem (the user is superuser) and when 
I move the same table to public schema (with pgAdmin) tinyows connect 
successfully.


Here my tinyows configuration file:

tinyows online_resource=http://127.0.0.1/cgi-bin/tinyows;
 schema_dir=/usr/share/tinyows/schema/
pg host=127.0.0.1 user=user password=user dbname=Inventari 
port=5432/

metadata name=TinyOWS Server
title=TinyOWS Server - Demo Service /
layer name=Accesos
 title=Accesos
 ns_prefix=Tgn
 ns_uri=http://www.tinyows.org;
 table=Accesos
 schema=Tgn
 retrievable=1
 writable=1
/layer
/tinyows

How can I connect to a table in a schema different to public?
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] tinyows fcgi enable

[Pedro Costa]

Hi guys,

Can anyone tell me how to enable fast cgi in tinyows or a link with more 
information?

I only find that: http://mapserver.org/tinyows/servertuning.html
I think I'm already activate in Apache with this [1].
But when i run './configure' I always get no support for fastcgi [2].


Thanks

[1]

$ sudo apt-get install -y libapache2-mod-fastcgi
$ sudo a2enmod fastcgi


[2]


checking for FCGI_Accept in -lfcgi... no
checking now FCGI in alternate fastcgi include dir
checking for FCGI_Accept in -lfcgi... (cached) no
configure: WARNING: \n\nNo FastCGI support. Performances will be strongly 
reduced !\n



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

Re: [mapserver-users] [TinyOWS] Unable to open config file

[Luca Delucchi]

On 9 May 2013 17:19, Worth Lutz w...@mindspring.com wrote:
 I have not used TinyOWS but it sounds like a permission problem on the
 config file.

 Is it readable by the web user (www-data in ubuntu)


Yes it is readable...

 Worth


thanks

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] [TinyOWS] Unable to open config file

[Rahkonen Jukka]

Hi, 

I have always used tinyows.xml configuration file, but in
http://mapserver.org/trunk/tinyows/mapfileconfig.html
there reads
To indicate where your Mapfile is located, to TinyOWS binary, use the 
''TINYOWS_MAPFILE'' environment variable.

Perhaps the environment is set for you when you run tinyows --check but not for 
the web user?

-Jukka Rahkonen-
 
Luca Delucchi wrote:

 
 On 9 May 2013 17:19, Worth Lutz w...@mindspring.com wrote:
  I have not used TinyOWS but it sounds like a permission problem on the
  config file.
 
  Is it readable by the web user (www-data in ubuntu)
 
 
 Yes it is readable...
 
  Worth
 
 
 thanks
 
 --
 ciao
 Luca
 
 http://gis.cri.fmach.it/delucchi/
 www.lucadelu.org
 ___
 mapserver-users mailing list
 mapserver-users@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/mapserver-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] [TinyOWS] Unable to open config file

[Luca Delucchi]

Sorry for boring you, someone can help me with this problem?

On 3 May 2013 14:49, Luca Delucchi lucadel...@gmail.com wrote:
 Hi everybody,
 I'm just starting to play with TinyOWS for WFS-T. I installed TinyOWS
 on a ubuntu server and I'm using mapfile to configure TinyOWS.
 If I run ./tinyows --check from command line it work well

 TinyOWS version:   1.0.0
 administrator@webcrev3:/usr/lib/cgi-bin$ TinyOWS version:   1.0.0
 PostGIS Version:   2.0.1
 PostGIS dsn:   dbname='gis_os' host=10.100.113.5 port=5432
 user='sde' password='sde' sslmode=disable
 Output Encoding:   UTF-8
 Database Encoding: UTF8
 Schema dir:/usr/share/tinyows/schema
 Display bbox:  Yes
 Estimated extent:  No
 Check schema:  Yes
 Check valid geoms: Yes
 Available layers:
  - public.sitiwgs84 (4326) - .sitiwgs84 [RW]

 but when I try from web browser it doesn't work and return Unable to
 open config file
 Do you have any advice to help me?

 Thanks

 --
 ciao
 Luca

 http://gis.cri.fmach.it/delucchi/
 www.lucadelu.org



-- 
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] [TinyOWS] Unable to open config file

[Luca Delucchi]

Hi everybody,
I'm just starting to play with TinyOWS for WFS-T. I installed TinyOWS
on a ubuntu server and I'm using mapfile to configure TinyOWS.
If I run ./tinyows --check from command line it work well

TinyOWS version:   1.0.0
administrator@webcrev3:/usr/lib/cgi-bin$ TinyOWS version:   1.0.0
PostGIS Version:   2.0.1
PostGIS dsn:   dbname='gis_os' host=10.100.113.5 port=5432
user='sde' password='sde' sslmode=disable
Output Encoding:   UTF-8
Database Encoding: UTF8
Schema dir:/usr/share/tinyows/schema
Display bbox:  Yes
Estimated extent:  No
Check schema:  Yes
Check valid geoms: Yes
Available layers:
 - public.sitiwgs84 (4326) - .sitiwgs84 [RW]

but when I try from web browser it doesn't work and return Unable to
open config file
Do you have any advice to help me?

Thanks

--
ciao
Luca

http://gis.cri.fmach.it/delucchi/
www.lucadelu.org
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] Tinyows shutdown Frida doesn't display

[NicolasPonzo]

Hi Every body,I'm trying to configure tinyows On Ubuntu Quantal from several
days but there is a problem with frida's data inside postgis.It doesn't
display through openlayers. Here is more informations so that you might help
me.When I make the check on my terminal from tinyows directory, here is what
i get:First question is FCGI is compulsory for tinyows to work ?secondly,
why the terminal can show me the layer frida and openlayers cannot do so in
the web client ?FYI, I manage to display frida's data stored in postgis with
qgis desktop Here is the result of the log while accessing the web client to
look at OpenLayers :Last but not least, here is the XML file that we have
according to all the tutorial that I found on the websites:I think that the
openlayer doesn't have a problem because I can display the OSM layer, and
the controls are activated, except the save button. Just so you can see my
result, you can look at the screen shot below:
http://osgeo-org.1560.x6.nabble.com/file/n5047842/screenshot.png Hope you
guys can help, its been very hard to work by myself.Best regards to all and
thanks in advance.Nicolas



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Tinyows-shutdown-Frida-doesn-t-display-tp5047842.html
Sent from the Mapserver - User mailing list archive at Nabble.com.___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] [tinyOWS]Trouble with feature insertion

[Serge Dikiy]

Hi, Vlad

Please show your configuration file (config.xml).

BR

On Thu, Mar 21, 2013 at 10:42 PM, Vlad Gapchich gav...@gmail.com wrote:
 Hello guys!
 I was very glad to find that tinyows supports wfs-t and tried it out with a
 simple example. However, it didn't work and i can't find a particular reason
 for that. I dug deep into code and found out that error happens on
 xmlSchemaValidateDoc, error code 1843 -  Element
 '{http://www.opengis.net/wfs}Transaction': Character content other than
 whitespace is not allowed because the content type is 'element-only'. I
 understand that it's not directly tinyows' issue, but i doubt that it's
 libxml2 either.

 The request i send looks like this:

 wfs:Transaction
   service='WFS'
   version='1.1.0'
   xmlns:wfs='http://www.opengis.net/wfs'
   xmlns:gml='http://www.opengis.net/gml'
   xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
   xmlns:map='http://www.tinyows.org/map'
   xsi:schemaLocation='http://www.opengis.net/wfs

 http://schemas.opengis.net/wfs/1.1.0/WFS-transaction.xsd

 http://127.0.0.1/cgi-bin/tinyows?service=WFSrequest=DescribeFeatureTypeversion=1.1.0'/
   wfs:Insert
 map:nodes
   map:coord
 gml:Point srsDimension='2' srsName='urn:x-ogc:def:crs:EPSG:4326'
   gml:coordinates decimal='.' cs=',' ts='
 '30.454343,50.447954/gml:coordinates
 /gml:Point
   /map:coord
 /map:nodes
   /wfs:Insert
 /wfs:Transaction

 Any help would be much appreciated, thanks in advance

 Best regards,
 Vlad

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

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

Re: [mapserver-users] [tinyOWS]Trouble with feature insertion

[Eichner, Andreas - SID-NLKM]

Try escaping the '' in the schema location URL as 'amp;' as otherwise
it would be interpreted as an enity. And schemaLocation should be a list
of pairs of namespace name and location. It's probably a good idea to
validate the request document before posting it to TinyOWS...

 The request i send looks like this:
 
 wfs:Transaction
   service='WFS'
   version='1.1.0'
   xmlns:wfs='http://www.opengis.net/wfs'
   xmlns:gml='http://www.opengis.net/gml'
   xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
   xmlns:map='http://www.tinyows.org/map'
   xsi:schemaLocation='http://www.opengis.net/wfs
   
 http://schemas.opengis.net/wfs/1.1.0/WFS-transaction.xsd
   
 http://127.0.0.1/cgi-bin/tinyows?service=WFSrequest=DescribeF
eatureTypeversion=1.1.0'/
   wfs:Insert
 map:nodes
   map:coord
 gml:Point srsDimension='2' 
 srsName='urn:x-ogc:def:crs:EPSG:4326'
   gml:coordinates decimal='.' cs=',' ts=' 
 '30.454343,50.447954/gml:coordinates
 /gml:Point
   /map:coord
 /map:nodes
   /wfs:Insert
 /wfs:Transaction 
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] [tinyOWS]Trouble with feature insertion

[Rahkonen Jukka]

Hi,

If you are on Windows you may not success. At least the version which is 
available for MS4W has a bug and it does not do inserts.
One error I can see in your request is that it is using geometry in GML2 style 
with WFS 1.1.0. I would be at least a good habit to use gml:pos there. This 
insert works for me on Linux.

?xml version='1.0' encoding='ISO-8859-1'?
wfs:Transaction version='1.1.0' service='WFS' 
xmlns:gml='http://www.opengis.net/gml' 
xmlns:ogc='http://www.opengis.net/ogc' 
xmlns:wfs='http://www.opengis.net/wfs' 
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' 
xsi:schemaLocation='http://www.opengis.net/wfs/1.1.0/WFS-transaction.xsd' 
xmlns:lv='http://latuviitta.fi/'  
wfs:Insert handle='insert1' idgen='GenerateNew' 
lv:editable_points
lv:geom
gml:Point xmlns:gml=http://www.opengis.net/gml; 
srsName=urn:ogc:def:crs:EPSG::3067 srsDimension=2  
gml:pos srsDimension=2 -160567.85652445967 5936050.398293516  
/gml:pos
/gml:Point
/lv:geom
/lv:editable_points
/wfs:Insert
/wfs:Transaction


-Jukka Rahkonen


Eichner, Andreas wrote:
 
 
 Try escaping the '' in the schema location URL as 'amp;' as otherwise it
 would be interpreted as an enity. And schemaLocation should be a list of
 pairs of namespace name and location. It's probably a good idea to validate
 the request document before posting it to TinyOWS...
 
  The request i send looks like this:
 
  wfs:Transaction
service='WFS'
version='1.1.0'
xmlns:wfs='http://www.opengis.net/wfs'
xmlns:gml='http://www.opengis.net/gml'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xmlns:map='http://www.tinyows.org/map'
xsi:schemaLocation='http://www.opengis.net/wfs
 
  http://schemas.opengis.net/wfs/1.1.0/WFS-transaction.xsd
 
  http://127.0.0.1/cgi-bin/tinyows?service=WFSrequest=DescribeF
 eatureTypeversion=1.1.0'/
wfs:Insert
  map:nodes
map:coord
  gml:Point srsDimension='2'
  srsName='urn:x-ogc:def:crs:EPSG:4326'
gml:coordinates decimal='.' cs=',' ts='
  '30.454343,50.447954/gml:coordinates
  /gml:Point
/map:coord
  /map:nodes
/wfs:Insert
  /wfs:Transaction
 ___
 mapserver-users mailing list
 mapserver-users@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/mapserver-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] [tinyOWS]Trouble with feature insertion

[Vlad Gapchich]

Thank you all guys for your support! :) I've found the answer - it was a
slash at the end of wfs:Transaction openning tag(i have no idea how it got
there).

Anyways, i'll leave here a working example of insert request just in case:

wfs:Transaction service='WFS' version='1.1.0' xmlns:wfs='
http://www.opengis.net/wfs' xmlns:gml='http://www.opengis.net/gml'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:map='
http://www.tinyows.org/map' xsi:schemaLocation='
http://schemas.opengis.net/wfs/1.1.0/WFS-transaction.xsd'
map:schemaLocation='
http://127.0.0.1/cgi-bin/tinyows?service=WFSamp;request=DescribeFeatureTypeamp;version=1.1.0'
wfs:Insert map:nodes map:coord gml:Point srsDimension='2'
srsName='urn:x-ogc:def:crs:EPSG:4326' gml:pos srsDimension='2'30.454343
50.447954/gml:pos /gml:Point /map:coord /map:nodes /wfs:Insert
/wfs:Transaction

P.S.

Changes i made:
Thanks to Andreas Eichner - escaping character in map:schemaLocation,
to Rahkonen Juka - gml2 - gml3 in gml:Point
- separate schemaLocation for map(don't even know what i was thinking
before)

And for Serge Dikiy my config.xml:
tinyows online_resource=http://127.0.0.1/cgi-bin/tinyows;
schema_dir=/usr/local/share/tinyows/schema/ log=/var/log/tinyows.log
log_level=15 check_schema=0 pg host=127.0.0.1 user=someuser
password=somepassword dbname=somedb port=2345/ metadata
name=TinyOWS Server title=TinyOWS Server - WFS-T Frida Service /
contact name=TinyOWS Server site=http://www.tinyows.org/; email=
tinyows-us...@lists.maptools.org / layer retrievable=1 writable=1
ns_prefix=map ns_uri=http://www.tinyows.org/map; name=nodes
title=Title / /tinyows

And i forgot to mention before that i use ubuntu 12.10 as an os


2013/3/22 Rahkonen Jukka jukka.rahko...@mmmtike.fi

 Hi,

 If you are on Windows you may not success. At least the version which is
 available for MS4W has a bug and it does not do inserts.
 One error I can see in your request is that it is using geometry in GML2
 style with WFS 1.1.0. I would be at least a good habit to use gml:pos
 there. This insert works for me on Linux.

 ?xml version='1.0' encoding='ISO-8859-1'?
 wfs:Transaction version='1.1.0' service='WFS'
 xmlns:gml='http://www.opengis.net/gml'
 xmlns:ogc='http://www.opengis.net/ogc'
 xmlns:wfs='http://www.opengis.net/wfs'
 xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
 xsi:schemaLocation='http://www.opengis.net/wfs/1.1.0/WFS-transaction.xsd'
 xmlns:lv='http://latuviitta.fi/'  
 wfs:Insert handle='insert1' idgen='GenerateNew' 
 lv:editable_points
 lv:geom
 gml:Point xmlns:gml=http://www.opengis.net/gml;
 srsName=urn:ogc:def:crs:EPSG::3067 srsDimension=2
 gml:pos srsDimension=2 -160567.85652445967 5936050.398293516
 /gml:pos
 /gml:Point
 /lv:geom
 /lv:editable_points
 /wfs:Insert
 /wfs:Transaction


 -Jukka Rahkonen


 Eichner, Andreas wrote:
 
 
  Try escaping the '' in the schema location URL as 'amp;' as otherwise
 it
  would be interpreted as an enity. And schemaLocation should be a list of
  pairs of namespace name and location. It's probably a good idea to
 validate
  the request document before posting it to TinyOWS...
 
   The request i send looks like this:
  
   wfs:Transaction
 service='WFS'
 version='1.1.0'
 xmlns:wfs='http://www.opengis.net/wfs'
 xmlns:gml='http://www.opengis.net/gml'
 xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
 xmlns:map='http://www.tinyows.org/map'
 xsi:schemaLocation='http://www.opengis.net/wfs
  
   http://schemas.opengis.net/wfs/1.1.0/WFS-transaction.xsd
  
   http://127.0.0.1/cgi-bin/tinyows?service=WFSrequest=DescribeF
  eatureTypeversion=1.1.0'/
 wfs:Insert
   map:nodes
 map:coord
   gml:Point srsDimension='2'
   srsName='urn:x-ogc:def:crs:EPSG:4326'
 gml:coordinates decimal='.' cs=',' ts='
   '30.454343,50.447954/gml:coordinates
   /gml:Point
 /map:coord
   /map:nodes
 /wfs:Insert
   /wfs:Transaction
  ___
  mapserver-users mailing list
  mapserver-users@lists.osgeo.org
  http://lists.osgeo.org/mailman/listinfo/mapserver-users
 ___
 mapserver-users mailing list
 mapserver-users@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/mapserver-users

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

[mapserver-users] [tinyOWS]Trouble with feature insertion

[Vlad Gapchich]

Hello guys!
I was very glad to find that tinyows supports wfs-t and tried it out with a
simple example. However, it didn't work and i can't find a particular
reason for that. I dug deep into code and found out that error happens on
xmlSchemaValidateDoc, error code 1843 -  Element '{
http://www.opengis.net/wfs}Transaction': Character content other than
whitespace is not allowed because the content type is 'element-only'. I
understand that it's not directly tinyows' issue, but i doubt that it's
libxml2 either.

The request i send looks like this:

wfs:Transaction
  service='WFS'
  version='1.1.0'
  xmlns:wfs='http://www.opengis.net/wfs'
  xmlns:gml='http://www.opengis.net/gml'
  xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
  xmlns:map='http://www.tinyows.org/map'
  xsi:schemaLocation='http://www.opengis.net/wfs

http://schemas.opengis.net/wfs/1.1.0/WFS-transaction.xsd

http://127.0.0.1/cgi-bin/tinyows?service=WFSrequest=DescribeFeatureTypeversion=1.1.0'/

  wfs:Insert
map:nodes
  map:coord
gml:Point srsDimension='2' srsName='urn:x-ogc:def:crs:EPSG:4326'
  gml:coordinates decimal='.' cs=',' ts='
'30.454343,50.447954/gml:coordinates
/gml:Point
  /map:coord
/map:nodes
  /wfs:Insert
/wfs:Transaction

Any help would be much appreciated, thanks in advance

Best regards,
Vlad
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] [TinyOWS] TinyOWS 1.1.0 and the old good axis order trouble

[Rahkonen Jukka]

Hi Olivier,

Sorry for the late response.  I analyzed finally what axis order alternatives 
the srs_wkt field in the spatial_ref_sys table contains and the situation is a 
bit more complicated than you have believed.  This is the result of a SELECT 
DISTINCT query


1)  AXIS[Easting,EAST],AXIS[Northing,NORTH]]

2)  AXIS[X,EAST],AXIS[Y,NORTH]]

3)  AXIS[Northing,NORTH],AXIS[Easting,EAST]]

4)  AXIS[X,NORTH],AXIS[Y,EAST]]

5)  AXIS[Y,EAST],AXIS[X,NORTH]]

6)  AXIS[X,SOUTH],AXIS[Y,WEST]]

7)  AXIS[Y,NORTH],AXIS[X,EAST]]

8)  AXIS[E(X),EAST],AXIS[N(Y),NORTH]]

9)  AXIS[x,NORTH],AXIS[y,EAST]]

10)   AXIS[Easting,UNKNOWN],AXIS[Northing,UNKNOWN]]

11)   AXIS[none,NORTH],AXIS[none,EAST]]

12)   AXIS[X,UNKNOWN],AXIS[Y,UNKNOWN]]

13)   AXIS[Northing,UNKNOWN],AXIS[Easting,UNKNOWN]]

My conclusions:

Must not be flipped: 1, 2, 8
Must be flipped: 3, 4, 9
Probably should not be flipped: 10, 12
Probably should be flipped: 11, 13
No idea: 5, 6, 7

The most important system for me is EPSG:3067 and it has the WKT as in 
alternative 1:  AXIS[Easting,EAST],AXIS[Northing,NORTH]]

-Jukka Rahkonen-




Lähettäjä: mapserver-users-boun...@lists.osgeo.org 
[mailto:mapserver-users-boun...@lists.osgeo.org] Puolesta Olivier Courtin
Lähetetty: 18. joulukuuta 2012 9:10
Vastaanottaja: Mapserver-Users (mapserver-users@lists.osgeo.org)
Aihe: Re: [mapserver-users] [TinyOWS] TinyOWS 1.1.0 and the old good axis order 
trouble

On Mon, Dec 17, 2012 at 11:16 AM, Rahkonen Jukka 
jukka.rahko...@mmmtike.fimailto:jukka.rahko...@mmmtike.fi wrote:

Hi Jukka,

Nice to see you again here :)
I have been running TinyOWS r558 for quite a long time because it is dealing 
almost right with the axis order of the projections I am commonly using. Now I 
had a fast try with the current TinyOWS 1.1.0 version but unfortunately I 
realized that it is doing wrong thing by flipping the axis with 
urn:ogc:def:crs:EPSG::3067.

On this topic we will not make any progress, without a regression test.
(OGC CITE don't cover this issue)

Could you provide from a single point stored in the database,
requests and answers awaited ?

I could also try to write it by myself too,
but will definitly need you to read it back,
for all eastern stuff...
What is the logic that TinyOWS is using when it decides whether the axis should 
be flipped or not  for WFS 1.1.0?

Mainly 2 factors, as i recall:
 - if it's SRS or CRS (meaning EPSG: or urn:ogc:def:crs:EPSG::)
 - if SRTEXT contain both AXIS[X,NORTH]] and AXIS[Easting,EAST]]

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

Re: [mapserver-users] [TinyOWS] TinyOWS 1.1.0 and the old good axis order trouble

[Rahkonen Jukka]

Hi,

Mapserver seems to rely on this list of coordinate systems with reversed axis 
order:
https://github.com/mapserver/mapserver/blob/master/mapaxisorder.csv

Because TinyOWS lives so close to Mapserver perhaps they could utilize the same 
list?  It would be nice if Mapserver WFS and TinyOWS WFS would have the same 
understanding about the axis order.

-Jukka-


Rahkonen Jukka wrote:

Hi Olivier,

Sorry for the late response.  I analyzed finally what axis order alternatives 
the srs_wkt field in the spatial_ref_sys table contains and the situation is a 
bit more complicated than you have believed.  This is the result of a SELECT 
DISTINCT query


1)  AXIS[Easting,EAST],AXIS[Northing,NORTH]]

2)  AXIS[X,EAST],AXIS[Y,NORTH]]

3)  AXIS[Northing,NORTH],AXIS[Easting,EAST]]

4)  AXIS[X,NORTH],AXIS[Y,EAST]]

5)  AXIS[Y,EAST],AXIS[X,NORTH]]

6)  AXIS[X,SOUTH],AXIS[Y,WEST]]

7)  AXIS[Y,NORTH],AXIS[X,EAST]]

8)  AXIS[E(X),EAST],AXIS[N(Y),NORTH]]

9)  AXIS[x,NORTH],AXIS[y,EAST]]

10)   AXIS[Easting,UNKNOWN],AXIS[Northing,UNKNOWN]]

11)   AXIS[none,NORTH],AXIS[none,EAST]]

12)   AXIS[X,UNKNOWN],AXIS[Y,UNKNOWN]]

13)   AXIS[Northing,UNKNOWN],AXIS[Easting,UNKNOWN]]

My conclusions:

Must not be flipped: 1, 2, 8
Must be flipped: 3, 4, 9
Probably should not be flipped: 10, 12
Probably should be flipped: 11, 13
No idea: 5, 6, 7

The most important system for me is EPSG:3067 and it has the WKT as in 
alternative 1:  AXIS[Easting,EAST],AXIS[Northing,NORTH]]

-Jukka Rahkonen-




Lähettäjä: 
mapserver-users-boun...@lists.osgeo.orgmailto:mapserver-users-boun...@lists.osgeo.org
 [mailto:mapserver-users-boun...@lists.osgeo.org] Puolesta Olivier Courtin
Lähetetty: 18. joulukuuta 2012 9:10
Vastaanottaja: Mapserver-Users 
(mapserver-users@lists.osgeo.orgmailto:mapserver-users@lists.osgeo.org)
Aihe: Re: [mapserver-users] [TinyOWS] TinyOWS 1.1.0 and the old good axis order 
trouble

On Mon, Dec 17, 2012 at 11:16 AM, Rahkonen Jukka 
jukka.rahko...@mmmtike.fimailto:jukka.rahko...@mmmtike.fi wrote:

Hi Jukka,

Nice to see you again here :)
I have been running TinyOWS r558 for quite a long time because it is dealing 
almost right with the axis order of the projections I am commonly using. Now I 
had a fast try with the current TinyOWS 1.1.0 version but unfortunately I 
realized that it is doing wrong thing by flipping the axis with 
urn:ogc:def:crs:EPSG::3067.

On this topic we will not make any progress, without a regression test.
(OGC CITE don't cover this issue)

Could you provide from a single point stored in the database,
requests and answers awaited ?

I could also try to write it by myself too,
but will definitly need you to read it back,
for all eastern stuff...
What is the logic that TinyOWS is using when it decides whether the axis should 
be flipped or not  for WFS 1.1.0?

Mainly 2 factors, as i recall:
 - if it's SRS or CRS (meaning EPSG: or urn:ogc:def:crs:EPSG::)
 - if SRTEXT contain both AXIS[X,NORTH]] and AXIS[Easting,EAST]]

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

Re: [mapserver-users] [TinyOWS] TinyOWS 1.1.0 and the old good axis order trouble

[Martin Kofahl]

Hi Jukka,
the mapaxisorder.csv was introduced with the axis order requirements of
WMS 1.3.0/INSPIRE and is still a poor workaround to get things working.
Accordning to [1] proj4 now supports an +axis parameter. Using the epsg
file with +axis seems quite worthwhile to me, much better than an own
list of codes. However, the epsg file shipped with proj4 4.8.0 doesn't
look complete regarding +axis. I'll try to get an answer from the proj
list.

Martin

[1] http://trac.osgeo.org/proj/wiki/GenParms



 Hi,
 
  
 
 Mapserver seems to rely on this list of coordinate systems with
 reversed axis order:
 
 https://github.com/mapserver/mapserver/blob/master/mapaxisorder.csv
 
  
 
 Because TinyOWS lives so close to Mapserver perhaps they could utilize
 the same list?  It would be nice if Mapserver WFS and TinyOWS WFS
 would have the same understanding about the axis order.
 
  
 
 -Jukka-
 
  
 
  
 
 Rahkonen Jukka wrote:
 
 
  
 
 Hi Olivier,
 
  
 
 Sorry for the late response.  I analyzed finally what axis order
 alternatives the srs_wkt field in the spatial_ref_sys table contains
 and the situation is a bit more complicated than you have believed.
 This is the result of a SELECT DISTINCT query
 
  
 
 1) AXIS[Easting,EAST],AXIS[Northing,NORTH]]
 
 2) AXIS[X,EAST],AXIS[Y,NORTH]]
 
 3) AXIS[Northing,NORTH],AXIS[Easting,EAST]]
 
 4) AXIS[X,NORTH],AXIS[Y,EAST]]
 
 5) AXIS[Y,EAST],AXIS[X,NORTH]]
 
 6) AXIS[X,SOUTH],AXIS[Y,WEST]]
 
 7) AXIS[Y,NORTH],AXIS[X,EAST]]
 
 8) AXIS[E(X),EAST],AXIS[N(Y),NORTH]]
 
 9) AXIS[x,NORTH],AXIS[y,EAST]]
 
 10)  AXIS[Easting,UNKNOWN],AXIS[Northing,UNKNOWN]]
 
 11)  AXIS[none,NORTH],AXIS[none,EAST]]
 
 12)  AXIS[X,UNKNOWN],AXIS[Y,UNKNOWN]]
 
 13)  AXIS[Northing,UNKNOWN],AXIS[Easting,UNKNOWN]]
 
  
 
 My conclusions: 
 
  
 
 Must not be flipped: 1, 2, 8
 
 Must be flipped: 3, 4, 9
 
 Probably should not be flipped: 10, 12
 
 Probably should be flipped: 11, 13
 
 No idea: 5, 6, 7  
 
  
 
 The most important system for me is EPSG:3067 and it has the WKT as in
 alternative 1:  AXIS[Easting,EAST],AXIS[Northing,NORTH]]
 
  
 
 -Jukka Rahkonen-
 
  
 
  
 
  
 
 Lähettäjä:mapserver-users-boun...@lists.osgeo.org
 [mailto:mapserver-users-boun...@lists.osgeo.org] Puolesta Olivier
 Courtin
 Lähetetty: 18. joulukuuta 2012 9:10
 Vastaanottaja: Mapserver-Users (mapserver-users@lists.osgeo.org)
 Aihe: Re: [mapserver-users] [TinyOWS] TinyOWS 1.1.0 and the old good
 axis order trouble
 
 
  
 
 On Mon, Dec 17, 2012 at 11:16 AM, Rahkonen Jukka
 jukka.rahko...@mmmtike.fi wrote:
 
 
 Hi Jukka,
 
 Nice to see you again here :)
 
 I have been running TinyOWS r558 for quite a long time because it is
 dealing almost right with the axis order of the projections I am
 commonly using. Now I had a fast try with the current TinyOWS 1.1.0
 version but unfortunately I realized that it is doing wrong thing by
 flipping the axis with urn:ogc:def:crs:EPSG::3067.
 
 
 On this topic we will not make any progress, without a regression
 test.
 (OGC CITE don't cover this issue)
 
 Could you provide from a single point stored in the database,
 requests and answers awaited ?
 
 I could also try to write it by myself too, 
 but will definitly need you to read it back,
 for all eastern stuff...
 
 
 What is the logic that TinyOWS is using when it decides
 whether the axis should be flipped or not  for WFS 1.1.0?
 
 
 Mainly 2 factors, as i recall:
  - if it's SRS or CRS (meaning EPSG: or
 urn:ogc:def:crs:EPSG::)
  - if SRTEXT contain both AXIS[X,NORTH]] and AXIS[Easting,EAST]]
  
 
 
 -- 
 Olivier
 
 
 ___
 mapserver-users mailing list
 mapserver-users@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/mapserver-users


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

[mapserver-users] [TinyOWS] TinyOWS 1.1.0 and the old good axis order trouble

[Rahkonen Jukka]

Hi,

I have been running TinyOWS r558 for quite a long time because it is dealing 
almost right with the axis order of the projections I am commonly using. Now I 
had a fast try with the current TinyOWS 1.1.0 version but unfortunately I 
realized that it is doing wrong thing by flipping the axis with 
urn:ogc:def:crs:EPSG::3067. That system is officially an Easting-Northing 
system and axis should not be flipped ever.  Also, TinyOWS does not flip the 
axes with urn:ogc:def:crs:EPSG::2393 which is officially a Northing-Easting 
system and axis should be flipped with WFS 1.1.0

I can see that TinyOWS is flipping the axis with WFS 1.1.0 if I I give 
srsName=urn:ogc:def:crs:EPSG::3067 or if I do not give it at all, which means 
the same because the uri-format is the default srsName.  Axis order is correct 
if I give it as srsName=EPSG:3067.  With EPSG:2393 axis are not flipped with 
either srsName format. What should be done next is to flip the behaviours of 
2393 and 3067.

What is the logic that TinyOWS is using when it decides whether the axis should 
be flipped or not  for WFS 1.1.0?  Can I manipulate TinyOWS somehow myself to 
behave in a correct way with EPSG:2393 and EPSG:3067 by editing something in 
the PostGIS or in  TinyOWS sources?  Another question is that is it guaranteed 
that axis order is handled similarly everywhere, also in filters? I mean that 
can I trust that once TinyOWS someday will again send  
urn:ogc:def:crs:EPSG::2393 data as Northing-Easting with WFS 1.1.0 it will then 
also treat the GML3 filters so that is knows that first comes Northing and then 
Easting?  Does the srsName format have the same meaning if filters, so that if 
short srsName is used then axis order is always Easting-Northing or lon-lat, 
but when the uri format is used then TinyOWS is trying to check the official 
axis with WFS 1.1.0?

-Jukka Rahkonen-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

[mapserver-users] [TinyOWS] Propertyname list does not work with Json

[Rahkonen Jukka]

Hi,

This request sends XML with just selected properties

http://hip.latuviitta.org/cgi-bin/tinyows?service=wfsversion=1.0.0request=GetFeaturetypename=lv:mml_railwayBBOX=246700,6780800,436400,6924000propertyname=sahko,the_geommaxfeatures=1

The same request with Json outpurformat gives all the properties
http://hip.latuviitta.org/cgi-bin/tinyows?service=wfsversion=1.0.0request=GetFeaturetypename=lv:mml_railwayBBOX=246700,6780800,436400,6924000propertyname=sahko,the_geommaxfeatures=1outputformat=application/json

Tested with TinyOWS 1.1.0 on Linux Ubuntu, PostgreSQL 9.0 and PostGIS 1.5.
 
Note that links probably work I have returned an older TinyOWS version on my 
server.  Behaviour with json is the same, though.  Shortened json would be most 
needed when using WFS for plain attribute queries like What is this parcel  
when the geometry of the parcel is unnecessary and the name and reference 
number would be enough.
 
-Jukka Rahkonen-

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

Re: [mapserver-users] [TinyOWS] TinyOWS 1.1.0 and the old good axis order trouble

[Olivier Courtin]

On Mon, Dec 17, 2012 at 11:16 AM, Rahkonen Jukka
jukka.rahko...@mmmtike.fiwrote:

Hi Jukka,

Nice to see you again here :)

I have been running TinyOWS r558 for quite a long time because it is
 dealing almost right with the axis order of the projections I am commonly
 using. Now I had a fast try with the current TinyOWS 1.1.0 version but
 unfortunately I realized that it is doing wrong thing by flipping the axis
 with urn:ogc:def:crs:EPSG::3067.


On this topic we will not make any progress, without a regression test.
(OGC CITE don't cover this issue)

Could you provide from a single point stored in the database,
requests and answers awaited ?

I could also try to write it by myself too,
but will definitly need you to read it back,
for all eastern stuff...

What is the logic that TinyOWS is using when it decides whether the axis
 should be flipped or not  for WFS 1.1.0?


Mainly 2 factors, as i recall:
 - if it's SRS or CRS (meaning EPSG: or urn:ogc:def:crs:EPSG::)
 - if SRTEXT contain both AXIS[X,NORTH]] and AXIS[Easting,EAST]]

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

Re: [mapserver-users] [TinyOWS] Propertyname list does not work with Json

[Olivier Courtin]

On Mon, Dec 17, 2012 at 3:34 PM, Rahkonen Jukka
jukka.rahko...@mmmtike.fiwrote:

Jukka,

Tested with TinyOWS 1.1.0 on Linux Ubuntu, PostgreSQL 9.0 and PostGIS 1.5.


I fixed a GeoJSON issue, just after 1.1.0 release,
could you give a try with current trunk to be sure,
it's not already fixed ?

Thanks !

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

Re: [mapserver-users] [TinyOWS] Inserting feature and XML schema validation

[Olivier Courtin]

On Mon, Nov 19, 2012 at 2:46 PM, Тимур Галиаскарович Суфиев 
t.suf...@acti.ru wrote:

Timur,

**
 I got the point: this is exactly the same fragment I've committed on Nov
 01, string src/wfs_get_feature.c:825:
 buffer_copy(id_name, ll-value);
 Previously (before commits from #19) ll-value contained layer's name, and
 now it contains ns-uri:layer-name. Should return from
 ns-uri:layer-name to layer-name somehow...


Thanks for the report and your code patch provided throught GitHub (and
commited)

For the record, this issue is relevant for GeoJSON id (GML one is safe)

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

Re: [mapserver-users] [TinyOWS] Inserting feature and XML schema validation

[Olivier Courtin]

Hi Timur,

XML validation is such issue-rich subject, so I have another question
 considering it :).


You noticed also this one ^^


 Recent TinyOWS commits (from 1st Nov till 13th, I don't know which one
 exactly is responsible) introduced some changes to feature ids naming, now
 I have the following error on features update/delete from OpenLayers:


#19 introduced that namespaces are also to be checked from Typename
parameter.
(prior (wrong) behaviour was just to ignore namespace prefix)



 [Mon Nov 19 16:03:30 2012] [ERROR] Element '{
 http://www.opengis.net/ogc}FeatureId', attribute 'fid': '
 http://www.tinyows.org/:cities.719' is not a valid value of the atomic
 type 'xs:ID'.

 Is 'ns-uri:layer-name.entity-integer-id' a new feature-id by design
 or something went wrong?


Should be only layer.name.entity-integer-id  (as ever)

Could you confirm that you are using current trunk version or 1.1.0 ?

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

Re: [mapserver-users] [TinyOWS] Inserting feature and XML schema validation

[Тимур Галиаскарович Суфиев]

Yes, it is 1.1.0. The head commit I'm building on is

commit 4e6220b43ffd33fb649afc9c954046e7bcbe185d
Author: Olivier Courtin olivier.cour...@oslandia.com
Date:   Wed Nov 14 01:07:34 2012 +0100

update NEWS since previous rc1


Best regards,
Timur Sufiev
  _  

From: Olivier Courtin [mailto:olivier.cour...@gmail.com]
To: mapserver-users@lists.osgeo.org
Sent: Mon, 19 Nov 2012 15:48:20 +0300
Subject: Re: [mapserver-users] [TinyOWS] Inserting feature and XML schema 
validation

Hi Timur,






XML validation is such issue-rich subject, so I have another question 
considering it :).



You noticed also this one ^^

 
Recent TinyOWS commits (from 1st Nov till 13th, I don't know which one exactly 
is responsible) introduced some changes to feature ids naming, now I have the 
following error on features update/delete from OpenLayers:



#19 introduced that namespaces are also to be checked from Typename parameter.
(prior (wrong) behaviour was just to ignore namespace prefix)

  

   
[Mon Nov 19 16:03:30 2012] [ERROR] Element 
'{http://www.opengis.net/ogc}FeatureId', attribute 'fid': 
'http://www.tinyows.org/:cities.719' is not a valid value of the atomic type 
'xs:ID'.

Is 'ns-uri:layer-name.entity-integer-id' a new feature-id by design or 
something went wrong?



Should be only layer.name.entity-integer-id  (as ever)


Could you confirm that you are using current trunk version or 1.1.0 ?

-- 
  Olivier___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] [TinyOWS] Inserting feature and XML schema validation

[Тимур Галиаскарович Суфиев]

Olivier,

I got the point: this is exactly the same fragment I've committed on Nov 01, 
string src/wfs_get_feature.c:825:
buffer_copy(id_name, ll-value);
Previously (before commits from #19) ll-value contained layer's name, and now 
it contains ns-uri:layer-name. Should return from ns-uri:layer-name to 
layer-name somehow...

Best regards,
Timur Sufiev
  _  

From: Olivier Courtin [mailto:olivier.cour...@gmail.com]
To: mapserver-users@lists.osgeo.org
Sent: Mon, 19 Nov 2012 15:48:20 +0300
Subject: Re: [mapserver-users] [TinyOWS] Inserting feature and XML schema 
validation

Hi Timur,






XML validation is such issue-rich subject, so I have another question 
considering it :).



You noticed also this one ^^

 
Recent TinyOWS commits (from 1st Nov till 13th, I don't know which one exactly 
is responsible) introduced some changes to feature ids naming, now I have the 
following error on features update/delete from OpenLayers:



#19 introduced that namespaces are also to be checked from Typename parameter.
(prior (wrong) behaviour was just to ignore namespace prefix)

  

   
[Mon Nov 19 16:03:30 2012] [ERROR] Element 
'{http://www.opengis.net/ogc}FeatureId', attribute 'fid': 
'http://www.tinyows.org/:cities.719' is not a valid value of the atomic type 
'xs:ID'.

Is 'ns-uri:layer-name.entity-integer-id' a new feature-id by design or 
something went wrong?



Should be only layer.name.entity-integer-id  (as ever)


Could you confirm that you are using current trunk version or 1.1.0 ?

-- 
  Olivier___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] [TinyOWS] Inserting feature and XML schema validation

[Тимур Галиаскарович Суфиев]

I found the problem (just in case it may be useful for someone): wfs layers in 
Javascript were using 

featureNS: http://www.tinyows.org;

while all layers in tinyows.xml used 

ns_uri=http://www.tinyows.org/;

Every symbol matters in deciding whether xml namespaces are the same, so adding 
trailing slash to Javascript solved my issue.

Best regards,
Timur Sufiev
  _  

From: Olivier Courtin [mailto:olivier.cour...@gmail.com]
To: mapserver-users@lists.osgeo.org
Sent: Wed, 07 Nov 2012 21:24:24 +0300
Subject: Re: [mapserver-users] [TinyOWS] Inserting feature and XML schema 
validation

On Wed, Nov 7, 2012 at 5:13 PM, Тимур Галиаскарович Суфиев t.suf...@acti.ru 
wrote:



Hi Timur,
   
This isn't the first question here about inserting features in TinyOWS, but I 
haven't found solution to my problem in archives.
  
and this xsd should make tinyows use element '{http://www.tinyows.org}cities' 
like '{http://www.opengis.net/gml}_Feature'
  
Where am I wrong and what should be changed in my setup?


Thanks for your detailled report,
first naive question, what about the tinyows.xml config file,
 and online_resource property ?
  
Next question, what happen, if you bypass schema validation, 
with: check_schema = 0   (in tinyows element)

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

Re: [mapserver-users] [TinyOWS] Inserting feature and XML schema validation

[Olivier Courtin]

On Fri, Nov 16, 2012 at 12:32 PM, Тимур Галиаскарович Суфиев 
t.suf...@acti.ru wrote:

 **
 I found the problem (just in case it may be useful for someone): wfs
 layers in Javascript were using

 featureNS: http://www.tinyows.org;

 while all layers in tinyows.xml used

 ns_uri=http://www.tinyows.org/;

 Every symbol matters in deciding whether xml namespaces are the same, so
 adding trailing slash to Javascript solved my issue.


Thanks Timur to post, for the record, your own answer !

And yes as it's an URI (and not a URL) every symbol matters...


Cheers,

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

Re: [mapserver-users] TinyOWS 1.1.0 release

[aho]

This is working for me on Windows with OpenLayers!
Really beautiful! :)

Thanks for helping Alexandre and Jukka!

Anna


Am 11/14/2012 1:55 AM, schrieb Olivier Courtin:

Hi all,

The 1.1.0 TinyOWS version is out.
Source code: http://www.tinyows.org/release/tinyows-1.1.0.tar.bz2

From 1.0.0 release the key point was to bugfixe, to improve again 
performances

and strict OGC standard implementation, and few userland improvements
on config file.


1.1.0 Changelog:
 - Add include_items and exclude_items config handling. To choose 
exactly which columns to retrieve (Serge Dikiy)
 - XSD max length and enumeration constraint handling (Serge Dikiy  
Alan Boudreault)
 - First real support of typename namespace provided in request 
(Olivier Courtin)
 - Generate PK value using PostgresSQL DEFAULT value if present (Serge 
Dikiy)
 - Add pkey configuration in layer config. Usefull for instance when 
retrieving data from a VIEW. (Serge Dikiy)

 - Buffer copy performance improve (Serge Dikiy)
 - Rewrite/fix max features handling (Olivier Courtin)
 - Extent layer's properties allowed to inherit (Olivier Courtin)
 - Several bugfixes as usual (special thanks to Andreas Peri, Serge 
Dikiy and Jukka Rahkonen for detailled reports)


Documentation was also refresh, including the OpenLayers HowTo.
http://ci.mapserver.org/job/docsmaster/lastSuccessfulBuild/artifact/build/html/en/tinyows/index.html#tinyows 




Enjoy,

--
Olivier


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


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

Re: [mapserver-users] tinyows

[aho]

Hi Alexandre,

ok, I changed to 'wfs:...', removed the Filter and got this in my -O 
test.txt file:


?xml version='1.0' encoding='UTF-8'?
ows:ExceptionReport
 xmlns='http://www.opengis.net/ows'
 xmlns:ows='http://www.opengis.net/ows'
 xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
 xsi:schemaLocation='http://www.opengis.net/ows 
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'

 version='1.1.0' language='en'
 ows:Exception exceptionCode='InvalidParameterValue' locator='request'
  ows:ExceptionTextxml isn't valid/ows:ExceptionText
 /ows:Exception
/ows:ExceptionReport

This is always the same actually.

This was the result and the adjusted wget command:

C:\Users\Annawget http://localhost/cgi-bin/tinyows.exe 
--post-data='wfs:GetFe
ature xmlns:wfs=http://www.opengis.net/wfs; service=WFS 
version=1.1.0 xsi:s
chemaLocation=http://www.opengis.net/wfs 
http://schemas.opengis.net/wfs/1.1.0/w
fs.xsd xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;wfs:Query 
typeNam
e=feature:frida srsName=EPSG:31467 
xmlns:feature=http://127.0.0.1/;/wfs:Q
uery/wfs:GetFeature' --header=Content-Type: application/xml; 
charset=UTF-8

-O C:\test.txt

SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
syswgetrc = C:\OSGeo4W\GnuWin32/etc/wgetrc
--2012-11-13 10:07:35-- 
http://localhost/cgi-bin/tinyows.exe%20--post-data='%3C

wfs:GetFeature%20xmlns:wfs=http://www.opengis.net/wfs%20service=WFS%20version=1.
1.0%20xsi:schemaLocation=http://www.opengis.net/wfs
Resolving localhost... 127.0.0.1, ::1
Connecting to localhost|127.0.0.1|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-11-13 10:07:35 ERROR 404: Not Found.

--2012-11-13 10:07:35-- 
http://schemas.opengis.net/wfs/1.1.0/wfs.xsd%20xmlns:xs

i=http://www.w3.org/2001/XMLSchema-instance%3E%3Cwfs:Query%20typeName=feature:fr
ida%20srsName=EPSG:31467%20xmlns:feature=http://127.0.0.1/%3E%3C/wfs:Query%3E%3C
/wfs:GetFeature%3E'%20--header=Content-Type:
Resolving schemas.opengis.net... 66.244.86.52
Connecting to schemas.opengis.net|66.244.86.52|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-11-13 10:07:35 ERROR 404: Not Found.

--2012-11-13 10:07:35--  http://application/xml;
Resolving application... failed: No data record of requested type.
wget: unable to resolve host address `application'
--2012-11-13 10:07:38--  ftp://charset=utf-8%20-o%20c/%5Ctest.txt
   = `%5Ctest.txt'
Resolving charset=utf-8 -o c... failed: No data record of requested type.
wget: unable to resolve host address `charset=utf-8 -o c'

Something is wrong with the host - maybe there is something missing in 
the tinyows configuration. Because now wget takes the application as the 
address instead of the coordinates of the bounding box!?
I took the same ns_prefix: feature because its also defined like that in 
my xml -- I changed it, because i read that recommendation somewhere - 
made no difference.





Am 11/12/2012 5:05 PM, schrieb Alexandre Dubé:

Anna,

  What does your C:\ms4w\Apache\logs\tinows.log file contain ?

  Also yeah you should use --post-data='wfs:GetFeature...' and not 
--post-data=wfs:GetFeature  If your dataset isn't too big, you 
could remove the ogc:Filter node.  Also, try replacing 
xmlns:feature=http://127.0.0.1/; by xmlns:tows=http://127.0.0.1/;.


HTH,

Alexandre


On 12-11-12 10:31 AM, aho wrote:

Hi Alexandre,

I already reinstalled pyhton and made the configuration of the apache 
server again. At least one thing I can exclude - specially because 
sooner or later I have to include it in another project which needs 
to run on a certain port. Anyhow... I also installed the wget and you 
are right, it helps a lot.
I took the GetFeature xml from chrome and constructed the following 
line:


wget http://localhost/cgi-bin/tinyows.exe; --post-data=wfs:GetF
eature xmlns:wfs=http://www.opengis.net/wfs; service=WFS 
version=1.0.0 outp
utFormat=application/json 
xsi:schemaLocation=http://schemas.opengis.net/wfs/1
.0.0/WFS-transaction.xsd 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
wfs:Query typeName=feature:frida 
xmlns:feature=http://127.0.0.1/;ogc:Filte
r 
xmlns:ogc=http://www.opengis.net/ogc;ogc:BBOXogc:PropertyNamethe_geom/o
gc:PropertyNamegml:Box xmlns:gml=http://www.opengis.net/gml; 
srsName=EPSG:31
467gml:coordinates decimal=. cs=, ts= 3413084,5782000 
3457916,5806000
/gml:coordinates/gml:Box/ogc:BBOX/ogc:Filter/wfs:Query/wfs:GetFeature 


 --header=Content-Type: application/xml; charset=UTF-8 -O C:/test.txt

wget returned:

SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
syswgetrc = C:\OSGeo4W\GnuWin32/etc/wgetrc
--2012-11-12 16:17:16--  http://localhost/cgi-bin/tinyows.exe
Resolving localhost... 127.0.0.1, ::1
Connecting to localhost|127.0.0.1|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/xml]
Saving to: `C:/test.txt'
[ =   ] 503 --.-K/s in 0s

2012-11-12 16:17:16 (11.4 MB/s) - `C:/test.txt' saved [503]
--2012-11-12 

Re: [mapserver-users] tinyows

[Rahkonen Jukka]

Hi,

On this page there are some WFS calls which do work against my TinyOWS server 
http://188.64.1.61/cgi-bin/tinyows.  Feel free to use it for testing.
http://latuviitta.org/Http-POST-ja-Filter.php

A very easy to use tool for testing POST requests is the Poster Firefox 
extension. This image shows how to use it. It is so simple that it should not 
matter that the texts I have added are in Finnish 
http://latuviitta.org/documents/WFS_POST_Poster.png.

-Jukka Rahkonen-

aho wrote:

 Hi Alexandre,
 
 ok, I changed to 'wfs:...', removed the Filter and got this in my -O test.txt
 file:
 
 ?xml version='1.0' encoding='UTF-8'?
 ows:ExceptionReport
   xmlns='http://www.opengis.net/ows'
   xmlns:ows='http://www.opengis.net/ows'
   xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
   xsi:schemaLocation='http://www.opengis.net/ows
 http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'
   version='1.1.0' language='en'
   ows:Exception exceptionCode='InvalidParameterValue' locator='request'
ows:ExceptionTextxml isn't valid/ows:ExceptionText
   /ows:Exception
 /ows:ExceptionReport
 
 This is always the same actually.
 
 This was the result and the adjusted wget command:
 
 C:\Users\Annawget http://localhost/cgi-bin/tinyows.exe
 --post-data='wfs:GetFe
 ature xmlns:wfs=http://www.opengis.net/wfs; service=WFS
 version=1.1.0 xsi:s
 chemaLocation=http://www.opengis.net/wfs
 http://schemas.opengis.net/wfs/1.1.0/w
 fs.xsd xmlns:xsi=http://www.w3.org/2001/XMLSchema-
 instancewfs:Query
 typeNam
 e=feature:frida srsName=EPSG:31467
 xmlns:feature=http://127.0.0.1/;/wfs:Q
 uery/wfs:GetFeature' --header=Content-Type: application/xml;
 charset=UTF-8
 -O C:\test.txt
 
 SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc =
 C:\OSGeo4W\GnuWin32/etc/wgetrc
 --2012-11-13 10:07:35--
 http://localhost/cgi-bin/tinyows.exe%20--post-data='%3C
 wfs:GetFeature%20xmlns:wfs=http://www.opengis.net/wfs%20service=WF
 S%20version=1.
 1.0%20xsi:schemaLocation=http://www.opengis.net/wfs
 Resolving localhost... 127.0.0.1, ::1
 Connecting to localhost|127.0.0.1|:80... connected.
 HTTP request sent, awaiting response... 404 Not Found
 2012-11-13 10:07:35 ERROR 404: Not Found.
 
 --2012-11-13 10:07:35--
 http://schemas.opengis.net/wfs/1.1.0/wfs.xsd%20xmlns:xs
 i=http://www.w3.org/2001/XMLSchema-
 instance%3E%3Cwfs:Query%20typeName=feature:fr
 ida%20srsName=EPSG:31467%20xmlns:feature=http://127.0.0.1/%3E%3C/wf
 s:Query%3E%3C
 /wfs:GetFeature%3E'%20--header=Content-Type:
 Resolving schemas.opengis.net... 66.244.86.52 Connecting to
 schemas.opengis.net|66.244.86.52|:80... connected.
 HTTP request sent, awaiting response... 404 Not Found
 2012-11-13 10:07:35 ERROR 404: Not Found.
 
 --2012-11-13 10:07:35--  http://application/xml; Resolving application... 
 failed:
 No data record of requested type.
 wget: unable to resolve host address `application'
 --2012-11-13 10:07:38--  ftp://charset=utf-8%20-o%20c/%5Ctest.txt
 = `%5Ctest.txt'
 Resolving charset=utf-8 -o c... failed: No data record of requested type.
 wget: unable to resolve host address `charset=utf-8 -o c'
 
 Something is wrong with the host - maybe there is something missing in the
 tinyows configuration. Because now wget takes the application as the
 address instead of the coordinates of the bounding box!?
 I took the same ns_prefix: feature because its also defined like that in my
 xml -- I changed it, because i read that recommendation somewhere - made
 no difference.
 
 
 
 
 Am 11/12/2012 5:05 PM, schrieb Alexandre Dubé:
  Anna,
 
What does your C:\ms4w\Apache\logs\tinows.log file contain ?
 
Also yeah you should use --post-data='wfs:GetFeature...' and not
  --post-data=wfs:GetFeature  If your dataset isn't too big, you
  could remove the ogc:Filter node.  Also, try replacing
  xmlns:feature=http://127.0.0.1/; by xmlns:tows=http://127.0.0.1/;.
 
  HTH,
 
  Alexandre
 
 
  On 12-11-12 10:31 AM, aho wrote:
  Hi Alexandre,
 
  I already reinstalled pyhton and made the configuration of the apache
  server again. At least one thing I can exclude - specially because
  sooner or later I have to include it in another project which needs
  to run on a certain port. Anyhow... I also installed the wget and you
  are right, it helps a lot.
  I took the GetFeature xml from chrome and constructed the following
  line:
 
  wget http://localhost/cgi-bin/tinyows.exe; --post-data=wfs:GetF
  eature xmlns:wfs=http://www.opengis.net/wfs; service=WFS
  version=1.0.0 outp
  utFormat=application/json
  xsi:schemaLocation=http://schemas.opengis.net/wfs/1
  .0.0/WFS-transaction.xsd
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  wfs:Query typeName=feature:frida
  xmlns:feature=http://127.0.0.1/;ogc:Filte
  r
 
 xmlns:ogc=http://www.opengis.net/ogc;ogc:BBOXogc:PropertyName
 th
  e_geom/o gc:PropertyNamegml:Box
  xmlns:gml=http://www.opengis.net/gml;
  srsName=EPSG:31
  467gml:coordinates decimal=. cs=, ts= 3413084,5782000
  3457916,5806000
 
 

Re: [mapserver-users] tinyows

[aho]

Hi Jukka,

thanks for your tips! But I don´t know where I am now. I think the 
host-problem was because of a wrong usage of wget. Anyhow - now it seems 
like I don´t have a problem anymore, which is not much better. Or at 
least I can say its a problem of openlayers?!...

I send:

wfs:GetFeature xmlns:wfs=http://www.opengis.net/wfs; service=WFS 
version=1.1.0 xsi:schemaLocation=http://www.opengis.net/wfs 
http://schemas.opengis.net/wfs/1.1.0/wfs.xsd; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;wfs:Query 
typeName=feature:frida srsName=EPSG:31467 
xmlns:feature=http://127.0.0.1/;ogc:Filter 
xmlns:ogc=http://www.opengis.net/ogc;ogc:BBOXogc:PropertyNamethe_geom/ogc:PropertyNamegml:Envelope 
xmlns:gml=http://www.opengis.net/gml; 
srsName=EPSG:31467gml:lowerCorner3413173.306773 
5782000/gml:lowerCornergml:upperCorner3457826.693227 
5806000/gml:upperCorner/gml:Envelope/ogc:BBOX/ogc:Filter/wfs:Query/wfs:GetFeature


to http://127.0.0.1/cgi-bin/tinyows.exe and got back:

?xml version='1.0' encoding='UTF-8'?
wfs:FeatureCollection
 xmlns:feature='http://127.0.0.1/'
 xmlns:wfs='http://www.opengis.net/wfs'
 xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
 xmlns:gml='http://www.opengis.net/gml'
 xmlns:xsd='http://www.w3.org/2001/XMLSchema'
 xmlns:ogc='http://www.opengis.net/ogc'
 xmlns:xlink='http://www.w3.org/1999/xlink'
 xmlns:ows='http://www.opengis.net/ows'
 xsi:schemaLocation='http://127.0.0.1/
http://127.0.0.1/cgi-bin/tinyows.xml?service=WFSamp;version=1.1.0amp;request=DescribeFeatureTypeamp;Typename=feature:frida 
http://www.opengis.net/wfs

   http://schemas.opengis.net/wfs/1.1.0/wfs.xsd
   http://www.opengis.net/gml
   http://schemas.opengis.net/gml/3.1.1/base/gml.xsd'

gml:boundedBy
  gml:Envelope srsName=EPSG:31467gml:lowerCorner5788323.50 
3427065.25/gml:lowerCornergml:upperCorner5800691.50 
3443999.25/gml:upperCorner/gml:Envelope

/gml:boundedBy
  gml:featureMember
   feature:frida gml:id=frida.1
   feature:gfshapeid1/feature:gfshapeid
   feature:gftypid1/feature:gftypid
   feature:the_geomgml:MultiSurface 
srsName=EPSG:31467gml:surfaceMembergml:Polygongml:exteriorgml:LinearRinggml:posList 
srsDimension=23429858 5799440 3429874 5799496 3429905 5799504 3429973 
5799561 3430035 5799577 3430032 5799639 3430140 5799691 3430147...


and so on...
so now I know - my problem is not in the configuration of my tinyows.xml 
and the get request is constructed correctly from my openlayers code. So 
where is this error that there is an invalid parameter which is always 
returned in my test.html when i am sending the same get feature request?


Am 11/13/2012 10:41 AM, schrieb Rahkonen Jukka:

Hi,

On this page there are some WFS calls which do work against my TinyOWS server 
http://188.64.1.61/cgi-bin/tinyows.  Feel free to use it for testing.
http://latuviitta.org/Http-POST-ja-Filter.php

A very easy to use tool for testing POST requests is the Poster Firefox 
extension. This image shows how to use it. It is so simple that it should not 
matter that the texts I have added are in Finnish 
http://latuviitta.org/documents/WFS_POST_Poster.png.

-Jukka Rahkonen-

aho wrote:


Hi Alexandre,

ok, I changed to 'wfs:...', removed the Filter and got this in my -O test.txt
file:

?xml version='1.0' encoding='UTF-8'?
ows:ExceptionReport
   xmlns='http://www.opengis.net/ows'
   xmlns:ows='http://www.opengis.net/ows'
   xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
   xsi:schemaLocation='http://www.opengis.net/ows
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'
   version='1.1.0' language='en'
   ows:Exception exceptionCode='InvalidParameterValue' locator='request'
ows:ExceptionTextxml isn't valid/ows:ExceptionText
   /ows:Exception
/ows:ExceptionReport

This is always the same actually.

This was the result and the adjusted wget command:

C:\Users\Annawget http://localhost/cgi-bin/tinyows.exe
--post-data='wfs:GetFe
ature xmlns:wfs=http://www.opengis.net/wfs; service=WFS
version=1.1.0 xsi:s
chemaLocation=http://www.opengis.net/wfs
http://schemas.opengis.net/wfs/1.1.0/w
fs.xsd xmlns:xsi=http://www.w3.org/2001/XMLSchema-
instancewfs:Query
typeNam
e=feature:frida srsName=EPSG:31467
xmlns:feature=http://127.0.0.1/;/wfs:Q
uery/wfs:GetFeature' --header=Content-Type: application/xml;
charset=UTF-8
-O C:\test.txt

SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc =
C:\OSGeo4W\GnuWin32/etc/wgetrc
--2012-11-13 10:07:35--
http://localhost/cgi-bin/tinyows.exe%20--post-data='%3C
wfs:GetFeature%20xmlns:wfs=http://www.opengis.net/wfs%20service=WF
S%20version=1.
1.0%20xsi:schemaLocation=http://www.opengis.net/wfs
Resolving localhost... 127.0.0.1, ::1
Connecting to localhost|127.0.0.1|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-11-13 10:07:35 ERROR 404: Not Found.

--2012-11-13 10:07:35--
http://schemas.opengis.net/wfs/1.1.0/wfs.xsd%20xmlns:xs
i=http://www.w3.org/2001/XMLSchema-
instance%3E%3Cwfs:Query%20typeName=feature:fr

Re: [mapserver-users] tinyows

[aho]

Ok, I left the poster and I am back to the tinyows.log file:

[Tue Nov 13 13:35:51 2012] [ERROR] Element 
'{http://www.w3.org/2001/XMLSchema}import': Failed to locate a schema at 
location 
'http://127.0.0.1/cgi-bin/tinyows.xml?service=WFSrequest=DescribeFeatureTypeversion=1.1.0'. 
Skipping the import.


I actually defined my tinyows.xml in C:/ms4w/Apache/apps/tinyows.xml in 
the httpd_tinyows.conf. Do you think this could be the problem?


Am 11/13/2012 10:41 AM, schrieb Rahkonen Jukka:

Hi,

On this page there are some WFS calls which do work against my TinyOWS server 
http://188.64.1.61/cgi-bin/tinyows.  Feel free to use it for testing.
http://latuviitta.org/Http-POST-ja-Filter.php

A very easy to use tool for testing POST requests is the Poster Firefox 
extension. This image shows how to use it. It is so simple that it should not 
matter that the texts I have added are in Finnish 
http://latuviitta.org/documents/WFS_POST_Poster.png.

-Jukka Rahkonen-

aho wrote:


Hi Alexandre,

ok, I changed to 'wfs:...', removed the Filter and got this in my -O test.txt
file:

?xml version='1.0' encoding='UTF-8'?
ows:ExceptionReport
   xmlns='http://www.opengis.net/ows'
   xmlns:ows='http://www.opengis.net/ows'
   xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
   xsi:schemaLocation='http://www.opengis.net/ows
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'
   version='1.1.0' language='en'
   ows:Exception exceptionCode='InvalidParameterValue' locator='request'
ows:ExceptionTextxml isn't valid/ows:ExceptionText
   /ows:Exception
/ows:ExceptionReport

This is always the same actually.

This was the result and the adjusted wget command:

C:\Users\Annawget http://localhost/cgi-bin/tinyows.exe
--post-data='wfs:GetFe
ature xmlns:wfs=http://www.opengis.net/wfs; service=WFS
version=1.1.0 xsi:s
chemaLocation=http://www.opengis.net/wfs
http://schemas.opengis.net/wfs/1.1.0/w
fs.xsd xmlns:xsi=http://www.w3.org/2001/XMLSchema-
instancewfs:Query
typeNam
e=feature:frida srsName=EPSG:31467
xmlns:feature=http://127.0.0.1/;/wfs:Q
uery/wfs:GetFeature' --header=Content-Type: application/xml;
charset=UTF-8
-O C:\test.txt

SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc =
C:\OSGeo4W\GnuWin32/etc/wgetrc
--2012-11-13 10:07:35--
http://localhost/cgi-bin/tinyows.exe%20--post-data='%3C
wfs:GetFeature%20xmlns:wfs=http://www.opengis.net/wfs%20service=WF
S%20version=1.
1.0%20xsi:schemaLocation=http://www.opengis.net/wfs
Resolving localhost... 127.0.0.1, ::1
Connecting to localhost|127.0.0.1|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-11-13 10:07:35 ERROR 404: Not Found.

--2012-11-13 10:07:35--
http://schemas.opengis.net/wfs/1.1.0/wfs.xsd%20xmlns:xs
i=http://www.w3.org/2001/XMLSchema-
instance%3E%3Cwfs:Query%20typeName=feature:fr
ida%20srsName=EPSG:31467%20xmlns:feature=http://127.0.0.1/%3E%3C/wf
s:Query%3E%3C
/wfs:GetFeature%3E'%20--header=Content-Type:
Resolving schemas.opengis.net... 66.244.86.52 Connecting to
schemas.opengis.net|66.244.86.52|:80... connected.
HTTP request sent, awaiting response... 404 Not Found
2012-11-13 10:07:35 ERROR 404: Not Found.

--2012-11-13 10:07:35--  http://application/xml; Resolving application... 
failed:
No data record of requested type.
wget: unable to resolve host address `application'
--2012-11-13 10:07:38--  ftp://charset=utf-8%20-o%20c/%5Ctest.txt
 = `%5Ctest.txt'
Resolving charset=utf-8 -o c... failed: No data record of requested type.
wget: unable to resolve host address `charset=utf-8 -o c'

Something is wrong with the host - maybe there is something missing in the
tinyows configuration. Because now wget takes the application as the
address instead of the coordinates of the bounding box!?
I took the same ns_prefix: feature because its also defined like that in my
xml -- I changed it, because i read that recommendation somewhere - made
no difference.




Am 11/12/2012 5:05 PM, schrieb Alexandre Dubé:

Anna,

   What does your C:\ms4w\Apache\logs\tinows.log file contain ?

   Also yeah you should use --post-data='wfs:GetFeature...' and not
--post-data=wfs:GetFeature  If your dataset isn't too big, you
could remove the ogc:Filter node.  Also, try replacing
xmlns:feature=http://127.0.0.1/; by xmlns:tows=http://127.0.0.1/;.

HTH,

Alexandre


On 12-11-12 10:31 AM, aho wrote:

Hi Alexandre,

I already reinstalled pyhton and made the configuration of the apache
server again. At least one thing I can exclude - specially because
sooner or later I have to include it in another project which needs
to run on a certain port. Anyhow... I also installed the wget and you
are right, it helps a lot.
I took the GetFeature xml from chrome and constructed the following
line:

wget http://localhost/cgi-bin/tinyows.exe; --post-data=wfs:GetF
eature xmlns:wfs=http://www.opengis.net/wfs; service=WFS
version=1.0.0 outp
utFormat=application/json
xsi:schemaLocation=http://schemas.opengis.net/wfs/1
.0.0/WFS-transaction.xsd

[mapserver-users] TinyOWS 1.1.0 release

[Olivier Courtin]

Hi all,

The 1.1.0 TinyOWS version is out.
Source code: http://www.tinyows.org/release/tinyows-1.1.0.tar.bz2

From 1.0.0 release the key point was to bugfixe, to improve again
performances
and strict OGC standard implementation, and few userland improvements
on config file.


1.1.0 Changelog:
 - Add include_items and exclude_items config handling. To choose exactly
which columns to retrieve (Serge Dikiy)
 - XSD max length and enumeration constraint handling (Serge Dikiy  Alan
Boudreault)
 - First real support of typename namespace provided in request (Olivier
Courtin)
 - Generate PK value using PostgresSQL DEFAULT value if present (Serge
Dikiy)
 - Add pkey configuration in layer config. Usefull for instance when
retrieving data from a VIEW. (Serge Dikiy)
 - Buffer copy performance improve (Serge Dikiy)
 - Rewrite/fix max features handling (Olivier Courtin)
 - Extent layer's properties allowed to inherit (Olivier Courtin)
 - Several bugfixes as usual (special thanks to Andreas Peri, Serge Dikiy
and Jukka Rahkonen for detailled reports)

Documentation was also refresh, including the OpenLayers HowTo.
http://ci.mapserver.org/job/docsmaster/lastSuccessfulBuild/artifact/build/html/en/tinyows/index.html#tinyows



Enjoy,

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

Re: [mapserver-users] tinyows

[aho]

Hi Alexandre,

thanks for the good hints! This is really great! I think its not my 
tinyows.xml or the Openlayers... but the error message tells something 
else somehow... :(...  I changed it to the following:

xml configuration of tinyows:

tinyows online_resource=http://127.0.0.1/cgi-bin/tinyows.exe;
   schema_dir=C:\ms4w\apps\tinyows\schema\
   log=C:\ms4w\Apache\logs\tinows.log log_level=15
pg host=127.0.0.1 user=postgres password=postgres 
dbname=tinyows port=5432/

metadata name=TinyOWS Server
  title=TinyOWS Server - WFS-T Frida Service /
contact name=TinyOWS Server
 site=http://www.tinyows.org/;
 email=tinyows-us...@lists.maptools.org /
layer retrievable=1
writable=1
   ns_prefix=tows
   ns_uri=http://127.0.0.1/;
   name=frida
   title=Frida Parks /
/tinyows

and the OpenLayers code:

  map = new OpenLayers.Map('map', {
  projection: new OpenLayers.Projection(EPSG:31467),
  units: m,
  maxResolution: auto,
  maxExtent: new OpenLayers.Bounds(3427000,5788000,3444000,580),
  controls: [
  new OpenLayers.Control.PanZoom()
  ]
  });
  var osm = new OpenLayers.Layer.WMS(
  OSM by Omniscale WMS,
  http://osm.omniscale.net/proxy/service;,
  {layers: 'osm', format: 'image/jpeg'},
  {projection:EPSG:31467,  units: m, maxResolution: auto, 
maxExtent: new OpenLayers.Bounds(3427000,5788000,3444000,580)}

  );
  var saveStrategy = new OpenLayers.Strategy.Save();
  saveStrategy.events.register(success, '', showSuccessMsg);
  saveStrategy.events.register(fail, '', showFailureMsg);
  var wfs = new OpenLayers.Layer.Vector(Editable Features, {
  strategies: [new OpenLayers.Strategy.BBOX(), saveStrategy],
  projection: new OpenLayers.Projection(EPSG:31467),
  protocol: new OpenLayers.Protocol.WFS({
version:1.1.0,
  url: http://127.0.0.1/cgi-bin/tinyows.exe;,
  featureType: frida,
  outputformat:application/json,
  readFormat: new OpenLayers.Format.GeoJSON(),
  featureNS: http://127.0.0.1/;,
  geometryName: the_geom
  })
});
  map.addLayers([osm, wfs]);

  map.zoomToMaxExtent();

The layer is actually in  31467 - I want to get it working for the frida 
parks example. I reduced everything else in my javascript file.


But I think I have a problem with my configuration. I am setting the 
following in OpenLayers: OpenLayers.ProxyHost = 
/cgi-bin/proxy.cgi?url=; and I saw that you were actually refering to 
a fcgi file in your config.xml. I thought I could define there the path 
to the tinyows.exe like this: http://127.0.0.1/cgi-bin/tinyows.exe - do 
I also give the proxy there?
Could you send me the content of your weather-sites-tinyows-1.0.0.fcgi 
file? I have to say that I can´t follow your instructions for setting 
the environment variable - I made that via the control Panel :) - and 
the ScriptAlias.


I have to install the wget first on windows, but thanks for that hint - 
I will try it after the restart now!


Thanks in advance,
Anna





Am 11/9/2012 2:50 PM, schrieb Alexandre Dubé:
### The apache config used to bind TinyOWS to this config using a 
different url
FastCgiServer /usr/lib/cgi-bin/tinyows-1.0.0-weather-sites.fcgi 
-initial-env 
TINYOWS_CONFIG_FILE=/opt/labs/weather-sites/etc/tinyows/config.xml
ScriptAlias /weather-sites-tinyows-1.0.0.fcgi 
/usr/lib/cgi-bin/tinyows-1.0.0-weather-sites.fcgi 


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

Re: [mapserver-users] tinyows

[Alexandre Dubé]

Hi Anna,

  While working locally, you don't need to set an 
OpenLayers.ProxyHost.  Put comments // in front of it for now.


  tinyows-1.0.0-weather-sites.fcgi - copy your tinyows.exe file giving 
it the name you want.  In Linux, you could use a symbolic link, like I 
did.  Here's the apache config for it.  It does 2 things : it enables 
FastCgi and set the TINYOWS_CONFIG_FILE env variable for this link to 
use a specific .xml config file.


###
FastCgiServer /usr/lib/cgi-bin/tinyows-1.0.0-weather-sites.fcgi 
-initial-env 
TINYOWS_CONFIG_FILE=/opt/labs/weather-sites/etc/tinyows/config.xml
ScriptAlias /weather-sites-tinyows-1.0.0.fcgi 
/usr/lib/cgi-bin/tinyows-1.0.0-weather-sites.fcgi

###

Once you start using wget, the idea is to edit the xml GetFeature 
request sent and/or the config.xml file as you try it to quickly see 
what causes things to not work.  Point to tinyows for now, you your 
proxy (yet), i.e. make your tinyows work first.


Best regards,

Alexandre


On 12-11-12 04:05 AM, aho wrote:

Hi Alexandre,

thanks for the good hints! This is really great! I think its not my 
tinyows.xml or the Openlayers... but the error message tells something 
else somehow... :(...  I changed it to the following:

xml configuration of tinyows:

tinyows online_resource=http://127.0.0.1/cgi-bin/tinyows.exe;
   schema_dir=C:\ms4w\apps\tinyows\schema\
   log=C:\ms4w\Apache\logs\tinows.log log_level=15
pg host=127.0.0.1 user=postgres password=postgres 
dbname=tinyows port=5432/

metadata name=TinyOWS Server
  title=TinyOWS Server - WFS-T Frida Service /
contact name=TinyOWS Server
 site=http://www.tinyows.org/;
 email=tinyows-us...@lists.maptools.org /
layer retrievable=1
writable=1
   ns_prefix=tows
   ns_uri=http://127.0.0.1/;
   name=frida
   title=Frida Parks /
/tinyows

and the OpenLayers code:

  map = new OpenLayers.Map('map', {
  projection: new OpenLayers.Projection(EPSG:31467),
  units: m,
  maxResolution: auto,
  maxExtent: new OpenLayers.Bounds(3427000,5788000,3444000,580),
  controls: [
  new OpenLayers.Control.PanZoom()
  ]
  });
  var osm = new OpenLayers.Layer.WMS(
  OSM by Omniscale WMS,
  http://osm.omniscale.net/proxy/service;,
  {layers: 'osm', format: 'image/jpeg'},
  {projection:EPSG:31467,  units: m, maxResolution: auto, 
maxExtent: new OpenLayers.Bounds(3427000,5788000,3444000,580)}

  );
  var saveStrategy = new OpenLayers.Strategy.Save();
  saveStrategy.events.register(success, '', showSuccessMsg);
  saveStrategy.events.register(fail, '', showFailureMsg);
  var wfs = new OpenLayers.Layer.Vector(Editable Features, {
  strategies: [new OpenLayers.Strategy.BBOX(), saveStrategy],
  projection: new OpenLayers.Projection(EPSG:31467),
  protocol: new OpenLayers.Protocol.WFS({
version:1.1.0,
  url: http://127.0.0.1/cgi-bin/tinyows.exe;,
  featureType: frida,
  outputformat:application/json,
  readFormat: new OpenLayers.Format.GeoJSON(),
  featureNS: http://127.0.0.1/;,
  geometryName: the_geom
  })
});
  map.addLayers([osm, wfs]);

  map.zoomToMaxExtent();

The layer is actually in  31467 - I want to get it working for the 
frida parks example. I reduced everything else in my javascript file.


But I think I have a problem with my configuration. I am setting the 
following in OpenLayers: OpenLayers.ProxyHost = 
/cgi-bin/proxy.cgi?url=; and I saw that you were actually refering 
to a fcgi file in your config.xml. I thought I could define there the 
path to the tinyows.exe like this: 
http://127.0.0.1/cgi-bin/tinyows.exe - do I also give the proxy there?
Could you send me the content of your weather-sites-tinyows-1.0.0.fcgi 
file? I have to say that I can´t follow your instructions for setting 
the environment variable - I made that via the control Panel :) - and 
the ScriptAlias.


I have to install the wget first on windows, but thanks for that hint 
- I will try it after the restart now!


Thanks in advance,
Anna





Am 11/9/2012 2:50 PM, schrieb Alexandre Dubé:
### The apache config used to bind TinyOWS to this config using a 
different url
FastCgiServer /usr/lib/cgi-bin/tinyows-1.0.0-weather-sites.fcgi 
-initial-env 
TINYOWS_CONFIG_FILE=/opt/labs/weather-sites/etc/tinyows/config.xml
ScriptAlias /weather-sites-tinyows-1.0.0.fcgi 
/usr/lib/cgi-bin/tinyows-1.0.0-weather-sites.fcgi 





--
Alexandre Dubé
Mapgears
www.mapgears.com

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

Re: [mapserver-users] tinyows

[aho]

Hi Alexandre,

I already reinstalled pyhton and made the configuration of the apache 
server again. At least one thing I can exclude - specially because 
sooner or later I have to include it in another project which needs to 
run on a certain port. Anyhow... I also installed the wget and you are 
right, it helps a lot.

I took the GetFeature xml from chrome and constructed the following line:

wget http://localhost/cgi-bin/tinyows.exe; --post-data=wfs:GetF
eature xmlns:wfs=http://www.opengis.net/wfs; service=WFS 
version=1.0.0 outp
utFormat=application/json 
xsi:schemaLocation=http://schemas.opengis.net/wfs/1
.0.0/WFS-transaction.xsd 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
wfs:Query typeName=feature:frida 
xmlns:feature=http://127.0.0.1/;ogc:Filte
r 
xmlns:ogc=http://www.opengis.net/ogc;ogc:BBOXogc:PropertyNamethe_geom/o
gc:PropertyNamegml:Box xmlns:gml=http://www.opengis.net/gml; 
srsName=EPSG:31
467gml:coordinates decimal=. cs=, ts= 3413084,5782000 
3457916,5806000

/gml:coordinates/gml:Box/ogc:BBOX/ogc:Filter/wfs:Query/wfs:GetFeature
 --header=Content-Type: application/xml; charset=UTF-8 -O C:/test.txt

wget returned:

SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
syswgetrc = C:\OSGeo4W\GnuWin32/etc/wgetrc
--2012-11-12 16:17:16--  http://localhost/cgi-bin/tinyows.exe
Resolving localhost... 127.0.0.1, ::1
Connecting to localhost|127.0.0.1|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/xml]
Saving to: `C:/test.txt'
[ =   ] 503 --.-K/s   in 0s

2012-11-12 16:17:16 (11.4 MB/s) - `C:/test.txt' saved [503]
--2012-11-12 16:17:16-- 
http://%3E3413084,5782000%203457916,5806000%3C/gml:coor

dinates%3E%3C/gml:Box%3E%3C/ogc:BBOX%3E%3C/ogc:Filter%3E%3C/wfs:Query%3E%3C/wfs:
GetFeature%3E
Resolving 3413084,5782000 3457916,5806000... failed: No data record of 
request

ed type.
wget: unable to resolve host address `3413084,5782000 3457916,5806000'
FINISHED --2012-11-12 16:17:17--
Downloaded: 1 files, 503 in 0s (11.4 MB/s)


I have really no idea why it is using the coordinates of the bounding 
box for the host?! I thought it would be a problem of wget and the 
quotation marks... but changing that to ' did not solve the problem.
In my test.txt is still the same response: invalid xml. Nothing else 
unfortunately. I think its a problem in my openlayers configuration - I 
check the spatial reference again; maybe I can also set the bbox or 
something. I will see...


If you or anyone else has an idea I will be very happy!
Anna

Am 11/12/2012 2:42 PM, schrieb Alexandre Dubé:

Hi Anna,

  While working locally, you don't need to set an 
OpenLayers.ProxyHost.  Put comments // in front of it for now.


  tinyows-1.0.0-weather-sites.fcgi - copy your tinyows.exe file 
giving it the name you want.  In Linux, you could use a symbolic link, 
like I did.  Here's the apache config for it.  It does 2 things : it 
enables FastCgi and set the TINYOWS_CONFIG_FILE env variable for this 
link to use a specific .xml config file.


###
FastCgiServer /usr/lib/cgi-bin/tinyows-1.0.0-weather-sites.fcgi 
-initial-env 
TINYOWS_CONFIG_FILE=/opt/labs/weather-sites/etc/tinyows/config.xml
ScriptAlias /weather-sites-tinyows-1.0.0.fcgi 
/usr/lib/cgi-bin/tinyows-1.0.0-weather-sites.fcgi

###

Once you start using wget, the idea is to edit the xml GetFeature 
request sent and/or the config.xml file as you try it to quickly see 
what causes things to not work.  Point to tinyows for now, you your 
proxy (yet), i.e. make your tinyows work first.


Best regards,

Alexandre


On 12-11-12 04:05 AM, aho wrote:

Hi Alexandre,

thanks for the good hints! This is really great! I think its not my 
tinyows.xml or the Openlayers... but the error message tells 
something else somehow... :(...  I changed it to the following:

xml configuration of tinyows:

tinyows online_resource=http://127.0.0.1/cgi-bin/tinyows.exe;
   schema_dir=C:\ms4w\apps\tinyows\schema\
   log=C:\ms4w\Apache\logs\tinows.log log_level=15
pg host=127.0.0.1 user=postgres password=postgres 
dbname=tinyows port=5432/

metadata name=TinyOWS Server
  title=TinyOWS Server - WFS-T Frida Service /
contact name=TinyOWS Server
 site=http://www.tinyows.org/;
 email=tinyows-us...@lists.maptools.org /
layer retrievable=1
writable=1
   ns_prefix=tows
   ns_uri=http://127.0.0.1/;
   name=frida
   title=Frida Parks /
/tinyows

and the OpenLayers code:

  map = new OpenLayers.Map('map', {
  projection: new OpenLayers.Projection(EPSG:31467),
  units: m,
  maxResolution: auto,
  maxExtent: new OpenLayers.Bounds(3427000,5788000,3444000,580),
  controls: [
  new OpenLayers.Control.PanZoom()
  ]
  });
  var osm = new OpenLayers.Layer.WMS(
  OSM by Omniscale WMS,
  http://osm.omniscale.net/proxy/service;,
  {layers: 'osm', format: 'image/jpeg'},
  {projection:EPSG:31467,  units: m, maxResolution: auto, 
maxExtent: new 

Re: [mapserver-users] tinyows

[Alexandre Dubé]

Anna,

  What does your C:\ms4w\Apache\logs\tinows.log file contain ?

  Also yeah you should use --post-data='wfs:GetFeature...' and not 
--post-data=wfs:GetFeature  If your dataset isn't too big, you 
could remove the ogc:Filter node.  Also, try replacing 
xmlns:feature=http://127.0.0.1/; by xmlns:tows=http://127.0.0.1/;.


HTH,

Alexandre


On 12-11-12 10:31 AM, aho wrote:

Hi Alexandre,

I already reinstalled pyhton and made the configuration of the apache 
server again. At least one thing I can exclude - specially because 
sooner or later I have to include it in another project which needs to 
run on a certain port. Anyhow... I also installed the wget and you are 
right, it helps a lot.

I took the GetFeature xml from chrome and constructed the following line:

wget http://localhost/cgi-bin/tinyows.exe; --post-data=wfs:GetF
eature xmlns:wfs=http://www.opengis.net/wfs; service=WFS 
version=1.0.0 outp
utFormat=application/json 
xsi:schemaLocation=http://schemas.opengis.net/wfs/1
.0.0/WFS-transaction.xsd 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
wfs:Query typeName=feature:frida 
xmlns:feature=http://127.0.0.1/;ogc:Filte
r 
xmlns:ogc=http://www.opengis.net/ogc;ogc:BBOXogc:PropertyNamethe_geom/o
gc:PropertyNamegml:Box xmlns:gml=http://www.opengis.net/gml; 
srsName=EPSG:31
467gml:coordinates decimal=. cs=, ts= 3413084,5782000 
3457916,5806000
/gml:coordinates/gml:Box/ogc:BBOX/ogc:Filter/wfs:Query/wfs:GetFeature 


 --header=Content-Type: application/xml; charset=UTF-8 -O C:/test.txt

wget returned:

SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
syswgetrc = C:\OSGeo4W\GnuWin32/etc/wgetrc
--2012-11-12 16:17:16--  http://localhost/cgi-bin/tinyows.exe
Resolving localhost... 127.0.0.1, ::1
Connecting to localhost|127.0.0.1|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/xml]
Saving to: `C:/test.txt'
[ =   ] 503 --.-K/s in 0s

2012-11-12 16:17:16 (11.4 MB/s) - `C:/test.txt' saved [503]
--2012-11-12 16:17:16-- 
http://%3E3413084,5782000%203457916,5806000%3C/gml:coor
dinates%3E%3C/gml:Box%3E%3C/ogc:BBOX%3E%3C/ogc:Filter%3E%3C/wfs:Query%3E%3C/wfs: 


GetFeature%3E
Resolving 3413084,5782000 3457916,5806000... failed: No data record 
of request

ed type.
wget: unable to resolve host address `3413084,5782000 3457916,5806000'
FINISHED --2012-11-12 16:17:17--
Downloaded: 1 files, 503 in 0s (11.4 MB/s)


I have really no idea why it is using the coordinates of the bounding 
box for the host?! I thought it would be a problem of wget and the 
quotation marks... but changing that to ' did not solve the problem.
In my test.txt is still the same response: invalid xml. Nothing else 
unfortunately. I think its a problem in my openlayers configuration - 
I check the spatial reference again; maybe I can also set the bbox or 
something. I will see...


If you or anyone else has an idea I will be very happy!
Anna

Am 11/12/2012 2:42 PM, schrieb Alexandre Dubé:

Hi Anna,

  While working locally, you don't need to set an 
OpenLayers.ProxyHost.  Put comments // in front of it for now.


  tinyows-1.0.0-weather-sites.fcgi - copy your tinyows.exe file 
giving it the name you want.  In Linux, you could use a symbolic 
link, like I did.  Here's the apache config for it.  It does 2 things 
: it enables FastCgi and set the TINYOWS_CONFIG_FILE env variable for 
this link to use a specific .xml config file.


###
FastCgiServer /usr/lib/cgi-bin/tinyows-1.0.0-weather-sites.fcgi 
-initial-env 
TINYOWS_CONFIG_FILE=/opt/labs/weather-sites/etc/tinyows/config.xml
ScriptAlias /weather-sites-tinyows-1.0.0.fcgi 
/usr/lib/cgi-bin/tinyows-1.0.0-weather-sites.fcgi

###

Once you start using wget, the idea is to edit the xml GetFeature 
request sent and/or the config.xml file as you try it to quickly see 
what causes things to not work.  Point to tinyows for now, you your 
proxy (yet), i.e. make your tinyows work first.


Best regards,

Alexandre


On 12-11-12 04:05 AM, aho wrote:

Hi Alexandre,

thanks for the good hints! This is really great! I think its not my 
tinyows.xml or the Openlayers... but the error message tells 
something else somehow... :(...  I changed it to the following:

xml configuration of tinyows:

tinyows online_resource=http://127.0.0.1/cgi-bin/tinyows.exe;
   schema_dir=C:\ms4w\apps\tinyows\schema\
   log=C:\ms4w\Apache\logs\tinows.log log_level=15
pg host=127.0.0.1 user=postgres password=postgres 
dbname=tinyows port=5432/

metadata name=TinyOWS Server
  title=TinyOWS Server - WFS-T Frida Service /
contact name=TinyOWS Server
 site=http://www.tinyows.org/;
 email=tinyows-us...@lists.maptools.org /
layer retrievable=1
writable=1
   ns_prefix=tows
   ns_uri=http://127.0.0.1/;
   name=frida
   title=Frida Parks /
/tinyows

and the OpenLayers code:

  map = new OpenLayers.Map('map', {
  projection: new OpenLayers.Projection(EPSG:31467),
  units: m,
  maxResolution: 

Re: [mapserver-users] tinyows

[aho]

Hi again,

I am still searching and not finding something. I setup everything again 
with the WFS-T tutorial. Now I am getting the following error message:


[Thu Nov 08 16:32:21 2012] [ERROR] local list type: A type, derived by 
list or union, must have the simple ur-type definition as base type, not 
'{http://www.opengis.net/gml}doubleOrNullList'.


Am I right with this forum? Because actually nobody replies.




Am 11/6/2012 1:30 PM, schrieb aho:

Hey,

I still havn´t found the problem with the tinyows - but at the moment 
there is no error message when i am loading the wfs. Also fiddler 
doesn´t list the tinyows.exe anymore. But my proxy is correct - I can 
load it via uDig and ArcMap. QGIS has a problem, but there is not a 
single error in the tinyows log file - just events and sqls are 
listed, that looks quite good. With Open layers there is nothing 
logged - it seems like the request is not send.


Is there any limitation for the version? I downloaded the latest 
(2.12) one, but on the tinyows page is version 2.09 listed?!


Kind regards

Am 11/2/2012 3:29 PM, schrieb Serge Dikiy:

Hi,

http://translate.google.com/translate?sl=rutl=enjs=nprev=_thl=enie=UTF-8layout=2eotf=1u=http%3A%2F%2Fgis-lab.info%2Fforum%2Fviewtopic.php%3Ff%3D41%26t%3D10329 



BR

On Fri, Nov 2, 2012 at 4:15 PM, aho forum.emai...@googlemail.com 
wrote:

Hi Jukka,

ok, I solved the problem with the requests. The following returns from
tinyOWS:

?xml version='1.0' encoding='UTF-8'?
ows:ExceptionReport
  xmlns='http://www.opengis.net/ows'
  xmlns:ows='http://www.opengis.net/ows'
  xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
  xsi:schemaLocation='http://www.opengis.net/ows
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'
  version='1.1.0' language='en'
  ows:Exception exceptionCode='InvalidParameterValue' 
locator='request'

   ows:ExceptionTextXML request isn't valid/ows:ExceptionText
  /ows:Exception
/ows:ExceptionReport

Here is the errorlog:

Fri Nov 02 15:11:46 2012] [EVENT] == FCGI START ==
[Fri Nov 02 15:11:46 2012] [QUERY] wfs:GetFeature
xmlns:wfs=http://www.opengis.net/wfs; service=WFS version=1.0.0
xsi:schemaLocation=http://www.opengis.net/wfs
http://schemas.opengis.net/wfs/1.0.0/WFS-transaction.xsd water
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsamp;request=GetFeatureamp;version=1.0.0amp;typename=water:armature; 


xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;wfs:Query
typeName=feature:armature xmlns:feature=waterogc:Filter
xmlns:ogc=http://www.opengis.net/ogc;ogc:BBOXogc:PropertyNamegeometry/ogc:PropertyNamegml:Box 

xmlns:gml=http://www.opengis.net/gml; 
srsName=EPSG:32740gml:coordinates

decimal=. cs=, ts= -2866.3885602952,-1910.9257068634
2866.3885602952,1910.9257068634/gml:coordinates/gml:Box/ogc:BBOX/ogc:Filter/wfs:Query/wfs:GetFeature 


[Fri Nov 02 15:11:46 2012] [ERROR] Element
'{http://www.w3.org/2001/XMLSchema}import': Failed to locate a 
schema at

location
'localhost/cgi-bin/tinyows.exe?service=WFSrequest=DescribeFeatureTypeversion=1.0.0'. 


Skipping the import.

[Fri Nov 02 15:11:46 2012] [ERROR] Element
'{http://www.opengis.net/wfs}GetFeature': No matching global 
declaration

available for the validation root.

[Fri Nov 02 15:11:46 2012] [ERROR] XML request isn't valid
[Fri Nov 02 15:11:46 2012] [EVENT] == FCGI SHUTDOWN ==
[Fri Nov 02 15:11:46 2012] [EVENT] == TINYOWS SHUTDOWN ==

Has it something to do with the schema? I found a post with something
similar
(http://osgeo-org.1560.n6.nabble.com/TinyOWS-wrong-call-in-OpenLayers-InvalidParameterValue-XML-request-isn-t-valid-td5009059.html) 


and replaced all my old tinyows files and copied the ones from the ms4w
homepage.

Do you have some more ideas?

Am 11/2/2012 10:56 AM, schrieb Rahkonen Jukka:

Hi,

Yes, it seems to be OpenLayers question then. However, do still 
capture the
requests because without them you cannot understand what happens 
really.  My
guess is that something in wrong in how EPSG:31467 and EPSG:32740 
are used

and OpenLayers is requesting data from a place where there are no data.

-Jukka-

aho wrote:


Hi Jukka,

thanks a lot for your answer and the good tips! I tried all of the 
links


and they are working. Also I checked it in QGIS and there I can load it
too.

So I guess it will be better to write again to the openlayers 
mailinglist?!


Am 11/2/2012 10:21 AM, schrieb Rahkonen Jukka:

Hi,

You must capture the traffic between OpenLayers and TinyOWS. I am using
myself Fiddler2 proxy but I suppose that Firebug can show you what
OpenLayers is sending and high enough TinyOWS logging level will 
also gather
requests into tinyows log. The software is not important but you 
just have
to get the requests so you can resend them with a browser or some 
other tool
that yuo can control and see what happens. You can also include the 
requests
in your further mails. Then the question will be OpenLayers is 
sending this
and TinyOWS is sending back that, what's wrong? and it will be much 
easier

to 

Re: [mapserver-users] tinyows

[Rahkonen Jukka]

Hi,

Forum is right but obviously there are not many people doing WFS-T with 
OpenLayers against TinyOWS installed on Windows. If you are totally jammed I 
would recommend you to leave TinyOWS aside for a while and try to make your 
OpenLayers application to work with Geoserver WFS-T. I believe you will have 
success with it.

-Jukka Rahkonen-



 -Alkuperäinen viesti-
 Lähettäjä: aho [mailto:forum.emai...@googlemail.com]
 Lähetetty: 9. marraskuuta 2012 11:27
 Vastaanottaja: sdi...@volz.ua
 Kopio: Rahkonen Jukka; mapserver-users@lists.osgeo.org
 Aihe: Re: [mapserver-users] tinyows
 
 Hi again,
 
 I am still searching and not finding something. I setup everything again with
 the WFS-T tutorial. Now I am getting the following error message:
 
 [Thu Nov 08 16:32:21 2012] [ERROR] local list type: A type, derived by list or
 union, must have the simple ur-type definition as base type, not
 '{http://www.opengis.net/gml}doubleOrNullList'.
 
 Am I right with this forum? Because actually nobody replies.
 
 
 
 
 Am 11/6/2012 1:30 PM, schrieb aho:
  Hey,
 
  I still havn´t found the problem with the tinyows - but at the moment
  there is no error message when i am loading the wfs. Also fiddler
  doesn´t list the tinyows.exe anymore. But my proxy is correct - I can
  load it via uDig and ArcMap. QGIS has a problem, but there is not a
  single error in the tinyows log file - just events and sqls are
  listed, that looks quite good. With Open layers there is nothing
  logged - it seems like the request is not send.
 
  Is there any limitation for the version? I downloaded the latest
  (2.12) one, but on the tinyows page is version 2.09 listed?!
 
  Kind regards
 
  Am 11/2/2012 3:29 PM, schrieb Serge Dikiy:
  Hi,
 
 
 http://translate.google.com/translate?sl=rutl=enjs=nprev=_thl=en;
  ie=UTF-8layout=2eotf=1u=http%3A%2F%2Fgis-
 lab.info%2Fforum%2Fviewto
  pic.php%3Ff%3D41%26t%3D10329
 
 
  BR
 
  On Fri, Nov 2, 2012 at 4:15 PM, aho forum.emai...@googlemail.com
  wrote:
  Hi Jukka,
 
  ok, I solved the problem with the requests. The following returns
  from
  tinyOWS:
 
  ?xml version='1.0' encoding='UTF-8'? ows:ExceptionReport
xmlns='http://www.opengis.net/ows'
xmlns:ows='http://www.opengis.net/ows'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
xsi:schemaLocation='http://www.opengis.net/ows
  http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'
version='1.1.0' language='en'
ows:Exception exceptionCode='InvalidParameterValue'
  locator='request'
 ows:ExceptionTextXML request isn't valid/ows:ExceptionText
/ows:Exception
  /ows:ExceptionReport
 
  Here is the errorlog:
 
  Fri Nov 02 15:11:46 2012] [EVENT] == FCGI START == [Fri Nov 02
  15:11:46 2012] [QUERY] wfs:GetFeature
  xmlns:wfs=http://www.opengis.net/wfs; service=WFS
 version=1.0.0
  xsi:schemaLocation=http://www.opengis.net/wfs
  http://schemas.opengis.net/wfs/1.0.0/WFS-transaction.xsd water
  http://127.0.0.1:8000/redir/cgi-
 bin/tinyows.exe?service=wfsamp;request=GetFeatureamp;version=1.0.
 0amp;typename=water:armature
 
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-
 instancewfs:Query
  typeName=feature:armature xmlns:feature=waterogc:Filter
 
 xmlns:ogc=http://www.opengis.net/ogc;ogc:BBOXogc:PropertyName
 g
  eometry/ogc:PropertyNamegml:Box
 
  xmlns:gml=http://www.opengis.net/gml;
  srsName=EPSG:32740gml:coordinates
  decimal=. cs=, ts= -2866.3885602952,-1910.9257068634
 
 2866.3885602952,1910.9257068634/gml:coordinates/gml:Box/ogc:BBO
  X/ogc:Filter/wfs:Query/wfs:GetFeature
 
  [Fri Nov 02 15:11:46 2012] [ERROR] Element
  '{http://www.w3.org/2001/XMLSchema}import': Failed to locate a
  schema at location
  'localhost/cgi-
 bin/tinyows.exe?service=WFSrequest=DescribeFeatureTypeversion=1.0.
 0'.
 
  Skipping the import.
 
  [Fri Nov 02 15:11:46 2012] [ERROR] Element
  '{http://www.opengis.net/wfs}GetFeature': No matching global
  declaration available for the validation root.
 
  [Fri Nov 02 15:11:46 2012] [ERROR] XML request isn't valid [Fri Nov
  02 15:11:46 2012] [EVENT] == FCGI SHUTDOWN == [Fri Nov 02 15:11:46
  2012] [EVENT] == TINYOWS SHUTDOWN ==
 
  Has it something to do with the schema? I found a post with
  something similar
  (http://osgeo-org.1560.n6.nabble.com/TinyOWS-wrong-call-in-
 OpenLayer
  s-InvalidParameterValue-XML-request-isn-t-valid-td5009059.html)
 
  and replaced all my old tinyows files and copied the ones from the
  ms4w homepage.
 
  Do you have some more ideas?
 
  Am 11/2/2012 10:56 AM, schrieb Rahkonen Jukka:
 
  Hi,
 
  Yes, it seems to be OpenLayers question then. However, do still
  capture the requests because without them you cannot understand
 what
  happens really.  My guess is that something in wrong in how
  EPSG:31467 and EPSG:32740 are used and OpenLayers is requesting data
  from a place where there are no data.
 
  -Jukka-
 
  aho wrote:
 
 
  Hi Jukka,
 
  thanks a lot for your answer and the good tips! I tried all of the
  links
 
  and they are working. Also

Re: [mapserver-users] tinyows

[Alexandre Dubé]

-
Lähettäjä: aho [mailto:forum.emai...@googlemail.com]
Lähetetty: 9. marraskuuta 2012 11:27
Vastaanottaja: sdi...@volz.ua
Kopio: Rahkonen Jukka; mapserver-users@lists.osgeo.org
Aihe: Re: [mapserver-users] tinyows

Hi again,

I am still searching and not finding something. I setup everything again with
the WFS-T tutorial. Now I am getting the following error message:

[Thu Nov 08 16:32:21 2012] [ERROR] local list type: A type, derived by list or
union, must have the simple ur-type definition as base type, not
'{http://www.opengis.net/gml}doubleOrNullList'.

Am I right with this forum? Because actually nobody replies.




Am 11/6/2012 1:30 PM, schrieb aho:

Hey,

I still havn´t found the problem with the tinyows - but at the moment
there is no error message when i am loading the wfs. Also fiddler
doesn´t list the tinyows.exe anymore. But my proxy is correct - I can
load it via uDig and ArcMap. QGIS has a problem, but there is not a
single error in the tinyows log file - just events and sqls are
listed, that looks quite good. With Open layers there is nothing
logged - it seems like the request is not send.

Is there any limitation for the version? I downloaded the latest
(2.12) one, but on the tinyows page is version 2.09 listed?!

Kind regards

Am 11/2/2012 3:29 PM, schrieb Serge Dikiy:

Hi,



http://translate.google.com/translate?sl=rutl=enjs=nprev=_thl=en;

ie=UTF-8layout=2eotf=1u=http%3A%2F%2Fgis-

lab.info%2Fforum%2Fviewto

pic.php%3Ff%3D41%26t%3D10329


BR

On Fri, Nov 2, 2012 at 4:15 PM, aho forum.emai...@googlemail.com
wrote:

Hi Jukka,

ok, I solved the problem with the requests. The following returns
from
tinyOWS:

?xml version='1.0' encoding='UTF-8'? ows:ExceptionReport
   xmlns='http://www.opengis.net/ows'
   xmlns:ows='http://www.opengis.net/ows'
   xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
   xsi:schemaLocation='http://www.opengis.net/ows
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'
   version='1.1.0' language='en'
   ows:Exception exceptionCode='InvalidParameterValue'
locator='request'
ows:ExceptionTextXML request isn't valid/ows:ExceptionText
   /ows:Exception
/ows:ExceptionReport

Here is the errorlog:

Fri Nov 02 15:11:46 2012] [EVENT] == FCGI START == [Fri Nov 02
15:11:46 2012] [QUERY] wfs:GetFeature
xmlns:wfs=http://www.opengis.net/wfs; service=WFS

version=1.0.0

xsi:schemaLocation=http://www.opengis.net/wfs
http://schemas.opengis.net/wfs/1.0.0/WFS-transaction.xsd water
http://127.0.0.1:8000/redir/cgi-

bin/tinyows.exe?service=wfsamp;request=GetFeatureamp;version=1.0.
0amp;typename=water:armature

xmlns:xsi=http://www.w3.org/2001/XMLSchema-

instancewfs:Query

typeName=feature:armature xmlns:feature=waterogc:Filter


xmlns:ogc=http://www.opengis.net/ogc;ogc:BBOXogc:PropertyName

g

eometry/ogc:PropertyNamegml:Box

xmlns:gml=http://www.opengis.net/gml;
srsName=EPSG:32740gml:coordinates
decimal=. cs=, ts= -2866.3885602952,-1910.9257068634


2866.3885602952,1910.9257068634/gml:coordinates/gml:Box/ogc:BBO

X/ogc:Filter/wfs:Query/wfs:GetFeature

[Fri Nov 02 15:11:46 2012] [ERROR] Element
'{http://www.w3.org/2001/XMLSchema}import': Failed to locate a
schema at location
'localhost/cgi-

bin/tinyows.exe?service=WFSrequest=DescribeFeatureTypeversion=1.0.
0'.

Skipping the import.

[Fri Nov 02 15:11:46 2012] [ERROR] Element
'{http://www.opengis.net/wfs}GetFeature': No matching global
declaration available for the validation root.

[Fri Nov 02 15:11:46 2012] [ERROR] XML request isn't valid [Fri Nov
02 15:11:46 2012] [EVENT] == FCGI SHUTDOWN == [Fri Nov 02 15:11:46
2012] [EVENT] == TINYOWS SHUTDOWN ==

Has it something to do with the schema? I found a post with
something similar
(http://osgeo-org.1560.n6.nabble.com/TinyOWS-wrong-call-in-

OpenLayer

s-InvalidParameterValue-XML-request-isn-t-valid-td5009059.html)

and replaced all my old tinyows files and copied the ones from the
ms4w homepage.

Do you have some more ideas?

Am 11/2/2012 10:56 AM, schrieb Rahkonen Jukka:

Hi,

Yes, it seems to be OpenLayers question then. However, do still
capture the requests because without them you cannot understand

what

happens really.  My guess is that something in wrong in how
EPSG:31467 and EPSG:32740 are used and OpenLayers is requesting data
from a place where there are no data.

-Jukka-

aho wrote:


Hi Jukka,

thanks a lot for your answer and the good tips! I tried all of the
links

and they are working. Also I checked it in QGIS and there I can load
it too.

So I guess it will be better to write again to the openlayers
mailinglist?!

Am 11/2/2012 10:21 AM, schrieb Rahkonen Jukka:

Hi,

You must capture the traffic between OpenLayers and TinyOWS. I am
using myself Fiddler2 proxy but I suppose that Firebug can show you
what OpenLayers is sending and high enough TinyOWS logging level
will also gather requests into tinyows log. The software is not
important but you just have to get the requests so you can resend
them with a browser or some other tool that yuo can control

Re: [mapserver-users] tinyows

[Jeff McKenna]

On 12-11-09 9:50 AM, Alexandre Dubé wrote:
 Finally, here's a trick I use when debuggin POST requests.  I use the
 wget command to quickly launch requests and see their result using the
 --post-data argument to send the GML GetFeature request.
 
 wget http://localhost/cgi-bin/tinyows;
 --post-data='your_wfs_getfeature_xml_goes_here'
 --header=Content-Type: application/xml; charset=UTF-8 -O /tmp/ttt.txt
 

Cool trick Alexandre!

-jeff





-- 
Jeff McKenna
MapServer Consulting and Training Services
http://www.gatewaygeomatics.com/


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

[mapserver-users] [TinyOWS] Inserting feature and XML schema validation

[Тимур Галиаскарович Суфиев]

Hi!

This isn't the first question here about inserting features in TinyOWS, but I 
haven't found solution to my problem in archives.

The working environment is OpenLayers 2.13dev + TinyOWS from github + PostGIS 
2.0 + PostgreSQL 9.2

Relevant js-code is:

var POINT = 1;
var save_objs_strategy = new OpenLayers.Strategy.Save(
{ saves_what: cities });
var cities = new OpenLayers.Layer.Vector(
'Города', {
strategies: [new OpenLayers.Strategy.BBOX(), 
 save_objs_strategy],
protocol: new OpenLayers.Protocol.WFS(
{
version: 1.1.0,
url: http://localhost/mapserver/tinyows;,
featureType: cities,
featureNS: http://www.tinyows.org;,
geometryName: geom,
outputFormat: JSON,
schema: 
http://localhost/mapserver/tinyows?service=wfsamp;request=DescribeFeatureTypeamp;version=1.1.0amp;typename=tows:cities;
})
}
);

var draw = new OpenLayers.Control.DrawFeature(
cities, OpenLayers.Handler.Point,
{
title: Создание объектов,
displayClass: olControlDrawFeaturePoint
}
);
draw.events.on(
{
featureadded: function(e) {
var attrs = e.feature.attributes;
attrs.pop_hk = 99;
attrs.city_name = Новый город;
attrs.type_id = POINT;
save_objs_strategy.save();
}
});

Adding a vector point feature (city) somewhere on the map creates the following 
XML request to tinyows:



wfs:Transaction xmlns:wfs=http://www.opengis.net/wfs; service=WFS 
version=1.1.0 xsi:schemaLocation=http://www.opengis.net/wfs   
http://schemas.opengis.net/wfs/1.1.0/wfs.xsd http://www.tinyows.org   
http://localhost/mapserver/tinyows?service=wfsamp;request=DescribeFeatureTypeamp;version=1.1.0amp;typename=tows:cities;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;


wfs:Insert


feature:cities xmlns:feature=http://www.tinyows.org;


feature:geom


gml:Point xmlns:gml=http://www.opengis.net/gml; srsName=EPSG:4326


gml:pos37.962548828124 55.22265625/gml:pos
/gml:Point
/feature:geom

feature:pop_hk99/feature:pop_hk

feature:city_nameНовый город/feature:city_name

feature:type_id1/feature:type_id
/feature:cities
/wfs:Insert
/wfs:Transaction
The request fails with the following string in tinyows.log:

[Wed Nov  7 19:55:01 2012] [ERROR] Element '{http://www.tinyows.org}cities': 
This element is not expected. Expected is one of ( 
{http://www.opengis.net/gml}_Feature, 
{http://www.opengis.net/gml}FeatureCollection, 
{http://www.opengis.net/gml}MultiPointCoverage, 
{http://www.opengis.net/gml}MultiCurveCoverage, 
{http://www.opengis.net/gml}MultiSurfaceCoverage, 
{http://www.opengis.net/gml}MultiSolidCoverage, 
{http://www.opengis.net/gml}GridCoverage, 
{http://www.opengis.net/gml}RectifiedGridCoverage, 
{http://www.opengis.net/gml}Observation, 
{http://www.opengis.net/gml}DirectedObservation ).

This seems a little bit cryptic to me because the schema parameter in js-code 
(http://localhost/mapserver/tinyows?service=wfsamp;request=DescribeFeatureTypeamp;version=1.1.0amp;typename=tows:cities)
 returns the following xsd:

xs:schema targetNamespace=http://www.tinyows.org/; 
elementFormDefault=qualified version=1.1xs:import 
namespace=http://www.opengis.net/gml; 
schemaLocation=http://schemas.opengis.net/gml/3.1.1/base/gml.xsd/xs:element 
name=cities type=tows:citiesType 
substitutionGroup=gml:_Feature/xs:complexType 
name=citiesTypexs:complexContentxs:extension 
base=gml:AbstractFeatureTypexs:sequencexs:element name=pop_hk 
type=int nillable=true minOccurs=0 maxOccurs=1/xs:element 
name=city_name nillable=false minOccurs=1 
maxOccurs=1xs:simpleTypexs:restriction base=stringxs:maxLength 
value=100//xs:restriction/xs:simpleType/xs:elementxs:element 
name=geom type=gml:PointPropertyType nillable=true minOccurs=0 
maxOccurs=1/xs:element name=type_id type=int nillable=true 
minOccurs=0 
maxOccurs=1//xs:sequence/xs:extension/xs:complexContent/xs:complexType/xs:schema

and this xsd should make tinyows use element '{http://www.tinyows.org}cities' 
like '{http://www.opengis.net/gml}_Feature'

Where am I wrong and what should be changed in my setup?

Best regards,
Timur Sufiev___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] [TinyOWS] Inserting feature and XML schema validation

[Olivier Courtin]

On Wed, Nov 7, 2012 at 5:13 PM, Тимур Галиаскарович Суфиев t.suf...@acti.ru
 wrote:

Hi Timur,


 This isn't the first question here about inserting features in TinyOWS,
 but I haven't found solution to my problem in archives.

 and this xsd should make tinyows use element '{http://www.tinyows.org}cities'
 like '{http://www.opengis.net/gml}_Feature'

 Where am I wrong and what should be changed in my setup?


Thanks for your detailled report,
first naive question, what about the tinyows.xml config file,
 and online_resource property ?

Next question, what happen, if you bypass schema validation,
with: check_schema = 0   (in tinyows element)

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

Re: [mapserver-users] tinyows

[aho]

Hey,

I still havn´t found the problem with the tinyows - but at the moment 
there is no error message when i am loading the wfs. Also fiddler 
doesn´t list the tinyows.exe anymore. But my proxy is correct - I can 
load it via uDig and ArcMap. QGIS has a problem, but there is not a 
single error in the tinyows log file - just events and sqls are listed, 
that looks quite good. With Open layers there is nothing logged - it 
seems like the request is not send.


Is there any limitation for the version? I downloaded the latest (2.12) 
one, but on the tinyows page is version 2.09 listed?!


Kind regards

Am 11/2/2012 3:29 PM, schrieb Serge Dikiy:

Hi,

http://translate.google.com/translate?sl=rutl=enjs=nprev=_thl=enie=UTF-8layout=2eotf=1u=http%3A%2F%2Fgis-lab.info%2Fforum%2Fviewtopic.php%3Ff%3D41%26t%3D10329

BR

On Fri, Nov 2, 2012 at 4:15 PM, aho forum.emai...@googlemail.com wrote:

Hi Jukka,

ok, I solved the problem with the requests. The following returns from
tinyOWS:

?xml version='1.0' encoding='UTF-8'?
ows:ExceptionReport
  xmlns='http://www.opengis.net/ows'
  xmlns:ows='http://www.opengis.net/ows'
  xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
  xsi:schemaLocation='http://www.opengis.net/ows
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'
  version='1.1.0' language='en'
  ows:Exception exceptionCode='InvalidParameterValue' locator='request'
   ows:ExceptionTextXML request isn't valid/ows:ExceptionText
  /ows:Exception
/ows:ExceptionReport

Here is the errorlog:

Fri Nov 02 15:11:46 2012] [EVENT] == FCGI START ==
[Fri Nov 02 15:11:46 2012] [QUERY] wfs:GetFeature
xmlns:wfs=http://www.opengis.net/wfs; service=WFS version=1.0.0
xsi:schemaLocation=http://www.opengis.net/wfs
http://schemas.opengis.net/wfs/1.0.0/WFS-transaction.xsd water
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsamp;request=GetFeatureamp;version=1.0.0amp;typename=water:armature;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;wfs:Query
typeName=feature:armature xmlns:feature=waterogc:Filter
xmlns:ogc=http://www.opengis.net/ogc;ogc:BBOXogc:PropertyNamegeometry/ogc:PropertyNamegml:Box
xmlns:gml=http://www.opengis.net/gml; srsName=EPSG:32740gml:coordinates
decimal=. cs=, ts= -2866.3885602952,-1910.9257068634
2866.3885602952,1910.9257068634/gml:coordinates/gml:Box/ogc:BBOX/ogc:Filter/wfs:Query/wfs:GetFeature
[Fri Nov 02 15:11:46 2012] [ERROR] Element
'{http://www.w3.org/2001/XMLSchema}import': Failed to locate a schema at
location
'localhost/cgi-bin/tinyows.exe?service=WFSrequest=DescribeFeatureTypeversion=1.0.0'.
Skipping the import.

[Fri Nov 02 15:11:46 2012] [ERROR] Element
'{http://www.opengis.net/wfs}GetFeature': No matching global declaration
available for the validation root.

[Fri Nov 02 15:11:46 2012] [ERROR] XML request isn't valid
[Fri Nov 02 15:11:46 2012] [EVENT] == FCGI SHUTDOWN ==
[Fri Nov 02 15:11:46 2012] [EVENT] == TINYOWS SHUTDOWN ==

Has it something to do with the schema? I found a post with something
similar
(http://osgeo-org.1560.n6.nabble.com/TinyOWS-wrong-call-in-OpenLayers-InvalidParameterValue-XML-request-isn-t-valid-td5009059.html)
and replaced all my old tinyows files and copied the ones from the ms4w
homepage.

Do you have some more ideas?

Am 11/2/2012 10:56 AM, schrieb Rahkonen Jukka:

Hi,

Yes, it seems to be OpenLayers question then. However, do still capture the
requests because without them you cannot understand what happens really.  My
guess is that something in wrong in how EPSG:31467 and EPSG:32740 are used
and OpenLayers is requesting data from a place where there are no data.

-Jukka-

aho wrote:


Hi Jukka,

thanks a lot for your answer and the good tips! I tried all of the links

and they are working. Also I checked it in QGIS and there I can load it
too.

So I guess it will be better to write again to the openlayers mailinglist?!

Am 11/2/2012 10:21 AM, schrieb Rahkonen Jukka:

Hi,

You must capture the traffic between OpenLayers and TinyOWS.  I am using
myself Fiddler2 proxy but I suppose that Firebug can show you what
OpenLayers is sending and high enough TinyOWS logging level will also gather
requests into tinyows log. The software is not important but you just have
to get the requests so you can resend them with a browser or some other tool
that yuo can control and see what happens. You can also include the requests
in your further mails. Then the question will be OpenLayers is sending this
and TinyOWS is sending back that, what's wrong? and it will be much easier
to answer.

As always with WFS, start with these requests with a browser before doing
anything with OpenLayers:
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetCapabilitiesversion=1.1.0

http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=DescribeFeatureTypeversion=1.1.0typename=water:pipeline_segment

http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetFeatureversion=1.1.0typename=water:pipeline_segmentmaxFeatures=10

If all those 

[mapserver-users] tinyows

[aho]

hello!

I have a problem with the configuration of tinyows. I have the following 
settings in my xml file:


tinyows online_resource=localhost/cgi-bin/tinyows.exe
   schema_dir=C:\ms4w\apps\tinyows\schema\
pg host=localhost user=postgres password=postgres 
dbname=watergis port=5432/

metadata name=TinyOWS Server
  title=TinyOWS Server - WFS-T Frida Service /
contact name=TinyOWS Server
 site=http://www.tinyows.org/;
 email=tinyows-us...@lists.maptools.org /
layer retrievable=1
   writable=1
   ns_prefix=water
   ns_uri=http://localhost/;
   name=pipeline_segment
   title=pipeline_segment
   table= pipeline_segment
   srid=32740
   schema=water/
/tinyows

if I enter tinyows --check I get the following back:

C:\ms4w\Apache\cgi-bintinyows --check
TinyOWS version:   1.0.0rc3
FCGI support:  Yes
Config File Path:  C:\ms4w\apps\tinyows\tinyows.xml (TinyOWS XML)
PostGIS Version:   2.0.0
PostGIS dsn:   host=localhost user=postgres password=postgres 
dbname=watergi

s port=5432
Output Encoding:   UTF-8
Database Encoding: UTF8
Schema dir:C:\ms4w\apps\tinyows\schema\
Display bbox:  Yes
Estimated extent:  No
Check schema:  Yes
Check valid geoms: Yes
Available layers:
 - water.pipeline_segment (32740) - water.pipeline_segment [RW]


which looks acutally quite good. But when i am trying to include that 
into my openlayer map - I always get 0 features back! Here the code for 
openlayers:


wfs = new OpenLayers.Layer.Vector(Editable Features, {
strategies: [new OpenLayers.Strategy.BBOX(), saveStrategy],
projection: new OpenLayers.Projection(EPSG:31467),
protocol: new OpenLayers.Protocol.WFS({
  version: 1.1.0,
  srsName: EPSG:32740,
  url: http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe;,
  featureNS :  tows,
  featureType: pipeline_segment,
  geometryName: geometry,
  schema: 
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=DescribeFeatureTypeversion=1.1.0typename=water:pipeline_segment;

})
});

Someone an idea?
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] tinyows

[Rahkonen Jukka]

Hi,

You must capture the traffic between OpenLayers and TinyOWS.  I am using myself 
Fiddler2 proxy but I suppose that Firebug can show you what OpenLayers is 
sending and high enough TinyOWS logging level will also gather requests into 
tinyows log. The software is not important but you just have to get the 
requests so you can resend them with a browser or some other tool that yuo can 
control and see what happens. You can also include the requests in your further 
mails. Then the question will be OpenLayers is sending this and TinyOWS is 
sending back that, what's wrong? and it will be much easier to answer.

As always with WFS, start with these requests with a browser before doing 
anything with OpenLayers:
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetCapabilitiesversion=1.1.0

http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=DescribeFeatureTypeversion=1.1.0typename=water:pipeline_segment

http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetFeatureversion=1.1.0typename=water:pipeline_segmentmaxFeatures=10

If all those requests work you know that TinyOWS works with those basic 
requests and if OpenLayers application does not get data the reason in probably 
in the application code.


-Jukka Rahkonen-

aho wrote:

 hello!

 I have a problem with the configuration of tinyows. I have the following
settings in my xml file:

 tinyows online_resource=localhost/cgi-bin/tinyows.exe
schema_dir=C:\ms4w\apps\tinyows\schema\
pg host=localhost user=postgres password=postgres
dbname=watergis port=5432/
metadata name=TinyOWS Server
   title=TinyOWS Server - WFS-T Frida Service /
contact name=TinyOWS Server
  site=http://www.tinyows.org/;
  email=tinyows-us...@lists.maptools.org /
layer retrievable=1
writable=1
ns_prefix=water
ns_uri=http://localhost/;
name=pipeline_segment
title=pipeline_segment
table= pipeline_segment
srid=32740
schema=water/
/tinyows

 if I enter tinyows --check I get the following back:

 C:\ms4w\Apache\cgi-bintinyows --check
TinyOWS version:   1.0.0rc3
FCGI support:  Yes
Config File Path:  C:\ms4w\apps\tinyows\tinyows.xml (TinyOWS XML)
PostGIS Version:   2.0.0
PostGIS dsn:   host=localhost user=postgres password=postgres
dbname=watergi
s port=5432
Output Encoding:   UTF-8
Database Encoding: UTF8
Schema dir:C:\ms4w\apps\tinyows\schema\
Display bbox:  Yes
Estimated extent:  No
Check schema:  Yes
Check valid geoms: Yes
Available layers:
  - water.pipeline_segment (32740) - water.pipeline_segment [RW]


 which looks acutally quite good. But when i am trying to include that
into my openlayer map - I always get 0 features back! Here the code for
openlayers:

wfs = new OpenLayers.Layer.Vector(Editable Features, {
 strategies: [new OpenLayers.Strategy.BBOX(), saveStrategy],
 projection: new OpenLayers.Projection(EPSG:31467),
 protocol: new OpenLayers.Protocol.WFS({
   version: 1.1.0,
   srsName: EPSG:32740,
   url: http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe;,
   featureNS :  tows,
   featureType: pipeline_segment,
   geometryName: geometry,
   schema:
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=DescribeFeatureTypeversion=1.1.0typename=water:pipeline_segment;
 })
});

Someone an idea?
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] tinyows

[aho]

Hi Jukka,

thanks a lot for your answer and the good tips! I tried all of the links 
and they are working. Also I checked it in QGIS and there I can load it 
too.


So I guess it will be better to write again to the openlayers mailinglist?!


Am 11/2/2012 10:21 AM, schrieb Rahkonen Jukka:

Hi,

You must capture the traffic between OpenLayers and TinyOWS.  I am using myself Fiddler2 
proxy but I suppose that Firebug can show you what OpenLayers is sending and high enough 
TinyOWS logging level will also gather requests into tinyows log. The software is not 
important but you just have to get the requests so you can resend them with a browser or 
some other tool that yuo can control and see what happens. You can also include the 
requests in your further mails. Then the question will be OpenLayers is sending 
this and TinyOWS is sending back that, what's wrong? and it will be much easier to 
answer.

As always with WFS, start with these requests with a browser before doing 
anything with OpenLayers:
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetCapabilitiesversion=1.1.0

http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=DescribeFeatureTypeversion=1.1.0typename=water:pipeline_segment

http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetFeatureversion=1.1.0typename=water:pipeline_segmentmaxFeatures=10

If all those requests work you know that TinyOWS works with those basic 
requests and if OpenLayers application does not get data the reason in probably 
in the application code.


-Jukka Rahkonen-

aho wrote:


hello!
I have a problem with the configuration of tinyows. I have the following

settings in my xml file:


tinyows online_resource=localhost/cgi-bin/tinyows.exe

 schema_dir=C:\ms4w\apps\tinyows\schema\
pg host=localhost user=postgres password=postgres
dbname=watergis port=5432/
metadata name=TinyOWS Server
title=TinyOWS Server - WFS-T Frida Service /
contact name=TinyOWS Server
   site=http://www.tinyows.org/;
   email=tinyows-us...@lists.maptools.org /
layer retrievable=1
 writable=1
 ns_prefix=water
 ns_uri=http://localhost/;
 name=pipeline_segment
 title=pipeline_segment
 table= pipeline_segment
 srid=32740
 schema=water/
/tinyows

  if I enter tinyows --check I get the following back:


C:\ms4w\Apache\cgi-bintinyows --check

TinyOWS version:   1.0.0rc3
FCGI support:  Yes
Config File Path:  C:\ms4w\apps\tinyows\tinyows.xml (TinyOWS XML)
PostGIS Version:   2.0.0
PostGIS dsn:   host=localhost user=postgres password=postgres
dbname=watergi
s port=5432
Output Encoding:   UTF-8
Database Encoding: UTF8
Schema dir:C:\ms4w\apps\tinyows\schema\
Display bbox:  Yes
Estimated extent:  No
Check schema:  Yes
Check valid geoms: Yes
Available layers:
   - water.pipeline_segment (32740) - water.pipeline_segment [RW]



which looks acutally quite good. But when i am trying to include that

into my openlayer map - I always get 0 features back! Here the code for
openlayers:

wfs = new OpenLayers.Layer.Vector(Editable Features, {
  strategies: [new OpenLayers.Strategy.BBOX(), saveStrategy],
  projection: new OpenLayers.Projection(EPSG:31467),
  protocol: new OpenLayers.Protocol.WFS({
version: 1.1.0,
srsName: EPSG:32740,
url: http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe;,
featureNS :  tows,
featureType: pipeline_segment,
geometryName: geometry,
schema:
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=DescribeFeatureTypeversion=1.1.0typename=water:pipeline_segment;
  })
});

Someone an idea?
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users


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

Re: [mapserver-users] tinyows

[Rahkonen Jukka]

Hi,

Yes, it seems to be OpenLayers question then. However, do still capture the 
requests because without them you cannot understand what happens really.  My 
guess is that something in wrong in how EPSG:31467 and EPSG:32740 are used and 
OpenLayers is requesting data from a place where there are no data.

-Jukka-

aho wrote:


 Hi Jukka,

 thanks a lot for your answer and the good tips! I tried all of the links
and they are working. Also I checked it in QGIS and there I can load it
too.

 So I guess it will be better to write again to the openlayers mailinglist?!


Am 11/2/2012 10:21 AM, schrieb Rahkonen Jukka:
 Hi,

 You must capture the traffic between OpenLayers and TinyOWS.  I am using 
 myself Fiddler2 proxy but I suppose that Firebug can show you what OpenLayers 
 is sending and high enough TinyOWS logging level will also gather requests 
 into tinyows log. The software is not important but you just have to get the 
 requests so you can resend them with a browser or some other tool that yuo 
 can control and see what happens. You can also include the requests in your 
 further mails. Then the question will be OpenLayers is sending this and 
 TinyOWS is sending back that, what's wrong? and it will be much easier to 
 answer.

 As always with WFS, start with these requests with a browser before doing 
 anything with OpenLayers:
 http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetCapabilitiesversion=1.1.0

 http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=DescribeFeatureTypeversion=1.1.0typename=water:pipeline_segment

 http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetFeatureversion=1.1.0typename=water:pipeline_segmentmaxFeatures=10

 If all those requests work you know that TinyOWS works with those basic 
 requests and if OpenLayers application does not get data the reason in 
 probably in the application code.


 -Jukka Rahkonen-

 aho wrote:

 hello!
 I have a problem with the configuration of tinyows. I have the following
 settings in my xml file:

 tinyows online_resource=localhost/cgi-bin/tinyows.exe
  schema_dir=C:\ms4w\apps\tinyows\schema\
 pg host=localhost user=postgres password=postgres
 dbname=watergis port=5432/
 metadata name=TinyOWS Server
 title=TinyOWS Server - WFS-T Frida Service /
 contact name=TinyOWS Server
site=http://www.tinyows.org/;
email=tinyows-us...@lists.maptools.org /
 layer retrievable=1
  writable=1
  ns_prefix=water
  ns_uri=http://localhost/;
  name=pipeline_segment
  title=pipeline_segment
  table= pipeline_segment
  srid=32740
  schema=water/
 /tinyows

   if I enter tinyows --check I get the following back:

 C:\ms4w\Apache\cgi-bintinyows --check
 TinyOWS version:   1.0.0rc3
 FCGI support:  Yes
 Config File Path:  C:\ms4w\apps\tinyows\tinyows.xml (TinyOWS XML)
 PostGIS Version:   2.0.0
 PostGIS dsn:   host=localhost user=postgres password=postgres
 dbname=watergi
 s port=5432
 Output Encoding:   UTF-8
 Database Encoding: UTF8
 Schema dir:C:\ms4w\apps\tinyows\schema\
 Display bbox:  Yes
 Estimated extent:  No
 Check schema:  Yes
 Check valid geoms: Yes
 Available layers:
- water.pipeline_segment (32740) - water.pipeline_segment [RW]


 which looks acutally quite good. But when i am trying to include that
 into my openlayer map - I always get 0 features back! Here the code for
 openlayers:

 wfs = new OpenLayers.Layer.Vector(Editable Features, {
   strategies: [new OpenLayers.Strategy.BBOX(), saveStrategy],
   projection: new OpenLayers.Projection(EPSG:31467),
   protocol: new OpenLayers.Protocol.WFS({
 version: 1.1.0,
 srsName: EPSG:32740,
 url: http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe;,
 featureNS :  tows,
 featureType: pipeline_segment,
 geometryName: geometry,
 schema:
 http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=DescribeFeatureTypeversion=1.1.0typename=water:pipeline_segment;
   })
 });

 Someone an idea?
 ___
 mapserver-users mailing list
 mapserver-users@lists.osgeo.org
 http://lists.osgeo.org/mailman/listinfo/mapserver-users

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

Re: [mapserver-users] tinyows

[aho]

Hi,

mh - I changed the srid. That was not very nice, but not the problem. I 
think its really a problem of the request. I am actually using another 
framework and there I defined a proxy for the redir. Usually this works 
in my browser, but maybe openlayers has a problem with that.


I downloaded fiddler and the strange thing is that there is actually not 
a single request listed to that proxy. Also usually when I load thes WFS 
in QGIS there is something logged in the tinyows.log - but not with 
OpenLayers. So there goes nothing out at all!


Thanks for your help!

Am 11/2/2012 10:56 AM, schrieb Rahkonen Jukka:

Hi,

Yes, it seems to be OpenLayers question then. However, do still capture the 
requests because without them you cannot understand what happens really.  My 
guess is that something in wrong in how EPSG:31467 and EPSG:32740 are used and 
OpenLayers is requesting data from a place where there are no data.

-Jukka-

aho wrote:



Hi Jukka,
thanks a lot for your answer and the good tips! I tried all of the links

and they are working. Also I checked it in QGIS and there I can load it
too.


So I guess it will be better to write again to the openlayers mailinglist?!


Am 11/2/2012 10:21 AM, schrieb Rahkonen Jukka:

Hi,

You must capture the traffic between OpenLayers and TinyOWS.  I am using myself Fiddler2 
proxy but I suppose that Firebug can show you what OpenLayers is sending and high enough 
TinyOWS logging level will also gather requests into tinyows log. The software is not 
important but you just have to get the requests so you can resend them with a browser or 
some other tool that yuo can control and see what happens. You can also include the 
requests in your further mails. Then the question will be OpenLayers is sending 
this and TinyOWS is sending back that, what's wrong? and it will be much easier to 
answer.

As always with WFS, start with these requests with a browser before doing 
anything with OpenLayers:
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetCapabilitiesversion=1.1.0

http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=DescribeFeatureTypeversion=1.1.0typename=water:pipeline_segment

http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetFeatureversion=1.1.0typename=water:pipeline_segmentmaxFeatures=10

If all those requests work you know that TinyOWS works with those basic 
requests and if OpenLayers application does not get data the reason in probably 
in the application code.


-Jukka Rahkonen-

aho wrote:


hello!
I have a problem with the configuration of tinyows. I have the following

settings in my xml file:


tinyows online_resource=localhost/cgi-bin/tinyows.exe

  schema_dir=C:\ms4w\apps\tinyows\schema\
pg host=localhost user=postgres password=postgres
dbname=watergis port=5432/
metadata name=TinyOWS Server
 title=TinyOWS Server - WFS-T Frida Service /
contact name=TinyOWS Server
site=http://www.tinyows.org/;
email=tinyows-us...@lists.maptools.org /
layer retrievable=1
  writable=1
  ns_prefix=water
  ns_uri=http://localhost/;
  name=pipeline_segment
  title=pipeline_segment
  table= pipeline_segment
  srid=32740
  schema=water/
/tinyows

   if I enter tinyows --check I get the following back:


C:\ms4w\Apache\cgi-bintinyows --check

TinyOWS version:   1.0.0rc3
FCGI support:  Yes
Config File Path:  C:\ms4w\apps\tinyows\tinyows.xml (TinyOWS XML)
PostGIS Version:   2.0.0
PostGIS dsn:   host=localhost user=postgres password=postgres
dbname=watergi
s port=5432
Output Encoding:   UTF-8
Database Encoding: UTF8
Schema dir:C:\ms4w\apps\tinyows\schema\
Display bbox:  Yes
Estimated extent:  No
Check schema:  Yes
Check valid geoms: Yes
Available layers:
- water.pipeline_segment (32740) - water.pipeline_segment [RW]



which looks acutally quite good. But when i am trying to include that

into my openlayer map - I always get 0 features back! Here the code for
openlayers:

wfs = new OpenLayers.Layer.Vector(Editable Features, {
   strategies: [new OpenLayers.Strategy.BBOX(), saveStrategy],
   projection: new OpenLayers.Projection(EPSG:31467),
   protocol: new OpenLayers.Protocol.WFS({
 version: 1.1.0,
 srsName: EPSG:32740,
 url: http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe;,
 featureNS :  tows,
 featureType: pipeline_segment,
 geometryName: geometry,
 schema:
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=DescribeFeatureTypeversion=1.1.0typename=water:pipeline_segment;
   })
});

Someone an idea?
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users


___
mapserver-users 

Re: [mapserver-users] tinyows

[aho]

Hi Jukka,

ok, I solved the problem with the requests. The following returns from 
tinyOWS:


|?xml version='1.0' encoding='UTF-8'?
||ows:ExceptionReport
||  xmlns='http://www.opengis.net/ows'
||  xmlns:ows='http://www.opengis.net/ows'
||  xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
||  xsi:schemaLocation='http://www.opengis.net/ows 
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport||.xsd'
||  version='1.1.0' language='en'
||  ows:Exception exceptionCode='InvalidParameterValue' locator='request'
||   ows:ExceptionTextXML request isn't valid/ows:ExceptionText
||  /ows:Exception
||/ows:ExceptionReport|

Here is the errorlog:

Fri Nov 02 15:11:46 2012] [EVENT] == FCGI START ==
[Fri Nov 02 15:11:46 2012] [QUERY] wfs:GetFeature 
xmlns:wfs=http://www.opengis.net/wfs; service=WFS version=1.0.0 
xsi:schemaLocation=http://www.opengis.net/wfs 
http://schemas.opengis.net/wfs/1.0.0/WFS-transaction.xsd water 
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsamp;request=GetFeatureamp;version=1.0.0amp;typename=water:armature; 
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;wfs:Query 
typeName=feature:armature xmlns:feature=waterogc:Filter 
xmlns:ogc=http://www.opengis.net/ogc;ogc:BBOXogc:PropertyNamegeometry/ogc:PropertyNamegml:Box 
xmlns:gml=http://www.opengis.net/gml; 
srsName=EPSG:32740gml:coordinates decimal=. cs=, ts= 
-2866.3885602952,-1910.9257068634 
2866.3885602952,1910.9257068634/gml:coordinates/gml:Box/ogc:BBOX/ogc:Filter/wfs:Query/wfs:GetFeature
[Fri Nov 02 15:11:46 2012] [ERROR] Element 
'{http://www.w3.org/2001/XMLSchema}import': Failed to locate a schema at 
location 
'localhost/cgi-bin/tinyows.exe?service=WFSrequest=DescribeFeatureTypeversion=1.0.0'. 
Skipping the import.


[Fri Nov 02 15:11:46 2012] [ERROR] Element 
'{http://www.opengis.net/wfs}GetFeature': No matching global declaration 
available for the validation root.


[Fri Nov 02 15:11:46 2012] [ERROR] XML request isn't valid
[Fri Nov 02 15:11:46 2012] [EVENT] == FCGI SHUTDOWN ==
[Fri Nov 02 15:11:46 2012] [EVENT] == TINYOWS SHUTDOWN ==

Has it something to do with the schema? I found a post with something 
similar 
(http://osgeo-org.1560.n6.nabble.com/TinyOWS-wrong-call-in-OpenLayers-InvalidParameterValue-XML-request-isn-t-valid-td5009059.html) 
and replaced all my old tinyows files and copied the ones from the ms4w 
homepage.


Do you have some more ideas?

Am 11/2/2012 10:56 AM, schrieb Rahkonen Jukka:

Hi,

Yes, it seems to be OpenLayers question then. However, do still capture the 
requests because without them you cannot understand what happens really.  My 
guess is that something in wrong in how EPSG:31467 and EPSG:32740 are used and 
OpenLayers is requesting data from a place where there are no data.

-Jukka-

aho wrote:



Hi Jukka,
thanks a lot for your answer and the good tips! I tried all of the links

and they are working. Also I checked it in QGIS and there I can load it
too.


So I guess it will be better to write again to the openlayers mailinglist?!


Am 11/2/2012 10:21 AM, schrieb Rahkonen Jukka:

Hi,

You must capture the traffic between OpenLayers and TinyOWS.  I am using myself Fiddler2 
proxy but I suppose that Firebug can show you what OpenLayers is sending and high enough 
TinyOWS logging level will also gather requests into tinyows log. The software is not 
important but you just have to get the requests so you can resend them with a browser or 
some other tool that yuo can control and see what happens. You can also include the 
requests in your further mails. Then the question will be OpenLayers is sending 
this and TinyOWS is sending back that, what's wrong? and it will be much easier to 
answer.

As always with WFS, start with these requests with a browser before doing 
anything with OpenLayers:
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetCapabilitiesversion=1.1.0

http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=DescribeFeatureTypeversion=1.1.0typename=water:pipeline_segment

http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetFeatureversion=1.1.0typename=water:pipeline_segmentmaxFeatures=10

If all those requests work you know that TinyOWS works with those basic 
requests and if OpenLayers application does not get data the reason in probably 
in the application code.


-Jukka Rahkonen-

aho wrote:


hello!
I have a problem with the configuration of tinyows. I have the following

settings in my xml file:


tinyows online_resource=localhost/cgi-bin/tinyows.exe

  schema_dir=C:\ms4w\apps\tinyows\schema\
pg host=localhost user=postgres password=postgres
dbname=watergis port=5432/
metadata name=TinyOWS Server
 title=TinyOWS Server - WFS-T Frida Service /
contact name=TinyOWS Server
site=http://www.tinyows.org/;
email=tinyows-us...@lists.maptools.org /
layer retrievable=1
  writable=1
  ns_prefix=water
  ns_uri=http://localhost/;
  name=pipeline_segment
   

Re: [mapserver-users] tinyows

[Serge Dikiy]

Hi,

http://translate.google.com/translate?sl=rutl=enjs=nprev=_thl=enie=UTF-8layout=2eotf=1u=http%3A%2F%2Fgis-lab.info%2Fforum%2Fviewtopic.php%3Ff%3D41%26t%3D10329

BR

On Fri, Nov 2, 2012 at 4:15 PM, aho forum.emai...@googlemail.com wrote:
 Hi Jukka,

 ok, I solved the problem with the requests. The following returns from
 tinyOWS:

 ?xml version='1.0' encoding='UTF-8'?
 ows:ExceptionReport
  xmlns='http://www.opengis.net/ows'
  xmlns:ows='http://www.opengis.net/ows'
  xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
  xsi:schemaLocation='http://www.opengis.net/ows
 http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'
  version='1.1.0' language='en'
  ows:Exception exceptionCode='InvalidParameterValue' locator='request'
   ows:ExceptionTextXML request isn't valid/ows:ExceptionText
  /ows:Exception
 /ows:ExceptionReport

 Here is the errorlog:

 Fri Nov 02 15:11:46 2012] [EVENT] == FCGI START ==
 [Fri Nov 02 15:11:46 2012] [QUERY] wfs:GetFeature
 xmlns:wfs=http://www.opengis.net/wfs; service=WFS version=1.0.0
 xsi:schemaLocation=http://www.opengis.net/wfs
 http://schemas.opengis.net/wfs/1.0.0/WFS-transaction.xsd water
 http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsamp;request=GetFeatureamp;version=1.0.0amp;typename=water:armature;
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;wfs:Query
 typeName=feature:armature xmlns:feature=waterogc:Filter
 xmlns:ogc=http://www.opengis.net/ogc;ogc:BBOXogc:PropertyNamegeometry/ogc:PropertyNamegml:Box
 xmlns:gml=http://www.opengis.net/gml; srsName=EPSG:32740gml:coordinates
 decimal=. cs=, ts= -2866.3885602952,-1910.9257068634
 2866.3885602952,1910.9257068634/gml:coordinates/gml:Box/ogc:BBOX/ogc:Filter/wfs:Query/wfs:GetFeature
 [Fri Nov 02 15:11:46 2012] [ERROR] Element
 '{http://www.w3.org/2001/XMLSchema}import': Failed to locate a schema at
 location
 'localhost/cgi-bin/tinyows.exe?service=WFSrequest=DescribeFeatureTypeversion=1.0.0'.
 Skipping the import.

 [Fri Nov 02 15:11:46 2012] [ERROR] Element
 '{http://www.opengis.net/wfs}GetFeature': No matching global declaration
 available for the validation root.

 [Fri Nov 02 15:11:46 2012] [ERROR] XML request isn't valid
 [Fri Nov 02 15:11:46 2012] [EVENT] == FCGI SHUTDOWN ==
 [Fri Nov 02 15:11:46 2012] [EVENT] == TINYOWS SHUTDOWN ==

 Has it something to do with the schema? I found a post with something
 similar
 (http://osgeo-org.1560.n6.nabble.com/TinyOWS-wrong-call-in-OpenLayers-InvalidParameterValue-XML-request-isn-t-valid-td5009059.html)
 and replaced all my old tinyows files and copied the ones from the ms4w
 homepage.

 Do you have some more ideas?

 Am 11/2/2012 10:56 AM, schrieb Rahkonen Jukka:

 Hi,

 Yes, it seems to be OpenLayers question then. However, do still capture the
 requests because without them you cannot understand what happens really.  My
 guess is that something in wrong in how EPSG:31467 and EPSG:32740 are used
 and OpenLayers is requesting data from a place where there are no data.

 -Jukka-

 aho wrote:


 Hi Jukka,

 thanks a lot for your answer and the good tips! I tried all of the links

 and they are working. Also I checked it in QGIS and there I can load it
 too.

 So I guess it will be better to write again to the openlayers mailinglist?!

 Am 11/2/2012 10:21 AM, schrieb Rahkonen Jukka:

 Hi,

 You must capture the traffic between OpenLayers and TinyOWS.  I am using
 myself Fiddler2 proxy but I suppose that Firebug can show you what
 OpenLayers is sending and high enough TinyOWS logging level will also gather
 requests into tinyows log. The software is not important but you just have
 to get the requests so you can resend them with a browser or some other tool
 that yuo can control and see what happens. You can also include the requests
 in your further mails. Then the question will be OpenLayers is sending this
 and TinyOWS is sending back that, what's wrong? and it will be much easier
 to answer.

 As always with WFS, start with these requests with a browser before doing
 anything with OpenLayers:
 http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetCapabilitiesversion=1.1.0

 http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=DescribeFeatureTypeversion=1.1.0typename=water:pipeline_segment

 http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetFeatureversion=1.1.0typename=water:pipeline_segmentmaxFeatures=10

 If all those requests work you know that TinyOWS works with those basic
 requests and if OpenLayers application does not get data the reason in
 probably in the application code.


 -Jukka Rahkonen-

 aho wrote:

 hello!
 I have a problem with the configuration of tinyows. I have the following

 settings in my xml file:

 tinyows online_resource=localhost/cgi-bin/tinyows.exe

  schema_dir=C:\ms4w\apps\tinyows\schema\
 pg host=localhost user=postgres password=postgres
 dbname=watergis port=5432/
 metadata name=TinyOWS Server
 title=TinyOWS Server - WFS-T Frida Service /
 contact 

Re: [mapserver-users] tinyows

[aho]

Hello,

thanks for the suggestion, I think I am a step further!
But here is the next problem: I found something that could make a problem:

http://127.0.0.1:8000/WNT/proxy.cgi?url=http%3A%2F%2Flocalhost%3A8000%2Fredir%2Fcgi-bin%2Ftinyows.exe 
500 (Internal Server Error)


what do I need to set in the prox.cgi and for what is the 
OpenLayers.ProxyHost = proxy.cgi?url= good?


Could that be the problem?

Am 11/2/2012 3:29 PM, schrieb Serge Dikiy:

Hi,

http://translate.google.com/translate?sl=rutl=enjs=nprev=_thl=enie=UTF-8layout=2eotf=1u=http%3A%2F%2Fgis-lab.info%2Fforum%2Fviewtopic.php%3Ff%3D41%26t%3D10329

BR

On Fri, Nov 2, 2012 at 4:15 PM, aho forum.emai...@googlemail.com wrote:

Hi Jukka,

ok, I solved the problem with the requests. The following returns from
tinyOWS:

?xml version='1.0' encoding='UTF-8'?
ows:ExceptionReport
  xmlns='http://www.opengis.net/ows'
  xmlns:ows='http://www.opengis.net/ows'
  xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
  xsi:schemaLocation='http://www.opengis.net/ows
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'
  version='1.1.0' language='en'
  ows:Exception exceptionCode='InvalidParameterValue' locator='request'
   ows:ExceptionTextXML request isn't valid/ows:ExceptionText
  /ows:Exception
/ows:ExceptionReport

Here is the errorlog:

Fri Nov 02 15:11:46 2012] [EVENT] == FCGI START ==
[Fri Nov 02 15:11:46 2012] [QUERY] wfs:GetFeature
xmlns:wfs=http://www.opengis.net/wfs; service=WFS version=1.0.0
xsi:schemaLocation=http://www.opengis.net/wfs
http://schemas.opengis.net/wfs/1.0.0/WFS-transaction.xsd water
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsamp;request=GetFeatureamp;version=1.0.0amp;typename=water:armature;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;wfs:Query
typeName=feature:armature xmlns:feature=waterogc:Filter
xmlns:ogc=http://www.opengis.net/ogc;ogc:BBOXogc:PropertyNamegeometry/ogc:PropertyNamegml:Box
xmlns:gml=http://www.opengis.net/gml; srsName=EPSG:32740gml:coordinates
decimal=. cs=, ts= -2866.3885602952,-1910.9257068634
2866.3885602952,1910.9257068634/gml:coordinates/gml:Box/ogc:BBOX/ogc:Filter/wfs:Query/wfs:GetFeature
[Fri Nov 02 15:11:46 2012] [ERROR] Element
'{http://www.w3.org/2001/XMLSchema}import': Failed to locate a schema at
location
'localhost/cgi-bin/tinyows.exe?service=WFSrequest=DescribeFeatureTypeversion=1.0.0'.
Skipping the import.

[Fri Nov 02 15:11:46 2012] [ERROR] Element
'{http://www.opengis.net/wfs}GetFeature': No matching global declaration
available for the validation root.

[Fri Nov 02 15:11:46 2012] [ERROR] XML request isn't valid
[Fri Nov 02 15:11:46 2012] [EVENT] == FCGI SHUTDOWN ==
[Fri Nov 02 15:11:46 2012] [EVENT] == TINYOWS SHUTDOWN ==

Has it something to do with the schema? I found a post with something
similar
(http://osgeo-org.1560.n6.nabble.com/TinyOWS-wrong-call-in-OpenLayers-InvalidParameterValue-XML-request-isn-t-valid-td5009059.html)
and replaced all my old tinyows files and copied the ones from the ms4w
homepage.

Do you have some more ideas?

Am 11/2/2012 10:56 AM, schrieb Rahkonen Jukka:

Hi,

Yes, it seems to be OpenLayers question then. However, do still capture the
requests because without them you cannot understand what happens really.  My
guess is that something in wrong in how EPSG:31467 and EPSG:32740 are used
and OpenLayers is requesting data from a place where there are no data.

-Jukka-

aho wrote:


Hi Jukka,

thanks a lot for your answer and the good tips! I tried all of the links

and they are working. Also I checked it in QGIS and there I can load it
too.

So I guess it will be better to write again to the openlayers mailinglist?!

Am 11/2/2012 10:21 AM, schrieb Rahkonen Jukka:

Hi,

You must capture the traffic between OpenLayers and TinyOWS.  I am using
myself Fiddler2 proxy but I suppose that Firebug can show you what
OpenLayers is sending and high enough TinyOWS logging level will also gather
requests into tinyows log. The software is not important but you just have
to get the requests so you can resend them with a browser or some other tool
that yuo can control and see what happens. You can also include the requests
in your further mails. Then the question will be OpenLayers is sending this
and TinyOWS is sending back that, what's wrong? and it will be much easier
to answer.

As always with WFS, start with these requests with a browser before doing
anything with OpenLayers:
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetCapabilitiesversion=1.1.0

http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=DescribeFeatureTypeversion=1.1.0typename=water:pipeline_segment

http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfsrequest=GetFeatureversion=1.1.0typename=water:pipeline_segmentmaxFeatures=10

If all those requests work you know that TinyOWS works with those basic
requests and if OpenLayers application does not get data the reason in
probably in the application code.


-Jukka Rahkonen-

aho wrote:

hello!
I 

Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid

[Riccardo Gaeta]

Yes, now I get:

{type: FeatureCollection,
crs:{type:name,properties:{name:urn:ogc:def:crs:EPSG::3857}},
features: [{type:Feature, properties:{gid: 1, id_posto:
25, id_servizi: 2, n_posto: 1},
geometry:{type:Point,bbox:[1572057,5243856,1572057,5243856],coordinates:[1572057,5243856]}}
,]}

Look good doesn't it?



2012/10/24 Olivier Courtin olivier.cour...@gmail.com

 On Wed, Oct 24, 2012 at 11:52 AM, Riccardo Gaeta riccardo...@gmail.comwrote:

 Riccardo,

 I get this message, seems GeoJSON is not accepted as output, maybe I need
 some more .dll library in my Win7?


 You don't need any extra lib, it's plain vanillia.

 I didn't check my previous URL before posting,
 so OUTPUTFORMAT parameter expect application/json

 HTH,

 --
 Olivier

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


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

Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid

[Riccardo Gaeta]

I get this message, seems GeoJSON is not accepted as output, maybe I need
some more .dll library in my Win7?

ExceptionReport xmlns=http://www.opengis.net/ows; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=
http://www.opengis.net/ows
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd; version=1.0.0
 language=en
Exception exceptionCode=OutputFormatNotSupported locator=GetFeature
ExceptionTextOutputFormat is not supported/ExceptionText
/Exception
/ExceptionReport


2012/10/22 Olivier Courtin olivier.cour...@gmail.com

 On Mon, Oct 22, 2012 at 4:55 PM, Riccardo Gaeta riccardo...@gmail.comwrote:

 HI Riccardo,


 I have quite solved the problem.


 Great to hear it !


 P.S.: As GeoJSON I get the following error message (from FireBug of
 Mozilla):
 JSON.parse: unexpected character
 Uncaught SyntaxError: Unexpected token ] 

 I don't know why. Anyway, for now is enough GML. Or if you know the
 reasons I get this error could be interesting to know...



 Could you provide GeoJson output from TinyOWS for a single feature
 i.e something like

 http://your_server/cgi-bin/tinyows.fcgi?SERVICE=WFSREQUEST=GetFeatureOUTPUTFORMAT=application/geojsonTYPENAME=ns:your_layerMAXFEATURES=1


 --
 Olivier

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


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

Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid

[Olivier Courtin]

On Wed, Oct 24, 2012 at 11:52 AM, Riccardo Gaeta riccardo...@gmail.comwrote:

Riccardo,

I get this message, seems GeoJSON is not accepted as output, maybe I need
 some more .dll library in my Win7?


You don't need any extra lib, it's plain vanillia.

I didn't check my previous URL before posting,
so OUTPUTFORMAT parameter expect application/json

HTH,

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

Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid

[Riccardo Gaeta]

Hi all.
I have quite solved the problem.
I need just to load another OpenLayers.js built with inside the GML vector
style.
So I add on my .html file this row:

script type=text/javascript src=http://openlayers.org/dev/OpenLayers.js
/script

Obviously I've to load my layer not as a GeoJSON but as GML:

readFormat: new OpenLayers.Format.GML({
   'internalProjection': new OpenLayers.Projection(EPSG:900913),
   'externalProjection': new OpenLayers.Projection(EPSG:900913)
})

Now it works!

Thanks at all,
Riccardo

P.S.: As GeoJSON I get the following error message (from FireBug of
Mozilla):
JSON.parse: unexpected character
Uncaught SyntaxError: Unexpected token ] 

I don't know why. Anyway, for now is enough GML. Or if you know the reasons
I get this error could be interesting to know...

2012/10/18 Riccardo Gaeta riccardo...@gmail.com

 I go to the link you suggest but I didn't find the rc4 version for windows
 to download...

 Anyway, I copy some dll (like gdal, geos,xercers,libxml2,etc) into my
 cgi-bin directory from a previous version of an Apache2 windows
 installation.
 And the error message change!
 Now I obtain (from tinyows.log):
 [ERROR] Element '{http://www.w3.org/2001/XMLSchema}import': Skipping
 import of schema located at '
 http://schemas.opengis.net/gml/2.1.2/feature.xsd' for the namespace '
 http://www.opengis.net/gml', since this namespace was already imported
 with the schema located at '
 http://127.0.0.1:8080/tinyows/schema/gml/2.1.2/feature.xsd'.
 [ERROR] Filter parameter doesn't validate WFS Schema

 On QGIS always work well.
 Mmmmhh

 I suppose I have maybe 2 problem:
 1-I need some dll library in window
 2-the tinyows.exe of version 1.0.0rc3 is damaged in someway

 Thanks again for your help, any other tips is appreciated!

 riccardo


 2012/10/18 Olivier Courtin olivier.cour...@gmail.com

 0.9 version is that old, and should not be used anymore, for any
 reasons...
 1.0.0rc3, well was an rc, and several fixes was corrected before
 launching 1.0.0

 You could give a look at OSGeo4W as they provide a 1.0.0rc4 (yeap still
 an rc)
 http://trac.osgeo.org/osgeo4w/wiki/pkg-tinyows

 But a real solution would be that someone take Win32 packaging in charge,
  Also for information:

 http://gis-lab.info/qa/tinyows-compile-vce-eng.html

  --
 Olivier

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



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

Re: [mapserver-users] TinyOWS 12.10rc1

[Peter Hopfgartner]

On 10/15/2012 12:21 AM, Olivier Courtin wrote:

Hi all,

TinyOWS 12.10rc1 is yet available:
http://www.tinyows.org/release/mapserver-tinyows-12.10rc1.tar.bz2

Thanks in advance in advance to test,
and report any bug or regression on this list

12.10 NEWS:
 - Generate PK value using PostgresSQL DEFAULT value if present (Serge 
Dikiy)
 - XSD max length and enumeration constraint handling (Serge Dikiy  
Alan Boudreault)
 - include_items and exclude_items config handling. To choose exactly 
which columns to retrieve (Serge Dikiy)
 - Add pkey configuration in layer config. Usefull for instance when 
retrieving data from a VIEW. (Serge Dikiy)

 - Buffer copy performance improve (Serge Dikiy)
 - Rewrite/fix max features handling (Olivier Courtin)
 - Several bugfixes as usual (special thanks to Andreas Peri, Serge 
Dikiy and Jukka Rahkonen for detailled reports)



--
Olivier


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


Hi Olivier,

I was happily trying to build it on CentOS 6, but it seems that my 
libxml2 is simply too old:


checking for libxml2 version... 2.7.6
configure: error: You need at least libxml 2.8.0

Is there a real reason to require 2.8.0 or could this be relaxed?

Regards,

Peter

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

Re: [mapserver-users] TinyOWS 12.10rc1

[Olivier Courtin]

Hi Peter,

I was happily trying to build it on CentOS 6, but it seems that my libxml2
 is simply too old:

 checking for libxml2 version... 2.7.6
 configure: error: You need at least libxml 2.8.0

 Is there a real reason to require 2.8.0 or could this be relaxed?


The reason is related to a libxml2 bug on schema handling, been fixed in
2.8.0.
cf http://mapserver.org/trunk/fr/tinyows/libxmlschemagmlbug.html,

If you really don't want to upgrade (even if it's not a big deal to compile
libxml2)
you could either choose:
 - to slightly modified OGC XSD Schema as describted:
  http://mapserver.org/trunk/fr/tinyows/libxmlschemagmlbug.html

 - or be sure to never use GML 3.1.1 (as the bug only impact this schema)

HTH,

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

Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid

[Olivier Courtin]

On Mon, Oct 22, 2012 at 4:55 PM, Riccardo Gaeta riccardo...@gmail.comwrote:

HI Riccardo,


 I have quite solved the problem.


Great to hear it !


 P.S.: As GeoJSON I get the following error message (from FireBug of
 Mozilla):
 JSON.parse: unexpected character
 Uncaught SyntaxError: Unexpected token ] 

 I don't know why. Anyway, for now is enough GML. Or if you know the
 reasons I get this error could be interesting to know...



Could you provide GeoJson output from TinyOWS for a single feature
i.e something like
http://your_server/cgi-bin/tinyows.fcgi?SERVICE=WFSREQUEST=GetFeatureOUTPUTFORMAT=application/geojsonTYPENAME=ns:your_layerMAXFEATURES=1


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

Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid

[Riccardo Gaeta]

Ok.
First of all I have to say that I use as Apache the EntrepriseDB-ApachePHP,
installed by PostgreSQL Application Stack Builder, I don't know if this
could be the problem...
Anyway, for Tinyows I unzip the file:
tinyows-1.0.0rc3-ms4w3.0.zip

Then:

- I've moved the folder tinyows (with the folder schema and the
config.xml) in C:\PostgreSQL\EnterpriseDB-ApachePHP

- I've moved the file tinyows.exe in
C:\PostgreSQL\EnterpriseDB-ApachePHP\apache\cgi-bin

- I've moved the file http_tinyows.conf in
C:\PostgreSQL\EnterpriseDB-ApachePHP\apache\conf\addons

- I've changed the content of the file http_tinyows.conf in:
# set environment vars necessary for Tinyows:
SetEnv TINYOWS_CONFIG_FILE
C:\PostgreSQL\EnterpriseDB-ApachePHP\tinyows\config.xml
SetEnv TINYOWS_SCHEMA_DIR
C:\PostgreSQL\EnterpriseDB-ApachePHP\tinyows\schema\

- I've added the follow lines at the end of the httpd.conf:
Alias /tinyows/ C:\PostgreSQL\EnterpriseDB-ApachePHP\tinyows\

Directory C:\PostgreSQL\EnterpriseDB-ApachePHP\tinyows
AllowOverride None
Options Indexes FollowSymLinks Multiviews
Order allow,deny
Allow from all
/Directory

- In the head of the file config.xml I put:
tinyows online_resource=http://127.0.0.1:8080/cgi-bin/tinyows.exe;
schema_dir=C:\PostgreSQL\EnterpriseDB-ApachePHP\apache\www\tinyows\schema\
log=C:\PostgreSQL\EnterpriseDB-ApachePHP\apache\logs\tinyows.log
log_level=7

Hope this could help.
Now I'm trying to do some test with the older version 0.9.0, I'll let you
know.

Riccardo



2012/10/18 Olivier Courtin olivier.cour...@gmail.com



 On Wed, Oct 17, 2012 at 2:09 PM, Riccardo Gaeta riccardo...@gmail.comwrote:

 Thanks Olivier. It doesn't work anyway. I can see the layer base but
 not my tinyows layer...


 Humm, could you give information on the way you install TinyOWS on your
 Win32  ?
 (looking for a way to reproduce this behaviour...)

 --
 Olivier

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


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

Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid

[Riccardo Gaeta]

I'm testing the pevious version for windows, the 0.9.0, and it doesn't work
as well.
But from the Windows shell when  I launch:
.\tinyows.exe --check

With this 0.9 version I get the first rows that seems to be good:
TinyOWS version:   0.9.0
FCGI support:  Yes
Config File Path:  @prefix@/tinyows/config.xml

Then the program tinyows.exe crash and I've to close it. Strange!
But if I think that with the version 1.0 I just get:
?xml version='1.0' encoding='UTF-8'?
ows:ExceptionReport
 xmlns='http://www.opengis.net/ows'
 xmlns:ows='http://www.opengis.net/ows'
 xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
 xsi:schemaLocation='http://www.opengis.net/ows
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'
 version='1.1.0' language='en'
 ows:Exception exceptionCode='ErrorConfigFile' locator='parse_config_file'
  ows:ExceptionTextUnable to open config file !/ows:ExceptionText
 /ows:Exception
/ows:ExceptionReport

The message get with the version 0.9 sounds to me better!

Anyway it doesn't work as well because it crash also by browser...



2012/10/18 Riccardo Gaeta riccardo...@gmail.com

 Ok.
 First of all I have to say that I use as Apache the
 EntrepriseDB-ApachePHP, installed by PostgreSQL Application Stack
 Builder, I don't know if this could be the problem...
 Anyway, for Tinyows I unzip the file:
 tinyows-1.0.0rc3-ms4w3.0.zip

 Then:

 - I've moved the folder tinyows (with the folder schema and the
 config.xml) in C:\PostgreSQL\EnterpriseDB-ApachePHP

 - I've moved the file tinyows.exe in
 C:\PostgreSQL\EnterpriseDB-ApachePHP\apache\cgi-bin

 - I've moved the file http_tinyows.conf in
 C:\PostgreSQL\EnterpriseDB-ApachePHP\apache\conf\addons

 - I've changed the content of the file http_tinyows.conf in:
 # set environment vars necessary for Tinyows:
 SetEnv TINYOWS_CONFIG_FILE
 C:\PostgreSQL\EnterpriseDB-ApachePHP\tinyows\config.xml
 SetEnv TINYOWS_SCHEMA_DIR
 C:\PostgreSQL\EnterpriseDB-ApachePHP\tinyows\schema\

 - I've added the follow lines at the end of the httpd.conf:
 Alias /tinyows/ C:\PostgreSQL\EnterpriseDB-ApachePHP\tinyows\

 Directory C:\PostgreSQL\EnterpriseDB-ApachePHP\tinyows
 AllowOverride None
 Options Indexes FollowSymLinks Multiviews
 Order allow,deny
 Allow from all
 /Directory

 - In the head of the file config.xml I put:
 tinyows online_resource=http://127.0.0.1:8080/cgi-bin/tinyows.exe;
 schema_dir=C:\PostgreSQL\EnterpriseDB-ApachePHP\apache\www\tinyows\schema\
 log=C:\PostgreSQL\EnterpriseDB-ApachePHP\apache\logs\tinyows.log
 log_level=7

 Hope this could help.
 Now I'm trying to do some test with the older version 0.9.0, I'll let you
 know.

 Riccardo



 2012/10/18 Olivier Courtin olivier.cour...@gmail.com



 On Wed, Oct 17, 2012 at 2:09 PM, Riccardo Gaeta riccardo...@gmail.comwrote:

 Thanks Olivier. It doesn't work anyway. I can see the layer base but
 not my tinyows layer...


 Humm, could you give information on the way you install TinyOWS on your
 Win32  ?
 (looking for a way to reproduce this behaviour...)

 --
 Olivier

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



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

Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid

[Olivier Courtin]

0.9 version is that old, and should not be used anymore, for any reasons...
1.0.0rc3, well was an rc, and several fixes was corrected before launching
1.0.0

You could give a look at OSGeo4W as they provide a 1.0.0rc4 (yeap still an
rc)
http://trac.osgeo.org/osgeo4w/wiki/pkg-tinyows

But a real solution would be that someone take Win32 packaging in charge,
Also for information:

http://gis-lab.info/qa/tinyows-compile-vce-eng.html

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

Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid

[Riccardo Gaeta]

I go to the link you suggest but I didn't find the rc4 version for windows
to download...

Anyway, I copy some dll (like gdal, geos,xercers,libxml2,etc) into my
cgi-bin directory from a previous version of an Apache2 windows
installation.
And the error message change!
Now I obtain (from tinyows.log):
[ERROR] Element '{http://www.w3.org/2001/XMLSchema}import': Skipping import
of schema located at 'http://schemas.opengis.net/gml/2.1.2/feature.xsd' for
the namespace 'http://www.opengis.net/gml', since this namespace was
already imported with the schema located at '
http://127.0.0.1:8080/tinyows/schema/gml/2.1.2/feature.xsd'.
[ERROR] Filter parameter doesn't validate WFS Schema

On QGIS always work well.
Mmmmhh

I suppose I have maybe 2 problem:
1-I need some dll library in window
2-the tinyows.exe of version 1.0.0rc3 is damaged in someway

Thanks again for your help, any other tips is appreciated!

riccardo


2012/10/18 Olivier Courtin olivier.cour...@gmail.com

 0.9 version is that old, and should not be used anymore, for any reasons...
 1.0.0rc3, well was an rc, and several fixes was corrected before launching
 1.0.0

 You could give a look at OSGeo4W as they provide a 1.0.0rc4 (yeap still an
 rc)
 http://trac.osgeo.org/osgeo4w/wiki/pkg-tinyows

 But a real solution would be that someone take Win32 packaging in charge,
 Also for information:

 http://gis-lab.info/qa/tinyows-compile-vce-eng.html

 --
 Olivier

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


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

Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid

[Riccardo Gaeta]

Thanks Olivier. It doesn't work anyway. I can see the layer base but not
my tinyows layer...
I post for you:

1) my config.xml file:

tinyows online_resource=http://127.0.0.1:8080/cgi-bin/tinyows.exe;
schema_dir=C:\PostgreSQL\EnterpriseDB-ApachePHP\tinyows\schema\
log=C:\PostgreSQL\EnterpriseDB-ApachePHP\apache\logs\tinyows.log
log_level=7

pg host=localhost user=*** password=*** dbname=*** port=5432/
metadata name=TinyOWS Server title=TinyOWS Server - Demo Service /
 layer retrievable=1
   ns_prefix=tows
   ns_uri=http://www.tinyows.org;
   name=france
   title=France Departments Boundaries /

/tinyows

2) the tinyows.log error:

[ERROR] Element '{http://www.w3.org/2001/XMLSchema}import': Failed to
locate a schema at location '
http://127.0.0.1:8080/cgi-bin/tinyows.exe?service=WFSrequest=DescribeFeatureTypeversion=1.0.0'.
Skipping the import.

[ERROR] Element '{http://www.opengis.net/wfs}GetFeature': No matching
global declaration available for the validation root.

3) the result of the call '
http://127.0.0.1:8080/cgi-bin/tinyows.exe?service=WFSrequest=DescribeFeatureTypeversion=1.0.0'
seems to work. I get:

xs:schema xmlns:tows=http://www.tinyows.org; xmlns:ogc=
http://www.opengis.net/ogcxmlns:xs=http://www.w3.org/2001/XMLSchema
 xmlns=http://www.w3.org/2001/XMLSchema; xmlns:gml=
http://www.opengis.net/gmltargetNamespace=http://www.tinyows.org
 elementFormDefault=qualified version=1.0
xs:import namespace=http://www.opengis.net/gml; schemaLocation=
http://schemas.opengis.net/gml/2.1.2/feature.xsd/
xs:element name=france type=tows:franceType
substitutionGroup=gml:_Feature/
xs:complexType name=franceType
xs:complexContent
xs:extension base=gml:AbstractFeatureType
xs:sequence
xs:element name=id_geofla type=decimal nillable=true
minOccurs=0 maxOccurs=1/
xs:element name=code_chf_l type=string nillable=true
minOccurs=0 maxOccurs=1/
xs:element name=nom_chf_l type=string nillable=true
minOccurs=0 maxOccurs=1/
xs:element name=x_chf_lieu type=int nillable=true minOccurs=0
maxOccurs=1/
xs:element name=y_chf_lieu type=int nillable=true minOccurs=0
maxOccurs=1/
xs:element name=x_centroid type=int nillable=true minOccurs=0
maxOccurs=1/
xs:element name=y_centroid type=int nillable=true minOccurs=0
maxOccurs=1/
xs:element name=nom_dept type=string nillable=true
minOccurs=0 maxOccurs=1/
xs:element name=code_reg type=string nillable=true
minOccurs=0 maxOccurs=1/
xs:element name=nom_region type=string nillable=true
minOccurs=0 maxOccurs=1/
xs:element name=code_dept type=string nillable=true
minOccurs=0 maxOccurs=1/
xs:element name=geom type=gml:MultiPolygonPropertyType
nillable=true minOccurs=0 maxOccurs=1/
/xs:sequence
/xs:extension
/xs:complexContent
/xs:complexType
/xs:schema

4) Finally the error on apache error.log:
[client 127.0.0.1] error : No such file or directory\r, referer:
http://localhost:8080/tinyows.html
[error] [client 127.0.0.1] I/O warning : failed to load external entity 
http://127.0.0.1:8080/cgi-bin/tinyows.exe?service=WFSrequest=DescribeFeatureTypeversion=1.0.0\r,
referer: http://localhost:8080/tinyows.html

On QGIS I'm able to load the layer without problem, as before.

Thanks again,
Riccardo


P.S.:sorry Olivier maybe before I've answered just to you...


2012/10/16 Olivier Courtin olivier.cour...@gmail.com

 Hi Riccardo,

 Well if everything work's fine except OpenLayers,
 maybe it's an OpenLayers configuration issue...

 TinyOWS debug tools are really unix based,
 so could be a bit painfull under Win32...

 I suggest you to begin to follow step by step
 this tutorial, to check that everything work as expected:
 http://mapserver.org/trunk/tinyows/openlayershowtobasic.html


 Nota: With OpenLayers client retrieving data as GeoJson
 is a better idea than as GML.

 HTH,

 --
 Olivier

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


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

[mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid

[Riccardo Gaeta]

Hi all,
I'm using Tinyows 1.0.0 on win7 machine, postgresql 9.1 and postgis 1.5.5.
All seems to work well, I mean:

1)
http://127.0.0.1:8080/cgi-bin/tinyows.exe?service=WFSrequest=DescribeFeatureTypeversion=1.0.0
Give a good answer

2)
http://localhost:8080/cgi-bin/tinyows.exe?service=wfsversion=1.0.0request=getfeaturetypename=posti_geommaxfeatures=1
Give a good answer

3) QGIS is capable to retrieve and plot the data (points)

So, the problems:

A) I'm not able from the shell of windows to launchcorrectly:
.\tinyows.exe --check
I get always the same error:
Unable to open config file
But maybe is a Windows error, because as I said by browser I'm pretty able
to retrieve the information I need.

B) Most important, I'm not able to have my data on OpenLayers!
Looking at tinyows.log I had these error messages:

[ERROR] Element '{http://www.w3.org/2001/XMLSchema}import': Failed to
locate a schema at location '
http://127.0.0.1:8080/cgi-bin/tinyows.exe?service=WFSrequest=DescribeFeatureTypeversion=1.1.0'.
Skipping the import.

[ERROR] Element '{http://www.opengis.net/wfs}GetFeature': No matching
global declaration available for the validation root.

And finally:
[ERROR] XML request isn't valid

The call made by TinyOws to retrieve the layer in OpenLayers seems to be
(from tinyows.log):
[QUERY] wfs:GetFeature xmlns:wfs=http://www.opengis.net/wfs;
service=WFS version=1.1.0 xsi:schemaLocation=http://www.opengis.net/wfs
http://schemas.opengis.net/wfs/1.1.0/wfs.xsd; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;wfs:Query
typeName=feature:posti_geom srsName=EPSG:4326 xmlns:feature=
http://localhost:8080///wfs:GetFeature

But I'm not trying to retrieve the data in EPSG:4326, but in 3875 (or
900913)!

Anyway, on the other side, in Apache error.log, I get:
[client 127.0.0.1] error : No such file or directory\r, referer:
http://localhost:8080/mappa.html
[error] [client 127.0.0.1] I/O warning : failed to load external entity 
http://127.0.0.1:8080/cgi-bin/tinyows.exe?service=WFSrequest=DescribeFeatureTypeversion=1.0.0\r,
referer: http://localhost:8080/mappa.html

And, from the browser, I get the following response message:
?xml version='1.0' encoding='UTF-8'?
ows:ExceptionReport
 xmlns='http://www.opengis.net/ows'
 xmlns:ows='http://www.opengis.net/ows'
 xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
 xsi:schemaLocation='http://www.opengis.net/ows
http://schemas.opengis.net/ows/1.0.0/owsExceptionReport.xsd'
 version='1.1.0' language='en'
 ows:Exception exceptionCode='InvalidParameterValue' locator='request'
  ows:ExceptionTextXML request isn't valid/ows:ExceptionText
 /ows:Exception
/ows:ExceptionReport


I don't know what to do, things seems to work fine except on OpenLayers...


I call the tiny_layer in OpenLayers like that:
var points = new OpenLayers.Layer.Vector(punti prova, {
strategies: [new OpenLayers.Strategy.Fixed()],
projection: new OpenLayers.Projection(EPSG:900913),
protocol: new OpenLayers.Protocol.WFS({
url: http://localhost:8080/cgi-bin/tinyows.exe?;,
version: 1.1.0,
featureType: posti_geom,
featureNS: http://localhost:8080/;,
readFormat: new OpenLayers.Format.GML({
'internalProjection': new
OpenLayers.Projection(EPSG:900913),
'externalProjection': new
OpenLayers.Projection(EPSG:900913)
})
})
});

The map is in 900913, with OSM as base layer (the OSM map is loaded without
problem).


Finally my config.xml file:
tinyows online_resource=http://127.0.0.1:8080/cgi-bin/tinyows.exe;
schema_dir=C:\PostgreSQL\EnterpriseDB-ApachePHP\apache\www\tinyows\schema\
log=C:\PostgreSQL\EnterpriseDB-ApachePHP\apache\logs\tinyows.log
log_level=7

pg host=localhost user=*** password=*** dbname=*** port=5432/
metadata name=TinyOWS Server title=TinyOWS Server - Demo Service /

layer retrievable=1
queryable=1
writable=0
ns_prefix=tows
ns_uri=http://localhost:8080/;
server=http://localhost:8080/;
name=posti_geom
title=posti_geom_tiny
schema=public
srid=900913,3857,4326 /

/tinyows

Thanks for any help!

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

Re: [mapserver-users] TinyOWS wrong call in OpenLayers - 'InvalidParameterValue' - XML request isn't valid

[Olivier Courtin]

Hi Riccardo,

Well if everything work's fine except OpenLayers,
maybe it's an OpenLayers configuration issue...

TinyOWS debug tools are really unix based,
so could be a bit painfull under Win32...

I suggest you to begin to follow step by step
this tutorial, to check that everything work as expected:
http://mapserver.org/trunk/tinyows/openlayershowtobasic.html


Nota: With OpenLayers client retrieving data as GeoJson
is a better idea than as GML.

HTH,

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

Re: [mapserver-users] TinyOWS and the logical operators

[Olivier Courtin]

On Sun, Oct 14, 2012 at 1:46 AM, Andrea Peri aperi2...@gmail.com wrote:

Hi Andrea,

reading the getcapabilities, I see the TinyOWS has not any LogicalOperator
 capability like AND , OR, etc..
 Is this correct for wfs 1.1.0 or is a lack of feature ?


LogicalOperators are supported in TinyOWS,
and it appears it the capabilities as LogicalOperators tags.

Indeed you're right there's no detail on what is exactly supported at
capabilities level (indeed it means 'all'),
but it's related to OGC Filter XSD itself:

see schema/filter/1.1.0/filterCapabilities.xsd


Thanks for asking,

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

Re: [mapserver-users] TinyOWS and the logical operators

[Andrea Peri]

mmh...

Hi,

'm try-ing to check the logical operator  but they don't seem work.

If the AND operator is supported this mean that I'm wrong something.

This request will get the results from a query with filter NAME=FIRENZE.

http://web.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs?service=WFSversion=1.1.0request=GetFeaturetypename=infrastrutture:rt_infr_idstrade_rt_bbpropertyName=geometry,dug,toponimo,den_estesa,tipo_prop,cod_istat,comunesortBy=dug+A,toponimo+AFilter=%3CFilter%20xmlns:wfs=%22http://www.opengis.net/wfs%22%3E%3CPropertyIsEqualTo%3E%3CPropertyName%3Ecomune%3C/PropertyName%3E%3CLiteral%3EFIRENZE%3C/Literal%3E%3C/PropertyIsEqualTo%3E%3C/Filter%3E

And the logs report correctly the filter used:

[Sun Oct 14 11:51:50 2012] [SQL] SELECT ST_xmin(g.extent),
ST_ymin(g.extent), ST_xmax(g.extent), ST_ymax(g.extent) FROM (SELECT
ST_Extent(foo.the_geom) as extent FROM (  (SELECT
ST_Transform(geometry::geometry, 3003) AS the_geom FROM
iternet.itnt_stradebb  WHERE comune = 'FIRENZE' ORDER BY dug
ASC,toponimo ASC LIMIT 500) ) AS foo) AS g


Now I try to call the same request with a double filter:
NAME=FIRENZE AND TIPO_PROP=Comune

I build it following a sample from mapserver docs.

http://web.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs?service=WFSversion=1.1.0request=GetFeaturetypename=infrastrutture:rt_infr_idstrade_rt_bbpropertyName=geometry,dug,toponimo,den_estesa,tipo_prop,cod_istat,comunesortBy=dug+A,toponimo+AFilter=Filter
xmlns:wfs=http://www.opengis.net/wfs
ANDPropertyIsEqualToPropertyNamecomune/PropertyNameLiteralFIRENZE/Literal/PropertyIsEqualToPropertyIsEqualToPropertyNametipo_prop/PropertyNameLiteralComune/Literal/PropertyIsEqualTo/AND/Filter

But this request don't return any results.
Seeing the log it report that the query has the where filter empty:

[Sun Oct 14 11:55:38 2012] [SQL] SELECT ogc_fid,ST_AsGML(3,
ST_Transform(geometry::geometry,3003),8, 23) AS geometry
,col_0,cod_top,comune,siglaprov,cod_com,cod_istat,dug,toponimo,cod_reg,den_estesa,tip_prp,tipo_prop,cod_prp,cls_amm,den_breve,data_elab
FROM iternet.itnt_stradebb WHERE  ORDER BY dug ASC,toponimo ASC LIMIT
500

so nothing is find.

If the AND operator is supported from TinyOWS, this mean that I'm wrong
something else.

Any hint is welcome

Thx,

Andrea.

2012/10/14 Olivier Courtin olivier.cour...@gmail.com

 On Sun, Oct 14, 2012 at 1:46 AM, Andrea Peri aperi2...@gmail.com wrote:

 Hi Andrea,

 reading the getcapabilities, I see the TinyOWS has not any LogicalOperator
 capability like AND , OR, etc..
 Is this correct for wfs 1.1.0 or is a lack of feature ?


 LogicalOperators are supported in TinyOWS,
 and it appears it the capabilities as LogicalOperators tags.

 Indeed you're right there's no detail on what is exactly supported at
 capabilities level (indeed it means 'all'),
 but it's related to OGC Filter XSD itself:

 see schema/filter/1.1.0/filterCapabilities.xsd


 Thanks for asking,

 --
 Olivier

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




-- 
-
Andrea Peri
. . . . . . . . .
qwerty àèìòù
-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] TinyOWS and the logical operators

[Olivier Courtin]

On Sun, Oct 14, 2012 at 12:04 PM, Andrea Peri aperi2...@gmail.com wrote:

Andrea,

If the AND operator is supported from TinyOWS, this mean that I'm wrong
 something else.

 Any hint is welcome


If i check with WFS 1.1 CITE:
$ sudo make install-test110

There 3 tests related to And Logical Operator with GetFeature - 0210 to
0212:
So take one:
$ test/unit_test test/wfs_110/cite/0211 4

Input query:
?xml version=1.0 encoding=UTF-8?wfs:GetFeature xmlns:wfs=
http://www.opengis.net/wfs; xmlns:ogc=http://www.opengis.net/ogc; xmlns:p=
http://teamengine.sourceforge.net/parsers; xmlns:xi=
http://www.w3.org/2001/XInclude; xmlns:saxon=http://saxon.sf.net/;
xmlns:xlink=http://www.w3.org/1999/xlink; xmlns=
http://www.occamlab.com/ctl; xmlns:xs=http://www.w3.org/2001/XMLSchema;
xmlns:ows=http://www.opengis.net/ows; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=
http://www.w3.org/2001/XMLSchema; xmlns:ctl=http://www.occamlab.com/ctl;
xmlns:sf=http://cite.opengeospatial.org/gmlsf;
xmlns:tec=java:com.occamlab.te.TECore xmlns:te=http://www.occamlab.com/te;
xmlns:parsers=http://www.occamlab.com/te/parsers; xmlns:gml=
http://www.opengis.net/gml; xmlns:myparsers=
http://teamengine.sourceforge.net/parsers; version=1.1.0
service=WFSwfs:Query
typeName=sf:AggregateGeoFeatureogc:Filterogc:Andogc:PropertyIsGreaterThanOrEqualToogc:PropertyNamesf:doubleProperty/ogc:PropertyNameogc:Literal24510/ogc:Literal/ogc:PropertyIsGreaterThanOrEqualToogc:PropertyIsEqualTo
matchCase=falseogc:PropertyNamesf:featureCode/ogc:PropertyNameogc:Literalak020/ogc:Literal/ogc:PropertyIsEqualTo/ogc:And/ogc:Filter/wfs:Query/wfs:GetFeature


SQL Request produced:
SELECT description,name,ST_AsGML(3,
ST_Transform(multiPointProperty::geometry,4326),6, 23) AS
multiPointProperty ,ST_AsGML(3,
ST_Transform(multiCurveProperty::geometry,4326),6, 23) AS
multiCurveProperty ,ST_AsGML(3,
ST_Transform(multiSurfaceProperty::geometry,4326),6, 23) AS
multiSurfaceProperty
,doubleProperty,intRangeProperty,strProperty,featureCode,id FROM
public.AggregateGeoFeature WHERE (doubleProperty = 24510 AND
lower(featureCode) = lower('ak020'))


I didn't look in detail to you query for now,
let me know it this sample is enough to you (or not),

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

Re: [mapserver-users] TinyOWS and the logical operators

[Andrea Peri]

Hi Olivier,

I resolved it.

The and operator is named using the first letter uppercase.

So  And is recognized, meanwhile AND was not recognized.
I guest perhaps there is some bugs, but not really sure.

However this version of the request work and has the right result.

http://web.regione.toscana.it/wfsvector/com.rt.wfs.RTmap/wfs?service=WFSversion=1.1.0request=GetFeaturetypename=infrastrutture:rt_infr_idstrade_rt_bbpropertyName=geometry,dug,toponimo,den_estesa,tipo_prop,cod_istat,comunesortBy=dug+A,toponimo+AFilter=Filter
xmlns:wfs=http://www.opengis.net/wfs
AndPropertyIsEqualToPropertyNamecomune/PropertyNameLiteralFIRENZE/Literal/PropertyIsEqualToPropertyIsEqualToPropertyNametipo_prop/PropertyNameLiteralComune/Literal/PropertyIsEqualTo/And/Filter

Many thx,


2012/10/14 Olivier Courtin olivier.cour...@gmail.com

 On Sun, Oct 14, 2012 at 12:04 PM, Andrea Peri aperi2...@gmail.com wrote:

 Andrea,


 If the AND operator is supported from TinyOWS, this mean that I'm wrong
 something else.

 Any hint is welcome


 If i check with WFS 1.1 CITE:
 $ sudo make install-test110

 There 3 tests related to And Logical Operator with GetFeature - 0210 to
 0212:
 So take one:
 $ test/unit_test test/wfs_110/cite/0211 4

 Input query:
 ?xml version=1.0 encoding=UTF-8?wfs:GetFeature xmlns:wfs=
 http://www.opengis.net/wfs; xmlns:ogc=http://www.opengis.net/ogc;
 xmlns:p=http://teamengine.sourceforge.net/parsers; xmlns:xi=
 http://www.w3.org/2001/XInclude; xmlns:saxon=http://saxon.sf.net/;
 xmlns:xlink=http://www.w3.org/1999/xlink; xmlns=
 http://www.occamlab.com/ctl; xmlns:xs=http://www.w3.org/2001/XMLSchema;
 xmlns:ows=http://www.opengis.net/ows; xmlns:xsi=
 http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=
 http://www.w3.org/2001/XMLSchema; xmlns:ctl=http://www.occamlab.com/ctl;
 xmlns:sf=http://cite.opengeospatial.org/gmlsf;
 xmlns:tec=java:com.occamlab.te.TECore xmlns:te=
 http://www.occamlab.com/te; xmlns:parsers=
 http://www.occamlab.com/te/parsers; xmlns:gml=http://www.opengis.net/gml;
 xmlns:myparsers=http://teamengine.sourceforge.net/parsers;
 version=1.1.0 service=WFSwfs:Query
 typeName=sf:AggregateGeoFeatureogc:Filterogc:Andogc:PropertyIsGreaterThanOrEqualToogc:PropertyNamesf:doubleProperty/ogc:PropertyNameogc:Literal24510/ogc:Literal/ogc:PropertyIsGreaterThanOrEqualToogc:PropertyIsEqualTo
 matchCase=falseogc:PropertyNamesf:featureCode/ogc:PropertyNameogc:Literalak020/ogc:Literal/ogc:PropertyIsEqualTo/ogc:And/ogc:Filter/wfs:Query/wfs:GetFeature


 SQL Request produced:
 SELECT description,name,ST_AsGML(3,
 ST_Transform(multiPointProperty::geometry,4326),6, 23) AS
 multiPointProperty ,ST_AsGML(3,
 ST_Transform(multiCurveProperty::geometry,4326),6, 23) AS
 multiCurveProperty ,ST_AsGML(3,
 ST_Transform(multiSurfaceProperty::geometry,4326),6, 23) AS
 multiSurfaceProperty
 ,doubleProperty,intRangeProperty,strProperty,featureCode,id FROM
 public.AggregateGeoFeature WHERE (doubleProperty = 24510 AND
 lower(featureCode) = lower('ak020'))


 I didn't look in detail to you query for now,
 let me know it this sample is enough to you (or not),

 --
 Olivier

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




-- 
-
Andrea Peri
. . . . . . . . .
qwerty àèìòù
-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] TinyOWS and the logical operators

[Olivier Courtin]

On Sun, Oct 14, 2012 at 2:19 PM, Andrea Peri aperi2...@gmail.com wrote:

Andrea,

I resolved it.


Perfect,



 The and operator is named using the first letter uppercase.

 So  And is recognized, meanwhile AND was not recognized.
 I guest perhaps there is some bugs, but not really sure.


Nope that's the way it is defined in filter.xsd schema
(so maybe a bit uncommon as SQL itself is not case sensitive,
 but surely not a bug)


 Many thx,


Your're wecome,

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

[mapserver-users] TinyOWS 12.10rc1

[Olivier Courtin]

Hi all,

TinyOWS 12.10rc1 is yet available:
http://www.tinyows.org/release/mapserver-tinyows-12.10rc1.tar.bz2

Thanks in advance in advance to test,
and report any bug or regression on this list

12.10 NEWS:
 - Generate PK value using PostgresSQL DEFAULT value if present (Serge
Dikiy)
 - XSD max length and enumeration constraint handling (Serge Dikiy  Alan
Boudreault)
 - include_items and exclude_items config handling. To choose exactly which
columns to retrieve (Serge Dikiy)
 - Add pkey configuration in layer config. Usefull for instance when
retrieving data from a VIEW. (Serge Dikiy)
 - Buffer copy performance improve (Serge Dikiy)
 - Rewrite/fix max features handling (Olivier Courtin)
 - Several bugfixes as usual (special thanks to Andreas Peri, Serge Dikiy
and Jukka Rahkonen for detailled reports)


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

Re: [mapserver-users] TinyOWS 12.10rc1

[Even Rouault]

Le lundi 15 octobre 2012 00:21:19, Olivier Courtin a écrit :
 Hi all,
 
 TinyOWS 12.10rc1 is yet available:
 http://www.tinyows.org/release/mapserver-tinyows-12.10rc1.tar.bz2
 
 Thanks in advance in advance to test,
 and report any bug or regression on this list
 
 12.10 NEWS:
  - Generate PK value using PostgresSQL DEFAULT value if present (Serge
 Dikiy)
  - XSD max length and enumeration constraint handling (Serge Dikiy  Alan
 Boudreault)
  - include_items and exclude_items config handling. To choose exactly which
 columns to retrieve (Serge Dikiy)
  - Add pkey configuration in layer config. Usefull for instance when
 retrieving data from a VIEW. (Serge Dikiy)
  - Buffer copy performance improve (Serge Dikiy)
  - Rewrite/fix max features handling (Olivier Courtin)
  - Several bugfixes as usual (special thanks to Andreas Peri, Serge Dikiy
 and Jukka Rahkonen for detailled reports)

Compiling with clang raises 2 interesting warnings, the 2nd one being clearly 
a bug :

src/mapfile/mapfile.l:412:18: warning: implicit conversion from enumeration 
type 
'enum map_lmd_state' to different enumeration type 'enum map_md_state' [-
Wconversion]
map_md_state = MAP_LMD_TOWS_GEOBBOX;
 ~ ^~~~

src/ows/ows_geobbox.c:62:23: warning: argument to 'sizeof' in 'memcpy' call is 
the same pointer type 'ows_geobbox *' (aka 'struct Ows_geobbox *') as the 
destination; expected
  'ows_geobbox' (aka 'struct Ows_geobbox') or an explicit length [-
Wsizeof-pointer-memaccess]
  return memcpy(c, g, sizeof(g));
~ ^

-- should be memcpy(c, g, sizeof(*g));

Best regards,

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

Re: [mapserver-users] TinyOWS 12.10rc1

[Olivier Courtin]

On Mon, Oct 15, 2012 at 12:44 AM, Even Rouault even.roua...@mines-paris.org
 wrote:

Compiling with clang raises 2 interesting warnings, the 2nd one being
 clearly
 a bug :

 src/mapfile/mapfile.l:412:18: warning: implicit conversion from
 enumeration type
 'enum map_lmd_state' to different enumeration type 'enum map_md_state' [-
 Wconversion]
 map_md_state = MAP_LMD_TOWS_GEOBBOX;
  ~ ^~~~

 src/ows/ows_geobbox.c:62:23: warning: argument to 'sizeof' in 'memcpy'
 call is
 the same pointer type 'ows_geobbox *' (aka 'struct Ows_geobbox *') as the
 destination; expected
   'ows_geobbox' (aka 'struct Ows_geobbox') or an explicit length [-
 Wsizeof-pointer-memaccess]
   return memcpy(c, g, sizeof(g));
 ~ ^

 -- should be memcpy(c, g, sizeof(*g));



Thanks Even for these report !
fixed and commited

Did'nt yet play with clang, could change soon...

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

[mapserver-users] TinyOWS and the logical operators

[Andrea Peri]

Hi,
reading the getcapabilities, I see the TinyOWS has not any LogicalOperator
capability like AND , OR, etc..
Is this correct for wfs 1.1.0 or is a lack of feature ?

Thx,

-- 
-
Andrea Peri
. . . . . . . . .
qwerty àèìòù
-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] [TinyOWS] Problem with attribute names with dots

[Olivier Courtin]

Jukka,

But i need to check against CITE,
 that the fix don't introduce new regression,
 before commiting.


CITE Checked and so commited, (#17).

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

[mapserver-users] [TinyOWS] Problem with attribute names with dots

[Rahkonen Jukka]

Hi,

I made a test layer with dots in feature type name and in an attribute name. 
The following request leads to an error.

POST http://188.64.1.61/cgi-bin/tinyows HTTP/1.1
Content-Type: text/xml
User-Agent: Jakarta Commons-HttpClient/3.0-beta1
Host: 188.64.1.61
Connection: Keep-Alive
Content-Length: 404

wfs:GetFeature xmlns:ogc=http://www.opengis.net/ogc; 
xmlns:gml=http://www.opengis.net/gml; xmlns:wfs=http://www.opengis.net/wfs; 
service=WFS version=1.0.0 maxFeatures=1000 outputFormat=GML2wfs:Query 
xmlns:tows=http://www.tinyows.org/; 
typeName=tows:dot.testogc:PropertyNametows:nom.dept/ogc:PropertyNameogc:PropertyNametows:the_geom/ogc:PropertyName/wfs:Query/wfs:GetFeature

I am not totally sure but probably this request is valid and it should work.  I 
am using a little bit old TinyOWS version from April 2012 so the problem is 
perhaps solved already.

There is some related discussion on the GDAL-dev list
http://article.gmane.org/gmane.comp.gis.gdal.devel/32744

-Jukka Rahkonen-
___
mapserver-users mailing list
mapserver-users@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users

Re: [mapserver-users] [TinyOWS] Problem with attribute names with dots

[Olivier Courtin]

On Mon, Oct 8, 2012 at 11:14 PM, Rahkonen Jukka
jukka.rahko...@mmmtike.fiwrote:

Hi Jukka,

I made a test layer with dots in feature type name and in an attribute
 name. The following request leads to an error. [...]



 I am not totally sure but probably this request is valid and it should
 work.  I am using a little bit old TinyOWS version from April 2012 so the
 problem is perhaps solved already.


Thanks for the detailled report,
i can reproduce it with trunk version,
for attribute name containing a dot,
and using PropertyName query.
(all others use cases are fine)

I've created a ticket, including a patch:
https://github.com/mapserver/tinyows/issues/17

But i need to check against CITE,
that the fix don't introduce new regression,
before commiting.

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

Re: [mapserver-users] [TinyOWS] Broken config using a MAPFILE?

[Richard Turner]

Hi Oliver,

Thanks for your help with this. I've been busy with other stuff, hence
the delay.

I've tweaked my map file a little and enabled TinyOWS logging. Still no
good.

I couldn't see what you changed in the request that would make it work
when you tried; it doesn't look significantly different from the one
OpenLayers is generating for me, except that the namespace is different.
This shouldn't matter though, should it?

Cheers,
R

Map file:

MAP
NAME postcodes
STATUS ON
EXTENT -20037508.34, -20037508.34, 20037508.34, 20037508.34
UNITS M

WEB
METADATA
tinyows_schema_dir /usr/local/share/tinyows/schema/
tinyows_onlineresource
http://richardt.gis.mediatel.co.uk/wfs;
tinyows_log /var/log/tinyows.log
tinyows_log_level 15
wfs_title Postcode Data
wfs_enable_request *
wfs_namespace_uri http://richardt.gis.mediatel.co.uk;
wfs_namespace_prefix mtl
END
END

PROJECTION
init=epsg:3857
END

LAYER
NAME areas
METADATA
wfs_name areas
wfs_title Postcode Areas
gml_featureid ogc_fid
gml_include_items all
wfs_enable_request *
tinyows_table postcode_area_boundaries
tinyows_retrievable 1
tinyows_writable 1
wfs_srs EPSG:3857
END
TYPE POLYGON
STATUS DEFAULT
CONNECTIONTYPE postgis
CONNECTION host=localhost dbname=osm user=osm password=osm
DATA wkb_geometry FROM postcode_area_boundaries
DUMP TRUE
END

LAYER
NAME sectors
METADATA
wfs_name sectors
wfs_title Postcode Sectors
gml_featureid ogc_fid
gml_include_items all
wfs_enable_request *
tinyows_table postcode_sector_boundaries
tinyows_retrievable 1
tinyows_writable 1
wfs_srs EPSG:3857
END
TYPE POLYGON
STATUS DEFAULT
CONNECTIONTYPE postgis
CONNECTION host=localhost dbname=osm user=osm password=osm
DATA wkb_geometry FROM postcode_sector_boundaries
DUMP TRUE
END
END

TinyOWS log:

[Wed Sep 26 13:23:27 2012] [EVENT] == TINYOWS STARTUP ==
[Wed Sep 26 13:23:27 2012] [SQL] SELECT substr(postgis_full_version(),
10, 5)
[Wed Sep 26 13:23:28 2012] [EVENT] == Connection PostGIS ==
[Wed Sep 26 13:23:28 2012] [SQL] SELECT DISTINCT f_table_schema,
f_table_name FROM geometry_columns
[Wed Sep 26 13:23:28 2012] [SQL] SELECT DISTINCT f_table_schema,
f_table_name FROM geography_columns
[Wed Sep 26 13:23:28 2012] [SQL] SELECT srid, f_geometry_column FROM
geometry_columns WHERE f_table_schema='public' AND
f_table_name='postcode_area_boundaries'
[Wed Sep 26 13:23:28 2012] [SQL] SELECT * FROM spatial_ref_sys WHERE
srid=3857 AND proj4text like '%%units=m%%'
[Wed Sep 26 13:23:28 2012] [SQL] SELECT a.attname AS field, t.typname AS
type FROM pg_class c, pg_attribute a, pg_type t, pg_namespace n WHERE
n.nspname = 'public' AND c.relname = 'postcode_area_boundaries' AND
c.relnamespace = n.oid AND a.attrelid = c.oid AND a.atttypid = t.oid AND
a.attname IN ('all',  '');
[Wed Sep 26 13:23:28 2012] [SQL] SELECT a.attname AS field FROM pg_class
c, pg_attribute a, pg_type t, pg_namespace n WHERE n.nspname = 'public'
AND c.relname = 'postcode_area_boundaries' AND c.relnamespace = n.oid
AND a.attnum  0 AND a.attrelid = c.oid AND a.atttypid = t.oid AND
a.attnotnull = 't' AND a.atthasdef='f'
[Wed Sep 26 13:23:28 2012] [SQL] SELECT c.column_name FROM
information_schema.constraint_column_usage c, pg_namespace n WHERE
n.nspname = 'public' AND c.table_name = 'postcode_area_boundaries' AND
c.constraint_name = (SELECT c.conname FROM pg_class r, pg_constraint c,
pg_namespace n WHERE r.oid = c.conrelid AND relname =
'postcode_area_boundaries' AND r.relnamespace = n.oid AND n.nspname =
'public' AND c.contype = 'p')
[Wed Sep 26 13:23:28 2012] [SQL] SELECT a.attnum FROM pg_class c,
pg_attribute a, pg_type t, pg_namespace n WHERE a.attrelid = c.oid AND
a.atttypid = t.oid AND n.nspname='public' AND
c.relname='postcode_area_boundaries' AND a.attname='ogc_fid'
[Wed Sep 26 13:23:28 2012] [SQL] SELECT
pg_get_serial_sequence('public.postcode_area_boundaries', 'ogc_fid');
[Wed Sep 26 13:23:28 2012] [SQL] SELECT column_default FROM
information_schema.columns WHERE table_schema = 'public' AND table_name
= 'postcode_area_boundaries' AND column_name = 'ogc_fid' AND
table_catalog = current_database();
[Wed Sep 26 13:23:28 2012] [SQL] SELECT srid, f_geometry_column FROM
geometry_columns WHERE f_table_schema='public' AND
f_table_name='postcode_sector_boundaries'
[Wed Sep 26 13:23:28 2012] [SQL] SELECT * FROM spatial_ref_sys WHERE
srid=900914 AND proj4text like '%%units=m%%'
[Wed Sep 26 13:23:28 2012] [SQL] SELECT a.attname AS field, t.typname AS
type FROM pg_class c, pg_attribute a, pg_type t, pg_namespace n WHERE
n.nspname =