Geoprocessing: Difference between revisions

From Wildsong
Jump to navigationJump to search
Brian Wilson (talk | contribs)
Brian Wilson (talk | contribs)
mNo edit summary
Line 8: Line 8:
I built a Docker Compose [[GeoServer]] for testing, and I have added plugins to it for WPS.  
I built a Docker Compose [[GeoServer]] for testing, and I have added plugins to it for WPS.  
I also have been developing an OpenLayers Javascript client.
I also have been developing an OpenLayers Javascript client.
== Following the Boundless tutorial ==
I am marching through [https://suite.opengeo.org/docs/latest/processing/contour/setup.html Contour Map setup] from Boundless Geospatial.
I don't have their Composer app so I used the
[https://suite.opengeo.org/docs/latest/dataadmin/importer/index.html#dataadmin-importer GeoServer Layer Importer]
to import irving.tif
In the Boundless docs it's difficult to tell what is a tool they provide (such as Composer) and what things are actually part of GeoServer.


== Use case: Select adjacent taxlots ==
== Use case: Select adjacent taxlots ==

Revision as of 19:09, 4 April 2019

In this case "Geoprocessing" means doing specialized spatial processing on data as required in my web maps work.

This page used to cover geoprocessing in the ESRI world, and it was mostly about tips for Python+ArcPy. I rewrote it to document WPS (Web Processing Service) first in GeoServer and later on in ArcGIS Enterprise.

I have separate pages on building and using GDAL and PostGIS, see the GIS category.

I built a Docker Compose GeoServer for testing, and I have added plugins to it for WPS. I also have been developing an OpenLayers Javascript client.

Following the Boundless tutorial

I am marching through Contour Map setup from Boundless Geospatial. I don't have their Composer app so I used the GeoServer Layer Importer to import irving.tif

In the Boundless docs it's difficult to tell what is a tool they provide (such as Composer) and what things are actually part of GeoServer.


Use case: Select adjacent taxlots

  1. User selects a taxlot in the Javscript client.
  2. This causes adjacent taxlots to be selected.
  3. Information about all selected taxlots appears in a table.

GeoMoose used to use use PHP Mapscript. They are client side only now so not really doing geoprocessing anymore.

The GeoServer demo "WPS Request Builder" feature is useless (probably more learning curve problems!). I seek other examples.