Add Support for Export OSM XML Format from Scripts

It amazes me how fast you are able to add features and fix bugs!

The software seems to make some decisions about what tags to generate. For example, a <tag k="maxspeed" v="20"/> seems to be associated with one of my other attributes (MP_TYPE = 0x03)? I set the first 7 attributes in my GM workspace and the software creates an additional <tag k="maxspeed" v="20"/>, effectively overwriting my setting of <tag k="maxspeed" v="15 mph"/>.

<tag k="name" v="Club"/>
<tag k="routeparam" v="1,0,0,0,0,0,0,0,0,0,0,0"/>
<tag k="mp_type" v="0x03"/>
<tag k="mp_bit_level" v="18"/>
<tag k="kml_html_desc_text" v="Snowmobile Club Trail"/>
<tag k="highway" v="tertiary"/>
<tag k="maxspeed" v="15 mph"/>
<tag k="maxspeed" v="20"/>

The GM software also seems to create a <tag k="waterway" v="river"/> associated with what a assume is MP_TYPE = 0x1F which in my case is effecting the rendering of <tag k="highway" v="secondary"/> that I desire.

To answer your question, is there a way to provide a list of feature attributes that should NOT get tags created? In the first example above, I would chose to disable the creation of tags for the following attributes:

routeparam
mp_type
mp_bit_level
kml_html_desc_text
<tag k="maxspeed" v="20"/> However I would want my setting of "maxspeed" to result in a tag.

So there would need to be a way to suppress some of the auto-generated keys such as waterway and maxspeed.

Sorry for several posts... In my case, if I were able to provide a list of attributes FOR tag creation that would be a short list and achieve what I need.

Hi - will the customized control of attributes be something you can release soon or should I start to look for a work-around?

Thank you Mike,

That's very helpful for eliminating clutter. However the issue that is causing me to perform some kind of manual post-editing is the auto-generated attributes, in particular maxspeed is over-riding my setting of maxspeed. If I specify ATTR_TO_DELETE="MAXSPEED", it deletes mine and still creates the auto-generated one. The auto-generation of <tag k="waterway" v="river"/> seems to have gone away.

In the example below, the blue <tag k="maxspeed" v="15 mph"/> is my setting and the red <tag k="maxspeed" v="20"/> is auto-generated.

<nd ref='-6076154'/>
<nd ref='-6076155'/>
<nd ref='-6076156'/>
<nd ref='-6076157'/>
<nd ref='-5955919'/>
<tag k="name" v="Club"/>
<tag k="routeparam" v="1,0,0,0,0,0,0,0,0,0,0,0"/>
<tag k="mp_type" v="0x03"/>
<tag k="mp_bit_level" v="18"/>
<tag k="kml_html_desc_text" v="Snowmobile Club Trail"/>
<tag k="highway" v="tertiary"/>
<tag k="maxspeed" v="15 mph"/>
<tag k="maxspeed" v="20"/>
</way>