Ko'proq

Plitalarni yangilash uchun brauzer keshidan foydalanmaslik uchun ochiq o'yinchilarni majbur qiling


Fayllarni TileStache serveridan serverning keshlash parametridan foydalanmasdan ko'rsatish uchun OpenLayers.Layer.XYZ dan foydalanaman. Shu bilan birga, butun sahifa Ctrl-F5 bilan yangilanmaguncha, plitkalar keshda (ehtimol brauzer keshida) qoladi.

Agar men XYZ qatlamini qayta chizishni xohlasam, u ishlamayapti, chunki xaritada brauzer keshidan foydalaniladi. Ushbu keshni ishlatmaslik uchun xaritani majburlashning bir usuli bormi? Serverdan yangi plitalar so'rab qatlamni yangilashi mumkin.

var map = new OpenLayers.Map ('map', {projection: new OpenLayers.Projection ("EPSG: 3857"), numZoomLevels: 20}); var tiledLayer = yangi OpenLayers.Layer.XYZ ('TMS', "{{tmsURL}} 1.0 / layer / {{shapefile.id}} / $ {z} / $ {x} / $ {y} .png">

Yoqub Kaniya o'z sharhida keshdagi plitkalar urlidan farq qilishi uchun urlga sana / vaqt qo'shilishi kerakligi to'g'risida to'g'ri fikr bildirdi. Buning uchun OpenLayers.Layer.XYZ kichik sinfiga o'tishingiz kerak:

OpenLayers.Layer.CustomXYZ = OpenLayers.Class (OpenLayers.Layer.XYZ, {getURL: function () {var url = OpenLayers.Layer.XYZ.prototype.getURL.apply (bu, argumentlar); urlni qaytarish + '? Vaqt = '+ yangi sana (). getTime ();}}); var tiledLayer = yangi OpenLayers.Layer.CustomXYZ ('TMS', "{{tmsURL}} 1.0 / layer / {{shapefile.id}} / $ {z} / $ {x} / $ {y} .png">Bu javobni yaxshilangjavob berdi 25-avgust '14 da 14:58 daRadar ostidaRadar ostida3,3041 ta oltin nishon26 ta kumush nishonlar53 ta bronza nishonlari 

Mijoz tomonidan CSS / JS keshini qayta yuklashni majburlash

Mijoz brauzerini JS / CSS fayllarini qayta tiklashga qanday majburlashim mumkin?

Mavjud .CSS fayllarini qo'shganimda, yangilanishlar faqat foydalanuvchi sahifani yangilasa qo'llaniladi. (Boshqacha qilib aytganda, shunchaki sahifaga o'tish ishlamaydi).

Men keshlarni tozalashga harakat qildim (JS / CSS-ni o'z ichiga olgan) va mening CSS / JS fayllarimni qayta tiklashga harakat qildim. Afsuski, men ushbu xatti-harakatni hali ham Chrome, Safari va amp Firefox-da ko'rmoqdaman. (Internet Explorer o'zini juda yaxshi tutdi).

Men ushbu savolga SO-da qaradim:

Magento manba o'zgarishlarini zaruriy qo'shmasdan / uchinchi tomon dasturlarini o'rnatmasdan buni amalga oshirishga qodirmi?


Baliq ovlash koordinatalarimni o'g'irlay olasizmi ?! (Izohlardagi ma'lumot)

Ha, osonlikcha. Ular JSON faylidan yuklangan. Siz barcha so'rovlarni ko'rish va ularni tanlash uchun shunchaki brauzer & # x27s tarmoq inspektoridan foydalanishingiz mumkin.

Xavfsiz buni amalga oshirish uchun har bir joyni tasodifan noto'g'ri joylashtirishingiz yoki past piksellar sonining raster ko'rinishini ishlatishingiz kerak bo'ladi (shuningdek, juda xavfsiz bo'lishni istasangiz, tasodifiy ofset bilan).

Ballarni ko'rsatish uchun raster plitka qatlamlaridan foydalanishni o'rganib chiqdim, lekin bulutdagi xususiyatlarni tahrir qila olmadim va har bir tahrirdan keyin butun kafel keshini qayta tiklashim kerak edi.

Tezda raster plitkalarni dinamik ravishda yaratish usuli bormi? Kirish orqali tahrirlashim mumkin bo'lgan, ammo foydalanuvchilarga faqat plyonkasi qiyin bo'lgan raster vakolatxonasiga kirish huquqini beradigan shaxsiy xaritani bulutda joylashtira olamanmi?

Hey, siz ularni qanday qilib qazib olganingiz va QGIS-ga yuklaganingiz haqida to'g'ri yo'nalishda ko'rsatishga qarshi emasmisiz?

Bu mening fikrimcha echim.

Va u erda sizda bor. Rahmat!

Men ESRI Online-ni baliq ovlash joylarini dengiz xaritasida aniq joylashishini ko'rsatmasdan aks ettirish usuli sifatida sinab ko'raman. Men ko'milgan xaritani yaratdim, bu mening ko'shaklarni asal teshiklarim xavfsizligini ta'minlaydi deb o'ylayman, lekin ishonchim komil emas.

Men ushbu xaritani inkognito oynasida sinab ko'rdim va shu paytgacha aniq koordinatalarni chiqarish usulini topmadim. Ilg'or GIS mahoratiga ega bo'lgan kishi ushbu test xaritasida mening joylarimni o'g'irlash uchun pichoq urishni xohlaydimi?

Mumkin bo'lgan ikkita yo'l:

Qandaydir tarzda joylashtirilgan xaritani bosib, uni ArcGIS onlayn xaritasi tomoshabinida oching.

Har bir nuqtada koordinatalari DMS formatida matn atributi sifatida saqlanadi. Men ushbu maydonlarni ochilgan ma'lumot qutilariga yashirdim, lekin agar foydalanuvchi atributlar jadvalini ochishga majbur qila olsa, ularda hamma narsa bor.

Asosiy xususiyat qatlamini yuklab olish va uni ish stolining GIS dasturida ochish.


Server keshi hanuzgacha manba fayllaridan foydalanmoqda

ArcGIS Server-da MrSid yoki Grid formatida tasvirlar asosida yaratilgan bir nechta rasm plitalari keshlari bor. Men ba'zi bir HD bo'sh joyni tozalashga harakat qilmoqdaman va ushbu serverdagi rasmlarning nusxasini olib tashlamoqchiman yoki hech bo'lmaganda uni ko'chirmoqchiman. Ammo, kesh yaratilganiga qaramay va men tasvirni namoyish qilish uchun foydalaniladigan narsa, deb o'ylayman, Server keshni yaratish uchun ishlatilgan rasm fayllarini olib tashlashga ruxsat bermaydi. Agar men server xizmatini to'xtatib, fayllarni olib tashlasam, endi mening ilovalarimda rasm paydo bo'lmaydi.

1. Kesh bilan ishlashda nima uchun keshga asl tasvir ma'lumotlari kerak bo'ladi? Buni o'zgartirishning biron bir usuli bormi?

2. Asl tasvirga havola qaerda joylashganki, men uni o'zgartira olaman? Ma'lumotlarni boshqa diskka ko'chirmoqchiman, lekin keshlarni qayta yaratishga hojat yo'q, chunki u ushbu jarayon davomida serverni ishdan chiqaradi.

RobertScheitlin tomonidan __GISP

Config.xml-ga qarab, siz hech qanday qatlam turlaridan foydalanmayapsiz, lekin dinamik, shuning uchun keshlangan qatlamlaringiz umuman ishlatilmaydi. Siz keshni chetlab o'tmoqdasiz, chunki ular turi = "dinamik".

Bu boshqalarga yordam beradigan bo'lsa. Manba ma'lumotlarining hanuzgacha ishlatilishining sababi, sozlamalarda qo'lda emas, balki "avtomatik ravishda yangilash" uchun kesh o'rnatildi. Tasvir ekanligi va o'zgarmagani uchun, men qo'l bilan o'zgartirdim va shu bilan tasvirni ko'chirishga muvaffaq bo'ldim.

RebeccaStrauch_ _GISP tomonidan

Bu eslab qolish uchun yaxshi maslahat.

xuddi men tomon sifatida har doim "qo'llanma" ni tekshirishga moyil bo'laman, chunki u juda toza, chunki mening fikrimcha, agar siz kesh qachon va qayerda (qay darajada) yaratilayotganini nazorat qila olsangiz. 10.2.x dan oldin men buni yanada zarurat deb o'ylar edim, ayniqsa, bizning to'liq hajmimizdagi katta (okean) suv havzasi mavjud, chunki hech qachon batafsil keshlash kerak emas edi (ma'lumotlar manbalari sifat jihatidan emas edi) farq qilmoq). Bu "qo'lda" tekshiruv boshqalarga yordam berishi mumkin bo'lgan yana bir sababdir.

..va yana bitta eslatma. oldingi versiyalarda (qaysi birini eslay olmayman), agar siz yangi xizmatni yaratgan bo'lsangiz va yaratishda keshni o'rnatgan bo'lsangiz ham, "qo'lda" ni tanlagan bo'lsangiz ham, u avtomatik ravishda avtomatik ravishda o'zgartiriladi. Shunday qilib, men xizmatni dinamik ravishda yaratdim. keyin darhol qaytib kirib, keshni o'rnatdi va "qo'lda" keshni yaratdi. Siz qaysi versiyadan foydalanayotganingizni aytmadingiz, shuning uchun siz ushbu muammoga duch kelsangiz, buni eslatib o'tmoqchiman.

Aytgancha, muammo hal qilinganligi sababli, savolingizga javob sifatida belgilashni unutmang.


Keshlangan hisobga olish ma'lumotlarini o'chirish uchun yordamchi dasturni topish qiyin. U sertifikat ma'lumotlarini va foydalanuvchi parollarini saqlaydi.

Buyruqning satrini oching yoki ishga tushirish buyrug'iga quyidagilarni kiriting

Windows 7 buni boshqaruv panelida "Hisobga olish ma'lumotlari menejeri" belgisini yaratish orqali osonlashtiradi.

Buyruqning yordam dasturi ham mavjud:

(nimaga bog'langaningizni ko'rish uchun)

(barcha ulanishlarni o'chirish uchun)

aniq foydalanish to'g'risidagi ma'lumotlar keymgr yoki hisobga olish ma'lumotlari mgr-da ko'rsatilgan ma'lumotlar bilan bir xil emas.

Ma'lumot uchun, men faqat hisobga olish ma'lumotlari (ehtimol buzilgan bo'lishi mumkin, chunki u faqat ikkita, g'alati Unicode belgilar bilan kiritilgan yozuv ostida paydo bo'lgan) faqat rundll32.exe keymgr.dll, KRShowKeyMgr interfeysida paydo bo'ldi va Hisob ma'lumotlari menejerida emas. Windows 7 boshqaruv panelida joylashgan interfeys. Keshlangan ma'lumot uchun ikkala interfeysni tekshirishga arziydi.


Ochiq o'yinchilarni plitkalarni yangilash uchun brauzer keshidan foydalanmaslikka majbur qiling - Geographic Information Systems

MapML (Map Markup Language) tushuntiruvchisi

HTML hamjamiyati guruhi uchun W3C xaritalari muammoli maydonda takrorlanmoqda. Siz Internet-xaritalarni standartlashtirish uchun foydalanish holatlari va talablari bo'yicha doimiy muhokamada va hujjatlarda o'z hissangizni qo'shishingiz mumkin. Shu bilan bir qatorda, agar sizning tashkilotingiz veb-platforma inkubatorlari jamoatchilik guruhining (WICG) a'zosi bo'lsa va siz u erda o'z hissangizni qo'sha olsangiz, lekin boshqa joyda bo'lmasangiz, iltimos, veb-xaritalash bo'yicha WICG forumi orqali o'z hissangizni qo'shib ko'ring. Sizdan xabar olishni istardik.

Veb-xaritalar - bu veb-dizaynning yaxshi rivojlangan domeni bo'lib, veb-xaritalarni yaratish va boshqarish uchun mashhur, etuk ochiq va yopiq manbali JavaScript kutubxonalari mavjud. JavaScript veb-xaritalari ko'pincha ommaga taqdim etiladigan va moliyalashtiriladigan ochiq geografik va statistik ma'lumotlar uchun konteynerlardir. O'rnatilgan JavaScript kutubxonalari va server tomonidagi API standartlariga qaramay, veb-xaritalar juda zarur bo'lgan ilm talablari tufayli o'rganish qiyin bo'lgan murakkab veb-joy bo'lib qolmoqda. Natijada, veb-xaritani ishlab chiquvchilar hamjamiyati mavjud bo'lib, ular veb-platformaga juda oz hissa qo'shadi va veb-sayt alohida va standartlarga asoslangan platforma sifatida mavjudligini kam tushunadi. Xuddi shunday, veb-platforma asosan veb-xaritalar va ularning talablariga befarq ko'rinadi va xaritalarni to'g'ridan-to'g'ri qo'llab-quvvatlamaydi. Boshqacha qilib aytganda, veb-xaritalarning veb-platformada mavjudligi veb-platformani "mavhumlashtiradigan" vositachilarga bog'liq.

Ushbu taklifning maqsadi ikki jamoalar o'rtasidagi tafovutni ikkala tomon uchun ijobiy foyda keltiradigan tarzda bartaraf etishdir. Bir tomondan, veb-xaritalash hamjamiyati vositachilar tomonidan yuklanadi va natijada xaritalar va ommaviy xaritalar ma'lumotlarini keng yaratish va ulardan foydalanish yo'lidagi to'siqlar mavjud. Boshqa tomondan, veb-platforma, ayniqsa, mobil veb-sayt ko'proq yuqori darajadagi xususiyatlarga va kamroq JavaScript-ga muhtoj. HTML-dagi sodda, ammo kengaytiriladigan veb-xaritalar, bu boshqa platforma standartlarini teng ravishda ishlatib, foydalanuvchilar uchun qulaylik va mavjudlikni yaxshilash uchun har ikkala jamoaning birlashishi kerak bo'lgan xususiyatdir.

Bugungi kunda veb-xaritalar xaridor va serverda, ba'zilari standart, ba'zilari ochiq va ba'zilarida xususiy texnologiya to'plamlarining keng doirasi yordamida yaratilgan. Tanlovlarning murakkabligi va veb-xaritalarni yaratish uchun zarur bo'lgan turli xil texnologiyalar, juda o'zgaruvchan foydalanishga va foydalanishga yaroqli xaritalarga olib keladi. Bu o'z navbatida veb-texnologiyalar yordamida amalga oshiriladigan yoki amalga oshirilmaydigan markazlashtirilgan xaritalash xizmatlarini yaratishga olib keldi, ish stoli veb-brauzerlarida yaxshi ishlaydigan xaritalash xizmatlari asosan mobil platformalarni xaritalash dasturlarini yaratish orqali mobil Internetni chetlab o'tmoqda. "veb-platforma qoidalari" (masalan, qurilmaga ruxsat berish) qo'llanilmaydi. Internetda ham, xususan mobil texnologiyalar platformalarida ham ba'zi markazlashtirilgan xaritalash xizmatlari foydalanuvchining joylashuvi va ularning qiziqish (qidirish) joylarini kuzatib borish va ushbu maqsad haqidagi ma'lumotni yuqori maqsadli reklamalarni sotish va qayta sotish uchun foydalanish uchun tuzilgan. .

Shuning uchun echilishi kerak bo'lgan muammo - bu mavjud, foydalanishga yaroqli va maxfiylikni saqlaydigan veb-xaritalarni yaratishning chekka murakkabligini kamaytirish va xarita yaratishda HTML, URL, SVG, CSS va JavaScript kabi veb-platforma standartlaridan to'liq foydalanishni ta'minlash, uslublar, taqdimot va o'zaro ta'sir.

Muammoni hal qilish uchun bizning yondashuvimiz, hozirgi vaqtda JavaScript-ni kutubxonalari tomonidan amalga oshiriladigan veb-xaritani qayta ishlashni belgilash kerak, buning o'rniga HTML dizayn printsiplariga muvofiq - CSS tomonidan qo'llab-quvvatlanadigan elementlar va atributlar sifatida, biz esa JavaScript domenida standart DOM API sifatida qolishi kerak bo'lgan veb-xaritani qayta ishlashni aniqlang. HTML-da xaritalar va qatlamlarning asosiy xatti-harakatlarini yaratish orqali o'zlarining sahifalarida oddiy xaritalarni yaratmoqchi bo'lgan veb-mualliflar buni osonlikcha, asosiy platforma texnologiyalari tomonidan qo'llab-quvvatlanadigan JavaScript-ning kuchi bilan, asosiy xarita va qatlam ishini yaxshilashga imkon beradi.

Shu tarzda veb-xarita mualliflari uchun to'siqlarni kamaytirish orqali biz foydalanishni yaxshilaymiz va veb-xaritalarning mavjudligini standartlashtiramiz. Tegishli ravishda ishlab chiqilgan veb-platforma standartlarini qo'llash masalasida xaritani yaratish orqali biz veb-mualliflar va foydalanuvchilarga taklif qilinadigan xaritalash xizmatlarini ko'paytirish uchun sharoit yaratamiz.

Veb-platforma orqali mavjud bo'lgan xaritalash xizmatlari o'rtasida tanlovni takomillashtirishda biz xaridorlar uchun shaxsiy shaxsiy ma'lumotlar evaziga boshqa xaritalar uchun to'lovlarni almashtirishning muqobil usullarini taklif etadigan xizmatlarning o'sishini ta'minlaymiz va qo'shimcha ravishda standart veb-xaritadan foydalanish imkoniyatini yaratamiz. HTML-ga xaritalar. Va nihoyat, mobil ilovalarni yaratishdan ko'ra, veb-xaritalarni yaratishni arzonlashtirgan holda, biz ishlab chiquvchi platforma sifatida mobil veb-ni tanlash uchun biznes asoslarini yaxshilaymiz va shu bilan biz (mobil) veb-sayt "muvaffaqiyat" ning ko'payishiga umid qilamiz. yoki tarmoq effektlari.

  • Mualliflarga bugungi kunda rasm, video yoki podkastni joylashtirishi mumkin bo'lgan darajada dinamik, foydalanishga yaroqli va qulay veb-xaritalarni yaratishga imkon beradigan vositalarni aniqlang.
  • Ekran o'quvchilari va boshqa yordamchi texnologiyalar uchun foydalanish uchun xaritalar xususiyati va joylashuv to'g'risidagi ma'lumotlarning HTML-ga kirishini aniqlang va joylashtiring.
  • Veb-platformada xarita ma'lumotlarini hisobga olish xavfsizligini aniqlang va loyihalashtiring.
  • Stsenariylashni yoki batafsil xaritalash serverining texnologiyasini bilishni talab qilmaydigan xaritalash mashuplarini yaratish uchun belgini belgilang, ya'ni hujjat bilan bog'lanish kabi oson bajarilishi mumkin.
  • Ushbu xizmatlarning taklif qilingan veb-platforma xaritalash standartlariga integratsiyalashuvini loyihalashtirish orqali OpenStreetMap va milliy va xalqaro SDIlar kabi umumiy fazoviy ma'lumotlar infratuzilmalaridan (SDI) foydalanishni soddalashtiring.
  • Mavjud kosmik (xarita) tarkibni boshqarish tizimlari, API va veb-xizmatlaridan foydalanish mumkin bo'lgan seriyalashtirish formatiga xaritada yoqilgan HTMLni aniqlash va (advokat).
  • Operatsion model bilan o'zaro bog'liqlik yoki mavjud bo'lgan kosmik (xarita) tarkibni boshqarish tizimlari, API va veb-xizmatlarning mavjudligi. Masalan, rivojlanayotgan OGC API standartlari.

Kengaytiriladigan veb-Manifest platforma xususiyatlarining takroriy rivojlanishi va evolyutsiyasini past darajadagi "ibtidoiy" lardan boshlanib, natijada yuqori darajadagi xususiyatlarga olib borishni talab qiladi. Ushbu taklifga xos bo'lgan yoki unga aloqador bo'lgan bir nechta past darajadagi ibtidoiy takliflar mavjud bo'lsa-da, umuman olganda, bu yuqori darajadagi xususiyat uchun taklif sifatida qaralishi mumkin. Ushbu xususiyat HTML-da deklarativ dinamik veb-xaritalardir. Veb-xaritalash - bu JavaScript-ni kutubxonasining etuk toifasi, uning rivojlanish tsikli bosqichida, ushbu kutubxonalarning ba'zi bir umumiy xususiyatlarini platformaga kiritish kerak. Shunday qilib, ushbu taklif ochiq va yopiq manbali JavaScript veb-xaritalash kutubxonalarining ba'zi "sigir yo'llari" ni qamrab oladi, shuningdek server tomoni xaritalash xizmatlari va API-larni qanday qo'shishni hisobga oladi.

Tavsiya etilgan kengaytma, foydalanuvchi agenti soyasi ildizida boshqaruv elementlarini o'z ichiga olgan (& ltvideo & gt-ga o'xshash bugungi kunda), child & ltlayer & gt elementlari bilan tarkibiga kiritilgan va o'z ichiga olishi mumkin bo'lgan engil DOM xaritasi bilan bog'liq belgilarni (so'z birikmasi) yaratadigan standart & ltmap & gt vidjetini yaratadi. shuningdek, ushbu taklifning bir qismi):

Tavsiya etilgan elementlar va polyfill haqida batafsil ma'lumot olish uchun Yuqori darajadagi API izohchisiga qarang.

Dizaynni batafsil muhokama qilish

Ishlar va talablardan foydalaning

Ushbu taklif veb-xaritalarni standartlashtirish uchun foydalanish holatlari va talablari asosida, talab qilinadigan funksionallik va polyfilled xatti-harakatlar o'rtasidagi bo'shliqlarni aniqlash uchun baholanmoqda.

MapML UCR bajarish matritsasiga qarang, MapML mavjud bo'lgan veb-xaritalash kutubxonalaridan farqli o'laroq, imkoniyatlarini qanday taqqoslaydi.

Internet uchun xaritalarda W3C / OGC qo'shma seminari

Tabiiy resurslar Kanadasi 2020 uchun Internet-xaritalar guruhi bilan hamkorlikda Internet uchun xaritalarda W3C / OGC qo'shma seminar seriyasini o'tkazdi.

MapML-ning muqobil dizaynlari ko'rib chiqildi

TBD - biz ko'plab alternativalarni ko'rib chiqdik, hozirda ularni hujjatlashtirish uchun bug 'tugadi. Shuningdek, ushbu hujjat allaqachon ancha uzun. Ishlar rivojlanib borar ekan, men bu erga tarkib qo'shaman.

    - SVGMap taklifini va ushbu taklifni birlashtirish mumkinmi? Yoki ular raqobatdosh takliflarmi?
  • API-lar: Leaflet, OpenLayers va boshqalar, (boshqalarga o'zaro bog'liq manbalarni taqsimlash tushunchasi bo'lmasa ham) mukammal xaritada skript yozish uchun API va hodisalarni taqdim etadi. Ushbu yoki shunga o'xshash API-lar taklif qilingan HTML infratuzilmasi ustiga qurilishi mumkinmi? Tavsiya etilgan HTML bilan mualliflar uchun hayot osonroq bo'ladimi?
  • Joriy vaziyat

Manfaatdorlarning mulohazalari / qarama-qarshiliklari

Ba'zi ishtirokchilar, biz itoat etish ruhiga o'xshamaydigan cho'kkan xarajatlarning noto'g'riligi sababli, boshidan boshlashimiz kerakligini aytishdi va umid qilamanki, ushbu taklifni energiya yoki pulni behuda sarflash sifatida ko'rish to'g'ri emas. Yaxshi strategiya aniq, harakatga keltiriladigan va bosqichma-bosqich o'zgarishlarni talab qilish uchun murojaat qilishdir. Hozirgi tushuntirishni aynan shu ruhda taklif qilishadi.

Ushbu loyihaning maqsadi - veb-brauzer loyihalarini veb-xaritalarni yuqori darajadagi xususiyat sifatida kerakli va taklifni amalga oshirish mumkinligi to'g'risida kelishib olish va keyin funktsiyani amalga oshirish va etkazib berish. Bu erga etib borish uchun bizda yo'qligi qarama-qarshilikka teng keladigan brauzer ishlab chiquvchilarining ishtiroki kerak. Shunday qilib, qilish kerak bo'lgan ish bor.

Adabiyotlar va minnatdorchiliklar

Quyidagi odamlarning hissalari, maslahatlari va yordamlari minnatdorchilik bilan qabul qilinadi:

Benoit Chagnon, Brayan Kardell, Maykl tm Smit, Robert Linder, Joan Maso, Kit Pomakis, Gil Xeo, Jerom St-Lui, Ameliya Bellami-Royds, Nik Chan, Nik Fitssimmonlar, Saymon Piters, Tom Kralidis, Daniel Morissette, Kris Xojson, Ahmad Yama Ayubi, Bennett Feely, Dag Schepers

Agar sizni eslashni unutgan bo'lsam, iltimos, biron bir masalani oching.

Xatolar va kamchiliklar, albatta, o'zimnikidir, agar siz yuqoridagi tuzatishlarni aniqlasangiz, iltimos, muammoni oching.


Xaritada tuzatishlar bera olamanmi? Ha, iltimos, menga elektron pochta orqali imkon qadar batafsil ma'lumot bering va men xaritani o'zgartirishga harakat qilaman. Iltimos, iloji bo'lsa, dastlabki hujjatlar yoki xaritalarga havolalar keltiring, ammo mahalliy bilimlar ham qadrlanadi. Agar siz xaritani chizib qo'ymoqchi bo'lsangiz yoki hatto juda yaxshi bo'lgan KML taqdim qilsangiz. Odatda men bir necha hafta ichida harakat qilaman va javob beraman, ammo agar ish og'ir bo'lsa yoki men bo'shashsam, bu menga ko'proq vaqt talab qilishi mumkin.

Sizga elektron pochta orqali xabar yuborishim mumkinmi? Ha, [email protected] manziliga. Bir necha hafta ichida barcha savollarga va takliflarga javob berishga harakat qilaman. Ba'zan men javob berolmayman, chunki pochta serverlari va spam-filtrlar blokirovkaga olib keladi. Agar siz elektron pochta orqali o'ta olmasangiz, unda Facebook yoki Twitter-ni sinab ko'ring.

Xaritaning nusxasini va uning manba ma'lumotlarini olsam bo'ladimi? Yo'q, hozir emas. Hozirda veb-saytning o'zi orqali kirishni cheklamoqdaman, shuning uchun hech qanday manba ma'lumotlari ochiq emas (kelajakda uni sotib olishim mumkin). Ammo, agar siz ma'lum bir kichik maydon uchun ma'lumotlarga qiziqsangiz, men yordam berishim mumkin. Faqat zamonaviy temir yo'l ma'lumotlariga muhtoj bo'lganlar uchun Open Street Map ma'lumotlari (Geofabrik) erkin foydalanish mumkin va siz ma'lumotlarni yuklab olishingiz va Google Earth kabi GIS dasturlarida namoyish qilishingiz mumkin.

Xaritadagi rasmlardan foydalanishim mumkinmi? Ha, lekin oddiy mualliflik huquqi qoidalari bo'yicha - ya'ni faqat o'rtacha miqdordagi rasmlardan foydalaning, hammasini nusxa ko'chirmang, qayta sotmang (UoY qo'llanmasiga qarang). Agar shubhangiz bo'lsa, menga elektron pochta orqali ruxsat so'rab yuboring. Iltimos, mening mualliflik huquqim to'g'risidagi bayonotni (sahifaning pastki qismida ko'rsatilgandek) har qanday rasmga qo'shib qo'ying va iltimos, RailMapOnline-ga qaytib ma'lumot bering. Shuningdek, fon xaritasi tasvirlari mualliflik huquqiga (masalan, Google tomonidan) tegishli ekanligini unutmang, shuning uchun ularning shartlarini ham bajarganingizga ishonch hosil qiling.

Nima uchun u mening brauzerimda / telefonimda ishlamaydi? Veb-saytni turli xil brauzerlar bilan sinab ko'raman, lekin eski brauzerlar (masalan, Internet Explorer) qo'llab-quvvatlanmaydi, deb qo'rqaman. Agar siz hali ham IE dan foydalansangiz, iltimos, zamonaviy brauzerga o'ting! Turli xil telefonlar va operatsion tizimlarni sinab ko'rolmayman - agar sizda muammo bo'lsa, iltimos, menga imkon qadar ko'proq ma'lumot bering.

Nima uchun u ishlamay qoldi? Men bepul sevimli mashg'ulot saytim bo'lishidan qo'rqaman, men xizmatga kafolat berolmayman. Xususan, men veb-xosting kompaniyamga (ular juda ishonchli) va xaritalarni ko'rsatish uchun Google-ga (vaqti-vaqti bilan muammolar bo'lgan) ishonaman. Muammo bo'lsa, menga xabar bering va men imkon qadar tezroq ko'rib chiqishga harakat qilaman. Uzoq sharqdagi internet-provayderlardan yoki ma'lum spam-serverlardan kirishni to'xtatishi mumkin bo'lgan Google tomonidan xavfsizlik bo'yicha ba'zi cheklovlar mavjud.

Nima uchun kvadrat plitkalar etishmayapti? Asosan, Google temir yo'l / kanal xaritalarini ko'rsatadi va ularni to'rtburchaklar shaklida brauzeringizda ko'rsatadi. Ba'zan plitkalar berilmaydi. Men buni tuzatolmasligimdan qo'rqaman, chunki bu Google muammosi. Sahifani qayta yuklashga harakat qiling yoki brauzer keshini bo'shatib bo'lmadi.

Nima uchun xaritaning bir qismi (butun mintaqa) yo'qolgan? Ba'zan Google xaritani so'rashi va mening veb-xostim javob berishi va Google vaqti tugashi orasida kechikish bo'ladi. Bu sodir bo'lganda, Google yana urinmaydi va xaritaning katta qismi ko'rsatilmaydi. Bu ertasi kuni tiklanishi kerak, ammo muammo hal etilmasa, menga xabar bering.

Tarixiy OS fon xaritalari bilan nima sodir bo'ldi? Ushbu ma'lumotlar Shotlandiyaning Milliy kutubxonasi tomonidan taqdim etilgan bo'lib, afsuski hozirda ushbu xizmatlar uchun (katta miqdordagi mablag ') talab qilinadi. Hozircha bu shuni anglatadiki, men saytdan fonlarni olib tashlashim kerak edi.

Joriy xarajatlarga o'z hissangizni qo'shish uchun sizga pul bera olamanmi? Ha, siz menga Ko-fi-dan kofe sotib olishingiz mumkin, bu veb-saytning xarajatlariga yordam beradi, veb-sayt reklamasini bepul saqlaydi va ma'naviy belgilarni sotib oladi. Va qo'llab-quvvatlash so'zlari har doim qadrlanadi! Afsuski, men xayriya evaziga qo'shimcha xizmatlarni va'da qila olmayman.

Xaritaga havola qilsam bo'ladimi? Ha, iltimos. Siz xaritani o'ng tugmasini bosib va ​​havolani yaratish-ni tanlab, ma'lum bir joyga havola yaratishingiz mumkin. Agar siz o'zingizning ma'lumotlar bazangizdan yoki veb-saytingizdan havolalar yaratmoqchi bo'lsangiz, u holda bog'laning va men sizning havolangizga o'tish uchun maxsus marker va popup yaratib berishim mumkin.

Veb-sayt uchun yangi g'oyani taklif qila olamanmi? Albatta - men har doim fikr-mulohazalarga qiziqaman. Ammo, bu faqat men bo'lgani kabi, sizning fikrlaringizni birlashtira olmasam, xafa bo'lmang.

Ilova bormi? Yo'q, hozirda faqat veb-sayt. Siz xaritaga telefoningizdagi istalgan brauzer orqali kirish imkoniyatiga ega bo'lishingiz kerak, ammo mobil telefonda ba'zi bir funksiyalar qiyin bo'lishi mumkinligini qadrlayman. Men sizning ma'lumotlaringiz uchun to'lovlarni kamaytirish uchun sayt foydalanadigan ma'lumotlarni kamaytirishga harakat qildim, lekin xaritalash tasvirining o'zi har doim va Internetga ulanishni talab qiladi.

Ma'lumot manbai nima? Men temir yo'llar va marshrutlar bo'yicha barcha ma'lumotlar uchun mualliflik huquqidan tashqarida xaritalash va erkin mavjud bo'lgan onlayn manbalardan foydalanaman. Shuningdek, men Vikipediya, forumlar va boshqa veb-saytlardagi ma'lumotlardan foydalanaman va ularni xaritadan bog'lashga harakat qilaman. Shuningdek, siz ko'p yillar davomida taqdim etgan ma'lumotlar xaritasi kam bo'lgan yoki faqatgina mahalliy bilimlar bilan joylarni aniqlab beradigan temir yo'llar uchun juda muhimdir.

Qanday temir yo'llar tasvirlangan? Barcha vaqt oralig'idagi barcha temir yo'llar. Agar u relslarda harakatlansa va siz unga minishingiz mumkin bo'lsa, men uni qo'shmoqchiman. Yarmarka safari (masalan, rollercoasters), vaqtinchalik qurilish temir yo'llari, minish uchun juda kichik model temir yo'llar, teleferiklar (relslar yo'q!) Va er osti temir yo'llari temir yo'llari (juda qiyin!) - agar men ularni kiritishga qaror qilmasam.

Qaysi vaqt davri tasvirlangan? Barcha davrlar, bir vaqtning o'zida bir xil xaritada. Buning natijasi o'laroq juda band bo'lgan xaritaga olib kelishi mumkinligini tushunaman, ammo afsuski, men buni boshlaganimda o'ylamagan edim!

Ranglar nimani anglatadi? Buyuk Britaniyaning temir yo'l xaritasi uchun rang egalik kompaniyasini oldindan guruhlashni aniqlaydi (taxminan 1923). AQSh temir yo'l xaritasi uchun rang chiziqni qurgan kompaniyani aniqlaydi. Men AQSh quruvchilarini va Buyuk Britaniyaning ba'zi yo'nalishlarini aniqlashda muammolarga duch keldim, shuning uchun xatolar borligini menga xabar bering. Bunday katta xaritada ba'zi kelishuvlar mavjud: xususiy egalarning kichik chekkalari qo'shilgan yo'l uchun rangli. Ko'pgina kichik sanoat tramvay yo'llari birma-bir aniqlanishdan ko'ra bir xil rangga ega. Buyuk Britaniyada, keyinchalik (1923 yildan keyin) treklar xuddi guruhlarga bo'lgandek ranglanadi. Buyuk Britaniyada, avvalroq (1923 yilgacha yopilgan) treklar hanuzgacha mavjud bo'lgan kabi ranglanadi. Buyuk Britaniyada, post BR (1948) treklari alohida quyuq kulrang rang sifatida aniqlanadi, ammo bu faqat muhim qo'shimchalar uchundir va har bir siding / kavşak tanlanmaydi.

Nega yonbag'ir etishmayapti yoki nega marshrut ikki martalik yo'l sifatida ko'rsatilmagan? Men har qanday pog'onani / pog'onani o'z ichiga olmayman, aksincha stantsiyalar / maydonlar va mavjud turli marshrutlarni namoyish etishga harakat qilaman. Ikki / uch kishilik trek bitta trekdan farqlanmaydi, agar turli yo'llar sezilarli darajada farq qilmasa.

Qanday stantsiyalar mavjud? Hozirda faqatgina Buyuk Britaniyaning temir yo'l xaritasida stantsiyalar mavjud. Barcha stantsiyalar, shu jumladan qayta joylashtirilgan joylar ham kiritilgan. Stantsiya nomlari juda o'zgaradi, shuning uchun men barcha o'zgarishlarni aks ettiruvchi matnni kiritishga harakat qildim. Stantsiyalarni qidirishda turli xil ismlarni hisobga olish uchun qidiruv so'zining boshida * joker belgidan foydalanishni maslahat beraman.

Qanday xususiyatlar mavjud? Hozirda faqatgina Buyuk Britaniyaning temir yo'l va kanal xaritasida xususiyatlar mavjud va har doim ko'proq narsalar qo'shilib boriladi. Sanoat, kavşaklar, ko'priklar va tunnellarni o'z ichiga olgan muhim xususiyatlar. Ismlar ba'zida o'zgarib turadi, shuning uchun muqobillar qavs ichida berilgan va men sizga qidiruv so'zining boshida * joker belgilaridan foydalanishni maslahat beraman. Signal qutilari va stansiya xususiyatlari hozircha kiritilmagan.

Nima uchun afsona to'liqsiz? Agar siz xaritalarda yo'qolgan afsonaviy yozuvni ko'rsangiz, iltimos, menga xabar bering - bu to'liq bo'lishi kerak!

Xarita qanchalik aniq? Treklarni tasvirlashga harakat qilaman, shunda siz ularning joylashuvini yerda yoki sun'iy yo'ldosh tasvirlarida osongina topishingiz mumkin va men yo'llarni to'g'ri yo'lga qo'yishni maqsad qilganman. Mening asl maqsadim landshaftni o'rganishda treklarni aniqlashga yordam berish edi. Biroq, mening xaritalarimda xatolar bo'ladi va ularni tasvirlar va xaritaning turli xil fonlari ustiga qo'yganda, bu xaritalarda ham xatolar bo'lishi mumkin. Ba'zi hududlar, xususan, AQShda taxminiy bo'lib qolmoqda, lekin men vaqti-vaqti bilan harakat qilib, yangilab turaman. Xulosa - xaritani navigatsiya yoki rejalashtirish uchun ishlatmang - o'zingizning tadqiqotlaringiz uchun boshlang'ich nuqta sifatida foydalaning.

Men hissa qo'sha olamanmi? Agar siz ma'lumot va tuzatishlarni taqdim etmoqchi bo'lsangiz, iltimos, bog'laning.

Saytda reklama bera olamanmi? Yo'q. Men har doim RailMapOnline-ni reklamasiz saqlashga intilaman. Ammo, agar siz tarixiy jamiyat, meros temir yo'li, miniatyura temir yo'l operatori yoki muzeyi bo'lsangiz, xaritada tasvirlangan trekka havolani qo'shmoqchi bo'lganingizdan keyin bog'laning.

Nima uchun fon xaritasida joy nomi yo'q yoki ma'lum bir xususiyat ko'rsatilmagan? Orqa fon xaritalari mening nazoratimdan tashqarida va muammo haqida xabar berish uchun xarita provayderlariga murojaat qilishingiz kerak bo'ladi.

Modern Rly qatlamidagi xatoni tuzata olasizmi? Modern Rly qatlami OpenStreetMap ma'lumotlarining to'g'ridan-to'g'ri nusxasi bo'lib, men yiliga bir marta yangi nusxasini yarataman. Men qatlamni tahrir qilmayman yoki uni tekshirmayman va tahrirlashga qodir emasligimdan qo'rqaman (mening e'tiborim Tarixiy qatlamlarga qaratilgan). Biroq, har kim OpenStreetMap-da yordam berishi va tahrirlashi mumkin, shuning uchun siz ishtirok etishni istasangiz va o'zingizning xaritalaringizni yaratishni boshlasangiz, ularni tekshirib ko'ring.

Veb-saytning xavfsiz versiyasi (HTTPS) bormi? Ha. Siz avtomatik ravishda xavfsiz HTTPS saytiga yo'naltirilishingiz kerak.

Nima uchun geolokatsiya mening pozitsiyamni ko'rsatmayapti? Siz xavfsiz saytni (HTTPS) ishlatishingiz, qurilmangiz joylashuvini yoqishingiz va brauzeringiz sizning joylashuvingizni bilishi uchun veb-sahifaga ruxsat berishingizni talab qilishi mumkin. Joylashuvning aniqligi sizning qurilmangizning imkoniyatlariga va GPS kabi xizmatlarning mavjudligiga bog'liq.

Men haqimda ma'lumot to'playsizmi? Yo'q, men cookie-fayllardan foydalanmayman yoki veb-saytdan qanday foydalanishingiz haqida ma'lumot to'plamayman. Qo'shimcha ma'lumot bu erda. Agar siz men bilan elektron pochta orqali bog'lansangiz yoki menga Facebook yoki Twitter-da xabar yuborsangiz, men sizning aloqa ma'lumotlaringizni marketing uchun ishlatmayman yoki uni uchinchi tomonga bermayman.


Ochiq o'yinchilarni plitkalarni yangilash uchun brauzer keshidan foydalanmaslikka majbur qiling - Geographic Information Systems

<% include new_since.ad version = "2.24"%> Klaster xususiyatlarini yoqish uchun 1 ga yoki bitta tugunni sozlash uchun 0 ga sozlang.

<% include new_since.ad version = "2.24"%> Barcha klaster tugunlarini ulash uchun umumiy url naqshini aniqlang. Har bir klaster tuguni berilgan manzilda mavjud bo'lishi kerak. Ushbu urlni umumiy qilish uchun 3 o'zgaruvchi almashtiriladi: - $ hostname $: hostname-dan hostname - $ url_prefix $: url_prefix-dan url prefiksini o'z ichiga oladi - $ proto $: http yoki https-ni avtomatik aniqlashga urinish, autodetect faqat OMD bilan ishlaydi va aks holda http ga qaytadi.

<% include new_since.ad version = "2.24"%> Vaqt tugashini o'rnating, shundan so'ng tugun klasterdan o'chiriladi.

YO'Q: buni o'rnatish Thruk 2.34 yoki undan keyingi versiyada ta'sir qilmaydi.

Qolgan api sukut bo'yicha yoqilgan bo'lib, uni o'chirib qo'yish Thruk ishini buzadi.

<% include new_since.ad version = "2.24"%> api tugmalaridan foydalanish 0 ga o'rnatilishi bilan o'chirib qo'yilishi mumkin.

Eslatma: ushbu qiymat har bir foydalanuvchi / guruh asosida bekor qilinishi mumkin emas, chunki u autentifikatsiyadan oldingi bosqichda ishlatiladi. Agar foydalanuvchilar yangi tugmachalarni yaratishini istasangiz, max_api_keys_per_user dan foydalaning.

<% include new_since.ad version = "2.32"%> Foydalanuvchi yaratishi mumkin bo'lgan kalitlarning cheklangan miqdori. Yangi kalitlarni to'liq yaratishni o'chirish uchun 0 ga sozlang

Mobil plaginiga yo'naltiriladigan foydalanuvchi agentlarini ko'rsating (agar yoqilgan bo'lsa).

Barcha foydalanuvchilar uchun foydalanish uchun standart mavzu. Mavzular papkasida yaroqli katalog bo'lishi kerak.

Haftaning birinchi kunini belgilang. Hisobotlarda ishlatiladi. Yakshanba: 0 dushanba: 1

Xotirani haddan tashqari ishlatmaslik uchun katta hisobotlarda vaqtinchalik fayllardan foydalaniladi. "Report_use_temp_files" yordamida hisobotning davomiyligini bir necha kun ichida belgilashingiz mumkin, bu esa vaqtinchalik fayllardan foydalanishni boshlaydi. Odatiy - 14 kun, shuning uchun "oxirgi 31 kun" hisobotida temp fayllari ishlatiladi, "bu hafta" emas. 0 ga o'rnatib o'chirib qo'yish mumkin.

Ushbu raqamdan ko'proq xost / xizmatlarga ega hisobotlarni yaratmang. Maqsad - kengaytirilgan xotira ishlatilishi sababli serverni buzmaslik. Agar siz ushbu cheklovga etib ketsangiz va xotirangiz etarli bo'lsa, bu raqamni oshiring.

Hisobotlarga (dastur xabarlari) bo'lgan xabarlarni kiriting. Buni 0 ga o'rnatish MySQL-ning orqa qismiga indekslardan samarali foydalanishga imkon beradi

Hisobotlarni ishga tushirishdan oldin logcache ma'lumotlar bazalarini yangilash kerakmi? Buni 0 ga o'rnatish hisobotlarni yuritish uchun sarflanadigan vaqtni qisqartiradi, ammo eng so'nggi ma'lumotlarga ega bo'lish shart emas. Agar siz ushbu parametrdan foydalansangiz, ehtimol "thruk -a logcacheupdate" ni ishga tushirish uchun cron yaratishingiz kerak

Ushbu havola boshlang'ich sahifa sifatida ishlatiladi va odatda main.html-ga versiya ma'lumotlari va umumiy havolalar ko'rsatiladi.

Ushbu havola asosiy logotiplardan birini bosganingizda ishlatiladi. Odatiy bo'lib, bu logotiplar Thruk logotiplari va havola sizni Thruk bosh sahifasiga olib boradi. Buni uyingiz joylashgan joy bilan almashtiring.

Ushbu havola hujjatlarga havola sifatida yon navigatsiya menyusida ishlatiladi. Hujjatlaringiz joylashgan joy bilan almashtiring. Hujjatlar havolasini menyuda umuman istamasangiz, uni bo'sh qiymatga qo'ying.

Yon menyuda "muammolar" havolasi uchun moslashtirilgan havola. Sizning kompaniyalaringizda xatolarni ko'rib chiqish jarayonini aks ettirish foydali bo'lishi mumkin.

Kadrlar ichidagi havolalar o'rnatilishi mumkin bo'lgan ruxsat berilgan naqshlar ro'yxati. Siz /thruk/frame.html?link=http://wiki.my-company.com/page/blah ga bog'lanishingiz mumkin, keyin sizning vikingiz Thruk navigatsiya ramkasida ko'rsatiladi. Boshqa qo'shimchalar uchun foydalidir, shuning uchun ular o'zlarining navigatsiyasini ko'rsatishlari shart emas.

Thruk jarayoni so'rov tugagandan so'ng chiqadigan maksimal xotiradan foydalanish (MB da). Faqat fcgid xizmatiga ta'sir qiladi.

Agar kontaktning o'zi uchun belgilanmagan bo'lsa, kontaktga buyruqlar yuborish uchun ruxsat berilishi kerak bo'lsa, buni o'rnating. This is the default value for all contacts unless the user has a can_submit_commands setting in your monitoring configuration.

Use this to disabled specific commands. Can be use multiple times to disabled multiple commands. The number can be found in the 'cmd_typ' cgi parameter from links to the command page. If you only want to allow a few commands, use command_enabled instead. You may use ranges here. If you want to disable all commands, you can use command_disabled = 0-999 or set the authorized_for_read_only role.

See a list of available commands along with their ids on the commands page.

Enable only specific commands. Overrides command_disabled setting by only allowing a few specific commands and disabling all others. The syntax is the same as in command_disabled . When using command_enabled then all commands are disabled and only those from command_enabled can be used.

See a list of available commands along with their ids on the commands page.

Convert authenticated username to lowercase.

Convert authenticated username to uppercase.

Convert authenticated username by regular expression. The following example removes everything after an @ from the authenticated username and '[email protected]' becomes just 'user'.

When set to a true value, every contact will only see the hosts where he is contact for plus the services where he is contact for. When disabled, a host contact will see all services for this host regardless of whether he is a service contact or not.

Allow specific hosts to bypass the csrf protection which requires a generated token to submit certain post requests, for example to send commands. Use comma seperated list or multiple configuration attributes. Wildcards are allowed.

Disable the possibility for a user to change his password. Only works with htpasswd passwords. To make this work you have to set a htpasswd entry in the Config Tool section.

Sets the minimum lenght a password must have for users changing their passwords. Admins still can change the password any way they want in the config tool. This just affects the user password reset.

<% include new_since.ad version="2.36" %>Show the basic auth user / password formular. Enabled when using cookie auth. You may want to disable this if you only use oauth2 authentication.

The path to your cgi.cfg. See cgi.cfg for details.

The path to your log4perl configuration file.

verbosity / debug level same as setting THRUK_VERBOSE environment.

0 = info / warnings (default)

3 = enables performance debug output for each request (same as THRUK_PERFORMANCE_DEBUG=3 in env)

Enable author tweaks. Same as setting THRUK_AUTHOR environment. Only required for development, disables caches, enables template strict mode and more.

If a page takes longer to render than this amount of seonds, a profile will be logged. Set to 0 to disable logging completely.

Set level of machine information send in bug reports.

Possible options: - prod contains release information (default) - full contains uname and release information - none no information

Defines an optional seperate logfile with some extra audit relevant log entries. The different categories can be used to enable/disabled specific messages. The logfile can use strftime format pattern to for ex.: add the timestamp to the logfile.

Path to your plugins directory. Can be used to specify different location for you Thruk plugins. Don’t forget to set appropriate apache alias or rewrite rules when changing the plugin path. Otherwise the static content from plugins is not accessible.

Example redirect rule for apache:

Url to Thruks plugin registry. The url must supply a json data structure with a list thruk plugins. Can be specified multiple times.

Path to your themes directory. Can be used to specify different location for you Thruk themes. Don’t forget to set appropriate apache alias or rewrite rules when changing the themes path. Otherwise the static content from your themes may not accessible.

Path to the var directory. Thruk stores user specific date here.

Path to a temporary directory. Defaults to /tmp if not set and usually this is a good place.

The path to your ssi (server side includes) files. See Server Side Includes for details.

Specify a additional directory for user supplied templates. This makes it easy to override thruks own templates. Template search order is:

Changes the path to your logo images. Default is $url_prefix+'thruk/themes/'$current_theme'/images/logos/' and therefor relative to the current selected theme. You could set a fixed path here. Like usual, paths starting with a / will be absolute from your webserver root directory. Paths starting without a / will be relative to the cgi directory.

Location of your logos in your filesystem. This directory should be mapped to your 'logo_path_prefix' directory where 'logo_path_prefix' is the path relative to your webserver root directory and 'physical_logo_path' is the corresponding filesystem path.

Mode used when creating or saving files.

Mode used when creating folders

Set a general resource file. Be warned, if any macros contain sensitive data like passwords, setting this option could expose that data to unauthorized user. It is strongly recommended that this option is only used if no passwords are used in this file or in combination with the 'expand_user_macros' option which will limit which macros are exposed to the user. Instead of using a general 'resource_file' you could define one file per peer in your peer config.

Search long_plugin_output in default search, ex. from the side navigation. It is enabled by default, but can have significat performance impact in larger setups.

<% include new_since.ad version="1.86-2" %>The default_service_filter set a default service filter which is used when no other filter is applied (except from links to hosts or groups). The filter is negated by a leading exclamation mark. The example filters out all services starting with "test_". You can use regular expressions. The Default is not set.

Using the pager will make huge pages much faster as most people don’t want a services page with 100.000 services displayed. Can be disabled if you don’t need it.

Define the selectable paging steps. Use the * to set the default selected value.

Just like the paging_steps, but only for the groups overview page.

Just like the paging_steps, but only for the groups summary page.

Just like the paging_steps, but only for the groups grip page.

Cut off objects on problems page, set 0 to disable limit completly. Defaults to 500.

Change path to your host action icons. You may use relative paths to specify completely different location. You also may want to use 'action_pnp.png' when using pnp. Icon can be overridden by a custom variable '_ACTION_ICON'.

Change path to your service action icons. You may use relative paths to specify completely different location. You also may want to use 'action_pnp.png' when using pnp. Icon can be overridden by a custom variable '_ACTION_ICON'.

Set whether you want to use a framed navigation or not. With using frames it’s sometimes easier to include addons. See allowed_frame_links option for how to integrate addons.

Show the new split command box on the host / service details page.

what email address bug reports will be sent to

Default timeformat. Use POSIX format.

Default trends timeformat.

Default timeformat for todays date. Can be useful if you want a shorter date format for today.

On which event should the comments / downtime or longpluginoutput popup show up. Valid values are onclick or onmouseover.

Options for the popup window used for long pluginoutput, downtimes and comments. See http://www.bosrup.com/web/overlib/?Command_Reference for what options are available

Display the current number of notification after the current / max attempts on the status details page.

<% include new_since.ad version="2.14" %>List of default columns on host details page. Determines which columns and the order of the displayed columns. See an example on the Dynamic Views page.

<% include new_since.ad version="2.14" %>List of default columns on service details page. Determines which columns and the order of the displayed columns. See an example on the Dynamic Views page.

<% include new_since.ad version="2.38" %>List of default columns on overview details page. Determines which columns and the order of the displayed columns. See an example on the Dynamic Views page.

<% include new_since.ad version="2.38" %>List of default columns on grid details page. Determines which columns and the order of the displayed columns. See an example on the Dynamic Views page.

Display the backend/site name in the status table. This is useful if you have same hosts or services on different backends and need to know which one returns an error. Valid values are:

Show links to config tool for each host / service. You need to have the config tool plugin enabled and you need proper permissions for the link to appear.

Display the full command line for host / service checks . Be warned, the command line could contain passwords and other confidential data. In order to replace the user macros for commands, you have to set the 'resource_file' in your peer config or a general resource_file option.

0 = off, don’t show the command line at all

1 = show them for contacts with the role: authorized_for_configuration_information

2 = show them for everyone

<% include new_since.ad version="2.18" %>Replace pattern for expanded command lines. Could be used to replace sensitive information from beeing displayed in the gui. The pattern is a simple perl regular substitute expression in the form of '/pattern/replacement/'

Usually the source of your expanded check_command should be the check_command attribute of your host / service. But under certain circumstances you might want to use display expanded commands from a custom variable. In this case, set 'show_full_commandline_source' to '_CUST_VAR_NAME'.

Show additional logout button next to the top right preferences button. (works only together with cookie authentication)

<% include new_since.ad version="2.42" %>Change url of logout link. Might be useful in combination with oauth.

When a plugin returns more than one line of output, the output can be displayed directly in the status table, as popup or not at all. Choose between popup, inline and off

Color complete status line with status colour or just the status itself.

Show if a host / service has modified attributes.

Show host / service contacts. User must have the configuration_information role.

Show check attempts for hosts too. The default is to show them on the problems page only. Use this value to force a value.

This option enables a performance bar inside the status/host list which create a graph from the performance data of the plugin output. Available options are 'match', 'first', 'all', 'worst' and 'off'.

Show pnp popup if performance data are available and pnp is used as graph engine. The popup will be available on the performance data bar chart on the right side of each host/service. It uses the normal pnp popup logic, so you need to install the proper SSI files.

If set, a Internet Explorer (IE) compatibility header will be added to the html header.

Defines the order to determine the worst/best states. Used in business processes and the panorama dashboard. Can be overriden in those plugins.

Show inline pnp graph if available. If a service or host has a pnp4nagios action or notes url set. Thruk will show a inline graph on the extinfo page. This works for /pnp4nagios/ urls and /pnp/.

graph_word is a regexp used to display any graph on the details page. if a service or host has a graph url in action url (or notes url) set it can be displayed by specifying a regular expression that always appears in this url. You can specify multiple graph_words.

When using pnp4nagios, no graph_word is required, just keep it empty.

sample service configuration for graphite:

Quotes are supported in the action_url statement, you may want to use it for special graphite function (http://graphite.readthedocs.org/en/1.0/functions.html) Do not escape double quotes here, otherwise graph won’t work.

graph_replace is another regular expression to rewrite special characters in the url. For example graphite requires all non-word characters replaced by underscores while graphios needs spaces removed too. You can use this setting multiple times.

sample service configuration for graphite:

sample service configuration for graphios:

The http_backend_reverse_proxy will proxy requests for pnp or grafana action_urls via the http backend if possible. This only works for http backends and if cookie auth is enabled. Can be used to proxy thruk nodes (experimental)

Possible options: - 0 disabled - 1 enabled

Show custom vars in host / service ext info. List variable names to display in the host and service extinfo details page. Can be specified more than once to define multiple variables. You may use html in your variables. Use * as wildcard, ex.: _VAR* To show a host custom variable for services, prepend _HOST, ex.: _HOSTVAR1. To show all host variables in the service view, use wildcards, ex.: _HOST* Host variables are only used with HOST*, not by * alone, see examples.

Expose custom vars sets a list of custom variables which is safe for all users/contacts to view. They will be used in filtering and column selection as well as in json result sets. Basically they will be handled the same way as show_custom_vars except they will not be displayed automatically. Syntax is the same as show_custom_vars .

Expand user macros ($USERx$) for host / service commands and custom variables. Can be specified more than once to define multiple user macros to expand. Be warned, some user macros can contain passwords and expanding them could expose them to unauthorized users. Use * as wildcard, ex.: USER*

Defaults to 'ALL' which means all user macros are expanded, because its limited to admin users anyway.

Show link to bug reports when internal errors occur. Set to '1' to show a error icon which links to a error report mail. Set to 'server' to log js error server side. Set to 'both' to log server side but still show the icon.

ex.: show_error_reports = both

don’t report some known harmless javascript errors

ex.: skip_js_errors = cluetip is not a function

Normally passive checks would be marked as disabled. With this option set, disabled checks will only be displayed as disabled if their last result was active. Otherwise they would be marked as passive checks. This option also changes the passive icon only to be shown when the last check was passive, otherwise the disabled icon will be displayed.

Normally passive checks whould be displayed with a passive icon if their last result is passive. With this option, passive icon will be hidden in status details.

The sitepanel is used to display multiple backends/sites at a glance. With than 10 or more sites, the list of backends will be combined into the 'compact' site panel which just displays the totals of available / down / disabled sites. The 'compact' panel will also automatically be used if you use sections. With more than 50 backends, the 'collapsed' panel will be selected in 'auto' mode. With more than 100 backends, the 'tree' panel will be selected in 'auto' mode. Set sitepanel to list/compact/collapsed/tree/auto/off to change the default behaviour.

You can integrate the output of apache status into Thruk. The following list of apache status pages will be accessible from the performance info page. Make sure the page is accessible from Thruk, credentials will be passed through. So both, basic authentication or ip based authentication would be possible. Read more about Apaches mod_status here: http://httpd.apache.org/docs/current/mod/mod_status.html

DEPRECATED: please use LMD when using multiple backends.

Set logging of backend in verbose mode. This only makes sense when debug logging is activated.

Use connection pool when accessing multiple sites. Increases the performance because backends will be queried parallel but uses around 10mb of memory per pool member. Disabled when set to 0, number of concurrent connections otherwise.

<% include new_since.ad version="2.12" %>Enable lmd connection handling. Set to 1 to enable. LMD handles all backend connections in a separate process which will be started automatically with thruk if enabled. Read more on lmd at: https://github.com/sni/lmd or here LMD.

Path to additional lmd configuration. The sites will be automatically generated. Can be used multiple times.

Set some extra command line options when starting lmd.

Thruk waits this timeout for lmd to respond, otherwise it gets killed and restarted. Set to 0 to turn off automatic restarts (it will still be started if it is not running).

Instead of using LMD managed by Thruk, you can run your own LMD and let Thruk use that one instead

Enables caching logfiles for faster access and less memory usage for the naemon process. Cache supports only Mysql. Prefered type is Mysql. Format is a Mysql connection string like 'mysql://hostname:port/db'. Using a cache dramatically decreases cpu and memory usage of Thruk and Naemon when accessing logfiles, for example when creating reports.

<% include new_since.ad version="2.10" %>Define filter which prevents the logcache from overgrowing with useless log messages. Since the main reason for the logcache are availability reports it is ok to remove some entries. Can be used multiple times.

<% include new_since.ad version="2.12" %>This option enables/disables the delta updates of the logcache whenever somebody opens a page which requires logfiles, ex.: the showlog page. This improves the responsiveness of the page but you miss the latest log entries since the last manual update.

When having multiple sites, you can change the number of parallel updates with the logcache_worker option. Setting worker number to 1 disables parallel execution.

Default duration when running thruk logcache clean .

Default duration when running thruk logcache compact . Compact removes duplicate alerts having the same state. It also removes basically everything not required for sla reports and keeps a few extras like notifications.

Define wether logcache will be bypassed if the start / end time of a log querys is outside the range of the cache.

0 : never, only use cached logs and return empty result if outside cached range. (default)

1 : partially, bypass logcache if start and end are outside cache range, otherwise return partialy result.

2 : always, bypass logcache if either start or end are outside the cache range.

The import command replaces the builtin logcache update with an external script which is then responsible for updating the logcache database. This might be useful if you pull the logfiles from a ndo/ido database and then manually import those files.

There are some useful enviromenet variables set before the script is started:

standard macros as listed in CLI Environment

THRUK_BACKENDS is a semicolon separated list of the selected backends.

THRUK_LOGCACHE is the connection string to the thruk logcache database.

THRUK_LOGCACHE_MODE is either 'import' on first initial import or 'update' for further consecutive updates.

The fetchlogs command is very similar to the logcache_import_command but it replaces only the the fetching logs part from the bultin logcache. This script should return the plain text logfiles on stdout (standard naemon/nagios logfile format). This might be useful if you pull the logfiles from a ndo/ido database.

When having mixed backend cores, this command can be overridden in the peer configuration.

See ./support/icinga2_ido_fetchlogs.sh for an example.

There are some useful enviromenet variables set before the script is started to control which logs should be fetched:

REMOTE_USER contains the current user.

THRUK_BACKEND is a the id of the backends to import.

THRUK_LOGCACHE_START is start date to fetch

THRUK_LOGCACHE_END is the end date to fetch

THRUK_LOGCACHE_LIMIT is the optional limit of logfiles to fetch

If you are using a mysql database with galera replication such as MariaDB Cluster, Percona XtraDB Cluster or Galera Cluster it is a good idea to avoid locks and optimize/repair table statements since they are not properly replicated.

Especially in Percona XtraDB Cluster > 5.6 the default setting of pxc_strict_mode will disable locks all togheter.

This setting will make the logcache work in that case. More information about pxc_strict_mode available here: - Percona documentation

Delay the page delivery until the backends uptime is at least this amount of seconds. Displaying pages soon after backend restarts may display wrong results and all services are pending. Enable this if you experience problems with pending services after reloading your backend. Should be obsolete with Livestatus versions greater than 1.2 ex.: setting this to 10 would start serving pages 10 seconds after the backend reload

Can be set to enable / disable hostname verification for https connections. For example for the cookie login, https backends or oauth requests. It is not recommended to disabled hostname verification, set ssl_ca_path or ssl_ca_file instead.

Sets path to your certificates. Either set ssl_ca_path or ssl_ca_file . Not both. Defaults to ssl_ca_file = Mozilla::CA::SSL_ca_file() if Mozilla::CA perl module is installed or ssl_ca_path = '/etc/ssl/certs' otherwise.

Sets path to your ca store. See ssl_ca_path for details.

Cookie Authentication Settings

Specifies the url where non-authenticated users will be redirected too.

Specifies the url against the cookie auth provider will verify its credentials.

Specifies the timeout for idle sessions. Session will be removed if not used within this timeperiod.

Specifies the amount of seconds in which subsequent requests won’t verify authentication again. Set to zero to disable storing hashed credentials in the filesystem and disabling revalidation of active sessions.

Timeout for internal sub request on authentication url. Defaults to 10 seconds and can be disabled by setting it to zero.

Cookie domain is usually set automatically. Use this option to override the default value. Domains have to contain at least two periods. Useful for single sign on environments.

Hook script which is called on every successful login. The REMOTE_USER environment variable will be set to the username of the current logged in user. Useful to do magic stuff on each login. The REMOTE_USER_GROUPS environment variable contains semicolon separated list of contactgroups. Available standard environment variables are listed on the CLI Environment page.

<% include new_since.ad version="2.12" %>Disable account after this number of failed login attempts. This feature will be disabled if set to zero.

<% include new_since.ad version="2.46" %>The error message when an account is locked, may contain html.

<% include new_since.ad version="2.32" %>Increase logging of cookie authentication related things. This usually gets printed to the apache error log.

OAuth2 Authentication Settings

When the oauth provider needs to configure an allowed callback url, set the url of the login page, ex.:

or without <omdsite> when not using OMD.

Set oauth (oauth2) authentication provider

Set the default checked state for command options.

Forces acknowledgments to be sticky.

Forces sending a notification for acknowledgments.

Forces comments on acknowledgments to be persistent.

Forces normal comments to be persistent.

Default duration of new downtimes in seconds. Default is 2 hours.

Maximum duration of new downtimes. Use quantifiers like d=days, w=weeks, y=years to set human readable values. Default is unlimited.

Default duration of acknowledgements with expire date. Default is one day.

Configure which commands should be available as quick status commands.

When you want to reschedule passive checks for which the result is fetched by an agent (For example check_mk or some scenarios of check_multi). You usually want to reschedule the agent instead of the passive check.

The command reschedule alias can be used to translate the reschedule command from the passive service to the active agent service.

The pattern will be tested against the service description and the command_name of the passive check.

The resulting service name be on the same host and the contact must be authorized for that service too.

The pattern must be a valid perl regular expression.

Duplicates will be removed. So if you reschedule 10 services which result in the same master service will only trigger one reschedule.

Only passive services will be translated

In this example, all passive check_mk checks will trigger the active agent check and therefor allow you to reschedule passive checks directly from the problems page.

Use recurring downtime, shows recurring downtime links.

Use service’s description instead of display name.

Use trends, shows trend links.

Waiting is a livestatus feature. When enabled, Thruk will wait after rescheduling hosts/services checks until the check has been really executed up to a maximum of 10 seconds. Adjust the time waiting with the 'wait_timeout' option.

Amount of seconds to wait until a rescheduled check finishes. Thruk will wait this amount and display the result immediately.

If set to 1, the user has to enter a comment for all disable active checks / disable notifications / disable event handler commands. These comments are automatically prefixed with the command name and will be deleted when checks / notifications / handlers are enabled again. They are also used by the 'reenable_actions' utility.

Specify a file which is then completely under the control of Thruk. It will be used to store cronjobs, ex. for reports. The file has to be writable by Thruk.

The pre edit cmd can be used to do run a command just before Thruk will edit the crontab.

The post edit cmd is necessary for OMD where you need to reload the crontab after editing or for replacing the users cron with the edited file.

Path to your thruk executable. Will be used in cronjobs.

<% include new_since.ad version="1.86" %>The Action Menu is a way to create custom icons and menus for every host or service. There are two ways to set the menu. First one is to directly assign the menu json data into the _THRUK_ACTION_MENU custom variable of your host or service. Or you can just put a placeholder into the _THRUK_ACTION_MENU custom variable and define the actual menu in 'action_menu_items'. You may add multiple action icons or even multiple menus for each host or service.

See the Action Menu section from the advanced topics for more examples and details.

<% include new_since.ad version="1.86" %>Defines the menu used by placeholders from the '_THRUK_ACTION_MENU' custom variable. The menu is a key/value pair with the name and the menu description in json format. The menu can either be a single icon/menu or a list of menus and icons.

A simple menu could look like this, note that the menu has to be in a single line without newlines and all newlines from the example have to be removed in order to try that. But its more readable this way. You can also use a trailing backslash to write the menus on multiple lines.

Sample menu with two items and a seperator:

A menu has the following attributes:

icon icon for the menu itself. You can use <% raw %><> <% endraw %>as placeholder in the url and <% raw %><> <% endraw %>for the user name. Within OMD, the the site variable <% raw %><> <% endraw %>must be prepended.

title title of the menu, will be display on mouse over.

menu the actual menu definition as a list '[…​]' of sub items.

…​ arbitrary attributes will be used as attributes of the menu icon html element.

A single "-" item can be used as a menu item seperator.

The menu item can have the following attributes:

icon icon for the menu item. You can use <% raw %><> <% endraw %>as placeholder in the url. Within OMD, the the site variable <% raw %><> <% endraw %>must be prepended.

label label name of the menu item.

menu list of sub menu items.

action url or action which will be run or openend. This can either be a http(s) link or a serveraction in the form server://actionname/argument1/argument2/…​ the actionname must be a reference to a command from 'action_menu_actions'. You may use <% raw %><> <% endraw %>here too. Also javascript: links are valid, for example javascript:alert('$HOSTNAME

Autofill with Authenticator

Q: What is Autofill with Authenticator?

A: The Authenticator app now securely stores and autofills passwords on apps and websites you visit on your phone. You can use Autofill to sync and autofill your passwords on your iOS and Android devices. After setting up the Authenticator app as an autofill provider on your phone, it offers to save your passwords when you enter them on a site or in an app sign-in page. The passwords are saved as part of your personal Microsoft account and are also available when you sign in to Microsoft Edge with your personal Microsoft account.

Q: What information can Authenticator autofill for me?

A: Authenticator can autofill usernames and passwords on sites and apps you visit on your phone.

Q: How do I turn on password autofill in Authenticator on my phone?

A: Follow these steps:

  1. Open the Authenticator app.
  2. On the Passwords tab in Authenticator, select Sign in with Microsoft and sign in using your Microsoft account. This feature currently supports only Microsoft accounts and doesn't yet support work or school accounts.

Q: How do I make Authenticator the default autofill provider on my phone?

A: Follow these steps:

Open the Authenticator app.

On the Passwords tab inside the app, select Sign in with Microsoft and sign in using your Microsoft account.

  • On iOS, under Settings, select How to turn on Autofill in the Autofill settings section to learn how to set Authenticator as the default autofill provider.
  • On Android, under Settings, select Set as Autofill provider in the Autofill settings section.

Q: What if Autofill is not available for me in Settings?

A: If Autofill is not available for you in Authenticator, it might be because autofill has not yet been allowed for your organization or account type. You can use this feature on a device where your work or school account isn’t added. To learn more on how to allow Autofill for your organization, see Autofill for IT admins.

Q: How do I stop syncing passwords?

A: To stop syncing passwords in the Authenticator app, open Settings > Autofill settings > Sync account. On the next screen, you can select on Stop sync and remove all autofill data. This will remove passwords and other autofill data from the device. Removing autofill data doesn't affect multi-factor authentication.

Q: How are my passwords protected by the Authenticator app?

A: Authenticator app already provides a high level of security for multi-factor authentication and account management, and the same high security bar is also extended to managing your passwords.

  • Strong authentication is needed by Authenticator app: Signing into Authenticator requires a second factor. This means that your passwords inside Authenticator app are protected even if someone has your Microsoft account password.
  • Autofill data is protected with biometrics and passcode: Before you can autofill password on an app or site, Authenticator requires biometric or device passcode. This helps add extra security so that even if someone else has access to your device, they can't fill or see your password, because they’re unable to provide the biometric or device PIN input. Also, a user cannot open the Passwords page unless they provide biometric or PIN, even if they turn off App Lock in app settings.
  • Encrypted Passwords on the device: Passwords on device are encrypted, and encryption/decryption keys are never stored and always generated when needed. Passwords are only decrypted when user wants to, that is, during autofill or when user wants to see the password, both of which require biometric or PIN.
  • Cloud and network security: Your passwords on the cloud are encrypted and decrypted only when they reach your device. Passwords are synced over an SSL-protected HTTPS connection, which helps prevent an attacker from eavesdropping on sensitive data when it is being synced. We also ensure we check the sanity of data being synced over network using cryptographic hashed functions (specifically, hash-based message authentication code).

(Re)presenting the police.uk data at a street scale

With the crime data attributed to the street network, it was possible to use these features as the unit of display for a revised cartographic style. Relative rates of crime were calculated as the frequency of crimes within a category divided by the total street segment length within each Thiessen Polygon. These ratios were multiplied by a thousand to convert the rates into crimes per kilometre. As part of this process, all individual streets within each Thiessen Polygon were combined into a single feature, otherwise rates would appear artificially high on those composite street segments with shorter lengths as denominators would be smaller. Furthermore, given that information about which streets crimes were actually located on was lacking, the re-appropriation of the point data back into the zonal geography should only be used to apply styles to the whole Thiessen Polygon zone, again to avoid those issues of spurious precision that are exhibited by the point data.

The crime attributed street network data and rates were stored and processed within the PostGIS database. For display, these data were coupled with the map-rendering engine Mapnik11 11 See http://mapnik.org/
that enabled the generation of map tiles with custom cartography. Using OpenLayers12 12 See http://openlayers.org/
as a map interface, new cartography was developed and displayed on top of a neutral feature background map.

Two cartographic options were enabled to reflect the rates of crime: the first scaled the widths of the street network (see Figure 3a), and the second altered the street network by colour intensity (see Figure 3b). With regard to colour selection, a ColorBrewer Yellow-Orange-Red sequential nine step colour ramp was chosen for its aesthetic appeal and accessibility (Harrower and Brewer 2003 ). The purpose of showing different visualisation was to enable these to be evaluated by stakeholders at a later stage, enabling different styling options to be easily demonstrated. The ability to adapt cartographic styles, including other advanced features such as the selection of a scaling factor to adjust line widths or colour intensity, was only available on the full map view. We argue that in both the line width and coloured street cartographic styles, these representations hold greater utility for interpretation than the display of points, and convey the lack of spatial accuracy due to disclosure control in a more appropriate way. At present the policestreets.co.uk website excludes those crimes that were recorded at those non-street centroids that were more recently added to the police.uk source data. These could however be integrated into the representation by aggregation into a revised Thiessen polygon geography, or, more appropriately, visualised as either points, lines or polygons, depending on the nature of the recorded feature.

Alternative cartography on policestreets.co.uk. (a) Line scaling. (b) Line colour

When a user visits policestreets.co.uk, search is enabled by input of a full postcode, and the initial screen shown incorporates a more limited map view, highlighting a mile radius around the searched postcode (Figure 4). In addition to the map, those crime points falling within a one-mile radius of the postcode are aggregated for a rolling six-month interval, and tabulated according to absolute crimes by type per month. A trend rate is calculated by comparing the first and latter three months to give an indication of change over the course of the six-month period. Pink to green colours are also used to indicate the directionality and intensity of the percentage change. The limited map view enables the display of different crime types and durations. Furthermore, when the ‘slippy map’ is moved, the change of focus is detected and the user is asked whether they wish to refresh the table of results. In addition to the crime data, a call is sent to the police.uk API13 13 See http://data.police.uk/docs/
with a request for the contact details of the neighbourhood policing team who are responsible for the searched area with the purpose of stimulating greater public engagement. This feature could be expanded in the future to incorporate an emailing system that might extract some statistics from the website, enabling stakeholders to send these to the neighbourhood policing team alongside further commentary related to the observed patterns, thus providing a community-based contribution to Problem Oriented Policing (Goldstein 1979 1979 ), where policing attention is encouraged to focus on underlying causes of events rather than the servicing of individual callouts viewed in isolation.

Search results showing the limited map view alongside the change analysis table


Videoni tomosha qiling: Лучший мобильный браузер UC Browser Turbo - Быстрая загрузка, тест скорости, скачать любое видео (Oktyabr 2021).