4

History files are still available from Geofabrik! You need to use their "OpenStreetMap internal server" download area, and log on with your OSM account. This was changed last year to accomodate for GDPR requirements. Link: https://osm-internal.download.geofabrik.de/


3

If you want to use QuickMapServices 1) go to Web -> QuickMapServices -> Settings 2) add/edit/remove -> create service from existing (3.a) or create new service (3.b) 3.a) If you chose create service from existing choose the one you want to edit. 3.b) If you create a new service choose TMS as Type 4) in TMS tab edit the url and insert your api key


3

As stated on an example at thunderforest.com use https://tile.thunderforest.com/cycle/{z}/{x}/{y}.png?apikey=<insert-your-apikey-here>. You can add XYZ-Tiles to QGIS via Browser -> XYZ-Tiles -> New Connection


3

Even though this blog is in Spanish, it will let you know about OSM data and how to make a request from Python. You'll find the code there too. import requests import json overpass_url = "http://overpass-api.de/api/interpreter" overpass_query = """ [out:json]; area["name"="Málaga"][admin_level=8]; (node["amenity"="restaurant"](area); node["amenity"="bar"](...


3

By default, osm2pgsql transforms the raw geographic coordinates (EPSG:4326 - WGS84) to EPSG:3857; to populate the geom column in your gps_coordinates table accordingly (i.e. defined as GEOMETRY(POINT, 3857)), run UPDATE gps_coordinates SET geom = ST_Transform(ST_SetSRID(ST_MakePoint(longitude, latitude), 4326), 3857) ; After that, running SELECT a.id, ...


2

The documentation for ST_Distance states: For geometry type returns the minimum 2D Cartesian distance between two geometries in projected units (spatial ref units). Therefore, it is not returning meters like you assumed, it is returning degrees. Depending on your latitude, one degree is equal to around 111 KM! https://en.wikipedia.org/wiki/...


2

As demonstrated by @ArturoMendes , Using Overpass API it is possible to do queries in a nice way , there is much information on the OSM Wiki, OSM Wiki Link. On the OSM Wiki there is a list of public global Overpass API providers you can query against. This list is reproduced below and is not complete https://lz4.overpass-api.de/api/interpreter https://z....


2

Pelias does not currently support directly returning polygon or polyline data. However, you can use a workaround until it does. A search or autocomplete request to pelias that returns Munich will have a feature in the response that looks something like this (with some data removed for conciseness): "properties": { "id": "101748479", "gid": "...


1

It should find the osmconf.ini local to the installation. You can override it using -o CONFIG_FILE=<yourpath>/osmconf.ini on the command line. (you might need OSM_CONFIG_FILE instead of CONFIG_FILE) You are probably also going to want to adjust your osmconf.ini to specify what is imported and what ignored. Also, how to handle closed ways,etc. Yes ...


1

You are trying to match two different map projections. The default OpenStreetMap tiles use the EPSG:3857 coordinate reference system, AKA Web Mercator Projection. It looks like this: On the other hand, the Natural Earth files use the EPSG:4326 coordianate reference system, AKA equirectangular projection. It looks like this: The issue of map projections, ...


1

You should go to the Query panel and write your own query such as: [out:xml][timeout:25]; ( nwr["name"~"Costco(.*)"] ["shop"] ({{bbox}}); ); out body; >; out skel qt; or in XML format, so QuickOSM will be able to highlight it correctly: <osm-script output="xml" timeout="25"> <union> <query type="nwr"> <...


1

Found the issue. Specifically this code: # GetNextFeature handles interleaved reading correctly for ily in range (0,nly): layer = ds.GetLayerByIndex(ily) I initially replaced it with: # GetNextFeature handles interleaved reading correctly for ily in (0,1,2,4,3): layer = ds.GetLayerByIndex(ily) ...which appeared to work. It ensures Layer 4 ("...


1

Don't change the CRS of the Open Street Map layer. Return the CRS of the layer to the original CRS that it came with (which was probably EPSG:3857). If you don't remember for sure, remove the layer and re-add it the same way you added it the first time. Change the CRS of the Project. Click on the project CRS in the bottom-right corner of the window. ...


1

Unless you're in the desert or somewhere like that, then there are likely to be nodes nearby. You should never expect to find a node at exactly the same point as you are searching for. (if this isn't 'obvious', I recommend you read up on floating point comparisons) So you need to find the closest node(s) to each of your query locations. I used a KD-Tree ...


Only top voted, non community-wiki answers of a minimum length are eligible