2013/1/23 Mikel Maron <[email protected]> > Interesting thought to add time ranges to tags, re "All changes to > attributes as described above must each have a time associated with them.". > And I like Christian's suggestion of modifying existing tags, in a similar > way to name localization. That makes sense in the OSM universe. > It can also apply to uses of entity, like a building that starts off as a > historic home, becomes a museum or an office. > > And to link an entity that changes geometry over time, well, relations > could be adapted for this. > Confidence factor is important to record, and that could sit fine in tags > as well. > > The trick for all this is how does it can translated into schemas for > rendering, geocoding, etc. What's an efficient way to represent these > things in postgres, in order for mapnik to make tiles? > > >
I think postgres just needs 2 additional fields: start_date and end_date that should be extracted from the tag key suffix when importing osm data. Then, Mapnik stylesheets need to include date range in its query using these 2 fields. -- Christian Quest - OpenStreetMap France - http://openstreetmap.fr/u/cquest<http://openstreetmap.fr/u/christian-quest>
_______________________________________________ Historic mailing list [email protected] http://lists.openstreetmap.org/listinfo/historic
