P3D v5 scenProc can not read this Value

[Clutch Cargo]

OSM has what I would call a strange Value under the Category they call 'other_tags'. The Value is "power"=>"tower" (with the quotation marks). The step I use is:

PointToPolygon|other_tags="power"=>"tower"|15;15|hdg|String;Type|power_tower

Which produces no polys. To ensure the step is working I have used |other_tags="*"| which does work but catches everything which is not usable. I have tried:

|other_tags=""power"=>"tower""|
|other_tags="*tower"|
|other_tags="power=>tower"|

Any suggestions short of having to go in and edit OSM's values?

thx

 

[arno]

Hi,

I think the => characters are fooling the filter logic, as these are used for calculations as well. Did you try to put quotes around the entire string?

Also, I think this is related with your specific OSM data. From which format are you reading? The attribute should just be "power"="tower":

Tag:power=tower - OpenStreetMap Wiki

wiki.openstreetmap.org

 

[Clutch Cargo]

If you look above, I tried putting quotes around the entire value. The file was d/l from Geofabrik 'california-latest.osm.bz2'. I unzipped and it became an .osm file. Right now I am testing to see if I can d/l via QGIS and their osm plugin. Maybe the tags will be different. Maybe the Category and the Values are being combined?

 

[arno]

Did you modify the osmconf.ini file that comes with scenProc in the gdal-data folder? If you don't have the power tag listed there to be read you can get this behaviour as well.

 

[Clutch Cargo]

Did you modify the osmconf.ini file that comes with scenProc in the gdal-data folder? If you don't have the power tag listed there to be read you can get this behaviour as well.

No, I have never even heard of that? (Gee, learn something new just about every time I open scenProc). So you are suggesting edit that ini and add a 'power=' or literally add "power"=>"tower" line to it? Taking a look at it now... very interesting. So If I understand you can add fields to this but wouldn't I need to add the Value? "power"=>"tower" or are you saying add power as the Field and tower as the Value?

 

[arno]

That ini file specifies which attributes of the OSM data OGR puts in the vector data when reading. But the ini file that comes with scenProc should already include the power tag. For the point features you should see something like this:

[points]
# common attributes
osm_id=yes
osm_version=no
osm_timestamp=no
osm_uid=no
osm_user=no
osm_changeset=no

# keys to report as OGR fields
attributes=name,barrier,highway,ref,address,is_in,place,man_made,power,amenity,religion,natural,generator:source
# keys that, alone, are not significant enough to report a node as a OGR point
unsignificant=created_by,converted_by,source,time,ele,attribution
# keys that should NOT be reported in the "other_tags" field
ignore=created_by,converted_by,source,time,ele,note,openGeoDB:,fixme,FIXME
# uncomment to avoid creation of "other_tags" field
other_tags=no
# uncomment to create "all_tags" field. "all_tags" and "other_tags" are exclusive
#all_tags=yes

But that also disables the other_tags, while you are still seeing that. I am wondering if your OGR might be using a different configuration file. At startup of scenProc it should ensure that the gdal_data folder of scenProc is used. Do you maybe have a GDAL_DATA environment variable in Windows as well?

 

[Clutch Cargo]

A further update. I discovered using QGIS I can query power and tower and easily get the results I need. I can also mask out the area so I am not running a huge osm file. I can then save it as a shp file and use that inside scenProc. I might try it this way... just need to code a python script to automate the QGIS steps.

I know I might get a "RTFM" on this nextr question but can scenProc do the above in the script? I think so but it would have to run through the entire OSM file or by using a mask that would cut down processing time?\\

Just saw your response.... gee isn't it awfully late there?

 

[arno]

A further update. I discovered using QGIS I can query power and tower and easily get the results I need. I can also mask out the area so I am not running a huge osm file. I can then save it as a shp file and use that inside scenProc. I might try it this way... just need to code a python script to automate the QGIS steps.

I know I might get a "RTFM" on this nextr question but can scenProc do the above in the script? I think so but it would have to run through the entire OSM file or by using a mask that would cut down processing time?\\

I don't think so, when you import the OSM file into scenProc to make a SHP, it would use that same osmconf.ini file to determine which attributes to read. So don't see how you can do that in scenProc.

Just saw your response.... gee isn't it awfully late there?

Not really, it's 22:35 here now. But it is about bed time indeed, so this will be my last reply for today