Explore a Portland site context
Build a site-context figure from real OpenStreetMap features around a reference coordinate in Portland. Transit platforms, education locations, parks and retail form four independent layers inside a 900 metre straight-line reference area. Toggle categories, inspect source records and open the example in Studio to prepare your own annotated report workflow.
Start an editable copy with this data and your current map styling.
Public OSM POI snapshot · ODbL 1.0
Data: selected public OpenStreetMap POIs, retrieved 2026-10-25. Portland upstream snapshot: 2026-05-31T22:37:44Z. The source date is retained in the downloadable data and each popup. Named features are selected nearest-first within 900 m, with at least 100 m between selected features of the same category and a per-category display cap. This is an incomplete, dated cartographic snapshot, not a field survey or a current directory. Area features use bounding-box centers from the public source geometry. The reference circle is a straight-line distance, not a walkshed, road accessibility result or proposed development site.
Start with the example data
Download the input files, inspect their sources and sample fields, then import them or open the styled example in Studio.
- Download public POI GeoJSON
The selected public features with category, OSM record link and original data timestamp.
- Download public POI CSV
A directly importable table with names, categories and coordinates.
- Download 900 m reference area
The derived straight-line reference circle used in the example.
What to look at
- Transit, education, parks and retail can be toggled independently without replacing the basemap.
- Each feature carries a public OSM identity and the source snapshot date rather than an invented business record.
- Download the GeoJSON or CSV, check the source information, then replace or supplement it with your own reviewed site data.
Source columns
These fields describe the example data. CSV and Excel use first-row headers; GIS formats store geometry and feature properties. Required geometry depends on the map type.
| Column | Type | Example |
|---|---|---|
| name | text | Public OSM place name |
| category | category | transit / education / parks / retail |
| source_url | URL | https://www.openstreetmap.org/node/… |
| source_date | timestamp | Source snapshot or retrieval date |
| distance_m | number | Straight-line distance from reference |
Rebuild it with your own data
- 1
Get your GeoJSON file ready
The example fields are name, category, source_url, source_date, distance_m. For CSV or Excel, put headers in the first row. GIS files carry geometry and feature properties. Prepare any grid, catchment or route geometry before import.
- 2
Drop it into the studio
MapCrafter detects the geometry, counts the features, and shows the layers it found.
- 3
Style the imported layer
Pick which column drives colour, and which drives size or width where relevant.
- 4
Pick a basemap theme
Positron is used here. 15 other basemaps are available, including official OpenFreeMap styles. Switch using Layers & basemap.
- 5
Share or export
Publish a link, embed the map, or export a PNG at print resolution.
Questions about this example
- What file format does this public site context use?
- This example illustrates GeoJSON data. The live preview uses GeoJSON geometry. MapCrafter reads GeoJSON directly, along with Excel, CSV, KML, KMZ, GPX, GeoJSON, TopoJSON and zipped Shapefile. No conversion step and no desktop software.
- What columns does the source data need?
- The file used here has 5 columns: name, category, source_url, source_date, distance_m. For tabular imports, supply coordinate columns, WKT or GeoJSON geometry, or address columns for an explicit geocoding step. Polygon and line files carry their geometry separately from these attributes.
- Can I use my own data with this map type?
- Yes. Open the studio, drop in your file, and MapCrafter detects the geometry and applies a starting style. Then style the layer and choose which property drives colour, size or width. The studio can render a point heatmap, but grids, routes and catchment polygons must be prepared before import.
- Can I export or share the finished map?
- Each map can be published to a short share link, embedded in another page with an iframe, or exported as a print-resolution PNG. The cleaned-up geometry can also be exported as GeoJSON. All of that is available on the free tier.
- Where does the data in this example come from?
- Data: selected public OpenStreetMap POIs, retrieved 2026-10-25. Portland upstream snapshot: 2026-05-31T22:37:44Z. The source date is retained in the downloadable data and each popup. Named features are selected nearest-first within 900 m, with at least 100 m between selected features of the same category and a per-category display cap. This is an incomplete, dated cartographic snapshot, not a field survey or a current directory. Area features use bounding-box centers from the public source geometry. The reference circle is a straight-line distance, not a walkshed, road accessibility result or proposed development site.
More pin maps examples
Gallery (322)- GeoJSONExplore a Seattle site contextBuild a site-context figure from real OpenStreetMap features around a reference coordinate in Seattle. Transit platforms, education locations, parks and retail form four independent layers inside a 900 metre straight-line reference area. Toggle categories, inspect source records and open the example in Studio to prepare your own annotated report workflow.
- CSVA bathymetric survey gridSquare cells for a survey where the measurement grid itself is square. Squares are the honest choice when the sampling geometry is square; hexagons are the honest choice when it is not. The grid should look like the method.
- CSVA tree inventory as a categorical point mapPoint data coloured by species category. Categorical colour is the hardest palette to get right: two categories that look alike are not a cosmetic problem, they are two categories the reader will merge into one.
Last updated 2026-10-25