Hello Michael,

        Further investigation using shapefiles that I believe were derived from the Hot Export system, I inspected these in my own GIS, Manifold GIS:
  • "planet_OSM line, point, roads" shapefiles contain key/value attributes but do not project at all; projection information from the PRJ file copied below.  It appears to be a custom projection that I would have to hardwire into Manifold.
  • "latest" shapefiles projected and displayed correctly but appeared to have just basic civil map information, nothing OSM related it would appear
        So, sorry to report that nothing useful has come from all this OSM data download thrashing.  I'm willing to press on if someone has a guaranteed recipe, but my energy and enthusiasm for further experimentation is pretty well finished.  OSM data dissemination is significantly inhibited by a plethora of file types and poorly connected tools, in my opinion.  After two or three very late nights I have 0 bytes of useful information.

        This is unfortunate because there is huge potential in extending the utility of all this laboriously generated information.  I was especially looking forward to reviewing and possibly improving upon the helipad information.  As Pierre has noted, with so many displaced survivors living in very difficult circumstances, and with the monsoon approaching, reliable helicopter access will probably become even more important.  In bad weather in the mountains, roaming around in a helicopter to find a landing spot is not fun and one's first inclination is to stay in the tent.  However, if helipad destinations are accurately mapped, pilots will be more willing to try a trip in dodgy weather if they have a good idea of where they are going.

                 Thanks again for your help and patience, Cheers . . . . . . . . Spring Harrison

PRJ file: 

PROJCS["WGS 84 / Pseudo-Mercator",GEOGCS["Popular Visualisation CRS",DATUM["Popular_Visualisation_Datum",SPHEROID["Popular Visualisation Sphere",6378137,0,AUTHORITY["EPSG","7059"]],TOWGS84[0,0,0,0,0,0,0],AUTHORITY["EPSG","6055"]],PRIMEM["Greenwich",0,AUTHORITY["EPSG","8901"]],UNIT["degree",0.01745329251994328,AUTHORITY["EPSG","9122"]],AUTHORITY["EPSG","4055"]],UNIT["metre",1,AUTHORITY["EPSG","9001"]],PROJECTION["Mercator_1SP"],PARAMETER["central_meridian",0],PARAMETER["scale_factor",1],PARAMETER["false_easting",0],PARAMETER["false_northing",0],AUTHORITY["EPSG","3785"],AXIS["X",EAST],AXIS["Y",NORTH]]




At 10-05-2015 10:33 Sunday, Michael wrote:
Hi Spring,

Am 10.05.2015 um 10:47 schrieb Springfield Harrison:
Further bad news, trying to download OSM through JOSM yielded the following message:

/The OSM server 'api.openstreetmap.org' reported a bad request.

The area you tried to download is too big or your request was too large.
Either request a smaller area or use an export file provided by the OSM community.

I am afraid but this is standard behavior in any editor. Basically this is not the way to go if you actually want to download OSM data for consumption.

/Does this process usually work? Is it not possible to simply get a shapefile
of this information and avoid all the multiple file type rigmarole?

If you actually want a shapefile for all of Nepal I would recommend using one of the available downloads listed on https://wiki.openstreetmap.org/wiki/2015_Nepal_earthquake#Exporting_OpenStreetMap_data

But if you are only interested in some feature you should have a look at Overpass Turbo. This allows to download filtered results. http://overpass-turbo.eu/s/9hb is a sample query for aeroway=helipad in the area showed in the map. But unfortunately this will not yield shapefiles. Also the query language requires to go through some learning curve if you want to create a bit more complex queries.

Cheers,
        Michael (user Ohr)
_______________________________________________
HOT mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/hot

Reply via email to