Hi, I have been fighting, again, with non-interoperatible WFS servers/clients. Problem is most often in servers sending such GML that clients, from some reason, do not want to parse. Situation is not much better now than five years ago when I made my first trials.
Now I have noticed that at least two WFS servers, Geoserver and TinyOWS, can send out geojson. For me it looks much more simple than GML. Developers, do you think it could be possible to make OpenJUMP in the first phase to import geojson data? Second phase would be to make an option to the WFS plugin to ask server to send geojson and parse that instead of GML. The format definitions are here: http://geojson.org/geojson-spec.html Data in geojson format are available from my server. points: http://188.64.1.61/cgi-bin/tinyows?service=wfs&version=1.0.0&request=getfeature&typename=tows:osm_points&maxfeatures=100&outputformat=application/json lines: http://188.64.1.61/cgi-bin/tinyows?service=wfs&version=1.0.0&request=getfeature&typename=tows:osm_lines&maxfeatures=100&outputformat=application/json polygons: http://188.64.1.61/cgi-bin/tinyows?service=wfs&version=1.0.0&request=getfeature&typename=tows:osm_polygon&maxfeatures=100&outputformat=application/json TinyOWS seems to send coordinates without projection info but that should not be a problem for OpenJUMP, and perhaps it will have CRS objects later. -Jukka Rahkonen- ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
