[OSM-dev] Using NULL values in mapnik / postgres DB
Joerg Ostertag (OSM Munich/Germany)
openstreetmap at ostertag.name
Tue Feb 20 23:30:02 GMT 2007
On Wednesday 21 February 2007 00:11, Martin Spott wrote:
> In article <200702202351.49991.openstreetmap at ostertag.name> you wrote:
> > If we're changing the database layout; do you see a chance of changing
> > the scheme with one column per feature to something like one column with
> > a feature_id. Then for example
> > highway=motorway would be feature_id=1
> > highway=primary would be feature_id=2
> > ...
> > waterway=river would be feature_id=21
>
> Tooo many different layers probably make the whole thing a bit
> confusing - there are at least 14 different road types in OSM - but
> creating different layers for each logical entity (highway, waterway)
> could make a really good deal.
I don't want to create different layers. I only want to have one layer, and
for this layer, one column which defines what this line in the database entry
should show.
As what I saw you always had only one column (out of 5) filled with a string.
This string can have something around 5 different meanings. I wanted to
change this to having only one column left and use a integer instead of
different strings.
--
Jörg (Germany, Munich)
http://www.ostertag.name/
TeamSpeak2: ts2.ostertag.name, user: tweety, Channel: "GPS Drive"
irc://irc.oftc.net/#osm
Tel.: +49 89 420950304
More information about the dev
mailing list