Emilie Laffray wrote: > That would mean that Mapnik needs to be checking a secondary field to > determine what to display. If the renderer doesn't do that, you will end > up with a map that is poorer in the end. In your case, that would mean
That's not really so different as highway + access, or highway=service+service=*. And while it is nice to keep render complexity in mind when you design a tagging scheme, don't let it make a case against the more logical tagging. > increasing the size of the table produced by osm2pgsql by one extra > column. Overall, you are increasing complexity with little or no benefits. Which means 1 bit per row, for the most part. > I am not sure it makes sense in the end since were are getting exactly > the same of information if you are using the tag directly in landuse. Extensibility. Plain and simple. If you come up with a new category for agricultural=*, and while you wait for the renderers to pick that up, you're still getting a plain landuse=agricultural rendered. Not a white spot on the map. Data users that don't need the complexity of different agricultural uses only need to process the main landuse=agricultural tag, and not try to group various agricultural landuse types into 1. -- Lennard _______________________________________________ talk mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk
