Hello Christoph,

I do have some code which gives GeoJSON from a standard OSM PostGIS database as 
a web service, if you're interested.


This code is available as part of the Freemap repository:


https://github.com.nickw1/Freemap/


Not sure if you understand PHP but the files you're interested in are in the 
"ws" directory, tsvr.php (which takes in tile x,y,z parameters) and bsvr.php 
(which takes in a bounding box of arbitrary projection, plus input and output 
SRIDs (projection identifiers).


Let me know if you're interested in this and would like to install it on your 
server.


Nick


Nick Whitelegg
Senior Lecturer in Computing (Internet)  | School of Media Arts and Technology
Southampton Solent University  | RM424 | East Park Terrace | Southampton SO14 
0YN
T: 023 8201 3075 | E: 
nick.whitel...@solent.ac.uk<mailto:nick.whitel...@solent.ac.uk> | W: 
solent.ac.uk<http://www.solent.ac.uk/>

Disclaimer<http://www.solent.ac.uk/disclaimer/disclaimer.aspx>
________________________________
From: Christoph Lingg <christ...@lingg.eu>
Sent: 15 May 2017 18:11:59
To: jukka.rahko...@latuviitta.fi
Cc: dev@openstreetmap.org
Subject: Re: [OSM-dev] Planet file with preprocessed lines/polygons


>> A huge file containing all osm items as geojson would be my dreamcase.
>> Does this exist?
>
> It could rather be a nightmare. GeoJSON can't be indexed spatially nor by 
> attributes so if you would like to work only on small area of interest or to 
> find just certain features you would still need to parse the whole huge 
> GeoJOSN file.

I agree that GeoJSON is not the format you would like to query your data. I 
wanted to refer to the way the data is available for download. To put it into 
other words: instead of raw xml (like now) a precomputed GeoJSON. Packing all 
OSM objects into a feature collection would be again a night mare as you need a 
huge amount of RAM. But having one GeoJSON object per line could work much 
better and would allow the creation of an OSM object stream easily. Without 
downloading the entire dataset on disk first.

Christoph
_______________________________________________
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev
_______________________________________________
dev mailing list
dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

Reply via email to