THE MAPNIB FIELD GUIDE

A better starting point.
A more useful result.

Practical guidance for moving from a floor-plan image to geographic linework. Know what to bring, what to review, and what to expect.

01 / PREPARE

Clean input makes the difference.

Choose a flat, high-contrast black-line PNG or JPEG showing one floor. Use a white or transparent background and readable, uninterrupted strokes. Keep a copy of the original and confirm that you have permission to process the drawing.

  • Crop unrelated borders and remove unnecessary labels or furniture where possible.
  • Have one reliable measured distance and the plan’s orientation available.
  • Avoid perspective photographs, colored plans, and noisy or distorted scans.

Current input boundaries

The development converter accepts up to 20 MiB, 16 megapixels, and 12,000 pixels per side; minimum dimensions are 16 × 16 pixels. Images may be downsampled. These are technical guards, not published service allowances.

02 / REVIEW

A trace is a starting point, not a finished map.

MapNib follows the centerlines of visible raster strokes. Two drawn edges of a wall may produce two lines. Text, dimension marks, and furnishings can also be traced.

The development editor lets you compare source and trace, exclude unwanted strokes, move vertices, add or delete line segments, and draw polygon areas. Choose Add polygon, place at least three corners, then Finish polygon. Each polygon has one exterior ring; holes and crossing edges are not supported. Review the geometry before saving a revision. Saved revisions and undo serve different purposes: save the work you want to keep.

NEW / EDIT WITH CONTEXT

Refine the geometry. Describe the rooms.

Guided repairs

Review suggested gaps, duplicate geometry, and overlapping room warnings. Preview a gap repair before applying it. Keep intentional openings such as doorways; overlapping rooms require your review rather than an automatic merge.

Smart snapping and shared boundaries

Snap corners to nearby vertices and room edges. Toggle right-angle drawing when you need 90° segments. With shared-boundary editing enabled, moving a shared polygon wall or vertex updates adjoining rooms together. Invalid shapes are rejected, and undo restores the complete edit.

Room names, types, and measurements

Create a polygon for each room, give it a name, and choose its type. Area and perimeter use the calibrated scale and update with the geometry. Estimated inputs remain labeled as estimated. These measurements are not a certified survey or a substitute for checking the source drawing.

Watch the editing walkthrough ↗

03 / PLACE

Connect the drawing to its location.

Set the scale

Identify two points with a known measured distance. Record the distance and its source. An estimated measurement should stay labeled as estimated.

Position and rotate

Search an address, select the correct match, and check its position on the map. Verify that the coordinates represent the center of your image, then set the clockwise rotation. The image center is the geographic anchor, even if you remove some lines.

Check the result

Compare the placed linework against a trusted reference, then check it again in your destination mapping tool. Geographic placement does not establish survey accuracy.

04 / EXPORT

Familiar data. Flexible next steps.

The output is a GeoJSON FeatureCollection containing LineString features and manually drawn Polygon areas. Coordinates use WGS 84 longitude first, latitude second. Saved exports include stable feature identifiers, compact coordinates, and scale/provenance metadata. Named room polygons also include roomId, name, roomType, areaM2, and perimeterM properties. Room IDs stay stable within a project.

The sample below contains the same nine linework features displayed in our interactive demo. It is a synthetic 20-meter-wide example centered at 0°, 0°, with estimated scale. It is not a real building or a customer result.

Original image bytes and editing history are not part of the GeoJSON export. Room labels shown in the demo are illustrative and do not represent inferred room data.

Download example GeoJSON

05 / SCOPE

A focused tool, with clear boundaries.

The current scope does not include PDF or CAD ingestion, multi-floor registration, automatic room recognition, BIM, routing, automatic georeferencing, or survey-grade accuracy. Specific destination integrations and customer conversion quality remain to be validated.

The public site provides a synthetic demo. The complete workflow is available to invited testers using synthetic plans. Public enrollment and real charging remain disabled.

Read about early access ↗