Slashgeo

REST and GIS

posted by Satri on Thursday April 05, @01:03PM        Permalink  Trackback URI  Slashdotthis  Diggthis  Del.icio.us
from the reastful-and-gisless dept.

The It is what it is blog has a nice summary of what is REST and its implication for GIS. From the entry: "State Transfer in the public standards-based GIS world (where REST really starts to achieve critical mass) is still all about the read-only flow of data from publishers to browsers. [...] Just becaues those resources have lat/longs doesn't mean that GIS should suddenly be the center of the universe. Why do I have to use KML for resources that probably have extremely rich alternate representations already?" This is the first of a series of upcoming entries.

Trackbacks:

• NONE
• http://slashgeo.org
• NONE
• NONE
• NONE
• NONE
• NONE
• http://slashgeo.org
• NONE
• NONE

Related Stories

Industry: REST Interest at the OGC [+]

Remember the previous entry on REST and GIS? Could RESTful webmapping become OGC standards? The cfis and import cartography blogs discuss new REST interest at the Open Geospatial Consortium. Here's the second post and the third. From the third post: "Everything that's wrong the the WxS Suite (that's a fancy acronym for Web Map Server, Web Feature Server, Web Context Server, etc.) boils down to one thing - they are based on the fundamentaly flawed concept of service endpoints. A service endpoint is a program sitting on the network that defines its own API."

Geospatial Web Services and REST 1 comment [+]

Geoblogs have been regularly covering REST technology and geospatial applications lately, see the related stories below. Directions Mag offers an informative article named Emerging Technology: Geospatial Web Services and REST which reduces the confusion with REST, SOAP, GET and POST. From the article's introduction: "However, when considering the evolution of geospatial Web services, it turns out that explaining REST and clarifying the discussion suggests the need for a proposal of how to apply REST to geospatial Web services. Such a proposal might help the open source and open standards communities establish better techniques to make geospatial Web services more open and accessible." Meanwhile, you have import cartography explaining how KML could be published in a RESTful manner, and the same blog also suggests serious (?) corrections to the DM article.

• Followup entry

  (Score:2)

  by Satri (3) on Tuesday April 10, @01:14PM (#1382)
  ( http://alexandreleroux.blogspot.com/ | Last Journal: Friday March 17, @05:07PM )

  A followup entry [palladiumconsulting.com] from the same blog.
• Another followup entry...

  (Score:2)

  by Satri (3) on Tuesday April 10, @04:37PM (#1385)
  ( http://alexandreleroux.blogspot.com/ | Last Journal: Friday March 17, @05:07PM )

  Right here [palladiumconsulting.com].
• Another entry on what is REST

  (Score:2)

  by Satri (3) on Wednesday May 02, @05:01PM (#1405)
  ( http://alexandreleroux.blogspot.com/ | Last Journal: Friday March 17, @05:07PM )

  This time [blogspot.com], from another blog.
• FeatureServer REST implementation

  (Score:2)

  by Satri (3) on Saturday May 05, @10:25AM (#1413)
  ( http://alexandreleroux.blogspot.com/ | Last Journal: Friday March 17, @05:07PM )

  http://featureserver.org/ [featureserver.org]
  FeatureServer is an implementation of a RESTful Geographic Feature Service. (What is REST?) Using standard HTTP methods, you can fetch a representation of a feature or a collection of features, add new data to the service, or delete data from the service. Use it as an aggregator -- post your GeoRSS feeds to it, and then browse them using WFS. Use it as a translator: use the OGR DataSource to load a shapefile and open it in Google Earth. Use it in any way you like.
  (via HEO [highearthorbit.com])