uDig

Since Stamen created wonderful maps out of Openstreetmap data and provides a Tile Map Service the following tutorial shows how to use it in uDig.Map Tiles from Stamen (http://maps.stamen.com/) are published under a Creative Commons Attribution (CC BY ... [More] 3.0) license. The How-to guide at Stamen shows map URL templates for three different types:http://tile.stamen.com/toner/{z}/{x}/{y}.pnghttp://tile.stamen.com/terrain/{z}/{x}/{y}.jpghttp://tile.stamen.com/watercolor/{z}/{x}/{y}.jpgHere are images for each in the same order  At the moment of writing toner and watercolor tile sets are available worldwide whereas terrain is only available for USA.How to use it in uDigTo add a new Layer click on Menu Layer -> Add .. to open Add Data Wizard. Choose Web Map Tiles in the list followed by button Next >.On the next page uncheck Mapnik first and check Custom Server in the left panel.Copy one of the map scheme URL's listed above and paste it into URL field on the right. To finally add the layer to the current map push Next > Button again. The layer is named Custom Server. To rename the layer, just right click on the layer in the layers view and choose Rename.  [Less]

Since Stamen created wonderful maps out of Openstreetmap data and provides a Tile Map Service the following tutorial shows how to use it in uDig.Map Tiles from Stamen (http://maps.stamen.com/) are published under a Creative Commons Attribution (CC BY ... [More] 3.0) license. The How-to guide at Stamen shows map URL templates for three different types: http://tile.stamen.com/toner/{z}/{x}/{y}.png http://tile.stamen.com/terrain/{z}/{x}/{y}.jpg http://tile.stamen.com/watercolor/{z}/{x}/{y}.jpg Here are images for each in the same order    At the moment of writing toner and watercolor tile sets are available worldwide whereas terrain is only available for USA.How to use it in uDigTo add a new Layer click on Menu Layer -> Add .. to open Add Data Wizard. Choose Web Map Tiles in the list followed by button Next >.On the next page uncheck Mapnik first and check Custom Server in the left panel.Copy one of the map scheme URL's listed above and paste it into URL field on the right. To finally add the layer to the current map push Next > Button again. The layer is named Custom Server. To rename the layer, just right click on the layer in the layers view and choose Rename.  [Less]

Since Stamen created wonderful maps out of Openstreetmap data and provides a Tile Map Service the following tutorial shows how to use it in uDig.Map Tiles from Stamen (http://maps.stamen.com/) are published under a Creative Commons Attribution (CC BY ... [More] 3.0) license. The How-to guide at Stamen shows map URL templates for three different types: http://tile.stamen.com/toner/{z}/{x}/{y}.png http://tile.stamen.com/terrain/{z}/{x}/{y}.jpg http://tile.stamen.com/watercolor/{z}/{x}/{y}.jpg Here are images for each in the same order    At the moment of writing toner and watercolor tile sets are available worldwide whereas terrain is only available for USA.How to use it in uDigTo add a new Layer click on Menu Layer -> Add .. to open Add Data Wizard. Choose Web Map Tiles in the list followed by button Next >.On the next page uncheck Mapnik first and check Custom Server in the left panel.Copy one of the map scheme URL's listed above and paste it into URL field on the right. To finally add the layer to the current map push Next > Button again. The layer is named Custom Server. To rename the layer, just right click on the layer in the layers view and choose Rename.  [Less]

First, we love fixes and improvements for functionality and stability!Second, we need you to make uDig better!What is a pull request for?We are allowed to host our source code at Github. Github introduced pull requests to "[..] review the set of ... [More] changes, discuss potential modifications, and even push follow-up commits if necessary [..]". It helps us to accept patches and discuss approaches directly with code fragments.Since uDig moved to LocationTech, which is a Industry Working Group of Eclipse Foundation, the project is following their committer guidelines. Eclipse Administrations set up few checks for pull requests to verify: if the committer have signed a CLA at Eclipse if the commit has valid Signed-off-by footers What is required?To create pull requests its required to create an Github account. Its also necessary that you've forked uDig.You should be familiar with Eclipse IDE and have successfully build uDig on your machine. Great!How to provide a bugfix?Following the best practices you should create a branch in your working copy. If you like to create a bugfix for an exiting release, please discuss at the mailing list where to start from. If you fix is for future releases, please create a branch from master, e.g. upd-gt-14:git checkout -b upd-gt-14Now you can fix the bug.Whenever you like to commit something, please use -s option. to sign off on commit:git commit -s -m "upgrade to GeoTools 14.1"If you are done, its time to share your improvement. Two steps are required to get it into core codebase.Push your work To get others in position to review and accept changes you necessary to publish your work. We are following the common guidelines, where LocationTech's repository is upstream and your fork is origin repository. Push your local branch to your forkgit push upd-gt-14 originCreate a pull requestOpen the repository URL of your fork in a browser and navigate to recently pushed branch. To create a pull request you can hit the green button or click on the link "pull request" This leads to the following screen where you can add comments and finally create the pull request against the LocationTech's repository.What if..?I've already created a pull request but forgot to sign off on commitsThe easiest way is to reset your work and commit again, the example down below just demonstrates how to change the last commit on your branch. NOTE: this is not recommend for master-branch if a commit pushed to LocationTech's repository already!git reset HEAD^1After that you have local changes in your working copy you can commit again. Once committed correctly with -s option again please use push command with the force option -f git push -f upd-gt-14 origin This rewrites history but doesn't break anything.I have lots of commits and like to get it into oneThats fine and helps a lot to identify and deal with changes later (merging, cherry-picking, etc). Just use rebase command in interactive mode and mark commits to squash into a single one. Please consult git docs for details. After successfully rewrite use force option for git push like mentioned above. git reset -i [Less]

First, we love fixes and improvements for functionality and stability!Second, we need you to make uDig better!What is a pull request for?We are allowed to host our source code at Github. Github introduced pull requests to "[..] review the set of ... [More] changes, discuss potential modifications, and even push follow-up commits if necessary [..]". It helps us to accept patches and discuss approaches directly with code fragments.Since uDig moved to LocationTech, which is a Industry Working Group of Eclipse Foundation, the project is following their committer guidelines. Eclipse Administrations set up few checks for pull requests to verify: if the committer have signed a CLA at Eclipse if the commit has valid Signed-off-by footers What is required?To create pull requests its required to create an Github account. Its also necessary that you've forked uDig.You should be familiar with Eclipse IDE and have successfully build uDig on your machine. Great!How to provide a bugfix?Following the best practices you should create a branch in your working copy. If you like to create a bugfix for an exiting release, please discuss at the mailing list where to start from. If you fix is for future releases, please create a branch from master, e.g. upd-gt-14:git checkout -b upd-gt-14Now you can fix the bug.Whenever you like to commit something, please use -s option. to sign off on commit:git commit -s -m "upgrade to GeoTools 14.1"If you are done, its time to share your improvement. Two steps are required to get it into core codebase.Push your work To get others in position to review and accept changes you necessary to publish your work. We are following the common guidelines, where LocationTech's repository is upstream and your fork is origin repository. Push your local branch to your forkgit push upd-gt-14 originCreate a pull requestOpen the repository URL of your fork in a browser and navigate to recently pushed branch. To create a pull request you can hit the green button or click on the link "pull request" This leads to the following screen where you can add comments and finally create the pull request against the LocationTech's repository.What if..?I've already created a pull request but forgot to sign off on commitsThe easiest way is to reset your work and commit again, the example down below just demonstrates how to change the last commit on your branch. NOTE: this is not recommend for master-branch if a commit pushed to LocationTech's repository already!git reset HEAD^1After that you have local changes in your working copy you can commit again. Once committed correctly with -s option again please use push command with the force option -f git push -f upd-gt-14 origin This rewrites history but doesn't break anything.I have lots of commits and like to get it into oneThats fine and helps a lot to identify and deal with changes later (merging, cherry-picking, etc). Just use rebase command in interactive mode and mark commits to squash into a single one. Please consult git docs for details. After successfully rewrite use force option for git push like mentioned above. git reset -i [Less]

First, we love fixes and improvements for functionality and stability!Second, we need you to make uDig better!What is a pull request for?We are allowed to host our source code at Github. Github introduced pull requests to "[..] review the set of ... [More] changes, discuss potential modifications, and even push follow-up commits if necessary [..]". It helps us to accept patches and discuss approaches directly with code fragments.Since uDig moved to LocationTech, which is a Industry Working Group of Eclipse Foundation, the project is following their committer guidelines. Eclipse Administrations set up few checks for pull requests to verify:if the committer have signed a CLA at Eclipseif the commit has valid Signed-off-by footersWhat is required?To create pull requests its required to create an Github account. Its also necessary that you've forked uDig.You should be familiar with Eclipse IDE and have successfully build uDig on your machine. Great!How to provide a bugfix?Following the best practices you should create a branch in your working copy. If you like to create a bugfix for an exiting release, please discuss at the mailing list where to start from. If you fix is for future releases, please create a branch from master, e.g. upd-gt-14:git checkout -b upd-gt-14Now you can fix the bug.Whenever you like to commit something, please use -s option. to sign off on commit:git commit -s -m "upgrade to GeoTools 14.1"If you are done, its time to share your improvement. Two steps are required to get it into core codebase.Push your work To get others in position to review and accept changes you necessary to publish your work. We are following the common guidelines, where LocationTech's repository is upstream and your fork is origin repository. Push your local branch to your forkgit push upd-gt-14 originCreate a pull requestOpen the repository URL of your fork in a browser and navigate to recently pushed branch. To create a pull request you can hit the green button or click on the link "pull request"This leads to the following screen where you can add comments and finally create the pull request against the LocationTech's repository.What if..?I've already created a pull request but forgot to sign off on commitsThe easiest way is to reset your work and commit again, the example down below just demonstrates how to change the last commit on your branch.NOTE: this is not recommend for master-branch if a commit pushed to LocationTech's repository already!git reset HEAD^1After that you have local changes in your working copy you can commit again. Once committed correctly with -s option again please use push command with the force option -fgit push -f upd-gt-14 origin This rewrites history but doesn't break anything.I have lots of commits and like to get it into oneThats fine and helps a lot to identify and deal with changes later (merging, cherry-picking, etc). Just use rebase command in interactive mode and mark commits to squash into a single one. Please consult git docs for details. After successfully rewrite use force option for git push like mentioned above. git reset -i [Less]

The uDig community is pleased to release uDig 1.5.0.RC1. Release Details uDig Downloads (Mac, Linux, and Windows) Release Notes Issue Tracker Change Log GitHub Tag New Features This release supports a couple new features: The web view down points ... [More] to a GitHub page (rather than a wiki page). Thanks to Frank for this work. The style editor now supports arrows (as shown in the above map). Thanks to Emily and Refractions for this work. Packages have been changed to org.locationtech.udig allowing SDK developers to migrate at this time (see below). DevelopersInternally the package structure and extensions have changed from net.refractions.udig to org.locationtech.udig. This blog post describes how to setup a development environment and update your plugin accordingly.Target Platform and EnvironmentFor instructions on using the project straight from GitHub (and building from Eclipse or Maven) see the project README.We also provide a uDig 1.5.0.RC1 SDK as a stand-alone target platform: 1. Download the SDK2. Unzip the SDK into a udig-sdk folder.3. Open up Windows > Preferences and navigate to the Target Platform page4. Set the target platform to the location of your udig-sdk folder. This will take a few moments while the folder contents are scanned.As a standalone target platform you can develop uDig with a recent version of Eclipse (uDig no longer depends on your development environment when running). The target platform also includes the JAI and ImageIO bundles which previously were installed as JRE Extensions.Thanks to Frank for these ease-of-use improvements for uDig developers.Dependency and Extension Point Migration At a high-level your plugins must be updated to use the org.locationtech.udig packages and extensions. This can be accomplished with a search and replace, but we will take the time to point out strategies for updating a few specific files.You can turn off eclipse automatic build when performing these changes to save time.MANIFEST.MFRequired Bundles (Require-Bundle) and imported Packages (Import-Package) in MANIFEST.MF files should reflect the namespace schange as well. Its a simple search and replace within Eclipse (Search -> File...):Click Replace... to change to new namespace:Extension PointsExtension definitions based on uDig Extension Points have to be updated. Search for net.refractions.udig in your plugin.xml and feature.xml files and replace the string with org.locationtech.udigSource Code MigrationWith the build environment fixed up we can now move on to updating your source code.You can turn on eclipse automatic build now, a lot of compile errors are expected after re-compilation against the new udig-sdk target-platform. This time we can perform the same search and replace on "*.java" files. This should fix the vast majority of problems (as it updates both imports and any extension point references you happened to make use of in your Java code).If any package import errors remain, click with right mouse on the project and hit Source and Organize Imports. The uDig 1.5.0.RC1 is built using GeoTools 11.2. The GeoTools project provides an upgrade guide for those using a prior version of the library.Looking AheadIf you have any problems with the current udig-sdk or like to ask something we didn't addressed in this post feel free to contact us: IRC (Internet Relay Chat) #udig on freenode #geotools on freenode Via Twitter (@udigGIS) Developer mailing list at mailing list [email protected] (subscribe here).  The 2.0.0 Release expects no further API change, its only focus is the transition to Eclipse Luna (a branch is available for developers here). [Less]

The uDig community is pleased to release uDig 1.5.0.RC1. Release Details uDig Downloads (Mac, Linux, and Windows) Release Notes Issue Tracker Change Log GitHub Tag New Features This release supports a couple new features: The web view down points ... [More] to a GitHub page (rather than a wiki page). Thanks to Frank for this work. The style editor now supports arrows (as shown in the above map). Thanks to Emily and Refractions for this work. Packages have been changed to org.locationtech.udig allowing SDK developers to migrate at this time (see below). DevelopersInternally the package structure and extensions have changed from net.refractions.udig to org.locationtech.udig. This blog post describes how to setup a development environment and update your plugin accordingly.Target Platform and EnvironmentFor instructions on using the project straight from GitHub (and building from Eclipse or Maven) see the project README.We also provide a uDig 1.5.0.RC1 SDK as a stand-alone target platform: 1. Download the SDK2. Unzip the SDK into a udig-sdk folder.3. Open up Windows > Preferences and navigate to the Target Platform page4. Set the target platform to the location of your udig-sdk folder. This will take a few moments while the folder contents are scanned.As a standalone target platform you can develop uDig with a recent version of Eclipse (uDig no longer depends on your development environment when running). The target platform also includes the JAI and ImageIO bundles which previously were installed as JRE Extensions.Thanks to Frank for these ease-of-use improvements for uDig developers.Dependency and Extension Point Migration At a high-level your plugins must be updated to use the org.locationtech.udig packages and extensions. This can be accomplished with a search and replace, but we will take the time to point out strategies for updating a few specific files.You can turn off eclipse automatic build when performing these changes to save time.MANIFEST.MFRequired Bundles (Require-Bundle) and imported Packages (Import-Package) in MANIFEST.MF files should reflect the namespace schange as well. Its a simple search and replace within Eclipse (Search -> File...):Click Replace... to change to new namespace:Extension PointsExtension definitions based on uDig Extension Points have to be updated. Search for net.refractions.udig in your plugin.xml and feature.xml files and replace the string with org.locationtech.udigSource Code MigrationWith the build environment fixed up we can now move on to updating your source code.You can turn on eclipse automatic build now, a lot of compile errors are expected after re-compilation against the new udig-sdk target-platform. This time we can perform the same search and replace on "*.java" files. This should fix the vast majority of problems (as it updates both imports and any extension point references you happened to make use of in your Java code).If any package import errors remain, click with right mouse on the project and hit Source and Organize Imports. The uDig 1.5.0.RC1 is built using GeoTools 11.2. The GeoTools project provides an upgrade guide for those using a prior version of the library.Looking AheadIf you have any problems with the current udig-sdk or like to ask something we didn't addressed in this post feel free to contact us: IRC (Internet Relay Chat) #udig on freenode #geotools on freenode Via Twitter (@udigGIS) Developer mailing list at mailing list [email protected] (subscribe here).  The 2.0.0 Release expects no further API change, its only focus is the transition to Eclipse Luna (a branch is available for developers here). [Less]

The uDig community is pleased to release uDig 1.5.0.RC1. Release DetailsuDig Downloads (Mac, Linux, and Windows)Release NotesIssue Tracker Change LogGitHub TagNew FeaturesThis release supports a couple new features:The web view down points to ... [More] a GitHub page (rather than a wiki page). Thanks to Frank for this work.The style editor now supports arrows (as shown in the above map). Thanks to Emily and Refractions for this work.Packages have been changed to org.locationtech.udig allowing SDK developers to migrate at this time (see below).DevelopersInternally the package structure and extensions have changed from net.refractions.udig to org.locationtech.udig. This blog post describes how to setup a development environment and update your plugin accordingly.Target Platform and EnvironmentFor instructions on using the project straight from GitHub (and building from Eclipse or Maven) see the project README.We also provide a uDig 1.5.0.RC1 SDK as a stand-alone target platform:1. Download the SDK2. Unzip the SDK into a udig-sdk folder.3. Open up Windows > Preferences and navigate to the Target Platform page4. Set the target platform to the location of your udig-sdk folder. This will take a few moments while the folder contents are scanned.As a standalone target platform you can develop uDig with a recent version of Eclipse (uDig no longer depends on your development environment when running). The target platform also includes the JAI and ImageIO bundles which previously were installed as JRE Extensions.Thanks to Frank for these ease-of-use improvements for uDig developers.Dependency and Extension Point MigrationAt a high-level your plugins must be updated to use the org.locationtech.udig packages and extensions. This can be accomplished with a search and replace, but we will take the time to point out strategies for updating a few specific files.You can turn off eclipse automatic build when performing these changes to save time.MANIFEST.MFRequired Bundles (Require-Bundle) and imported Packages (Import-Package) in MANIFEST.MF files should reflect the namespace schange as well. Its a simple search and replace within Eclipse (Search -> File...):Click Replace... to change to new namespace:Extension PointsExtension definitions based on uDig Extension Points have to be updated. Search for net.refractions.udig in your plugin.xml and feature.xml files and replace the string with org.locationtech.udigSource Code MigrationWith the build environment fixed up we can now move on to updating your source code.You can turn on eclipse automatic build now, a lot of compile errors are expected after re-compilation against the new udig-sdk target-platform.This time we can perform the same search and replace on "*.java" files. This should fix the vast majority of problems (as it updates both imports and any extension point references you happened to make use of in your Java code).If any package import errors remain, click with right mouse on the project and hit Source and Organize Imports.The uDig 1.5.0.RC1 is built using GeoTools 11.2. The GeoTools project provides an upgrade guide for those using a prior version of the library.Looking AheadIf you have any problems with the current udig-sdk or like to ask something we didn't addressed in this post feel free to contact us:IRC (Internet Relay Chat)#udig on freenode#geotools on freenodeVia Twitter (@udigGIS)Developer mailing list at mailing list [email protected] (subscribe here). The 2.0.0 Release expects no further API change, its only focus is the transition to Eclipse Luna (a branch is available for developers here). [Less]

Easier collaboration to internationalize UDIGDuring the FOSS4G conference Andrea Antonello and myself we'd the chance to improve Internationalization workflows for users and developers. It was a goal to migrate all User Interface (UI) labels and ... [More] messages to Transifex translation platform.BackgroundIn UDIG several UI labels, dialog titles, and messages are externalized from the core Java code and are stored in properties (*.properties) files. Each file has keys on the left to access messages. The message text is separated from the key by an equal sign, e.g.:OpenFileDialog.dialogTitle = Open File Dialog In the origin file, which is named messages.properties the messages for all UI elements are stored in English. To translate UI elements its only required to have a new message properties files for a specific language, e.g. messages_de.properties for German translations. For more details about Java internals have a look at the Java properties files tutorial.About TransifexTransifex provides a platform for translation teams to add, modify, and review text strings. Its possible to set up resources in a way that changes in a public accessible Source Code Repository can be pulled. In addition to this translated properties files can be synchronized back into a working copy with a Python based client tool. A client executable for Windows environments is also available (Python isn't required). However, if you don't want to install a tool you can use Transifex' REST API to achieve the same results.A neat feature is the translation memory for each project. Translators can add words or phrases and can comment the translations. The web front-end looks like this, where you can see suggestions from already translated strings and underlined words already defined in translation memory.Current StateTransifex project After half an hour sed coding with Andrea a project has been created and configured at Transifex for all UI elements of the current code base. We identified two different type of properties files, plugin.properties and messages.properties. For all bundles we found 110 resources and pushed these and its already available translations:To join a Translation Team you have to create a Transifex account or use your Social Account such as Twitter, Facebook, Google+ or even LinkedIn. Go to the main page and choose LOG IN top right.Origin Resources will be synchronized in a daily manner from our Github repository to keep up-to-date with added, changed or even deleted text strings for UI elements.Transifex client tool configurationThe client tool needs a configuration on client side. Its a simple text file which should be stored in a .tx folder of your working copy. Its name is config and contains configurations for each resource - where to find it in the workspace and how the resource is accessible from Transifex (project slug and resource slug).An initial configuration is available right here.If you're interested to contribute feel free to join a Translation Team. Happy Translating!! [Less]