[GRASS-dev] [GRASS GIS] #3409: d.what.vect JSON issue with OSM data

[GRASS GIS]

#3409: d.what.vect JSON issue with OSM data
----------------------+---------------------------------
  Reporter:  neteler  |      Owner:  grass-dev@…
      Type:  defect   |     Status:  new
  Priority:  normal   |  Milestone:  7.2.2
 Component:  Display  |    Version:  svn-releasebranch72
Resolution:           |   Keywords:  d.what.vect, v.what
       CPU:  x86-64   |   Platform:  Linux
----------------------+---------------------------------

Comment (by mmetz):

 Replying to [ticket:3409 neteler]:
 > I have imported successfully an OSM pbf file, can display it but not
 query:
 >
 [...]
 >
 > Here an example for v.what output not parsable by d.what.vect (note:
 this is not exactly the same position as in the error msg screenshot):
 > {{{
 > v.what roads coordinates=13.3926375553,52.5548668929 -a
 > East: 13:23:33.495199E
 > North: 52:33:17.520814N
 > ------------------------------------------------------------------
 > Map: roads
 > Mapset: osm
 > Type: Point
 > Id: 34721
 > Layer: 1
 > Category: 34721
 >
 > Driver: sqlite
 > Database: /home/mneteler/grassdata/latlong_wgs84/osm/sqlite/sqlite.db
 > Table: roads_1
 > Key column: cat
 > cat : 34721
 > osm_id : 631984925
 > name :
 > barrier :
 > highway :
 > ref :
 > address :
 > is_in :
 > place :
 > man_made :
 > other_tags : "addr:city"=>"Berlin","addr:street"=>"Bornholmer
 Straße","addr:suburb"=>"Gesundbrunnen","addr:country"=>"DE","addr:postcode"=>"13359","addr:housenumber"=>"50"
 > }}}
 >
 > Some more "escaping" might be needed here?

 Alternatively you can use a osmconf.ini file
 [http://gdal.org/drv_osm.html] to 1) avoid the creation of the other_tags
 field, 2) select some of the OSM keys summarized in the other_tags field.

--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3409#comment:1>
GRASS GIS <https://grass.osgeo.org>