After importing geodata from the GIS to MongoDB and creating a spatial index (part 1), the exciting (spatial) adventure starts. With „normal“ (relational) databases and their spatial extensions (Oracle spatial, PostgreSQL/PostGIS, SQLite/Spatialite,…) a lot of spatial queries and geoprocessing are possible. So let’s try to find out which adresses have to be evacuated 250m around some „event“…
MongoDB (3.2) is a kind of database-hipster at the moment – with improving support for spatial data. So it was time for me to discover some of it’s features concerning spatial data. As a GIS-user my first intention was to get some bigger simple (point) geodata into MongoDB. Part 1 covers this topic, part 2 will cover some spatial operations within MongoDB. I also want to do some performance checks between PostgreSQL/PostGIS and MongoDB related to geodata.
Yesterday my Fedora 23 did not show up the 3G-Modem (USB) in Network Manager Mobile Connections (using KDE; Kerndel 4.3). Having a look with dmesg reported a registered modem…
Today I started to test the developer-version of the upcoming QGIS 2.14 and found a nice feature integrated out-of-the-box. In previous QGIS-versions tracing along existing geometries required 3rd-party plug-ins (e.g. http://isticktoit.net/?p=131) – now it looks like integrated with QGIS 🙂
Update 7.3.2016: Lutra Consulting describes all details in it’s Blog
Many different organisations have to deal with the management of guideposts – especially in alpine regions. Sometimes all the data about the guideposts is managed in databases and GIS-Systems, often no digital data management is in use. In the first case mostly internally developed databases/applications are used and there is no open technical “standard” for storing “guidepost-data” and EXCHANGING it. In some regions – like in Tyrol – governmental standards for the guideposts (“the hardware”) are available (how guideposts have to look like – e.g. size, classification of difficulty, …). Based on the idea that around the world guideposts have some elements (direction, name of target,…) in common, we started to work on a modern technical standard…
Die Verwendung eines Internet-Zugangs über Drei (drei.at / Hutchinson 3G) mit den DNS von Drei kann zu manch Überraschung führen. Gesperrte Webseiten und bei fehlerhaften URLs wird einem gleich durch eine von Drei zwischengeschaltete Seite „geholfen“ – inkl. Google Analytics. Netzneutralität ? User-Enscheidung ?
Just yesterday I wandet to use my mobile (Nexus 5 / Android 5.1 CM 12.1) for connecting to the internet on my notebook (Fedora 22 / KDE Plasma 5). Connecting it via USB and activating USB-Tethering did something in network manager – but did not connect 🙁
Sometimes (eg. doing it for a bulk of geodatasets) converting and transforming geodatasets from their Source-CRS to another with command line tools like ogr2ogr (http://www.gdal.org/ ) can be helpful.
With ogr2ogr it’s also an easy task to use NTv2-based transformations like for Austria the AT_GIS_GRID.