https://github.com/opensmock/pharoows
OGC Web Services (OWS) support for Pharo
https://github.com/opensmock/pharoows
cartography map open-smock pharo pharo-smalltalk qgis qgis-server smalltalk smock tile-server tilemap tiles tileserver wms wms-service
Last synced: 12 months ago
JSON representation
OGC Web Services (OWS) support for Pharo
- Host: GitHub
- URL: https://github.com/opensmock/pharoows
- Owner: OpenSmock
- License: mit
- Created: 2022-11-07T17:09:32.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2025-06-10T19:03:48.000Z (12 months ago)
- Last Synced: 2025-06-10T20:29:22.097Z (12 months ago)
- Topics: cartography, map, open-smock, pharo, pharo-smalltalk, qgis, qgis-server, smalltalk, smock, tile-server, tilemap, tiles, tileserver, wms, wms-service
- Language: Smalltalk
- Homepage:
- Size: 1010 KB
- Stars: 1
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# PharoOWS
[](https://pharo.org/download)
[](https://pharo.org/download)
[](https://pharo.org/download)
[](https://github.com/OpenSmock/PharoOWS/actions/workflows/test.yml)
A variety of protocols and standards exist to enable communication with map
servers and access geographic data in both raster and vector formats. Defined
by the [Open Geospatial Consortium (OGC)](https://www.ogc.org/), these
protocols are fondamental to ensure interoperability between clients and
servers.
PharoOWS supports the official OGC protocols along with some widely adopted de
facto standards, offering tools for querying map servers and parsing the
returned data.
## :wrench: Install
PharoOWS can be installed using [Metacello](https://github.com/Metacello/metacello):
```smalltalk
Metacello new
baseline: 'PharoOWS';
repository: 'github://OpenSmock/PharoOWS:main';
load.
```
Dependencies are:
- [XMLParser](https://github.com/pharo-contributions/XML-XMLParser)
## :globe_with_meridians: Geospatial services: OGC Standards and de facto Protocols
Standard communication protocols with map servers can be divided into two main
categories:
1. Official protocols defined by the Open Geospatial Consortium (OGC)
2. De facto protocols that have emerged due to widespread use (such as XYZ)
### 1. Formal OGC protocols
**Traditional OGC Services**
These services are based on SOAP or HTTP protocols with specific requests often
constructed as URLs with parameters. They primarily exchange XML or other
specialized formats (XML for requests/responses, images for maps). These
standards have been widely used for many years to ensure geospatial
interoperability.
```console
http://mapserver?SERVICE=WMS&REQUEST=GetMap&Layers=layer0,layer1
```
**Modern RESTful Services**
These adopt a RESTful architecture based on modern web principles. They use
simple HTTP methods (`GET`, `POST`, etc.) and return responses in JSON. This
approach makes integration with applications easier due to its simplicity and
compatibility with current web technologies. OGC API - Features is a key
example of this new generation, providing standardized REST APIs for accessing
vector data.
```console
http://mapserver/collections/layer0/items.json
```
### 2. De facto standards
Although not officially standardized by organizations like the OGC, protocols
such as TMS (Tile Map Service) and the XYZ URL scheme are widely adopted in web
mapping. Their simplicity and compatibility with modern web technologies have
made them essential de facto standards for serving map tiles.
## :package: PharoOWS : overview of supported protocols and standards
PharoOWS is split into several packages according to the supported protocols
and standards:
| Package | Type | Supported Protocols | Status |
|-------------------|-----------------------|-----------------------------------|------------------|
| PharoOWS-TMS | De facto standard | TMS | In development |
| PharoOWS-Service | Official OGC | WMS, WMTS | In development |
| PharoOWS-API | Official OGC (modern) | OGC API - Processes | Upcoming |
:loudspeaker: PharoOWS is still in development, so new protocols and standards
will be added over time.
## :computer: Examples
### WMS
```smalltalk
| wms operations getmap layers size map |
"Create a WMS client targeting the IGN WMS server"
wms := PharoOWSServiceWMS new.
wms url: 'https://data.geopf.fr/wms-r'.
"Introspect the server capabilities"
operations := wms operations.
# 'operations' is a XMLOrderedList(
# a PharoOWSServiceWMSOperation
# a PharoOWSServiceWMSOperation
# a PharoOWSServiceWMSOperation
# )
"Listing available image formats for maps"
getmap := operations detect: [ :request | request name = 'GetMap' ].
getmap formats.
# 'formats' is an OrderedCollection(
# image/jpeg
# image/png
# image/tiff
# image/geotiff
# image/x-bil;bits=32
# )
"Listing available layers"
layers := wms layers.
# 'layers' is a XMLOrderedList(
# a PharoOWSServiceWMSLayer(ADMINEXPRESS-COG-CARTO.LATEST)
# a PharoOWSServiceWMSLayer(ADMINEXPRESS-COG.2017)
# [...]
# )
"Download a raster map with two layers for a bounding box defined by EPSG:3857 coordinates"
map := wms
map: { 'EL.GridCoverage'. 'FORETS.PUBLIQUES' }
bbox: (-546079 @ 6126282 corner: -398839 @ 6212047)
size: 800 @ 600
epsg: '3857'
format: 'image/png'.
# 'map' is a Bitmap
```
## :page_facing_up: License
This project is licensed under the MIT License - see the [LICENSE](LICENSE)
file for details.