This discussion has been copied to a work item. Click here to go to the work item and continue the discussion.
↧
New Post: Project (dspx) serialization and GDAL Imagery
↧
New Post: Project (dspx) serialization and GDAL Imagery
↧
↧
New Post: Loading layers using WMS...... confused on if DotSpatial can do this
Mogikanin - Thanks for the reply. I did find what you referenced. I found a some oddities, however, which was that I could only load a single layer from a single WMS, the "identify" feature was showing my feature data, and the features were not displayed properly. That being said, some of these things just may not have been enabled in the test app. Our goal is to be able to read in multiple WMS & WFS (get unhandled exceptions when using the test apps WFS extention) layers. In other clients (like QGIS and Openlayers), we are able to load a WMS layer that contains features and make successful GetFeatureInfo calls. We are hoping to be able to do something similar with DotSpatial because DotSpatial fits with our .Net WinForms architecture.
So, my question now is how do I enable a WFS capability within my own DotSpatial application. Do I need to create an extension/plugin or can I just import some DLL (WebMap maybe??) and write my own code. Since WMS access seems to be available in some fashion for the demo app, just need to find the way to add it to my app.
Thanks - Peter
So, my question now is how do I enable a WFS capability within my own DotSpatial application. Do I need to create an extension/plugin or can I just import some DLL (WebMap maybe??) and write my own code. Since WMS access seems to be available in some fashion for the demo app, just need to find the way to add it to my app.
Thanks - Peter
↧
New Post: Loading layers using WMS...... confused on if DotSpatial can do this
Yes, this WMS feature is new in DotSpatial and may not contains some features. But at least it works.
But we will be glad to hear what need to include into next releases :)
I'm not sure that existing WFS plugin is in working state and can be used for any purposes. I never used it.
If you want to enable WebMap in your app - you need to copy all dlls from WebMap plugin to your plugins folder: DotSpatial.Plugins.WebMap.dll, BruTile.dll, BruTile.Desktop.dll. Of course your app should deal with AppManager\Extensions stuff.
As alternative you can try directly reference WebMap to your project and try to reuse it with your needs.
Maxim.
But we will be glad to hear what need to include into next releases :)
I'm not sure that existing WFS plugin is in working state and can be used for any purposes. I never used it.
If you want to enable WebMap in your app - you need to copy all dlls from WebMap plugin to your plugins folder: DotSpatial.Plugins.WebMap.dll, BruTile.dll, BruTile.Desktop.dll. Of course your app should deal with AppManager\Extensions stuff.
As alternative you can try directly reference WebMap to your project and try to reuse it with your needs.
Maxim.
↧
Created Unassigned: Plugins build improvements [25124]
Put output of each plugin into separate folder. Also add readme for each plugin.
This will help to see which dlls needed for every plugin.
This will help to see which dlls needed for every plugin.
↧
↧
New Post: Projections for Hawaii
Mogikanin, thanks for your reply. I now know enough more to make my post a little clearer. I have previously gotten DotSpatial from Nuget and I have updated to the latest version 1.6. And I have recently downloaded the source code just for browsing purposes as I do not plan to make any changes and to recompile.
There are two Datum's that exist (actually there are hundreds like you say, but only two of interest for me). One is a NAD83(Conus) datum and the other is a NAD83(Hawaii) datum. The Nad83(Conus) datum is the one exposed in KnownCoordinateSystems and it is named UtmNad1983. All of the other projections in DotSpatial, except those named OldHawaiian, produce results that are identical with a fraction of a centimeter. OldHawaiian produces results that are hundreds of meters different.
However, using a NAD83(Hawaii) datum and comparing a NAD83(Conus) datum in other applications produces Northing and Easting coordinates that are different by approximately 50cm in both Easting and Northing. I have been unable to find the NAD83(Hawaii) datum in DotSpatial nor any datum that gives results that matches those obtained from other sources. My two other sources are a Trimble GPS R8 receiver, for one, and the application Geosoft Oasis/montaj for another.
So this is a request that the NAD83(Hawaii) datum be included in DotSpatial and exposed in KnownCoordinateSystems.
There are two Datum's that exist (actually there are hundreds like you say, but only two of interest for me). One is a NAD83(Conus) datum and the other is a NAD83(Hawaii) datum. The Nad83(Conus) datum is the one exposed in KnownCoordinateSystems and it is named UtmNad1983. All of the other projections in DotSpatial, except those named OldHawaiian, produce results that are identical with a fraction of a centimeter. OldHawaiian produces results that are hundreds of meters different.
However, using a NAD83(Hawaii) datum and comparing a NAD83(Conus) datum in other applications produces Northing and Easting coordinates that are different by approximately 50cm in both Easting and Northing. I have been unable to find the NAD83(Hawaii) datum in DotSpatial nor any datum that gives results that matches those obtained from other sources. My two other sources are a Trimble GPS R8 receiver, for one, and the application Geosoft Oasis/montaj for another.
So this is a request that the NAD83(Hawaii) datum be included in DotSpatial and exposed in KnownCoordinateSystems.
↧
New Post: Loading layers using WMS...... confused on if DotSpatial can do this
Can't find a reference on how top integrate the plugin into my Visual Studio project. Not sure what "plugins" folder you were referring to. I took the three DLLs you referenced and added them to my project's references, but the closest thing I could find related to a WMS call is a DotSpatial.Plugins.WebMap.WMS.WmsRequest but could not find anyway to hand it off to something to execute it, much less at it to my DotSpatial map control. I found some reference to the class DotSpatial.Plugins.WebMap.WMS.WMSClient, but could not find that in the DLL. So, the bottom line is that I can't find anything that would help in figuring out how to make a WMS call and display the results on the map control. By chance is the project file for the demo map app available? I could look how it implement the WMS call? Just a thought. Any clues as to how to get this working would be appreciated.
↧
Commented Unassigned: Print Layout scale bar bug [25095]
Hello:
In the print layout view when I change the units on the scale bar's properties window, the measurement units are being changed on the map scale bar. That's correct. However, still it shows "km" on the scale bar. It has to be as same as the unit text from properties window.
Comments: ** Comment from web user: Tevaganthan **
In the print layout view when I change the units on the scale bar's properties window, the measurement units are being changed on the map scale bar. That's correct. However, still it shows "km" on the scale bar. It has to be as same as the unit text from properties window.
Comments: ** Comment from web user: Tevaganthan **
Thanks! It works!
↧
Closed Unassigned: Print Layout scale bar bug [25095]
Hello:
In the print layout view when I change the units on the scale bar's properties window, the measurement units are being changed on the map scale bar. That's correct. However, still it shows "km" on the scale bar. It has to be as same as the unit text from properties window.
In the print layout view when I change the units on the scale bar's properties window, the measurement units are being changed on the map scale bar. That's correct. However, still it shows "km" on the scale bar. It has to be as same as the unit text from properties window.
↧
↧
Commented Issue: Project (dspx) serialization and GDAL Imagery [25121]
This seems to happen even when using the DemoMap.exe.
1.) Start up DemoMap.exe
2.) Add a gdal imagery layer to the application
3.) Save the project file
4.) Close DemoMap.exe
5.) Reopen DemoMap.exe
6.) Open the saved project file
7.) -- Error Here --
Link to a relatively small sid file I was using for this test:
https://dl.dropboxusercontent.com/u/16831965/gdal_sid.zip
Comments: ** Comment from web user: FObermaier **
1.) Start up DemoMap.exe
2.) Add a gdal imagery layer to the application
3.) Save the project file
4.) Close DemoMap.exe
5.) Reopen DemoMap.exe
6.) Open the saved project file
7.) -- Error Here --
Link to a relatively small sid file I was using for this test:
https://dl.dropboxusercontent.com/u/16831965/gdal_sid.zip
Comments: ** Comment from web user: FObermaier **
This has probably to do with types not being recognized. The GDAL plugin needs to handle the ```AppDomain.Current.AssemblyResolve``` event. An examples is here:
https://github.com/FObermaier/DotSpatial.Plugins/blob/master/DotSpatial.Plugins.BruTileLayer/BruTileLayerPlugin.cs
↧
Edited Task: Plugins build improvements [25124]
Put output of each plugin into separate folder. Also add readme for each plugin.
This will help to see which dlls needed for every plugin.
This will help to see which dlls needed for every plugin.
↧
New Post: Loading layers using WMS...... confused on if DotSpatial can do this
Not sure that at the moment you will be able to use WebMap directly without using AppManager\Extensions. This need some modifications in WebMap source code.
Here the minimal set of dlls with demomap exe which you need to use WebMap as extension.
http://wikisend.com/download/484446/DotSpatial.WebMapMinimal.zip
Also, there is another DS plugin - https://github.com/FObermaier/DotSpatial.Plugins/
You can try it too, is supports WMSC and WMTS.
Here the minimal set of dlls with demomap exe which you need to use WebMap as extension.
http://wikisend.com/download/484446/DotSpatial.WebMapMinimal.zip
Also, there is another DS plugin - https://github.com/FObermaier/DotSpatial.Plugins/
You can try it too, is supports WMSC and WMTS.
↧
New Post: Projections for Hawaii
Well, at the moment you can use
ProjectionInfo.FromProj4String() or ProjectionInfo.FromEsriString() to create any projection without having it in KnownCoordinateSystems. Also you can edit properties of ProjectionInfo to tune projection to your needs.
It will be great if you will provide a patch for NAD83(Hawaii) so we can include it into DotSpatial.
ProjectionInfo.FromProj4String() or ProjectionInfo.FromEsriString() to create any projection without having it in KnownCoordinateSystems. Also you can edit properties of ProjectionInfo to tune projection to your needs.
It will be great if you will provide a patch for NAD83(Hawaii) so we can include it into DotSpatial.
↧
↧
New Post: add attribute
add attribute to shp you can find in doc "DotSpatial_Tutorial_4.docx"
↧
Source code checked in, #73696
Move output path of each plugin to own subfolder. Added readmes.
↧
Closed Task: Plugins build improvements [25124]
Put output of each plugin into separate folder. Also add readme for each plugin.
This will help to see which dlls needed for every plugin.
Comments: Resolved with changeset 73696: Move output path of each plugin to own subfolder. Added readmes.
This will help to see which dlls needed for every plugin.
Comments: Resolved with changeset 73696: Move output path of each plugin to own subfolder. Added readmes.
↧
Source code checked in, #73697
Branched from $/dotSpatial/Trunk
↧
↧
Edited Task: DotSpatial.Topology vs NetTopologySuit [25064]
At the moment in the NetTopologySuit there are a lot of fixes\improvements, which not included into DotSpatial.Topology. I think we need to think how to syncronize these two projects. I think we should reuse NetTopologySuit as a reference dll insde DotSpatial.Topology with some converters from NTS to DS classes.
↧
Commented Task: DotSpatial.Topology vs NetTopologySuit [25064]
At the moment in the NetTopologySuit there are a lot of fixes\improvements, which not included into DotSpatial.Topology. I think we need to think how to syncronize these two projects. I think we should reuse NetTopologySuit as a reference dll insde DotSpatial.Topology with some converters from NTS to DS classes.
Comments: ** Comment from web user: mogikanin **
Comments: ** Comment from web user: mogikanin **
There is a problem with referencing NTS and GeoAPI.
DotSpatial.Topology is a signed assembly (all core DS dlls are too), but NTS and GeoAPI - not. So i can't to reference them :(
Any suggestions?
↧
Source code checked in, #73699
Optimizing code, restored some tests in DotSpatial.Projections
↧