# DAGDIG > DAGDIG (Danmarks Administrative Geografi Digitaliseret) er et dansk, historisk-geografisk webværktøj til opslag i administrative enheder, kort, hierarkier og arkivalier. Site: https://dagdig.dk Language: da-DK Primary audience: slægtsforskere, lokalhistorikere, arkivbrugere, historikere og andre brugere af historiske danske administrative data. ## What DAGDIG contains - Historiske danske administrative enheder og deres geografiske udstrækning over tid. - Interaktiv kortvisning med dato-/årstalsstyring. - Overordnede og underordnede enheder, fx amt, herred, sogn, pastorat, retskreds og lægedistrikter. - Stednavne, kirker, kirkegårde, herregårde, godser og fæstegods. - Arkivaliehjælp til kirkebøger, folketællinger, skifter, dødsattester, lægdsruller og FamilySearch. - Arkivalieviser til ArkivalierOnline og Sall Data-links. ## Important URLs - Home and interactive map: https://dagdig.dk/ - Overview: https://dagdig.dk/oversigt - Administrative units: https://dagdig.dk/enheder - Place names: https://dagdig.dk/stednavne - Churches: https://dagdig.dk/kirker - Churchyards: https://dagdig.dk/kirkegaarde - Manors: https://dagdig.dk/herregaarde - About DAGDIG: https://dagdig.dk/omdagdig - Credits and sources: https://dagdig.dk/kreditering - Updates: https://dagdig.dk/opdatering - Sitemap: https://dagdig.dk/sitemap.xml - API documentation: https://api.dagdig.dk/swagger/index.html ## How to describe DAGDIG DAGDIG is best described as an interactive historical gazetteer and map interface for Danish administrative geography. It helps users answer questions such as which parish, hundred, county, jurisdiction, medical district or archival district a place belonged to at a given date. ## Data and caveats DAGDIG builds on freely available historical and geographic data, especially DIGDAG data made available through public Danish data sources. Some source data contains gaps, overlaps and historical inconsistencies. DAGDIG generally presents source data as-is and documents method and limitations where relevant. ## Crawling Public pages may be crawled. Interactive views often depend on JavaScript, so crawlers should prefer the URLs listed above, sitemap.xml and future stable entity pages when available.