dymaptic.GeoBlazor.Core 3.0.1

.NET 6.0 
dotnet add package dymaptic.GeoBlazor.Core --version 3.0.1
NuGet\Install-Package dymaptic.GeoBlazor.Core -Version 3.0.1
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package. 
<PackageReference Include="dymaptic.GeoBlazor.Core" Version="3.0.1" />
For projects that support PackageReference, copy this XML node into the project file to reference the package. 
paket add dymaptic.GeoBlazor.Core --version 3.0.1
#r "nuget: dymaptic.GeoBlazor.Core, 3.0.1"
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package. 
// Install dymaptic.GeoBlazor.Core as a Cake Addin
#addin nuget:?package=dymaptic.GeoBlazor.Core&version=3.0.1

// Install dymaptic.GeoBlazor.Core as a Cake Tool
#tool nuget:?package=dymaptic.GeoBlazor.Core&version=3.0.1

GeoBlazor

PUT MAPS IN YOUR BLAZOR APPS

With GeoBlazor, you have access to the world’s most powerful and versatile web mapping API, the ArcGIS JavaScript API, but without having to write a single line of JavaScript.

Home Page

GitHub Repository

View the live demo site!

Read the Docs

Join our Discord Server!

Getting Started

(from https://docs.geoblazor.com/pages/gettingStarted.html)

  1. Create a new Blazor Web App (.NET 8), Blazor Server, Blazor Wasm, or Blazor Hybrid (MAUI) project, using the templates provided in your IDE or the dotnet CLI.

  2. add a PackageReference to the latest version of the dymaptic.GeoBlazor.Core package via your IDE's Nuget Package Manager or dotnet add package dymaptic.GeoBlazor.Core. For Blazor Web Apps supporting WebAssembly, add this reference to the .Client WebAssembly project.

  3. The ArcGIS API requires some form of authentication. The simplest is to use an API Key. Generate a key from the ArcGIS Developer Dashboard. For Blazor Server, place it in your appsettings.json, like this:

    {
    "ArcGISApiKey": "yourKeyValue"
}

    <div style="font-size: 0.8rem; font-style: italic; margin-bottom: 1rem;">

    Note: If you are using Blazor WASM, there are several issues with this approach. First, <code>appsettings.json</code> is not added by default to all templates. If you want to add it yourself, you need to add it inside the <code>wwwroot</code> folder. For Blazor Web Apps with WebAssembly, you must define the API key in both projects.

    <span style="color:red;">Be Aware</span> that the API key will be exposed in the browser (just like it would with Javascript). Even when using Blazor Server, the API key may be present in HTTP requests visible to the user in the browsers dev tools, so you should probably take other steps like <a href="https://developers.arcgis.com/documentation/mapping-apis-and-services/security/api-keys/#referrers" target="_blank"> setting up referrer rules in ArcGIS</a>. </div> <div style="font-size: 0.8rem; font-style: italic"> You can also set up an OAuth2 workflow, which is more secure as it does not expose a static API key, but this is more complex. You can read about all the authentication options in <a href="https://docs.geoblazor.com/pages/authentication.html">Authentication</a>. </div>

  4. In the root file that defines your html, add the following lines to the <head> section. This would be _Layout.cshtml for Blazor Server, index.html for Blazor Wasm and Blazor Hybrid, or App.razor for Blazor Web Apps. Note that YourProject is the namespace for the application that you are creating.

    <link href="_content/dymaptic.GeoBlazor.Core"/>
<link href="_content/dymaptic.GeoBlazor.Core/assets/esri/themes/light/main.css" rel="stylesheet" />
<link href="YourProject.styles.css" rel="stylesheet" />

    or (dark theme)

    <link href="_content/dymaptic.GeoBlazor.Core"/>
<link href="_content/dymaptic.GeoBlazor.Core/assets/esri/themes/dark/main.css" rel="stylesheet" />
<link href="YourProject.styles.css" rel="stylesheet" />

    <div style="font-size: 0.8rem; font-style: italic; margin-bottom: 1rem;"> Note: You may already have the YourProject.styles.css file. If so, you can just add the two lines to the existing file. In some .Net templates, this file is commented out by default and you will need to add it. </div>

  5. In _Imports.razor (for each executable project), add the following lines, or add as needed to resolve code that you consume.

    @using dymaptic.GeoBlazor.Core.Components
@using dymaptic.GeoBlazor.Core.Components.Geometries
@using dymaptic.GeoBlazor.Core.Components.Layers
@using dymaptic.GeoBlazor.Core.Components.Popups
@using dymaptic.GeoBlazor.Core.Components.Symbols
@using dymaptic.GeoBlazor.Core.Components.Views
@using dymaptic.GeoBlazor.Core.Components.Widgets
@using dymaptic.GeoBlazor.Core.Events
@using dymaptic.GeoBlazor.Core.Objects

  6. In Program.cs (for each executable project), add the following line to your builder.Services to inject logic components like GeometryEngine.

       builder.Services.AddGeoBlazor(builder.Configuration);

    If you are using Blazor Server or InteractiveServer mode in Blazor Web Apps, you should also add the following lines to Program.cs to support the .wsv file type.

    var provider = new FileExtensionContentTypeProvider();
provider.Mappings[".wsv"] = "application/octet-stream";

app.UseStaticFiles();
// NOTE: for some reason, you still need the plain "UseStaticFiles" call above
app.UseStaticFiles(new StaticFileOptions
{
    ContentTypeProvider = provider
});

  7. Create a new Razor Component in the Pages folder, or just use Index.razor. Add a MapView. Give it basic

  8. Create a new Razor Component in the Pages folder, or just use Index.razor. Add a MapView. Give it basic parameters to ensure that it can render.

    @page "/"

<MapView Longitude="_longitude" Latitude="_latitude" Zoom="11" Style="height: 400px; width: 100%;"> 
</MapView>

@code {
   private readonly double _latitude = 34.027;
   private readonly double _longitude = -118.805;
}

  9. Within the MapView, define a map using the WebMap component. To load a pre-generated map from ArcGIS Online or Portal, get the Map Id (PortalItem Id) of the map.

    <MapView Longitude="_longitude" Latitude="_latitude" Zoom="11" Style="height: 400px; width: 100%;"> 
    <WebMap>
        <PortalItem Id="4a6cb60ebbe3483a805999d481c2daa5" />
    </WebMap>
</MapView>

  10. Add a Widget to the MapView, after the WebMap.

<MapView Longitude="_longitude" Latitude="_latitude" Zoom="11" Style="height: 400px; width: 100%;"> 
    <WebMap>
        <PortalItem Id="4a6cb60ebbe3483a805999d481c2daa5" />
    </WebMap>
    <ScaleBarWidget Position="OverlayPosition.BottomLeft" />
</MapView>
  1. Run your application and make sure you can see your map!
  2. Now that you have a great starting point, you can now start to customize the features available in your new app using Geoblazor's capabilites:<br/> -Take a look at the Documentation pages to learn more.
  3. Optional: To remove the Thank You message from your console messages, please consider registering your application on the dymaptic licensing server. After registering and filling out a small questionnaire, you will receive a registration key, which you can add to any configuration (e.g., appsettings.json) to remove the message.
"Logging": ...,
 "AllowedHosts": ...,
 "ArcGISApiKey": "YOUR_ARCGIS_API_KEY",
 "GeoBlazor": {
     "RegistrationKey": "YOUR_REGISTRATION_KEY"
 }
Product Compatible and additional computed target framework versions.
.NET net6.0 is compatible.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 is compatible.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 is compatible.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages (1)

Showing the top 1 NuGet packages that depend on dymaptic.GeoBlazor.Core:

Package Downloads
dymaptic.GeoBlazor.Pro

GeoBlazor is a GIS Component Library and SDK for building interactive maps in Blazor, powered by ArcGIS. For more information, visit https://www.geoblazor.com or contact dymaptic at geoblazor@dymaptic.com

GitHub repositories (1)

Showing the top 1 popular GitHub repositories that depend on dymaptic.GeoBlazor.Core:

Repository Stars
dymaptic/GeoBlazor
Core Components for the Dymaptic GeoBlazor Library
Version Downloads Last updated
3.0.1 532 3/26/2024
3.0.0 220 3/23/2024
3.0.0-rc.2 102 3/9/2024
3.0.0-rc.1 82 3/6/2024
3.0.0-beta-95 273 2/24/2024
2.5.3.2 2,937 2/11/2024
2.5.3.1 249 2/10/2024
2.5.3 275 2/10/2024
2.5.2 1,530 12/20/2023
2.5.1 642 12/13/2023
2.5.0 956 11/26/2023
2.4.1-beta-1 1,004 10/19/2023
2.4.0 2,467 10/12/2023
2.3.3 2,037 9/14/2023
2.3.2 1,209 9/12/2023
2.3.1-beta-1 1,511 8/18/2023
2.3.0 2,021 8/9/2023
2.3.0-beta-1 1,605 8/2/2023
2.2.1 2,880 7/7/2023
2.2.1-beta-1.1 132 6/16/2023
2.2.0 2,885 6/2/2023
2.2.0-beta-5 1,724 5/28/2023
2.2.0-beta-4 1,979 5/23/2023
2.2.0-beta-3 720 5/20/2023
2.2.0-beta-2 742 5/20/2023
2.2.0-beta-1 1,605 5/13/2023
2.1.0 5,442 4/18/2023
2.1.0-beta-1 1,658 4/16/2023
2.0.2-beta-2 1,965 4/2/2023
2.0.2-beta-1 1,960 4/1/2023
2.0.1 2,151 3/18/2023
2.0.1-beta-3 1,624 3/5/2023
2.0.1-beta-2 1,647 3/4/2023
2.0.1-beta-1 1,818 3/4/2023
2.0.0 2,440 2/28/2023
2.0.0-beta-9 1,716 2/24/2023
2.0.0-beta-8 1,855 2/19/2023
2.0.0-beta-7 1,592 2/19/2023
2.0.0-beta-6 1,900 2/15/2023
2.0.0-beta-5 1,652 2/15/2023
2.0.0-beta-4 1,760 2/11/2023
2.0.0-beta-3 1,842 2/9/2023
2.0.0-beta-2 1,654 2/7/2023
2.0.0-beta-11 1,765 2/25/2023
2.0.0-beta-10 1,583 2/25/2023
2.0.0-beta-1 1,727 2/5/2023
1.2.0 2,526 11/13/2022
1.1.1 1,309 10/20/2022
1.1.0 1,163 10/8/2022