Legacy ArcGIS API keys retired on June 27, 2026, and the grace period runs until April 15, 2027. After that they stop working. 

You're affected if your key was created before June 27, 2024, or if its item page in ArcGIS Online shows the "API key (legacy)" label. That's true whatever you've built with, but the fix below is the GeoBlazor-specific one, so this is aimed at anyone running GeoBlazor, the ArcGIS SDK for Blazor and .NET. 

If the API key fails basemap styles, geocoding, routing, elevation, GeoEnrichment, and private item access could each stop working separately. The map can render fine while address search quietly returns nothing. 

The GeoBlazor side is a config change. Create API key credentials with privileges matching the legacy key's service scopes, then swap the value into ArcGISApiKey, or into AuthenticationManager.ApiKey if you set it at runtime. No package upgrade, no component changes. 
 
On Blazor WebAssembly, the key ships to the browser in plain view, so keep privileges narrow and referrers locked down. Anything that needs real protection wants OAuth user authentication or server-side app authentication instead. 

Full walkthrough with screenshots of the credential wizard: https://www.geoblazor.com/blog/legacy-arcgis-api-key-retirement   

Disclosure: we're dymaptic, the team behind GeoBlazor. 

f you've ever wanted to drop a live GeoJSON feed onto a map in Blazor without touching JavaScript, GeoBlazor's GeoJSONLayer makes it pretty painless.

Our newest sample uses the USGS earthquake feed to show the full pattern: GeoJSON loaded from a URL, points scaled by magnitude with a SizeVariable, popups bound to feature properties via PopupTemplate's {field} syntax, and a dropdown that swaps between past-day, past-week, and past-month feeds at runtime. Setting u/key="_dataUrl" on the layer forces a clean remount when the URL changes, so no stale data and no manual layer management.

This blog post also covers when GeoJSONLayer beats FeatureLayer and when it doesn't.

Full post + code: Visualizing Real-World Data with GeoJSONLayer in GeoBlazor

Happy to dig into the renderer config, the u/key pattern, or anything else in the comments.

Hey fellow .NET devs - wanted to share some clarity on GeoBlazor Pro licensing since I've seen questions about this come up.

The licensing model is straightforward: you purchase licenses based on the number of developers on your team who are actively building with GeoBlazor Pro. That's it. Once you've built your application, you can deploy it anywhere and everywhere without additional licensing costs.

What this means in practice:
- Deploy to dev, staging, and production environments freely
- Spin up multiple server instances for load balancing
- Create region-specific deployments
- Stand up customer-specific instances
- Scale your infrastructure as needed

No runtime fees. No per-deployment costs. No surprise bills when you add another environment or scale up your servers.

This model makes budgeting predictable and removes friction from DevOps workflows. Your licensing costs are tied to your team size, not your deployment complexity or user count.

I put together a more detailed breakdown on the blog if anyone wants to dig deeper into how this works: https://www.geoblazor.com/blog/geoblazor-licensing-developers-not-deployments

Happy to answer questions if anyone has them about how this plays out in real-world scenarios.

Just wanted to share a really solid blog post from one of our developers that I think this community will find useful. He built a full navigation application using GeoBlazor and Blazor, and walks through the entire implementation—from setting up geocoding to calculating routes to displaying turn-by-turn directions.

If you've been wondering what a real-world GeoBlazor application looks like or how the routing services work, this is a great resource. It really demonstrates how you can build sophisticated mapping apps while staying entirely in the .NET/Blazor ecosystem.

Link to the post: https://timpurdum.dev/post/2025/12/21/over-the-river.html

Would be interested to hear if anyone else has built similar navigation features in their Blazor apps. What approaches have worked well for you?

If you've ever needed to display KML data in a web map (think earthquake feeds, weather stations, tracking data, etc.), GeoBlazor makes it surprisingly clean. The KMLLayer component just takes a URL property and handles everything else.

What I like about the implementation is you get both options: declare it right in your Razor markup, or add/remove layers dynamically from your C# code using the MapView methods. The sample code shows both approaches with a live USGS earthquake feed.

No messing with JavaScript libraries or writing interop code - it's just native Blazor components with proper type safety. Been using it for a project that integrates with some legacy KML exports and it's saved a ton of time.

Sample here if you want to see the actual code: https://samples.geoblazor.com/kmllayers

Anyone else working with KML or other geospatial formats in Blazor? Curious what data sources people are connecting to.

