2018 was a very productive year for OpenStreetMap in Ireland.
Around 70k nodes added, 60k ways added, and 160k polygons added.
Finally a company was formed to facilitate becoming a fully fledged local chapter.
What does that look like day to day:
GIS and Mapping Blog from Ireland
2018 was a very productive year for OpenStreetMap in Ireland.
Around 70k nodes added, 60k ways added, and 160k polygons added.
Finally a company was formed to facilitate becoming a fully fledged local chapter.
What does that look like day to day:
I ran into a process where I wanted to create copies of rasters in PostgreSQL. While seemingly a simple process this took me a bit of work to figure out.
For my workflow I had three rasters, which all have the same size, and I want to load them into the same PostGIS table with three raster geometry columns. I don’t think this will work for different sized rasters since the rid’s will not match.
Three rasters:
raster1
raster2
raster3
Which I want to copy into:
merged_raster
First to create the merged raster table:
CREATE TABLE merged_raster ( rid serial NOT NULL, raster1 raster, raster2 raster, raster3 raster );
Then to add the rid’s. These are the id’s of the tiles that the raster was split into when loading. If your tile size is large enough then you may only have one.
INSERT INTO merged_raster(rid) (SELECT rid FROM raster1);
Then copying the actual data is straighforward (this assumes the raster column in the raster1 datasets is called rast):
UPDATE merged_raster m SET raster1 = r.rast FROM raster1 r WHERE r.rid = m.rid; UPDATE merged_raster m SET raster2 = r.rast FROM raster2 r WHERE r.rid = m.rid; UPDATE merged_raster m SET raster3 = r.rast FROM raster3 r WHERE r.rid = m.rid;
Now I still have an issue that QGIS will not load these layers. It will always load the initial raster column no matter what is chosen.