Geoprocessing: Difference between revisions
Brian Wilson (talk | contribs) mNo edit summary |
Brian Wilson (talk | contribs) mNo edit summary |
||
Line 1: | Line 1: | ||
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 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 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. | |||
== Use case: Select adjacent taxlots == | == Use case: Select adjacent taxlots == | ||
# User selects a taxlot in the Javscript client. | # User selects a taxlot in the Javscript client. | ||
# This causes adjacent taxlots to be selected. | # This causes adjacent taxlots to be selected. | ||
# Information about all selected taxlots appears in a table. | |||
I | I am comparing my work with [[Gemooose]] to see how their Geoprocessing works for all the various buffering options but this is just the initial test case. | ||
First things first, I need a way to test the GeoServer. | |||
I find the demo requests feature to be modestly useless (probably more learning curve problems!) but I can get a chunk of XML out of it, | |||
then send that in a request to the server via Python script and catch what comes back. | |||
[[Category:GIS]] | [[Category:GIS]] |
Revision as of 19:24, 27 March 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.
Use case: Select adjacent taxlots
- User selects a taxlot in the Javscript client.
- This causes adjacent taxlots to be selected.
- Information about all selected taxlots appears in a table.
I am comparing my work with Gemooose to see how their Geoprocessing works for all the various buffering options but this is just the initial test case.
First things first, I need a way to test the GeoServer.
I find the demo requests feature to be modestly useless (probably more learning curve problems!) but I can get a chunk of XML out of it, then send that in a request to the server via Python script and catch what comes back.