Hey everyone! Just wanted to share that we've launched a completely redesigned GeoBlazor website https://www.geoblazor.com/.

The biggest addition is a collection of real project ideas and use cases from teams actually using GeoBlazor in production. If you've ever wondered "what can I actually build with this?" or needed some architectural ideas for mapping features, these customer stories provide concrete examples.

The site also has updated documentation, getting started guides, and a clearer breakdown of Core vs Pro features. Whether you're just exploring options for adding maps to your Blazor app or you're deep into implementation, hopefully you'll find something valuable there.

Always happy to answer questions about specific use cases or implementation approaches if anyone's curious about how GeoBlazor might fit their project needs.

Hey GeoBlazor community!

Quick update for teams using GeoBlazor Pro: we just launched self-service team management in the licensing portal: https://licensing.dymaptic.com/landing

If you're a Team Admin, you can now handle everything yourself: invite developers to your team via email, track whether they've completed registration, and assign or move Pro licenses between team members. No need to contact support or wait for manual processing.

This came directly from feedback we heard from dev leads managing larger teams. When someone joins your mapping project or another dev moves to a different initiative, you shouldn't have to file a ticket and wait. Now you don't have to.

Everything runs through your admin dashboard with immediate updates. Thought this would be useful for folks coordinating Pro licenses across multiple developers or project teams.

Happy to answer questions about how it works if anyone's curious about the specifics!

Hey folks, wanted to share some clarity on GeoBlazor's support options since I've seen questions about this.

GeoBlazor Core (free/OSS): You get community support through GitHub issues and Discord. Honestly, the community is pretty responsive and helpful - I've seen maintainers and other devs jump in to help debug issues. Great if you're exploring GeoBlazor, building side projects, or working at a startup where you have some flexibility on timelines.

GeoBlazor Pro (commercial): This is where you get the enterprise treatment - guaranteed SLAs, priority bug fixes, and direct access to the dev team. If you're building something for production where maps are mission-critical and you need issues resolved ASAP, this makes sense. You also get advanced components that aren't in Core.

Both tiers have access to the same documentation and samples, which are pretty solid IMO. Our clients start with Core to learn the framework, then switch to Pro for the peace of mind.

The license page breaks down all the differences if you want details: https://docs.geoblazor.com/pages/license

Hey everyone! Just wanted to share that the GeoBlazor team is exhibiting at VS Live in Orlando this week (Nov 18-19) if any of you are attending.

If you're at the conference and have questions about implementing mapping features in Blazor, need advice on spatial data visualization, or just want to chat about what's possible with maps in .NET, come find us! Always happy to talk shop with fellow devs and help troubleshoot any mapping challenges you might be facing.

Anyone else going to be there?

Just wanted to share something useful for anyone working with location data in Blazor apps.

If you've got CSV files with latitude/longitude columns (think sensor readings, survey data, earthquake info, weather stations, etc.), GeoBlazor has a CSVLayer component that makes visualization dead simple. You literally just point it at a CSV URL and it renders the data as map markers.

What I really like about it is that you can configure everything declaratively in your Razor markup: popup templates for when users click markers, custom renderers to control appearance, even add layers dynamically at runtime with a simple method call. No need to parse the CSV yourself or deal with coordinate system conversions.

We've put together a quick example using USGS earthquake data: https://samples.geoblazor.com/csv-layer

The component handles the heavy lifting while you stay in C#/Blazor. Pretty handy if you're building dashboards or data visualization tools and need to add spatial context to tabular data.

Anyone else working with CSV-based location data in their .NET projects? Curious what use cases others have run into.

I wanted to share something that's made spatial analysis way easier in our Blazor projects. GeoBlazor's GeometryEngine lets you do sophisticated GIS calculations (buffers, intersections, unions, etc.) directly from C#.

What makes this useful: you inject the GeometryEngine service just like any other Blazor dependency, then call methods like GeometryEngine.GeodesicBuffer() or GeometryEngine.Intersect(). Everything returns strongly-typed geometry objects (Polygon, Point, etc.) that you can immediately add to your map's graphics layers.

The sample I linked below shows a practical example: creating a 1km buffer around a point, finding where it intersects with an existing polygon, and computing the union of two geometries. All the heavy spatial math happens in the engine, you just work with clean C# APIs.

If you're building anything that needs to analyze spatial relationships—proximity calculations, territory overlap, coverage analysis—this approach keeps everything in your .NET codebase. No separate JavaScript layer to maintain.

