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: FObermaier **

There is an issue on the NTS issue tracker
http://code.google.com/p/nettopologysuite/issues/detail?id=157&can=1&q=signed

We've had troubles with signed assemblies, that's why we quit doing that.
Now, if that is a requirement for you to use NTS, we need to reconsider that.

↧

Commented Task: DotSpatial.Topology vs NetTopologySuit [25064]

January 25, 2014, 2:00 am

≫ Next: Commented Unassigned: Distance.Parse is inconsistant with invalid input [24937]

≪ Previous: Commented Task: DotSpatial.Topology vs NetTopologySuit [25064]

>Now, if that is a requirement for you to use NTS, we need to reconsider that.
+1

↧

Commented Unassigned: Distance.Parse is inconsistant with invalid input [24937]

January 26, 2014, 5:30 am

≫ Next: New Post: Projections for Hawaii

≪ Previous: Commented Task: DotSpatial.Topology vs NetTopologySuit [25064]

Distance.Parse throws an exception when a number with an unrecognized unit is entered:

```
Distance.Parse("3 this should not be valid");
```

This is fine, but if the number is removed:

```
Distance.Parse("this should not be valid");
```

Then the function returns a Distance object set to "0 ft" and IsInvalid=false.

Invalid text without a number should throw an exception.
Comments: ** Comment from web user: RayHarwood **

For VB, this is actually "technically consistent". In the first case, it parses a 3 and discards the rest. In the second case, it cannot find any valid numerical at the beginning, so it throws an error.

I recommend using the alternative TryParse instead.

↧

New Post: Projections for Hawaii

January 26, 2014, 10:49 am

≫ Next: Source code checked in, #73706

≪ Previous: Commented Unassigned: Distance.Parse is inconsistant with invalid input [24937]

Mogikanin,

I have finally solved my problem, at least to my satisfaction. I am still not sure if it is the correct way to implement but it gives me the answers I need. Here is a snipped from my VB code. The key was to add the +towgs84=-1,=1,1 parameter to the Proj4 string. That produces about a 50cm translation in both easting and northing on the big island.

The reference string is EPSG:1252, or so I think.

Hope this helps

Regards,

Dim pLatLon As ProjectionInfo

If bHawaiiUTM Then

pLatLon = ProjectionInfo.FromProj4String(" +proj=latlong +ellps=WGS84 +towgs84=-1,-1,1")

'ref EPSG 1252: is practically same as NAD83 but includes offsets of 1,1,-1

pLatLon.Name = "[NAD83] (4m) United States (USA) - Hawaii"

Else

pLatLon = KnownCoordinateSystems.Geographic.World.WGS1984

End If

↧

Source code checked in, #73706

January 26, 2014, 1:30 pm

≫ Next: Closed Issue: Project (dspx) serialization and GDAL Imagery [25121]

≪ Previous: New Post: Projections for Hawaii

Fixed #25121: Project (dspx) serialization and GDAL Imagery.

↧

Closed Issue: Project (dspx) serialization and GDAL Imagery [25121]

January 26, 2014, 1:30 pm

≫ Next: Commented Issue: Setting FilePath property of a FeatureSet doesn't populate the FeatureSet [22287]

≪ Previous: Source code checked in, #73706

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: Resolved with changeset 73706: Fixed #25121: Project (dspx) serialization and GDAL Imagery.

↧

Commented Issue: Setting FilePath property of a FeatureSet doesn't populate the FeatureSet [22287]

January 26, 2014, 1:55 pm

≫ Next: New Post: How to disable the "invalid or Missing Projection Message box"

≪ Previous: Closed Issue: Project (dspx) serialization and GDAL Imagery [25121]

I have the following test code:

var fs = new FeatureSet()
fs.FilePath = ("c:\\temp\\test.shp")
Assert.Greater(fs.Features.Count) //fails - Features.Count is still zero

The test fails, because setting the FilePath doesn't have the expected side effect of populating the Features and the AttributeTable.

