Does DEGURBA combine too many cities into a single conurbation?
In countries where population data were only available at relatively coarse resolution and densities are generally high, these estimates may include conurbation that are too large. For example, the DEGURBA-defined city that includes Hajipur in India appears to aggregate multiple distinct cities and towns. Using finer grained population data or even better a population grid based on a geo-coded census may lead to this conurbation shrinking and turning into a multitude of individual cities and towns.
The following online portal provides you more details: https://human-settlement.emergency.copernicus.eu/raster.php - Based on this methodology, Hajipur corresponds to the whole red urban centre combining multiple contiguous urban units. If you zoom on the interactive map you'll see the name of smaller urban places included. For the most recent periods, the initial units of analysis for the population grid were the 5,967 Sub-districts/Tehsils/Cercles of the 2011 census of India projected using the 2001-2011 censuses. Population distribution is downscaled using estimates of building volume from the GHSL, which you can see here: https://human-settlement.emergency.copernicus.eu/visualisati...
You can see that Patna is the larger/closest urban area, but it is not physically connected to the rest of the urban area due to the river in between. SO Patna appears as distinct urban area.
They will have to support auth if they are adding support for connecting with remote host. It's not difficult but it's not as trivial as you suggested.
A very good list. You should add https://github.com/nchudleigh/vimac to the list. It works similar to shortcat but I found Vimac to be more performant and reliable.
I used to use vimac (https://github.com/nchudleigh/vimac) when I had macbook. I was pretty happy with it. I liked its interface. Its interface was inspired by Vimium extension on browser.
There are browser extensions which make it easier to debug grapgql. A new pane is added to the browser debug panel. Last I used them more than two years ago, it was still not as good as the built-in network tab for rest queries. Still better than the default for the graphql queries.
An interesting use-case could be localized haptic feedback on the screen. You could rotate a knob or push a button on the screen and get a localized sound and haptic feedback from the item on the screen.
You may even add haptic texture on the screen. close your eyes and scan the screen with your finger. It would feel like a series of mechanical switches and knobs. It would be useful for people who don't like using only the screen in their car because of lack of haptic feedback.
If you want even faster search across different formats, you can try ripgrep-all ( https://github.com/phiresky/ripgrep-all ). It can search across epub, docx, pdf, zip, mp4 etc. If you are handy with the tool, you can write custom adaptor to search across images using OCR with tesseract.
I have used HTMX with Flask and Jinja. It makes the process much simpler to do the frontend development as a backend developer. But I can see its limitations. It's not suitable for anything bigger than a hobby project. Also, it doesn't help with keeping the frontend and the api totally separate. You have to return the html object from API which has its own set of problems.
Usually there are a lot of comments about how text is the best interface and it's making a comeback in the LLMs but in this case picture is the better medium since parsing the webpage js would prove too difficult. I think a screenshot of a webpage has a smaller footprint than the raw payloads (js, assets, etc.).
I think this can be extended to desktop as well. There are programs that act like vimium for your desktop (win-vind, etc.). I don't have the openai API key to try it but I wish someone gave it a try (in obviously an isolated environment).
Have you tried lnav? It has somewhat steeper learning curve but it'd fit the bill. One small binary and some log parsing config, and you are good to go.
>Thanks for your email. In our online FAQ for the DEGURBA methodology (https://population.un.org/wup/faqs), you'll see:
Does DEGURBA combine too many cities into a single conurbation?
In countries where population data were only available at relatively coarse resolution and densities are generally high, these estimates may include conurbation that are too large. For example, the DEGURBA-defined city that includes Hajipur in India appears to aggregate multiple distinct cities and towns. Using finer grained population data or even better a population grid based on a geo-coded census may lead to this conurbation shrinking and turning into a multitude of individual cities and towns.
The following online portal provides you more details: https://human-settlement.emergency.copernicus.eu/raster.php - Based on this methodology, Hajipur corresponds to the whole red urban centre combining multiple contiguous urban units. If you zoom on the interactive map you'll see the name of smaller urban places included. For the most recent periods, the initial units of analysis for the population grid were the 5,967 Sub-districts/Tehsils/Cercles of the 2011 census of India projected using the 2001-2011 censuses. Population distribution is downscaled using estimates of building volume from the GHSL, which you can see here: https://human-settlement.emergency.copernicus.eu/visualisati...
You can see that Patna is the larger/closest urban area, but it is not physically connected to the rest of the urban area due to the river in between. SO Patna appears as distinct urban area.