Starting to get really frustrated with how long features are taking to develop. We only have 55 users, but with the developer pack, it should easily cover the wage of a developer. And given the amount of bugs appearing, they need more people.

Seems like Sandbox testing is an unknown quantity.....

We find that all “lines” we want we make a drawing of on the map (using MBTiles) and then we use Fulcrum to gather information about a “point” on that line. We never really capture information about the “entire” line. For example and town’s levee bank which is a line many kilometres long. Or if we want to describe a section of that “line” (I.e. type of levee, height etc.) we just create a point along that line to do that. Any report we generate we always seem to draw the levee on one page and have a table of observations on another page.

We don’t need to have the “start / end” point co-ordinates WITH the data. However, in saying that, there are a few people in our organisation (who are ESRI GIS users) who are “used to thinking” it’s needed (essential?), but in reality, it’s (most often) not.

And maybe a simple solution for Fulcrum to develop is to have a separate Child Database containing the drawing “co-ordinates” associated with each record.

Paul Wheeler - "If we had the ability to use lines and polygons, we would replace ArcGis and overall company usage would expand significantly"

Same request from me too.

You show how to capture a line using CURRENTLOCATION() in your Data Events/Examples/Capturing vector coordinates example.

It would be a great idea to be able to display this information (Maybe using SETPOINTLOCATION()?) when revisiting the site.

Are there any updates on this functionality? Like many of the commenters state below, this remains the biggest hurdle for getting more widespread adoption of Fulcrum in our organization and the larger environmental community.

Honestly as a shortcut if lines and polygons will take longer to develop, allow a single form to have multiple points. All lines and polygons are just made up of vertices and even if its on the back end, linking all the points to one RECORDID would allow for a lot more workflows with more complex geometry. I see it working like Repeatable sections, just with the location pins.