Skip to main content
Geographic Information Systems

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • "Image representation" is not quite accurate. As Miguel states, GetFeatureInfo can return GML which is vector data and server may also support for example KML format for GetMaps which is all vectors. However, WMS is not planned to be transactional and it just can't be used for editing features. Commented Sep 30, 2014 at 10:11
  • And is a JDBC connection to POSTGIS possible and a viable alternative to update attributes by feature ID? Commented Sep 30, 2014 at 10:21
  • @user30184 you're right indeed i've corrected my answer. By the way, this lack of terminology accuracy you point out seems to reach the OGC WMS specification itself (see opengeospatial.org/standards/wms), which unfortunately also refers to "images". Anyway, the matter here is about protocols and the fact WMS cannot be used to edit features. Commented Sep 30, 2014 at 10:27
  • 5
    @MiguelÂngeloBelém Your are not obliged to go through WFS-T. I would say it's the way to go if you are going to edit the geometries. But in your case, as you only need to edit attributes, yes you can develop a system to interact with your database using JDBC, without passing by WFS-T. Commented Sep 30, 2014 at 10:33
  • 1
    I see your point. By using WMS GetFeatureInfo, you should inherit all attributes + the featureId. If you didn't specify to use the postgis table primary key as FeatureId in geoserver, the field that you use as primary key should anyway be available as attribute (implicit feature identifier). You can sure use it to identify the feature to edit through WFS-T. Commented Sep 30, 2014 at 13:37