On Mon, Jan 10, 2011 at 12:24 AM, Richard Fairhurst <[email protected]> wrote: > Definitely use a single <feature> element with both <area/> and <point/> > subelements, rather than using two separate <feature>s. > > If the tags are divergent, then the syntax to use is: > > <point> > <tag k="amenity" v="frog_bothering_ground"/> > </point> > <area> > <tag k="amenity" v="frog_bothering_ground"/> > <tag k="frogs" v="yes"/> > </area> > > This isn't supported yet (see line 929 of map_features.xml) but it should > be. :)
What if the inputs are divergent? Does something like this make sense: <inputSet id="roadPhysical"> <input type="checkbox" name="Area" description="Is this loop an open area of road?" node="no" way="no"/> ... </inputSet> (Or should it be done on the feature itself?) >> 3) Should we take into account the likelihood of any given POI being >> mapped as a node (ie, supermarket is far more likely than vending >> machine), or take a blanket approach that all POIs can be areas? > > Don't assume that all POIs can be areas. <point/><area/> is > self-explanatory: overloading <point/> to mean "oh, it can be an area as > well" would be counter-intuitive. Ah, I didn't mean that. I meant "in reworking the map_features.xml, should I treat add <area/> to all poi's, or should I be more selective?" Steve _______________________________________________ Potlatch-dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/potlatch-dev