This creates a problem in Serialization. Sometimes a FeatureSet instance is serialized using the DotSpatial.Data.FeatureSet data type. When it is being deserialized, first the default constructor is used (this creates a new empty FeatureSet) and then the FilePath property is being set (this doesn't populate the features as the original author of XmlDeserializer expected).

Suggested solution ideas:
Option 1 - When the FeatureSet is empty and the FilePath property is set, populate the features and attributes of the current instance from the FilePath file.
Option 2 - When serializing a FeatureSet, try to serialize all its geometry features and attributes to the xml file (this would solve the issue of user-generated in-memory FeatureSets that don't have a source file)
Option 3 - When serializing a FeatureSet, try to check the data type. If it's SHP, then serialize it as a PointShapefile, LineShapefile or PolygonShapefile. In other words, delegate the responsibility of serializing from FeatureSet to the DataProvider. For example, the ShapefileProvider would serialize the FilePath but the SpatiaLite provider would serialize the database connection and table name.
Comments: ** Comment from web user: mogikanin **

Populating inner FeatureSet when FilePath changed will break a lot of code which uses DS.
If you want to use FeatureSet directly in such manner (without using specific classes like PointShapefile, PolygonShapefile,....) you need to create your own FeatureSet inheritor:
```
public class FeatureSetSerializableFilePath : FeatureSet
{
private void OpenFileInternal(string filePath)
{
// Open logic...
}

[Serialize("FilePath")]
public override string FilePath
{
get { return base.FilePath; }
set
{
if (FilePath == value) return;
base.FilePath = value;
OpenFileInternal(value);
}
}
}
```

↧

New Post: How to disable the "invalid or Missing Projection Message box"

January 26, 2014, 7:20 pm

≫ Next: Edited Issue: Problem with GDAL write filter [23730]

≪ Previous: Commented Issue: Setting FilePath property of a FeatureSet doesn't populate the FeatureSet [22287]

Can you also explain where to put this part of code?

↧

Edited Issue: Problem with GDAL write filter [23730]

January 26, 2014, 11:58 pm

≫ Next: Source code checked in, #73707

≪ Previous: New Post: How to disable the "invalid or Missing Projection Message box"

↧

Source code checked in, #73707

January 27, 2014, 12:18 am

≫ Next: Closed Issue: Problem with GDAL write filter [23730]

≪ Previous: Edited Issue: Problem with GDAL write filter [23730]

Fixed #23730: Problem with GDAL write filter

↧

Closed Issue: Problem with GDAL write filter [23730]

January 27, 2014, 12:18 am

≫ Next: Source code checked in, #73708

≪ Previous: Source code checked in, #73707

↧

Source code checked in, #73708

January 27, 2014, 1:09 am

≫ Next: Commented Feature: FeatureToRaster tool doesn't recognize GeoTiff as valid output format [22237]

≪ Previous: Closed Issue: Problem with GDAL write filter [23730]

Fixed #22237: FeatureToRaster tool doesn't recognize GeoTiff as valid output format

↧

Commented Feature: FeatureToRaster tool doesn't recognize GeoTiff as valid output format [22237]

January 27, 2014, 1:09 am

≫ Next: Closed Feature: FeatureToRaster tool doesn't recognize GeoTiff as valid output format [22237]

≪ Previous: Source code checked in, #73708

Steps to duplicate:
Run Demo Map
Add a polygon shapefile
Run the FeatureToRaster tool
In the Output file dialog, BGD is offered as the only possible file type.

Expectation: If GDALExtension is loaded, then all GDAL raster file formats should be available as output.
Note: The same problem also occurs with the "Clip Raster Layer" tool and with all "Raster Overlay" tools.
Comments: Associated with changeset 73708: Fixed #22237: FeatureToRaster tool doesn't recognize GeoTiff as valid output format

↧

Closed Feature: FeatureToRaster tool doesn't recognize GeoTiff as valid output format [22237]

January 27, 2014, 1:10 am

≫ Next: Closed Issue: Point Symbology possible error [23339]

≪ Previous: Commented Feature: FeatureToRaster tool doesn't recognize GeoTiff as valid output format [22237]

↧

Closed Issue: Point Symbology possible error [23339]

January 27, 2014, 1:25 am

≫ Next: Closed Unassigned: Cross-thread operation not valid [24848]

≪ Previous: Closed Feature: FeatureToRaster tool doesn't recognize GeoTiff as valid output format [22237]

Have some problems with diffined symbology for a point layer, have attached a project which reproduces the error. after pressing button1, on mouse click within the mapcontrol should add a point to one layer in the centre of the grid and turn the grid cell grey.
First click adds the point but does not turn grid cell grey.
Second click behaves as intended.
Third click give error in MapPointLayer.DrawFeatures.
I have to admit not to sure if I've put this together correctly, or if I've crossed wires some where.
Been having plenty of problems refreshing with the correct symbology within the mapcontrol after adding features.
Feeling very clumsy using DotSpatial, so I'm sure I'm missing some concept.
Thanks for any help.
Did want to place this under the discussion section but could not attach a file.
Comments: Please use discussions tab for such questions.
You can share your files using dropbox or any other free services for sharing.

↧

Closed Unassigned: Cross-thread operation not valid [24848]

January 27, 2014, 1:33 am

≫ Next: Closed Unassigned: 一个问题 [25052]

≪ Previous: Closed Issue: Point Symbology possible error [23339]

I am attempting to reproject a raster. When I get to the point of output.saveas(outputfilename) I get a cross-thread error with the ribbonstatusbar (see below). Is there a way to work around this or fix it?

System.InvalidOperationException: Cross-thread operation not valid: Control 'ribbonStatusBar' accessed from a thread other than the thread it was created on.
at System.Windows.Forms.Control.get_Handle()
at System.Windows.Forms.Control.PointToClientInternal(Point p)
at System.Windows.Forms.Control.PointToClient(Point p)
at DevExpress.XtraBars.Ribbon.ViewInfo.RibbonItemViewInfo.PointToClient(Point p)
at DevExpress.XtraBars.BarItemLink.ScreenToLinkPoint(Point p)
at DevExpress.XtraBars.ViewInfo.BarLinkViewInfo.get_MousePosition()
at DevExpress.XtraBars.ViewInfo.BarEditLinkViewInfo.CompareLinkState(BarLinkState newState, BarLinkState current)
at DevExpress.XtraBars.ViewInfo.BarLinkViewInfo.UpdateLinkState()
at DevExpress.XtraBars.BarItemLink.CheckUpdateLinkState()
at DevExpress.XtraBars.BarItemLink.LayoutChanged()
at DevExpress.XtraBars.BarItemLink.OnLinkChanged()
at DevExpress.XtraBars.BarItem.OnItemChanged(BarItemLink link, Boolean onlyInvalidate, Boolean onlyUpdateAppearance)
at DevExpress.XtraBars.BarItem.OnItemChanged(Boolean onlyInvalidate, Boolean onlyUpdateAppearance)
at DevExpress.XtraBars.BarItem.OnItemChanged(Boolean onlyInvalidate)
at DevExpress.XtraBars.BarEditItem.OnEditValueChanged()
at DevExpress.XtraBars.BarEditItem.set_EditValue(Object value)
at DotSpatial.RibbonHeader.Progress(String key, Int32 percent, String message)
at DotSpatial.Data.ProgressMeter.SendProgress()
at DotSpatial.Data.ProgressMeter.set_CurrentPercent(Int32 value)
at DotSpatial.Data.ProgressMeter.set_CurrentValue(Object value)
at DotSpatial.Data.Raster`1.GetStatistics()
at DotSpatial.Data.Raster.SaveAs(String fileName, String driverCode, String[] options)
at DotSpatial.Data.Raster.SaveAs(String fileName)
Comments: Not DS issue. Probably you are saving raster in not GUI thread and you need to synchronize this by yourself.

↧

Closed Unassigned: 一个问题 [25052]

January 27, 2014, 1:35 am

≫ Next: Commented Unassigned: Distance.Parse is inconsistant with invalid input [24937]

≪ Previous: Closed Unassigned: Cross-thread operation not valid [24848]

DotSpatial.Data.IFeatureSet fs = DotSpatial.Data.FeatureSet.Open(fileName);
foreach (DotSpatial.Data.IFeature f in __fs.Features__)
{
//
}
从外部导入一个shp文件（我的测试文件大小为5MB），每当调用fs.Features时，内存直线上升。
Comments: Not an issue.

↧

Latest Images