GIS

GIS

90 bookmarks
Custom sorting
Geospatial API Fundamentals
Geospatial API Fundamentals
Geospatial APIs enable seamless access to spatial data, powering mapping, analysis, and urban analytics with standardized operations and protocols.
Geospatial APIs are software abstraction layers that provide standardized methods to query, analyze, and visualize spatial data from diverse sources. They support essential functionalities including 2D/3D map rendering, geocoding, coordinate transforms, and real-time sensor data integration. Modern designs employ RESTful architectures and OGC standards to enhance interoperability, performance, and scalability across geospatial applications.
A geospatial Application Programming Interface (API) is a software abstraction layer—typically a web service or client library—that exposes standardized operations for querying, rendering, analyzing, and modeling spatial data, including vector features, raster coverages, multi-dimensional sensor observations, and geospatial attributes. Geospatial APIs are foundational for scientific computing, urban analytics, planetary research, public health surveillance, and geospatial-AI workflows, enabling programmable access to distributed spatial resources and seamless integration across data repositories, sensor infrastructures, visualization platforms, and analytic pipelines.
·emergentmind.com·
Geospatial API Fundamentals
Adopting semantic types - Taxi
Adopting semantic types - Taxi
Learn how Taxi uses semantic typing to describe the meaning of data, not just its structure
Types are meant to be shared across systems, while models are system-specific. Your project structure should reflect this separation.
A well-implemented Taxi ecosystem has clear separation between shared semantics and system-specific implementations.
A mature implementation typically includes: ​ Shared Taxonomy Collection of semantic types Broadly shared across organization Version controlled and carefully governed Published as a reusable package ​ Service Implementations Models and service definitions using types from taxonomy System-specific structures Published to TaxiQL server (like Orbital) Each service depends on shared taxonomy ​ Data Consumers Import shared taxonomy only Don’t depend on service-specific models Query data using TaxiQL Receive data mapped to their needs ​
Best Practices ​ Type Development Focus on business concepts Keep types focused and single-purpose Document type meanings clearly Version types carefully ​ Model Development Use semantic types for fields Keep models service-specific Don’t share models between services ​ Service Integration Publish service contracts to TaxiQL server Use semantic types in operation signatures Let TaxiQL handle data mapping
Measuring Success Your implementation is successful when: Services can evolve independently Data integration requires minimal code New consumers can easily discover and use data Changes to one service don’t cascade to others Semantic meaning is preserved across systems
·taxilang.org·
Adopting semantic types - Taxi
rspatialdata
rspatialdata
·rspatialdata.github.io·
rspatialdata
Production PostGIS Vector Tiles: Caching | Crunchy Data Blog
Production PostGIS Vector Tiles: Caching | Crunchy Data Blog
Building maps that use dynamic tiles from the database is a lot of fun. You get the freshest data, you don't have to think about generating a static tile set, and you can do it with very minimal middleware, using pg_tileserv.
·crunchydata.com·
Production PostGIS Vector Tiles: Caching | Crunchy Data Blog
pg_featureserv
pg_featureserv
Because there are usually many functions in a Postgres database, the service only publishes functions defined in the schemas specified in the FunctionIncludes configuration setting. By default the functions in the postgisftw schema are published.
·access.crunchydata.com·
pg_featureserv
Spatial Parallel Computing by Hierarchical Data Partitioning
Spatial Parallel Computing by Hierarchical Data Partitioning
Geospatial data computation is parallelized by grid, hierarchy, or raster files. Based on future (Bengtsson, 2024 doi:10.32614/CRAN.package.future) and mirai (Gao et al., 2025 doi:10.32614/CRAN.package.mirai) parallel back-ends, terra (Hijmans et al., 2025 doi:10.32614/CRAN.package.terra) and sf (Pebesma et al., 2024 doi:10.32614/CRAN.package.sf) functions as well as convenience functions in the package can be distributed over multiple threads. The simplest way of parallelizing generic geospatial computation is to start from par_pad_*() functions to par_grid(), par_hierarchy(), or par_multirasters() functions. Virtually any functions accepting classes in terra or sf packages can be used in the three parallelization functions. A common raster-vector overlay operation is provided as a function extract_at(), which uses exactextractr (Baston, 2023 doi:10.32614/CRAN.package.exactextractr), with options for kernel weights for summarizing raster values at vector geometries. Other convenience functions for vector-vector operations including simple areal interpolation (summarize_aw()) and summation of exponentially decaying weights (summarize_sedc()) are also provided.
·docs.ropensci.org·
Spatial Parallel Computing by Hierarchical Data Partitioning
VRT -- GDAL Virtual Format — GDAL documentation
VRT -- GDAL Virtual Format — GDAL documentation
The VRT driver is a format driver for GDAL that allows a virtual GDAL dataset to be composed from other GDAL datasets with repositioning, and algorithms potentially applied as well as various kinds of metadata altered or added. VRT descriptions of datasets can be saved in an XML format normally given the extension .vrt.
·gdal.org·
VRT -- GDAL Virtual Format — GDAL documentation
gdalbuildvrt — GDAL documentation
gdalbuildvrt — GDAL documentation
gdalbuildvrt [--help] [--long-usage] [--help-general] [--quiet] [[-strict]|[-non_strict]] [-tile_index <field_name>] [-resolution user|average|common|highest|lowest|same] [-tr <xres> <yes>] [-input_file_list <filename>] [[-separate]|[-pixel-function <function>]] [-pixel-function-arg <NAME>=<VALUE>]... [-allow_projection_difference] [-sd <n>] [-tap] [-te <xmin> <ymin> <xmax> <ymax>] [-addalpha] [-b <band>]... [-hidenodata] [-overwrite] [-srcnodata "<value>[ <value>]..."] [-vrtnodata "<value>[ <value>]..."] [-a_srs <srs_def>] [-r nearest|bilinear|cubic|cubicspline|lanczos|average|mode] [-oo <NAME>=<VALUE>]... [-co <NAME>=<VALUE>]... [-ignore_srcmaskband] [-nodata_max_mask_threshold <threshold>] <vrt_dataset_name> [<src_dataset_name>]...
This program builds a VRT (Virtual Dataset) that is a mosaic of a list of input GDAL datasets. The list of input GDAL datasets can be specified at the end of the command line, put in a text file (one filename per line) for very long lists, or it can be a MapServer tileindex (see the gdaltindex utility). If using a tile index, all entries in the tile index will be added to the VRT.
·gdal.org·
gdalbuildvrt — GDAL documentation
Farm
Farm
Investing in farmland regeneration.
·farm.vc·
Farm
Topographic Map Colors - Coolors
Topographic Map Colors - Coolors
Get inspired by these beautiful i-am-looking-for-colors-for-topographic-maps color schemes and make something cool!
·coolors.co·
Topographic Map Colors - Coolors
Maps Color Palettes - Coolors
Maps Color Palettes - Coolors
Get inspired by thousands of beautiful color schemes and make something cool!
·coolors.co·
Maps Color Palettes - Coolors
7 Geospatial Data Visualization – Geospatial Data Science with R
7 Geospatial Data Visualization – Geospatial Data Science with R
Emphasizing clarity, accuracy, and purpose-driven design, the guide covers how to create compelling static and interactive visualizations tailored to diverse analytical and communicative objectives. Throughout, we will adhere to best practices in cartographic design to ensure that each visualization conveys its intended message clearly and truthfully.
Successful geospatial visualization demands attention to several core principles that ensure the resulting map or graphic is both informative and comprehensible. Visualizations must balance aesthetic considerations with functional accuracy to effectively convey spatial information.
Clarity and Simplicity Clarity in geospatial visualization means the core message of a map is immediately apparent to viewers. Overloading a map with too much information or too many design elements can confuse rather than enlighten. Designers should strive for minimalism—include only the critical spatial features and data relevant to the map’s purpose. An expert data visualization principle is to “remove any elements that do not contribute to understanding the data”, such as excessive labels, grid lines, or decorative clutter. By simplifying the visual display, we direct the audience’s attention to the most important patterns or locations. Key guidelines for simplicity include: Limit the number of thematic layers shown on a single map. Use intuitive symbols and clear labeling for features. Avoid excessive annotation or unnecessary visual noise. In practice, a clean design with ample white space and straightforward symbology will enhance comprehension and engagement. The goal is a map that communicates rather than overwhelms.
Appropriate Color Schemes: Choose color palettes that are perceptually uniform and appropriate for the data. Avoid using arbitrary or excessively bright colors that could mislead or cause eye strain. Instead, use scientifically derived colormaps like viridis or plasma, which are designed to be uniform and colorblind-friendly. For example, a sequential palette (light to dark in one hue) makes sense for a unipolar data range (e.g., population density), whereas a diverging palette (two hues fading to a neutral midpoint) is best for data that have a meaningful center (e.g., above/below average comparisons). Ensure that the colors have sufficient contrast against each other and the map background for readability – legend text and boundary lines should also be clearly visible. (A poorly chosen palette or low-contrast colors can render a map useless to colorblind viewers or even to those in print vs. screen viewing.) Maintain consistency in color use across multiple maps; if one map shows intensity of something in red, another map in the report should ideally use red for that same intensity concept.
Clear Legends and Annotations: Provide explanatory legends, titles, and annotations to guide the viewer. A well-crafted legend is crucial for interpreting a map’s symbology – it should be clear, concise, and not overly cluttered. Viewers should not struggle to match colors or symbols to their meaning. As a cartography guide points out, a confusing legend can undermine your visualization, whereas a clear legend “guides [readers] seamlessly through your data story”. Tips include: place the legend in an unobtrusive but noticeable location (often corners work well), use intuitive labels (e.g., “Population (millions)” rather than “Pop_val”), and avoid too many categories. Additionally, titles and subtitles are important: they frame what the map is about. A good title might state the what/where/when (e.g., “Population Distribution by Region, 2020”) so the audience immediately knows the context. Annotations like callout labels or arrows can highlight key insights (e.g., “Area X has the highest value”). However, avoid excessive text on the map itself; maintain a balance so the map doesn’t become a textbook diagram unless that’s intended. The goal is to inform without overwhelming.
·warin.ca·
7 Geospatial Data Visualization – Geospatial Data Science with R
ColorBrewer: Color Advice for Maps
ColorBrewer: Color Advice for Maps
1. Sequential schemes are suited to ordered data that progress from low to high. Lightness steps dominate the look of these schemes, with light colors for low data values to dark colors for high data values.
X TYPES OF COLOR SCHEMES 1. Sequential schemes are suited to ordered data that progress from low to high. Lightness steps dominate the look of these schemes, with light colors for low data values to dark colors for high data values. 2. Diverging schemes put equal emphasis on mid-range critical values and extremes at both ends of the data range. The critical class or break in the middle of the legend is emphasized with light colors and low and high extremes are emphasized with dark colors that have contrasting hues.
3. Qualitative schemes do not imply magnitude differences between legend classes, and hues are used to create the primary visual differences between classes. Qualitative schemes are best suited to representing nominal or categorical data.
The appearance and robustness of a color scheme is in part a product of what else goes on the map and the background over which you are trying to show your colors. Small differences in the color of linework or the presence of other map items (like labels) really has a big impact on the appearance of a color scheme, so be sure to try these options here before settling on a final color scheme. Overlay cities and roads for a first look at how well text and symbols can be read with the area colors you select. Though the examples we have chosen are highways and cities, they should give you a good idea of how other linework or typography will function on the map. We have also provided a grayscale DEM so you can see what happens to your colors when you combine them with other underlying map data: Generally speaking, colors become harder to distinguish and you will need to user fewer classes of data.
TIP: Try turning off the county borders or making them white; notice a big difference? Try changing the background surrounding the map to see how colors are changed by their surroundings.
Choosing the number of data classes is an important part of map design. Increasing the number of data classes will result in a more "information rich" map by decreasing the amount of data generalization. However, too many data classes may overwhelm the map reader with information and distract them from seeing general trends in the distribution. In addition, a large numbers of classes may compromise map legibility—more classes require more colors that become increasingly difficult to tell apart. Many cartographers advise that you use five to seven classes for a choropleth map. Isoline maps, or choropleth maps with very regular spatial patterns, can safely use more data classes because similar colors are seen next to each other, making them easier to distinguish.
·colorbrewer2.org·
ColorBrewer: Color Advice for Maps
OpenFreeMap
OpenFreeMap
OpenFreeMap – Open-Source Map Hosting lets you display custom maps on your website and apps for free.
·openfreemap.org·
OpenFreeMap
Home
Home
Pixi Documentation — Next-gen package manager for reproducible development setups
·pixi.prefix.dev·
Home
ArcGIS Hub
ArcGIS Hub
Discover, analyze and download data from ArcGIS Hub. Download in CSV, KML, Zip, GeoJSON, GeoTIFF or PNG. Find API links for GeoServices, WMS, and WFS. Analyze with charts and thematic maps. Take the next step and create StoryMaps and Web Maps.
·atlas.eia.gov·
ArcGIS Hub
MassGIS Data Layers
MassGIS Data Layers
Each digital dataset name below links to a complete data layer description. On each page you will find metadata and links to free data downloads.
·mass.gov·
MassGIS Data Layers
Landscape Visualizations in R and Unity
Landscape Visualizations in R and Unity
Functions for the retrieval, manipulation, and visualization of geospatial data, with an aim towards producing 3D landscape visualizations in the Unity 3D rendering engine. Functions are also provided for retrieving elevation data and base map tiles from the USGS National Map https://apps.nationalmap.gov/services/.
·docs.ropensci.org·
Landscape Visualizations in R and Unity
Accessing Data in Cloud-Optimized GeoTIFFs (COGs) with terra in R – Cloud-Optimized Geospatial Formats Guide
Accessing Data in Cloud-Optimized GeoTIFFs (COGs) with terra in R – Cloud-Optimized Geospatial Formats Guide
Cloud-Optimized GeoTIFFs (COGs) are a specialized format of GeoTIFF designed to enable efficient access to raster data, particularly in cloud environments. By organizing data into tiled structures and enabling partial reads, COGs allow users to fetch only the portions they need, significantly reducing bandwidth and storage costs
·guide.cloudnativegeo.org·
Accessing Data in Cloud-Optimized GeoTIFFs (COGs) with terra in R – Cloud-Optimized Geospatial Formats Guide