FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W4386677009> ?p ?o ?g. }

• W4386677009 abstract "Most Geographic Information Systems started as a substitute for loose paper maps. These paper maps did not have a built-in time dimension and could only represent history indirectly as a sequence of physically separate images. This was in fact imitated by these first generation systems. The time dimension could only be represented by means of separate files. A minority of Geographic Information Systems however, started their life as a substitute for ordered lists and tables with a link to paper maps. In these lists, the inclusion of a time com-ponent in the form of a data field was quite usual. This method too was copied by the systems that replaced these paper tables. The current trend in the development of Geographic Information Systems is towards the inte-gration of the classical map-oriented concepts with the table-oriented concepts. This often leads to the explicit embedding of the time component in the GIS environment. The Subcommission Geo-Information Models of the Netherlands Geodetic Commission has organized a workshop to discuss the theory and practice of time and history in GIS on 18 May 2000. This publication contains 6 articles prepared for the workshop. The first paper, written by Donna Peuquet, gives a bird’s-eye view of the current state of the art in spatio-temporal database technology and methodology. She is a well-known expert in the field of spatio-temporal information systems and the author of many articles in this field. The second article is written by Monica Wachowicz. She describes what you can do with a GIS once it contains a historical dimension and how you can detect changes in geographic phenomena. Furthermore, her article suggests how geographic visualisation and knowledge discovery techniques can be integrated in a spatio-temporal database. How to record the time dimension in a database is one thing, how to show this dimension to users is another one. In his contribution, Menno-Jan Kraak first tells about the techniques, which were used in the age of paper maps and the limitations these methods had. He goes on to explain what kind of cartographic techniques have been developed since the mass introduc-tion of the computer. Finally he describes the powerful animation methods which currently exist and can be used on CD-ROM and Internet applications. Peter van Oosterom describes how the time dimension is represented in the information sys-tems of the Cadastre and how this is used to publish updates. The Cadastre has a very long tradition in incorporating the time component, which has always been an inherent component of the cadastral registration. In former times this was translated in very precise procedures about how to update the paper maps and registers. Today it is translated in spatio-temporal database design. The article of Luc Heres tells about the time component in the National Road Database, origi-nally designed for traffic accident registration. This is one of the systems with ''table'' roots and with quite a long tradition in handling the time dimension. He elucidates first the core objects in the conceptual model and how time is added. Next, how this model is translated in a logical design and finally how this is technically implemented. Geologists and geophysicians also have a respectable tradition in handling the time dimension in the data they collect. This is illustrated in the last paper, which is written by Ipo Ritsema. He outlines how time is handled in geological and geophysical databases maintained by TNO. By means of some practical cases he illustrates which problems can be encountered and how these can be solved." @default.
• W4386677009 created "2023-09-13" @default.
• W4386677009 date "2000-01-01" @default.
• W4386677009 modified "2023-09-29" @default.
• W4386677009 title "Time in GIS: Issues in spatio-temporal modelling" @default.
• W4386677009 doi "https://doi.org/10.54419/v5m55p" @default.
• W4386677009 hasPublicationYear "2000" @default.
• W4386677009 type Work @default.
• W4386677009 citedByCount "0" @default.
• W4386677009 crossrefType "book" @default.
• W4386677009 hasConcept C119599485 @default.
• W4386677009 hasConcept C121332964 @default.
• W4386677009 hasConcept C124101348 @default.
• W4386677009 hasConcept C127413603 @default.
• W4386677009 hasConcept C168167062 @default.
• W4386677009 hasConcept C180198813 @default.
• W4386677009 hasConcept C202444582 @default.
• W4386677009 hasConcept C205649164 @default.
• W4386677009 hasConcept C23123220 @default.
• W4386677009 hasConcept C2522767166 @default.
• W4386677009 hasConcept C33676613 @default.
• W4386677009 hasConcept C33923547 @default.
• W4386677009 hasConcept C41008148 @default.
• W4386677009 hasConcept C41856607 @default.
• W4386677009 hasConcept C45235069 @default.
• W4386677009 hasConcept C56321713 @default.
• W4386677009 hasConcept C58640448 @default.
• W4386677009 hasConcept C58754882 @default.
• W4386677009 hasConcept C9652623 @default.
• W4386677009 hasConcept C97355855 @default.
• W4386677009 hasConceptScore W4386677009C119599485 @default.
• W4386677009 hasConceptScore W4386677009C121332964 @default.
• W4386677009 hasConceptScore W4386677009C124101348 @default.
• W4386677009 hasConceptScore W4386677009C127413603 @default.
• W4386677009 hasConceptScore W4386677009C168167062 @default.
• W4386677009 hasConceptScore W4386677009C180198813 @default.
• W4386677009 hasConceptScore W4386677009C202444582 @default.
• W4386677009 hasConceptScore W4386677009C205649164 @default.
• W4386677009 hasConceptScore W4386677009C23123220 @default.
• W4386677009 hasConceptScore W4386677009C2522767166 @default.
• W4386677009 hasConceptScore W4386677009C33676613 @default.
• W4386677009 hasConceptScore W4386677009C33923547 @default.
• W4386677009 hasConceptScore W4386677009C41008148 @default.
• W4386677009 hasConceptScore W4386677009C41856607 @default.
• W4386677009 hasConceptScore W4386677009C45235069 @default.
• W4386677009 hasConceptScore W4386677009C56321713 @default.
• W4386677009 hasConceptScore W4386677009C58640448 @default.
• W4386677009 hasConceptScore W4386677009C58754882 @default.
• W4386677009 hasConceptScore W4386677009C9652623 @default.
• W4386677009 hasConceptScore W4386677009C97355855 @default.
• W4386677009 hasLocation W43866770091 @default.
• W4386677009 hasOpenAccess W4386677009 @default.
• W4386677009 hasPrimaryLocation W43866770091 @default.
• W4386677009 hasRelatedWork W1658219227 @default.
• W4386677009 hasRelatedWork W2056437374 @default.
• W4386677009 hasRelatedWork W2145979795 @default.
• W4386677009 hasRelatedWork W2349070320 @default.
• W4386677009 hasRelatedWork W2353291850 @default.
• W4386677009 hasRelatedWork W2357740668 @default.
• W4386677009 hasRelatedWork W2360727749 @default.
• W4386677009 hasRelatedWork W4320506559 @default.
• W4386677009 hasRelatedWork W592383815 @default.
• W4386677009 hasRelatedWork W801894267 @default.
• W4386677009 isParatext "false" @default.
• W4386677009 isRetracted "false" @default.
• W4386677009 workType "book" @default.