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=wfs&request=GetCapabilities&version=1.1.0
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfs&request=DescribeFeatureType&version=1.1.0&typename=water:pipeline_segment
http://127.0.0.1:8000/redir/cgi-bin/tinyows.exe?service=wfs&request=GetFeature&version=1.1.0&typename=water:pipeline_segment&maxFeatures=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="[email protected]" />
<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-bin>tinyows --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=wfs&request=DescribeFeatureType&version=1.1.0&typename=water:pipeline_segment";
})
});
Someone an idea?
_______________________________________________
mapserver-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapserver-users
_______________________________________________
mapserver-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapserver-users