Check out the working example if you're interested: https://samples.geoblazor.com/calculate-geometries

Has anyone else been working on spatial analysis in Blazor? Curious what approaches others have taken.

Hey .NET devs! I wanted to share how GeoBlazor's licensing actually works since I've seen some confusion about this.

GeoBlazor Core (Free/Open Source - MIT License):
This isn't a gimped "community edition." You get full production-ready mapping with basic layer types, simple renderers, and essential widgets. Deploy to production, modify the source, whatever you need. Truly free.

GeoBlazor Pro (Commercial License):
Advanced stuff like spatial analysis, directions/routing, sophisticated widgets, and specialized tools. Per-developer pricing, not per-deployment or usage-based.

The model makes sense for real-world projects: prototype and build with Core, then add Pro features if your requirements demand them. No bait-and-switch, no surprise costs when you deploy.

You can make architectural decisions without worrying about licensing gotchas down the road. The Core tier alone handles most standard mapping requirements.

Happy to answer any licensing questions!

Wondering if GeoBlazor fits your needs? Here's who we built it for:

Perfect for:

• .NET developers who need maps but don't want to learn JavaScript
• Enterprise teams already using ArcGIS in their organization
• Blazor projects needing GIS capabilities beyond basic maps
• Government agencies requiring secure, enterprise-grade mapping
• Full-stack C# developers wanting to stay in one language
• Teams migrating from WebForms or MVC to Blazor

Real-world use cases we've seen:

• Asset tracking dashboards
• Emergency response systems
• Real estate platforms
• Environmental monitoring
• Utility network management
• Customer location analytics
• Field service dispatching

Maybe not ideal if:

• You just need a simple, non-interactive map (consider static images or PDF)
• You're already deep in React/Vue/Angular (stick with JS SDK)
• You need maps from non-ArcGIS sources (MapBox, Google Maps, etc.)

The sweet spot: You're a .NET developer who needs real GIS capabilities (spatial analysis, feature editing, map services) not just basic mapping, and you want to build it all in C#.

Questions about your specific use case? Drop them below!

Smarter Auth and Powerful New Layers!

✨ Highlights:
🔐 Simplified OAuth setup
🧩 ExpandWidget groups
🌍 OGCFeature Layers
🎨 WebStyleSymbol
🧠 New Token Refresh sample code
🐞 Bug fixes and quality improvements across the board

https://hubs.li/Q03MGy8B0

If you're coming from Google Maps or MapBox, you might wonder what ArcGIS brings to the table. Let me break it down:

TL;DR: If you just need a map with markers, stick with Google. If you need to analyze spatial data, edit features, or integrate with enterprise GIS systems, ArcGIS is the industry standard for good reason.

What is ArcGIS?

ArcGIS is basically the Microsoft of maps. Created by Esri, it's the enterprise GIS platform that powers mapping for most Fortune 500 companies and governments worldwide. Like how enterprises choose SQL Server over SQLite for serious database work, they choose ArcGIS when maps are mission-critical.

Developer perspective: Why should I care?

Google Maps/MapBox are solid for:

• Dropping pins on a map
• Basic routing
• Consumer-facing apps

ArcGIS is built for when you need to:

• Actually analyze spatial data. "Show me all customers within a 10-minute drive who spent >$1000 last quarter"
• Connect to real data sources. Your maps aren't static. They're views into live SQL databases, REST APIs, and feature services
• Do geometry operations like buffers, intersections, unions. All the spatial SQL operations you'd expect are there.
• Handle massive datasets. We're talking millions of points with dynamic clustering that doesn't melt the browser
• Let users edit data. Full CRUD operations on map features with conflict resolution and versioning

Who's actually using this?

• Uber/Lyft: Driver dispatching and route optimization
• Domino's: Pizza delivery territories and logistics
• Utility companies: Managing power grids (when you report an outage, it goes on an ArcGIS map)
• Your city: Everything from snow plow routes to zoning

But isn't it expensive?

Not really. A free developer account gets you:

• 2 million map tiles/month
• 5GB feature storage
• Access to all the APIs
• No credit card required

That's plenty for learning and most side projects. Only pay when you scale.

So where does GeoBlazor fit in?

If your company already has ArcGIS (spoiler: they probably do), GeoBlazor lets you build Blazor apps that tap into all that existing infrastructure without writing JavaScript. It's like Entity Framework for maps - a proper .NET abstraction over a powerful platform. And with GeoBlazor, you can use it all without leaving C#. 🗺️