{"id":389,"date":"2019-06-16T20:16:38","date_gmt":"2019-06-16T20:16:38","guid":{"rendered":"https:\/\/blog.get-map.org\/?p=389"},"modified":"2019-06-16T20:54:20","modified_gmt":"2019-06-16T20:54:20","slug":"umap-geojson-export-api-support","status":"publish","type":"post","link":"https:\/\/blog.get-map.org\/index.php\/2019\/06\/16\/umap-geojson-export-api-support\/","title":{"rendered":"Umap GeoJson Export API Support"},"content":{"rendered":"

<\/a> <\/p>\n

Upload of Umap<\/a> files exported manually via the Umap web interface has been supported by my MapOSMatic instance<\/a> for quite a while, and the MapOSMatic API<\/a> has also supported submitting a Umap file via an URL instead of uploading an actual file.<\/p>\n

There’s also a (so far inofficial) export URL for exporting an Umap for exporting a map directly, without manual browser interaction.<\/p>\n

See this Umap Github issue<\/a> for a more detailed description.<\/p>\n

The basic idea is that for a map with Id 123 the stable web access URL would be:<\/p>\n\n\n
\n
https:\/\/umap.openstreetmap.fr\/m\/123<\/pre>\n<\/td>\n<\/tr>\n<\/table>\n
and the inofficial map export URL<\/p>\n\n\n
\n
https:\/\/umap.openstreetmap.de\/en\/map\/123\/geojson<\/pre>\n<\/td>\n<\/tr>\n<\/table>\n
Unfortunately the export file retrieved this URL is not yet complete though, as unlike the manualy exported file unsing “Export all data” in the web interface, it only contain the maps meta data, and references to the actual data layers, but not the actual layer data itself.<\/p>\n
So when processing a file exported this way, we first need to check the “urls” dictionary from the map properties for the datalayer_view<\/code> URL path, and combine this with the protocol and host part from the maps own export URL.<\/p>\n
For the original Umap instance the datalayer_view<\/code> looks like this:<\/p>\n\n\n
\n
\/en\/datalayer\/{pk}\/<\/pre>\n<\/td>\n<\/tr>\n<\/table>\n
and so the full URL template becomes<\/p>\n\n\n
\n
https:\/\/umap.openstreetmap.de\/en\/datalayer\/{pk}\/<\/pre>\n<\/td>\n<\/tr>\n<\/table>\n
The {pk}<\/code> placeholder needs to be replaced with the Ids from the datalayers<\/code> list entries, which e.g. look like this:<\/p>\n\n\n
\n
{\n\"name\": \"Layer 1\",\n\"id\": 123456,\n\"displayOnLoad\": true\n}<\/pre>\n<\/td>\n<\/tr>\n<\/table>\n
So we need to download actual layers data from URLs like<\/p>\n\n\n
\n
https:\/\/umap.openstreetmap.de\/en\/datalayer\/123456\/<\/pre>\n<\/td>\n<\/tr>\n<\/table>\n
which returns JSON data we need to append to the layers<\/code> list to form a complete export file.<\/p>\n
Once we fetched and merged all data layers we can then process the resulting JSON document the same way as the JSON exported from the web frontend.<\/p>\n
This should allow a more direct integration between Umap and MapOSMatic servers, to automate the process of creating printed representations of maps generated with Umap.<\/p>\n
An API request to render an umap with Id 123 would then simply look like this:<\/p>\n\n\n
\n
{\n    \"umap_url\": \"https:\/\/umap.openstreetmap.fr\/en\/map\/123\/geojson\/\"\n}<\/pre>\n<\/td>\n<\/tr>\n<\/table>\n
In actual PHP code for example launching a map rendering job for this umap would look like this:<\/p>\n\n\n
\n
<?php\nrequire_once 'HTTP\/Request2.php';\n\nheader(\"Content-type: text\/plain\");\n\ndefine('BASE_URL', 'https:\/\/print.get-map.org\/apis\/v1\/');\n\n$data = ['umap_url' => 'https:\/\/umap.openstreetmap.fr\/en\/map\/123\/geojson\/'];\n\n$request = new HTTP_Request2(BASE_URL . \"jobs\");\n\n$request->setMethod(HTTP_Request2::METHOD_POST)\n        ->addPostParameter('job', json_encode($data));\n\n$response = $request->send();\n$status   = $response->getStatus();\n\nif ($status < 200 || $status > 299) {\n    print_r($response->getBody());\n    exit;\n}\n\n$reply = json_decode($response->getBody());\necho \"Result URL: \".$reply->interactive.\"\\n\";<\/pre>\n<\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"
Upload of Umap files exported manually via the Umap web interface has been supported by my MapOSMatic instance for quite a while, and the MapOSMatic API has also supported submitting a Umap file via an URL instead of uploading an actual file. There’s also a (so far inofficial) export URL for exporting an Umap for … Continue reading “Umap GeoJson Export API Support”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[2],"tags":[],"_links":{"self":[{"href":"https:\/\/blog.get-map.org\/index.php\/wp-json\/wp\/v2\/posts\/389"}],"collection":[{"href":"https:\/\/blog.get-map.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.get-map.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.get-map.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.get-map.org\/index.php\/wp-json\/wp\/v2\/comments?post=389"}],"version-history":[{"count":2,"href":"https:\/\/blog.get-map.org\/index.php\/wp-json\/wp\/v2\/posts\/389\/revisions"}],"predecessor-version":[{"id":391,"href":"https:\/\/blog.get-map.org\/index.php\/wp-json\/wp\/v2\/posts\/389\/revisions\/391"}],"wp:attachment":[{"href":"https:\/\/blog.get-map.org\/index.php\/wp-json\/wp\/v2\/media?parent=389"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.get-map.org\/index.php\/wp-json\/wp\/v2\/categories?post=389"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.get-map.org\/index.php\/wp-json\/wp\/v2\/tags?post=389"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}